like everybody else says, be nice or you'll not get more help. chill. I doubt anyone will give more nice warnings.
when you get errors like that with any rom, wipe system data and cache then reflash it again in recovery.
[TWRP RECOVERY][OS2SD][INTERNAL][KITKAT ROM DEV] - TechVendetta
- Thread starter TechVendetta
- Start date
when you get errors like that with any rom, wipe system data and cache then reflash it again in recovery.
Recovery is black screen remember? I can't use it! I can't flash new one due to root issue! What should I do?
you'll have to see if adb works in the black recovery. if it does you can reflash it from there.
I love the recovery so far! I don't use all the features.. (I flashed the kitkat from the other thread, just because I need mms.:x)
I'm having a bit of a problem flashing the int2ext scripts though.. I only have one sd-ext, meant for internal (with the int2ext script mentioned)
Am I right that I need to mount OS2SD system and internal system first?
I'm having a bit of a problem flashing the int2ext scripts though.. I only have one sd-ext, meant for internal (with the int2ext script mentioned)
Am I right that I need to mount OS2SD system and internal system first?
Casey and others new to phone rooting/hacking/testing:
I can't emphasize this enough. Most of the people experimenting with recoveries and kitkat roms in the Optimus Rooting, ROMs and Hacks forums are doing so on a second/spare phone. Things are not yet stable enough to be installing this stuff on your main phone that you need to have everything working on unless you really know what you are doing.
Unless you are a developer or someone who has been doing this sort of stuff for a while and knows his way around adb, you are quite likely to end up with a messed up phone. Using adb running on your computer gives you the option to interact with both the rom and the recovery via usb - either can be used to recover the other. And you never want to change both of them at the same time - it's too risky! By using your backup/spare/extra phone for testing/experimenting you don't need to panic when things don't work or there's a problem. The spare phone I use for playing with kitkat stuff was given to me by a friend when he upgraded to a new phone and provider. They are also available pretty cheaply on places like ebay.
If you only have one Optimus phone and you need for everything to work then you should be running Mirage's gingerbread rom on it. It is the most stable and well-tested rom for this phone, by far. Yes, it's only gingerbread, but everything works well and it's stable and reliable. Mrg666 still maintains it to this day and integrates any updates that are needed. Thanks, Mrg666!
If this is your only phone and you do not know how to use adb to work with both a recovery and a rom from your computer using a usb cable, then you are in great danger of bricking your phone. And that is a royal pain to recover from and there is a risk that you will not be able to use your phone to make regular phone calls again. Do some searching in the Optimus forums about phone unbricking and critical information you should preserve before messing with it. Is it a ZV4 or ZV5? Does it have the new screen or the old screen? Have you recorded the AAA and HA shared secret values for your phone? At the rate you're going, you may need the recovery information! And, given your attitude, don't be expecting people to jump through many hoops to help you.
Last edited:
Ah.
I was flashing the internal rom, but with the TWRP recovery. I think I'll just take the plunge and use the OS2SD rom.
I was flashing the internal rom, but with the TWRP recovery. I think I'll just take the plunge and use the OS2SD rom.
brotherswing
Well-known member
- Feb 24, 2011
- 555
- 167
- 0
Casey, first of all, please stop beginning your posts with accusations. Secondly, a quick Google search for QtADB will provide the best tool for working with ADB for those inexperienced with it. Full GUI interface and many functions are automated. I understand how stressful it is when you think your phone may be bricked, but seriously, every thread here is experimental and has a disclaimer. If you didn't realize that there's always a possibility that your phone may be damaged by these actions, and if you didn't see (or disregarded) the warnings, then perhaps Android modification might not be the best hobby for you. Again, please try to be more respectful, otherwise you most likely will not receive any further help.
Sent from my HTC_A510c using Tapatalk 2
Sent from my HTC_A510c using Tapatalk 2
Yeah sorry everyone, I'm busy preparing for a hacking competition in new york this week so I haven't been able to keep up with all my various side projects. As for Casey, if I remember correctly the maker of the flash image gui actually had issues with black screening which is why it was abandoned for the most part. Since you already had a custom recovery, you clearly neglected the zip version that could have been flashed from recovery. As for your root issues, odds are you were probably using some form of apps2sd and messed up your sdcard or grew dalvik too large causing a partial data reset and permission errors. This is a known issue that has plagued this phone ever since roms started using more data. There are various other methods to recover, from re-installing or rerooting to recovering from fast boot or using adb.
As for the other issues, there is a known issue with usb storage mounting. This is due to twrp using a different fstab format, I have a fix for it, just haven't had the time to apply and test it. And Squid, that lazy system mount was what I was asking about. That's how devs used to do it back around gingerbread, before devices started using internal storage that was actually a soldered in sd card. Its standard practice now to use the block mounts.
And yeah my focus for this twrp was for os2sd roms because honestly we're at the point now where that is becoming one of the only options to keep these phones running the latest code. The sd partitioner I added really makes it so much easier for people to take the plunge. I added the internal rom support mainly for backwards compatibility and the potential for future dual booting. I'm also running squid's os2sd build, mainly because I'm too damn busy to merge his mms fix and add in my power and time fixes. I'll have more time for dev work some time next week.
One other thing I noticed about mounting.
On booting into recovery, in mounts, you have "OS2SD" and "Internal" system,data, and cache.
After formatting the "OS2SD" partitions, the names become system, data, and cache. The "Internal" partitions become system_internal etc after formatting them.
mounting/unmounting in the menu does not affect the names.
On booting into recovery, in mounts, you have "OS2SD" and "Internal" system,data, and cache.
After formatting the "OS2SD" partitions, the names become system, data, and cache. The "Internal" partitions become system_internal etc after formatting them.
mounting/unmounting in the menu does not affect the names.
Last edited:
Those should be just mount points. Mtd blocks don't have labels, there's a start and end assignment with fake labels usually in bootloader or kernel. For backup and restore purposes twrp uses the mount point names. Which is how it knows where to restore to.
Posted via Android Central App
I was just referring to the "what-u-see' when running recovery. The actual mount points don't change, yes. Bootloader holds the atag data, kernel deciphers it. I remember looking over the kernel bit for that while porting it.
My last side project was reverse engineering the Coby Kyros tablet. I actually hexedited the u0 bootloader and modified the block partition map. xD Pretty risky business however. But it sure solved the storage issues on that tab. The default map was total crap.
I'm still having issues with both internal and ext partitions mounting to /system at the same time. Shouldn't happen... both CrossBreeder which is generic about mounting and the sd-gapps which specify mount points do it, and not consistently.
//edit: seems to happen after messing in the mounts menu. if I leave the mounts alone the sd-gapps flash fine.
//edit: seems to happen after messing in the mounts menu. if I leave the mounts alone the sd-gapps flash fine.
Last edited:
Silly question.
What do I need to do to allow your recovery to see my backups made with a ClockworkMod recovery?
What do I need to do to allow your recovery to see my backups made with a ClockworkMod recovery?
Do you still have a black screen in the recovery mode? If you need help to straighten out, start a new thread and I'll be happy to help you fix it.
Another silly question:
Has anybody backed up the OS2SD KitKat with this recovery, and successful restored said backup?
Has anybody backed up the OS2SD KitKat with this recovery, and successful restored said backup?
Is there a way to button-press boot to recovery or fastboot? Otherwise I might be bootlooped to death...
I was playing with OV-KitKat, didn't like the battery life + random FC's, decided to go back to Mirage. I altered my SD partitions back the way they were using Minitool Partition Wizard. Phone attempts to actually boot (obviously, to nothing) with USB cable connected. LG logo over and over again.
Any suggestions on key combo to boot to fastboot or recovery so I can start over?
Sorry, disregard, got it, don't know if maybe I wasn't pressing buttons hard enough.....
Hold volume down, hold Home, hit Power.... same as usual.
I was playing with OV-KitKat, didn't like the battery life + random FC's, decided to go back to Mirage. I altered my SD partitions back the way they were using Minitool Partition Wizard. Phone attempts to actually boot (obviously, to nothing) with USB cable connected. LG logo over and over again.
Any suggestions on key combo to boot to fastboot or recovery so I can start over?
Sorry, disregard, got it, don't know if maybe I wasn't pressing buttons hard enough.....
Hold volume down, hold Home, hit Power.... same as usual.
Last edited:
Similar threads
Trending Posts
-
-
-
-
Notification sound when headphones are connected
- Started by chico777
- Replies: 0
-
Facebook
Twitter
Instagram