Related
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
EXT4 recovery
Unlocked Hboot 1.5 s-on
I was running ZR3Dv2.4b smoothly and tried to use boot manager to boot MIUI. MIUI ran fine, but I could not boot back. I tried to flash a new rom and it would still only boot MIUI. It said data, system, and boot are all unmounted? But said image flashed succesfully. I can remount system and data, but no option for boot. Now I cant even boot back to even MIUI. All I get is the HTC screen.
I also tried to download the first posted link for a 2.17 ruu from this thread; http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
Bootloader finished checking it and quickly says wrong zip and brings me back to main bootloader screen.
Please help me us my phone again!
Did you try fastbooting into your recovery. 4ext leaves a copy of the boot.img on your sd card. If you have a sd card reader you should try to extract it, place it on your pc and fastboot into it.
Coming from sense to aosp and back and forth can cause all kinds of headaches.
I tried to get fastboot usb to pop up when i plug the cord in, but it does not. i have htc sync installed so i should have the drivers. i also have not done anything with phones using my pc, always just from the phone. is there a thread that could help me with this? i searched, i always search, first time i couldnt find an answer!
rsgalas said:
I tried to get fastboot usb to pop up when i plug the cord in, but it does not. i have htc sync installed so i should have the drivers. i also have not done anything with phones using my pc, always just from the phone. is there a thread that could help me with this? i searched, i always search, first time i couldnt find an answer!
Click to expand...
Click to collapse
Have you tried a nandroid restore? I believe I've ram across the problem before and my fix was mounting USB I'm recovery and deleting the boot manager folder, hope one of these options helps
****'ll Buff Out
I cant seem to connect my phone to my pc with fastboot usb or with usb storage in ext4 touch recovery. What software and device drivers do i need?
install htc sync and uninstall it I believe...
tried that, still says "windows does not recognize usb device"
I've had this happen on my 4g before. Your boot.IMG is borked. A nandroid restore will fix it.
Next time, click the create phone Rom button several times to ensure it took.
sent from my AnthraX infused Evo3D running Infectedrom Eternity using xda premium
nandroid restore? just a restore from recovery?
I am Now connected with fastboot usb, what do i do now?
rsgalas said:
I am Now connected with fastboot usb, what do i do now?
Click to expand...
Click to collapse
have you installed boot manager in MIUI from play store? You should boot phone ROM from it.
If you get stuck , all you need to do is flash update.zip located in bootmanger/phonerom folder from recovery, if you are s-on you can't flash the update.zip without booting recovery from fastboot or without using 4ext recovery.....
Next time do a little search outside xda too. The boot manager's site has a guide and faqs and solutions too.
if you had setup the zr3d rom with bootmanager, flash the same rom again and flash the update.zip.....see if that works
i cannot boot back into any rom. I tried everything in recovery. no matter what my device hangs on the htc screen.
Why not just reformat your sd after backing it up. Then reflash your recovery. Then do a full wipe and flash a rom.
Sent from my PG86100 using XDA App
I can get into recovery, I can flash images and use it just fine, why would i reflash it? also i flashed it from android so i wouldnt know where to begin to do so.
I have been searching for instructions (with download) on how to relock my bootloader via fastboot connected to a pc. But unable to find what I am looking for. If I can just relock the bootloader sprint will give me a new one.
So now my new problem is please direct me to the files, instructions and commands to relock my bootloader, and of course all the other good stuff.
Thank you all very much for your time spent helping me sort out this issue.
EDIT: I can get my phone to connect via the bootloader in "fastboot usb" mode, Its the PC end where I am lost.
what version of the phone do you have? gsm? cdma? what software version do you have and what hboot and recovery?
Cdma
Unlocked Hboot 1.5 S-on
2.17xxxxxx
Ext4 Touch Recovery
I just tried to flash a 2.17 exe from the pc via fastboot and it failed.
rsgalas said:
Cdma
Unlocked Hboot 1.5 S-on
2.17xxxxxx
Ext4 Touch Recovery
I just tried to flash a 2.17 exe from the pc via fastboot and it failed.
Click to expand...
Click to collapse
here... take this file im sending you and download it and save it in the same folder as your fastboot and adb files and once its saved there start your phone into the bootloader... the part where you get it to say fasyboot usb... then go to your computer and PM me from three ill give you further instructions to fix it and then relock it if you choose to
You don't flash an exe you run it from your pc while your phone is plugged in and on charge mode only. Also make sure usb debugging is checked. Also the reason why I suggest to flash a new recovery or reflash your current recovery is that sometimes recoveries can become corrupt. Just because you can flash doesn't mean your recovery is functioning the way it should. So rather than try to figure out if your recovery is corrupt it takes like 5min to reflash it. That way you rule out your recovery as being the culprit.
#Root-Hack_Mod*Always\
Messaged you wflotus.
Well I am sitting here in fastboot usb via the bootloader with no knowledge of how to flash, unlock/lock, or what to do now for anything via fastboot usb.
EDIT: To rule out that its not my recovery, how do I flash ext4 or cwm from recovery or fastboot?
Windows 7
I got it now.
Finally found the sdk.
fastboot oem lock.
Bootloader took my 2.17 Ruu
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
[SOLVED] Help Needed for Updating to 4.4.2: "htc_fastboot.exe has stopped working"
Hi Developers
I have a SIM-unlocked AT&T HTC One (32GB, completely stock, Android 4.3, Sense 5, modelid: PN0712000, cidnum: CWS__001, Hboot 1.55.0000, baseband: 4T.20.3218.13, S-ON, LOCKED bootloader). I have been trying to update the OS to 4.4.2 but I failed every time. Here's a list of what I did so far:
1. I tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2_2.exe. It starts OK but when it reaches 5%, an error "htc_fastboot.exe has stopped working" appears and the process is terminated. I have tried this on three different PCs (all with Windows 7 and proper drivers installed, adb and fastboot working) and all of them showed the same error. Suprisingly, RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe runs just fine and I can reflash the 4.3 using it without any trouble.
2. I tried flashing the OTA update.zip via stock recovery by copying the update.zip on the phone storage, rebooting into recovery and selecting "apply from phone storage". It didn't work either. I failed to catch the error message showed on the recovery screen as it was very quick to exit recovery and start the phone in normal mode.
3. I extracted the rom.zip from the RUU.exe and tried to flash the rom.zip from fastboot using "fastboot flash zip rom.zip". It also starts to work but after some time (around 220 seconds) it shows "12 signature verification failed" error.
Could anyone please let me know how can I update my OS to 4.4.2? Thanks in advance.
OK, after two days of constant searching, I have found a solution to update the AT&T HTC One to Android 4.4.2 (Sense 5.5) from Android 4.3 (Sense 5.0). Here's what I had to do. I started from complete stock Android 4.3 (OS version 3.17.502.3), S-ON, bootloader locked.
1. I unlocked the bootloader by collecting the Unlock_code.bin file from htcdev.com.
From Settings > Power, uncheck the "Fast boot". Then turn off your device. Wait for a few seconds. Turn on the device with the volume down button pressed. This will take you to bootloader mode. Using the volume up/down keys, select FASTBOOT and connect your device to your PC using a USB cable. On the device screen, you should see FASTBOOT USB.
Now open a terminal window on your PC (I am assuming you have adb and fastboot installed. If not, search Google for "Minimal ADB and Fastboot" and install it). Type the following command:
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device screen, you will have to choose YES using the vol up/down keys and Power button. This will unlock your device's bootloader and wipe your device completely. Your phone will reboot.
2. I flashed a custom recovery for rooting the device.
Download your favorite recovery. I used twrp-recovery-2.7.0.4b-m7-20140408.img.
Enter the bootloader mode again as described before. In the terminal windows, write the following code to flash the custom recovery:
Code:
fastboot flash recovery twrp-recovery-2.7.0.4b-m7-20140408.img
Now reboot your device. Download your favorite SU binary zip and copy it to your phone. I used UPDATE-SuperSU-v1.65.zip.
Turn off your device and enter bootloader mode again. It should show TAMPERED and UNLOCKED but S-ON now.
Select RECOVERY from the bootloader menu. This will reboot the device into TWRP recovery. Navigate to the SU zip file and flash it. Upon completion of the flash, wipe cache.
3. I used rumrunner to get S-OFF.
Now that we have a rooted device, we can use rumrunner. Download rumrunner_HTC_0.5.0.zip. Extract it. Connect your phone (turned on) to the PC and enable USB Debugging from Settings>Developer Options. On your PC, from the extracted rumrunner folder, run the sojo.exe in administrator mode.
For rumrunner to run, you need to be connected to the internet (I don't know why). Also, the process will be easier if you - a) turn off all screen securities, b) connected your device to the PC in adb mode and fastboot mode at least once before running rumrunner (this will ensure if you have proper drivers installed or not). It will take some time for rumrunner to get S-OFF. Your device will reboot many times, don't worry, this is normal.
So, now we have a tampered, unlocked, S-OFF device.
4. I returned to Stock 4.3 ROM using RUU.
Relock your bootloader using the following command:
Code:
fastboot oem lock
I used the RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe to return to stock. This RUU didn't give any "htc_fastboot.exe stopped working" error and ran smoothly every time. This will remove the "Tampered" sign, but your S-OFF will be as it were. This is what we wanted in the first place. A complete stock firmware/ROM with S-OFF.
5. I flashed the OTA.zip using stock recovery.
Now, download the 4.4.2 OTA zip file and place it in your phone storage. Reboot the phone in bootloader and then recovery mode. Clear cache from the stock recovery and then select "apply from phone storage". Navigate to the OTA.zip file on your phone and select it. After it completes the flashing process, do a factory reset from the recovery or the bootloader mode. Now, you should have a stock HTC 4.4.2 device with Sense 5.5, locked bootloader and S-OFF.
hafizimtiaz said:
OK, after two days of constant searching, I have found a solution to update the AT&T HTC One to Android 4.4.2 (Sense 5.5) from Android 4.3 (Sense 5.0). Here's what I had to do. I started from complete stock Android 4.3 (OS version 3.17.502.3), S-ON, bootloader locked.
1. I unlocked the bootloader by collecting the Unlock_code.bin file from htcdev.com.
From Settings > Power, uncheck the "Fast boot". Then turn off your device. Wait for a few seconds. Turn on the device with the volume down button pressed. This will take you to bootloader mode. Using the volume up/down keys, select FASTBOOT and connect your device to your PC using a USB cable. On the device screen, you should see FASTBOOT USB.
Now open a terminal window on your PC (I am assuming you have adb and fastboot installed. If not, search Google for "Minimal ADB and Fastboot" and install it). Type the following command:
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device screen, you will have to choose YES using the vol up/down keys and Power button. This will unlock your device's bootloader and wipe your device completely. Your phone will reboot.
2. I flashed a custom recovery for rooting the device.
Download your favorite recovery. I used twrp-recovery-2.7.0.4b-m7-20140408.img.
Enter the bootloader mode again as described before. In the terminal windows, write the following code to flash the custom recovery:
Code:
fastboot flash recovery twrp-recovery-2.7.0.4b-m7-20140408.img
Now reboot your device. Download your favorite SU binary zip and copy it to your phone. I used UPDATE-SuperSU-v1.65.zip.
Turn off your device and enter bootloader mode again. It should show TAMPERED and UNLOCKED but S-ON now.
Select RECOVERY from the bootloader menu. This will reboot the device into TWRP recovery. Navigate to the SU zip file and flash it. Upon completion of the flash, wipe cache.
3. I used rumrunner to get S-OFF.
Now that we have a rooted device, we can use rumrunner. Download rumrunner_HTC_0.5.0.zip. Extract it. Connect your phone (turned on) to the PC and enable USB Debugging from Settings>Developer Options. On your PC, from the extracted rumrunner folder, run the sojo.exe in administrator mode.
For rumrunner to run, you need to be connected to the internet (I don't know why). Also, the process will be easier if you - a) turn off all screen securities, b) connected your device to the PC in adb mode and fastboot mode at least once before running rumrunner (this will ensure if you have proper drivers installed or not). It will take some time for rumrunner to get S-OFF. Your device will reboot many times, don't worry, this is normal.
So, now we have a tampered, unlocked, S-OFF device.
4. I returned to Stock 4.3 ROM using RUU.
Relock your bootloader using the following command:
Code:
fastboot oem lock
I used the RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe to return to stock. This RUU didn't give any "htc_fastboot.exe stopped working" error and ran smoothly every time. This will remove the "Tampered" sign, but your S-OFF will be as it were. This is what we wanted in the first place. A complete stock firmware/ROM with S-OFF.
5. I flashed the OTA.zip using stock recovery.
Now, download the 4.4.2 OTA zip file and place it in your phone storage. Reboot the phone in bootloader and then recovery mode. Clear cache from the stock recovery and then select "apply from phone storage". Navigate to the OTA.zip file on your phone and select it. After it completes the flashing process, do a factory reset from the recovery or the bootloader mode. Now, you should have a stock HTC 4.4.2 device with Sense 5.5, locked bootloader and S-OFF.
Click to expand...
Click to collapse
Thanks for posting your solution ... Sorry I have been absent. I have been Busy with work
clsA said:
Thanks for posting your solution ... Sorry I have been absent. I have been Busy with work
Click to expand...
Click to collapse
Thanks
Thank you, Hafizimtiaz!!! Finally, I'm the lastest OTA with Sense 6!
Unfortunately I am facing this issue on both Win 8 and a brand new Win 7 too. I have no clue how to run the RUU. I used to use this same PC for RUU in the past. Now I get this error of HTC_fastboot.exe has stopped working. Any help appreciated.
fareed_xtreme said:
Unfortunately I am facing this issue on both Win 8 and a brand new Win 7 too. I have no clue how to run the RUU. I used to use this same PC for RUU in the past. Now I get this error of HTC_fastboot.exe has stopped working. Any help appreciated.
Click to expand...
Click to collapse
you need the older 3.x.502.x RUU
you can download it directly from HTC here >>
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
Hi I unlocked my bootloader and flashed TWRP recovery and den tried flashing custom ROM. after flashing it gets rebotted n gets stuck at HTC logo. Im really worried. I tried pushing another ROM thru adb MIUI/CM n tried flashing.. Flashing shows succesful but gets stuck at HTC logo.
I have my backup of stock ROM in my PC but since i cant connect my mobile to pc i dont know if I can transfer my backup to mobile. Also I dont have sdcard slot so cant try that option too..
Please helo:crying::crying::crying::crying::crying::crying::crying:
you have to flash the correct kernel,too. read here: http://forum.xda-developers.com/showthread.php?t=2066390
you need cwm recovery http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-enrc2b.img to flash cm11, twrp wont work
Cant find RUU for my device
crusader727 said:
you have to flash the correct kernel,too. read here: http://forum.xda-developers.com/showthread.php?t=2066390
you need cwm recovery http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-enrc2b.img to flash cm11, twrp wont work
Click to expand...
Click to collapse
I shall be trying this for sure once I go home. But today I tried one more method found from link
But the problem here is I can't find the RUU for my device. After fastboot OEM lock , it shows the following
Details as follows:
ENRC2b_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-NONE
MICROP-NONE
RADIO- 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
Modem path : OFF
So what I understand is I need RUU as per Radio-3.1204.171.33 which I'm not able to get , any1 please suggest the solution.
Now since I have relocked my device I will have to unlock my device again , Flash Custom Recovery , SuperSu , Den Flash ROM/Kernal.
Instead of the method mentioned above is there any solution to go back to my old version with RUU. If yes provide me link of RUU for my verison
http://badandmadstudio.wordpress.com/guides/htc-one-x-flash-back-2-stock/
If you need to Flash your phone back because it is stuck at the ‘HTC quietly brilliant’ and not booting, you might be interested in this guide.
I had a long and painful way of googling and complaining about the fact, that HTC One X has everything and One X+ is never mentioned. However i found a solution. I will repeat everything here for beginners.
At first you might have waited about 30 mins or something like that for the device to boot, so maybe the battery is going to be over 30% which will be necessary. Maybe it’s not possible to load the device normally. Don’t panic there is a stupid way to do this.
Loading with laden.bat (which means loading)
You will need these downloads:
laden.bat, adb-tools
Extract the adb-tools folder found in the downloaded zip-file to your hard drive c:\.
Put the laden.bat into this folder. laden.bat should be in the same folder as fastboot.exe.
Go to command line by Start > write: ‘cmd’.
Use ‘cd..’ & ‘cd adb-tools’ to get to the ‘c:\ads-tools’ folder.
Boot your phone to FASTBOOT: press power & sound down, hold sound down until bootmanager appears -> select FASTBOOT
Connect your phone via USB
Now on the phone you can read blablabla… USB
Start the laden.bat
Now the phone will restart the whole time, and the battery loads during the time from start to bootmanager screen.
Please check the mV shown in the console, if they don’t go up to (3800-3900 mV) stop the procedure and check USB connection.
Relock the device
If your device is rooted, the boot loader was unlocked and this might be a problem so we relock it in this step.
HowTo:
Turn the device off
start to FASTBOOT like before
connect to PC via USB
go to command shell and switch to the adb-tools directory (like above)
in the directory you start fastboot.exe by -> ‘fastboot oem lock’
Reboot -> take a look in boot loader (at the top) if the device is now *relocked*
Using RUU’s to flash back the Firmware
You can find some RUU’s here.
I used the RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1 204.168.32_release_299688_signed.exe file.
This is a simple procedure:
Connect the device via USB
Your device has to be in FASTBOOT mode
Just install the exe File and follow the instructions on the screen.
:crying::crying::crying::crying::crying::crying:
stop spamming all threads pls...
unlock your phone again.
flash cwm linked above
download cm11 on your pc and extract boot.img (kernel)
flash boot.img
go to recovery and look for sideload
transfer cm11 from your pc using adb sideload and flash it