I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. After applying "Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
diggerb said:
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. "After applying Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
Click to expand...
Click to collapse
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Sent from my SAMSUNG-SGH-I747 using xda premium
nakedninja42 said:
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Click to expand...
Click to collapse
Thank you for your reply.
I updated to the latest version in Play Store, it shows Binary v2.3.1-ef , update check shows latest version 3.1.1 but when I click Update, it fails on the step "Gaining root access..."
Cheers
diggerB
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Tyxerakias said:
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the feedback... but I just went back into CWM and applied the root again, still in exactly the same boat.
Thanks to all, I found a solution in another thread: http://forum.xda-developers.com/showthread.php?p=31179418#post31179418
Superuser just didn't want to work. The SuperSU root method referred by the OP in that thread worked great. All is well again. Until next time of course.
Hi, if you go to "www.galaxytabhacks.com" you will find the solution, there is an upgrade to superuser.
Related
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!
Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......
I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714
oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk
Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.
aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.
You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App
I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.
Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk
Running ROM Manager Premium v4.7.0.5 with ClockworkMod 3.0.0.8 (newer versions did not flash ROMs properly) on Cyanogenmod 7.1 with SuperUser 3.0.6 (su binary 3.0.2).
When I try to run Fix Permissions from ROM Manager, it asks me to confirm as normal. When I confirm, it just sits there in the Fix Permissions window where the log output would usually appear. I've let it go for several minutes and nothing ever seems to show up. It should be noted that ROM Manager never requests root permissions for this either.
Am I not waiting long enough, or has anyone seen this issue before?
Edit: I also posted this to reddit under Android (can't link because I don't have enough posts).
Are you running the latest su? I had an issue with the latest version and had to uninstall updates to get it to work, once I did that it let me flash the latest CWM and fix permissions
Sent from my ADR6300 using XDA App
I was running the latest version of Superuser and su. I uninstalled updates to Superuser, but that only brings it down to 3.0.4, and the same problem results.
Edit: It would appear this is deeper than just ROM manager, and that SuperUser is the culprit. I just tried updating the su binary, and it's stuck at "Gaining root access." Always exciting when Superuser can't give itself root rights...
This is affecting everything requiring root permissions. The programs just hang because the root prompt never shows up. Not really sure what would've caused this. Must be an su/Superuser update. I can't flash from ROM manager because Superuser is broken. Is there any place to install an older Superuser APK?
Did you downgrade in the market? That just put me back to version 2.3.6.3 which shouldn't give you problems, and I'm pretty sure there's a way to install it with adb but I'm not sure how, you could always install a new ROM with CWM.
Sent from my ADR6300 using XDA App
I also just noticed your binary is outdated... Try updating that and c if it fixes anything, the latest version of su with the latest binary are actually working for me but, the previous version didn't .
Sent from my ADR6300 using XDA App
The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
http://rootzwiki.com/topic/194-superuser-2363-17-june-2011/
gadzooks64 said:
The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
Click to expand...
Click to collapse
That fixed it, thanks. Now running Superuser 3.0.6/su 2.3.5.3 and things requiring root permission are actually asking for them again.
Why not just "Fix Permissions" straight through the recovery?
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.
Did you run the busybox free app?
Sent from my Nexus 7 using xda premium
Metallice said:
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.
Click to expand...
Click to collapse
I installed busybox installer and when I try to install/update it says it failed. As for SuperSu, it doesn't give me an option to update the su binary.
ScipioWarrior said:
Did you run the busybox free app?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I ran busybox free and it says it's unable to verify whether or not certain utilities needed for this app to run are present and functional on my device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured
njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2
Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.
animatechnica said:
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I installed the update after rooting.
jonnyg1097 said:
Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.
Click to expand...
Click to collapse
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.
njswift10141980 said:
Yes, I installed the update after rooting.
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.
Click to expand...
Click to collapse
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.
neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
I feel like a moron especially since I froze the updater on my droid x, I'll give it a try when I get home from work, is there anything special I should do or will I just have to click the root button?
demandarin said:
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.
Click to expand...
Click to collapse
I will have to look at this app.
I will report back later.
Just rerooted and it looks like everything is working, thanks everybody
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
I can't yet because of root. I need access to my computer.
crystalstylez said:
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
Click to expand...
Click to collapse
Installed it...
I got it also. 16gb u.s. Wifi version. it was installing & updating android apps as I left out for work.
Any changelog on what was changed or added?
I want to install it but will a root method be made for it. I am not near a computer to use the zedomax root method. Anyone had root while installing this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Downloading it now. Will install shortly.
Sent from my GT-N8013 using XDA Premium HD app
Edit:
Installed, must have wiped cache as all apps went through the updating process. No noticeable differences or problems. Seems to be a tick faster but that's probably just my perception.
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
californiarailroader said:
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
Click to expand...
Click to collapse
I hope one of the fixes is making bookmarks appear quicker in the stock browser.
cmunho said:
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Click to expand...
Click to collapse
I wonder exactly which bugs. I hope that folder & keyboard bug got fixed. the one where they open by themselves when going to homescreen from certain apps or whatever. it was getting irritating having to constantly close them. Lol
Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
OK, as expected, lost root. Odin flashed the original cwm recovery back. reinstalled the original root file and and back to being rooted.
Still 4.0.4.
All you had to do was use voodoo ota rootkeeper to backup n restore root file. access to computer not needed.
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
vanillanesquik said:
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
Click to expand...
Click to collapse
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
mitchellvii said:
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
Click to expand...
Click to collapse
I used OTA rootkeeper as specified above. If that does not restore root I can re-do the Odin. Thanks
Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
ye i just did it and i lost root but the first thing i noticed that is working faster. also the snote app was update you can upload your own template finally. when choosiing a background on the window pop up touch the little square image on the top right corner and it lets you choose from images in your gallery.
tmaurice said:
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
Click to expand...
Click to collapse
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
californiarailroader said:
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Click to expand...
Click to collapse
Thanks - I saw that link a couple of days ago, but didn't use it because it's the N8000 and we've got the 8013 here in the States.
My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?
SirLoinOfBeef said:
My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?
Click to expand...
Click to collapse
Flash CF-Root with Odin and you`re rooted. Link http://forum.xda-developers.com/showthread.php?t=2219803, read the OP well and it will be easy.
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No, it will only root it, you will not loose any data. After that flash a custom recovery if you need it and Busybox from Google Play,
SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There won't be any changes but root will be extra it won't wipe anything and u need not factory reset also
.
I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s
SirLoinOfBeef said:
I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s
Click to expand...
Click to collapse
Close all apps, reboot and try again to update the binaries. Have you checked for an update of the SU app in Google Play?
There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted
SirLoinOfBeef said:
There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted
Click to expand...
Click to collapse
Open the SU app and unroot and try rooting again by flashing CF-Root. Do you have usb debugging enabled on the phone in developer options?
I have debugging enabled.
I tried re-rooting, and now have no SU app at all
Very confused. This should be a simple process.