Develop Bugs

[Q] Need help Rooting

I have been searching and reading, but I still am unsure of which rooting method I should use. I just got my "new" EVO on Friday. Here are my specs:
HBoot 2.2
Hardware 0003
Baseband 2.15.00.09.01
Kernal [email protected]#17
Software 3.30.651.3
Any and all help would be greatly appreciated.

You have two choices:
option 1. Follow the directions and root your phone using these instructions that I copied from the thread below and use the following link to download the correct files: (http://forum.xda-developers.com/showthread.php?t=829045)
option 1 is not recommended for a noob...
option 2. Wait for unrevoked to come out with their update to unrevoked 3. If you wait, almost all of the root process will be automated. Unrevoked should be releasing this update in the next couple of weeks or so. They have been tweeting about it.
Directions from option 1 copied from thread link above:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V71.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V71 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
GOOD LUCK!

Thank you very much. I had been looking at the three different methods, I just wasn't sure which one to go with. I'm downloading the files now, but won't be able to do the thing until i get home. I had a Hero for the longest, and rooting that was pretty simple, but when I got the EVO and looked at the forum; I knew it wouldn't be quite as easy. I just wanted to be certain before I bricked my phone trying to fly blind. I'll let you know how it turns out. Thanks again, I really appreciate it.

You are welcome! I am sure you know this, but make sure you read through the thread first so you can see other hangups other people are having before you start the rooting process. If you have rooted a phone before, I am sure you can root the evo. Good luck!

Worked like a charm. 30 minutes, and I'm rooted. That went easier than I expected. Thanks again!

you are welcome...good luck with choosing a rom kernel combination. I dont flash a new rom or kernel very often (once a month) but right now i have myn 2.2 for a rom and baked battery #5 for a kernel with some setcpu profiles and it works great! I can get a full day of 10 hours of heavy usage (connected to exchange all the time) and lots of texts, web browsing etc and still have 20% battery left

I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.

what version is your hboot?

jay-are said:
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
Click to expand...
Click to collapse
if you still got s-on then you might need to run unrevoked forever. just go to this site.http://unrevoked.com/rootwiki/doku.php/public/forever and run the correct update.zip like you would another rom or kernel

weaselp1 said:
what version is your hboot?
Click to expand...
Click to collapse
i dunno about him. (y must i assume its a dude n not a female on these boards... tsk tsk) but i have hboot 0.97.000
I feel as if i missed my window of rooting my fone when i should of.. now theres a 1000 and 1 threads on the newer versions for newer fones.. and yes i've 'been' reading most of them.. and its all starting to stick. **and whats this i hear about the newer evo screens being more brilliant? anyways, can i follow those same directions u posted? 30 mins doesnt sound bad. even tho 30 seconds with unrevoked is pretty enticing. thanks for your time and effort. might even give u an actuall "thanks" above ur name. just seen those recently and been wanting to give em a try.

the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.

Sent from my PC36100 using XDA App

Some people are having trouble using unrevoked-forever on hboot 2.10 saying that their radio is not supported. Some people have not had trouble and the root worked fine. So, make sure you root before updating to the latest build.

weaselp1 said:
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Click to expand...
Click to collapse
So with me having such an older hoot - 0.97.000, u would recommend what...?? Unrevoked? Thanks for ur time.

Yes, use the unrevoked method because of the version of hboot you have
Sent from my PC36100 using XDA App

[HOWTO]Unlock, Root, and install CWR Galaxy Nexus with Ubuntu Linux or Linux Mint 12

warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP

thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.

I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.

you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply

I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA

ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?

Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?

AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.

loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.

Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.

Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.

Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app

Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img

Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks

worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder

[Q] impossible to access the recovery

Hi guys
I have a huge problem, I have the physical buttons of the volume broken (absolutely non-repairable) while they are trying to install a new Romy (total Wipe and /system format) I accidentally pressed on system reboot into recovery.
in this moment i have the written google when access (obviously it is)
I tried with GNEX Toolkit V11.1 but I have a serious problem
the serial number of the writer but also writes offline
GNEXUS 4.2.2
How do I get into recovery?
Sorry for my bad English

pull the battery, put battery back in.
press and hold vol up and down, then press and hold the power button while still holding vol up and down
use volume buttons to go to recovery. press power button to enter after recovery is selected.
this is basic nexus 101. learn it. and stop using a toolkit.

I have the physical buttons of the volume broken. I usually use the function number 24 of the toolkit to get into recovery, but this time I formatted the /system and I accidentally restarted the cell without installing anything.
The various drivers are installed correctly
GNEX Toolkit gives me the serial number but not online.

pollopopo said:
Hi guys
I have a huge problem, I have the physical buttons of the volume broken (absolutely non-repairable)
Click to expand...
Click to collapse
So basically, you're left with a stock recovery, no adb because of that (Does sideload work out the box? Can't remember; if yes, then OP has a driver issue) and no system to boot from.
Yet another solution would be a USB jig and Odin. Maybe that works for you.
You should drop the toolkit.
a maguro wrote this.

i have the CWM recovery.
already happened once but I had formatted the /system folder, on that occasion was able to enter through the starter toolkit in recovery mode.

help me pleas...

pollopopo said:
i have the CWM recovery.
already happened once but I had formatted the /system folder, on that occasion was able to enter through the starter toolkit in recovery mode.
Click to expand...
Click to collapse
If you have cwm and you can enter the recovery you can adb push..
Sent from my Galaxy Nexus using XDA Premium HD app

This is not xda-spoonfeeeders, read the stickies
Sent from my Nexus 10 using Tapatalk 4 Beta

in the management of devices in windows says it is a samsung device but does not recognize the ADB interface. It is not the first time I connect drivers are all there and they work.

i use the gnex toolkit and the CMD (ADB command ecc...) but both give me the serial number, but respond "device offline" for any command

pollopopo said:
i use the gnex toolkit and the CMD (ADB command ecc...) but both give me the serial number, but respond "device offline" for any command
Click to expand...
Click to collapse
listen buddy, read this thread
http://forum.xda-developers.com/showthread.php?t=1812959
questions that you're asking were answered many many times. learn something for a change. stop using that godamn toolkit.

I have already tried etc. ... I can not get into recovery
I have the volume buttons broken and adb gives me "device offline"
http://imageshack.us/photo/my-images/822/dgq9.png/
I searched and searched but can not seem to solve the problem
all the drivers are installed, as well as "omap 4460" and all work properly.
I can not get him in the recovery through adb or toolkit

pollopopo said:
I have already tried etc. ... I can not get into recovery
I have the volume buttons broken and adb gives me "device offline"
http://imageshack.us/photo/my-images/822/dgq9.png/
I searched and searched but can not seem to solve the problem
all the drivers are installed, as well as "omap 4460" and all work properly.
I can not get him in the recovery through adb or toolkit
Click to expand...
Click to collapse
Forget it. Use a USB jig to get in download mode, its your only chance.
a manta wrote this.

thank you very much, as soon as I get from ebay hope to be able to solve everything

how do I prevent odin erase all sd memory??
I downloaded the original rom I extracted,
I extracted the file image-yakju-jdq39.zip
Inside there is the file system.img
I converted the file through GNEXUS toolkit. Tar
If I use this file with odin you can avoid that deletes all data on sd and change the recovery etc. ..?
Solved by the method mentioned above

[Q] Nexus 7 (2013) no operating system, No ADB. Am I boned??

I have a Nexus 32gb 2013 model that I've rooted with Wug's Nexus root toolkit v. 2.04. Everything was all find and dandy when I tried to update to Timer's Rom (not his fault) and I somehow deleted the operating system. The Nexus just shows the "Google" logo with a unlocked logo beneath and nothing happens. I did do a backup when I originally unlocked and rooted the Nexus but when I tried to install the backup, it does nothing. I already tried the DeVeiw thing and it did nothing. Actually it did help my PC recognize my phone again. To make it worse, I tried to install something to the Nexus but the computer won't recognize the Nexus. Neither will it load anything from an OTG cable. I took it to some place in town and they told me although the Nexus charges without any issues, the port might be messed up but I think this was his way of saying he has no idea what's up. Any ideas would be greatly appreciated. P.S. I still have access to TRWP (V. 2.8.4) and under "Restore" I do have a backup in there named cm_flo_userdebug 4.3.1 JLS361 blablabla. I already tried to install that with no luck. Am I boned? Any ideas would be greatly appreciated.

Does your computer see it when it's in fastboot? If so, flash a factory image (with fastboot) and start over.
And don't use toolkits.

No. Sadly it does nothing when I plug it in.

Does your computer recognize it while in bootloader? When in recovery, do you mount /system?

It does nothing when I plug it in. Not sure what you mean by me mounting the system.

1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.

pacificfils said:
1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.
Click to expand...
Click to collapse
I tried doing this but there is no way for me to side load anything because the PC wont recognize it. I think I am boned. I seriously wondering if there is something wrong with the USB connection even though it charges, I cant seem to get the PC to recognize it. The Nexus goes into TWRP but it wont recognize an OTG cable. When I connect it and try to select it, it just doesn't register. I wonder if I need to changed the USB board?Any other ideas before I do that? P.S. thanks for any help guys, I really appreciate any input.

LG Nexus 5X V7.1.2 B/N: N2G47Z ( No Command No Custom Recovery )

Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!

DarkXShadowX21 said:
Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk

In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
jugoslavpetrovic said:
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you guys for the help! I successfully rooted my Nexus 5X! It's time to go exploring into the roots! :good: