Related
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
dyndragon said:
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
Click to expand...
Click to collapse
When u say u saved a phone. Do u mean u stopped someone before they did it, or you mean u have a working fix. Pls post fix if u have one. I will post mine as soon as I confirm it.
Btw- I have seen 5 happen in the last 3 days. As I haven't gave up on any yet, some are worse off then others and only 2 have a possible fix in the am, well a fix I know of.
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
So does that mean the instructions for how to Un-Root are no good?
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
I unrooted my phone, no problems.
No the instructions to unroot are correct because at the beginning you flash an alternate misc.img to change the main version number. I got stuck the other day because my phone wouldnt boot and i couldn't flash the ota because i had removed google goggles and some other system apps so i tried to downgrade using PC10IMG.zip and it cancelled during installation just as stated in the op and i was somehow able to flash the misc.img through fastboot and reflash with PC10IMG.zip
sethrd said:
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
Click to expand...
Click to collapse
If you did not flash the stock rom before you flashed the pc10, you got lucky. When it reboots half way though, it does a version check, and the rom version you happened to be running must have been an older base. If your phone is bootable and you flash the pc10 OUT OF ORDER it will lock you down that way, ie locked on sense. If anyone wants to go back to stock, just flash one of the stock w/root roms in recovery or via rom manager... trust me on this, there are more people screwing up there phone because of this then anything, just not posting about it. I've been up all hours of the night, helping differnt people the last few days.
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
No the unroot guide is ok. If you notice, the first thing it has you flash is the stock w/root rom. Like I said if you follow proven instructions to a T, you will be ok. That is if you want to go back to non-root only though. If you just want stock with root, flash a stock with root rom via RECOVERY or ROM MANAGER.
Im not to sure how it all works and i just got up a little bit ago .
but since s-off doesnt check the sign couldnt we unpack and repack pc10img with the hboot with s-off?
fastludeh22 said:
Like I said if you follow proven instructions to a T, you will be ok.
Click to expand...
Click to collapse
Well he's edited his post now, and people have followed his instuctions and bricked their phones.
So just to confirm before I brick mine: The instructions in their current form will not brick my phone, right?
I had s-off when running baconbits. I tried to revert back to stock but couldn't. I then flashed pauls prerooted phone rom and tried to install the stock rom back onto the phone. I seems to have removed the s-off and now displays s-on. I am permanently rooted, but fastboot still shows s-on. Was this caused because I tried to flash the pc10img.zip? Now how do i revert back to stock? I don't have a nandroid backup for the stock rom, just paul's which after a recovery still displays s-on. It doesn't loop, I just can't install anything else on there.
I flashed pc10 and it turned S-ON. But when I booted it up I still had root acess, so it was like a temp root but where I could not write to the system. I took the ko file from the perm root and hex edited it to match the kernal on my phone.. boom rooted again and I was able to flash recovery and do a nand restore
I tested it out again by hbooting pc10.. and I was able to obtain s-off by changing the kernal number in the ko file
Sent from my T-Mobile G2 using XDA App
So let me get this straight, in order to flash pc10 safely we MUST have an existing PreRooted STOCK ROM?
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
marc91988 said:
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Exactly. If you actually follow the directions in the thread you will be fine. I've done it more than a few times and have not had any problems yet.
I have also updated the instruction on the unroot guide aswell.
I was running the original Sense rom that was loaded via hboot which kept me at s-off. I was able to revert back to stock using the PC10 zip from here http://forum.xda-developers.com/showthread.php?t=831398 At the time I had no clockwork recovery. Was what I unsafe?
Thanks for the piece of mind. I don't want to unroot just yet, I'm running pretty much the stock rom w/ ota and bacon bits anyway, so........ Still it's nice to know that I can get back to stock should I NEED to.
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
fryrice8850 said:
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
Click to expand...
Click to collapse
These people didnt nand back before messing around with stuff
Sent from my T-Mobile G2 using XDA App
Hi !
So I finally did it : I've just finished the installation of a custom rom (Virtuous Unity 1.29.0).
Needless to say it was painful, even with the great tutorials available here.
I had to make a gold card with the SD card provided with Desire HD (haven't got any other one), downgrade, Radio & ENG S-OFF, Clockwork, backup and flash.
It was painful mostly because you have to click here to do this, but there you have to click on another link to do that before...
In the end, I only had a minor issue with ENG S-OFF (related to that unknown su authorization).
I was a little scared after the final reboot as the rom took its time to load but everything's working fine.
So thanks to all tutorials/tips writers
I just have few minor questions, mostly related to the rom but I can't write them in the proper thread :
- Seems the rom is bundled with the proper radio, was it flashed in the process or do I have to flash it myself ? If yes, where are the files ?
- Do I have to keep ENG S-OFF now that I'm done ? Or does the rom require this option to be off ? I'd rather have this security feature turned back on if possible.
Radios are flashed using fastboot you will need to do that separately.
If you follow the link in my signature to my site you can find all the latest radios there. Some are even packaged ready to flash using the small tool I wrote.
andyharney said:
Radios are flashed using fastboot you will need to do that separately.
If you follow the link in my signature to my site you can find all the latest radios there. Some are even packaged ready to flash using the small tool I wrote.
Click to expand...
Click to collapse
Done, thank you
Rooted successfully yesterday, installed Caulkulins latest ROM and have been having constant reboots...so I figured I would reload my nandroid backup...but it won't happen.
I am loading the stock, rooted rom from Goo-Inside me using Rom Manager.
Now...is there a way to actually un-root?
Updated Title for clarification of the question.
Idk about getting s-on but I know there's an ruu with the newest update in the dev section
Sent from my SYNERGIZED **EVO 4G** (Screw 3D!)
I would like to know as well. I'm having issues with my phone and need to take it in for a repair.
Someone please answer, this is I know the 3rd thread asking this question. Thanks.
Sent from my PC36100 using Tapatalk
Just FYI. I tried to use the unrevoked method of unrooting knowing it wouldnt work but gave it a whril anyway and no go. Cant downgrade hboot and cant set s-on. I need a solution to the Revolutianary root method for S-On
Is it at least possible to get stock everything else at least?
rquinn19 said:
Is it at least possible to get stock everything else at least?
Click to expand...
Click to collapse
Yes. You can find the stock unrooted ROM (it should be around here somewhere) and flash that. You will then be unrooted but still have S-OFF (NAND Unlocked). You can not get that last bit (S-ON) back for now.
You can find the stock ROM here. If you flash that I think you will be stock except for the S-OFF bootloader.
oldpreowner said:
Someone please answer, this is I know the 3rd thread asking this question. Thanks.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
People cant answer a question that they have no answer too...Dont assume it can be done and others are hiding it from you. Quite sure the moment someone figures it out it will be posted....Until then you are going to have to either use the stock ruu or flash one of those stock looking roms without SU
I would think that you could go back to s-on but it seems the method to get there is a bit risky. If you were to follow this guide:
http://forum.xda-developers.com/showthread.php?t=883548
it may be possible to get back hboot 2.16 and then ruu.
Edit: Flash hex edited hboot and then run ruu to obtain s-on.
{ParanoiA} said:
I would think that you could go back to s-on but it seems the method to get there is a bit risky. If you were to follow this guide:
http://forum.xda-developers.com/showthread.php?t=883548
it may be possible to get to a hboot version that the unrevoked s-on tool would work on. Maybe someone that really wants to go back that badly will try it and report the results.
Click to expand...
Click to collapse
Thank you for this post!
I was able to hex edit the 2.16 HBOOT to 6.17, which allowed it to overwrite the Revolutionary HBOOT, and immediately set me to S-ON. Then, I flashed the stock GB 4.24 PC36IMG.zip, which successfully overwrote the hex-edited 2.16 HBOOT with the one from the PC36IMG, and my phone is back to stock! AWESOME .
Captain_Throwback said:
Thank you for this post!
I was able to hex edit the 2.16 HBOOT to 6.17, which allowed it to overwrite the Revolutionary HBOOT, and immediately set me to S-ON. Then, I flashed the stock GB 4.24 PC36IMG.zip, which successfully overwrote the hex-edited 2.16 HBOOT with the one from the PC36IMG, and my phone is back to stock! AWESOME .
Click to expand...
Click to collapse
That is good to know. I am going to have to remember that.
Captain_Throwback said:
Thank you for this post!
I was able to hex edit the 2.16 HBOOT to 6.17, which allowed it to overwrite the Revolutionary HBOOT, and immediately set me to S-ON. Then, I flashed the stock GB 4.24 PC36IMG.zip, which successfully overwrote the hex-edited 2.16 HBOOT with the one from the PC36IMG, and my phone is back to stock! AWESOME .
Click to expand...
Click to collapse
Can you put together instructions on how to do this or provide the edited files to use? Great work!
Restore stock HBOOT, S-ON after rooting with Revolutionary (Gingerbread, HBOOT 6.16)
sabauman said:
Can you put together instructions on how to do this or provide the edited files to use? Great work!
Click to expand...
Click to collapse
UPDATED ON 7-MAR-2012
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Files Needed:
6.17 HBOOT - Hex-edited version of 2.16 HBOOT modified to overwrite Revolutionary version
[*]Official Stock ROM (RUU or PC36IMG.zip signed by HTC) - see bottom of post for list of several different stock ROM versions
IMPORTANT NOTES:
The file attached to this post can either be extracted, and the HBOOT.img flashed via Android Flasher, or it can be saved to the root of the /sdcard and flashed via Bootloader (file must be renamed to PC36IMG.zip to flash successfully).[*]If you are using File Explorer and do not see any file extensions, but Windows tells you that the file is a "ZIP file," do NOT add a .zip to the file name! That will result in this happening.
Steps to Un-Root Revolutionary (should work for all S-OFF EVO hardware versions):
Download HBOOT 6.17 and flash using Android Flasher or in Bootloader. Once flashing is complete, Reboot Bootloader and note NAND status. NOTE: At this point, your HBOOT version should be 6.17. If it isn't, then the modified HBOOT file did not flash successfully, and you will need to flash it again.
[*]If you're now "S-ON", move down to "After you're S-ON" section. If not (i.e. you are still "S-OFF"), continue on to next step.
[*]Download the Radio 2.15.00.11.19 from Calkulin's thread and install via recovery (if you'd prefer to install via Bootloader, use this version) - thanks to Calkulin
[*]Download unrevoked S-ON zip - thanks to unrevoked
[*]Boot into recovery and flash unrevoked S-ON zip.
[*]Boot into Bootloader and note NAND status - you should now be S-ON! Proceed to "After you're S-ON section".
After you're S-ON:
Flash an unrooted stock ROM to return your device to factory conditions. Here is a link to Football's thread, with several different RUU versions. Below are direct links to the latest official Froyo & Gingerbread PC36IMG.zip files that can be rooted with unrevoked and Revolutionary, respectively. Also included is the latest Gingerbread OTA release that is rootable via the HTCDev.com website.
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed | Mirror - ONLY rootable with unrevoked
PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed | Mirror - ONLY rootable with Revolutionary
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed | Mirror - ONLY rootable with HTCDev.com
After flashing one of the above stock ROMs, you should be restored to stock conditions, including HBOOT, Radio, & NAND-locked status, and ready to return your device for servicing!
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Any questions, please post here.
Captain_Throwback said:
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Click to expand...
Click to collapse
captain, you are the man. Just renamed zip to PC36IMG and flashed in hboot. S-ON and unrooted. Thanks a ton!!!!!
Captain_Throwback said:
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
Click to expand...
Click to collapse
thanks that worked on my evo hardware 4 i finally got it back to stock !!!!!!!! and i rename the HBOOT file to pc36img and worked too
SWEET UNROOT Revolutionary!
Okay since im new to this stuff and for the noobies like me out there
1. DL his zip file!
2. Rename the Zip file to PC36IMG
3. Connect your phone to your cpu and transfer your PC36IMG zip to your sd card
4. Reboot your phone. (remove battery) then hold Power + Down Volume
5. Phone will boot then just wait till your phone ask if you want to update file! Hit Up to say yes
6. Then THATS IT! YOU CAN REBOOT AND CHECK TO MAKE SURE S-ON IS ON!
Captain_Throwback said:
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Click to expand...
Click to collapse
I would like to say thank you so very much! I've been looking all day and this was the only method that worked for me. I made this account solely to thank you, I apologize if thats considered spam but again I'd like to thank you very very very much
Evo4Gluscious said:
Okay since im new to this stuff and for the noobies like me out there
1. DL his zip file!
2. Rename the Zip file to PC36IMG
3. Connect your phone to your cpu and transfer your PC36IMG zip to your sd card
4. Reboot your phone. (remove battery) then hold Power + Down Volume
5. Phone will boot then just wait till your phone ask if you want to update file! Hit Up to say yes
6. Then THATS IT! YOU CAN REBOOT AND CHECK TO MAKE SURE S-ON IS ON!
Click to expand...
Click to collapse
This is exactly what I did and it worked flawlessly (btw I'm on 004 and was very scared it would not work but it did
I am still running the .92 bootloader. I am running cm10.1. Is there any benefits to upgrading?
Sent from my ADR6300 using xda app-developers ap
zombolt said:
I am still running the .92 bootloader. I am running cm10.1. Is there any benefits to upgrading?
Sent from my ADR6300 using xda app-developers ap
Click to expand...
Click to collapse
Only benefit is that you can unlock it, and are then able to fastbot flash recoveries and boot images.
thankful
cmlusco said:
Only benefit is that you can unlock it, and are then able to fastbot flash recoveries and boot images.
Click to expand...
Click to collapse
I'm so thankful that cmlusco had these simple words listed here. I was trying without success to flash a recovery via hboot.92 to no avail. I am s-off and rooted running tinys cm10.1. The problem started when i wanted to use twrp as a recovery. I tried installing that in android itself with goomanager. It said it was successful so tried to reboot into recovery. no dice. it now doesn't even have cwm recovery which was what i was trying to replace. it just goes back into hboot. so i thought, "ok, i'll just adb it" again either with shell in android or via fastboot in hboot it says remote failed. this one line he just wrote tells me that despite everything i have, i cannot install via hboot. The only thing that works is having a pb31img file to install it. the problem is, most recoveries come in .img. so I thought i could just repackage it as a zip and use the txt from another twrp i had previously gotten to work by way of a pb31img and create my own new pb31img with the newest version (the old one i had was already made by someone else and installs flawlessly). basically now i'm curious if i should just ask how to make the newest twrp into a proper pb31img file to flash (since i know this works) or is there an easy way to upgrade hboot.092 to 1.07? Any help on either of these or both subjects would be greatly appreciated. Just for the record cmlusco, am i right in thinking the reason i can't fastboot flash my recovery is because my loader is locked somehow despite being rooted and s-off? will upgrading to hboot 1.07 enable all of what i want to do? Also, what's the best way to go about doing this? I have everything i need backed up so no worries there. Thanks in advance to any and all help!
thejase said:
I'm so thankful that cmlusco had these simple words listed here. I was trying without success to flash a recovery via hboot.92 to no avail. I am s-off and rooted running tinys cm10.1. The problem started when i wanted to use twrp as a recovery. I tried installing that in android itself with goomanager. It said it was successful so tried to reboot into recovery. no dice. it now doesn't even have cwm recovery which was what i was trying to replace. it just goes back into hboot. so i thought, "ok, i'll just adb it" again either with shell in android or via fastboot in hboot it says remote failed. this one line he just wrote tells me that despite everything i have, i cannot install via hboot. The only thing that works is having a pb31img file to install it. the problem is, most recoveries come in .img. so I thought i could just repackage it as a zip and use the txt from another twrp i had previously gotten to work by way of a pb31img and create my own new pb31img with the newest version (the old one i had was already made by someone else and installs flawlessly). basically now i'm curious if i should just ask how to make the newest twrp into a proper pb31img file to flash (since i know this works) or is there an easy way to upgrade hboot.092 to 1.07? Any help on either of these or both subjects would be greatly appreciated. Just for the record cmlusco, am i right in thinking the reason i can't fastboot flash my recovery is because my loader is locked somehow despite being rooted and s-off? will upgrading to hboot 1.07 enable all of what i want to do? Also, what's the best way to go about doing this? I have everything i need backed up so no worries there. Thanks in advance to any and all help!
Click to expand...
Click to collapse
You don't even need to go through all that trouble. Just use the PB31IMG.zip here:
PB31IMG.zip - 3.61 MB
It's also in the TWRP thread on one of the last few pages, TWRP 2.4.1.0.
thejase said:
I'm so thankful that cmlusco had these simple words listed here. I was trying without success to flash a recovery via hboot.92 to no avail. I am s-off and rooted running tinys cm10.1. The problem started when i wanted to use twrp as a recovery. I tried installing that in android itself with goomanager. It said it was successful so tried to reboot into recovery. no dice. it now doesn't even have cwm recovery which was what i was trying to replace. it just goes back into hboot. so i thought, "ok, i'll just adb it" again either with shell in android or via fastboot in hboot it says remote failed. this one line he just wrote tells me that despite everything i have, i cannot install via hboot. The only thing that works is having a pb31img file to install it. the problem is, most recoveries come in .img. so I thought i could just repackage it as a zip and use the txt from another twrp i had previously gotten to work by way of a pb31img and create my own new pb31img with the newest version (the old one i had was already made by someone else and installs flawlessly). basically now i'm curious if i should just ask how to make the newest twrp into a proper pb31img file to flash (since i know this works) or is there an easy way to upgrade hboot.092 to 1.07? Any help on either of these or both subjects would be greatly appreciated. Just for the record cmlusco, am i right in thinking the reason i can't fastboot flash my recovery is because my loader is locked somehow despite being rooted and s-off? will upgrading to hboot 1.07 enable all of what i want to do? Also, what's the best way to go about doing this? I have everything i need backed up so no worries there. Thanks in advance to any and all help!
Click to expand...
Click to collapse
Correct you can not fastboot flash unless your bootloader is unlocked. Since your s-off you can update the bootloader by flashing this file http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip, thru hboot. Once updated, you can unlock it and then flash img files with fastboot.
However, here is the TWRP 2.4.1.0 PB31IMG.zip http://dinc.does-it.net/Recoveries/TWRP_2.4.1.0/PB31IMG.zip, if you dont want to update the bootloader. You may need to flash it two or three times to get it to take.
---------- Post added at 01:43 PM ---------- Previous post was at 01:37 PM ----------
tiny4579 said:
You don't even need to go through all that trouble. Just use the PB31IMG.zip here:
PB31IMG.zip - 3.61 MB
It's also in the TWRP thread on one of the last few pages, TWRP 2.4.1.0.
Click to expand...
Click to collapse
Beat me to it lol, i took to long to type.
cmlusco said:
Correct you can not fastboot flash unless your bootloader is unlocked. Since your s-off you can update the bootloader by flashing this file http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip, thru hboot. Once updated, you can unlock it and then flash img files with fastboot.
However, here is the TWRP 2.4.1.0 PB31IMG.zip http://dinc.does-it.net/Recoveries/TWRP_2.4.1.0/PB31IMG.zip, if you dont want to update the bootloader. You may need to flash it two or three times to get it to take.
---------- Post added at 01:43 PM ---------- Previous post was at 01:37 PM ----------
Beat me to it lol, i took to long to type.
Click to expand...
Click to collapse
Thanks to you and tiny for such a quick and simple response. pb31img used and updated perfectly! Just curious, cmlusco, in your signature i noticed you on hboot 1.07 but it's locked. Any particular reason for having it locked? I have yet to update mine but i did download and organize the pb31 hboot img you gave me for possible future use ( if i feel the need). Other than the aformentioned advantage of flashing hboot via fasboot and adb, is there any other advantage of hboot 1.07? Thanks again guys, you make my life easier.
thejase said:
Thanks to you and tiny for such a quick and simple response. pb31img used and updated perfectly! Just curious, cmlusco, in your signature i noticed you on hboot 1.07 but it's locked. Any particular reason for having it locked? I have yet to update mine but i did download and organize the pb31 hboot img you gave me for possible future use ( if i feel the need). Other than the aformentioned advantage of flashing hboot via fasboot and adb, is there any other advantage of hboot 1.07? Thanks again guys, you make my life easier.
Click to expand...
Click to collapse
Not really, S-OFF should get you what you need. You only miss the ability to flash via fastboot without an unlocked HBOOT. PB31IMG.zip works fine with S-OFF.
thejase said:
Thanks to you and tiny for such a quick and simple response. pb31img used and updated perfectly! Just curious, cmlusco, in your signature i noticed you on hboot 1.07 but it's locked. Any particular reason for having it locked? I have yet to update mine but i did download and organize the pb31 hboot img you gave me for possible future use ( if i feel the need). Other than the aformentioned advantage of flashing hboot via fasboot and adb, is there any other advantage of hboot 1.07? Thanks again guys, you make my life easier.
Click to expand...
Click to collapse
I have never had the need to unlock it yet, but like having the ability if needed.
Hey everyone,
I recently acquired an old EVO 4g, and it's old as balls, and I can't figure out how to get it to upgrade - and many of the files that I find around the internet are 404 links, so I'm somewhat stuck.
The device IS rooted (s-off) with HBOOT 2.10.0001
Firmware : 2.1-update 1
Kernel : [email protected] #1 (2.6.29)
Software number : 1.32.651.1
PRI : 1.90_003
PRL : 60687
I could care less about the data on the phone, or anything about it - but I would like to get it upgraded to at least stock 2.3.5. The device can't get OTA updates, and the main problem is every link I try to follow that leads to a pc36img.zip that I want to try is dead. All I really need is a way to get this device to a place where I can fall into one of the tracks to the many guides out there.
It's S-OFF, but there is no superuser file or rom manager, and it seems the recovery is stock. Any images I try to flash from recovery throw signature verification failed. Using the unrevoked drivers, I can ADB around in the phone without a problem, but since I received the phone in this state, I'm not sure the method that was taken to get it here (hence, do not know the steps to un-do whatever was done)
I can't find any files that I have been able to successfully flash to upgrade the system, recovery, or downgrade the hboot to .76 - my thought was to downgrade to the hboot-eng then fastboot load a recovery - but that failed since I couldn't find an active link.
So amid the sea of old information and broken links, I am adrift. Anyone help me out?
Thanks!
Try installing Smelkus recovery using this link below. There are a couple of ways to do it; just boils down to personal preference, really.
http://forum.xda-developers.com/showthread.php?t=1661543
If all goes well, you can flash a custom ROM. I would then go about updating the firmware.
Another thing you could try is to run an RUU to a newer software version. You'll retain S-off, so all you would have to do is install a custom recovery and then flash a custom ROM.
Also, root and S-off are two different things.
Sent from my EVO using xda premium
+1 Smelkus recovery
After installing Smelkus, flash the rooted version of the current Sprint ROM http://forum.xda-developers.com/showthread.php?t=1671395 and apply any updates for the phone's PRI and network profile. You can continue to use the Sprint ROM or flash the custom ROM of your choice. There is a wide variety of ROMs still available for the EVO 4G. You can select from the ROMs lsited at http://evo4g.roms-db.com/all-builds/ for the functional features that fill your needs. Just remember to make a nandroid backup of your current working phone firmware before flashing a new ROM and be sure the phone's battery is at least 40% charged before you begin to flash the ROM!
thanks for the tips! I'll try it out when I get a chance and report back.
SmelkusMOD Recovery is the best recovery that i have used to this date!