Related
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
jaysonic88 said:
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
Click to expand...
Click to collapse
LG Bridge doesn't see my device either =(
alane708 said:
LG Bridge doesn't see my device either =(
Click to expand...
Click to collapse
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
jaysonic88 said:
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
Click to expand...
Click to collapse
Yeah windows sees it as a Portable Device (Attached), I can transfer files to it.
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
slayerh4x said:
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
Click to expand...
Click to collapse
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
alane708 said:
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
Click to expand...
Click to collapse
Mine showed the bootloader message and they still took it back.
slayerh4x said:
Mine showed the bootloader message and they still took it back.
Click to expand...
Click to collapse
I guess I can only wait for a custom ROM now
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
mrbigdrawsz said:
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
Click to expand...
Click to collapse
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
What variant are you using?
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
WishRyder said:
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
Click to expand...
Click to collapse
Awesome. I was getting a little worried myself when I was stuck in TWRP because I was trying everything I could think of.
I didn't think the backup part was necessary but it's one of those things where you mention everything you did just in case.
check this out https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
^ This 100% worked for me after my h918 got stuck in recovery after I got a system update message and accidently selected "reboot & install".
Thank you imucarmen!!!!:good::highfive:
OMG thank you so much. Merry Christmas to me. It worked like a charm. Tytyty
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had the same issue after rooting with Dirty Santa and have been sweating it for the past hour. Stumbled upon your solution and voila! THANK YOU!!
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had some trouble following this at first but it indeed worked.
My v20 was stuck in TWRP (3.0.2-1) after forgetfully hitting OK on the System Update, it was running H91810q and was previously rooted.
I first backed up my phone in TWRP to my SD card and then copied that to my laptop.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
I held Power+VolumeDown, released Power while still holding volume down and I got the white Factory data reset screen. I choose Yes on the next two options to perform the factory reset.
Then it restarted and went back into TWRP. I choose Mount, selected System, pressed Mount USB Storage, then Unmount, Reboot, System.
It booted and took a while since I also flashed the H91810t rom to do an upgrade at the same time from here:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
0m3ga said:
I had some trouble following this at first but it indeed worked.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
Click to expand...
Click to collapse
Glad you got it working. As far as the issue with the instructions that could be down to a change in the newer versions of TWRP. I posted this 16 months ago and many new versions of TWRP have come out since. I remember trying to be extremely accurate in my instructions but it is possible I screwed up. Been too long ago and I can't remember now.
Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Pretty sure you are using msmdownloadtool wrong. Completely shut down the phone. Make sure to DISCONNECT the phone form pc. Hold vol up and vol down for 5 sec. And it should unbrick hour phone
Hold power and volume up till the phone shuts off...
Now with the device completely powered off hold both volume buttons down at the same time for about five seconds then while continuing to hold both volume buttons plug USB in from pc to your phone the screen will be black and it's normal.... After this it should be showing up in the MSM tool....
It showed up in the MSM tool, but when i click start it goes for 4 seconds and then tells me that it doesnt recognize the image.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Yes, i was on the NoLimits rom and wanted to stop using it since i felt it was impacting a few things on my phone that i didnt like, but i really enjoyed Viper4Arise. So i was trying to flash V4A and after i was done flashing it wouldnt load past the unlocked bootloader screen, and i was stupid enough to not create a backup before i started because i didnt think V4A would be that harmful. After trying to wipe my phone and start fresh, i got stuck in the recovery loop.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Also, whats a good thread to get the system image?
Bildo41383 said:
Also, whats a good thread to get the system image?
Click to expand...
Click to collapse
If you are booting into recovery, first try formatting your data. In OnePlus's recovery, select English, and somewhere there is an option to "ERASE EVERYTHING." This will format the partition for OOS. On TWRP, go to Wipe--> Format Data. That may fix the bootloop.
If this does not fix it, the MSM download tool is a good option, however, I see it did not work for you. You can download OnePlus's official ROM from here, and for that, you want to flash it in TWRP like any other mod, then reboot. If you are still boot-looping after that, try formatting your data again for good measure.
For the MSM Download tool, you MUST be on Windows, and you must have extracted the archive fully, which can be done by right-clicking on the ZIP and selecting "Extract all." Then, turn the phone completely off, no USB attached. Press and hold Volume Up + Volume Down, and connect the device to the computer. You should then be able to launch the MSM tool, selecting the normal one for the stock variant, and the factory_mcl for the McClaren variant. If your device does not show up, make sure you have installed Qualcomm drivers from here.
Good luck and I hope you get your phone working!
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
That happened to me as well with the 9.0.1.2 version.
What I did is I used an older version 9.0.1.1 works all the time. No matter what Rom you had previously installed, So try an older version.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
This saved my butt 100 times...whenever I mess with slot A and B and end up booting to recovery mode again n again
Hello, any help would be appreciated as I have seemed to have gotten Myself stuck on the screen that warns Me about the bootloader being unlocked. I hope this is in the right section of the forum.
So I have enabled at least 10 Magisk Modules at the same time, carefully read the files attached to them within the app, tried to make sure they didn't do too much to the system where I'd have to worry about this sort of thing happening but of course, with My luck, it did anyway. I plugged My device into My laptop to try to just flash the magisk_patched.img and it just brought Me back to the same screen, sometimes it would reboot itself several times before stopping when plugged in to My laptop. I've read somewhere that the Miracast module might be the culprit so I sought to enter TWRP through fastboot and delete the module BUT IT'S NOWHERE TO BE FOUND. I have also tried all these button combinations I kept seeing people talk about on various forums, like pressing all 3, Power+Volume Up, etc and holding them for various amounts of time and none of this has gotten Me past the warning screen. I seen something about uninmod but I've heard that this doesn't work on v.19+ and I can't seem to even find the magisk folder anywhere at all to begin with. I couldn't backup My phone because Google kept saying "waiting to backup" so I'm screwed if I have to just restart and hope it doesn't have to come to that.
My questions are:
Is there any folders I may be missing?
Is there any way to backup My device through TWRP or fastboot now even though TWRP won't mount and I can't boot into the OS?
Is there a way to delete Magisk or the modules that I can try, that I haven't mentioned/don't know about?
Thanks in advance!
Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?
Hw4ng3r said:
Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?
Click to expand...
Click to collapse
It's all good. No I wasn't going to mess with it until I done enough research or someone had replied and I had the time. I was thinking about doing something today or this weekend. I read some things online that I bookmarked about using the "pull" command on ADB, being able to save the image from TWRP after using the fastboot command to boot into TWRP, and I seen some other post on XDA about a certain method they used to stop bootloops. Even though I don't have bootloops, I'm just stuck, maybe it'll be helpful information. At this point though I'm wondering if I even want to save anything, like will restoring it have Me stuck right back on the same screen? I'm sure I did something wrong because I have none of My old phones app DATA, and I think I thought the Google Backup or OnePlus Switch App was going to put the whole APK on My phone (which I don't want) or the data only, which is what I want. Any help would be appreciated because someone is trying to buy this S10+ but I'm still using it.
First questions: what phone are you trying to fix, s10+ or 7T Pro McLaren?
Second: If you answered 7T Pro McLaren, what mode (recovery, fastboot, etc) can you get into?
I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.
iAMe100XP said:
I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.
Click to expand...
Click to collapse
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).
Hw4ng3r said:
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).
Click to expand...
Click to collapse
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.
iAMe100XP said:
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.
Click to expand...
Click to collapse
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
OK, I will check these things out and report back. I believe I flashed TWRP and the patched Magisk image but maybe I didn't do the original boot image. The problem with the one suggestion is I don't see a 1+ image at all, it just stays on the warning screen forever. I do have advanced boot or whatever turned on I believe where it gives Me more options when holding the power button, provided I can get into the OS but that's not the case. I will try to just hold the volume down when I see the warning screen.
Correction: I see a 1+ logo but no matter what I did, any button combination or booting in with the power button after getting into Safe mode, none of these things did anything but bring Me to the same screen...
Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?
iAMe100XP said:
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?
Click to expand...
Click to collapse
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol
Hw4ng3r said:
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol
Click to expand...
Click to collapse
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.
iAMe100XP said:
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.
Click to expand...
Click to collapse
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.
Hw4ng3r said:
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.
Click to expand...
Click to collapse
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!
iAMe100XP said:
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!
Click to expand...
Click to collapse
It's great that you posted the final result. Not enough people do this IMO.
Sorry some of the suggestions didn't really work out, but at least you could get back into the phone without complete loss of data.
No need for donations; I'm just an enthusiast/ordinary user wanting to help!