yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] xDragod:
Question.. I'm S-Off on 1.58. I want to flash an AOSP Rom, but I believe I need to be on 1.50, right?

Are there any flashable Hboot zips for 1.50 and 1.58 so that I can switch between the two when I am on either a Sense ICS or AOSP rom? If someone could message me links or information, I'd really appreciate it. I've done some searching and can't find anything definitive...
[HTC EVO 3D] mpgrimm2:
My hboot thread is stickied in the general section. Also in my signature.
[HTC EVO 3D] theycallmebrown:
I've searched through this forum looking for an answer and came up with nothing, its possible its here and i just don't what I am looking at...

I have the h-boot 1.58 and it came shipped with S-off. It says not to follow this tutorial if i already have S-off... what am i supposed to do? I want to try the new Cyanogen and it says i cant have 1.58 to use it. I have been running custom roms sine my G2, then on my nexus 1, now my evo 3d, and as "smart" as i like to pretend i am i really have no basic understanding of why what you guys do works, i just follow instructions to make my phones more awesome.

So... With h-boot 1.58 s-off what do i do so that i can downgrade to a compatible h-boot with the latest cyanogen?
[HTC EVO 3D] ramjet73:
Regarding changing the hboot to run GB and AOSP ROM's, this post should provide what you need.

ramjet73
[HTC EVO 3D] motoelliot:
Is the VM radio fix on this live cd? I cant seem to find it...

Sent from 3D A.W.E.S.O.M-O
[HTC EVO 3D] mpgrimm2:
No its definitely not. Should be in Unknownforce's Ultimate Recovery Toolkit thread.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] motoelliot:
Oh ok, i thought it was included on the live cd....

Sent from 3D A.W.E.S.O.M-O
[HTC EVO 3D] midnightmaraude:
Hi guys,

SOrry to bother you all. I have done this procedure before on two other evo 3ds. I just got my insurance replacement one today and it has hboot 1.58 and s on. WIll this step bring me to s-off?

I had the ZR3D rom on before and would like to go back to that. Any guidance would be appreciated. I read the thread with the wire trick. IS that the only way to downgrade 1.58?
[HTC EVO 3D] coal686:
This process still works, but you have to brick your phone twice now. At this point, the wire trick is easier from what I've heard.
[HTC EVO 3D] midnightmaraude:
Can u link me? I don't see any mention about having to brick it twice
[HTC EVO 3D] mpgrimm2:
If you go one page back you can see Closeone's reply HERE for how to do the "brick" step twice.

If you decide to use the Jbear Wire Trick, see Ramjet73's thread HERE.

Sidenote: @ closeone, can you or unknownforce pop in at the UltimateRecovery Tool thread? There is someone over there that has been waiting for a hand for quite a while. Thanks.
[HTC EVO 3D] JustinFields95:
Does this work on 1.57 version of HBOOT?
[HTC EVO 3D] mpgrimm2:
It's not known if it (vs Igor) works on virgin mobile Evo V, but Ramjet73's thread for Jbear works well for it. See previous post.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] ramjet73:
It's pronounced eye-gor and he works on virgins, but I'm not sure about the Evo V. ;)

ramjet73
[HTC EVO 3D] mpgrimm2:
Haha. Auto correct failed miserably.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] rodre12:
This will work for the htc evo v 4g right?
[HTC EVO 3D] mpgrimm2:
Unknown.

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

[Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] rodre12:
Can someone test this on the evo v i dont like the wire trick
[HTC EVO 3D] ramjet73:
If you read the instructions it requires GB RUU's and there is none for the Evo V, only the ICS version with hboot 1.57.

ramjet73
[HTC EVO 3D] Unknownforce:
The partition layout of the V (that sounds dirty) is something I'm unfamiliar with. I don't recommend doing this. If you can temp root it and get a partition layoutI can tell you whether or not it will work.
[HTC EVO 3D] rodre12:
How do i do that
[HTC EVO 3D] ramjet73:
The partition layout of the Virgin Mobile Evo V 4G should be the same as the Evo 3D since it has identical hardware, and can use some of the same firmware and ROM's. The baseband version for the current VM OTA is 1.09.00.0108, including the 1.58 hboot. Many users with that device have been using Evo 3D hboots and radios for a while.

But wouldn't using a Sprint GB RUU cause the same problems for Evo V users that Evo 3D users experienced last May when they tried to flash the leaked VM firmware? Doesn't the actual S-OFF process for this method depend on having a GB RUU installed?

ramjet73
[HTC EVO 3D] Unknownforce:
The layout could definitely still be different. I do agree that it's most likely that they are the same. But, you have to understand how the flashing works in recovery or fastboot... they don't flash by number, they flash by name... And then based on that name, somewhere in the device, it has a list of which one is which and then it's flashed to that place. So even though you can flash them to the device, it still might not be the same numbered layout.

Best thing to do would be to do a cat /proc/emmc in adb shell and make sure they are the same as the Sprint version... Below is the output from 2.89:

shell@android:/ $ cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p35: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p33: 00140200 00000200 "local"
mmcblk0p25: 06eb5c00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p29: 01400000 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p26: 00008000 00000200 "extra"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p20: 01000000 00000200 "adsp"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p27: 00400000 00000200 "modem_st1"
mmcblk0p28: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p34: 007ffa00 00000200 "udata_wimax"
shell@android:/ $

If they are the same, then the downgrade will likely work, if they are not the same, then it will probably not work.
[HTC EVO 3D] ramjet73:
So what GB RUU would a VM user flash and why wouldn't that cause the same kind of problems that flashing the VM firmware on the Evo 3D caused last May?

Perhaps you missed my previous post but there is no GB RUU for the VM Evo V and flashing the Sprint GB RUU would install the incorrect RFG_1.img and RFG_2.img files that caused problems for Evo 3D users.

ramjet73
[HTC EVO 3D] Unknownforce:
I had pointed out somewhere before that those 2 files don't actually flash, all the rfg's live inside the radio_config partition. rfg_0, 2, 4, 6, and 7 are all blank. rfg_1 stores the device unique information such as the meid and msl, rfg_3 stores a lot of the same information, and rfg_5 is the activation information used when the device communicates with the towers. I'm not even sure why they even include those files, because if it did flash the rfg_1 image, it would completely screw up the device. rfg_1 is device unique, it contains the meid, msl and other things that all make the device unique.

The VM Firmware that came out last may was a firmware that was specifically coded to change a device into a VM device. That's what that firmware was supposed to do. The Sprint releases of their software do not include such a forceful change in their firmwares. That's why we had the big problem of trying to revert back, because the VM stuff was the only one that had that forceful change.

My only guess is that it was most likely used as a patch by Sprint to offload their remaining stock of EVO 3D's and change them into the V devices they are now and re-branded them with the VM logos. I wouldn't be surprised if the RFG_1 on a V device still had the Sprint name in it.

Anyways, with all of that in mind, it's highly likely that it will work with all the Sprint software (any version) if done correctly, but without a VM device to test with, I cannot be certain.
[HTC EVO 3D] ramjet73:
Thanks for the explanation.

I don't know if anyone with an Evo V has tried flashing a Sprint RUU yet but there's always a first. I just didn't want anyone with an Evo V to have to go through what Sprint users experienced last May. I still remember how hyper some people got over that when they couldn't remove the VM branding.

Also, the CID for VM is SPCS_002 not the Sprint SPCS_001. Is that going to be a problem when a VM user still S-ON tries to flash the RUU or does the bricking mask that?

ramjet73
[HTC EVO 3D] Unknownforce:
That is a possibility, I don't know if the RUU checks the CID of it or not. I know the GSM devices do have this check... If it doesn't allow it because of the CID, I might try to figure out how to change the CID while it's bricked... But it also might be possible to just use the PG86IMG to bypass that CID check... I think just using the RUU exe has that check in it...

But again, I don't know anyone that's tried this yet... So I have nothing to go on...
[HTC EVO 3D] Remanifest:
Thank you for your work on this. Below is the output of cat /proc/emmc. There are differences between the EVO V 4G and EVO 3D CDMA. Block ID's are different, as are some of the sizes. EVO 3D CDMA also has an "extras" partition that is not present on my phone.

dev: size erasesize name
mmcblk0p34: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p32: 00140200 00000200 "local"
mmcblk0p25: 06ebde00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p33: 007ffa00 00000200 "udata_wimax"
[HTC EVO 3D] ramjet73:
I've found that the partition layout, and in the case of the misc partition even size, varies depending on what hboot is flashed. See this post which has several layouts for the Evo 3D, and I think you will find that the 1.50 version matches exactly what you posted, which I'm guessing was done with the JBear 1.50.5050 hboot. If you flash another bootloader the layout will be different.

ramjet73
[HTC EVO 3D] Unknownforce:
While this is true, it doesn't mean that it won't work. In fact, I'm fairly confident that it will work now judging by the layout provided.

With regards to extra and adsp, they are still there, they just don't have have them specifically labeled for the system to read in plain text like that. That's all. The partitions themselves and the data stored there is all still there.

The reason for the differences should be obvious, but I'll point it out for those that can't connect the dots. The ENG hboot was developed before the "release" versions were applied to the phones themselves. HTC has many different and more hboot versions than we have, they simply never released them all, they only release the final versions and they are typically the locked down ones. (1.30, 1.40, 1.50, 1.57, 1.58) The ENG hboots are not designed for public release. The only reason we have them is because it was leaked or mistakenly left on a development phone that made it's way out the door.

This is why the partition layout (block numbers) is different because the partition layout itself was likely not finalized when the ENG Hboot was developed.

(Technical section)

As to why there is now an "extra" partition, I don't know because they didn't even put anything in there... But, What I do know is that the partition itself took away from some of the cache partition. If you look at the sizes and add the new cache(p25) size (0x06eb5c00) to the extra(p26) size (0x8000) you get 0x06ebdc00 which is exactly 0x200 short of the old cache size of the original pre-ICS layout. (0x06ebde00) 0x200 is 512 bytes, which is most likely used to establish and identify the partition to the emmc itself. (all partitions probably have a 0x200 identifier attached to them) So it likely was also pulled from cache when they created this extra partition.

(End of Technical Section)

Anyways, as to the issue at hand, it looks like the layout changed from 1.57 to 1.58, because the V uses the 1.57 hboot IIRC. It appears V has the same partition layout as the Sprint's EVO 3D BEFORE ICS. So, in theory, the downgrade to Sprint's 1.13 ROM should work without issue on a V. They could then use Revolutionary to gain S-OFF, then re-flash the stock V ROM to get the firmware back to normal and then go from there, with S-OFF, they could flash a custom recovery, and start flashing roms like normal. You'll need to still use an unlocked hboot, like revolutionary, eng or jbear, but all hboot's other than 1.58 should theoretically work because the partition layouts are pretty much identical.
[HTC EVO 3D] ramjet73:
I think the layout that remanifest posted might have confused things a little because I believe it was done with the JBear 1.50.5050 hboot installed, which is based on the Sprint 1.50 version. If you compare the layout between the stock VM 1.57 and Sprint 1.58 hboots I think you will find them identical and with the March OTA installed VM users now have exactly the same 1.58 hboot as Sprint users.

Having said that, I agree with you that this is good news as far as the feasibility of this S-OFF method working for VM users, but my primary concern is still what the effect, if any, of flashing Sprint GB RUU's on a VM phone will be and we won't know that until a VM user tries it. ;)

ramjet73
[HTC EVO 3D] Unknownforce:
I don't think it will be a problem, because we can go from 1.58 (2.89/2.95 ICS stock) down to 1.40 (1.13 GB stock) without a problem on the Sprint model now that URT is updated to work with it properly. On top of that, we know the Sprint model can run the VM stock hboot (1.57) without a problem, with the correct ROM installed at least.

All things point to yes I think. :)
[HTC EVO 3D] Remanifest:
Would it provide more clarity for me to go back to 1.57.0000 or 1.58.0000 and run cat again? Just trying to add some clarity for the EVO V users - both of those HBOOTs are "stock" now, with the 1.58.0000 HBOOT coming with the 2.95 OTA.
[HTC EVO 3D] ramjet73:
That would provide definitive proof that the 1.57 hboot and the VM version of the 1.58 hboot (which is identical to the Sprint 1.58 version) have the same partition configuration as the Sprint stock ICS bootloader. I'm 99.9% sure that is the case, but if you can post the /proc/emmc output for the Evo V with the 1.57 hboot installed I don't think it's necessary to do the 1.58 version.

ramjet73
[HTC EVO 3D] Remanifest:
Here's the output on the 1.57.0000 HBOOT with the EVO V 4G:

dev: size erasesize name
mmcblk0p35: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p33: 00140200 00000200 "local"
mmcblk0p25: 06eb5c00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p29: 01400000 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p26: 00008000 00000200 "extra"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p20: 01000000 00000200 "adsp"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p27: 00400000 00000200 "modem_st1"
mmcblk0p28: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p34: 007ffa00 00000200 "udata_wimax"

Exactly the same as the EVO 3D CDMA. On 1.58.0000, I got a slight difference running diff, but I don't see the issue myself - maybe it's just too late:

1.58.0000 EVO V 4G

dev: size erasesize name
mmcblk0p35: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p33: 00140200 00000200 "local"
mmcblk0p25: 06eb5c00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p29: 01400000 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p26: 00008000 00000200 "extra"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p20: 01000000 00000200 "adsp"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p27: 00400000 00000200 "modem_st1"
mmcblk0p28: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p34: 007ffa00 00000200 "udata_wimax"
[HTC EVO 3D] Unknownforce:
They are in fact identical. There should be no problem using a sprint RUU and going back to 1.13 GB. Do we have any V users that are wanting to do this? I say go! ;)
[HTC EVO 3D] ramjet73:
Hopefully an Evo V user who wants S-OFF and has been putting off doing the wire trick will be willing to give this method a try. I made this post in a thread on the Evo V All Things Root forum at androidforums.com to let those users know that you are ready to try it.

ramjet73
[HTC EVO 3D] Remanifest:
If nobody's done it by this weekend, I'll turn S-ON again and give it a go!

---------- Post added at 09:03 PM ---------- Previous post was at 08:51 PM ----------

One question before I begin - perhaps I overlooked it, but is there a standalone version (non-livecd) of the binary that I can use on an existing Linux installation?

---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------

Ah, belay my last... I see it's in the other thread - I'll be using that binary, and will NOT be using the LiveCD; presuming operation is identical anyhow.
[HTC EVO 3D] Unknownforce:
It's fully functional as long as ncurses libraries are installed. The functionality of the radio fix is lost when ncurses aren't present. (adb and fastboot need these)

Let us know how that goes ;)
[HTC EVO 3D] ChrisFSU:
I am currently on HBOOT 1.58 with S-On unlocked through HTCDev.

I am trying to install a rom which requires 1.5 or earlier. Can I use this CD to downgrade my HBOOT to 1.5?

Thanks.
[HTC EVO 3D] Unknownforce:
Short answer is yes, but the tool from this thread is obsolete. Use the latest one in the Ultimate Recovery Tool thread, click the CDMA in my signature.

Long answer is... You will need to relock the bootloader and return to a stock rom. After this you can then use the tool to downgrade to 1.4, then use revolutionary to S-OFF the device and then you can flash whatever hboot you want. But, you should know that 1.5 offers no noticeable difference than 1.4, and revolutionary hboot is unlocked, if you're going to use an earlier hboot, I recommend sticking with revolutionary's hboot after gaining S-OFF.
[HTC EVO 3D] ChrisFSU:
thanks for the reply. Where can I find a stock rom?

EDIT: I found this thread explaining how it's done (http://xdaforums.com/showthread.php?t=2136964) except it says S-Off only. I can't rename the zip and boot into bootloader with S-On? How do I go about it if not?

Also, will any of the RUUs work. I already have the latest one downloaded... just want to make sure I don't have to download an older version.

Thanks again.
[HTC EVO 3D] coal686:
Ramjet73 links to the RUU in his thread. That will get you back to stock. http://xdaforums.com/showthread.php?t=1889438
[HTC EVO 3D] ChrisFSU:
I edited my post as you were replying. ha. Here's what I edited...

EDIT: I found this thread explaining how it's done (http://xdaforums.com/show....php?t=2136964) except it says S-Off only. I can't rename the zip and boot into bootloader with S-On? How do I go about it if not?

Also, will any of the RUUs work. I already have the latest one downloaded... just want to make sure I don't have to download an older version.

Thanks again.
[HTC EVO 3D] Unknownforce:
To return to stock, only a version equal to or higher will work. But you will still need the 1.13 RUU also for after you downgrade to get back to a bootable rom.
[HTC EVO 3D] ChrisFSU:
Great, thanks again. I am downloading the proper RUU now.

One last thing... can I just rename the RUU to PG86IMG.zip and boot into bootloader, even if I have S-On, Unlocked?
[HTC EVO 3D] mpgrimm2:
There are 2 basic versions of the RUU's, a Ruu.exe (pc based with phone in "Fastboot USB" mode) and Ruu.zip (renamed to PG86IMG.zip and run from phone's bootloader & root of sdcard). The "zip" version is actually "extracted" from the .exe version right before it is flashed on the phone by the pc installer.

To answer your question, if the file you are using started as a zip like PG86IMG_Sprint_2.89.zip then yes, just rename it and flash as suggested. The reason they are posted with different names is because you can't have a bunch of files on your phone/pc all named exactly PG86IMG.zip even though they need to be named that to be flashed by the bootloader (just rename it back afterwards so you keep track or work with/delete a copy). Same holds true for flashing "Firmware & Radio Only" files, "Hboot Only" files, etc that the devs and advanced users post for everyone; they get renamed to PG86IMG.zip for flashing.

Keep in mind that Unknownforce has an updated version of his Ultimate Recovery/Downgrade Tool v3.1 that also has a LiveCd version and should do the same thing as this without the "bricking it twice" step (i think).
[HTC EVO 3D] Unknownforce:
Correct, and also in that thread is a much smaller signed zip file to use for bricking purposes, but the power pull doesn't work very well with it, unless you wait a long time before pressing volume up to update...

I've discovered that the time the device remains on while flashing the update when there is no battery in seems to be somehow linked to the time it's plugged in without a battery BEFORE you hit the volume up key to update. (Might need to read that a couple times to understand what I mean.) But, in other words the device will not shut off

before it's updating

, but the shorter you have it plugged in without a battery before you press volume up, the shorter the device will stay on without a battery while it's updating/flashing...

He's a little step by step number chart to understand what I'm saying here...

1.) Boot to bootloader, phone sees PG86IMG, processes it

2.) Pull off cover, plug in to power, pull battery

3.) Press Volume up to Update

4.) Pull cord at the right time

Now, BETWEEN steps 2 and 3 is the time that the phone is on the charger power without the battery in. THIS time is somehow linked to the time that the phone will stay on AFTER step 3. Eventually it will shut off after step 3, regardless of whether or not you pull the power cord.

So because the new file is so small and it loads it that quick, what happens is that the device shuts off prematurely, before you can even get to the right time to interrupt the bootloader flash. This could be helpful to find the exact time to wait till pressing volume up, but it's just easier to pull the battery at the right time to brick it, cause then you don't even need the power cord at all...
[HTC EVO 3D] mpgrimm2:
@Unknownforce,

Dipping back into my "old" electronics toobag, I suspect the "time" between 2 & 3 and then pulling the power at 4 has to do with internal capacitors on the mainboard's charging/power supply circuit. Basically there is an "RC Time Constant" and percent of charge based on how long it has been plugged in without the battery "Charging" and then once unplugged how long until it "discharges" and shuts off.

So, (without the battery in) if you leave it plugged in for 2 minutes before updating/pulling the cord, it should stay powered longer than if you only waited 30 seconds before updating/pulling the cord (power source).
[HTC EVO 3D] Unknownforce:
Very interesting. I'm not much of an electrician myself. But that's most likely it.

The capacitors start charging even from the battery, and then get a little more from the charger, but once it starts updating it activates more parts of the emmc and then pulls more charge than it can maintain from the just the charger... and essentially becomes a "leaky bucket" where it's discharging at a slightly higher rate than the rate that it can charge and then once it runs out on the capacitors, the power cord alone can't provide enough voltage to power everything it needs to and thus shuts off.