Develop Bugs

Rooting the HTC Hero/G2..(success)

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

[GUIDE][US WIFI & 3G] How To Root Your Xoom From 3.2 Stock [PC & Mac]

**THIS IS FOR US WIFI & 3G XOOM**​
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.​
________________________________________________________________________________________​
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom **DO NOT USE WITH HC 3.2.1. IT HAS BEEN REPORTED TO CAUSE WIFI FAILURES** USE THIS TO ROOT HC 3.2 AND THEN UPDATE TO 3.2.1 USING THIS METHOD.​
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.​
You will need Xoom USB drivers and Fastboot​
You will need the WIFI boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
OR You will need the 3G Verizon boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
You will need Superuser.apk and su binary to enable functioning root​
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**​
PROCEDURE
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.​
Type; adb reboot bootloader​
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)​
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.​
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)​
Type; fastboot flash boot rootboot.img (for WiFi)​
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)​
Type; fastboot reboot ​
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.​
In the command window on your PC type; adb remount​
Type; adb push su /system/bin​
Type; adb shell​
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)​
Type; chmod 4755 /system/bin/su ​
Type; exit​
Type; adb push Superuser.apk /system/app​
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted. You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it. You should be prompted to allow superuser permissions.​
Mac Only Procedure​
You will need fastboot for mac - download HERE​
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot rootboot.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell
Type; chmod 4755 /system/bin/su
Type; exit
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.​
If you found this helpfull press the THANKS button.​

Excellent write-up, I'll try this when I get a chance.
Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...

Works great!
I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!

thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?

_delice_doluca_ said:
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
Click to expand...
Click to collapse
It is only a boot partition with rooted stock 3.2 kernel.
Sent from my HD2

[*]In the command window on your PC type; adb remount​[*]Type; adb push su /system/bin​[*]Type; adb shell​[*]Type; ln -s /system/bin/su /system/xbin/su ​[*]Type; chmod 4755 /system/bin/su ​[*]Type; exit​[*]Type; adb push Superuser.apk /system/app​
Click to expand...
Click to collapse
when I type adb remount after completely boot, I've got error device not found !!! any idea??

Hussain Isa said:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Click to expand...
Click to collapse
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.

Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out
Mad respect to Motorola for getting this one right
And last but not least, Thanks so much to the OP for the great writeup!

jase33 said:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Click to expand...
Click to collapse
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App

Hussain Isa said:
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you certain you have unlocked the bootloader?
Sent from my HD2

jase33 said:
Are you certain you have unlocked the bootloader?
Click to expand...
Click to collapse
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App

Hussain Isa said:
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If you get an error please post exactly what it says.
Sent from my Xoom

Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.

droidx1978z4 said:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
Click to expand...
Click to collapse
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.
Sent from my HD2

thanks jase33 my problem was with the driver, I re-install it & now rooted

Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock

WOW! Thanks jase33 that was painless.
Everything worked great, just as you said it would.

fwempa said:
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you worked it out.
Sent from my HD2

Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
Sent from my Nexus One using XDA App

fwempa said:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall the driver, that will solve your problem
Sent from my Xoom using XDA Premium App

KF Failed Root

Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!

Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2

Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.

I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.

AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2

ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567

From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA

I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!

soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!

AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA

For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.

soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA

backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!

I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.

AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA

AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.

soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.

AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.

[WIP] [TUT] How to Root HTC One Xv

Want closed till me and 8trix figure what the hboot update IMG is called
PLEASE HIT THANKS.... READ ALL BEFORE PROCEEDING
FIXED COMMANDS HAD A COMMON MISTAKES
Hi, I am a developer from the " HTC Droid Incredible 4G LTE " My Rom http://forum.xda-developers.com/showthread.php?t=2065615 and I am still a newbie at this developing thing.. So with this being said I am not resposable for anything that could or may happen.*
Now I'm this TUTORIAL I will be providing the links and the instructions on how to proceed on the rooting process
*Requirments*:
-Android SDK - http://developer.android.com/sdk/index.html
-HTC drivers -*http://www.htc.com/us/support/
-The Su .zip - attachment
-And.... The HTC One Xv of course.
STEPS:
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4. To makes matter safer your gonna need to Temp Root, download this : http://uploaded.net/file/h44f6vni
5.Once downloaded, unzip it to C:\Root. Navigate to the folder in the command Prompt by typing *please follow directions CLEARLY
- *cd c:\Root\stuff
- *adb devices
- *adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet! Now type:
- *adb shell "while ! ln -s
/data/local.prop /data/data/com.android.settings/a/file99; do
:; done"
(errors will appear, ignore) Accept the restore on the device, then type:
-adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.) After reboot type:
- adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over. At this point, you can optionally do this ONLY if you want to revert changes:
- rm /data/local.prop
- exit
- adb reboot
Close cmd and start a new one then type
- adb devices
- adb install /system/apps/superuser.apk
- adb push su /system/bin or try adb push su /system/bin/su
6. - adb reboot
7. reboot twice, and if this don't work then please leave a comment and I will explain a new way.
ATTENTION
2nd way to try to root
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4.read carefully
5. create a folder were the superuser.apk and Su file is and name it system and inside that make a bin folder and place the Su file in the bin folder
6.Go to the folder were you extracted root folder in the last root alternative
7.Open cmd in that folder and make sure to extract the files ( superuser.apk and Su file to the root of the root folder )
8.Type : adb devices
9. Type: adb shell
10. Type: adb install ( locate were apk is on your pc.... Here is an Example of what ide put: adb install c:/root/nameOf app.apk , then press enter )
11. Type: adb push su /system/xbin or try adb push su /system/xbin/su or try adb push system/xbin/su /system/xbin/su
12. Use the following command to add the correct permissions to the su binary on the device adb shell chmod 6755 /system/bin/su
13. Adb reboot
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

I'll try when I get ack home tonight,
thanks for this

avid.aria said:
I'll try when I get ack home tonight,
thanks for this
Click to expand...
Click to collapse
Download a ruu to be on the safe side too... There's 2 ways on how you could root
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

Reserved

Another reserved

Hope this helps everyone

Not working
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.

8trix said:
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
Click to expand...
Click to collapse
Me and you will work on finding a way
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

but there is no support for unlocking the bootloader in htc dev , how did you do it ??

Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.

hasoon2000 said:
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
Click to expand...
Click to collapse
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
To unlock the bootloader is easy, its like any other htc. Go to htc dev site and choose "all other supported devices" and follow the guide. It'll give you the file to fastboot flash to unlock. We're just working on getting root now. HTC definitely did something different with this phone because none of the other methods seem to work. Seems like there are some smart dedicated people working with us so please be patient and keep a watch on this thread!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
24ky said:
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Click to expand...
Click to collapse
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?

flipinfin said:
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
Click to expand...
Click to collapse
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app

jose51197 said:
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip

8trix said:
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
Click to expand...
Click to collapse
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium

jmztaylor said:
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
Click to expand...
Click to collapse
I know this is old and not needed anymore since you're putting up root tomorrow, but I wanted to close this with yes, I did re-lock, and it kind of almost worked, like it finished sending the file, but then errored out with some other bs. No woory now though, I am back to fully stock unlocked and will test your root tomorrow if it's up then. Thanks again jmz, great work!

So... how do I get the UI working again? I'm stuck with an unusable UI ._. !

zeratos said:
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
Click to expand...
Click to collapse
Whats wrong?

None of the methods described on the main post work and I got stuck on the unusable UI, I google how to do a factory reset and now it's working again.
Thanks.
Also, is there a way to root this thing?

HELP - full wiped my phone

_-_

phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/

_-_

adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??

_-_

Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....

_-_

phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj