Related
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
koty2012 said:
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
Click to expand...
Click to collapse
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
LesbianSeagull said:
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
Click to expand...
Click to collapse
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Bizarre1 said:
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
Click to expand...
Click to collapse
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
LesbianSeagull said:
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
Click to expand...
Click to collapse
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
*Edit: I believe the drivers will install if you install HTC sync. Unfortunately I cant post the link to it, but just do a Google for HTC Evo 3D drivers. It's on HTC's website
koty2012 said:
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Click to expand...
Click to collapse
PM'd and thanked
Bizarre1 said:
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
Click to expand...
Click to collapse
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Click to expand...
Click to collapse
That's really strange. Just to make sure you have the right drivers, go to Control Panel and then to Device Manager and see if your phone is there. It should be under "Android USB devices" or the like. Also, is USB debugging on before the going into hboot?
*Edit: Some more little things, HTC Sync should be uninstalled from your computer, and your phone should be locked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
laie1472 said:
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I used the instructions and download links from androidadvices(dot)com/update-htc-evo-3d-cdma-leaked-ics-403-firmware/. Reading the instructions now I see that I didn't put the phone into USB recovery mode. I can't get back into the ROM to do so and I can't get into my recovery either.
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
iTzLOLtrain said:
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
Click to expand...
Click to collapse
I'm trying that now. Hopefully it works!
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
LesbianSeagull said:
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
Click to expand...
Click to collapse
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
koty2012 said:
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
Click to expand...
Click to collapse
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
LesbianSeagull said:
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
Click to expand...
Click to collapse
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Bizarre1 said:
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Click to expand...
Click to collapse
Tried it, still gave me the signature verification error. I think it's because the bootloader is locked.
bump
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
LesbianSeagull said:
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
Click to expand...
Click to collapse
You have to be unlocked to flash the recovery image. Does it not say its unlocked at the top of HBOOT after using the HTC method?
Sent from the mobile paperweight itself!
****ORIGINAL POST****(REWARD CLAIMED ALREADY)
So here's the deal. I was running cm10 a few days ago and was having a lot of issues with 3g/4g not working and things just being buggy in general. So i decided i wanted to go back to stock since the new jb update was released. I was s-on so i knew it would be a little tricky. So here's what i did. I installed the stock rooted version of the rom, flashed boot.img and all that got the latest stock rom working fine. However, I was still getting really weird issues with 3g/4g dropping and not connecting (even when areas with good signal) so i looked at my radios (which i can't recall ever updating) and decided they would require an update. Since i was s-on this can only be done through the ruu which essentially takes you back to stock but i was ok with this.
So here's what i did today:
relocked my bootloader following this video exactly: http://youtu.be/5yS7yy4XVA4
after i did this the phone may or may not have been stuck in bootloader loop i'm not sure since then i decided to apply the ruu right after.
following this video: http://www.youtube.com/watch?v=NChdbyaHy3k
now the phone only boots into the bootloader heres all this info:
****Tampered****
****Relocked****
***Security Warning***
Jewel Pvt ship s-on rl
hboot-2.09.0000
radio-1.05.11.0606
opendsp-v25.1.0.32.0405
eMMC-boot
Oct 18 2012, 15:4620
FASTBOOT
So i'm offering $15 via paypal to anyone who can help me out step by step to get my phone working again. I just want it to be completely stock running the latest. I tried running, and re running the ruu and everything goes through says its complete but i'm still stuck in the boot loop PAY
****UPDATES****BEWARE OF RUUUUUUUUUUUU
So it seems a lot of people have been having issues with this RUU and have been running into similar problems. Basically the ruu is updating everyones hboot to 2.09 and skipping over the radios. So its come to the conclusion that you should avoid applying the ruu or use it only as a last resort(brick). If you want stock jb then simply install the stock rooted rom. For now it seems the only thing we can do is wait for a method that will give us s-off for 2.09 and allow us to update the radios, or a newer ota/radio update from htc.
for more info/updates on the ruu situation see here http://forum.xda-developers.com/showthread.php?t=2089509
Try running the ruu again while in fastboot.
Sent from my EVO using xda premium
Which hboot were you on previously? I it looks like the ruu updated your hboot, but it didn't update your radios or anything else. Since it appears you can get into fastboot mode, I would plug your phone into a usb port and try to flash the ruu using fastboot. Look for a post by bigdaddy in the Android development stickies. It may help you. One of your problems will be you have some of the current firmware bits installed but not all of them. Which means you risk a hard brick if you to to revert to an older version. There was a post a while back where someone had a hboot flashable pj75img.zip that HTC sent him. That way you could put it on your sdcard and run it from hboot. If I pop can find it I will post a link.
Sent from my A500 using Tapatalk
---------- Post added at 10:20 PM ---------- Previous post was at 10:05 PM ----------
Here is the post with a link to the pj75img.zip. Download it, put it on the root of your sdcard, boot your phone into the bootloader, let it find the file and select yes to install it.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Sent from my A500 using Tapatalk
Was it really necessary to offer money??
Send a message to captain throwback, he'll help you if you can be helped. And there are others too who would do it for free...
Good luck to you
Yep happens to me every time I relock my bootloader. Either (1) run ruu and let it finish. Or (2) use the htcdev sife to unlock your bootloader.
Sent from my EVO using xda app-developers app
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
rollerpig said:
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
Click to expand...
Click to collapse
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Sigh...
I am in the EXACT same boat.
Unfortunately the radios go completely biserko running anything jelly bean.
Fortunately I am able to unlock at will and run whatever ROM I want though... just not run it well at all.
Current status in my bootloader for the lurkers:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ****
JEWEL OVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMC-boot
Oct 18 2012,15:46:20
The 3.15 RUU completes supposedly "successfully" when ran with the phone in fastboot, however it completes in record time. What takes 10 minutes in the videos takes but maybe 3 minutes on my phone. Sigh.
Gonna flash ICS and continue to lurk. If anyone finds a fix for this please update this thread as I'm subscribed.
As clarification to lurkers...
UB2NOZ said:
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Click to expand...
Click to collapse
Relocked bootloader.
Ran Jelly RUU 3.15
Unlocked bootloader
Made my backup in TWRP
Not sure what the point of that backup is though, the ROM doesn't get updated by the RUU. As soon as I re-unlock I am able to boot right into my previous rom.
I've tried a complete wipe then ran the RUU, same result, except obviously I just had to reload a ROM afterwards.
Flashed an ICS ROM then ran my RUU thinking maybe it was verifying the current ROM version, still no joy.
The RUU goes through it's process, all be it faster than what one would think it should, and finishes saying it successfully completed. But it never actually updates the ROM.
I'm adding tags so others can find the thread as it took awhile to sort through and find this particular issue.
TAGS:
Bootloader HBOOT 2.09 Boot Loader Loop Security Warning Radio-1.05.11.0606 Firmware 3.15
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Brick the phone as a solution.... Sigh...
cruise350 said:
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
tankerkevo said:
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2081631 this sign good things coming to 2.09 hboot
Sent from my EVO using xda premium
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
rollerpig said:
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
Click to expand...
Click to collapse
I hate to be a debbie downer, but...
I wouldn't put too much stock in the latest dirtyracun s-off technique.
The first step in Dirty Racun requires you to stock the phone with the official RUU. In our case the 3.15 RUU.
Well, for the folks in our position the official HTC 3.15 RUU doesn't actually do a damn thing.
Per their instructions:
Download the RUU for your current HBOOT and put it in your DirtyRacun folder:
This step is REQUIRED even if you are on Stock RUU already!
RUU 1.22.651.3 - HBOOT 1.15
MD5 0fde3633b4fe22123d49ea66615b57ff
RUU 2.13.651.1 - HBOOT 1.19
MD5 3c6dbe048b7cfa09fd8f31a1d65ddb51
RUU your device (with your phone in fastboot):*
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
Now unless they are using a modified RUU, I don't see this technique working in our case. That said, as soon as I get home I'm going to grab the ROM out of the EXE temp folder and try flashing it this way as I haven't done it yet:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ROM.zip
Every time I've tried flashing I've used the Windows EXE which hasn't had any problems discovering the device while it's in fastboot usb, but trying this way may fix it, I'll let the thread know in a few hours.
Fail blog time
So I ran the flash through a terminal, at least I got a more verbose error:
***NOTE The RUU.zip used here is the PJ75IMG.zip from this thread, just renamed:
http://forum.xda-developers.com/showthread.php?t=2067921
[email protected]:/home/user/Downloads# fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (No such device))
finished. total time: 5.944s
[email protected]:/home/user/Downloads# fastboot erase cache
erasing 'cache'...
OKAY [ 0.115s]
finished. total time: 0.115s
[email protected]:/home/user/Downloads# fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.068s]
finished. total time: 0.068s
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.722s]
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: 85.132s
For good measure I ran the flash a second time with the same "remote: 22 loading zip info fail" result:
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.271s]
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: 83.659s
So far the bottom line is, if you ran the latest RUU, have s-on, your hboot is at 2.09 and radio at 1.05, welcome to the SOL club.
I've received several PMs from peeps who are suffering the same deal, and everytime I check the forum there's another member joining our not so elite club.
:crying:
Bummers.
I'll donate another $20 to rollerpigs fund if we can get this fixed before the next OTA... :silly: Just kidding, but seriously...
As always any help from the cloud will get stacks of kudos.
---------- Post added at 07:52 AM ---------- Previous post was at 07:19 AM ----------
To verify the image from the other thread, I just ran the same thing on my Windows partition using the rom_01.zip from the RUU EXE, and as anticipated got the same result.
Just got a new Evo LTE yesterday. Unlocked, but can't get S-off following the infamous YouTube video. Relocked then tried RUU. I have the same problem. RUU runs faster then it should. Was 2.13 and when I ran 2.13, it would say I had 2.13 installed. Doesnt work. Tried 3.15. Checks RUU image and says 3.15 is installed on my phone. Huh??? Reboot phone and still running ICS. Can't flash it back to stock. Going to try PJ75IMG. Maybe I will be lucky enough for it to brick and I can take it back to Sprint.
Maybe when Dirty Racun is for hboot 2.09 is released to the public soon, the ruu they provide to flash before you run their process may fix you guys up. Don't know. I think for the mean time people should stop running the ruu to try to upgrade and take the ota instead. The OP should try to change the title of this thread to something more informative like: "help, I ran the 3.15 RUU to upgrade my phone and it screwed up my phone, DO NOT RUN THE RUU BEFORE READING THIS"
Unbelievable how HTC has taken such a nasty stance on enabling people to tweak these phones. I have been using Sense since windows mobile, but all these hoops are not worth the hassle.
PS I am in the same boat. The 3.15RUU file updated the bootloader but NOT the Rom. On reboot the stock sprint Rom was still there along with all settings email etc. P.S. Also followed qbking77 youtube videos except went with the latest RUU instead of the one I had installed.
Op should change thread title to warn others. Problem with these forums is that there is SO much information its impossible to know what is important without spending hours reading.
Thoughts :
What if we were to unlock the bootloader again (I used RegawMOD and install TWRP, then run the older RUU with the earlier HBOOT version wouldn't that work? Does TWRP recovery overwrite the stock HBOOT? I was under the impression that it did, but now I am not too sure.
PS check this out folks:
http://www.pocketables.com/2013/01/...&utm_campaign=Feed:+GoodAndEvo+(Good+and+EVO)
Pretty much summing it all up.
http://www.pocketables.com/2012/12/...es-for-rooted-s-on-htc-evo-4g-lte-owners.html
No
I believe the current HBOOT 2.09 is what is validating the RUU being flashed. So if you try to flash an earlier RUU the current HBPOOT 2.09 halts you in your tracks.
As far as MeanBean, yeah it looks to be shaping up to be a great ROM. Unfortunately any JB ROM installed on antiquated and unflashable radio firmware isn't likely to function well. I've flashed an old stock ICS ROM and it seems to be faring well as far as radios and battery life. The only radio I've noticed dropping is WIFI but it recovers rather quickly. To be honest, I remember stock having that issue previously, so my phone is basically in the status it was in October.
I'm kicking myself, I never should have ran HTCs RUU. Hopefully this was an unintentional move by HTC and they provide updated version signatures in a soon to be released RUU to fix the issue they have caused. If not, I see them going the way of Nokia, superior quality but the geeks advise others away from it. The only non technical people I know that have an HTC cell are either the people I recommended to buy one or people who were referred by other geeks.
When it comes to Android you don't want to piss off the geeks... When you ask a non-geek why they bought a specific Android phone 90% of the time they say "because my geek friend recommended it" and that's a true reality.
The problem is, people are using the ruu improperly. A ruu is not meant to update the phone to the next version of software. It is for returning a phone back to factory condition. The ruu you flash is supposed to correspond to your current hboot and firmware. That is why you are supposed to take the ota to upgrade not run a ruu. I believe if you would have started with a pj75img.zip, which is an update file you would have been alright. Now that the hboot has upgraded all future attempts at running the ruu are failing. I am afraid you maybe out of luck on fixing this until the next ota that updates hboot and radio comes out.
Sent from my A500 using Tapatalk
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Snowman1771 said:
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Click to expand...
Click to collapse
Wow! 1)..RUU does totally format, erase and finally restore the original system that came with the phone as new. so you loose everything
2) Try it from Windows 7 PC
3) Return to stock on Moonshine S-Off > http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(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: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Snowman1771 said:
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(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: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Click to expand...
Click to collapse
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
IDK it may work, worked in a different phone, but have to be pushed to the sd card
http://forum.xda-developers.com/showthread.php?p=32574569
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Snowman1771 said:
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Click to expand...
Click to collapse
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
I have S-ON and Bootloader is locked,Problem,i have Software 1.15 but i flash the HBoot,Boot.img ... To make Moonshine S-OFF.This is the 2.06 Kernel with Software 1.15 and i have Problem with Wifi and the Screen flackered white.And the next Problem,i can't unlock the Bootloader witn Hboot 1.33,i hope you understand me.
jake.corey.jacobs said:
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
Click to expand...
Click to collapse
My bootloader screen reads,
"Tampered
Locked
Monarudo pvt ship s-off
CID-VZW_001
HBOOT-1.33.0001
RADIO-1.01.01.0110"
I am on Windows 8 (and have access to a Windows 7 desktop) and yes, I have working drivers.
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Phaded said:
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Click to expand...
Click to collapse
Okay I tried both of my 2.0 USB slots and neither worked, Here is what I get -
C:\Users\Matt\Desktop\adt-bundle-windows-x86_64-20130522\sdk\tools>fastboot flas
h splash1 splash.img
sending 'splash1' (4050 KB)...
OKAY [ 0.616s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.653s
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Phaded said:
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Click to expand...
Click to collapse
Just tried to OEM unlock and nothing, it gives me this.
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s
The command is "fastboot oem unlock" isn't?
Just looked into HTC Dev and the DNA is not listed as being supported.
Snowman1771 said:
Just looked into HTC Dev and the DNA is not listed as being supported.
Click to expand...
Click to collapse
you have to select other devices.
Like Jake said, scroll to the other devices part, then try
jake.corey.jacobs said:
you have to select other devices.
Click to expand...
Click to collapse
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Snowman1771 said:
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
does your CID say vzw_001 or 111111 or 222222
You may be able to write the cid since you're s-off. Don't hold me to that tho.
jake.corey.jacobs said:
does your CID say vzw_001 or 111111 or 222222
Click to expand...
Click to collapse
The CID says VZW_001.
As the title specifics, I currently have no OS or recovery on my Droid DNA. I'm S-On and Locked. all i have access to is fastboot, no recovery. I'm trying to get back to stock so that i can bring it in to vzw. any idea how i can unlock and install my recover?
thanks
EDIT: some more details on my problem - i initially had it unlocked/s-off via moonshine. currently, its version 2.06 (doesn't boot), hboot version 1.33.0001. the only thing that correctly installs is dna2.06firmware.zip.
RUU doesn't complete (error 158). installing PL83IMG.zip and PL8320000-DNA.zip doesn't work either. not sure where to go now.
read in this section, this problem has been answered many times
hyphydragon said:
read in this section, this problem has been answered many times
Click to expand...
Click to collapse
I've read through many of the threads but unfortunately none of them help with my problem
snazztasticmatt said:
As the title specifics, I currently have no OS or recovery on my Droid DNA. I'm S-On and Locked. all i have access to is fastboot, no recovery. I'm trying to get back to stock so that i can bring it in to vzw. any idea how i can unlock and install my recover?
thanks
EDIT: some more details on my problem - i initially had it unlocked/s-off via moonshine. currently, its version 2.06 (doesn't boot), hboot version 1.33.0001. the only thing that correctly installs is dna2.06firmware.zip.
RUU doesn't complete (error 158). installing PL83IMG.zip and PL8320000-DNA.zip doesn't work either. not sure where to go now.
Click to expand...
Click to collapse
You need to flash Stock Hboot and then RUU
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
piled onedati
finanandroid said:
You need to flash Stock Hboot and then RUU
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
Click to expand...
Click to collapse
it doesn't flash. this is the message i get when i try to flash it:
Code:
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.254s
heres what fastboot says:
Code:
*** TAMPERED ***
*** LOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Mar 9 2013,17:46:45:-1
I have Sprint CDMA Evo 3D NOT ROOTED
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
Software Version: 2.95.651.6 710RD
I have been stressing for hours trying to figure this out!
I tried following a tutorial to root the phone and I get stuck trying to unlock the bootloader following htcdev.
After I enter the commands I do not get a dialog on my phone screen asking to unlock bootloader. After googling the issue i found that many people have this problem and running the RUU will fix the problem. I ran the 2.89.651.2 RUU and it failed saying that I have the wrong RUU. The problem is There is no RUU for my current version. I googled this problem as well and barley found answers, the answers I did find said I had to downgrade to 2.89.651.2 I had no idea how to do this and when i looked up how to do it I found an answer that said running the RUU while in temproot state will work (which i tried and got the same outcome as before) I found another answer that said I have to install a recovery and then flash a file that would lower my version and allow me to RUU. I got the img file for the recovery and put it in PG86IMG.zip and put that on my sd card and when i went into hboot it says checking PG86IMG.zip but then it just goes back to the regular hboot screen. Then i looked up an ADB method to flash recovery, I put the img with my fastboot and ran the commands and ended with
C:\Users\Yianni\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platf
stboot flash recovery recovery.img
sending 'recovery' (6914 KB)...
OKAY [ 1.787s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.759s
Now im lost
Breakdown:
Im trying to root
I need to unlock bootloader first
I need to RUU before I unlock bootloader but i cant without downgrading
I cant successfully downgrade
****
Any help is greatly appreciated!!