Upon every reboot, the Galaxy Tab appears to have wiped all data. It prompts me to setup the device. Apps I install are wiped out.
Q. How do I get the device onto Honeycomb Alpha 2?
or
Q. How do I get root on FroYo to get onto Honeycomb Alpha 2.5?
A coworker dumped this device on me. I've been working with Chaos67731, using his instructions to get this Galaxy Tab restored to stock. Here is a video (in 2x and sometime 20x) of that process: http://www.youtube.com/watch?v=5eNLh6wu0ZE. It was on some flavor of Honeycomb, probably a custom ROM, from an outside developer/consultant. From conversations with Chaos67731 it would appear that the recovery on the device is far from stock. After I reboot, the device prompts for setup and flashes "Force close" messages left and right. Chaos67731 mentioned something about "Fix permissions," but I'm not sure where to start with that. Do I need root access?
I attempted to temproot with Visionary+. No dice. (I tried V+ because it's how I temproot my HTC-G2 to run gfree to permroot)
I attempted to root using superoneclick. OS Version Check Failed. Running psneuter... FAILED.
I attempted to root using z4root. "...has stopped unexpectedly. Please try again."
Any and all help would be appreciated! I'm working mostly off adb on OSX at this point. I'm able to hop on Ubuntu 10.04 and WinVista if necessary.
Verizon Galaxy Tab 7-inch
Unsure what version of Android is installed
Hardware version: I800.0.3
Model SCH-I800
Firmware version 2.2 (this sounds discouraging)
Baseband S:I800.0.3V.EB24
Kernel 2.6.32.9 [email protected] #3
Build SCH-I800.DJ11
-- eta June 30, 2011, 3:30pm CT --
It looks like I have root access, but cannot execute root commands. Superuser.apk kicks an "unexpectedly quit" type error.
Use Super One Click. Honeycomb is Android 3.0-3.1 not 2.5. Also the Honeycomb port is still in Alpha and seeing how you don't really know what software version it is I don't know that I would really recommend you switching to it because a lot of stuff doesn't work. It takes some work to move around on it.
alforque said:
Upon every reboot, the Galaxy Tab appears to have wiped all data. It prompts me to setup the device. Apps I install are wiped out.
Q. How do I get the device onto Honeycomb A2?
or
Q. How do I get root on FroYo to get onto Honeycomb A2.5?
A coworker dumped this device on me. I've been working with Chaos67731, using his instructions to get this Galaxy Tab restored to stock. Here is a video (in 2x and sometime 20x) of that process: http://www.youtube.com/watch?v=5eNLh6wu0ZE. It was on some flavor of Honeycomb, probably a custom ROM, from an outside developer/consultant. From conversations with Chaos67731 it would appear that the recovery on the device is far from stock. After I reboot, the device prompts for setup and flashes "Force close" messages left and right. Chaos67731 mentioned something about "Fix permissions," but I'm not sure where to start with that. Do I need root access?
I attempted to temproot with Visionary+. No dice. (I tried V+ because it's how I temproot my HTC-G2 to run gfree to permroot)
I attempted to root using superoneclick. OS Version Check Failed. Running psneuter... FAILED.
I attempted to root using z4root. "...has stopped unexpectedly. Please try again."
Any and all help would be appreciated! I'm working mostly off adb on OSX at this point. I'm able to hop on Ubuntu 10.04 and WinVista if necessary.
Verizon Galaxy Tab 7-inch
Unsure what version of Android is installed
Hardware version: I800.0.3
Model SCH-I800
Firmware version 2.2 (this sounds discouraging)
Baseband S:I800.0.3V.EB24
Kernel 2.6.32.9 [email protected] #3
Build SCH-I800.DJ11
Click to expand...
Click to collapse
it's the verizon tab. so you need to download the samsung sch-i800 drivers, because the tab doesn't install them well, generally. then, run superoneclick, in psneuter mode, with usb debugging enabled. it'll get to a point where it looks like it's hung? it hasn't. leave it be. this takes longer to root for some odd reason. my impatience made me think it was unrootable, but then i had to walk away from the computer during a rooting attempt, and when i came back, it had gotten past the point where it usually 'hung' and was chugging right along. so yeah. be patient. lol.
as far as honeycomb goes, it's only in alpha mode. but once you're rooted, you can flash via the instructions found here: http://forum.xda-developers.com/showpost.php?p=14428575&postcount=718
or, you can run a custom FroYo mod called better than life, which is epic win. find that here: http://forum.xda-developers.com/showthread.php?t=1147277
and if you brick it, you can fix it with instructions found here: http://forum.xda-developers.com/showthread.php?t=1133590
good luck!
Thanks for the tips. I'm 90% there. I'm able to root, but I can't get root access. Perhaps that's for another thread.
i'm not really sure what you mean, that you can't get root access. if you're rooted, then use a root file explorer like root explorer, or es file manager.
New post about my current problem. When I try to run anything as root, I receive an error that Superuser has unexpectedly quit.
Related
Ok this is getting RIDICULOUS.
I have tried multiple rooting methods
Samsung KIES does not work, no fixes work (running on windows 7)
I cannot find DECENT INSTRUCTIONS on how to root ( noob rooting guide method IS NOT working for me,z4root NOT WORKING) The person who had the tab before me "tried" to root it and got superuser stuck on( wont disapear after a reset/uninstall)
I cant reflash becasue there dosnet seem to be a SIMPLE way to do this
I rooted my thunderbolt EASILY doing it in TERMINAL. now I cant root something using a 1 click?
I cannot find a rom to run on this even if i got it rooted
any help?
Im running 2.2.1 ( idiot updated) and my kernel version is 2.6.32.9
Im rather confused there is very little info on these tabs. I thought there would be more...
What problems are you having? Error messages?
A. Nonymous said:
What problems are you having? Error messages?
Click to expand...
Click to collapse
lets see
1.issues with kies
-wont recognize tablet
says use "studio mode" ( dont have that option anywhere i checked trust me)
(stopped saying that recently after fiddling with android sdk?)
-constantly tries to connect in kies, but wont connect
-tried installing all the drivers, no changes
-reinstalled kies multiple times, no changes
2. issues with flashing
-cant use kies so.....
-tried using odin to flash... didn't even touch that, the instructions are REALLY not clear.
3. super one click
-made sure to follow all given directions
- read through the debugging and is shows all the things are getting installed properly
- fails "root checker" app check when checking for root even though one click check said it was done.
I think thats every issue ive had.
EDIT: z4root wont work either, just make smy tablet slow and wont work. i have to reboot to get the speed back
So I just got a refurb tab from AT&T for 200 bucks. It works fine but I want to root it and install some cfw but it is comically locked down. The allow untrusted sources button just isn't there, usb debugging is greyed out, and that Kies software wont recognize the phone no matter what I do.
Also, the 3g is really spotty on it, but that is besides the point.
Any idea what I can do here? I want to install the Overcome rom but it is hard to start if I can't get past steps 1, 2 and 3 due to the nature of my Tab! This will be my first time playing around with rooting an android device fwiw. I own an IDEOS which I use for my phone and that was my first android device a month or so ago.
I got this tab as well and have been able to root and flash Overcome GB without any problems.
For the Kies software, you should download and install it first before plugging it in. Once its installed, you can plug it in and the drivers should be installed. At first, Kies won't recognize it, so you might have to restart your computer for the drivers to work. Once the drivers are installed, you should be able to use SuperOneClick to root then follow the overcome instructions to flash.
How about the bootloader? It says to check if it is locked down but I can run the apk in my tab. Any ideas?
You should root the tab first and use SuperOneClick to do the non-market apps fix. If the root and non-market app fix is successful, reboot your tab and it should allow apps from unknown sources. From there, you should be able to download and run the bootloader checker apk then follow the overcome instructions to flash.
So I got it flashed and set up. Works great. But not my 3g that was kind of off and on just won't work at all!
Fantasysage said:
So I got it flashed and set up. Works great. But not my 3g that was kind of off and on just won't work at all!
Click to expand...
Click to collapse
If you're on the $15/mo prepaid plan you'll need to adjust your APN settings:
http://forum.xda-developers.com/showthread.php?t=1083173
Just got my verizon galaxy tab 7 today, did a bunch of reading to find the best way to root my tab but nothing works. Cant use superoneclick because its cannot connect properly to kies. The newest version of z4root crashes into force close. From what ive read it has something to do with a eco2 update which ive confirmed my tablet has on it. Its currently running 2.2 android, any suggestion how to root this bugger ??
I have a Verizon tablet as well, and I used Superoneclick (PSneuter option) without bothering with Kies. It worked just fine for me. Just make sure that you have the proper drivers installed ahead of time. In my case, my tab came with drivers, and they were sufficient. To access them, plug in the tablet (make sure debugging is off) and you should be prompted with an autoplay by windows. Alternatively, Oldmacnut has a thread going in the development area for a 2.3.4 rom for the Verizon tablet that he released, and which comes rooted.
Seamus1 said:
I have a Verizon tablet as well, and I used Superoneclick (PSneuter option) without bothering with Kies. It worked just fine for me. Just make sure that you have the proper drivers installed ahead of time. In my case, my tab came with drivers, and they were sufficient. To access them, plug in the tablet (make sure debugging is off) and you should be prompted with an autoplay by windows. Alternatively, Oldmacnut has a thread going in the development area for a 2.3.4 rom for the Verizon tablet that he released, and which comes rooted.
Click to expand...
Click to collapse
Before i read your reply i was able to get it rooted with the newest version of superoneclick 2.1.1 and the drivers installed by kies. Even though kies doesnt show a successful connection it still works. Sorry to waste bandwidth ! thanks for the reply though Seamus !
Hey thats great I have the same problem with rooting my Tab VZW I will try the new version of superoneclick 2.1.1
Thx
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
Don't know what the above means
Does 2.3.1 work without modification?
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!
sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?
envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.
Pete has a stock rooted FRK76 Rom on his website, fyi
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.
I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.
Is there a RUU i can run to unroot my phone?
YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one
YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.