Related
Ok, here's the procedure for returning to stock S-ON after running revolutionary if required for warranty reasons.
Preparation
(Windows): Uninstall HTC Sync and any other sync software ( eg Androsync ) that you have been using.
(Windows) : Install these fastboot drivers
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
Download the RUU for your device
Download the downgrade hboot for your device:
Flyer downgrade hboot MD5SUM=6f82c00e2029c4bf3cb00e861789e2f8
View downgrade hboot MD5SUM=d3462b3587564db133c2215127485fe4
Check the mdsum of your download
Check the mdsum of your download
Reboot to to fastboot mode
Flash the downgrade hboot
Flyer:
Code:
fastboot flash hboot flyer_downgrader.nb0
View:
Code:
fastboot flash hboot express_downgrader.nb0
Run the RUU for your device
I can't use adb on recovery mode. Can you upload your fastboot driver?
buidung said:
I can't use adb on recovery mode. Can you upload your fastboot driver?
Click to expand...
Click to collapse
1. Yes, you can use adb in recovery mode if you followed the instructions correctly.
2. Done
an system's update
...can be installed if i use this procedure?
I get an error
C:\Users\Namit>fastboot flash zip RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204116_signed.zip
sending 'zip' (500195 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 157.279s
Click to expand...
Click to collapse
EDIT1: Just moved the zip to sdcard as PG41IMG and went into bootloader. It is working right now; will report on results.
EDIT2: Worked! Flashed Radio and rebooted to finish the rest of the installation.
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
chong5379 said:
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
Click to expand...
Click to collapse
It is something like hboot_xxxxx.nb0
I try to flash the stock recovery by fastboot on my Htc View but not success. It shows "failed, signature .... Bla bla". My device is still s-on and hangs at htc screen. Hmm, I think its recovery partition was damaged and RUU can't overwrite another recovery.img on it. Can someone help me out ? Thanks
Namit1994 said:
It is something like hboot_xxxxx.nb0
Click to expand...
Click to collapse
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Hello there,
I'm really desperate as I have this problem and I hope someone could help me, I'd be really grateful.
My following problem is :
I have an HTC FLYER and I tried to flash a new hboot FROM HERE ( http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 ) but mistakenly it was from another device, now my FLYER wont turn on at all.
Can someone help me how to flash a new hboot so my device can finally power up ? Please I really need my HTC FLYER to start working.
I tried running ADB and "adb devices" but my device serial doesn't how in the list of attached devices and i don't know neither how to flash the new hboot through adb.
Please I'm really desperate, I hope someone can help me . I'm really afraid my Htc Flyer is dead.
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
hm
globatron said:
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
Click to expand...
Click to collapse
yes but its bought in sweden and now i live in balkans so no warranty for me and i was thinking if i can fix it with some box method like jtag jig?
I motion that this thread either be stickied or combined with the S-OFF sticky thread.
hboot_1.11.0003.nb0
chong5379 said:
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Click to expand...
Click to collapse
It was hboot_1.11.0003.nb0 in my case.
It can be either, mostly it will be .nb0 but it can be a .img. The important thing is that it is hboot not boot.
Where i can find RUU for my 3g flyer.
Now I use Leedroid rom i want to go back to official 2.3 to wail for official 3.2.
When or where?
Sent from my HTC Flyer P510e using xda premium
Where is can download RUU for my 3g flyer
^_^
I will correct my post
Thz
hi,
I updated to honeycomb using your method, but my tablet is now slower so I wanted to revert back to gingerbread.
The problem is I can't use ADB commands with it. It responds to fastboot commands but doesn't respond to adb commands. It shows: Error: device not found.
I have tried to put the rom.zip in the sd card, which seems to install gingerbread back, but it won't boot.
What can I do? I am desperate now.
Reflash honeycomb before you run out of battery
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.
Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.
Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.
Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...
UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:
sending 'zip' (913111 KB)...
OKAY [ 35.667s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 118.073s
Click to expand...
Click to collapse
I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Phaded said:
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Click to expand...
Click to collapse
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.
Is there a way to get s-off without ADB (only using fastboot)?
Flash firmware zip located on the moonshine thread, then use moonshine
Phaded said:
Flash firmware zip located on the moonshine thread, then use moonshine
Click to expand...
Click to collapse
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
jdpalmer2k13 said:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
Click to expand...
Click to collapse
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
I recently flashed the RUU from fastboot.
http://forum.xda-developers.com/showthread.php?t=2115987 post#4
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
bwhxeon said:
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
Click to expand...
Click to collapse
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
jdpalmer2k13 said:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
Click to expand...
Click to collapse
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
bwhxeon said:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
Click to expand...
Click to collapse
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Phaded said:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Click to expand...
Click to collapse
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19
Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
jdpalmer2k13 said:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
Click to expand...
Click to collapse
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
Try this please
fastboot oem readcid
What's it say?
Phaded said:
Try this please
fastboot oem readcid
What's it say?
Click to expand...
Click to collapse
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
PiperBen85 said:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
Click to expand...
Click to collapse
Yep same here
jdpalmer2k13 said:
Yep same here
Click to expand...
Click to collapse
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Phaded said:
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Click to expand...
Click to collapse
Yes, I am locked. Here is the result of trying to writecid:
Code:
C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
pourya-man said:
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
Click to expand...
Click to collapse
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
pbergonzi said:
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
Click to expand...
Click to collapse
thank's :laugh:
CID is HTC__044
Which RUU do I get?
pourya-man said:
thank's :laugh:
CID is HTC__044
Which RUU do I get?
Click to expand...
Click to collapse
If you are capable enough to flash your phone, you are capable of searching.
I searched, and without any certainty of what you did do or should do, found this link:
http://forum.xda-developers.com/showpost.php?p=41310223&postcount=135
If this link is helpful to you, be certain to use proper instructions for what you want to do.
Let me repeat that, "Be certain to use proper instructions for what you want to do."
thank my friend . problem fixed
Glad for you--you're getting pretty good at this.
Hello again . i s-off amaze and updated to ics but can't flash recovery
log :
---------------------------------------------------------------------------------------------------------------------------------
E:\Application\Android\Phone\HTC\01 Fastboot>"E:\Application\Android\Phone\HTC\0
1 Fastboot\Flash Recovery.bat"
E:\Application\Android\Phone\HTC\01 Fastboot>fastboot flash recovery recovery.im
g
sending 'recovery' (5502 KB)... OKAY [ 1.264s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.580s
---------------------------------------------------------------------------------------------------------------------------------
hboot is locked . i can't unlock it with Unlock_code.bin file.
What is the solution?
you need to get a new Unlock_code.bin file from htcdev.com, Something has changed older code won't work.
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.