I need to wipe the dalvik-cache through adb. could someone tell me the command for this. I can't find the command in the search.
i updated my recovery image (google how to update recovery when still rooted [the unlockr method]) and it cured the problem instantlu.
blue carebear
I will look into that, thanks.
bernard_photography said:
I will look into that, thanks.
Click to expand...
Click to collapse
Here's a guide on how to update recovery. Download updated recovery of your choice (RA, Clockworkmod, etc.) and name it recovery.img. Put it on the root of your sdcard. Now, when booted into normal Android, run this:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done!
bernard_photography said:
I need to wipe the dalvik-cache through adb. could someone tell me the command for this. I can't find the command in the search.
Click to expand...
Click to collapse
The command to issue within the adb shell would be
Code:
rm -r /data/dalvik-cache/*
Thank you! That is exactly what I needed.
buck2202 said:
The command to issue within the adb shell would be
Code:
rm -r /data/dalvik-cache/*
Click to expand...
Click to collapse
I found you were missing a letter. Should be: rm -rf /data/dalvik-cache/*
you left off the "f" in "-rf".
bernard_photography said:
I found you were missing a letter. Should be: rm -rf /data/dalvik-cache/*
you left off the "f" in "-rf".
Click to expand...
Click to collapse
The f isn't necessary.
Related
sorry but how do i get to adb shell from the command propt??
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
wadeheisen said:
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
Click to expand...
Click to collapse
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
xxxk15 said:
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
Click to expand...
Click to collapse
What are you trying yo do? What rom are you running? Are you rooted? Need more info please.
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
Click to expand...
Click to collapse
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
Click to expand...
Click to collapse
Go to a command promt. In other words go to start and search for this
Cmd
Then type commands mentioned above
The easiest way is to just hold down SHIFT and then right click on blank space, and then select Open Command Window Here. Also, I'd HIGHLY recommend adding ADB to your PATH.
well i am running 2.09.1 DC and i am rooted. when i download apps it tells me "Insufficient Storage Available" I have enough internal memory so i searched that and one person said they fixed it by
cd /data/data
rm -rf info.lamatricexiste.network
So i wanted to try it but i am really confussed on how about going to do this
xxxk15 said:
well i am running 2.09.1 DC and i am rooted. when i download apps it tells me "Insufficient Storage Available" I have enough internal memory so i searched that and one person said they fixed it by
cd /data/data
rm -rf info.lamatricexiste.network
So i wanted to try it but i am really confussed on how about going to do this
Click to expand...
Click to collapse
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click Start
1. Click RUN
2. type CMD in the box press enter
3. In the command prompt type
Code:
cd C:\AndroidSDK\Tools
this is just a guess and where most people have it. It MAY be different for you.
4. Type
Code:
adb remount
adb shell
5. You should see a "#"
6. Now type
Code:
cd /data/data
rm -rf info.lamatricexiste.network
Kcarpenter said:
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click Start
1. Click RUN
2. type CMD in the box press enter
3. In the command prompt type
Code:
cd C:\AndroidSDK\Tools
this is just a guess and where most people have it. It MAY be different for you.
4. Type
Code:
adb remount
adb shell
5. You should see a "#"
6. Now type
Code:
cd /data/data
rm -rf info.lamatricexiste.network
Click to expand...
Click to collapse
ok i understand but my command propt comes up with stuff in it
C:\Documents and Settings\Admin>
How do i get rid of this??
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click
Click to expand...
Click to collapse
ok i understand but my command propt comes up with stuff in it
C:\Documents and Settings\Admin>
How do i get rid of this??
Click to expand...
Click to collapse
Nothing just type the commands that were given and UT will take u to the right directory
Papa Smurf151 said:
Nothing just type the commands that were given and UT will take u to the right directory
Click to expand...
Click to collapse
o ok thanks it worked!!
Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts
fenwaynomar45 said:
Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts
Click to expand...
Click to collapse
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).
I have the tools directory open as im doing the command... i didnt have this problem last time i did this... so idk whats wrong
corrosivefrost said:
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).
Click to expand...
Click to collapse
And isn't the correct version Recovery-RA-eris-v1.6.2?
I downloaded it and thats the recovery image im using but it saves as recovery when i zip it
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse
Here are the steps I have used over and over, so try this. And I used this link for the recovery, so maybe download this one and give these commands and recovery a shot.
Download Link: http://www.sendspace.com/file/jje5xr
Extract file contents to your \tools\ directory of your Android SDK
Open up a command prompt and go to your tools directory, and execute these commands: (MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THESE COMMANDS WON'T WORK! MAKE SURE IT IS ON "CHARGE ONLY")
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
Type dir recovery-ra-eris.img in your c:\AndroidSDK\tools directory. If it comes back with nothing, then you actually put the file somewhere else (don't worry, happens to me from time to time).
fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse
whats with everybody elses free version of rom manager not flashing the alternate recovery? im still a huge fan of ease of use personally. and its always worked im too scared to flash using it but i always flash the recovery when they update just to check it out.
and fyi renaming the recovery to something simple like recovery.img always makes things in the terminal easier as the gentleman above had mentioned
I want to root but want to be reassured I can unroot for warranty purposes.
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
mmm easy
Ahh, easiest root/unroot makes me happy
Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.
bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?
where can I find the terminal On my pc?
temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.
bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.
hopefully this will help when people want to unroot if the update won't work without unroot
Hi everyone,
A few days ago I got the OTA 2.2.1 on my MT3G and then rooted it using the SuperOneClick tool. I was able to remove all useless apps, pushed others to /system/app with Root Explorer, etc., there is only one to do, and I am clueless: how to replace the stock Android System Recovery <3e> with a custom recovery image, so I can do Nandroid backups, flash .zip files, etc?
I used the ROM Manager app to flash Clockwork, got an "Installation successful" confirmation, but then on reboot into recovery mode my phone got stuck on the MT3G logo. I had to remove the battery, then in second attempt the phone booted into the <3e> image. Restarted again, opened the ROM Manager, according to it Clockwork was installed. Total craziness! Then I tried to flash it using Better Terminal Emulator (su, flash_image recovery /sdcard/Clockwork.img) but I got a "flash_image: not found" message, though I had the image on my sd card.
Any good ideas, folks?
All useful suggestions much appreciated, thanks!
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
It's kinda relative to the topic. I'm stuck on clockworkmod and would like to get back to stock recovery as the new HBOOT doesn't let me flash roms. Is there any way I can do so?
Look in my guide... all the files, steps and binaries are included...
Check out my signature!
Thanks, Asadullah. One more question: Are there different versions of flash_image for different android versions, because I saw in another forum a user complaining he/she didn't use the right binary.
Edit: I've extracted a flash_image binary from CM 6, hope it will work
Edit2: It worked, thanks a lot, man!
I think that flash_image from different devices is different someone correct me if I'm wrong. Glad it worked
Sent from my HERO200 using XDA App
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
lgtsanev said:
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
Click to expand...
Click to collapse
I know it's been a while and you didn't get a reply, and while I found this thread because I too am having enormous trouble rooting this whatever it is cheap chinese android 2.2.1 momo 2 thing covered completely in chinese language apps that I simply cannot use even for the low price it cost me - I thought I'd offer an answer, most likely wrong, but one that may help the next person who may fall into your position.
adb root is an option to start the adb service in root mode, and I can only assume that means for the device.
As I have not been able to get this thing sorted, not knowing what it is really - no phone, no camera, no buttons on the case apart from power/sleep - Home/Esc which do nothing on booting apart from alert the PC to detect a new USB device, no market access, but otherwise exactly what I required - I dont know if it'll help.
But I hate threads left in a question, because I always find them. And this circle of frustration seriously should not be real, it just cannot be this damn hard to do something...
yikes!
help please
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
sky rider said:
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
Click to expand...
Click to collapse
root your phone
install terminal emulator on your phone
type in everything that you quoted except for adb shell
Confused in differences
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Jkhim said:
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Click to expand...
Click to collapse
Honestly it's been so long I forgot ?? I don't think you need too use flash image anymore
rm failed????
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sh: ./flash_image: not found how to fix this sir? im so new about this, sorry about that
---------- Post added at 05:22 AM ---------- Previous post was at 04:43 AM ----------
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sir is this CM.12 cyanogenmod fakelollipop is an example of flash_image even its in a zip file? because i cant get it at all, im stuck at flash_image not found
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.