My device was fine and rooted until 4.3 dropped and just like when 4.2 dropped I lost root access.
I downloaded the Nexus Root Toolkit and ran through the Root process. There were a couple of times where the on screen messages weren't going forward such as push files to device, etc. but when I rebooted the device it seemed to be ok and it went into TWRP.
After it went into TWRP it said Rooting but nothing happened. I hit reboot, system, then it asked if I wanted to root. I swiped for yes.
I rebooted my device and started Super SU. It says my device isn't rooted.
Can anyone assist me with this. I'm almost thinking this isn't worth it if I have to jump through hoops every time there is an update.
Thanks.
Nevermind I fixed it. I had to install SuperSU 1.5 manually in recovery in order to get it to work.
Will tht work on my razor hd maxx xt926..same issuie had root.then over the air ota update 4.3 took my root accsess..tried reroot several ways..no luck.got it to install a diff su app..but when reboot..says su not installed .everytime I reboot the symbal # pops up says update binary .try to says same .su not installed..plz tell me step by step how u went in recovery to manually install.how reboot in recovery?.then update from playstore?.or flash again?and re root?
Sent from my SCH-I545 using xda app-developers app
http://techglimpse.com/steps-root-custom-rom-android-nexus/
Related
Hi,
I had rooted my N7 with the Wug's toolkit back when i received it. I did not select CWM at that time (i was crazy).
Since rooted people cannot apply the OTA 4.1.2 update, I have been trying various methods to get into recovery (a common problem with rooted devices).
Nothing seemed to work so I decided to re-run the process of root from the toolkit. during the process, whenever the toolkit rebooted to bootloader, my device would just stay on the fastboot menu. the toolkit showed as if it was pushing the binaries etc and doing its thing, and then rebooted the device back to normal (i had opted the CWM this time to right my wrongs).
After the process, when i checked for Super User, it failed to install updates. Upon checking with 'root checker', it said this device is not properly rooted.
I can boot into CWM recovery now but is doesn't allow me to install the update manually.
Another weird thing is that although i'm still on 4.1.1 JRO03D, the system update prompts have gone and on manually check for updates in settings, it says that my system is up to date!
Please help!
This is the WRONG section.....again....
I had the same problem, you should flash the old bootloader with a toolkit, search for a guide...
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
GatorsUF said:
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
To enable ADB to go:
Settings-> About Tablet-> Click Build Number for Easter Egg Multiple times! BOOM!
I am not sure if there's a way of rooting without PC and custom recovery.
I got a Google Nexus 4 about a month ago. Somebody told me I should root my phone so I installed the Nexus toolkit and did all of that. I proceeded to install a buncha stuff on it like Call Master, Titanium backup, etc.
But then I kept getting notifications saying there was an update to Android 4.2.2 so I updated it thinking maybe it wouldn't cause a problem. But now none of my programs work, and when I open up SuperSU it says:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
how can I fix this?
htothez said:
I got a Google Nexus 4 about a month ago. Somebody told me I should root my phone so I installed the Nexus toolkit and did all of that. I proceeded to install a buncha stuff on it like Call Master, Titanium backup, etc.
But then I kept getting notifications saying there was an update to Android 4.2.2 so I updated it thinking maybe it wouldn't cause a problem. But now none of my programs work, and when I open up SuperSU it says:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
how can I fix this?
Click to expand...
Click to collapse
Do you have a custom recovery? You'll have to flash the SuperSU zip again so it can install the binaries.
http://forum.xda-developers.com/showthread.php?t=1538053
Alot of times u lose root when u install an OTA. You will need to reroot your phone
CMNein said:
Do you have a custom recovery? You'll have to flash the SuperSU zip again so it can install the binaries.
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
What's a custom recovery exactly? I'm a complete noob to this stuff.
And how do I flash the SuperSU zip again?
Just download the toolkit from WuFresh and in it they have an for Nexus 4 on 4.2.2 proceed to root again since your bootloader should be already unlocked (when the phone boots you see under Google a lock that has been unlocked) once it's rooted again, you'll be clear, I would suggest making a fresh Nandroid after you rooted having the new OTA.
Sent from my Nexus 4 using xda app-developers app
Sparta507 said:
Just download the toolkit from WuFresh and in it they have an for Nexus 4 on 4.2.2 proceed to root again since your bootloader should be already unlocked (when the phone boots you see under Google a lock that has been unlocked) once it's rooted again, you'll be clear, I would suggest making a fresh Nandroid after you rooted having the new OTA.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i might try this.
So basically I gotta re-root my phone again? If I do that am I gonna lose everything?
No only unlocking the bootloader will erase your data
Sent from my Nexus 4 using Tapatalk 2
Get OTA Root Keeper from the Play Store and back up. Then whenever there is an OTA update, you just restore the back up and you will have root again.
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
Hi
I have Android 5.1.1 running with root on my Nexus 4 (using Nexus Root tool kit)
So there's a stock recovery installed.
There's Superuser installed.
There's an update waiting to be installed and I would like to keep the root or be able to root without losing data.
My phone has bootloader unlocked. And SU app installed.
Cheers
Sent from my Nexus 4 using Tapatalk
I don't remember if you need to be unrooted or not, but you can just try to see if it works rooted first. If it doesn't you can unroot your phone by going to settings in the SuperSU app. To reroot after that just flash the SuperSU zip.
EDIT: You can get the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
Hi again
So I tried to apply the OTA update and it restarted and started to install the update and it gave me an error in the midway with a red exclamation () mark in the androids stomach.
So I pressed power + Vol up button and restarted my phone using the menu.
I thought it was probably because of the root. So I went to SUPER SU app and Uninstalled it (un rooted). Restarted and SUPERSU was gone.
After a while the update came back. And I applied it again. And this time the same error.
So I pressed power + Vol up again and checked the log and it says that /cache/update.zip has unexpected contents.
Anyone got any idea why is this happening?
This time I've formatted cache. And so far (5 mins) no update Notification yet.
Looking forward to your help.
Cheers
Sent from my Nexus 4 using Tapatalk
You can't have an amended /system partition to use the OTA with 5.0+. Even uninstalling SU will not work. If you want to use the OTA Process, you will need to flash the factory /system image, which will cause you to lose root (and is sort of redundant in light of the fact you can just extract the updated system.img file from the latest Factory Image and just flash that to upgrade to it). That said, it only takes a minute to root so would suggest just making sure you are comfortable with the process as opposed to trying to preserve root.
Thanks.
Sent from my Nexus 4 using Tapatalk