Yeah hey,
So I was running Trinity kernel and noticed a lot of random system freezes and so I reverted back to stock kernel through this thread I just made. I flashed the 4.1.1 stock kernel zip over the trinity kernel.
My phone got stuck in Boot Screen (Didn't see a boot loop, just stuck there while the Animation plays for infinite time) I took the battery out, then rebooted... same thing.. So I was gonna wipe and reinstall the whole thing through recovery (CWM), I pulled the battery, held Power + Vol down.. I was expecting recovery, but then I saw a Fastboot screen ("Odin Mode" as labelled in the top left corner) with only one single option ("START") and a label that says "Downloading..."Then system info ("Tuna" and the other stuff)
Now MY MAIN QUESTION:
Did I lose my CWM recovery system restore zip?? The one in the virtual "SD" Card?! PLEASE SAY I DIDN'T!!!
Now second question, how do I get things back to normal?? :crying:
Vol up + vol down + power :highfive:
Then use the volume key to select Recovery
CMNein said:
Vol up + vol down + power :highfive:
Then use the volume key to select Recovery
Click to expand...
Click to collapse
Oh, Thanks.
Just tried that and DID get recovery as an option, clicked it, and just *poof*... Nothing happened..
I think the battery was 11% when it all started so I'll give it 30 minute and try again. And update this accordingly.
If you were referring to your clockworkmod folder in the first post, would be wise to pull it via adb in case you have to completely wipe your phone.
CMNein said:
If you were referring to your clockworkmod folder in the first post, would be wise to pull it via adb in case you have to completely wipe your phone.
Click to expand...
Click to collapse
Could you please guide me to somewhere where this method is explained? I really want to pull that file any way possible.
I'm not the best in using adb..
But I'm now about to install Win7 or Linux to be able to use adb.
This is probably the easiest to follow initially: http://forum.xda-developers.com/showthread.php?t=1058431
If in doubt there are dozens of other adb guides/tutorials on XDA and elsewhere. Just take your time.
CMNein said:
This is probably the easiest to follow initially: http://forum.xda-developers.com/showthread.php?t=1058431
If in doubt there are dozens of other adb guides/tutorials on XDA and elsewhere. Just take your time.
Click to expand...
Click to collapse
Thank you for the help. Recovery just worked and my restore file is still there.. So I'll try reflashing and if it failed I'll wipe and reflash.
I can manage on my own when recovery in intact.
Thank you -and people like you- for making this forum such an amazing place.
Related
Hi,
I recently rooted my phone through VISIONary+ r14 and today downloaded ROM Manager. I flashed ClockworkMod Recovery, but I can't back up my current ROM (stock/branded). I want to make a complete 100% backup of my current phone to be able to restore later if I need to.
However, I don't know how to do it. There is a 'Backup current ROM' option on ROM Manager, but whenever I do it my phone restarts showing the black screen with the phone and the red Caution exclamation mark + triangle, so I have to hold Volume Up and the Power button to restart my phone.
What do I do?
Also, it may be worth mentioning my Desire HD is a Vodafone Australia branded phone which hasn't been updated at all.
Well, the triangle image thingy means you dont have recovery flashed...
So, you have to choose 'Flash ClockworkMod Recovery' first. - That wil download a file from the internet and install it for you, so make sure you have internet connection
That will flash/install a recovery for you, in which you can create a backup.
Oh and i think you need to S-OFF your phone before installing recovery (im not sure about that but thats what i've heard)
click here for S-OFF http://forum.xda-developers.com/showthread.php?t=855403 --the last process says that after S-OFF you can install CWM recovery
noodlesfordaddy said:
I flashed ClockworkMod Recovery,
Click to expand...
Click to collapse
Can you confirm if you did this separately to ROM Manager or as per above, used the Flash Recovery option in ROM Manager?
Have you confirmed you do have root?
If you reboot into recovery do you get to the clockworkmod recovery screen? What version is it?
If root can't be confirmed, re-do the visionary method. If root is confirmed but can't get to CWM-R do as per above and flash recovery from RM console.
Yes, I can confirm it is rooted.
I just ENG S-OFFed, so I'm going to try flashing recovery once again, although I'm still pretty sure it worked before that since Clockworkmod says "Current Recovery: ClockworkMod 3.0.2.6, Latest Recovery: ClockworkMod 3.0.2.6"
Will I do damage flashing it again?
EDIT: I pressed Flash ClockworkMod Recovery again and it waited for a little and then said that it was successful.
EDIT 2: Attempting another backup... And it's working!
No, you won't damage the it.
As I fly through different ROM's and do lot's of restores and backups I often have times where I need to reflash recovery.
look uot the link in my signature and try to do what it explanes......
Do all fases of rooting and you will have a perfectly rooted phone.
Also follow suggestions of CodeNameUnknown1.
Try man....Try
noodlesfordaddy said:
EDIT: I pressed Flash ClockworkMod Recovery again and it waited for a little and then said that it was successful.
EDIT 2: Attempting another backup... And it's working!
Click to expand...
Click to collapse
Great news!! Glad you got it sorted so far.
So, I have a problem.
I pressed the Backup option in ROM Manager, and the phone restarted, I'm now in Recovery mode... But I have a very strange problem. I can't make any selections.
I can scroll through the menu options fine, but can't select anything. If I press the power/lock button, the menu goes away and the clockworkmod logo in the middle just brightens up. If I press the home or menu buttons, the same thing happens, and if I press them again the menu just reappears. The return and search buttons do nothing except vibrate. What the hell?
That's an odd one.
Can you boot into recovery by turning phone off then holding vol- press power button and go to recovery from there? Does this do the same thing?
If same then I would uninstall ROM Manager and flash the recovery again via fastboot (in which case you can download the 3.0.2.8 version (page 3 ish of the development forum). Then try again.
Then re-install ROM Manager (which will show wrong version but ignore it).
At the moment I'm having trouble trying to turn off the phone at all :S looks like I'm actually going to have to open this horrible battery cover.
EDIT: After a battery pull I tried holding the Vol+ button and power button but it has just booted normally.
I can't actually try the vol- and power because my volume down button simply doesn't work...
EDIT 2: Uninstalled ROM Manager, reinstalled, booted into Recovery Mode, now it's backing up right next to me! Yay!
So I assume that, once it's done, I just take one big file it makes and put it on my laptop or something?
EDIT 3: Okay, one more step and I should be completely rooted with no hassles.
Will this method (http://forum.xda-developers.com/showthread.php?t=857537) work for a branded phone? It says it requires a stock kernel. My phone meets all other requirements, but is the kernel of a Vodafone AU branded Desire HD 'stock' enough to work with this S-OFF tool? I would attempt it but I'm a little worried I might screw something up.
noodlesfordaddy said:
EDIT: After a battery pull I tried holding the Vol+ button and power button but it has just booted normally.
I can't actually try the vol- and power because my volume down button simply doesn't work...
Click to expand...
Click to collapse
Is this still an issue? If so you really need to get that fixed!!
noodlesfordaddy said:
EDIT 2: Uninstalled ROM Manager, reinstalled, booted into Recovery Mode, now it's backing up right next to me! Yay!
So I assume that, once it's done, I just take one big file it makes and put it on my laptop or something?
Click to expand...
Click to collapse
Yep.
noodlesfordaddy said:
EDIT 3: Okay, one more step and I should be completely rooted with no hassles.
Will this method (http://forum.xda-developers.com/showthread.php?t=857537) work for a branded phone? It says it requires a stock kernel. My phone meets all other requirements, but is the kernel of a Vodafone AU branded Desire HD 'stock' enough to work with this S-OFF tool? I would attempt it but I'm a little worried I might screw something up.
Click to expand...
Click to collapse
You are good to go.
Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.
I had me phone sitting beside me. I had just turned off the screen. Then it randomly started bootlooping. I can get into the recovery screen ( Fboot, Hboot, Recovery, Etc... ) I think it might be the power button some how?? It doesn't boot loop until I turn on the phone. I've tried different batteries. Got any ideas??
jonahly said:
I had me phone sitting beside me. I had just turned off the screen. Then it randomly started bootlooping. I can get into the recovery screen ( Fboot, Hboot, Recovery, Etc... ) I think it might be the power button some how?? It doesn't boot loop until I turn on the phone. I've tried different batteries. Got any ideas??
Click to expand...
Click to collapse
Cannot get into the actual recovery!!! But I can get into the little android guys on skateboard's screen!
jonahly said:
Cannot get into the actual recovery!!! But I can get into the little android guys on skateboard's screen!
Click to expand...
Click to collapse
Hahahha,you made my day bro,thats the bootloader,see if you can access the recovery from there,if not,guess its time to start over and you might as well do it right,unless you have already done,what im about to show you....
<<<<Takes a breath.....Ok go here and read the whole OP,then go here and read the instructions and partition your sd card.Then go here and install DT's ap2sd.Download the recovery here and the rom of your choice.Boom!
That did not help. I cannot get into recovery!!!
jonahly said:
That did not help. I cannot get into recovery!!!
Click to expand...
Click to collapse
Have you tried installing a new recovery? I recommend downloading SmelkusMod Recovery from http://forum.xda-developers.com/showthread.php?t=1661543. Download a zip version such as PC36IMG_ra-supersonic-4.3-smelkus-aokp.zip to your computer, rename the file to PC36IMG.zip (watch out for Windows hidden extensions), copy PC36IMG.zip to the root folder of your EVO 4G's sdcard, and power the phone off. Then simultaneously press and hold the volume down and power buttons until the bootloader starts, allow the bootloader to scan for updates, and press volume up to confirm that you want to install the updated recovery.
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
justsomedude23 said:
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
Click to expand...
Click to collapse
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM(clockworkmod) is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache(the factory reset in TWRP), but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search.
But if its loading to the CM logo, it is not a paperweight. Worst case scenario you can use LGNPST and a stock bin file to go completely back to stock. But as long as you can get into recovery you shouldn't have to go to those lengths.
Hope this helps.
EDIT: I know it's your phone and if you are like me, it's probably your only phone. But don't panic, real bricks are rare and if you can get back into recovery you are usually fine!
HPTesla said:
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache, but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search. Hope this helps.
Click to expand...
Click to collapse
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
justsomedude23 said:
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
Click to expand...
Click to collapse
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
HPTesla said:
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
Click to expand...
Click to collapse
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
justsomedude23 said:
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
Click to expand...
Click to collapse
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
HPTesla said:
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
Click to expand...
Click to collapse
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
justsomedude23 said:
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
Click to expand...
Click to collapse
Good stuff man, glad to hear it and you're welcome!
From a full power off, how do I boot into stock recovery? I've tried multiple button configurations and none work.
EDIT:
I called T-Mobile and they said:
1. Power off
2. Press and hold the Vol - and Power button until the LG boot screen appears.
3. Release the Power button ONLY. Do not release the Vol - button.
4. After 1 second, press and hold the power button again. You should see the white recovery screen.
Use the Vol+/- to navigate and Power to select.
This brought up a Factory data reset menu on my H815.
Brings up factory reset on T-mo version H-811
That is the LG factory recovery.
thank you this worked
With a Verizon model, I had to keep holding both Power and Vol - until the recovery screen appeared. If I released and then re-held Power, as described above, it did not work.
When I hold down power and vol down, it boots to an IMEI display screen. It shows a long barcode. Can't get to recovery with the hold, release and hold down again the power and volume down buttons. Frustrating.
I love you so much right now. It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
THANK YOU!!!
amd206 said:
I love you so much right now. It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
Click to expand...
Click to collapse
I love you!
Your comment just saved me from doing a complete factory reset!
I never clicked "Yes" in the Factory Reset phone option because I thought it would do just that. Instead it took me to TWRP!!
gonsa said:
I love you!
Your comment just saved me from doing a complete factory reset!
I never clicked "Yes" in the Factory Reset phone option because I thought it would do just that. Instead it took me to TWRP!!
Click to expand...
Click to collapse
This is funny because It just factory reset my phone.
joesee said:
This is funny because It just factory reset my phone.
Click to expand...
Click to collapse
oh no!
how come it has different outcomes..
sorry to hear that.
Sent from my LG-H815 using Tapatalk
gonsa said:
oh no!
how come it has different outcomes..
sorry to hear that.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
The difference was that you have twrp recovery and he didn't. The question pops for both, but for those that have the original recovery it will do the factory reset.
worked
worked for me, but the first screen is the one where it ask if i want to factory reset, i had to pick YES, then again confirm, and then i was in TWRP
gonsa said:
I love you!
Your comment just saved me from doing a complete factory reset!
I never clicked "Yes" in the Factory Reset phone option because I thought it would do just that. Instead it took me to TWRP!!
Click to expand...
Click to collapse
joesee said:
This is funny because It just factory reset my phone.
Click to expand...
Click to collapse
And I get a factory reset as well on my H811, even though TWRP was already installed and working on the recovery partition.
Something else funny going on, the OS seems to kill TWRP after the next one or two boots tho. Maybe I need to set the TWRP option to allow change of the system partition to read/write? (Since apparently it writes something there that prevents the OS from killing the custom recovery after it's been installed)
Exabyter said:
And I get a factory reset as well on my H811, even though TWRP was already installed and working on the recovery partition.
Something else funny going on, the OS seems to kill TWRP after the next one or two boots tho. Maybe I need to set the TWRP option to allow change of the system partition to read/write? (Since apparently it writes something there that prevents the OS from killing the custom recovery after it's been installed)
Click to expand...
Click to collapse
I've learned a lot with LG phones over the past few weeks.
The biggest thing is.. when you first flash over TWRP, you HAVE to reboot into recovery before you try rebooting the system, or else the bootloader will overwrite the TWRP install and replace it with the factory recovery.img. (You probably already know this.) To make sure it boots into TWRP first, since fastboot doesn't have a "reboot-recovery" command.. I just pull the battery then do the button combination to boot directly into TWRP. Doing this allowed me to say "YES" to the question "Do you want to factory reset the phone".
I don't know how many times I've wiped my phone because of this:
1. flash TWRP.
2. reboots (tries to hold the finger combo but failed - and didn't know it)
3. gets asked question - "do you want to factory reset the phone"
4. I hit YES expecting it to take me to TWRP - but instead it wipes the phone and puts stock recovery back on.
Just do this:
1. flash TWRP.
2. PULL THE BATTERY
3. Use finger combo to boot recovery.
4. When asked "do you want to factory reset the phone" - hit YES
5. TWRP boots in like 5 seconds.
This has worked now for my G4 and my V10 since they both have this issue. The V20 however does not (my current phone) - so hopefully LG is done with this crap!!
Good luck!
joesee said:
The biggest thing is.. when you first flash over TWRP, you HAVE to reboot into recovery before you try rebooting the system, or else the bootloader will overwrite the TWRP install and replace it with the factory recovery.img. (You probably already know this.)
Click to expand...
Click to collapse
What was happening on my H811 was that it was either corrupting the recovery partition afterwards or just invalidating it or something because instead of getting back the stock recovery, I'd get the scary "broken robot" screen when trying to boot into recovery.
joesee said:
To make sure it boots into TWRP first, since fastboot doesn't have a "reboot-recovery" command.. I just pull the battery then do the button combination to boot directly into TWRP. Doing this allowed me to say "YES" to the question "Do you want to factory reset the phone".
I don't know how many times I've wiped my phone because of this:
1. flash TWRP.
2. reboots (tries to hold the finger combo but failed - and didn't know it)
3. gets asked question - "do you want to factory reset the phone"
4. I hit YES expecting it to take me to TWRP - but instead it wipes the phone and puts stock recovery back on.
Click to expand...
Click to collapse
The technique I've learned to appreciate (which apparently is a new thing, and is now the suggested method for installing via fastboot according to the twrp.me website) is to load a copy of TWRP into RAM to do the flashing and rebooting. ("fastboot boot [TWRP_IMAGE_NAME]")
I try to avoid battery pulls as much as possible but I have never relied on them on a phone the way I have done over the last week (just had my G4 for about a week now) due to these funky mechanisms that LG has for getting into recovery/bootloader/download mode.
joesee said:
Just do this:
1. flash TWRP.
2. PULL THE BATTERY
3. Use finger combo to boot recovery.
4. When asked "do you want to factory reset the phone" - hit YES
5. TWRP boots in like 5 seconds.
This has worked now for my G4 and my V10 since they both have this issue. The V20 however does not (my current phone) - so hopefully LG is done with this crap!!
Click to expand...
Click to collapse
TBH I am fearful of even trying it now. (Especially since I just read about how a nandroid backup done from TWRP doesn't backup anything on the /data partition, either.. )
Which makes me even more appreciative of LineageOS's "advanced reboot" power button menu. :good:
One of the problems in my view with this LG system is that it can be very difficult to reliably press both the power and volume at the same time on this phone due to it's unusual placement of those buttons. Much harder than on a phone with those buttons on opposite sites of the device. Not to mention this silly "press both these, then release one, then 1s later press that one again" stuff.
And due to the way they designed these sequences, which among other things often have no way to easily escape them (can you imagine having this on a phone with a non-removable battery?? ), but worse, have defaults that progress to another state without any user interaction (because of the limitations of this control logic - eg, if you boot to bootloader but can't escape and don't do anything in 2 minutes, the device automatically reboots), I personally have to wonder if this doesn't make a significant contribution to the infamous bootloop issues that lots of people are having with recent LG's like the G4, G5, V20, etc.
joesee said:
Good luck!
Click to expand...
Click to collapse
Thanks.