Related
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
api1996 said:
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Using fastboot from the PC, as in
Code:
fastboot flash hboot name-of-hboot-image.nb0
(The phone needs to be in FASTBOOT USB mode (coldstart with Send+End), and an acceptable USB driver needs to be installed on a Windows PC)
The S-OFF bootloader is happy to let you replace itself - it is running in memory when you interact with it, not directly from the NAND flash memory.
You can find the .nb0 files inside any of the HTC leak PB00IMG.ZIP ROMs, or the "rom.zip" files embedded within the RUUs. (Note that the built-in Windows "compressed folder" methods for extracting a zip file will not work with these HTC .zip files because of the way that HTC "signs" these zip files, but the 7zip Utiltity for Windows will work).
The 1.47.0000 S-ON bootloaders are only found in the MR1 and MR2 RUUs; all of the "Leak" PB00IMG.ZIP files from HTC (Leak-V1,-V2, and -V3) contain the 1.49.0000 S-ON bootloader.
[SIZE=+1]Please be aware that flashing the bootloader is the single most dangerous thing you can do to your phone, and that if you flash a corrupted file to the bootloader you will certainly hard-brick the device. You absolutely must VERIFY THE MD5 SIGNATURE of the bootloader .nb0 image file before using it with fastboot! Fastboot provides you absolutely no protection from errors! YOU HAVE BEEN WARNED! You can find checksums listed in this reference post[/SIZE]
For clarity, I will repeat them here:
Code:
RUU___MR1 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
RUU___MR2 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
Leak___V1 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Root_Leak 22d3c7082811170e70f308e3213b5d1f hboot_7501a_1.49.2000_100124.nb0
Leak___V2 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Leak___V3 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
bftb0
PS I could swear I wrote a post essentially identical to this one within the last week
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
api1996 said:
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
Click to expand...
Click to collapse
[ Edit ] Updated - check Consolidated HTC Eris RUU/OTA/ROM URLs for the MR1 or MR2 PB00IMG.ZIP files - if you haven't already done the steps below. cheers! bftb0
I don't have a download link right now. If you want to wait a couple days, maybe I'll have something more convenient. In the meantime, the way to get these files is to run the associated RUU utility - but not all the way through. More on that in a second.
You can get the MR2 (1.17.605.1) RUU utility from this folder at shipped-roms.com - the MR2 link is the RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed_with_driver.exe link.
OK, now how do you "get" the PB00IMG.zip file out of the RUU?
Simple. You run the RUU right up to the point where you would normally be starting the install to the phone - but you don't do that. Leave the RUU running, don't terminate it yet. The point of doing this is so that the RUU unpacks all the temporary files it is going to use - including the "rom.zip" file. It puts all this unpacked junk in two temporary folders underneath your Windows user area, perhaps at
C:\Documents and Settings\<your_windows_user_name_here>\Local Settings\Temp
use your windows search capability to look for a big "rom.zip" file underneath there. (The two top-level folders will have long names that look like Windows registry keys). Note that you may have to diddle with your Windows Explorer folder settings to "Display Hidden Files".
Now copy the "rom.zip" file to some other location on your hard drive, and when the copy is complete, exit the RUU utility. (You can't do this until you have copied the file someplace else first, because all the temporary files get wiped when you exit the RUU).
You can then rename the "rom.zip" file to PB00IMG.ZIP. If I am not mistaken, the MD5 checksum of that particular (1.17.605.1) "rom.zip" file will be 9e9ad31f01bbcb05157443287f4f38dd
bftb0
PS. Note the "_with_driver.exe" part of the RUU file name. All the RUUs attempt to install a USB driver for the Eris on to your PC. Since MR1 and MR2 came out one year ago - a couple months after the consumer release of Windows 7, the drivers might not be the same quality as whatever you have on your machine now (if it in fact installs the driver despite the presence of an existing driver). Just a heads up in case it tries to kang a crappy driver into your Windoze box. You might want to take a restore point just before running the RUU in case you find you need to un-kang the driver from your PC.
Thanks for the download links. I had just extracted the rom.zip and found the bootloader and figgured that I should check the tread one more time. That's when I saw the edit! I guess I just have bad timing . Anyway, I went ahead and extracted the bootloader, here's a download link for the 1.47 S-ON bootloader from the MR2 update for anyone who wants it: http://www.multiupload.com/9300LRSFZP
Thanks
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
bftb0 said:
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
Click to expand...
Click to collapse
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
api1996 said:
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
. I thought I had read that someplace recently! LOL
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
USSENTERNCC1701E said:
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
Click to expand...
Click to collapse
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
No kidding, my first one was amazing, ran stable and cool, no trackball issues. I got some dirt in the speaker, when it blew out completely I just got it replaced. If I'd have know all the issues I'd be having with these refurbs I'd have just bought a bluetooth and called it good.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
Not for a lack of trying, though.
Can't post in the Dev section yet. That's what I get for trolling around since you guys showed me how to root my OG Droid. Thanks, btw.
Now, I'm trying to root my Tbolt, and when I click on the downgrade RUU file to see the contents it says the file is invalid. So, then I tried to extract it, to see what would happen, but same message.
I also downloaded the exploits.zip and the final PG05IMG.zip and was able to view both their contents. Plus, I had to extract the exploits file to the SDK directory, and it worked fine.
So, I then downloaded from all three mirrors, but same result. And then I went to the rom.galaxysense.com site and downloaded from there, but same result. Am I the only one having retarditis? Is the file jacked, or just run-of-the-mill incompetence on my part???
Thanks to whomever takes the time to help out. And thanks for all the help everyone puts out there for the rest of us.
I am confused by your massive amount of words in this post. You need to say maybe, 20 things total.
First, you don't need to open anything, you simply need to put the ZIP onto your SD card and reboot into Hboot.
The only ZIP you need to unzip is the exploit.zip.
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
drweltman said:
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
Click to expand...
Click to collapse
haha, I was feeling like being a smart ass. The RUU needs to be renamed to PG05IMG.ZIP and put on the sd card, then you need to reboot into bootloader.
Also to add, I came into the problem where I renamed to PG05IMG.zip It was already zipped so just had to name it PG05IMG Then it worked for me.
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
I'm pretty sure that the RUU downgrade is not something you can open. Just make sure the checksum is valid and you're good to go.
I had tried to flash the RUU after I first rooted becuase I was having location issues. It would check the PG05IMG.ZIP and go back to the Hboot screen. I had flashed another rom so I didn't mess with it any further.
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
Finally! I've been looking through threads forever in search of this very issue. I was all set on rooting last night, and just like you, the Mecha_RUU file wouldn't unzip, said it was invalid, etc. I stopped right there out of fear that I'd get burned pressing on with one of the key files "broken." Have you rooted since with no trouble?
The best thing to always do is get an MD5 sum for the file and compare it to the root post. I have rooted my thunderbolt twice now and never had a problem.
If the md5sum is correct then you should be fine. Also remember in Windows, it hides the extensions. So when you rename your files do not add the extension as it is already there.
You can show the extensions by changing the folder settings.
Downgrade wont flash
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
JDBSC1 said:
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
Click to expand...
Click to collapse
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Absolute_Zero said:
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Click to expand...
Click to collapse
I appreciate the thread link. That's exactly the error I'm getting. Problem is I'm supposed to downgrade to obtain root ( or at least that's one of the steps). I have downloaded this downgrade file from multiple links and verified its the correct one to use in this step and I always receive the "main version higher" issue. Should I be using a different file to downgrade or is this no longer an option for root since the 7/8/11 ota?
Sent from my ADR6400L using Tapatalk
Interesting..
I wiped everything ADB and Thunderbolt related from my PC.
Then I downloaded the easy root from this link
http://forum.xda-developers.com/showthread.php?t=1005292&highlight=easyroot
Then I downloaded and opened the pdf instructions on the same page.
Then I followed the written directions to a T!
Worked like a charm. Steps 1, 2, and 3 hung up and had to be done multiple times but I finally got through it. Some other links if found with this same method were misleading as to doing the steps over again but he accounted for this in his pdf instructions and if you follow it to the letter you should be good.
I've been trying to locate some older versions of the PRI but haven't been able to find any. Judging from Haus' radio AND pri update file I'm looking for a rcdata.img file I think but I haven't been able to find any in the 1.13 stock rooteds or on the dev forum. Anyone know where I can find them?
Thanks.
blingeorkl said:
I've been trying to locate some older versions of the PRI but haven't been able to find any. Judging from Haus' radio AND pri update file I'm looking for a rcdata.img file I think but I haven't been able to find any in the 1.13 stock rooteds or on the dev forum. Anyone know where I can find them?
Thanks.
Click to expand...
Click to collapse
The only source we've had for PRI files on both the EVO and seemingly also for the EVO 3D are the RUU files released by a user named Football with a Russian flag in his profile (occasionally maybe one or two official OTA updates on the EVO contained rcdata.img files...).
The RUU files are posted in the development board by Football and also mirrored on http://goo-inside.me/shooter/ruu.
The RUU is released as a .exe file. There is a rom.zip file inside the .exe which contains all the .img files including (if released in that specific RUU) the rcdata.img or nv.img.
Goo-inside.me has already extracted these rom.zip files and posted them renamed as PG86IMG.zip files because the rom.zip has the first 256 bytes of the digital signature required by the bootloader to be loaded directly when renamed to PG86IMG.zip. If you grab these zip files off goo-inside.me and open them up there should be a firmware.zip file which would contain the rcdata.img/nv.img if it was released in that RUU. Otherwise we haven't really been given rcdata.img/nv.img files from any other source on the EVO or EVO 3D yet.
If you want to extract the rom.zip file from inside the .exe yourself from linux - very helpful guide I've used: Extract ROM Image from RUU Windows Exe On Linux
As for the EVO 3D, off the top of my head, I only recall seeing an rcdata.img file distributed with this latest RUU 2.08, but I could be wrong and it is def worth double checking. With the HTC EVO, we didn't receive rcdata.img files very often .. might be the same case with the EVO 3D, only time will tell.
I know that might not be the best news but hopefully the technical information is helpful for now and the future in advising where to look and diff options on how to obtain!
Im also looking for this because ever since i upgraded the PRI on my evo 3d, ive had horrible service no matter what rom or radio i flash. i have an airave in my house and the phone constantly roams, goes on 1x and never passes 1 bar on sprint signal. Missing calls... it really sucks. Its weird because on my evo 4G, i never had a problem no matter what radio/pri/prl combo/setup i had... Wish i could get ahold of that earlier PRI because i had perfect signal and 3G everywhere in my house before this. =\
So i did a bit of searching and have not came up with anything.
I am trying to modify a rom to fit in a different hboot then it was originally developed for.
Could i just move the files around in the .zip to there appropriate places and update the updater-script or is it more complex? I know where all the files and folders are supposed to go (that belong in the system and Data).
I was just wandering if anyone has come accross the same thing and my have a tutorial or guide that may help? I have found one on porting a rom from one to another but nothing for diffrent size hboots.
Thanks
anybody? specifically the .nbh files given out in a xtc clip and not the old ruu format?
i wish to edit the file to remove how it asks for the htcsim/ tell it to always confirm that its there. i am aware that this would not work on s-on devices as the bootloader wont accept files that are not signed by htc, but i have a htc wildfire with revolution hboot in mind any programs and whatnot to do it with would be a help please
also 300th post XD