Temproot for Desire Z/G2 help needed - G2 and Desire Z General

I can use a computer to temproot my Gingerbread 2.34 G2/Desire Z
I run this batch file and to Re Root, (root fades off after a while) I run the lines in RED and it works again as rooted.
adb wait-for-device
adb push ./fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo -debug -start Fb990000 -end FFFFFFFF
adb wait-for-device
adb remount
adb shell
adb shell exit
cls
adb shell chmod 755 /data/local/tmp/fixsu.sh
adb shell /data/local/tmp/fixsu.sh
Exit
Is there anyone who knows of a local application that would act like adb but DOES NOT NEED THE PHONE TO BE HOOKED UP TO A COMPUTER ? If not, is there anyone who could get something written that would do the red commands on the phone without having to use adb and a computer? (When I use Connect Bot or Terminal Emulator, I get access denied, but the same commands via ADB succeeds... I don't know why.) That'd really make the TempRoot very usable when the user is on the road, and away from a computer. I really think the super smart android afficionados in our forum would easily be able to cobble something that we all could use, Like Visionary... Thank you for reading this, and thank you even more if you can tell us how to do it on the phone, or even writing a one button job that accomplishes this.
Aloha from Hawaii !

fre3vo is an adb exploit, thats why it only works in abd.
one thing you could try is, after running fixsu.sh for the first time through adb, open a terminal session, gain root access in it (type 'su') and then leave that in the background until you need to run fixsu.sh again.
-Nipqer

Can I just ask why you want to have temp root over perm root? Nothing wrong with it but maybe there are other solutions out there

Related

Where to find an Ubuntu guide to root and remove stock apps on the Hero?

If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.
Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.
Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.
romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.
Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.
back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic
Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices

Automated ADB script

Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!
94kram01 said:
Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!
Click to expand...
Click to collapse
adb shell su -c ls
Thanks! It seems to work, but somehow it just did not ask for permission on the phone, so returns 'Permission denied.' I checked phone, but it didn't ask me if I want to enable or not.
Try
Code:
adb shell su -c "ls" -root
Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?
94kram01 said:
Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?
Click to expand...
Click to collapse
I'd think if u call it with -root it should only ask once.
Not sure though.
If it asks more than once, could you push a script to the device (somewhere that normally has full r/w access), run it with a single command, then delete it?

ADB required?

After looking at the rooting steps outlined here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
I was wondering if there was any reason you couldn't do the ADB steps in the terminal? Just place all the files on the sdcard and cp them to the proper directory from there. Taking ADB out of the steps would defnately make the process easier for people.
Is there something I am missing? Would this work?
Rooting the G2 and MT4G
Download:
gfree_temp-root.zip
gfree_04.zip
Unzip the contents of the above files, and place them them on the sdcard as follows:
/sdcard/ (root directory):
su
Superuser.apk
gfree
/sdcard/root/
rage
busybox
root
In Terminal make the following commands::
cd /sdcard/
cp -r /root/ /data/local/tmp/
chmod 0755 /data/local/tmp/*
/data/local/tmp/rage
After a minute or so, you will see the following message on the phone Forked #### childs. Press the Menu button & select Reset Term. The Terminal Emulator will exit out.
Launch Terminal Emulator. It will force close. Launch it a second time, and you'll have a root shell. You are now temp-rooted.
In Terminal make the following commands:
cp gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
/data/local/tmp/root
NOTE: You may see an error that states mkdir: /system/xbin already exists, if you do, simply ignore and continue on.
sync
Reboot. You are now perma-rooted, have radio S-OFF, and SIM-unlocked.
I perm rooted my first G2 without adb. There are specific guides for doing it without adb. Although if you do have the SDK and ADB, its very very easy lol.
Lol i didnt use adb. I use visionary and terminal
Sent from my HTC Vision using XDA App
I didn't use ADB either. Just a few simple commands in terminal.
http://forum.xda-developers.com/showthread.php?t=928160
Thanks, however.....
I have been reading that there have been issues with using Visionary to temp root. I just wanted to validate that it was OK to use terminal for the ADB steps.
Thanks!
~Jeff

[HOWTO]: Rooting the Huawei S7 Android 2.2.2 stock

Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might, like mine, just blink on and off for a while trying to flash what it thinks it finds is already flashed but what just gives an error!
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests done in that post on which rom work best for which model.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils im used to in the world of *nix was missing from the 2.2.2 image kindly provided by Huawei ( The Norwegian Telenor image i might add that the camera on a model 101 will not work with!) so i found an easier way! push push push!
Here's what i did, for convenience ill try making it a script, but be prepared to copy these commands manually instead! For windows simply remove the ./ and add .exe .
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adb binary that comes with SOC is a simpler route if your just in for a quick root fix. Simply rename the appropriate adb for your system and use this method.
The simplest thing to do i guess is to copy Exploits/psneuter or gingerbreak to the ADB folder (in SuperOneClick's folder) and go on from there, also copy su-v3 (rename it to su) and Superuser.apk from "Root/" to the folder (ADB), or if you choose to, rewrite this "script" with the appropriate paths. Im unsure if the following script will work in every case, so you might want to do it manually, but most should get the drift, if you are not comfortable with this procedure you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your USB mode to "Developer" mode
AND BE ROOT ON YOUR MACHINE!
Code:
#/bin/bash
echo "The BackAsswardsRootScript!\n\n"
echo "Lets start the adb server.\n\n"
./adb kill-server
./adb start-server
echo "Pushing the exploit psneuter onto the device.\n\n"
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter"
./adb push busybox /data/local/tmp/busybox
./adb shell "chmod 4755 /data/local/tmp/busybox"
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "We should be root now, making sure.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
./adb shell " /data/local/tmp/busybox mount -o rw,remount /system"
echo "Pushing the system files in place\n"
./adb shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/bin/busybox"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox"
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only, just for kicks!
echo "Remounting the filesystem as Read-Only\n\n"
./adb shell "busybox mount -o ro,remount -t /system"
echo "You should now be rooted my friend.\n Enjoy!\n"
Please help feed my Linux addiction! Go to http://threader.zapto.org and click Donate!
Rooting S7 using Gingerbreak
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Cool, theres a gingerbreak exploit in the superoneclick package also, i tried that after i though psneuter didnt work, just a matter of replacing psneuter with gingerbreak. Did you use this method though or did you find some other way?
I didn't change or replace anything. My terminal skills are not on a level to have the guts anyway.
I simply updated from S7V100R001C43B010 to S7v100R001C98B021.
Then ran the Gingerbreak 1.2 exploit.
Interesting, yeah the gingerbreak exploit will work, when i wrote the fist post i used the gingerbreak exploit instead of the psneuter one thinking psneuter didnt work, turns out it did though and i went back to that one as its designed for 2.2.2, didnt know of this wrapper though, thanks!
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
threader said:
./adb shell "chmod 0755 /data/local/tmp/psneuter
Click to expand...
Click to collapse
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
threader said:
Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might like mine just blink on and off for a while trying to flash what it finds is already flashed but what just gives an error. !
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests there on which roms work best for which models also.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils was missing from the 2.2.2 image kindly provided by Huawei (Norwegian Telenor image, that i might add, the camera on a model 101 will not work with!) soo i found an easier way! push push push!
Heres what i did, for convenience ill try making it a script, but im making it as i type this post so this is untested as a script(!) Be prepared to copy these commands instead!
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adblinux binary that comes with SOC will work just as well, simply rename it to adb and use this method. The simplest thing to do i guess is copy Exploits/psneuter to the ADB folder (in SuperOneClick's folder) and go from there, also copy su-v3 (and rename it to su) and Superuser.apk from Root to the folder (ADB), or rewrite this "script"/collection of commands i used" with the appropriate paths. Im unsure if the following script will work as is as i said, so you might want to do it manually, but most should get the drift, if not you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your usb mode to Developer mode
BE ROOT!
#/bin/bash
echo "The backasswardsrootscript!\n\n"
echo "Lets start the adb\n\n"
./adb kill-server
./adb start-server
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "Should say we are already root now.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
# This really should be /dev/block/mmcblk0p1, i have no idea why this works.
./adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p1 /system"
# Now instead of copying using cp or moving with mv, considering "cp" was missing
# and mv just didnt work for some reason...! I found just pushing the files straight to the
# system after remounting worked just fine
echo "Pushing the system files in place\n"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
./adb push busybox /system/bin/busybox
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only just for kicks!
echo "Remounting the filesystem as Read-Only\n"
./adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p1 /system"
echo "You should be rooted my friend\n Enjoy!\n BE SURE TO DONATE TO SUPERONECLICK!!!"
# One of the main strangenesses i found was the block device was logically enough placed on
# partioton 1, of block1 which really should have been block 0 part 1, but that doesnt work.
# So it boils down to that this shouldnt work but does for no apparent reason(!).
# even /etc/mtab says that mmcblk0p1 is mounted to a non existent /mnt/dcard
# as an EXT4 partition which isnt supposed to be supported until 2.3.x
Click to expand...
Click to collapse
Dear S7 users,I am using the ideos s7 by Teltra supllier and i did unlock sim by norwegian rom.I read a lot of document but i didnt find out an easy way to run clockwork that i can run cook rom,can u help me how to run it in easy way.Thanks and appreciate that.
http://www.androidtablets.net/forum...wegian-2-2-2-s7v100r001c57b111.html#post82863
PuZZleDucK said:
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
Click to expand...
Click to collapse
Great! Thanks! Ops, yeah missed that, fixed now, thank you for pointing that out. I haven't spent much more time on this. the pad has pretty much been untouched since i moved house. I would like to make this easier for less technical inclined here but its just a matter of replacing ./adb with adb.exe if your on windows. Besides, i don't want to be at fault for bricking someone. And maybe i could write some simple application for installing Gnu/Linux as well, ( http://forum.xda-developers.com/showthread.php?t=1109730 ) but that will have to wait until someone bribes me or hits me over the head i guess.
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..
---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------
Maniacnl said:
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Click to expand...
Click to collapse
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..

how do i root now that i have gingerbread?

I have a Verizon tab that was rooted. I updated to gingerbread which removed root. Is there a way to root now that I have gingerbread?
Thanks!
you may try SuperOneClick 2.2 with ZergRush...
Thanks. I'll give it a shot.
Soundchasr said:
Thanks. I'll give it a shot.
Click to expand...
Click to collapse
Did it work?
Haven't had a chance yet.
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
receptr said:
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Telling me, I have gingerbread on mine and it does nothing but forceclose crap all over the place
Lakilaulea said:
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Click to expand...
Click to collapse
I was able to get mine rooted by using the kernel from Galaxy Cubed 3 ROM. Downloaded the whole ROM and flashed only the kernel in heimdall. Then I used adb to push the correct files to the system and fixed permissions and rebooted. Worked great.
UPDATE:
If people want to know the adb commands I used, here they are:
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
You can copy and paste these commands to a bat file and run it in a command prompt window. These were taken from a script used to root devices.
Here are links for the files you need. They are:
su
superuser.apk
busybox
They need to be placed in the same directory that you run the adb commands from.
SECOND UPDATE:
Rather than go through all this, go here:
http://forum.xda-developers.com/showthread.php?p=19678785
This is dsb9938's plain stock EI04 VZW ROM that is pre-rooted. Just flash in Heimdall and you are good to go. As long as you only wipe cache and dalvik, all your apps should stay intact.
Gingerbreak.apk should do the trick. Worked on my P1010
chris_toshiba said:
Gingerbreak.apk should do the trick. Worked on my P1010
Click to expand...
Click to collapse
It did not work on my VZW Tab. Someone said it is because it only works on 2.3.3 and older gingerbread and we have 2.3.5.
BTW, look at my earlier post (second update) to get a really easy way to have rooted stock 2.3.5 VZW Tab.

Categories

Resources