yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Just got a replacement 3d, 1.58 hboot. I want to make sure I'm doing this right. Pull plug when bootloader is updating, because mine takes about 1/2 second to update. I'm not fast enough to time it right. I've bricked my old phone before, I don't want to unlock to s off.

Is it possible to use wire trick to brick?
[HTC EVO 3D] Unknownforce:
No, wire trick only puts phone into download mode, it doesn't brick the device.

You can brick on 1.58, it has been done. Just keep trying, try different times, pull it earlier each time. Best way I think is to let it flash a couple times, watch for the bar in the upper right hand corner to appear and disappear quickly (it only shows for a split second) then see exactly how long it takes for that bar to appear... then try to time it just right so that you pull the power RIGHT before or JUST as it shows up.

As I said before, the "right time" window is very small in that you only have about a quarter of a second, if that, to interrupt the flash for it to corrupt the hboot and brick.
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Been trying for 3 days now, hours on end with no brick. Just frustrating. I will keep trying.
[HTC EVO 3D] Unknownforce:
Well if time isn't a factor, you are welcome to send it to me and I can get it done for you. I can overnight it back if you need as well. (Compliments of my job. ;) ) Toss me a PM if you want.

It would give me the chance to test out version 3.0 too. ;)

Speaking of 3.0, it's pretty much complete, I just have no way to test it right now. I re-wrote nearly all of the code. So, while it still does the same functions, the method in which it carries them out is much different, and much more optimized. It no longer requires -options or anything, you just run ./ultimate and then select a numbered option. It's got it's own "interface" much like the preview I posted a few pages back and is much easier to use. I've also created a LiveCD for it that you just burn and boot to and it starts ultimate. I've also eliminated the need for the hboot image files and misc files or any extra files at all, they are all embedded into the tool now, so no more missing file possibilities or permission issues. (the tool still needs to be run with sudo or root, but after that it's fine)

I don't want to release it and have it not work as intended or cause unwanted side effects, when version 2.5.2 worked just fine...

Because it's a complete re-write, I need to make sure there aren't any major bugs with the new code... and I can't do that without a device. :(

I was hoping to get my phone back from my friend who is using it as a temp replacement while he gets a new one, but he's now just going to buy it off of me and use it permanently, so I no longer have an EVO 3D.

I'm going to look into buying another 3D that I can use for this, but money is kinda tight right now. :(
[HTC EVO 3D] Unknownforce:
Well, I just bought one on ebay for $40 that he claims all of a sudden "won't power on"

Taking a little chance here, but hopefully I can revive it ! :good:
[HTC EVO 3D] The Fer-Shiz-Nizzle:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Sounds like a good deal. You have resurrected my device twice, so if it's un-brickable I know you can do it. If it's just a broken LCD, hit me up, I might be able to help u out.
[HTC EVO 3D] Unknownforce:
Will do, thanks!
[HTC EVO 3D] jcfunk:
I was finally about to to brick my phone. Did downgrade my hboot, but my main var still 2.89 can't install 1.13. I wish I know which partitions has main var info. so I can change it. I've not be able to brick, downgrade, and then brick again with out updating hboot on mistake. This phone is nothing but problems. Also for me if the progress bar comes up its already installed bootloader.
[HTC EVO 3D] mpgrimm2:
I haven't used this version of the downgrade tool, so I would

wait and see if Unknownforce has something to add

, but I believe it sets the MainVer lower as part of the process. I did recall a 'related' thread by Ramjet73 for changing the MainVer but it may only work for S-Off...

Main Version (mainver)
[HTC EVO 3D] Unknownforce:
He got it working.

The problem is that they changed the misc partition location in ICS. Which stores the mainver number. But this is why I had to give GSM users the option to pick 31 or 32, theirs was 31 in GB, then 32 in ICS, the CDMA was 34 in GB, now it's 35 in ICS.

URT 2.5.1 and lower are hard coded to write to 34 (as I didn't know that the misc partition changed in ICS) so the main version didn't change because it's updating the wrong partition.

I've resolved this exact issue in 3.0 (hopefully) by adding a way to detect the misc partition before writing to it, which will eliminate the need for Selecting GSM Mode as well.

Downgrading and Unbricking will be able "auto-detect" cdma/gsm where the tool finds the misc partition first then write just that version number, not the entire partition, just the version number. (this caused issues on GSM)

Then, based on the misc partition number it finds, it writes the corresponding hboot to the corresponding partition (if the misc partition is 31 or 32, the tool will know to flash gsm hboot to 12, if it's 34 or 35, it will flash cdma hboot to 13)

Anyone doing this from ICS ROM's will be better off waiting until I get 3.0 out, as it will work correctly the first time around rather than having to do it twice.
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Ah, good to be downgraded. With Unknown's help and lots of research. It worked. Thanks

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] mpgrimm2:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Thanks Unknownforce for the info here and over at Ramjet73's thread. Sorry if I sidetracked the thread.

Sent from my "Up all night, sleep all day" HP CM9 Touchpad
[HTC EVO 3D] Unknownforce:
Not at all, once we get down to the nitty gritty "low level" stuff like we use for the downgrade and discussing partitions and whatnot, just about anything goes ;)
[HTC EVO 3D] uf20wop:
Hey Unknown, If i want to downgrade my 1.58 in one shot, would i use -g -d and enter 35 as my misc partition?
[HTC EVO 3D] Unknownforce:
NO, this would do damage, possibly irreparable damage. Do not do this, it would write a gsm partition to your device and also write it to the wrong partition.

Downgrading in one shot right now would require bricking, then doing ./ultimate -p 35 -c misc.img first.

Then do a normal downgrade with ./ultimate -d

Adding -g sets it to use partition 12 for hboot and the gsm hboot image file. I forgot what 12 was on CDMA, but I would venture a guess that it wouldn't be good to write an hboot partition to it.
[HTC EVO 3D] uf20wop:
ha k thanks. I didn't think -g was right so I'm glad I asked.
[HTC EVO 3D] uf20wop:
Thanks to Unknown and jcfunk for helping out... finally got it bricked and downgraded this morning.

to brick 1.58 I had to pull the power BEFORE the progress bar showed up... probably about 4 seconds after pressing volume up... everything else was a piece of cake, including using revolutionary to get s-off.
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Well, I get to do it again. Getting another replacement. Hopefully it won't take 3 days to brick. :D

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] mpgrimm2:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

What happened this time?

Sent from my "Up all night, sleep all day" HP CM9 Touchpad
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

The phone they sent was crap, or battery was bad. On stock it would just keep rebooting, battery would drain fast. Was hoping to fix with custom rom, but no go so they going to send me a new replacement.

Edited: I know the phone they first sent had issues, because it only had 189 calls made on it. Data use was only 50 megs. The one they sent me today had 3000 calls made on it.

I was able to brick it in 3 tries. Installing 1.13 on it now. Glad this one went easier.

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] Unknownforce:
Just an update, I finally found another EVO 3D I can use for testing, the one I got before was completely dead, no signs of life, most likely a board/power issue, the one I just got works, so I'll be able to piece together one that I can permanently use for testing.

I hopefully should have it by next Tuesday, and then I'll be able to fully test 3.0 and hopefully get it released mid next week. I'll also include a LiveCD for folks who don't know how to use Linux at all. :)
[HTC EVO 3D] The Dark Knight Patriot:
Wow, talk about perfect timing!

I'm currently in the process of trying to root my HBOOT 1.5 EVO 3D (I received it the day they first hit the U.S. market, and this thing's been great). However, I've been having serious issues with internal memory shortage since late last Autumn, and while at least two OTA updates fixed the memory leakage to a certain extent, they in turn sucked up most of my remaining memory. Subsequently, I'd like to gain full access to the device so I can hopefully clear it up while backing up all of my data first (I've used My Backup Pro, but it only saves my downloaded apps, and I want to save data from my pre-loaded Internet App, Facebook, a few games, etc.). I'm looking forward to your latest release, and hopefully it works for my intended purposes.
[HTC EVO 3D] Unknownforce:
Got the phone pieced together last night and it's working well. I was able to use 3.0 to get it downgraded (after fixing several bugs) I'm still doing a little testing...

The things I have tested: Unbrick, Downgrade, Backup

The things I have not tested: Flash Custom, VM Radio Fix.

The misc partition detection works, so that removed the need to specify GSM or CDMA, or set that "mode." It will set the hboot partition based on the number of the misc partition, and write them accordingly. Below is a small chart... If ANYONE has a device that differs from this. PLEASE let me know ASAP.

Last partition on device(misc) -- 31 32 33 34 35

Corresponding Hboot partition -- 12 12 NO 13 13

I also fixed the GSM's CID related issues as well, I hope. I have no way to test this for certain, but I'm 99.99% sure it's resolved.

The menu interface works well. It's still got some minor bugs that I need to iron out, but such is the case when you completely re-design something...

I was able to use the backup function without issue. However, this I would like to figure out a better way to put the backup in a location that isn't deleted in a LiveCD Environment. Booting to a LiveCD stores everything in RAM (temp memory) and naturally when you reboot, the memory is flushed so you can use fresh for your next boot up, And so your backup is lost to the abyss.

If you know Linux well enough you can just specify the location with the file name to backup to and that will work, but not everyone knows how to do that or how to know where to write to, and besides you're likely not going to need the LiveCD if you know Linux well enough. ;) It needs some other location to store the backup. This isn't a major concern, and I won't be looking into this anytime soon. And it won't stop me from releasing 3.0 as it was this way in 2.5.1 as well, so it's not a show stopper.

Anyway, to the main point, I'm wrapping up a few loose ends in the code and I should have it finished either tonight or tomorrow night. (I work from 8-5 every day, so I can only work on this after work)
[HTC EVO 3D] mpgrimm2:
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade, VM Radio Fix/Reset)

Perhaps the backup's folder can be placed on the LiveCd's desktop so it can be easily copied off to a thumbdrive/sdcard that the user plugs into the pc.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] Unknownforce:
Right now, I'm using TinyCore without the GUI interface. I suppose I could try to make the GUI interface work for us... But I'm hardly familiar enough to do that just yet.

But anyway... Bad news...

I managed to permanently brick the device I had for testing with 3.0, so I'm glad that I didn't release it...

I can't be certain what happened, because I have no way to read from it now... but I'm guessing the misc detection failed somehow and it wrote the GSM hboot to it... and now it doesn't know how to boot properly, and doesn't go into the brick mode I need to see it and write partitions to it anymore. It's now a permanent brick, so that is unfortunate. Quite a setback in both time and money...

But, the good news is, I found another device that I can use for relatively cheap, but this is the last time I'm spending money on this.

Obviously I'm going to be more careful with this one and put in some checks before I do the writing, or simulate the write to somewhere other than the device, but still if something should go wrong, I'm not going to throw more money into a fire.

This obviously sets back the release until I can test it further, I should have the device by Monday.

I plan on changing the way the misc detection works and putting some more checks in to avoid detection issues, and then test the crap out of it, so it functions properly...

I might change it back to a "two plug" method, where the first plug, does the detection, and then asks the user to verify that it's a CDMA or GSM device, if not, then give them the option to specify it, with a long warning that clearly indicates that if you select the wrong one, you will end up with a paperweight, and then the second plug actually does the writing...

Either way, we've been set back by about a week :(
[HTC EVO 3D] Unknownforce:
Updated to 3.0 ALPHA, removed VM Radio Fix till I can get it working properly in 3.0

3.0 ALPHA

Completely Redesigned and Re-Written

New menu interface

Removed the need for hboot/misc image files to be present, they are now embedded in the program and used as necessary.

CID issue fixed for GSM devices

Misc detection implemented

GSM/CDMA detection implemented

Fixed a few missing things from the VM Radio Fix (CDMA Only)

Many minor bug fixes
[HTC EVO 3D] Unknownforce:
3.0 Released, fixed the VM Radio Fix. and Released URTLiveCD v1.0 as well.
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

Great job!

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] webender:
adb.linux: error

Tried to do the VM radio fix from the live cd, got hung up with the error:

"adb.linux: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"

any suggestions?

Thanks
[HTC EVO 3D] Unknownforce:
Ugh, the damn LiveCD is killin me.. It's not loading the libraries it needs to run adb, Try using a (blank) USB Flash drive and core2usb -> http://sourceforge.net/projects/core2usb/

And then boot from the USB stick. I'll look at getting the CD to work properly...
[HTC EVO 3D] webender:
Pulling fresh partition 19....

Thanks for the tip, booting from a usb stick worked. but..

Nevermind, I switched from a laptop to a desktop, and it's all good w/ the usb stick.

**Now I get to "Pulling fresh partition 19" (step 5?) and it resets back to the startup options screen. (Options 1-7)

and leaves the phone on the 4ext screen.**

Thanks again
[HTC EVO 3D] Unknownforce:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

Check the log file, exit out of the tool and type in: cat urtlog.txt

What do the last few lines say?

Sent from the spots between 4G coverage where I typically am
[HTC EVO 3D] Unknownforce:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.

I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.

Here's the PG86IMG file -> http://d-h.st/3p8
[HTC EVO 3D] Unknownforce:
Updated the post a bit, and added a video of the latest Tool and the battery pull method (which seems to be easier to do) from 1.58 to 1.40, and using the latest zip file as well!
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

Don't know if its just me, but the video says it's private.

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] Unknownforce:
Whoops, fixed.
[HTC EVO 3D] jcfunk:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

Unknownforce always makings the brick process look so easy, I have yet to get it to happen on que.

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] whbisondtr:
So is this the new radio for vm?
[HTC EVO 3D] Unknownforce:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

This file does not, it's only used in the downgrade process.

And the VM Radio Fix is just to get those who have a Spirit device who flashed a VM Firmware on their device back to Sprint and completely remove the VM Firmware.

Sent from the spots between 4G coverage where I typically am
[HTC EVO 3D] zozeus:
I need help! Not sure if this is the right place, but I've been using this tool. Phone had boot loop issue on stock all the way. Checked it out and it said hboot 1.58, mainver 2.89. Used the bricking method to downgrade to hboot to 1.4 but something weird happened, it said found misc on partition 33.It would never let me install 1.13 until I manually put misc.img on part 34. I was using most recent tool 3.0 on live cd. However, no matter what hboot/recovery/ruu combination I have I am stuck in boot loop and fails to load recovery. I have posted this in the main Q & A, but thought here would get the experts opinion. ;)

http://xdaforums.com/showthread.php?t=2195210
[HTC EVO 3D] Unknownforce:
Re: [TOOL] Ultimate Recovery Tool 3.0 (Unbrick, Downgrade, VM Radio Fix/Reset)

This is very strange, the misc partition should definitely not be detected there. Does it still bootloop on 1.13 or only when you update to ICS?

Sent from the spots between 4G coverage where I typically am
[HTC EVO 3D] zozeus:
It boot loops on 1.13, 2.08, 2.17, 2.89. The first time URT is ran from 2.89 it detects it on part 34, but if I run it a second time it does part 33 repeatedly until I manually put it in 34. Doing the whole process again I did it from the Rhq tools live cd or something with ultimate 3.0 instead of your live disc and does the same thing. I'm wondering if there's a bad partition somewhere and if it was possible to flash all of them(or significant ones if I knew which ones). Since my 3vo works fine and this is my girlfriend's I'm working on. Btw the link to my thread in Q&A is in the first post with more details of what all I've done and the results.
[HTC EVO 3D] Unknownforce:
We're working on this in the other thread, in case anyone is wondering.

On another note:

I'm going to add another level of verification for the misc partition detection. This shouldn't affect a downgrade from scratch, but it looks like some that have used the old tool on 1.58 HBOOT and ICS ROM's are running into problems running the new tool after already running the old tool once before...

Another level of verification will only make the misc partition that much better. The file is small enough that another level of checking won't affect the speed of the tool enough to matter.

3.1 will be out later tonight to at least add this new check. I'm also going to try and get the LiveCD to work properly on a read-only media like a CD. (currently the radio fix does not work properly when booted via CD, but it does work from a USB Flash drive.)
[HTC EVO 3D] strykerider:
@Unknownforce i don't know if my problem could be related to your tools, please forgive me if i'm posting as a junk or spam at this thread, since i have no luck try a couple method to recover from "soft brick" (maybe soft brick).

the problem is i cannot access recovery at all, already tried 7-8 times to flash a different recovery before i open the thread as mention below, but no luck..

i already open a thread in Q&A section, here's the thread and currently i have this after a couple troubleshooting:

but before i have this:

already try this with no luck and also this with zero results..

please ignore my signature since now i have both GSM and CDMA (accidentally, eh? XD), and the problem is occurred in CDMA devices..

kindly need your advice if i can use your tools to recover this device..

FYI, i have ubuntu so if you say i good to go.. i'll try your tools with your direction, of course.. :)

Thank you..

-b-
[HTC EVO 3D] Unknownforce:
Updated to 3.1, added another check to the misc partition detection, this should help to avoid the possibility of using the old tool followed by using the new tool and ultimately detecting the wrong partition.
[HTC EVO 3D] strykerider:
@Unknownforce.. please advice.. :)
[HTC EVO 3D] Unknownforce:
I responded in the thread you posted. Check there.

Sent from the spots between 4G coverage where I typically am
[HTC EVO 3D] Remanifest:
I've got both RUU files (1.13 exe and 2.17 zip), but my question before I begin is should I change anything at all since I'm on the EVO V?

---------- Post added at 10:22 PM ---------- Previous post was at 09:52 PM ----------

One final question, then I'll wait for a reply before proceeding. Will the 1.13 RUU check my CID prior to allowing me to flash it? I'm asking because I had to change the CID of the PG86IMG provided on the first page of this thread (to the VM CID)
[HTC EVO 3D] ramjet73:
This was a concern that I raised earlier. You won't be able to flash an RUU while S-ON if you change the CID in android-info.txt since it will no longer be signed by HTC.

When this was discussed earlier unknownforce thought there might be a work around so we'll have to wait for his response.

ramjet73
[HTC EVO 3D] Remanifest:
LOL, that's what I get for jumping the gun & not keeping up with your logic on time. I'm sitting here with S-ON like a clown now. ControlBear, here I come!!!

---------- Post added at 11:57 PM ---------- Previous post was at 10:59 PM ----------

I was just reading about using a SuperCID (11111111), but I don't know if it would be safe for me to go S-ON again while that CID is present. Also, using another CID would kind of defeat the purpose of this test, I think.
[HTC EVO 3D] ramjet73:
That's a possibility, or even changing your CID to "SPCS_001" which is the Sprint value that the RUU's are expecting.

I've never modified my CID so I think we should wait for unknownforce to comment on that as well.

ramjet73
[HTC EVO 3D] Unknownforce:
I have no experience modifying the CID... All the devices I've tested with have been on Sprint stock and the CID unchanged as well.

I cannot offer any real suggestions here, but I would think that as long as you put it to what it expects before downgrading, you should be fine.

Once I have a little time, I can play around with the CID stuff. I know where it's stored and I could probably write some code to change it when during the downgrade/unbrick process.
[HTC EVO 3D] Unknownforce:
Oh, if you've already done it, what you might try is to use the zip file for the 2.95 firmware that I've included which is htc signed, and has hboot 1.58 in it, you should be able to use it to brick the phone. Then do a backup of partition 4 send me a copy of that.
[HTC EVO 3D] Remanifest:
No worries, I'll probably do it later this evening or tomorrow evening. How should I do the backup of partition 4? I don't have any experience in manually backing up partitions on this phone, and I want to make sure I do it in the format you're expecting. I imagine it's a simple dd through shell, but I want to make sure we're all on the same page. I'll just change my CID to SPCS_001 before I begin, and it should work the same.

Will partition 4 contain something that will show you how to change the CID in the downgrade process? Just curious - this tool is quite incredible.