Related
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
Hey Guys,
I Clockwork3'd my Aria, but I wanted to update my sources (thread 730398) so I can get non market apps. When I follow the instructions in that post I get an error:
Code:
./adb remount
remount failed: operation not permitted
'adb devices' does show my Aria's SN, I'm su'd and I'm running in debug mode. I also chowned everything in the android sdk tools and its subdirectories.
Here's the question -
In searching, I found (thread 614645) that suggested ro.secure wasn't set properly, and sure enough if I do:
Code:
./adb shell
$ getprop ro.secure
1
$
Shouldn't applying clockwork have set that properly? Would the instructions at (thread 8041739 post 9 ) be the right steps to resolve this on an Aria?
Thanks!
PS - sorry I can't post direct links.
if you have all the drivers installed, it should work...
which OS are you using?? (Mac, Win7, etc)
dont rund SDK command in Clockwork, with phone on connect data cable and select "charge only" when asked.
the ./ command is used for Linux i think, i never got that command to work either. just go to the folder where SDK/Tools is located in CMD prompt or Terminal(depending on the OS) and run the following command:
adb remount
hope this helps a bit
I had a lot of issues with driver installs on Windows 7, so I'm doing this on a netbook with Ubuntu netbook remix. Also tried the reflash CD, similar issue.
Right, so with Ubuntu, and the cable my phone came with (have tried a few others just in case)
1. phone on and operational
2. plug in to laptop
3. phone gives happy USB connected and Charge Only notifications
4. fire up terminal window, and su
5. type ./adb remount
and I get the error above. If I do kill-server to refresh it, I get the demon starting successfully on port 5037.
Yeah, I was hoping I'd just missed something stupid. Should I need to modify the boot.img file outside of what Clockwork did?
My symptoms match those described in thread 685146 post #3, however, I've only applied Clockwork (which seems to work) not done anything else funky.
I have my windows 7 machine at the same point now -
adb remount gives 'remount failed: operation not permitted'
and
getprop ro.secure at the adb shell returns 1.
I think this means there's something wrong on the phone, if both machines act the same.
One other data point, I noticed the new Superuser Permissions app that installing clockwork gave me is asking to give superuser permissions to /system/bin/sh when I try to run the adb shell, but it doesn't trigger that when I do the adb remount.
Not sure what this means, any ideas most welcome - TIA!
steps here fixed it, thanks - http://forum.xda-developers.com/showthread.php?t=730398
I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).
martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us
901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.
Do i enter commands 1 at a time or all at once?
901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck
Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again
Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available
You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".
You don't need ADB for G2s.
trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?
After having nearly hung myself trying to figure out the whole SDK thing, what the hey ADB was and all that jazz, I thought I would give the rest of the people out there a step by step guide on getting from stock to root in no time. If you follow this guide, you won't spend the hours I did on google, XDA and irc trying to get where I am. This stuff can be confusing, and I am only here to make it less so.
Disclaimer: If you destroy your phone, I take no responsibility for it. You are performing this at your own risk.
I take no credit for the root process itself, there are people much smarter than I who worked on this. I used the method outlined here by jcase. I am simply compiling this and making it easy for people (much like myself) who had no prior experience be able to have root.
jcase said:
Credits (from original post here)
Scotty2, jamezelle, jcase, and all of Team AndIRC
Testers, especially ProTekk and Trident
Thanks to scotty2 for WPThis
Busybox was pulled from a CyanogenMod ROM, source should be available here
psneuter was pulled from somewhere, credit to scotty2, source here
All firmware credit goes to 911sniper
Jaroslav from Android Police for editorial help
If I missed anyone in the credits, it was unintentional and I will fix it soon. Lots of people had their hands in on this project.
Original warnings, posted by jcase:
Pros
Root with read/write access to /system
Ability to downgrade and flash any RUU (i.e. signed firmware)
S-OFF
Fully unlocked bootloader
All ThunderBolts survived testing
Cons
Voids warranty
Could brick your phone if you aren’t careful
The method of rooting your Android device as described in the article herein is solely for enthusiasts and not for the faint of heart.
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
Android Police and Team AndIRC disclaim all liability for any harm that may befall your device, including, but not limited to: bricked phones, voided manufacturer warranties, exploding batteries, etc.
The instructions below assume you already have a strong familiarity with adb command lines – this is not for beginners.*
Click to expand...
Click to collapse
*I made this guide as seamless and easy as possible. I have tested this 4 times now with success each time. Just follow every step to a T and there will be no problems. The warning is there to tell you what could happen if you don't listen very well...
Step 1: Download the Android SDK
http://developer.android.com/sdk/index.html
Step 2: Get into the SDK
After downloading, you should have a package named android-sdk_r10-mac_x86.zip in your downloads folder. Unzip it and move it to your desktop, to make life easier on yourself.
*Stop here right now if you have no idea what terminal is... shame on you, also this might be slightly more technical than you thought. No worries, I am going to hold your hand through it all*
Step 3: Get ADB
You can search as hard as you want to in that SDK and you won't find ADB. It's not there, leave it to google to be smug and leave a "ADB's not here sucka!!" readme in the file... cheeky muppets. Regardless of my personal feelings, You need to get ahold of the ADB. Easy enough to do. Open the tools folder located in the android-sdk-mac_x86 folder. Click on "android" (it's right next to google's smug readme...), and wait until it pulls up the screen seen below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you've gotten here, click "available packages" on the left and install Android SDK Platform-tools, revision 3. Let it go through it's process and click close. Now, go back to your android-sdk-mac_x86 and you'll have the folder titled "Platform-tools", open it and, TA-DA! You have adb, don't click it... you don't need to.
Step 4: Prepare your phone for rooting.
Make sure your phone is fully charged before beginning. Go to Menu>Settings>Applications>Developer> and turn on USB Debugging. I had my phone on Disk Drive the entire procedure, I'm not sure if it had any benefits other than convenience, but, granted, it helped.
Step 5. Setup terminal for ADB.
To this point, you haven't had to open terminal on your own. It is probably still open from when you installed the platform-tools folder from the android executable file. If it is, right click (control click) the terminal icon, click new window and then click basic. If you closed it haphazardly (shame on you!) you need to open it. It is located in your application folder, in another folder titled Utilities.
Once you get to the terminal screen, you should see a white box, with the name of your computer, followed by the place your currently "located." A ~ means you are in your home folder. For fun, type the following into your terminal window.
Code:
touch test_file.txt
Now, navigate to your home folder and there is a text file there for you. Pretty neat, eh?
Now, we need to navigate to adb. Go to your android-sdk-mac_x86 folder, open it. Now, go back to terminal, type cd and drag the folder Platform-tools to the terminal window. You should see a green dot with a plus sign in it, that means you can add the folder to the terminal window. It should read something like this:
Code:
cd /Users/Your Computer's Name/Downloads/android-sdk-mac_x86/platform-tools
If you moved the android-sdk-mac_x86 folder (Like I did) after downloading it, it will only be slightly different. (My folder was in my home folder, so it just says /users/my computer/android-sdk-mac_x86/platform-tools)
Once you do this, you are ready to begin.
Step 6: GAIN ROOT!!!!11!!
Take a moment, breathe, cry, caress your phone... No, it really isn't that bad. I am what many consider a hypochondriac, I say I am just more "down to earth."
Glass half empty, half full, etc. we begin. I've slightly modified these to make them usable for us Apple guys. (All that has been changed is the adding of a "./" to the beginning of ever adb.)
Step 1
First, download these files:
RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.0103_2r_NV_8k_1.37_9k_1.52_release_
165253 (md5sum : aae974054fc3aed275ba3596480ccd5b):
Multiupload mirror
GalaxySense mirror
DroidSite mirror
Mirrors for the package (contains busybox, wpthis, psneuter, su, readme.txt, misc.img, and hbooteng.nb0) (md5sum : 3b359efd76aac456ba7fb0d6972de3af):
Multiupload mirror
GalaxySense mirror
DroidSite mirror
Custom RUU mirrors (md5sum : aff07b8256628a175c40938d408fa16f):
Multiupload mirror
GalaxySense mirror
(Personally, I extracted the exploit.zip folder, and the RUU_MECHA to my platform-tools folder so I never had to cd anywhere. I strongly recommend you do the same. I put the Custom RUU [PG05IMG.zip] on my desktop, so I didn't get it confused later in the process)
Step 2
Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:
Code:
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push misc.img /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
Step 3
This step will gain temp root and flash the custom misc.img. Run:
Code:
./adb shell
Now the shell should display "$".
Run:
Code:
/data/local/psneuter
You will now be kicked out of adb, and adb will restart as root. Let’s confirm the md5 of misc.img:
./adb shell
At this point, the shell should display "#".
Run:
Code:
/data/local/busybox md5sum /data/local/misc.img
Output should be "c88dd947eb3b36eec90503a3525ae0de." If it’s anything else, re-download the file and try again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
exit
Step 4
Here you will rename the downgrade RUU (RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.0103_2r_NV_8k_1.37_9k_1.52_release_165253_signed.zip) as PG05IMG.zip and place it on your SD card. Then, run the following command:
Code:
./adb reboot bootloader
Choose the bootloader option and press power; let the ROM flash. When asked to upgrade, choose yes. Don’t freak, it’s a long reboot.
Once done, reboot and delete PG05IMG.zip from your SD card.
**Make sure to Re-enable USB Debugging!!! (Menu>Settings>Applications>Development>USB debugging)**
Set up the two part exploit, to gain root and unlock MMC.
Code:
Push wpthis, busybox, and psnueter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push wpthis /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
./adb shell chmod 777 /data/local/wpthis
Step 5
Next, enter the following commands:
Code:
./adb shell
/data/local/psneuter
To unlock eMMC:
./adb shell
/data/local/wpthis
exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
Code:
./adb push hbooteng.nb0 /data/local/
./adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
Code:
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
Code:
/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #thunderbolt.
DO NOT REBOOT.
Now, reboot your phone and put the custom RUU (PG05IMG.zip) on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
**Make sure to Re-enable USB Debugging!!! (Menu>Settings>Applications>Development>USB debugging)**
Next, run this command:
Code:
./adb reboot bootloader
After it flashes, you will be running release firmware with S-OFF.
Step 7
Code:
Push SU, busybox, and psneuter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push su /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
To gain root:
Code:
./adb shell
/data/local/psneuter
The following will remount /system and set up SU:
Code:
./adb shell
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
/data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Step 8
Install Superuser from the Market.
Reboot your phone. You should now have full root permissions.
Step 9
Finally, install ROM Manager from the market, enter ROM Manager and flash the ThunderBolt recovery.
If you have problems getting SU to work, a couple extra reboots will likely fix it. If you still have problems, come to the chat: irc.andirc.net #thunderbolt or use http://chat.andirc.net:9090/?channels=#thunderbolt.
And there you go. You now have root. That was fun right? The irc is absolutely invaluable if you are having any trouble. The people there are really helpful and knowledgable. They won't talk down to you, just try to help.
Again, thank you to the people who made this possible, You all are awesome. the work that had to be done to make this user friendly is beyond amazing.
If I missed anything, please let me know. I might have missed something, I haven't slept all night.
Quite the thorough walk through. Nice job!
Sent from my ADR6400L using Tapatalk
Looks like a nice walk-through.
I may suggest including all of your steps for configuring the SDK and then simply referencing the official root guide... because if that would get updated then you would have old instructions on this thread.
It is not that hard for people to type the ./ in front of every command...
Alternatively (and recommended), you could provide a more thorough guide and include instructions on adding the SDK platform-tools directory to the PATH environment variable. Once this is added, the user can use adb whenever they want, they do not have to change directories to the SDK! This also allow for using the command without needing the leading ./
I knew people would come in who knew something... You both are right. The problem I was having was the same many of my friends and people on here were having, they kept getting a -bash: adb: command not found. I am working on fixing my .bash_profile, but until I get that fixed, this tutorial is the best I've got.
IISiDeK1CKII said:
I knew people would come in who knew something... You both are right. The problem I was having was the same many of my friends and people on here were having, they kept getting a -bash: adb: command not found. I am working on fixing my .bash_profile, but until I get that fixed, this tutorial is the best I've got.
Click to expand...
Click to collapse
I am excited try try this, thank you so much for writing this up. I get very confused doing these things the first time and didn't realize you could do this on mac by adding the prefix in the commands. So, now that I know that, I am hoping to try it!
One question.....and this is a total newbie question, sorry..... In the steps that have several commands like this one:
Set up the two part exploit, to gain root and unlock MMC.
Code:
Push wpthis, busybox, and psnueter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push wpthis /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
./adb shell chmod 777 /data/local/wpthis
Click to expand...
Click to collapse
Should the commands all be ran individually, or all at the same time just on their own lines? Like, can I just copy all six commands and paste them in just like this then hit enter? Or do I need to run them all one at a time?
gadsden said:
I am excited try try this, thank you so much for writing this up. I get very confused doing these things the first time and didn't realize you could do this on mac by adding the prefix in the commands. So, now that I know that, I am hoping to try it!
One question.....and this is a total newbie question, sorry..... In the steps that have several commands like this one:
Should the commands all be ran individually, or all at the same time just on their own lines? Like, can I just copy all six commands and paste them in just like this then hit enter? Or do I need to run them all one at a time?
Click to expand...
Click to collapse
You hit enter after each of those commands.
I'm AMAZED at how well this went! I'd been avoiding ADB on windows, plus avoiding all the 1-click options as they didn't work correctly on VMWare/WinXp on my Mac Pro. So, I saw this post and decided to take the leap.
THANK YOU!!!! My device is now rooted and working flawlessly.
Nice write up, I completely avoided the whole ADB setup subject, due to a lack of mac/windows knowledge. Glad the community can come through.
Can you please paste in my warnings, full credits and links to the GPL (this part if very important to us) sources if you are going to base this on our stuff. Just take them from the original post please.
~jcase
I ALWAYS had to put the
./
before adb so it would be "./adb" for anything that started with adb. I see you missed it a couple times and that concerns me. I followed the original tut by jcase and put ./adb instead of plain adb and everything worked perfect. Just my 2¢.
bmcclure937 said:
Looks like a nice walk-through.
I may suggest including all of your steps for configuring the SDK and then simply referencing the official root guide... because if that would get updated then you would have old instructions on this thread.
It is not that hard for people to type the ./ in front of every command...
Alternatively (and recommended), you could provide a more thorough guide and include instructions on adding the SDK platform-tools directory to the PATH environment variable. Once this is added, the user can use adb whenever they want, they do not have to change directories to the SDK! This also allow for using the command without needing the leading ./
Click to expand...
Click to collapse
I really didn't realize until today that I could just as easily perform a manual root on a mac as a windows machine. So, I am trying to learn about this, been doing a bunch of reading. I am interested in what you are mentioning about adding SDK platform-tools directory to the PATH environment. On a mac, what environment should I be using? I am a little confused about the options listed on the Andorid Developer website. It seems Eclipse is what everything is all about primarily, but I have no clue which one to use. Perhaps I ought to just not worry about all that right now and just follow these steps to root my TB? I'm not really after doing anything other than rooting and flashing ROMs, so is it really necessary to set all that up?
xCHPx said:
I ALWAYS had to put the
./
before adb so it would be "./adb" for anything that started with adb. I see you missed it a couple times and that concerns me. I followed the original tut by jcase and put ./adb instead of plain adb and everything worked perfect. Just my 2¢.
Click to expand...
Click to collapse
Regarding the ./ Are you saying that we need to use that in front of these commands even though it's not listed in the steps?
adb reboot bootloader
adb shell
Other than that, the steps in this post work, right? I have everything downloaded and got as far as getting ADB, but I don't want to go any further if this isn't really as comprehensive as its made out to be.
gadsden said:
Regarding the ./ Are you saying that we need to use that in front of these commands even though it's not listed in the steps?
adb reboot bootloader
adb shell
Click to expand...
Click to collapse
Yes otherwise i don't believe it will work.
Wow! I really didn't think this would get quite as much attention. I think I need to do some more solid work and clean this up a bit. Now, for the individual responses:
@Gadsden: You're very welcome. I kept thinking, this is impossible! But, with a little Red Hat experience and some awesome google skills, I got this.
@Jayhammy: You're welcome man. Enjoy!
@jcase: Of course I can. I never really thought this would gain so many views. There aren't words to explain how psyched I am to see you talking directly to me... lol, I will give full credit to everyone, as soon as I post this
@xCHPx: I posted this after a long night, with no sleep. I knew I would miss something. The cool thing about that is if you copy and pasted the command without ./ in front of it, it would simply not run. There is really no way to mess this up.
@gadsden (pt.2): Hypothetically speaking, you don't need to do ANYTHING other than what I've listed. If you decide to start developing themes, apps, etc. you'd have to worry about eclipse. I made a mistake on the two things listed there, every adb command must have ./ in front of it. I simply overlooked it when typing this up. There was a lot of stuff to be typed.
thanks for the walk-through!
i have 2 quick questions...
for say like this step:
./adb shell
/data/local/psneuter
To unlock eMMC:
./adb shell
/data/local/wpthis
exit
Click to expand...
Click to collapse
ur hitting enter after shell correct? the /data/... doesnt need a program command like ./adb before it correct? same with all other lines with no ./adb in front of them?
also for this:
Step 9
Finally, install ROM Manager and flash the ThunderBolt recovery.
Click to expand...
Click to collapse
im assuming ROM Manager is in market like Super User but i dont know what flash the Thunderbolt recovery means...could u explain that?
Thanks again!
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
IISiDeK1CKII said:
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
Click to expand...
Click to collapse
Funny, I had the same exact question. I posted it in the jcase discussion and got the answer there. Definitely put that in the OP, because first timers don't know these things!
gadsden said:
Funny, I had the same exact question. I posted it in the jcase discussion and got the answer there. Definitely put that in the OP, because first timers don't know these things!
Click to expand...
Click to collapse
Fixed it, I overlooked it. I guess I assumed that everyone knew what ROM Manager was... lol. I've been rooting since the Droid 1, so I've always been around people who know these things. Sorry for not clarifying though, I hope my new updated post is more concrete.
gadsden said:
I really didn't realize until today that I could just as easily perform a manual root on a mac as a windows machine. So, I am trying to learn about this, been doing a bunch of reading. I am interested in what you are mentioning about adding SDK platform-tools directory to the PATH environment. On a mac, what environment should I be using? I am a little confused about the options listed on the Andorid Developer website. It seems Eclipse is what everything is all about primarily, but I have no clue which one to use. Perhaps I ought to just not worry about all that right now and just follow these steps to root my TB? I'm not really after doing anything other than rooting and flashing ROMs, so is it really necessary to set all that up?
Click to expand...
Click to collapse
You can add the path of the SDK to your $PATH variable. This allows you to run ADB from any directory and not need the ./ in front of every single command.
From terminal, do the following:
Code:
ls -la
You should see a file called ".bash-profile within your home directory.
Edit this file and add the path of your SDK to the $PATH variable.
Code:
nano .bash-profile
Familiarize yourself with editing files in nano if you have not done this before. It is very simple. Once you have edited and saved the file... run this last command to check if the PATH variable now contains the new path.
Code:
echo $PATH
If you get lost or confused... Google is your friend! There is a lot of info on editing the PATH environment variable.
*Please Note* this is not needed for the guide but it does allow you to run ADB from any directory... and without leading ./ in front of all commands.
Thanks for this. I'm going to go to lunch and then get into this. How long did it take everyone to go through this?
bmcclure937 said:
You can add the path of the SDK to your $PATH variable. This allows you to run ADB from any directory and not need the ./ in front of every single command.
Click to expand...
Click to collapse
I've set my path up, and it works when I want it to... but this is easier to do (imho) without getting too far into command line. If I feel I could streamline this by doing such, then I will do so.
edit: And now it is broken again... back to troubleshooting... not quite sure wth I did...
@want a droid: The thing that will take the longest is downloading the files needed. Everything else will take you all of 30 minutes at most.
IISiDeK1CKII said:
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
Click to expand...
Click to collapse
IISiDeK1CKII said:
Fixed it, I overlooked it. I guess I assumed that everyone knew what ROM Manager was... lol. I've been rooting since the Droid 1, so I've always been around people who know these things. Sorry for not clarifying though, I hope my new updated post is more concrete.
Click to expand...
Click to collapse
thanks man!
yea im coming from a BB so new to this stuff...i have a PC and im doing long way to learn...doesnt seem hard, simple terminal commands but just want to get everything rights...soon as i do it once, ill be good to go and help out others like u guys
I am getting the following error when I try to pull a TWRP backup from my Nexus 4. Can anyone please help?
Code:
remote object '/sdcard/TWRP' does not exist
It doesn't exist there. /sdcard/ is really a symlink. The actual location is /data/media/0/TWRP, but try /storage/emulated/0/TWRP as well.
Next time type "adb shell" to go into the phone, then type:
find / -type d -iname twrp
this will search the entire phone for folders with the name TWRP and list their path.
/ is the root folder of the phone to search in
-type d means search for folders only, leave it out if you want to search for file names
-iname means to search for terms case insensitive
sent from xda premium app
Thanks for the help eksasol. I've tried to pull many different paths and they all return the same remote object does not exist error. I've even tried sudo adb pull, with the same result. I've tried this, find / -type d -iname twrp but, all I get is Permission denied. If anyone else has got some ideas I'd be happy to hear them. Thanks. :good:
If you are using Ubuntu or linux, typing 'find' only search what is in your PC. You get permission denied because you want to search in a root directly that required root permission.
To search for files in your phone, you need to log into your phone by typing "adb shell". TWRP give you root by default, then you can use the find command.
Since you have root by default in TWRP, you don't need to use sudo, also Android do not have "sudo" installed. The correct way to gain root privilege in linux (Android) is by typing: su -
To tell if you have are root, you should see # where your user name is in the command window.
Once you are done finding the path, you need to exit the adb shell in order to make contact with your PC, so just type exit. Only then you can start using "adb pull".
by the way, its "adb pull /data/media/0/TWRP/ \home\username\backup\"
Rememer in linux (Android), it's case sensitive.
OK, I see my mistakes now. I was not exiting adb shell when typing adb pull. Anyway, thanks to your help, everything is working correctly now. Thank you again, I really appreciate it. Now I can flash the 4.4 update safely.
eksasol said:
If you are using Ubuntu or linux, typing 'find' only search what is in your PC. You get permission denied because you want to search in a root directly that required root permission.
...
by the way, its "adb pull /data/media/0/TWRP/ \home\username\backup"
Rememer in linux (Android), it's case sensitive.
Click to expand...
Click to collapse
Thanks for helping me re-learn that linux (Android) is case sensitive