Hi,
I have rooted G2 802 International version, with stock ROM V30B.
Now I try to install TWRP there.
Tried multiple image versions, including from TWRP download site,
last one from here http://techerrata.com/file/twrp2/g2d802/openrecovery-twrp-2.8.5.0-d802.zip
Installed through adb shell,
Code:
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
When I try to enter recovery mode I get a brief "Critical Error" message (in text mode), then promp to choose whether to reboot or enter download mode. No TWRP.
Any ideas ?
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
AutoRec, you had one job...
PolishVodka said:
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
Click to expand...
Click to collapse
AutoRec seems not to work. I installed the VS980 version for the Verizon variant of the phone, but all the app has is a picture of lollipops. Tapping the one at the bottom restores my (corrupted) backup, while tapping the one at the top does absolutely nothing. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Hi, I tried to install TWRP using Autorec. But my phone stuck on fastboot mode. although the phone said it is d802 varient after I remove the back it says ls 980. I can run fstboot commands but not adb. Itried 5 different computers with win7/8/10. No good results. worse case is, no download mode at all. So I can not flash the phone. I tried to flash TWRP using fastboot but nothing changed. Can some one please help me
Related
Hi all,
I have put myself/phone in an interesting situation, which I am hoping the community can help me with.
I recently bought an LG G2, dold with stock 4.4.2. I proceeded to root it, and tried installing custom recovery.
I first installed ROM manager, which didnt work.
I then tried flashing twrp through adb using loki, which gave me a 'this is not a loki file' error.
I eventually realized that they had closed the Loki loophole in stock 4.4.2.
At this point, trying to enter recovery wouls give me a 'secure booting failed' error, making me have to reboot the phone again.
I then unrooted my phone, and factory reset it. I realized Clockworkmod recovery (which ROM manager installed) persisted despite the data wipe, so I unchecked that option in ROM manager and wiped it again.
My thinking was that I vould now downgrade to 4.2.2, install custom recovery there, then flash 4.4.2 whitout losing root or recovery.
Problem: I can't do any of this, because I can't reroot my phone with ioroot25. It fails as when it reboots inti recovery it gives me the 'secure booting failed' error.
Thanks for any help. I simply want to root my phone and if possible, have a functional recovery in order for me to flash some mods. At least being able to have it rooted again would be sweet.
Hehh...
Last thing you can do is try to flash with LG Flash Tools Method or LG Support Tool
Flash stock recovery either via fastboot / or dd(on linux). Then you can proceed further.
Or ^ kdz via download mode.
I have a similar problem. I restored the stock recovery via adb using a dd command. Then I unrooted in order to accept the latest OTA. The OTA fails with a "suspected root" error. Download mode still has "ROOTED" in red letters. At this point I gave up on the OTA and wanted to get back to where I was.
IOROOT25 doesn't work because when the phone reboots to recovery mode, I get the broken android with the red triangle but nothing else on the screen at all. There are no options, nothing. Eventually it reboots. I've done a factory reset to no avail. Recovery seems corrupted.
I need instructions for flashing the stock recovery with no root.
I managed to get my recovery rewritten using the LG Mobile Support Tool on a different computer. Then I was able to root again using ioroot25. I'm not sure why I couldn't run on my own laptop, but it's fixed now.
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...
I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.
Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)
remove battery after install recovery before restarting phone
Hey everyone I just recently got a Moto X Pure with TWRP recovery already installed and the bootloader unlocked, unrooted. The phone was stuck on Marshmallow so I went to update and it would take me to TWRP recovery every time and when I reboot back into the system, I'm still stuck on Marshmallow. So I downloaded an app that would make me download OTA updates while still having TWRP recovery but it needed root access, which I didn't have. I tried all of the one-click root apps but non worked then I stumbled across an easy root method: ( oops it said I can't post links, but basically I downloaded a supersu zip and flashed it) which I followed very precisely and I'm pretty sure I did nothing wrong. But when I flashed the ZIP using TWRP and booted back into system it was stuck on the Motorola logo which I'm assuming is bootloop. I was going to download a stock recovery using fastboot but I discovered that it would relock the bootloader, which would render the device useless to me so I can't. I also tried wiping the Dalvrik Cache but it always failed. I'm new to all of this so please guys I'm desperate for help. Thanks in advance
You can flash with fastboot the newest stock(the same version or upper) without commands "...oem..." at start and the end.
Or
The newest downloadable without commands "..oem, bootloader, gpt, oem...". @Philo0o
BL will be still unlocked.
Do you have a tutorial on how to do that please?
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 @Philo0o
More accurately you need to flash boot.img which is the kernel , in the case where root was being installed using systemless mode.
Otherwise, if you tried an old SuperSU version (where systemless didn't existed or the ones that failed to detect to install using systemless method on this phone) you'll need to reflash the whole system partition (using Firmware system chunks or custom ROM zip file).
Having issues install the September OTA update for my Moto XT1644 that is currently running on Systemless Magisk v14.0 and Xposed v88.2.
I set Magisk into core-only mode, so Xposed is disabled. I did had TWRP on the phone before but flash over it with fastboot with the stock recovery.img.
Whenever I tried to installed the OTA update, it errors out in the install.
-Do I need to uninstall Xposed framework?
-I am currently on the ElementalX Kernel. Do I need the stock kernel?
-I do have a custom boot logo image and also for the boot loader if that matters.
-The stock recovery I got only displays "no commands" with the Android Robot when it boots up. This definitely does not look like stock recovery to me.
Thanks for taking a look and trying to help me.
Issue have already been solved!!!!!
Finally decided to try this, https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and it worked. Just skip the "fastboot erase userdata". Lost root though.
shineburst said:
Finally decided to try this, https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and it worked. Just skip the "fastboot erase userdata". Lost root though.
Click to expand...
Click to collapse
Similar issue like here again https://forum.xda-developers.com/moto-g4-plus/help/moto-g-boots-twrp-t3701768
shineburst said:
Having issues install the September OTA update for my Moto XT1644 that is currently running on Systemless Magisk v14.0 and Xposed v88.2.
I set Magisk into core-only mode, so Xposed is disabled. I did had TWRP on the phone before but flash over it with fastboot with the stock recovery.img.
Whenever I tried to installed the OTA update, it errors out in the install.
-Do I need to uninstall Xposed framework?
-I am currently on the ElementalX Kernel. Do I need the stock kernel?
-I do have a custom boot logo image and also for the boot loader if that matters.
-The stock recovery I got only displays "no commands" with the Android Robot when it boots up. This definitely does not look like stock recovery to me.
Thanks for taking a look and trying to help me.
Click to expand...
Click to collapse
I'm just answering your questions, nothing else.
You need to have a STOCK boot image, and a STOCK recovery. I'm fairly certain Xposed can also cause issues. The safest thing you can do when you've heavily modified your system is to flash your stock ROM and wiping everything but your internal storage in your device.
Yes, the “no command” is the standard stock recovery itself. You need to hold the power button, and either the upper or lower volume key at the same time (I don't recall which one, think it's the bottom), and let go of the volume key you're pressing to view the recovery menu that you are familiar with.
You obviously will lose root access when you flash a ROM via fastboot because you're wiping almost every common partition with new data, replacing all the previous data (root access is in the /boot partition) with the files from the fastboot image(s).
I tried flashing TWRP to my device as I unlock the bootloader. But every time I reboot to recovery it does some funky stuff. How do I get TWRP to work m?
You unlocked the bootloader - right?
If so, get the latest TWRP for your device (that happens to be 3.3.1 HLTE), and flash it using the AP section of Odin. Either that, or from your rooted OS (your os is rooted, right?) you can flash it using the official TWRP app.