Problem: GingerBreak simply sits and churns forever trying to exploit and root my tablet but never succeeds, I have left it running for almost an hour once.
My notes
1. I started with a stock install of 3.0 on the tablet and rooted with GingerBreak no problem.
2. I tossed the recently leaked 3.1 update.zip onto my SDCard and flashed using the stock methods.
3. Checked if root was maintained through the update, and it was not.
4. Double checked that USB Debugging is enabled, even disabled and re-enabled to make sure.
5. I have a clean SDCard in the tablet and mounted with no issues.
6. I have removed and reinstalled GingerBreak to try and see if that would clear things up.
I have seen a few other posts on threads that people have had no issues using GingerBreak on 3.1 but for the life of me I cannot get it to successfuly root my device.
If it comes down to it, I will just return to stock and go about it another way. But, I thought I would inquire if anyone had any suggestions for the current situation.
Are you tried iconiaroot-1.0.apk special for HC3.1 ?
look for it in developement section
Ah, thankyou for pointing out that thread. This has allowed me to root on 3.1 stock.
Related
I've noticed a few pre-Froyo changes that seem to have appeared suddenly with no warning:
1. Report button when an app force closes
2. No longer have root with Paul's superboot as Root Explorer and Quickboot don't work. Re-running the Superboot reinstates root.
3. Phone seems quite a bit smoother
Has anyone found any other changes? Also, can you say which ROMs you've had. According to something I read on the official Nexus One forums, rooted phones stay on the update white-list.
I'm on the stock EPE76 (via Paul O'Brian) previously with Paul's superboot root.
nexus5894 said:
I've noticed a few pre-Froyo changes that seem to have appeared suddenly with no warning:
1. Report button when an app force closes
2. No longer have root with Paul's superboot as Root Explorer and Quickboot don't work. Re-running the Superboot reinstates root.
3. Phone seems quite a bit smoother
Has anyone found any other changes? Also, can you say which ROMs you've had. According to something I read on the official Nexus One forums, rooted phones stay on the update white-list.
I'm on the stock EPE76 (via Paul O'Brian) previously with Paul's superboot root.
Click to expand...
Click to collapse
There's a whole other thread right below this one talking about this. Why start a new thread?
A
Arghh- must have missed it. Someone close this please
Seemingly simple question among all the confusion I have...
I have a stock (un-rooted) Dinc w/ the ota installed. Have recently had phone locking up (freezing) problems since the ota install.
I want to remove the ota and restore the firmware back to stock.
1. How?
2. Is the PB31IMG.zip process just for those who have rooted their phones or would that work for me also?
Edit later: I transferred the PB31IMG.zip file to my SD card and followed the update procedure. Got a message after loading the file...then checking it...."main version is older, update failed".
Not sure where I go from here w/out some imput.
http://forum.xda-developers.com/showthread.php?t=727263&highlight=ruu
This works I have done it myself many times, you will have to root first but after your phone will be back completely stock. I use the PB31IMG.zip method instead of using a RUU like in the post.
Thank you MachString. That was my problem....it never occurred to me that I need to root my phone first, then unroot back to my original firmware.
Hey guys, need some help. I've searched around and tried to do different things but I'm afraid that I might be stuck (due to my limited knowledge of working with androids).
So I rooted my Fascinate and installed ROM manager and clockwork recovery onto it. Well, after fiddling around with it for a few weeks, I feel like I’ve gotten my self into a position where I’ve lost the way back. So now, I’ve tried unrooting using a couple of methods (update.zip and one click unroot) but it fails every time. This led me to believe that root/super user was not gone from my system (Super User icon/app is still there). This morning, I installed Titanium Back up and it said it couldn’t start because my phone is not rooted. I go into the Super User app and no app has requested it. I’m just kinda lost at this point and want my phone back to the state when I had first purchased it.
Now I know there is the Odin way, however, his post says that his files include superuser and busybox already installed – this I don’t want. I want the unrooted factory Samsung Fascinate state back. I was thinking about using the “factory reset” option in the settings but wanted to get your opinion on this before proceeding (since several posts said to do it where as others said don’t do this way).
Can someone help this clueless android n00b? Please?
If you do a factory reset superuser will still be installed.
When I did Oden restore i think I had to re-root my phone.
You could also root your pone again, then un-root to remove superuser.
Why do you care? My wife and I both have gotten replacements because of hardware defects. Both phones were rooted and they never questioned it either time.
This thread contains ODIN files for a completely stock device:
http://forum.xda-developers.com/showthread.php?t=782204
No root/bb/su.
NKT said:
This thread contains ODIN files for a completely stock device:
No root/bb/su.
Click to expand...
Click to collapse
Actually, the system file in that thread does have SU/Superuser.apk/Busybox, but otherwise it's stock.
atrich0608 said:
You could also root your pone again, then un-root to remove superuser.
Click to expand...
Click to collapse
This did the trick!!
I used the the z4root app from appbrain, rooted and unrooted. SU = Gone!! Amazing!
Thank you!!
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
Find the APK file for Z4 root and give it a go that way or Superoneclick has always worked for me. Just make sure you have the latest drivers from Motorolla for your phone and PC OS. It's far easier then rageagainstthecage.
Thanks, some of the things I've tried... Z4 all 3 editions, they dont hang and run through as if there sucessful, but when the X reboots and i try running an app like root explorer. It says phone not rooted. Super1click gets stuck in a loop and using adb devices, shows device connected but offline. Rebooting phone is the only way out. I Just can't see what im missing here, other than I should have unrooted b4 the OTA update.
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
There's been a coupe threads already started with your issue..I think there's one on the 3rd page called can't reroot after the ota update...find it and follow the directions..
Sent from my DROIDX
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
DasNas said:
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
Click to expand...
Click to collapse
That's good..Enjoy
Sent from my DROIDX
I have a problem as I am now in circle of problems.
I need to have a rooted Android to install a clockwork mod.
But I need to have clockwork mod installed so I can install a b518 bootloader
But as clockwork mod installation needs root, I can not install anything.
I have now Official 2.3.5 b526 and I can not download b518 because terrible sharing sites (torrents anyone?), it toke 6 hours to even get the b526 with my nice 10Mibts connection so I don't want to spend next 12 hours trying to get a older version with multiple interrupts and re-downloads with capped speeds.
I have now browsed almost three hours XDA forums about this problem. No one can say directly how to solve thing.
I can return to 2.2 version fine but I don't want. I can root 2.2 fine and install CWM.
With 2.3 I can not root. Not with Z4root, SuperOneClick, Superuser, Superbootloader or any other way. All those say that I have rooted phone and even CWM manager things I have rooted phone but everytime root permissions are needed, everything fails just to errors that permissions are not possible to gain.
I have rooted, unrooted b526 and b136 versions multiple times but never got working root.
So question is very simple.
How to actually get Official 2.3 rooted?
Did you enable logging? That may be the cause: http://forum.xda-developers.com/showthread.php?t=1420728
Blefish said:
Did you enable logging? That may be the cause: http://forum.xda-developers.com/showthread.php?t=1420728
Click to expand...
Click to collapse
Enabled:
Loggin
USB Debug
Mock locations
Allow all sources
And didn't mount MicroSD or NAND while rooting
Oh and tried even what someone said that they needed to disable WiFi so I even enabled it and disabled it.