Related
To make things easier here is a link to BRD's update to 3.1 I suggest you check it out for an easy upgrade to 3.1.
http://forum.xda-developers.com/showthread.php?t=1074609
If you are already on 3.1 just flash the stock HRI66 system image and Tiamats boot image to get sd card support back from there you should be able to run BRDs update from the SD card in clockwork
I did this using CWR on a rooted Xoom
1. Copy the update to your sdcard and name it update.zip
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
4. Then back to fastboot and flash the root31.img to your boot partion (link below)
5. Then reboot your xoom and push su using koush's original root instructions and you are rooted running 3.1
6. You can then use rom manager to reflash CWR.
Link to post with root31.img
http://forum.xda-developers.com/showthread.php?t=1073298
Other files easily found on xda
Just have to wait for an updated kernel to has sdcard support back.
All credit goes to the people that did the actual work I'm just listing instructions. And of course you assume all risk in flashing and modding your device.
Sent from my Xoom using my Xoom
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
dch921 said:
6. You can then use rom manager to reflash CWR.
Click to expand...
Click to collapse
Just use fastboot. That's what it's there for.
JFMFT said:
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Haven't tried it but worse case scenario just reflash root31.img
Sent from my Xoom using my Xoom
Nice! It worked perfectly!
I tried flashing Tiamat 1.4.1, wouldn't recommend it, you'll have to go right back to stock.
I am doing this right now on my XOOM. I will update this post when I am done.
Thank you for the instructions
EDIT: works perfectly!!
Got confused at first and followed the whole guide to originally root...but then realized that you do not flash rootboot.img.
Only do the following code:
1. adb remount
2. adb push su /system/bin
3. adb shell
4. ln –s /system/bin/su /system/xbin/su
5. chmod 4755 /system/bin/su
6. exit
7. adb push Superuser.apk /system/app
Click to expand...
Click to collapse
props worked great
Cansay that this worked great. I love the update and I love keeping my root. The device is running smoothly with the stock 3.1. Good post indeed.
Sent from my Xoom using Tapatalk
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
Click to expand...
Click to collapse
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
This instruction is very unclear...
Blades said:
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
Click to expand...
Click to collapse
Of course not. You can have a ramdisk with ro.secure 0 and the stock kernel, or you can use any kernel you like that will run.
(IMO, it's better to root with as small a change as needed, and if you want to use a different kernel, you can do so if you want separate to the decision of wanting root)
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
Again, just use fastboot (because it's unlocked), then reboot into recovery. Does that not work?
ljwnow said:
This instruction is very unclear...
Click to expand...
Click to collapse
No its pretty simple you must not know what your doing
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
after you flashing boot.img and HRI66 system.img, type this in cmd, fastboot reboot
xoom will reboot to normal mode, then wait untill it completly settle to home screen, it will take sometime (it seems like bootloop but it does not, HC doing re-dalvik cache, so it takes time)..after it boot to normal mode type this in cmd, adb reboot recovery
you will reboot to cwm recovery (i'm guessing you have flash cmw before on 3.0.1) then follow the OP steps..
i'm on 3.1 now.. with no data loose and rooted ;-)
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
wsuo2006 said:
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
Click to expand...
Click to collapse
No sdcard support until we get a new kernel
Sent from my Xoom using my Xoom
I was wondering if anyone could package the stock 3.0.1 kernel and system.img into an update.zip so this can all be done using rom manager? Thinking about it most likely not cause moto has been pulling system dump images
Sent from my Xoom using XDA Premium App
dch921, would it be possible for you to please add the relevant links to your OP instead of saying to search XDA for them? If you do this, I will gladly sticky this guide.
Thanks!
I rooted my phone at 4.0.2, then applied the update up to 4.0.4 and am still able to flash new versions of clockwork mod through rom manager... However, all my other apps won't be granted root access. In the superuser application, I'm running superuser v3.0.7(41) and my Su binary is at v3.0.3, for which there is an update available. However, when I try to apply the update, it tries to ask for root privileges and gets denied access... I tried reflashing su.zip through clockwork mod touch but I guess I may be flashing an outdated su.zip? Any insight into the matter would be greatly appreciated!
Same here
Same exact scenario, I went from 4.0.2 to 4.0.4, and even after a factory restore I cant seem to get root access for any app. I checked the bootloader, and I still am rooted.
Help appreciated for us both!
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
ezcats said:
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
Click to expand...
Click to collapse
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Clockwork recovery does not require root if it is already installed. If not, fastboot clockwork recovery.
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
evanextreme said:
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Click to expand...
Click to collapse
Flash from recovery, not an app.....
Sent from my Galaxy Nexus using xda premium
jerseyh22accord said:
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
Click to expand...
Click to collapse
This did the trick!
Had this same problem earlier
I need help
I am having the same problem. I am a noob and it sucks cause I can't figure it out. I can't even go into recovery since I installed 4.0.4 someone please dumb it down so i can understand
Install busybox free, then install titanium backup free. Open busybox and click inatall. Then run
Titanium backup, it will ask you do you want it to configure root, accept this. please note After completing busybox steps reboot. Then after titanium backup steps reboot again
Did this help?
If not pm me and il see if i can help
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
brightsideme said:
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Try flashing this:
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
brightsideme said:
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Do you have CWM installed yet?
If not...
I'd recommend simply starting from the top and using my guide.
But if you have CWM:
Just navigate to "Install Zip From SD Card"
"Choose Zip"
And find it.
Yes to install.
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
brightsideme said:
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
boot to clockworkmod manually, than flash the superuser zip from here http://www.box.com/s/jvcf196j7x8f8vrc9cyt (this does not require busybox, that why the other su zip was failing)
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
brightsideme said:
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Jubakuba said:
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Click to expand...
Click to collapse
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
andQlimax said:
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
Click to expand...
Click to collapse
nope, he was getting a permissions error because rom manager didn't have root access, that was the issue there.
edit: re-read the post, yes, you might be right about busybox in stock recovery, although i believe cwm has a set of minimal busybox tools.
if manually booting into recovery by shutting down the phone, pressing power+vol up until Google screen appears, doesn't take him to cwm but to stock recovery, he doesn't even have cwm installed, which could very well be the case, since stock rom default behaviour overrides any existing recovery when flashing.
I ODIN the tar to get the OUDHS Custom Recovery, which is fine, but it didn't put the su binary, and thats why my superuser app is unable to provide the root access.
is there a separate zip file which let me just flash the su binay?
byteless said:
I ODIN the tar to get the OUDHS Custom Recovery, which is fine, but it didn't put the su binary, and thats why my superuser app is unable to provide the root access.
is there a separate zip file which let me just flash the su binay?
Click to expand...
Click to collapse
Search "supersu XDA" in Google and flash that zip
Sent from my SGH-M919 using Tapatalk 2
My phone is a Huawei u8160 (AKA Vodafone 858) and I rooted it a long time ago with z4root and have had no problems eversince.... until recently when my mate got hold of my phone and accidently flashed an experimental/beta (possibly a binary for x86 systems) SU binary through CWM recovery. I thought I could fix this quite easily by using z4root to uninstall root and then do a fresh reinstall, but it would force close on me after a few seconds. I tried this method with both temporary and permanent root options but nothing worked. The button that pops up saying ''unroot'' wasn't there even though there is still a SU file in /system/xbin as it showed in Rom toolbox. I soon realised that the version of android i was running on my custom rom was not compatible with z4root, so i searched for how to root android version 2.3.9 pro. I dont know the name for that version and it must have been a bit of a flop because google didnt know it either. I dont know how akiro-E (the developer that cooked up the rom) got his hands on version 2.3.9 pro but i recommend to other devs reading this to not use it as there is not much compatibility.
Anyway, i found this apk made by chainsDD called gingerbreak and decided to give it a go. It said that it needed debugging on and that it might take a while, so i did that and pressed the root button. I left it to do its business, but 15 minutes later it was still trying to run the exploit so I stopped and removed it. When i got home later on i searched up how to root any phone and it came up with the pc program 'superoneclick'. I got it, opened it and clicked unroot. It did its thing but failed to remove su and the superuser app like it was meant to. So then i clicked on root and shell root but it did not reinstall properly and got the same error as in unroot error. I did all the steps multiple times but it still wouldnt remove/replace su from the xbin folder. I then reinstalled superuser 3.1.3 and tried using the binary updater on there. I noticed that the su installed was called 'legacy'. The updater was having a spaz and didnt want to update so i tried manually removing su with the root explorer in rom toolbox butvrealised that you needed root (a working one) to do that. Then i found an app on my sd called root cleaner. I tried quick and full cleaning but to no results except for a force close multiple times. I tried to fi the foce close issue by running the script for this in rom toolbox but you need root (surprise surprise) Then i tried flashing cwm recovery through fastboot as i have done lots of succesful times before. It flashed after putting my phone in download/debug mode (power and volume down) but i cant boot to it as you need proper root rights to do that.
I am going to use total commander to check if the permissions are set to 644 for the su binary, if not ill attempt to change them.
I know this a long desciption and technical question but does anyone know any ways to delete the retarded root from my phone and help me restore root as normal? This is a question for the more experienced users and devs on this forum but any help will be appreciated, cheers.
If you've got recovery, you can install one of these zips in recovery mode.
Google "superuser 3.1.3 arm signed zip" and click the first link that comes up - the androidsu one. Then download the superuser zip package that suits your device to your phones internal storage, reboot into recovery, install the zip and there you go! Your root is fixed.
Sent from my LG-E400 using xda app-developers app
Thanks
@odigITECH thanks for the help. I fixed the problem using your method. . . kind of. I flashed recovery via fastboot and then just flashed another rom from my sd card via cwm after I rebooted. Thanks for the help anyway, much appreciated!
No probs
Sent from my LG-E400 using xda app-developers app
I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I have to restart and try it again 5-6 times anyone know why im losing root
laniclamoore said:
I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I
have to restart and try it again 5-6 times anyone know why im losing root
Click to expand...
Click to collapse
Please reply if need more info let me know what ya need im realy hoping for some suggestions
I had this happened to me a while ago it actually ended up either being an app or an xposed module. Do you use xposed?
I had this problem with Cyanogen mod 11 and running exposed framework.
I switched ROMs and now I have no problems.
losing root
I don't use xposed im just using the root66 stock 4.3 rom I have tried different super user apps no help. Im currently using superSU 2.0 (not the one from market) so far its no longer losing root. I uninstalled the superSU app from the market and used the one I found on a different thread in the Q&A forum. thanks for asking about it I will post if it stops working or anything else goes skiddy wumpus.
Thanks guys.
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Philosuffer said:
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Click to expand...
Click to collapse
Yes I agree I set the SU request during boot to grant superSU root access so the superSU app would protect SU binary from being deleted during boot.
well crap
Crap im once again losing root on restart/boot I've tried using different root methods to no avail. Could it be the SE for Android still says enforcing maybe my bootloader is locked but I don't know how to check if it is. I have not tried custom roms because I don't know which ones work for the t999l lte.
All of the roms are safe to try. They work fine for most people, but if you have problems you can always flash back to what you have now. (Don't forget to make a nandroid backup).
And the bootloader is not locked btw.
Might also help to flash your stock firmware Via Odin. Have you tried the root66 firmware?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
su binary present in xbin but on reboot not executing
Ok im still having the same problem.
I have the su binary installed in the /system/xbin folder but when rebooting from recovery su binary is not detected by superSU but its still in the xbin folder.
This jpeg is when I have full root access is the setuid not present a problem? See errors on second jpeg.
I don't know what info is needed to find problem will someone tell me what info I should gather to help solve problem with su binary (like logcat/busybox version,) thanks
Did you try v1.94 or 2.00? I guess 2.13 didn't solve the problem.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
thread closed use thread "keep losing root access"
There are 2 threads on the same issue. Please use Keep losing root access.