yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] Tekn010933:
Very useful info and thanks for sharing, although I learned while back to "never" run ota through there sever's. Would get the modified one's here since it can be customize, our methods are not as same with what you had performed prior to your hardware replacement's.

But I had started this thread and even documented it on video to show that it worked for me, so I can only try to help as much as I can.

RUU 4.53.651.1

And how are you loading the RUU file's?

although I keep forgeting to change My signature to 4.54 :)
[EVO 4G General] Captain_Throwback:
What happens when you put the 4.53 PC36IMG.zip on the root of your SD Card, and boot into the bootloader to update? Have you tried that way yet?
[EVO 4G General] evoxsin:
I've tried either the sync method on the pc and got the error 104 I believe such said the version was older(although it was the same) it just did not finish and prompt me to exit

yes I have it completes the flash on bootloader. But right after that it tries to ally the update and I get another error I try to remember what the error was from memory but I believe it stated wrong xxxxx file and I have to reboot. I can try again and come back with error if you would like.

further more I would like to add if at all it matters everyone who has been having issues before me have been on evt3 bootloader. Gosh am I so far back.

thank you both for the fast replies.

what now? How can I trick the hex to run and downgrade my hboot if it won't complete
[EVO 4G General] Captain_Throwback:
The error message might help, but you said it does complete the Bootloader update? If that's the case, your HBOOT version should be 2.16, not 6.17. Unless you're flashing the wrong file.
[EVO 4G General] Tekn010933:
What did for me was replaced the bootload back to stock, as shown in the OP.
[EVO 4G General] evoxsin:
I am attempting to flash the file posted on post 49 by tekn0 via bootloader by renaming it to pc36img method at this eye moment n will report with the error, from my understanding this will not change the hboot but the hex file. Correct me if I'm wrong please

bootloading your file now, will report in this post

update, it scans my card for the zip what's a pc36diag.zip? As it attempts to look for it then does not recognize it or wrong file. Anyway it then finds the imgzip and the progress bar at the top right begins to fill up it goes all the way assuming it loaded/ next screen states again the imgzip and states

main version is older!

update fail!

reboot device?

all I want to do is give back the lemons I was given. :-P

---------- Post added at 06:56 PM ---------- Previous post was at 06:43 PM ----------

are you asking if the 4.53 ruu/zip depending on how it is loaded will change my hboot? I believe you made a hex file to trick the bootloader to accept a zip believing it was something it isn't, that's what I need to do. I wish to ursurper the file so I can change the hboot to a rev.io rootable
[EVO 4G General] Tekn010933:
See that your EV has changed, have you already tried from Fastboot with debuggin on and be sure to have the drivers installed. but it does not hurt to use the hex from the OP again since your spec's has changed.
[EVO 4G General] Tekn010933:
That's what I was looking at, error" but before he did not have the hex ran onto what stage his device is on current.
[EVO 4G General] evoxsin:
you are incorrect sir, I believe I've been on the same evt since before anything was attempted, bootloader does complete the first stage of downloading but does not install to the device on the bootloader it calls this stage "updating" and that's when it fails.

as I've mentioned the best method should be to downgrade the hboot correct? But this does not do anything when renaming the hex file to pc36img. I wish the captain would edit the hex file for my set up.

or I would need to do the ruu method once more on a desktop(already done 3times) but I get the same error that the version is older
[EVO 4G General] Tekn010933:
whe the hex was ran, it did not ask to "parsing?" or did it read "no img found?" I am asking due to a simple erro I did in the past of renaming zip's, I had did this from a file explorer on my device and at the end .zip, well the problem was with this I did not know that the app auto put's .zip on for me.

So scanning and keeps giving me error's, after some hair pulling, head pounding, I had to go back and surely saw. The file say's pc36img.zip.zip, but it's worth to check everything and everything as we proceed..
[EVO 4G General] Tekn010933:
and was refering to the evt posted here.
[EVO 4G General] Captain_Throwback:
You shouldn't need a hex edited HBOOT file. The stock HBOOT 2.16 WILL overwrite my hex edited version. That's what you need to flash, which is included in the stock PC36IMG.zip I posted on the first page. Even if the ROM doesn't update, the bootloader should. I can post a link to the file I'm referring to, if it would help.

EDIT: This is the post I'm referring to. The PC36IMG should overwrite the 6.17 hex-edited HBOOT.
[EVO 4G General] evoxsin:
it does not say parshing on the bootloder, I was aware of the double extension issue some were having but that's not the case here astro explorer does not add a zip unless you tell it too. But I'll leave that alone n report back. Assuming it's already in zip format I would not even need to touch the extension of the file. Since even the ruu I downloaded were in zip format and also used astro to rename a d those worked I don't see how the hex should be different but I'll try again, no harm in that. I wish I saw the "parshing" but last time I got an error. Also I've tried the op multilink hex file and the other two mentioned by captain_throwback that he linked and attached on page one

I go into overloaded and it scans my card nothing happens then I go back to the options to fastboot/recovery/clearstorage/airlock/hbootusb

again no parshing
[EVO 4G General] Captain_Throwback:
So it's not even recognizing the PC36IMG when you put it on the card? That sounds like it's either an SD Card issue or an extension issue, like Tekn said. It should at least recognize the file, if it's on the card correctly.
[EVO 4G General] evoxsin:
it says loading then no parshing back to fastboot hboot
[EVO 4G General] Captain_Throwback:
Give me a couple of minutes - I'll make you a quick zip that has just the stock HBOOT in PC36IMG.zip format, and you can try that to see if it'll downgrade your HBOOT. You said your HBOOT is still 6.17, right?
[EVO 4G General] evoxsin:
I agree with you both gentlemen, but it does read the stock ruu room when fastbooted. Why will it not read the hex? The error when reading the edited hex says no IMG or wrong IMG I agree with you both that its not reading the file, what if the file is corrupt? This was done with all of the 3 hex files on page one. Does anyone have the checksum?

and captain_throwback as you said I would not need the hex since the ruu edited name to fastboot as a IMG zip would flash me to stock with an older built, here is where it gets interesting, the error I get when in overloaded is "the file is older" :eek:

---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------

yes sir, it is. I believe that's the custom boot for those who rooted the rev.io method.
[EVO 4G General] Captain_Throwback:
There are a lot of files on the first page, so unfortunately, I'm not sure I know what files you're referring to. THe PC36IMG I was talking about from the 1st page was not hex-edited at all - it is a stock ROM. If your HBOOT can't read that, then that's a different problem entirely. Clearly, whichever hex-edited file you ran worked, because you have the modded HBOOT and S-ON, but at this point, you can ONLY flash a stock update, because with S-ON, HTC's signature checking is now enabled, so you won't be able to flash anything that's unsigned. That's why I'm confused as to why the stock update won't work, but it could be because of the software version your device has. You may have to wait until the official 4.54 RUU surfaces to be able to re-root. In the meantime, I'll try and put a zip together for you, but it may not work, because of the signature issue I mentioned above.

EDIT: Nope, I can't create a zip that includes the necessary info from 4.54 to be flashed as stock, due to the signature of the zip file. If the stock zips I linked to earlier don't work, it looks like you'll have to wait for a new RUU to emerge.

EDIT 2: As I read back to your original post, I'm still confused as to how you ended up with the wrong HBOOT version. If you followed the complete unrooting method, you should've had the stock HBOOT, at the end of the full unrooting process, right? Isn't the last step to flash a completely stock ROM, to restore the stock ROM and HBOOT? Did you just neglect to perform that step, or is it missing from the OP?
[EVO 4G General] evoxsin:
that's the main concern I predicted, I apologize if this is very inconvenient for you members lending me a hand. I mentioned before that this may infact be the culprit as to why it will not install the stock Rom if the error I've been getting is that the Rom in attempting to install is older than of course that's the issue, had I been able to get the hboot down to what the rev.io method accepts, I would be flashing a diff Rom with out the need to handshake a signature on the Rom.

I await for this magical file your working on, and if that does not work, then well hang up the lab coats untill the signed 4.54 ruu shows up.

I see your edited post, thank you for the attempt. I'll keep my eye out for the official file.....should not be too long- I hope.

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

there's numerous reasons as to why I may have the wrong hboot as I've questioned the steps I took to manage my dilemma. I may have not googled as great as I could have as my searches came up with people returning their devices to sprint for exchanges, in my case it was a repair, with hopes of the repair center having the screen in stock I would gain s-on and rush to the store, that I did! Being happy as a kid on xmas after they replaced my screen because the device said s-on the did their work, I flew home and was ready to root. here's the kicker my brother said, "hey do the update its just a software patch for security ull b able to root, I did n I rooted" so I did(is this where I screwed up?) maybe I should not have updated a stock patch if I wasn't on the stock hboot, and why did the security update not change the hboot. From 6.xx to 2.xx?

since then I have not been able to flash

so sir, I agree I believe it is because of the software issue not handshaking the rom.
[EVO 4G General] Captain_Throwback:
It appears there are two places where you may have gone wrong:

1. After you got your device to S-ON (prior to repairs), it seems you skipped the last step to get your HBOOT back to 2.16, which would've made it not matter whether you accepted the OTA update afterwards.

2. Since you didn't perform the above mentioned step, accepting the OTA update is now preventing you from updating anything, due to the version of HBOOT now installed on your device, in conjuction with the Software version.

So, I think the moral of the story here is, make sure you follow ALL of the steps in the unrooting process, and don't return the device until it's COMPLETELY stock. Also, NEVER take an OTA update if you're expecting to root your device.
[EVO 4G General] evoxsin:
do you think there may be hope if the official 4.54 ruu is signed and released I may be able to go back down in hboot?

no matter how many ways I may have screwed up I take full responsibility and saying I am at fault. I was looking for a loophole

Edit-

I fear that even with that file I wont be able to flash because of the hboot version. or if rev.io makes an update to their exe then it would root/s off on 6.17?
[EVO 4G General] Captain_Throwback:
Yes, I believe that when the 4.54 RUU is released, you *should* be able to restore stock HBOOT. I'll be sure to update my post on the first page with the latest version once available.
[EVO 4G General] Tekn010933:
forgive as I am poping in and out, flashing for a review at the moment. But 6.17 would still be able to overturn, but will try that 4.54 first see how it goes. uploading it for you if Throwback has gotten there already/
[EVO 4G General] evoxsin:
That sounds like the light shining at the end of the tunnel

Thank you kind sir

I wont ask for eta...thats a bad omen :p

You have a signed 4.54?
[EVO 4G General] Tekn010933:
ah Think it's already released. uploading a mirrior and checking it first before I can post it, don't want mishap's..
[EVO 4G General] Tekn010933:
I am 20mins to finishing up this review, after that since I only have one evo(Suks!) I will check the RUU throughly and flash it myself, now if throwback have something in between this time feel free for he is a good name on here. 4.54 mirror is uploading 17% now and my review will be done just in time for me to check the file...
[EVO 4G General] Captain_Throwback:
Where did you find it? I haven't seen it.
[EVO 4G General] Tekn010933:
c:/RUU/4.54.651.1 :)
[EVO 4G General] Captain_Throwback:
That sounds like the rooted version someone built - you sure that's an official release?
[EVO 4G General] evoxsin:
....if you flash and its confirmed. Ill be a test subject. I mean whats the worst that can happen. Assuming its the right radio, ill try once your finished.

I do believe ive seen the 4.54 before, and when attempting to run ot in desktop ruu I got a do you wish to flash from 4.54 to this (4.54) then I accepted and errored with the file isnolder than current one...how more updated can I be:rolleyes:
[EVO 4G General] Tekn010933:
Bro, if I could only remeber the link you know I would've post it already. My shift schedule and school together with family has got me all tied up, I can assure you I will send you the link to check too once done uploading.

I am not like that Bro? was only kidding what I posted earlier, but honestly I don't have the link just teh RUU/4.54 it's been about 2weeks now and I have not even touched it to check before posting..
[EVO 4G General] Tekn010933:
Your at 6.17 I am at 6.16, This should not be a problem.. Hope you understand what I have to do here, put my device in the stage you are at??
[EVO 4G General] Captain_Throwback:
Ah, got it. If you can PM me a link, I can take a look at it too.
[EVO 4G General] evoxsin:
Yes and I.really appreciate the.help
[EVO 4G General] Tekn010933:
will do 80%
[EVO 4G General] Tekn010933:
We at 80%...
[EVO 4G General] Tekn010933:
sorry took long kinday busy here, but was trying tosend to Throwback too to get a second opinion. I had installed it and it's 4.54 stock for sure have not seen this in awhile :)
[EVO 4G General] Tekn010933:
Am trying to PM you it's not coming through,

Stock 4.54.651.1 ROm
[EVO 4G General] evoxsin:
I assume the file above can be flashed/installed by renaming it to the img and going trough the stock bootloader correct? Ill wait to see what throwback can give me imput on this procedure
[EVO 4G General] Tekn010933:
yes it can be flashed as pc36 and I know it should kick that 6.17 off..
[EVO 4G General] evoxsin:
The second link takes me to a sign In page user name/password prompt, but im downloading the file at the momment just to keep it ready in case throwback checks out
[EVO 4G General] Tekn010933:
File about 197.65MB, and It's the link I replied to post #86? multiuploads is the one working for me at the moment.
[EVO 4G General] Captain_Throwback:
I'm downloading now and will report back once I take a look.
[EVO 4G General] evoxsin:
Gentlemen, I dont kno if its an official release. But I tried flashing and I got the same results. It scans my card. Finds the img zip then loads it with the blue progress bar up at the top right part of the screen. When it reaches the top it changes into the hboot/checking img then goes.back to the four vol up/vol down selections....then I have to either fastboot to try and flash again or reboot bootloader or jus reboot in general. No "complete" or .....what is missing?
[EVO 4G General] Captain_Throwback:
As I suspected, it is not an official release. Looks like you'll still have to wait a bit.
[EVO 4G General] evoxsin:
Thats understandable. im patient

Can you breakdown how an official signed 4.54 will revert my hboot back to 2.xx would that be like if I had ota' dl the update wich in turn breaks root? Is that what im being pointed to duplicate that kind of process? In all honesty....if that does not work....would I have to wait for htc to release another ota and update with their file(god forbid I do that again, the reason I did it this last time was because that update was still in the 2.xx hboot allowing users to still rev.io root as my brother did on his device)
[EVO 4G General] Captain_Throwback:
Essentially, yes. As I explained before, the HBOOT you currently have is an unofficial, unsigned version, which can only be overwritten by an official signed version (at least when you're S-ON). Apparently, your software version is preventing the previous official version from overwriting it (though I'm still not really sure why). So, an official ROM, based on the same software version you already have installed (or newer) should successfully overwrite your current bootloader.
[EVO 4G General] Tekn010933:
Guys I am on this and I can say it is stock, as I had flashed it there is nothing touched with this rom I am looking and going through it, Size is 197 MB (207,253,921 bytes), is this the same size you two have?
[EVO 4G General] Tekn010933:
"When it reaches the top it changes into the hboot/checking img then goes.back to the four vol up/vol down selections....then I have to either fastboot to try and flash again or reboot bootloader or jus reboot in general. No "complete" or .....what is missing?"

Sorry to hear that, thought it would work on yours for sure, Can assure that this is the Stock I am on right now since I had to flash install it to make sure it was not a bad file I am giving out..
[EVO 4G General] Captain_Throwback:
It might be stock, but it is not an official, SIGNED HTC release, which is what it needs to be to update the HBOOT.

The easiest way to tell is that within the zip file, with an official release, are img files, as well as android_info.txt.

Besides that, the zip you posted doesn't even include a flashable bootloader - it's only the system & data.
[EVO 4G General] Tekn010933:
Yes I am Very aware of HTC signature's Sir, were you able to download the file all the way through?
[EVO 4G General] evoxsin:
Yes tech0 that is the same file I have that you uploaded. I am sure it is a stock unmodified rom...that can be flashed by bootloader/cwm/ra mon in zip format but as its been addresed it needs to be signed for "secure on" devices for the zip to "handshake" checking/verification and authenticate the update to be validated and installed. Thats where I fAil because I have secure on.

Ill wait you both have been more than helpfull and polite with me. Ill set to "receive updates" on this topic in case the posts get updated with the signed 4.54 img.

Ps. There was no md5 checksum on the file posted above. I wanted to check it.
[EVO 4G General] AngusTutnbull:
I hope this isnt to off topic since we are talking about getting our lhones warrnty use ready, but will the warrnty fix a broken speaker? It sounds all crackly. And also will it void my warrnty if I did the mod where you scrape of the plastic around the back to reveal the red? Thanks in advance! Cant wait to get my phone fixed!!
[EVO 4G General] Tekn010933:
Give them a ring and see what or what not, save you some time going in. I know screens, usb, hdmi, button keys on the side sorry that's all I can remember for now.
[EVO 4G General] Tekn010933:
I am checking this and yes it is "6.17 S-ON" that was taken off by the RUU 4.53 with S-ON and returnded BL back to 2.15, had to check on Video Guide in the "OP" part 3 of 3 From 12:46 to 14:04 you will see that it did exactly that.
[EVO 4G General] evoxsin:
But in my situation until a signed zip is released then can u get my hboot down to 2.xx from 6.17. I am on 4.54 software and it being the newest will not install/flash an older file unless it is the same and signed.

Back to your post. The diff between that situation and mine is the software differance.
[EVO 4G General] Tekn010933:
Yes correct, and the Root method will not work anymore correct? on 6.17 that is?
[EVO 4G General] evoxsin:
Yes at the moment. Until the 4.54 gets released in zip
[EVO 4G General] Captain_Throwback:
RUU has been posted (thanks to Football!).

I've already refreshed my link to the RUU here: http://xdaforums.com/showpost.php?p=17206283&postcount=5

I'm in the process of downloading and extracting the PC36IMG.zip. Once complete, I will update the above mentioned post.

The RUU should work for you, though.
[EVO 4G General] evoxsin:
I'm away from home and I'm on the road. Can you please link me to the post where you will edit/update with the img file?

Edit- disregard. I see the link is the post. I await to download it later this morning. Thank you
[EVO 4G General] Captain_Throwback:
Link in Post 5 updated. Info below for easy access:

PC36IMG.zip for latest ROM (4.54.651.1) - Rename to PC36IMG.zip, place on root of SD card, then flash from bootloader: Dropbox Direct Link

MD5: 7A989BA6535DAF452BDACD9618BC9CE2
[EVO 4G General] evoxsin:
I ran into a snag. The direct dropbox link is the 4.53 update. It said so on the zip title when downloaded. I did it anyway with same results of "version is older" did you mix up the links?
[EVO 4G General] Captain_Throwback:
The link isn't 4.53, it's 4.54 - I checked it twice, and just now again.

Perhaps you downloaded it before I'd finished updating the post? I updated the RUU link first, but now they're both definitely up to date.
[EVO 4G General] Tekn010933:
Thank you Football with another one.. will update
[EVO 4G General] evoxsin:
That was the case. I dowloaded the file before you had finiahed editing the post I apologize. Im dowloading all files to update and re root. Will report back on this post with and update.

update I downloaded the IMG.zip and it flashed my hboot back down, then I re ran rev.io and gained s-off and my hboot changed to 6.16 wich I thought was odd because the first time I ran rev.io root, the hboot was 6.17. Anyways long story short, thanks guys for being far above helpfull and patient. I'm now re rooted and running a Rom.
[EVO 4G General] Tekn010933:
Great, uploading mirror's.
[EVO 4G General] DrizzyGadget:
Can't remove SuperUser after unroot

Having a real problem. Followed unroot method, managed to get S-On, but phone still rooted. SuperUser permissions still available and everything else. Did a factory reset and still have same problem. Can't fully unroot phone and therefore cant update evo from 4.24 to 4.53. Tried to delete superuser.apk via Root Explorer, but after soft reset, superuser icon still in app drawer and still have full root privileges. Would really appreciate a way to fully unroot and remove superuser so I can update and sell phone back to Sprint.
[EVO 4G General] Tekn010933:
Ok, after you recvd your security on now you run the RUU pc36img zip at the HBoot screen.

The latest too is attched in the OP 4.54.651.1.
[EVO 4G General] Journeyman83:
Not Rooting Evo 4g with White Back

Has anyone had trouble rooting the Evo 4g with the white backing on it? I've successfully rooted two regular EVO 4Gs, but can't root two others with the white back. Nothing has changed between all the phones. Ideas?
[EVO 4G General] Tekn010933:
What is the differences in "spec's?"