[RESOLVED] Problems rooting US Cellular Tab - Galaxy Tab Q&A, Help & Troubleshooting

Hi,Noob here,
I have a SCH-I800 branded for US Cellular. I tried rooting it with SuperOneClick and got "OK" and confirmation from it that my Tab was rooted. I tried Titanium to do a backup and it said my Tab wasn't rooted. I downloaded and tried Root Checker and it said the Tab wasn't rooted but that BusyBox was installed correctly. I rebooted the Tab and now it's looping in bootloader with the US Cell logo only. It loads into recovery and I tried wiping the cache and doing a factory reset, but it's still looping. Now what? I've done some searching but I guess I don't know what to put in the search field as it keeps coming up with no matches.
Help!
UPDATE (4/3/11): I haven't been able to use ADB with the Tab, so I bit the bullet and flashed stock Verizon firmware and that worked like a champ! And, it's rooted as well...not sure why unless SuperOneClick did transfer the files and exploit and it worked. So, I now have a US Cellular Tab running rooted stock VZW firmware. I just followed this guide: http://forum.xda-developers.com/showthread.php?t=967175
And I'm lovin' my Tab again

Not sure whats preventing it from booting.
Does ADB work?
If so maybe you can follow the steps in the manual rooting method & maybe that will fix what superonleclick screwed up.
See this thread http://forum.xda-developers.com/showthread.php?t=859712
Please note I used the su named su-v3

Thanks
I forgot about that in my panic! I'll give that a try and report back.

Update
I was finally able to work on the Tab last night for a few minutes. Tried ADB, as suggested. My PC sees the tab and loads the drivers when I plug in the USB, but I get "device not detected" when I try to do the manual root. I'll try connecting to Kies later today, but it didn't connect to Kies before the crash. Anyone have a link for the stock US Cellular CDMA Tab files?

Update...Got Adb to work by putting the tab into recovery. Now when I try to do the manual root it errors with "file or directory does not exist." If I try to push RATC to just /data, I get "permission denied ". Is there a directory that doesn't need permission that I can push RATC into?
Sent from my DROIDX using XDA Premium App

I used z4root to root my tablet. Working fine. Also installed cwm. No errors or problems.
Sent from my SCH-I800 using XDA App

Related

[Q] 2.2.2 OTA and root, where did I go wrong?

Hey guys, I'm definitely a novice in these matters, but this is the first time I've had a problem so I'd appreciate some help.
While my Droid was on FRG83D I rooted with SuperOneClick using rageagainstthecage. I had to install PdaNet to get it to work, but it did work for me. This morning I got the OTA update for FRG83G and downloaded and installed it just a few minutes ago.
I didn't unroot my phone before I did this.
Afterwards the two apps I use that require su won't work (Barnacle and ROM Manager for backups, I don't have a custom ROM flashed to my phone yet) so I ran SuperOneClick again, ran root using psneuter. Still didn't work so I unrooted using psneuter. Then I realized that I should probably unroot using rageagainstthecage and did so. So at this point (theoretically) my phone was unrooted. Then I ran root with rageagainstthecage again and my two apps still won't work.
Every time I rooted or unrooted using either method SuperOneClick worked seemingly perfectly.
So here's my question: What did I do wrong? And just as importantly, how do I fix it so I can have root access on my phone again?
*Edit* Well this is pretty embarrassing. I just rebooted my phone and tried Barnacle again, and the su acceptance box came up like it's supposed to. I suppose I'm back to being rooted. I think I'll leave this here, and if anyone has any constructive criticism of my (lack of) process or comments about why things acted the way they did and why it works now I'd like to hear it. I'm all about learning more about all of this.

root access?

I purchased att tab one week again, rooted using superoneclick and flashed to overcome 2.3.3 as instructed, everything works out fine.
Soon after I installed Titantium backup root, it showed "not rooted access", and I tried other apps (root explorer, tweeks), same message happens, and z4root superoneclick fail to do the magic this time.
Also, I tried to flash cf-root 2.3.3 JQ1 to root this tab, still no luck.
Just want to know how to root my tab? searched the board, could not find solution, any suggestion is appreciated.
My tab information:
baseband 19000ugjk3
pda: P1000xxjq1
phone: 19000ugjk3
csc: P1000Oxajq1
When you go to the app list do you see Superuser?? If I recall correctly, all you had to do is flash the gb stock safe in odin, and that should have given u all the root you needed.
Yes, I can see superuser in app list, and having no problem opening it.
So how can I do this, restocking GB-safe, can you provide more detailed steps, thanks very very much, I desperately need to unlock this tab.
ok when u open superuser can you click on log and see if superuser is denying your apps or if you maybe unknowingly denied them superuse access? The easiest way I can think of it to redo it again. download the gingerbread stock safe on the overcome website in my sig, backup all and i mean all your apps you care about, texts whatever it is. then download odin 1.7. Follow the overcome guide and you should be fine. Once your done your tab should already have superuser. Download and install the overcome RC1 full and flash that threw recovery.. following the guide again. you should be good to go. Hopefully your titanium backups are on external sd card
thanks, I checked the log, no denying of any applications, I will try to re-flashing once again, and see what happens. The only confusion I am having is that flashing overcome Rom requires a rooted system, since my current system is not completely rooted, is it ok? will this procedure brick my tab?
Again, thanks!
restocking shouldnt brick your tab, just clear your system and start fresh. But if your worried about bricking, make sure you are using a computer that wont just turn off in the middle of the flashing process or kids running around knocking your tab off the connector while flashing. If for some reason odin is not successful, just clear odin and try again without disconecting anything. Hope this helps
restocking ROM, seems everything is ok, thanks again,
But I could not find a version of root explorer working in this version,
it keeps shutting down saying "xx stop working", wired!
busybox
have you tried to re-install busybox?
when you open Ti Backup, click the problems button on the bottom. This will usually prompt you to update busybox. Just yes to whatever it says and wait for the application to restart.
Hit thanks if I helped!
I updated busybox through ti as suggested.
Reinstall root explorer 2.12.4, once opened, granted root access, still no luck, "sorry, the application root explorer (process com.speedsoftware.rootexplorer) has stopped unexpectedly, please try again.
really bothers me right now, any alternative app for the same function?
gtechnical said:
I updated busybox through ti as suggested.
Reinstall root explorer 2.12.4, once opened, granted root access, still no luck, "sorry, the application root explorer (process com.speedsoftware.rootexplorer) has stopped unexpectedly, please try again.
really bothers me right now, any alternative app for the same function?
Click to expand...
Click to collapse
Why not update root explorer from the market? seeing as the latest version is 2.15?
updated to root explorer 2.15, problem solved!
Thanks a lot, guys!

Issues with One-Click?

I just tried running the one click method. I had USB debugging enabled, upgraded to the latest drivers, and ran the exe. Everything said it was successful, I rebooted again, and installed Titanium Backup, and it's telling me it was unable to access root. What gives?
Do you see Superuser on your phone? Doesn't sound like the one click was successful, did you use a Mac? The one click was broken earlier for Macs, seems to work now though.
militant said:
I just tried running the one click method. I had USB debugging enabled, upgraded to the latest drivers, and ran the exe. Everything said it was successful, I rebooted again, and installed Titanium Backup, and it's telling me it was unable to access root. What gives?
Click to expand...
Click to collapse
I would manually type the root method into adb, then use the one click app to automatically push su and stuff to the phone. That seemed to work really well for me.
Sent from my DROID3 using XDA App
Thanks for both of your suggestions. For whatever reason, doing a second reboot on the phone seemed to work. I noticed SU was indeed installed, but TB wasn't finding root. After the 2nd reboot poof TB found root and all is well. Admin can close/lock this thread or I guess keep it open if others happen to have issues with One-Click to consolidate some threads. From what I've been reading one click is damn near bulletproof though.

[Q] SuperOneClick not giving Root

Before I get into it, I'm not sure if this is the best section for this. I posted here because it's a Samsung Captivate I am using and this is a question.
Anyway, I used a video to root my Captivate. I downloaded SuperOneClick, the USB Drivers for Captivate and .NET Framework. Everything went well and it said my phone was rooted successfully. Well, I used Root Check and Term Emulator and both said my phone was, infact, not rooted.
I also have the SuperUser app on my phone. I then proceeded to try again, where I got the error that my Captivate was already rooted. I used psneuter exploit to root. Now, I'm attempted to unroot my phone, where SuperOneClick seems to be frozen at "Waiting for device.."
After I unroot, what should I change or try?
Did you enable USB debugging from your phone? Give me more details on your rom and other stuff.
Also if your on gingerbread the one click root doesn't work on some gingy builds
Sent from my SPH-D700 using XDA App
Download any app from the market that requires root. Try to use it. If it works, your rooted, if not something is wrong.

[Q] Double Rooted!?

I think I have double rooted my Galaxy Tab 8.9 - but my tiny technical mind is thinking they have probably cancelled eachother out... or probably the second root did not work because the first root file was still present? in any case it is not allowing me to remove bloatware / Superuser App appears to be not granted root access so my rootin tootin first dive into tablet hacking has gone awry! Can you help?
I have a UK Galaxy Tab 32Gb 3G (GT-P7300). I tried installing two separate root zip files via the standard recovery mode, my first attempt should have been flashed/installed in CWM recovery (according to a user on XDA) - but wasn't. I then did factory reset, and tried the standard root advice as given on the top of the XDA Developers GT 8.9 thread. In both cases, I assume the root has not worked, because root checker, and more importantly Superuser App does is not gaining root access. Weirdly, an app called Orbot, which usually tells me that my HTC phone is not rooted, does not do the same when I install it on my GTab 8.9.
I have tried backing up to an old back up via KIES, and also a regular factory reset, but neither seem to get me back to square one (i.e the Superuser app is still installed (and not working) in both cases).... any ideas gratefully received!
I'm thinking of using the Factory Reset function from within CWM Recovery....good idea? or will it wipe everyting including the OS?
No root
I've managed to get back to square one, but flashing the unroot.zip from the How to guide, from within CWM recovery. Then factory reset just to be sure. Then followed original instructions on the how to guide, but once I had flashed the root.zip file, it appeared (in CWM Recovery) to have installed ok, but when I go to reboot, it tells me that "root access may have been lost - fix it?" - I say yes, it reboots, and superuser again cannot gain root access....
what am i doing wrong here?
Any help really appreciated...
Hi Folks - I've tried all combinations now and am wondering if:-
The root.zip file contained in the GTab89Files.zip from the How to guide in this forum is out of date... is that possible? or my second guess is that superuser App is out of date...when I open it up, click the "i" information menu, is says su binary v3.1.1 - outdated binary box is ticked, and i then tap to update...everything green or okay, until "Gaining root access.....FAIL" - ( by the way, I have I think given Superuser the admin rights, by selecting Preferences>Auto response>Allow)
I know there is a new version of Superuser v3.1.3 available. Would it help, do you think, to swap out the superuser.apk file in the original root.zip mentioned above? or will I get into a real mess then?
I've searched all over these threads but can't seem to find an answer - any advice appreciated.

Categories

Resources