Related
If you have a 2.73+ rom with the latest hboot you will need to follow This Post to boot the recovery image
1) restart into bootloader (switch on holding the back button)
2) Extract the latest GSM Hero recovery IMG into your android SDK/tools folder
(For SDK & CMD help reffer to Post 3 "The Basics" )
3) Download Superuser.zip and extract the contents to your SDK/tools folder.
4) Plug in USB
5) open a CMD prompt from the tools directory and type the following command> fastboot boot recovery-RA-hero-v1.5.2.img
(you should now enter a recovery console on the handset)
NOW PERFORM A NANDROID BACKUP from the recovery menu, once completre, continue..
6)then type the following commands in CMD exactly as they are here, hitting enter for a new line.
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
Congratulations you now have root access..
Download "Root Boot" from the app store (this will only work if you have root!)
Step 6 modified thanks to ENLIGHTENER, cheers, su whitelist working nicely now..
Recovery image updated to recovery-RA-hero-v1.5.2.img , thanks to Amon_RA
Please be carefull! I accept no liability!
FYI, To unroot you will have to either restore an earlier backup or flash a stock rom..... (reccomend the new official HTC Update via RUU to do a full reset)
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
The Basics
gaabrysz said:
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
Click to expand...
Click to collapse
1) you need to download the android software development kit from Here and extract it to yourhard drive.
2) (check) fastboot and adb should be located in the tools folder.
3) in tools right click>new>shortcut when asked enter CMD.exe
4) right click on cmd.exe shortcut, go to properties and clear the "start in" box.
job done, follow as above.
*Edit*
FYI
Verify you have root, go to app store> download Root Booter and test its functions if this works, you have root!
The G2 is the HTC Hero on T-Mobile.
The SDK includes all the drivers needed.
once you have booted the img via fastboot you should enter a recovery console, at this point you need to follow the instructions exactly as typed for adb,
I am running windows 7 Ultimate, should be the same for all windows platforms,
Cheers
__________________
Thank you
Oh and one more question. Do i loose any data doing this??
gaabrysz said:
Thank you
Oh and one more question. Do i loose any data doing this??
Click to expand...
Click to collapse
No, you will not loose anything but be sure to do a Nandroid incase you need to go back to "Stock"
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
Use a program that requires root access.
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
If by G2 you mean HTC Magic/Sapphire rather than HTC Hero you're in the wrong place...
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Just tried it and it works sweet... Took all of 5 minutes... Awesome work thank you
I now have root access on my Hero
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Have you installed the correct drivers? They are located in the SDK folders you downloaded.
If so try entering "adb devices" in the commmand prompt, Just incase the daemon didnt start.
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Having the exact same problem here.
gaabrysz said:
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
Click to expand...
Click to collapse
try entering adb devices see if that makes any differences
btw, when i done mine the phone was in the recovery console..
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Ok so lets clear something. after i type in cmd: fastboot boot cm-hero-recovery.img my phone reboots and goes to recovery console where i have some otions.... so now i have to type in cmd: adb shell, yes??
still nothing and the adb devices didn't help.
Mienaikage said:
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Click to expand...
Click to collapse
Can u share a link to the drivers?? Please
it sounds like a driver issue. Using the lastest SDK?
android-sdk-windows-1.5_r3
OK got it working. It is a driver issue. using latest sdk but i had to use older drivers just like Mienaikage sad.
gaabrysz said:
Can u share a link to the drivers?? Please
Click to expand...
Click to collapse
They came with the SDK I believe, in the android-sdk-windows-1.5_r3\usb_driver\amd64 folder.
If that's not it then it was this one: http://forum.xda-developers.com/showthread.php?t=446274
I was just messing around with TWRP trying to flash a new ROM. I forgot to make a backup and wiped the internal storage + system (in other word I wiped everything) I have the files in my computer but I don't know how to access them since the computer can't recognize my device. Any suggestions? :crying:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Since the device can't be recognized I would try to search for the ADB drivers. This happened to me on my kindle fire hd 7" and the only way I could fix it was by doing "adb sideload filenamehere.zip" after going into Advanced > ADB Sideload.
Hope I could help!
I'm very grateful
thanks
you rock bro
Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Im new to this world of tablets and all the commands and prompt, etc... but I thought that I would never solve my problem lol. I'm still a noob but
Thank you for all what you did for my kindle fire hd. I just wanna let people know you helped me unbrick my kindle ( you worked more than 4 hours to be exactly on my kindle) not many people in this forum would do that :good: and thanks to all the developers and mods you nailed it quite well on unbricking my kindle using the programs they have developed.
Editing the drivers so they could work on my machine (I live in El Salvador so my region is a problem when i try to install the drivers) was no easy quest and using teamviewer for letting you work was cool, but the best part is that you installed the cm10.1 by Hash which I had before bricking my device. You saved my kindle bro, thanks A LOT!!!!! I appreciate it. :victory:
EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways
lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app
when i tried to push error device not found lol
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*
xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1
Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Raziel88 said:
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
In TWRP, go to advanced settings, click ADB Sideload, swipe to start sideload, and then type in adb sideload rom.zip
Raziel88 said:
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Did you change the command prompt to the directory where adb/fastboot is located at?
You can also try and download mini-sdk . Unzip it into c:\mini-sdk. Go to folder and hold shift and right inside folder then select open command prompt. See if you can then get adb devices to pick up device.
Raziel88 said:
openned cmd, used "adb devices" command but it says device offline.
Click to expand...
Click to collapse
You have a basic USB connectivity issue, so no adb commands are going to work.
Try uninstalling HTC Sync and any HTC drivers, then re-install HTC Sync.
If it still doesn't work uninstall them all again, then try to plug in the phone. When it tries to install HTC Sync automatically, cancel it. Go to Device Manager (if using Windows) find the device, select the option to install drivers manually and select Generic Android MTP device (or something to that effect).
Also, try a different USB port or cable; even another computer if possible.
ty friend it helped +1
Raziel88 said:
ty friend it helped +1
Click to expand...
Click to collapse
One of the solutions worked? Which one specifically?
redpoint73 said:
One of the solutions worked? Which one specifically?
Click to expand...
Click to collapse
finding the driver on device manager solved the problem thanks again :good:
Raziel88 said:
finding the driver on device manager solved the problem thanks again :good:
Click to expand...
Click to collapse
You're very welcome. Please feel free to click the "Thanks" button for any posts you found helpful.
USB connection was driving me crazy one time, trying everything else (various drivers, different ports, etc.) until I tried this simple solution.
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
djr83 said:
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
Click to expand...
Click to collapse
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Heisenberg420 said:
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Click to expand...
Click to collapse
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
djr83 said:
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
Click to expand...
Click to collapse
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Heisenberg420 said:
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Click to expand...
Click to collapse
Exactly, I'm not getting any devices.
djr83 said:
Exactly, I'm not getting any devices.
Click to expand...
Click to collapse
Have u enabled USB debugging in developer options?
Heisenberg420 said:
Have u enabled USB debugging in developer options?
Click to expand...
Click to collapse
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Edit: Tried another USB port on the computer and it's working now.
djr83 said:
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Click to expand...
Click to collapse
I'd say its the drivers. Try to reinstall
You can try adb over WiFi without the drivers, download an adb wireless app from the market, enable it, get the IP address of your phone in the app, then connect through adb
Adb connect <IP[emoji14]ORT HERE>
then try adb devices