Database Develop

[RESOLVED] Problems rooting US Cellular Tab

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

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.

Phone keeps failing to root on step 3

Error : We are root but unable to push SU... It does this every time then recommends unrooting and trying again..
Any thoughts?

im having the same problem. it gives me a build prop error and states how it hopes i dont have a version that has the exploit fixed.

Fixed it by using my Mac... PC wasnt playing nice.

it happened to me too. as long as you see SU app there your rooted should be fine

[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] Kindle Fire 2. Generation = Kindle Fire HD?

Hi,
I recently got a 2. Generation Kindle Fire and would like to turn it into an ICS Android Tablet. However, I am not quite sure where to look for a suitable tutorial / whether I could possibly run into troubles when rooting my Kindle and using a clean version of Android instead.
I am posting in here because I do not have access to the Kindle 2 development forum and there is no Q&A Board for my particular device.
So, I'm not totally unexperienced in regards to computers and stuff, but completely new to tablets and regarding operating systems.
I did read this and this, but people kept running into technical problems. On one hand, the boot screen would always have to remain or some particular apps won't probably or on the other hand the kindle would keep updating itself to prevent the foreign os from working probably - or not not working at all.
I would like to just spend one afternoon reconfiguring my kindle 2 (not HD) and then not run into technical issues every few weeks. Is that even possible or is the developement regarding my advice not advanced enough, yet?
Sorry for the inconvenience; I read some general advice on rooting beforehand, but can't quite figure out whether it also applies to my particular device or not. (For example, will Kindle 7 HD stuff also work with my device?)
Thanks in advance!

I used the first link provided to root and install play store.
Once play store was installed I bought kindlefree for 1.99 which allowed me to install a custom launcher and remove ads from the lock screen.
AFAIK we cannot use anything from the HD 7"... but I just got this device today and haven't a clue yet.
Once I have more of a clue... watch out!!
Edit: using custom launcher is not quite perfect.. some apps don't notify my unless I start them (Google+).
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
I used the first link provided to root and install play store.
Once play store was installed I bought kindlefree for 1.99 which allowed me to install a custom launcher and remove ads from the lock screen.
AFAIK we cannot use anything from the HD 7"... but I just got this device today and haven't a clue yet.
Once I have more of a clue... watch out!!
Edit: using custom launcher is not quite perfect.. some apps don't notify my unless I start them (Google+).
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
pretty much correct.

I ran into an issue...
I tried the first method as suggested, but when I try to run "runme.bat" from Qemu, it hangs at "* daemon started successfully *"
I downloaded the ADB drivers from the link. When those failed to install properly (repeatedly, giving me the exact same issue as linked above), I uninstalled, downloaded the Android SDK, got the proper files for the KF2, made sure I killed the ADB process before I started, I ran cmd as admin, I basically followed every instruction from the original post to the letter. I'm working with a KF2 (not HD) running 10.2.4. Any ideas? Suggestions?
Thanks so much!

mgierhart said:
I tried the first method as suggested, but when I try to run "runme.bat" from Qemu, it hangs at "* daemon started successfully *"
I downloaded the ADB drivers from the link. When those failed to install properly (repeatedly, giving me the exact same issue as linked above), I uninstalled, downloaded the Android SDK, got the proper files for the KF2, made sure I killed the ADB process before I started, I ran cmd as admin, I basically followed every instruction from the original post to the letter. I'm working with a KF2 (not HD) running 10.2.4. Any ideas? Suggestions?
Thanks so much!
Click to expand...
Click to collapse
You will have to install the drivers manually through the device manager on windows.
Sent from my KFOT using Tapatalk 2

That worked!
mindmajick said:
You will have to install the drivers manually through the device manager on windows.
Click to expand...
Click to collapse
That did it. My fault--I assumed that, when I installed through the Android SDK, it had taken care of installing the drivers as necessary.
Thanks!

mgierhart said:
That did it. My fault--I assumed that, when I installed through the Android SDK, it had taken care of installing the drivers as necessary.
Thanks!
Click to expand...
Click to collapse
Lol. 99.999999% of the time that would be correct. If i hadn't had the same issue i wouldn't have known how to fix it. Mine kept picking up the adb drivers for my samsung phone. Needless to say- that didn't work
Sent from my KFOT using Tapatalk 2