Related
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
reaper24 said:
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
Click to expand...
Click to collapse
Sorry, update the status apologize for the mistakes
Any expertise?
Helpppppppppppppppp pleaseeeeeeeee!!!!!!!!!!!!!!!!!!!!! (((
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
I am having something close to that issue. i have Hboot 1.49.0008 it is Unlocked but with s-On
now i can boot farther then the htc white. mine goes to the htc + quietly brilliant screen. then hits a boot loop.
what are my options and how do i do it?
thanks
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
ok...then what can I do to fetch the data out or save my phone?
Nokiawithandroid said:
ok...then what can I do to fetch the data out or save my phone?
Click to expand...
Click to collapse
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
megabiteg said:
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
Click to expand...
Click to collapse
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Nokiawithandroid said:
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Click to expand...
Click to collapse
You posted this same question in a separate thread: http://forum.xda-developers.com/showthread.php?t=1525176
In an effort to keep the threads organized, I answered in that thread as follows:
Background on system.img: The system partition is generally only distributed in the system.img format for stock system images. Most aftermarket ROMs perfer to distribute their system content in the form of an update .zip file.
Background on bootloader: The system.img can't be flashed until you unlock the device. This is a standard security feature on any device with a "locked" bootloader, as yours shows from the information you posted.
One option: Once the bootloader is unlocked, the command should be as simple as: fastboot flash system c:\system.img
Hope that helps. Good luck!
Click to expand...
Click to collapse
Not sure how many times this can be repeated or how many different ways the same thing can be repeated. Without unlocking the device, HTC will not allow you to selectively modify any of the partitions from the bootloader or fastboot.
With these three conditions:
1) Without unlocking the device
2) Having the device freeze on the HTC splash screen
3) Never having previously loaded a custom recovery
The only option HTC provides is to run the RUU which will return the device to 100% stock erasing all information currently on the device.
If you're able to unlock the device (condition #1), you would be able to either flash a custom recovery (condition #3), or a stock/new system.img which would allow you access to the device where you can retrieving the stored SMS and MMS.
Using the stock RUU should resolve condition #2, if it didn't, there could be a more serious hardware issue with the device.
I might have missed some aspect. I'm sure somebody will post up if I did.
Hope that helps make more sense!
Dear Memeber
i find that my htc legend is un rooted and i need to root it to install a room to it i try many ways i find other the internet and it doesn't success to do it so am look for how and the way to root it
and will be thankful for you
-Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
-Flash ClockworkMod Recovery
-Flash any ROM you want.
These are the basic steps. I might write up an updated, more detailed guide for others when I get back to a computer.
Sent from my Legend using XDA
Go to http://www.htcdev.com/bootloader/
Register, select your device and unlock the bootloader
Get HTC Super Tools from
http://forum.xda-developers.com/showthread.php?t=1343114
Run it, do options 1 and 3, in that order, to root your phone
Get Clockwork Recovery Mod from
http://forum.xda-developers.com/showthread.php?t=1290841
Use 1st step for S-OFF method to install ClockworkRecovery
Boot into Recovery mode and take a backup of your ROM
Download the ROM of your choice and copy it to your SD card
Boot into Recovery Mode, do a data wipe/factory reset and a cache wipe
Select Install from zip in Recovery, navigate to your ROM in SD Card and install it. Hope this helps.
This is a long process, at least for the first timers. You may get stuck at various places, please let us know if you do
Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
i download this two items and i try to root it but it dosen't work with me or maybe i did something wrong
what is the steps that i have to follow by using them
and thanks for your replies
Regards
sometimes it says like this
C:\Android>fastboot oem get_identifier_token
< waiting for device >
...
and it stuck for along time and nothing changed
and other times when i press power button for the fastboot it change to be like this
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Android>fastboot oem get_identifier_token
...
FAILED (status read failed (Too many links))
finished. total time: 4.670s
All I can think of is that you should start again reading every step carefully.
Also, jc36 that's a great guide
Sent from my Legend using XDA
clarify jc36 clockwork recovery mod step
I need to clarify something important for the "Get Clockwork Recovery Mod step which says to follow the 1st step for S-OFF method to install ClockworkRecovery.
On the linked page http://forum.xda-developers.com/show....php?t=1290841
Where it says the following:
"How to use S-OFF user
Download file and move on adb fastboot folder"
Does "move on adb fastboot folder" mean, put the file into the folder? And if so where is the folder?
There is no such folder: "adb fastboot folder"?
Does it mean:
1. put it in the Android folder created (C:\android) to hold the files instructed by HTC Dev for unlocking the bootloader?
2. Or put it in the android-sdk folder, somewhere? May be the Platform Tools folder where adb.exe exists?
Thanks to anyone who can help clarify this step for me
Yes it means put the recovery into the folder with adb.exe and fastboot.exe
Sent from my Legend using XDA
Thanks again
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
xdadufus said:
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
Click to expand...
Click to collapse
Brief is good although I do understand how a noob would want a step-by-step guide. In relation to date, none of the links I gave you were really outdated. The datestamp at the top of the thread might say '6th October 2011, 10:00 AM' but if you look at the bottom of the post it'll say something like 'Last edited by (username); 21st March 2012 at 09:32 AM' on threads/posts that get updated. Welcome to the Legend forums!
Further Clarification
I am continuing with my quest to clarify and document the whole jc36 procedure accurately.
1. After you have unlocked the bootloader are there any mode changes to be made before running SuperTools?
2. After running SuperTools, following the 1st step for S-OFF Clockwork Recovery Mod how do you put the phone into "fastboot" mode? Does the phone have to be disconnected again, powered down, restart with volume held down, highlighting Fastboot then press Power button and reconnecting to computer? Is this the procedure or is there another way while it still connected to the computer?
3. Continueing with Clockwork Recovery Mod code where it says:
"In fastboot mode:
Code:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img"
I'm guessing the code above is for command prompt for the c:\android directory as done previously for HTC Dev unlocking of the bootloader?
Open up command prompt. ( Start> Run> Type CMD,).
Command Prompt: cd c:\Android)
Type in Command Prompt:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img
Correct?
4. After completing Clockwork recovery Mod it says to "Boot into Recovery mode and take a backup of your ROM" -- again do you disconnect the phone to do this and boot into the bootloader to select Recovery mode? And how to you backup? Is it to an SD card or is the phone connected to the computer to take the backup to your hardrive?
Thank you to all in advance who take the time to go over these questions.
1. By mode changes I'm assuming you mean something like enabling USB debugging which is definitely recommended.
2.You get into fastboot mode by rebooting into the bootloader (Hold volume down+trackball+power button). Fastboot is the first selected option so all you have to do is press the power button to choose it and then it will go into fastboot mode
3.Yes in command prompt you navigate to the folder that has adb.exe, fastboot.exe and the recovery image and then carry out those commands
4.If you've flashed a ROM that supports it then in phone options(hold down power button) you can select Reboot and then Recovery. Otherwise to get to recovery you would have to go through the bootloader. To backup you go to Backup and Restore in CWM and select Backup or alternatively you can use ROM Manager to do a backup. The phone doesn't have to be disconnected and the backups are made to the micro SD Card.
Sent from my Legend using XDA
run in to trouble at the beginning
I have run into an error with the command provided with HTC Dev Unlock Bootloader.
I have followed all instructions very carefully. When in command prompt I get this error after entering:
fastboot oem get_identifier_token
...
<bootloader> [ERR] Command error !!!
I am in the android directory in c:\android and have the three files there:
adb.exe
adbWinApi.dll
fastboot (which I extracted from an older version of SDK as instructed by HTC because it doesn't exist in the latest SDK software)
Is your phone connected with USB Debugging on and HTC drivers installed on your computer?
bootloader now unlocked successfully
I just flashed the RUU that HTC Dev recommended for my phone, the version it should have before attempting to unlock the bootloader.
My phone originally had this updated version anyway so I never updated it on my first attempt.
After reading the forums here for people having similar issues I flashed their recommended RUU for the Legend and from that point on the command in command prompt worked. I have now unlocked the bootloader ...
what about gapps?
I finally rooted my phone and flashed cm7.2 ROM successfully after some nail biting experiences... it is not as simple as the instructions posted earlier in this forum make it appear... There were some issues I ran into. I will post an explanation of how I resolved them soon.
What good is a new android ROM without essential Google apps? I know they are not packaged due to licensing but I can not find a reasonable explanation of how to get them on my phone. I thought it would be simple but it is not. Right now I can not download any apps...
I read the gapps packages should be installed during the flashing of the ROM... that point is missing from the instructions here! So what now? Do I have to run through the process of flashing the ROM again along with the gapps package this time?
I tried installing the latest Google Play app but it would not connect to the server -- whatever that means -- after entering in my google account.
Is there any way to get the apps downloaded directly to my computer so I can copy them to the SD card? I did find a couple of solutions to do this but you need to enter google account details and some id number for the phone which I can not find... what is the identifier for the phone and where?
Any assistance on this would be greatly appreciated because at this point the whole new fresh ROM is useless...
You can flash GApps at any time. Whether it's during installation, right after first boot, or years later. Make sure you flash the appropriate .zip.
You can use APK Downloader to get them straight from the Play Store to your computer in .APK format.
http://codekiem.com/2012/02/24/apk-downloader/
All the latest Gapps packages can be found here. Use the 'gapps-gb-20110828-signed.zip' package if you're running Gingerbread and 'gapps-ics-20120429-signed.zip' if you're running ICS.
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
icanttinkofaname said:
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
Click to expand...
Click to collapse
You do see the words "locked"? that means its "locked" you need to follow the steps provided by htcdev in the email they would have sent you including the unlock.bin file with out those steps you can't do anything, its like its still not rooted.
Sent from my Legend using XDA
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
Credits go to @nlooooo for starting this thread!
WARNING
I’m not responsible for bricked devices, all you do is on your own responsibility. Most of the processes I’ll mention will work with some vital parts of your phone, so if you don’t have enough courage or until you don’t understand all the things you should do I recommend not to get involved with this.
Click to expand...
Click to collapse
Ok, there's a tool for almost all of that. Tool is updated, but you need to be sure to click the button for the right recovery, explanation below.
1. UNLOCKING OF BOOTLOADER
Everything starts with this. Unlocking of bootloader will allow you to make changes to some critical partitions of your phone (boot, system and recovery) and will allow you to flash custom recovery that can be used for installing of custom roms, mods and all kind of flashable zips. However, it won't s-off your phone, and other critical partitions (bootloader, radio) remain inaccessible.
So, I won't explain how to do that. Why? Because if you successfully unlock bootloader on your phone it means that you received enough knowledge for the rest of the process and you're qualified to go further.
This process will factory reset your phone (erase data partition) so backup your stuff before you proceed.
Ok, now go to htcdev.com, register your account, go to unlock bootloader section, for the device choose 'All other supported models' and follow the instructions carefully everything is explained in details. Pay attention to 'Required resources' on the first page after confirmation - you need Android SDK platform tools Java Runtime Environment and HTC Sync installed and there are all needed links. Files mentioned in step 5 you will find in Android Bundle zip you downloaded in folder adt-bundle-windows-x86_64\sdk\platform tools.
Here are some useful links about Android SDK platform tools, you won’t be needing most of it but it won't be bad to read.
http://developer.android.com/tools/help/adb.html
http://android-dls.com/wiki/index.php?title=ADB
http://android-dls.com/wiki/index.php?title=Fastboot
http://wiki.cyanogenmod.org/wiki/fastboot
Remark: once unlocked bootloader can be relocked but can never be locked again. This can be done issuing command from fastboot:
fastboot oem lockThis means that on the top of you bootloader screen you’ll have a sign RELOCKED instead of LOCKED, which is a notice to HTC that you unlocked it once. Plus they have data about all users that requested unlock_code so they can deny your warranty whenever they want.
If you’ve successfully unlocked your phone bootloader we can proceed to the next step.
Click to expand...
Click to collapse
2. CUSTOM RECOVERY INSTALLING
- Go to this address:
http://forum.xda-developers.com/showthread.php?t=2502327There you can find custom recoveries for DesX. Some of them have a few bugs but they are generally functional. Download one of your choice, rename it to recovery.img and put it on the root of c: drive on your PC. Before downloading, read the thread linked to carefully, as it is important to check your hboot before installing a custom recovery.
Remark: you can use recovery image provided in WindyCityRockr's tool.
- Go here:
http://download.chainfire.eu/370/SuperSUdownload SuperSU, connect your phone to PC and put it somewhere on your phone sd card.
- Do not disconnect your phone from PC, reboot phone to fastboot on one of this ways :
1. choose restart from power menu and when the screen comes off wait for the buttons to turn off and immediately push volume down, the phone will boot to bootloader, then select fastboot from bootloader menu
2. issuing command
adb reboot-bootloaderfrom command prompt that will take you directly to fastboot
- once you’re in fastboot mode open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
The second and third commands are not quite necessary but they don’t harm and leave your phone with no trails of previous recoveries. Now you can disconnect your phone from your PC.
Click to expand...
Click to collapse
3. BACKING UP STOCK ROM
Now it is really important to backup your stock ROM. Dependent on your CID and hboot version, you can't use RUU to get back to stock, especially if your phone is branded by your carrier. Also, RUUs are only available for ICS bootloader (hboot 1.24 and lower). For JB there are only nand backups for a few CIDs uploaded by some nice xda members. So if you definitely want to be able to get back to stock any time, you'll have to backup your current configuration first. That's done by:
Reboot your phone to recovery
Backup -> Select all partitions -> Swipe to BackupThat will take some time. After that's finished, you should make a copy of that backup somewhere safe (it's located on the sdcard in folder TWRP, just copy the whole folder somewhere).
Click to expand...
Click to collapse
4. ROOTING YOUR PHONE
- From fastboot menu choose bootloader and then recovery to reboot phone to recovery
- If you successfully boot to recovery choose options:
Install zip from sd card
Choose zip from sd cardNavigate to UPDATE-SuperSU-vx.xx.zip you stored on sd card and choose it. Once the installation is finished reboot your phone. Now you should see SuperSU app in app drawer and your phone is rooted.
Click to expand...
Click to collapse
5. CUSTOM ROMS INSTALLING
There are already quite a few ROMs available for our device. But watch out... many of them are discontinued, mostly the CM ROMs as well as the ROMs based off CM. Go here for the index:
http://forum.xda-developers.com/showthread.php?p=35735267#post35735267That’s the Index thread I created for all user to track development for our device. There you’ll find roms that can be installed.
I have to emphasize that every chef gives an instruction how to install his rom, so here I’ll just give you the basics for custom rom installing using custom recovery.
- Download the rom of your choice and put it on the sd card of your device
- Unpack boot.img from rom.zip and put it on the root of c: drive on your PC
- Reboot phone to recovery
- Choose option ‘wipe data/factory reset’
- Choose option ‘wipe cache partition’
- Choose option ‘advanced’ and in next menu choose ‘wipe dalvik cache’
- Go back to main menu and choose ‘install zip from sd card’ and then ‘choose zip from sd card’
- Navigate recovery to rom zip you put on sd card and choose it
- Wait until the installation is finished
- Reboot your phone to fastboot and connect it to your PC
- Open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash boot c:\boot.img
fastboot reboot-bootloader
fastboot erase cache- Reboot your phone
The last few steps are needed since there is no way to s-off our device, so boot.img included in rom.zip has to be flashed separately via fastboot.
Remark: don’t ever forget for the golden rule of flashing ‘Always make a nand backup before you flash something'.
Click to expand...
Click to collapse
6. S-OFF
As S-OFF makes your device vibrating 7 tmes on each boot, you should really think about if you need it. If you are not sure about it, then it's not for you. If you still want to do it, go here:
http://forum.xda-developers.com/showthread.php?t=2630531
http://forum.xda-developers.com/showthread.php?t=2667156Use the first link to get to the files needed to do your S-OFF. In the second link you'll find the things you can do after the S-OFF procedure including downgrading the hboot in order to install RUUs etc.
Click to expand...
Click to collapse
Ok, I did what I had promised, all suggestions and corrections are more than welcome.
All this came as 2 years experience with HTC phones (had Desire and Incredible S before), unlocking, rooting and taking their guts out .
Sources and links posted:
- HTC Developers site
- WinDroid HTC Desire X Toolkit v2.1 made by WindyCityRockr
- Android Developers site
- Cyanogen Wiki site
- SuperSU made by Chainfire
- Thanks to ckpv5 for nand ICS backup thread
- Thanks to Izzy Stinson for pointing me to things not explained enough
- Sources for recoveries can be found in my recovery thread
- Thanks to GtrCraft for the idea to include the backup of stockrom
- Thanks to nightwalkerkg and the rumrunners team for getting us the S-OFF
- Again thanks to ckpv5 for the S-OFF tutorial
Going back to stock for official update
Now to say more about a reverse part. The point of this is to make your phone available for official updates, and make it possible to do. Thanks to Ranalakshay36 and Bedroom we have information that you can apply OTA without need to relock bootloader on the phone. However, relocking is still mandatory if you want to install a fresh new rom using RUU.
The first important thing for this is: PEOPLE, MAKE A NAND BACKUP OF STOCK ROM BEFORE REMOVING OF ANY APP FROM SYSTEM OR INSTALLING A CUSTOM ROM!!! This will make this process much easier to do.
RECEIVING AND OFFICIAL UPDATES INSTALLING
Part one:
Ok, you just unlocked bootloader and rooted your phone (no custom rom installed), but you received a notification that you have an official update available and you want to install it. No problem at all if you didn't touch the apps on system partition (some of them are necessary for official support), and all you have to do are these 2 things:
1. Reinstall stock recovery - I attached it. Remember the part about custom recovery? The process for this is the same:
- download recovery I attached, rename it to recovery.img and put it on the root of c: drive on your PC
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
Now your phone should be ready to apply official update.
Click to expand...
Click to collapse
Part two:
1. You installed a custom rom, however you made a nand backup of your intact stock rooted, so all you need is to restore your nand backup and go to "Part one", that will do a thing.
2. You installed a custom rom, however you didn't make a nand backup of your intact stock rooted, or you deleted some important files from system partiton. So, you're almost scre**d. I said almost because you can ask some of your geeky friends to borrow you his nand backup that you can use for restore.
The best option is to revert back to stock using RUU, but that's currently limited only for devices with Europe based firmware. Here is the thread I made where you can find info about 1.18.401.1 RUU and CID compatibility and a way to check CID of your phone to make sure you can use it:
Get CID and RUU 1.18.401.1 Compatibility
RUU Download page
To run RUU you need to relock your bootloader. This is how you can do it:
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue command
fastboot oem lock- the phone should restart automatically and you'll have a sign RELOCKED on the top of bootloader screen.
After you successfully relock bootloader you can run RUU directly from fastboot. With earlier HTC models there was I a way to bypass CID checking and use any RUU to revert back to stock using a GoldCard, but someone told me that it's not possible with Desire X.
Remark: once you relock bootloader it can be unlocked again in the same way you did it for the first time, and, of course, it will factory reset you phone. Also, going in this order is mandatory, cause if you relock bootloader before you flash stock recovery, you won't be able to do that with relocked bootloader
Click to expand...
Click to collapse
If you can't run a RUU because of incompatible CID, you have to have a nand backup ready for restoring or else to find one in the forums. Here is a thread with different nand backups incompatible from the RUUs:
ICS nandroid backups
Follow the instructions in the above thread to restore your backup.
Click to expand...
Click to collapse
Credits:
- Cobje - stock recovery img from latest update (1.18.xx)
http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
- Ranalakshay36 and Bedroom for the intel.
Reserved once more...
Nice on nlo, will hopefully stop alot of the questions
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
nightcrow said:
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
Click to expand...
Click to collapse
Thanks, forgot about that while I was writing all this stuff.
I can imagine it's quite a story
Anyway well done and it will definitely be useful to the ones that are about to dive into the rabbit-hole.
thanks for the tutorial! very easy to understand and very simple. :good::good::good:
thanks for the tutorial! nice Job men.:good:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
ayyu3m said:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
Click to expand...
Click to collapse
When an English gentleman says that's an easy use of English I somehow get delighted...
Updated, added flashing boot.img via fastboot for custom roms installing.
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
AxR979 said:
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
Click to expand...
Click to collapse
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
nlooooo said:
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
Click to expand...
Click to collapse
it worked !! thx
any idea how to keep the changed font after restarting ? it appears the system revert any change i do
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Izzy Stinson said:
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
nlooooo said:
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
Click to expand...
Click to collapse
thanks. and one last question. you gave 3 links to download for cwm recovery. which of those three are the best cwm for you?
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
nlooooo said:
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
Click to expand...
Click to collapse
so i guess im gonna download clauddy cwm then.
so it is CWM-protou.img, i should rename it to recovery.img right?
sorry for asking so many questions, i dont like to make mistakes when doing this kind of things.. :silly:
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app