yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] mthomp9561:
hboot 1.58

i am on hboot 1.58 and every time I try to flash the 1.13 RUU it stops and tells me that it cant update because the ruu is older than what is on the phone. I have tried the jbear wire trick for DAYS with no luck and I messed up my radio calibration trying to flash to ST so my phone barely gets any signal and figured that getting s-off was the only way of fixing it. if someone could guide me through this it would be greatly appreated. And yes i have searched and searched again... for about the last 4 to 5 months... so this method was my last hope.
[HTC EVO 3D] deja hu:
Issue with Bootloader after

My software version is 2.17.651.3 so i downloaded the .zip file that corresponded w/ that from this page below. I am HTC Relocked after using the Toolkit and S-On.

http://xdaforums.com/showthread.php?t=1447839

When launching bootloader after it boots to fastboot, it registers that I renamed the file downloaded to PG86IMG.zip and goes through the process, but it never ends up at the point where I have to press up to update. It just goes back to the bootloader screen. I can't even reboot the phone, it loops back to bootloader and won't launch into recovery either.

I tried renaming the newer .651.5 zip file to PG86IMG.zip and do the same process as above. I can get the part where i have to press "up to update" and it'll run through the steps. Using Unknownforce's temp brick mode method, I unplugged the charging cable right before "updating" finished and I'm still having a problem getting it to brick properly. it keeps turning on when holding the power and booting only into the bootloader.

What am i missing? Thank you in advance guys.
[HTC EVO 3D] mthomp9561:
I had that... it was a bad download

Just try and redownload and then rename it to PG86IMG.zip and it is case sensitive.

You have to pull the cable just after pushing the up button... i count to 4 one thousand then pull just after i say 5 if it goes to update the boot section you went to far... start over.

You should have a list of things

bootloader

boot

Ect...

Ect...

For about 12 to 20 items... not sure mine is sitting bricked waiting for help from somebody... but you should not get done with the first one in the list but you cant just pull right after it starts it either
[HTC EVO 3D] closeone:
Hi mthomp9561. Flashing to other carriers is something I know little about, so that's something you'll have to do at your own risk. Now. You say that you are running the 1.13 RUU. Did you run through the brick and downgrade? You'll need to brick the phone by running the 1.58 RUU and pulling the battery as soon around 5 seconds (give or take one or two) after the update starts. Varying your timing is important.

The other could have been a bad download, or in some cases, I've found that using a different SD card, or backing up the one being used, formatting it, and copying only the file to the card has worked. In getting the phone to brick, it's truly all in the timing. Try pulling the battery at the correct time instead. Some people have had more success when doing that. ;)

Wait. So is the phone now not turning on? If that's the case, that's when you'll run the Unbrick on the CD. If you've already done that and it comes up saying that your HBOOT version is 1.4, you should be able to run the 1.13 RUU. If not, then there may be an issue with the mainver not being set properly. Would you mind running this fastboot command while booted into FASTBOOT USB mode? That would help me a bit.

fastboot getvar mainver

What number is it? If it's higher than 1.13.651.7, then that would explain it. I'm curious, as that number should have changed while unbricking. If it hasn't, I'm not completely sure what change might have been made by HTC. If you try actually bricking the device again, and running through the downgrade/unbrick, there's a chance it might set that number properly, allowing you to run the 1.13 RUU.

~co~
[HTC EVO 3D] mpgrimm2:
I have multiple links in my HTC Unlock Guide for the 2.17 & 2.89 RUU's that may help:

Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)

( i need to locate more working 1.13 Ruu links)

And just to point out, Until you are s-off (or psuedo bricked), you won't be able to run an earlier RUU version than the one currently installed on the phone.
[HTC EVO 3D] mthomp9561:
The second post was trying to help the other guy...sorry for the confusion... the mainver is 2.89... so far i have done the down grade twice and both times it comes up like that. Yes i get hboot 1.40 after but the mainver is 2.89. I have gotten pretty good at bricking it... then i do the unbrick/downgrade and it says success on steps 1 and 3... step 2 is just unplugging the phone... then i try to flash the 1.13 ruu and it gets to the point just after updating signature and gives error code 141 if my memory serves me correctly and says that the version of software being flashed is older than whats on the phone and then exits.
[HTC EVO 3D] mthomp9561:
So i did what you said about rebricking it if it didnt change the version number... then it took... good to go thanks for the help
[HTC EVO 3D] mpgrimm2:
Mthomp,

Could you summarize what software/firmware/hboot u started with & what u ended up with?

I ask because I get the impression u successfully downgraded hboot 1.58 & 2.89 firmware. Thanks.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] mthomp9561:
Ok I was on

hw ver 002

Sw ver 2.89651.2 710RD

Pri ver 1.43_003

Prl 21086x

Build No. 2.89.651.2 CL409645

Hboot 1.58.0000

Radio 1.09.00.0706

I flashed jbear 1.58.5858 hboot after s-off but i just needed to brick/downgrade it twice in a row without trying to start fresh (flash the stock 2.89 rom to get the phone in a "working" condition again... it would boot loop it trying to do anything but go into bootloader.)

I had unlocked and rooted at one point but relocked and unrooted to do the downgrade. I had never flashed any other roms to it,let alone do anything with the VM leak. I screwed up the radio by copying the NV files from my Precident to try and get ST working on it. I took the OTA's to try and fix the NV screw up. The NV screw up is what I blame for the jbear wire trick not working but might not be it... But stock would be best to call it. I pulled the PG86IMG.zip for 2.89 from the RUU from shipped-roms.com. If you want more info just ask

I would post a photo of hboot screen but well...
[HTC EVO 3D] mpgrimm2:
I am confused as to when you flashed the Jbear 1.58.5858 and by mention of the NV / ST acronyms.

So, were you previously S-Off before doing this process or S-On?

Ultimately, I am trying to verify if this process works with Stock Hboot 1.58/2.89 fw/S-ON to downgrade to Stock Hboot 1.40/1.13 fw/S-OFF.
[HTC EVO 3D] mthomp9561:
Before I started I was s-on and and after I was s-off. I flashed jbear 1.58.5858 after completion of the process. Yes, it works but you may need to brick twice to get the version to take so 1.13 can be flashed.

As for NV and ST...

ST = Straight Talk

NV = NV item files that hold things like ESN and other settings that most of the time dont get over written when flashing an update... if you dont try to flash to another carrier then you might never even play with them. CDMA Workshop edits them directly, along with QPST.

I hope that helps to clearify.
[HTC EVO 3D] ricohz:
hey guys need a lil help and thanks in advance i am locked s off running the latest boot 1.58 how can i unlocked and go back to flashing

?:o
[HTC EVO 3D] ricohz:
here is what my hboot looks like

never mind guys i got it thanks
[HTC EVO 3D] ricohz:
does anyone have a 2.17 ruu zip i can use ???:o
[HTC EVO 3D] mpgrimm2:
Why would u want the 2.17 zip if you are on 2.89 base?

Either way...

Head over to my HTC Unlock/hboot 1.5x Guide and post 11 will have some links and if needed, how to extract the zip yourself.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] ricohz:
i got another 3d that has 1.50 s-on so im trying to downgrade but it seems any 2.17 ruu i try doesn't work,Been trying all night i even fallow your instructions to pull my own but they don't seem to take
[HTC EVO 3D] ramjet73:
If it's S-ON you have to relock the bootloader ("fastboot oem lock") then run the RUU.exe from Windows. S-ON phones can't run the RUU .zip file from the bootloader.

Also, if you are already on the 2.89 build you can't downgrade to a lower RUU (2.17) with gaining S-OFF first, which you will need to do with the JuopunutBear (wire trick) method.

ramjet73
[HTC EVO 3D] ricohz:
first of all thanks for your reply's grimm and ramjet :D you guys are awesome and always helping every one:good::good::good:

this is another device that is s-on locked 1.50
[HTC EVO 3D] ramjet73:
Thanks!

Since that device is S-ON, locked with the 1.50 bootloader (fully stock) you can use either the HBoot 1.4 downgrade method in this thread or the JuopunutBear (wire trick) method. The Jbear method requires an HTC unlocked device, so it might be easier to proceed with the downgrade if you are ready to do that.

ramjet73
[HTC EVO 3D] closeone:
I'm right here guys. :( It's hard maintaining multiple threads like this (for me at least.. I know it's really not that many, but it's not easy).

The HBOOT Downgrade Method does work even if you are on the latest HBOOT. I'm not sure why, but the mainver variable doesn't take the first time you brick the phone and do the unbrick, but bricking and unbricking one more time fixes that problem.

So yes, the HBOOT Downgrade is 100% usable on the 1.58 HBOOT.

Sorry again, :(

~co~

Edit:

Absolutely no offense to you ramjet73. None at all. But you can downgrade if you're already on 2.89. It's my fault for not updating the instructions. Brick using that RUU. Unbrick. Brick using the RUU again (I know it's not exactly the most convenient), then unbrick and continue with flashing the 1.13 RUU.

~co~
[HTC EVO 3D] ramjet73:
No offense taken. I read in other threads that the downgrade method didn't work if the 2.89.651.2 Sprint ICS build was installed via OTA or RUU.exe, but apparently that was incorrect. I'm glad you clarified it. :)

ramjet73
[HTC EVO 3D] mpgrimm2:
Closeone,

FYI, I think some of the 2.17 & 1.13 Ruu links in your op may be dead (& Unknownforce's I think).

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] closeone:
The wonderful thing here is just that, we have the RUU. Albeit, it's an executable, but I've been pointing people to Mpgrimm2's post on extracting the ZIP from the executable. Works every time. ;) Actually, the funny thing is, I had to do some guesswork in trying to figure out why the downgrade wasn't working. It wasn't until someone said that they had bricked and unbricked, but weren't able to run the RUU, that I realized that the downgrade tool was failing to set the mainver variable (the one that the phone uses to see if an RUU is a higher version or lower version than what's already on there. Running through it one more time seemed to fix the problem.

Yeah... about that...

...I'm not too surprised. After Goo.im had their huge data loss (where I believe I linked to most of them)...​

I have yet to find the correct RUUs every time. I keep having to retrace back to find them, because I pretty much always just went to the site and linked to the proper RUU whenever someone requested a link to one.

If someone can find links to all of them for me, I think I'll upload them to my account over at AndroidFileHost so that they are easy to find from now on.

~co~
[HTC EVO 3D] ramjet73:
You might be interested in this thread that I started in the Evo 3D General Forum since it includes a flashable zip that will modify the mainver from recovery using the HTC misctool utility, so it can be changed even if you are S-ON. That might eliminate the requirement to run the RUU twice for the downgrade from 2.89, but I understand there may also be more involved than just that.

ramjet73
[HTC EVO 3D] closeone:
My apologies for not replying sooner. That might work, but the user would have to be, at the very least, HTC Unlocked. If the phone was upgraded to 2.89 without S-OFF (which would make this moot), or came that way after being factory serviced (very likely), then I don't see this working unfortunately. After the unbricking, the device would be on the 1.40 bootloader, but still be unable to load a custom recovery to flash this with.

Oh... all the hoops we have to jump through just so we can do what we want to do with our phones. Thanks HTC/Sprint...

~co~
[HTC EVO 3D] Unknownforce:
I find it strange that you have to brick twice... What exactly is the reasoning behind this?
[HTC EVO 3D] closeone:
I know it sounds strange, but it's the one way I could figure out how to have the Miscver variable take if someone was on the 1.58 bootloader. Essentially, with a device that's on HBOOT 1.58 and with the newer OTA/RUU loaded, when the device is "unbricked" after bricking, the variable has not changed for users. It stays at 2.89.651.2, preventing the 1.13RUU from being run (because it's lower). So, after doing it a second time, the variable changes, allowing the downgrade to continue. I don't know what's causing it to not work, whether it's a change to how/where that variable is stored, or something else, but after doing this, it works as it should.

~co~
[HTC EVO 3D] mpgrimm2:
From the Ultimate Recovery Tool Thread:

Erick is now the second person to confirm it. Maybe this will be enough info to update/tweak the process some more.

Edit: I see you may have already saw his post. Sorry about that.
[HTC EVO 3D] nerv666999:
Another way to brick??

Well I just got a replacement Evo3D from Asurion since my local Sprint knuckleheads didn't want to replace the screen (made up some noise about discoloration on the board that must have been water damage even though none of the sensors were red). Sticker under the battery says Asurion and the production date was 9/12. I was jazzed to see it was still 2.17 and hboot 1.5 that was until I tried to brick it. It won't stay on once you pull the battery. I've tried dozens of times with every charger and cable I have and nada. So now what? I think they must have modified it, but do they really pay that close attention to the activities of groups like XDA? Any ideas would be appreciated.:eek:
[HTC EVO 3D] mpgrimm2:
Have u tried the original HTC charger & cable plugged directly into the wall outlet?

I think you can do the bricking with a fully charged battery and skip the charger, ie remove the usb cable & back cover, start the update, and pull the battery at the appropriate time.

It's hard for me to search the thread on my phone, but if you do, there should be posts that confirm this as I recall.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] nerv666999:
thanks because it appears that Asurion phones are not able to htcdev unlock either. Got an error about my provider restricting the unlock process
[HTC EVO 3D] mpgrimm2:
I doubt that's it. You are on Sprint right? Likely you just need to run the full 2.17 Ruu all the way through, reboot, and try again. There are "quirks" with the partial ota updates that affect the process that 99% of the time get straightened out with a full Ruu beforehand.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] closeone:
Exactly this nerv666999. Not exactly sure why the power draw is different on a number of phones, but a battery pull works extremely well. Thanks for catching this Mpgrimm2.

I'm not sure what to say about this. It's a new one on me. If it hasn't been activated with Sprint yet, that could possibly be an issue, but it's hard for me to say. Anyways, you're a lot better off obtaining S-OFF than doing the HTC Dev Unlock.

~co~
[HTC EVO 3D] contradude:
I've successfully used this process for my father's hboot 1.5 htcdev unlocked device but my brother's hboot 1.58 stock locked device is proving to be a bit of a pain. I extracted the RUU from the .exe for the ICS rom, and it only takes about 2.75 seconds to go through the bootloader step. I have been trying the suggested battery pull and I am unable to brick the device. I bricked my dad's device on the second try... does anyone have the timing on this? is 3 seconds too fast? I used the RUU to completely flash the device and it seems stable now
[HTC EVO 3D] mpgrimm2:
Contradude,

If it takes 2.75 secs to finish the boot loader step (1) then u have less than 2.75 secs to brick it. Once it moves to step 2 of the update, you've missed it and have to try again.

If u can't get it to work (apparently it does work for 2.89 fw) u can run the 2.89 Ruu.all the.way through and try the Jbear wire trick for 2.89. See Ramjet73's thread:

http://xdaforums.com/showthread.php?t=1889438﻿

[Guide] Quick And Dirty Evo3D Root & S-OFF (Sprint Only)

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] contradude:
am I trying to time it just before it moves on, or any time that the updating is purple? just trying to get a feel for the timing
[HTC EVO 3D] mpgrimm2:
Vary the timing from, right after you select "update" to before it moves on past step 1.

It can be a pia to get it right.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] negativzeroe:
That's true. I had one that wouldn't give me an error but the unlock prompt never showed up on my phone screen. I called Asurion and told them it was "overheating" and they sent me another one that I did root via HTC before this, so I don't think its them.

Sent from my Zerg'd ZR3D in a galaxy far, far away...
[HTC EVO 3D] loveVII:
Does this method work for Virgin Mobile?

I relocked my device and got the security warning at the top.

Can't get RUU 2.17 to flash because of CID error.

Can someone please help a brother out? Am I stuck going the JBEAR method?
[HTC EVO 3D] mpgrimm2:
Here's some info recently from the Hboot Differences thread:
[HTC EVO 3D] loveVII:
Thank you kindly.
[HTC EVO 3D] xDragod:
Okay, so, I am going to be attempting this with my 1.58 Hboot.

I am aware I have to do brick, unbrick, then rebrick? Can anyone explain how to unbrick before I try this? and when exactly I do these steps? Do I follow unknownforce's directions to brick, confirm it's bricked, then do the unbrick process (Whatever that is), then brick again? Or do I brick, boot into the toolkit and do 'downgrade'?

Any help would be appreciated.
[HTC EVO 3D] mpgrimm2:
DISCLAIMER: Keep in mind that I did this on Hboot 1.50 not 1.58 ur on Sprint Right?

I know the previous person's post to do it successfully started here.

I reread your question a few times to understand the difference in what was being asked and mthomp's posts. Since I'm not sure when Closeone will pop in here, I'm going to tell u what I would try from reading prior posts.

Option 1 (probably won't work):

- load up the 2.89 Ruu.zip and run it all the way through and let it reboot to clean out all the cob webs.

Double check to make sure u r not S-off.

- Reboot to bootloader and brick it during the boot loader update as listed in the op.

- If possible, kill all power, reboot bootloader, and do the previous brick step again

( if it won't boot to bootloader because its bricked, move to option 2).

- continue with step 19 from the OP (I think) to do the "Downgrade" (unbrick) from the Toolkit.

Option 2:

- continue with step 19 from the OP (I think) to do the "Downgrade" from the Toolkit.

- once done, instead of running the 1.13 Ruu, rebrick with the 2.89 zip again.

- redo the step 19 Downgrade again and continue on as normal in the op.

Basically you will cycle through steps 12 - 27 from the OP twice with the 2.89 zip.

Sent from my "Up all night, sleep all day" HP CM9 Touchpad
[HTC EVO 3D] closeone:
Sorry. :o

Hopefully I don't repeat what you just said (little tired) Mpgrimm2.

Exactly. You'll brick the phone twice with the 2.89 zip.

1. Brick using the 2.89 zip

2. Unbrick from the Toolkit

3. Brick again using the 2.89 zip

4. Unbrick again from the toolkit

5. Then continue from step 28 on as normal :)

Thank you,

~co~
[HTC EVO 3D] Logic33:
Hey closeone! Thanks a lot for the guide and offering a way to downgrade, it's really awesome that you've taken the time to do this. Unfortunately, I'm stupid and not worthy of it D: I successfully bricked my phone (solid dim light and all) but the problem is, I completely spaced on enabling USB debugging. I'm used to it being on by default with custom ROMs, so when I flashed the stock RUU this morning I totally forgot to enable it before starting. Now my phone is a true brick.

I've tried using dexter's HTC Unbricking Project method, but that can't detect the device. I'm assuming it's for the exact same reason. I just wanted to know if you have any idea if I can fix this. It isn't a complete disaster if this phone is ****ed -- I think I still have my old EVO 4G, so if it's really ruined I should be able to just go back to that, but I'm really punching myself here for making such a dumb mistake and it feels cheap that I spent so much time trying to brick it that, as soon as I do it right, I screwed up, lol.

Thanks a ton to anyone who reads the thread that can help! You're saving a true noob a lot of money and time.. :D
[HTC EVO 3D] mpgrimm2:
Go to post 3 and identify what step # you are at. USB debugging doesn't make sense to me because its not an option with the phone bricked. You should be running some of the steps from the Linux liveCD.
[HTC EVO 3D] Logic33:
After I bricked the device, I tried to unbrick it but the live CD couldn't recognize the phone. It would just sit there waiting for device while I was holding down the Vol - button and not recognize it. I waited about a minute - should it take longer?
[HTC EVO 3D] closeone:
Hi Logic33. Make sure that the battery is out of the phone while you're at that screen. Also, check to make sure that the phone is actually bricked, by popping the battery back in. If the phone does power on, keep trying. If everything still seems right, I'd recommend using another computer to unbrick.

Hope this helps,

~co~
[HTC EVO 3D] Logic33:
Alright, I'll keep on trying. So then it isnt horrible that I didnt enable USB debugging beforehand? When I get the chance ill keep on trying to downgrade, and I'll try it on my desktop as well. Also, I can confirm that it is bricked, because when the battery is in and you hit the power button it just has that solid dim light, no screen power on or anything like that.
[HTC EVO 3D] tx_jaycee:
Ok I'm having some problems with the 2.17 PG86IMG.zip as I get Main Version is older! Update Fail. I'm S-ON Hboot 1.58.
[HTC EVO 3D] ramjet73:
I think you have to use the 2.89.651.2 RUU since you cannot flash an older version that what's installed with S-ON.

ramjet73
[HTC EVO 3D] tx_jaycee:
Ok that makes sense. What do I need to do to RUU exe file to convert to PG86IMG.zip?

NVM found my answer here
[HTC EVO 3D] tx_jaycee:
Now my issue is that I can't brick. I keep getting a power off when hitting volume up after a battery pull. Any suggestions?
[HTC EVO 3D] mpgrimm2:
In my HtC Unlock Guide ( post 11 I think. See signature) there are copies of the ruu exe& zip versions. Try another 2.89 zip.

Sent from my "Up all night, sleep all day" HP CM9 Touchpad
[HTC EVO 3D] SinisterChedda:
So another replacement(black lcd) that I have to s-off to run jellybean aokp. This will be my 4th time doing this but this time I have hboot 1.58 and newest software(sucks I know). I am wondering after searching the thread what I need to to do for the 1.58 downgrade and how successful it is or if I should use another method. I have a older toolkit(2-3 months old or so) and if I can use that or if I need a newer toolkit that works with the 1.58 . Thanks for any help
[HTC EVO 3D] mpgrimm2:
It works with the 2.89 zip, but u have to brick twice. Your other option is to run the bear wire trick (Ramjet73's Quick & Dirty recommended for that method)
[HTC EVO 3D] fitusv:
I will recommend using the wire trick, it took me 3 minutes to become s-off, and now I change from hboots, like changing chones