i have no idea what your post means? so are you confirming it works?
In fact, you could actually flash the PC36IMG.zip and then install the official OTAs straight from HTC using the on-phone update process. Since neither of the OTAs included an HBOOT image, you'd still have the engineering HBOOT at the end of the OTA updates, so you could just use fastboot to flash the Amon RA recovery and then use the recovery to install the su-2.1-e-unsecure-signed.zip, and poof, you'd have root. The only foot in the door you need is the engineering HBOOT, and like I said, neither of the official OTAs touch it.*shrug* Really no credit is due to me. These files are almost straight from HTC. The only change I made to the OTAs was to add one line so they don't blow away the setuid-root permissions on /system/xbin/su.
no 4g doesnt work, it goes on, then starts to scan and then goes off!i have no idea what your post means? so are you confirming it works?
You're using the released HBOOT, not the engineering one. Have you tried running the RUU exe?hboot version: 0.79.0000
Whenever I try to flash, I get a signature verification failure, or a remote: not allowed
Any ideas?
You're using the released HBOOT, not the engineering one. Have you tried running the RUU exe?
I don't want any donations. Believe it or not, this was actually insanely easy to put together. I just needed to have the right knowledge about how all this works, which I've been accruing over the past few days.
If you have only the released HBOOT (so fastboot won't flash anything) and a broken recovery and a broken system, then yeah, you're hosed.I think I'm hosed. Everytime I try to flash something, I get a signature verification failed, or a "Not Allowed" for example when I try to boot into recovery. It seems as though I lost all permissions. I was holding out some hope since I still had fastboot access, but that appears to be a dead end as well.
In fact, you could actually flash the PC36IMG.zip and then install the official OTAs straight from HTC using the on-phone update process. Since neither of the OTAs included an HBOOT image, you'd still have the engineering HBOOT at the end of the OTA updates, so you could just use fastboot to flash the Amon RA recovery and then use the recovery to install the su-2.1-e-unsecure-signed.zip, and poof, you'd have root. The only foot in the door you need is the engineering HBOOT, and like I said, neither of the official OTAs touch it.
If you're looking for a way to have working WiMAX with the 1.47.651.1 update and keep your root access, try this. It exhibits some interesting behavior at the end that is not seen with other update methods, which leads me to believe that this method does correctly upgrade the WiMAX. Awaiting confirmation of this from someone.
Step 1: Revert to the initial release of everything
This PC36IMG.zip contains all the original firmwares from the first released RUU (hboot, boot, recovery, system, userdata, microprocessor, touch panel, radio, and WiMAX), except the HBOOT has been replaced with the one from the engineering build (to give you unlocked NAND) and the recovery has been replaced with Amon RA 1.7.0.1 (so you can flash updates signed with the test keys).
.[/B][/SIZE]
- Download this file, rename it PC36IMG.zip, and put it on the root of your SD card however you like.
- PC36IMG-1.32.651.1_eng-hboot_RA-1.7.0.1.zip (md5=413285641ee70e8c197f38cea649205b)
- Power off your phone.
- Hold down the Volume Down and Power buttons until the white screen appears.
- HBOOT will scan the PC36IMG.zip file. You'll see a blue progress bar on the right side of the screen.
- When it's finished scanning, it will ask if you want to start the update. Press the Volume Up button to answer Yes.
- Wait a while for it to flash all the images.
- When it finishes and asks if you want to reboot the device, press the Volume Up button to answer Yes.
- Your device is brand new again, except you have unlocked NAND and a custom recovery.
- Delete the PC36IMG.zip file from your SD card.
Total control over the phone comes from fastboot, which is a utility in two parts: half of it lives on the phone as a piece of HBOOT, and the other half lives on the computer as the fastboot program. The release version of HBOOT has its half of fastboot crippled. The engineering version of HBOOT has a fully working fastboot.With that said I somewhat follow what you are saying but wonder why (if I understand correctly) if replacing the HBOOT gives us total control over the phone why wasn't done from day one? Do I understand that the the "root hole" that was patched by the latest OTA did NOT touch the HBOOT and that in order for them to "plug" it in the future they would need to push a new HBOOT file?
if replacing the HBOOT gives us total control over the phone why wasn't done from day one? Do I understand that the the "root hole" that was patched by the latest OTA did NOT touch the HBOOT and that in order for them to "plug" it in the future they would need to push a new HBOOT file?
Total control over the phone comes from fastboot, which is a utility in two parts: half of it lives on the phone as a piece of HBOOT, and the other half lives on the computer as the fastboot program. The release version of HBOOT has its half of fastboot crippled. The engineering version of HBOOT has a fully working fastboot.
With a working fastboot, you can overwrite any partition on the NAND with anything you want. It's carte blanche. That's all you need to flash a new system image (in .img format). Or, you can flash a custom recovery and use it in turn to flash an update zip.
If HTC were to push out a new HBOOT in an OTA update, yes, it would cripple us. But we can always remove the HBOOT from the update before applying it, so it really wouldn't do them any good to try it. (Hear that, HTC?! Don't bother!)
To make changes to /system, you have to remount it read/write.
- After switching to a root shell (# prompt), type mount and press Enter.
- Look for a line that includes the word /system. On that line, look at the part that says /dev/block/mtdblockN, where N is a digit. That is the partition that your system lives on.
- Type "mount -o remount,rw -t yaffs2 /dev/block/mtdblockN /system", substituting the digit you saw in the previous step for N.
- Now your system is mounted read/write and you can make changes. Proceed cautiously.
If you have the engineering HBOOT, you can flash anything you want at any time. That's why it's so crucial to have it.
The point of no return looks like this:
- You have the release HBOOT, AND
- You are running system 1.47.*, AND
- You have the stock recovery, AND
- You do not have root access.
In other words, if one or more of the following are true, you can get all the rest:
- You have the engineering HBOOT, OR
- You are running system 1.32.*, OR
- You have a custom recovery, OR
- You have root access.
I did a back up of original stock right after I rooted, will running it be a problem ? thank you for your answers, bricking in not a option.
hello whitslack i was referred to you from Captain_throwback here is my Dilemma
i have a boot looping evo 4g phone with corrupted nv we copied the nv from 1
sprint phone to this evo and that what caused the boot loop. now we are trying to get it back up and running as my life depends on it lol.. my phone status is
*** UNLOCKED ***
Supersonic EVT2-3 Ship S-on
Hboot-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL03_16ac
RADIO-2.15.00.12.19
Dec 21 2011,12:50:32
hewre is a clip from my previous conversation with Captain_throwback
<Captain_throwback> Yeah, that's not going to work. You're not fully NAND unlocked, so you can only flash zips that have a main version that's exactly the same as your current version. Even then, you can only flash to the unlocked partitions. I was suggesting you go to that other thread I linked so you could try to flash that nv.img (not sure if that's possible or not, but that's your best shot at this point). You need to find the right nv.img to flash. I don't know anything about that; that's why I suggested contacting the guy from the other thread.
PLease advise and be my Savior please please