I had my Fire rooted at 6.2.1 with twrp. Last night it installed the OTA 6.2.2 on its own. Which I didnt think was possible but it happened. Anyway Ive been able to reroot with burritoroot2. But I havent been able to get twrp back. Ive tried the KFU, and manual installs but havent been able to. Has anyone else been able to get twrp back after the forced 6.2.2? And if so what did you do? Ive been working on this for hours and hours, reading threads and posts, trying different methods and nothing has worked. Any help would be appreciated. Thanks
Try to Do it manually via adb. Good thing I deleted Otacerts.zip So now im on 6.2.1 and I dont have to worry about the Update.
The craziest thing just happened. I was trying to install the new CWM based recovery that was just posted here. http://forum.xda-developers.com/showthread.php?t=1454241
And I was able to get further in the installing through adb process. SO I decided to give twrp a last chance. I went to install it and it worked. But when I rebooted it wasnt twrp it was the CWM based recovery. So Im not sure how it installed the other, but I now have CWM on my fire and am running a full backup now.
just for others who have problems with kfu on 6.2.2:
http://forum.xda-developers.com/showpost.php?p=21575038&postcount=622
or if you want to edit the run.bat:
http://forum.xda-developers.com/showpost.php?p=21575038&postcount=730
Related
Hey guys, so I've got my 0089_US tablet rooted currently and protected with RootKeeper, but I don't currently have CWM. If I do the OTA ICS upgrade, will I still be able to install CWM at a later date provided I still have root?
No CWM after ICS update
I'm also interested to hear if anyone has been able to install CWM after ICS update.
I followed the process to keep root and restore stock recovery and managed to get ICS with root successfully (big improvement over HC). But now I have no CWM recovery and I'm not too sure about reinstalling as I've read others have experienced boot loop issues when they tried.
Has anyone successfully installed CWM after ICS update?
word is no, CWR is not ready for ICS yet but i hear root worked. I am having issues getting back to stock recovery to install in the first place. guess i'm waiting for a modified CWR flashable update.zip
seamonkey420, look forward to positive results. really want to CWM at ICS
I have a Razr M -- if there is a better place to ask this, please don't hesitate to let me know. I am new to this, but trying to learn.
I had the phone rooted and the bootloader unlocked, 4.1.2. I haven't accepted the OTA, but as you'll see below it's a pain because I've lost root and can't freeze the updater. The phone is still unlocked, and TWRP is still installed, but no root.
I had a problem with Safestrap where it would not create new ROM slots. I fixed it with a data format and factory reset. I was able to reroot with Motochopper, and then used Titanium to restore my apps. I must have restored something that the system didn't like, because I got stuck in a bootloop.
I then factory reset again, to start over. Only now Motochopper doesn't root.
I get a success message from Motochopper, Superuser does appear on the phone, but I also get the lines:
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory
Superuser itself says that the binary needs to be updated, but none of the install options (install, recovery install) work. I tried Voodoo OTA Rootkeeper, since I had a protected SU installed, and it didn't work either.
Since I had Safestrap installed, I thought I might be able to get CMOD to a custom ROM slot even if the stock had lost root. I went ahead and created a custom ROM slot and tried to flash the Razr M CMOD 10.1 and gapps to it. I got a success message, but when I boot I just get a blackscreen; I've waited it out for 20 minutes or so, and nothing loads.
I have the Razr 1.20 utility, but frankly I am afraid to use it to try to go back to stock 4.1.2. I don't know what the OTAs have done, and frankly everything I have loaded to the M has bombed, and if I mess with my (now screwed up) stock install, I don't know that I'll be able to recover. But using the 1.20 utility and flashing 4.1.2 is my last idea.
Any help or thoughts? Why the hell did Motochopper stop working? What does this line about busybox mean? Can it be fixed short of trying to go back to stock 4.1.2?
Any help would be deeply appreciated. Because I lost root (and Titanium) I can't freeze the updater any more, which means it's now a matter of postponing every 12 hours. Not my favorite thing. And because my bootloader is unlocked I really hesitate to accept the OTA.
Since you have TWRP installed, get rid of Safestrap, you don't need it. If you're unlocked you can use Utility1.20 with no issues. If, somehow you did install the OTA, and you still have TWRP, then you just need to flash a SU zip in recovery to retain root. However, I think your best bet right now to get everything back to normal is to use the utility.
Sent from my Droid RAZR M using xda app-developers app
Many thanks. A few questions.
First, I may have misspoken, apologies -- the terminology is new to me. Safestrap has a version of TWRP, and that is what I mean when I say that I have TWRP installed. I don't have it separately installed. Does that change your advice?
Second, can I flash a zip of SU from Safestrap? Would I navigate to the Titanium Backup .zip and use the install function of Safestrap?
I deeply appreciate the advice. I may indeed have to go back to stock with the 1.20 utility, as you note.
Safestrap isn't a version of TWRP. It's based off of TWRP, but it's designed to work with a locked bootloader. Honestly, I would just use the utility and flash back to stock, re-root, and then install TWRP.
If you don't want to do this, your next step needs to be flashing TWRP, deleting and uninstalling SS, and flashing SU. You shouldn't be able to flash SU in SS. If you want to take the OTA, then you need to install an aftermarket recovery, first, so you can flash SU.
Sent from my Droid RAZR M using xda app-developers app
Hello. I have GALAXY S5 - SM-G900F Lollipop. I wanted to root it and i used Kingo. It said that root was successful i even had superSU app, but i couldn't open it and when i installed app that i know needs root access i didn't get prompted to allow it. So after some checking i concluded that root was not successful and wanted to revert it with kingo again. It said that S5 was not rooted and i couldn't root it again (was getting failed this time).
Then i wanted to do factory reset to 4.4.2 via mobile but each time i would select that option phone would just freeze. I booted into recovery TWRP that i installed previously and did hard wipe. After that i was without ROM, and installed lollipop using this tutorial (/watch?v=r_ifFnj9tbo). Everything was fine but i lost TWRP and was with stock recovery.
I wanted to root phone again using different method (/watch?v=iBNGeppOzGI) but when i installed TWRP via odin (i got success and phone rebooted as last time i installed it) and tried to boot into TWRP using button combinations phone would just load standard recovery instead. I also tried to install CWM, same results. Success message, phone reboots and it still loads stock recovery so i'm stuck now. Anyone has any idea how to install TWRP now?
Anyone got any idea, don't know what to do here. Any help appreciated.
Could you paragraph your post please, it hurts my brain trying to read it like that
*Detection* said:
Could you paragraph your post please, it hurts my brain trying to read it like that
Click to expand...
Click to collapse
Just for you any ideas to why i can't get into twrp or cwm?
Anyone?
Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.
laoki said:
Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.
Click to expand...
Click to collapse
CN? Or US!?
dieselman6969 said:
CN? Or US!?
Click to expand...
Click to collapse
Thank you for your reply, it is CN version.
I was able to root the phone again, by doing fastboot commands manually.
flash recovery, flash misc
After that, I was able to enter recovery mode.
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.