Hi all, i just recently rooted my i9000m (baseband version I9000UGJL2) with psneuter on superoneclick, easy stuff, i came from a desire z so in comparison the root process was much easier, anyways i
went to rom manager, flashed CWM, reboot into recovery, and voila, stock 3e recovery, no reinstall packages option, and apply update.zip not working. What's wrong?
nevermind, searched it on forums, used CFroot
Had the exact same problem, you will need to do this in order to make it work. If you dont have it already download Root Explorer from the Market to apply this fix.
http://forum.xda-developers.com/showthread.php?t=909213
Related
i was looking and serching for a fix my nexus s , i update from Alpha 13 to ICS 4.0.3 and i lost ither root or SU permicion can someone guime to right way i nedd get to CWM and go to my backups and i can do the rest i try update SU buth i not able to get CWM i just get stock recovery i try update SU from app not root acdsse .
I would think that you need to flash your recovery again. fastboot your recovery .img then flash rom manager after you reboot and you should be ok. do this the same way you did when you originally rooted your phone.
You may need to unlock bootloader, root and install. Official stock ROM erased them all.
I unlocked then rooted my nexus 7 8GB. Mainly to access external storage. This I achieved and with stickmount was able to achieve the objective, reading from a usb stick.
I felt at the time that there was something wrong as installed app Titanium backup pro - but could never find it. though google still tells me it is installed.
Rom manager states I have ClockworkMod 6.0.1.0 & that 6.0.2.3 is available BUT after dowloading "Flash ClockworkMod Recovery" an error occures.
I installed root checker pro. It advises that not rooted properly although busybox is installed correctly. Reports attached
I have both superuser installed at original root. Since also installed Super su, neither will install binary code.
Is there anything I can do to ensure I am rooted and stay that way?
Thanks for any help offered.
Easiest thing to do boot into recovery, make a backup always,do a wipe flash a custom ROM plenty out there
You may have lost your root, so try to reroot. As for keeping root, DL Voodoo OTA RootKepper from the Play Store. Works like a charm.
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'm having problems with rooting my S4 i9505.
I've rooted it before, but I installed a new stock rom, so I needed to root the new rom too.
I installed custom recovery via ODIN, and that worked fine.
Then I booted into the recovery, and selected SuperSU.zip or whatever it's named, installed that.
When the ROM boots up, it gives SuperSU has stopped working error, and when I update superSU via google play, it gives me error that binaries are not installed.
So what am I doing wrong, and what should I do to root the phone?
braien334 said:
Hello, I'm having problems with rooting my S4 i9505.
I've rooted it before, but I installed a new stock rom, so I needed to root the new rom too.
I installed custom recovery via ODIN, and that worked fine.
Then I booted into the recovery, and selected SuperSU.zip or whatever it's named, installed that.
When the ROM boots up, it gives SuperSU has stopped working error, and when I update superSU via google play, it gives me error that binaries are not installed.
So what am I doing wrong, and what should I do to root the phone?
Click to expand...
Click to collapse
If your phone doesn't rooted yet , use the towelroot application it's should root your phone right
You can find an option in the recovery to root your phone. Atleast in Philz there is that option. After that install supersu from the playstore.
I flashed Chainfire-auto root with odin, that worked.
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
dberthia said:
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
Click to expand...
Click to collapse
I've asked this very question in Chainfires main SuperSU XDA thread. Hopefully we can get some clarity.
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
velis74 said:
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
Click to expand...
Click to collapse
Interesting but I wonder what state your boot.img is in. I downloaded and examined the SuperSU v2.35 update flash file. I did not see anything to indicate that it backs out whatever non-stock boot.img changes were introduced. There was a "clean-up" comment which was intriguing.
As my tablet works well I'll wait for a while to see if I get any definitive response to my post. If not I'll likely use fastboot to re-install the stock boot.img and TWRP (which is already installed on my N10) to flash SuperSU v2.35 file.
Glad to read your tablet is in good shape.
I updated Binary via twrp and get fcs for all Google apps. Tried to clear Cache of everything, also wiped it: nothing changes. Going to reflash lollipop