Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.
Bookmarking this, just in case. Thanks, Jcase!
Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!
http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread
I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!
Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890
droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.
jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.
Related
This is for people that used either of the leak root methods. The engineering bootloader is an unsecured bootloader, and is better in many ways (google it I am not explaining why). Just say its harder to brick with it.
Before attempting, please check your md5sums.
I want to thank Framework for being my punching back and helping with this. And the desire guy's who's work stuck in my head and gave me this idea (Sorry I forgot who you are!!).
Needed Files:
Original Root Rom - PB00IMG.zip - 63eacc5ede3b179f95dc22d8ef585f94
Custom Misc Image - custom.img - 19de71cf42b3a7992d2660e7980c50bf
Fastboot for linux - 4baca1f80fc9bb31aa75fd3fee2cc36b
Amon's Recovery - 354d30c38c59b442340c8b72aa9f547e
Windows users should have fastboot in the sdk, and mac users I dont have a copy of yours.
lash_image - 16559f2c27d08ff1ddfcaca05fbf10fb
Step 1:
Get follow root tutorials and get amon's recovery installed. If you want to skip installing a new rom after rooting, You can flash EngTools.zip will root your device . If you flash engtools you can skip step 2.
Step 2:
Take a nandroid backup, if you wish as this will wipe your device.
Code:
adb push flash_image /data/local/flash_image
adb shell chmod 777 /data/local/flash_image
Step 3:
Push custom.img to your phone
Code:
adb push custom.img /data/local/custom.img
Custom.img is the misc img for your device, it contains the mainversion. I took one off a rooted phone and hex edited the version to be lower than the original root rom so it will flash.
Step 4:
Copy PB00IMG.zip to your sdcard
Step 5:
Flash custom.img
If you flashed engtools3.zip (http://www.multiupload.com/L97EUYBG3V)
Code:
adb shell flash_image misc /data/local/custom.img
If you pushed flash_image
Code:
adb shell /data/local/flash_image misc /data/local/custom.img
Step 6:
Reboot to Bootloader and flash PB00IMG.zip
Code:
adb reboot bootloader
After the new rom is flashed, you can now use fastboot to flash a recovery image while in the bootloader
Code:
fastboot flash recovery recovery.img
Enjoy
Like my work? Buy a bum a beer downtown or donate to local homeless youth org.
How do I know what bootloader I have ? Are you referring to the "1.49 S-OFF" type version number ?
hallstevenson said:
How do I know what bootloader I have ? Are you referring to the "1.49 S-OFF" type version number ?
Click to expand...
Click to collapse
yes, 1.49.2000 s=off
This post if for those that used one of the two new methods for root.
jcase said:
This post if for those that used one of the two new methods for root.
Click to expand...
Click to collapse
Thank you! This will help the leakers *stay* rooted. Otherwise I imagine some will get the new OTA, lose their recovery image, and have to re-root.
This is perfect...That's been my only headache, however step one confuses me. can I just skip step one?...I already have AmonRa recovery and i use Conap's CELB. And can I do this while in AmonRa recovery or when my phone is on regularly?
Works perfect. Now on s-off.
HaRdC0r3 said:
This is perfect...That's been my only headache, however step one confuses me. can I just skip step one?...I already have AmonRa recovery and i use Conap's CELB. And can I do this while in AmonRa recovery or when my phone is on regularly?
Click to expand...
Click to collapse
Yeah, you'll skip step one essentially.
Step 2 and 3, you'll do while the phone is booted up, provided you have USB Debugging on.
Then when you copy the PB00IMG.zip to the SDCard and reboot into bootloader, you'll automatically start installing the PB00IMG.zip file.
Doing this will flash the engineering bootloader and you'll no longer have recovery, which is why we do the last step of flashing recovery.
It's best to make a nandroid backup prior to all of this, that way you can restore your OS exactly how you had it.
Is there any real reason to do this other than ota protection? I tried to google it but found no real reason as long as I had root.
jcase said:
This is for people that used either of the leak root methods.
Click to expand...
Click to collapse
jcase said:
This post if for those that used one of the two new methods for root.
Click to expand...
Click to collapse
I skipped over the first post too quickly and missed the above line. No worries.
Hi, long time lurker first time poster.
Worked like a champ, thank you for your work! Finally the cursed hboot is gone!
Why can't we just do
fastboot flash hboot hboot.nb0
Does that only work once the you already have the s-off bootloader?
Very long time lurker, new to posting. Just wanted to say thanks to jcase. People like you are the reason the Android community exists. :TU:
OMG this is awsome. Thank You So Much!!!!
sco12345 said:
Hi, long time lurker first time poster.
Worked like a champ, thank you for your work! Finally the cursed hboot is gone!
I pulled the battery after the first reboot on step 6 (after pressing action when the hboot is updated) and saved having to do a nand restore. I'm pretty sure as long as you pull the battery before the second "ACTION" on the rooted PB000IMG you're safe. If not let me know and I'll delete the info to keep anyone from getting bad ideas.
May motivate those happy with their setup to kill the cursed 1.49 S-ON, of course you may have left it out to prevent bricks...
Just thought I'd share.
Click to expand...
Click to collapse
I don't like potential bricks on my head.
Hey Jcase why not add this to your simple version of the new root method then ask for it to be a sticky?
pjsockett said:
Why can't we just do
fastboot flash hboot hboot.nb0
Does that only work once the you already have the s-off bootloader?
Click to expand...
Click to collapse
Yeah no workie on lock bootie.
worked great =D now i love my eris and have no need to upgrade to incredible now haha(mostly cuz i dont have $200) =D
jcase said:
Yeah no workie on lock bootie.
Click to expand...
Click to collapse
I'm assuming you can't do a symlink to mtd0 like you did with mtd1, right?
Will this work?
My wife has been having huge issues with her dialer on all 3 of the 2.1 leaks and the RUU. She just wants to go back to stock so she can take it into Verizon. I stole her phone to root it after I had leak on mine and shee has been complaining ever since.
Can I make a nandroid backup, use this method to get the engineering bootlaoder, and then restore the backup to get back to the RUU rom? From there I should be able to flash the 1.47 hboot through fastboot. I'm just not sure what will happen on the nandroid restore. I looked at one of the backups and the hboot doesn't seem to be a part of it but I wanted to make sure it was safe.
Could we do this then use this
http://htcpedia.com/forum/showthread.php?t=2934
to change the hboot number? or would that be point less?
All,
I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.
I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.
Has anyone successfully done this?
I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.
Thanks!
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.
- Can't do a nandroid backup (to unlock) because I don't have root.
Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
51Cards said:
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
Click to expand...
Click to collapse
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.
Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.
This stuff is stupid easy on the N1.
ATnTdude said:
Custom bootloader? Just unlock the one you have and flash a new recovery.
Click to expand...
Click to collapse
Ok so feeling like a newb here.
First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.
But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.
Thanks for the info.
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.
I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that
SO....has anyone used gingerbreak successfully on 2.3.4?
Disregard. I misread the post.
MitchRapp said:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
Click to expand...
Click to collapse
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
Sent from my Nexus One using XDA Premium App
DownloaderZ said:
All,
I have updated to 2.3.4, lost root as expected
Click to expand...
Click to collapse
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
GnatGoSplat said:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Click to expand...
Click to collapse
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.
What's the deal?
Thanks,
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.
I got the GRI40 update from here:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
GRI22 update:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
brettbellaire said:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Click to expand...
Click to collapse
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
droidexplorer said:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:
1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2
2) Root using Super-One-Click
3) Install ROM Manager and flash CWM
4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4
5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip
6) Remove/rename /system/etc/install-recovery.sh via ADB
7) If you have a recent backup, use CWM to 'advanced restore' the data portion.
8 ) Profit! (or root)
Step 5 may require explanation:
Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).
The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.
So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.
EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.
When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
GnatGoSplat said:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
Click to expand...
Click to collapse
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.
I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.
In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.
EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
Could someone please point me in the direction of where I can get the Evo 4G 4.22 stock recovery image?
Stock recovery is no recovery,what exactly are you looking for?
Sent from my PC36100 using XDA App
I am rooted and have CWM installed. I am looking to put back the stock 4.22 recovery so I may install the the 4.24 OTA update.
I like to keep my Rom stock and prefer to install updates via OTA.
If you take the 4.24 OTA you will no longer be "rooted" Look for one of the rooted ROMs and flash it
Yeah,what he said
Sent from my PC36100 using XDA App
I am using the Unrevoked root method and no update (3.70,4.22) to date has unrooted my phone.
I have simply been restoring the current version of the stock recovery, which I have previously found on the internets, and then running the OTA update as normal. Once done I install CWM and the latest SU updates. Works great.
I would like to perfrom this method once agian to install the 4.24 update and all I need is the 4.22 stock recovery.
If you don't want to be rooted anymore, then just accept the OTA - it'll override your current recovery with the stock recovery, which is actually a lack of recovery.
But as others have said, you won't be able to root again unless you've ran unrevoked or unrevoked forever and remain s-off. In that case, you'll have to flash a recovery and then flash the rooted version. So if you want to stay rooted, you might as well go ahead and do that. You should be able to just wipe cache and dalvik and install, so the end result will be the same but you'll be rooted.
I hope that made sense...
(from... Evo/MIUI/Tapatalk)
kc8emd said:
Could someone please point me in the direction of where I can get the Evo 4G 4.22 stock recovery?
Click to expand...
Click to collapse
You probably want this:
http://forum.xda-developers.com/showthread.php?t=1133379
This is the actual update, but rooted, so you can keep your CWM recovery, get the latest update that was made OTA, but remain rooted. You don't want to just accept the OTA if prompted, your root will go away.
Once you've downloaded it (and the radio update as well), follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=14933526&postcount=31
Thats the problem. I cannot install the OTA 4.24 update with CWM installed, nor can I install the update manually, via renaming and then update method, as it will error out during install.
OTA updates will only install if the proper stock verion of recovery in installed, hence I really need the 4.22 recovery.
Installing OTA updates when using Unrevoked does not change S-OFF, it only overwrites SU which can be easily reinstalled. I know as I rooted my evo way back when it was version 3.26 using unrevoked 3 and have installed every OTA update since using this method and still have S-OFF
Thanks, but I do not need to go that route. My method will update as normal and I wont have to wipe my phone.
dmolavi said:
You probably want this:
http://forum.xda-developers.com/showthread.php?t=1133379
This is the actual update, but rooted, so you can keep your CWM recovery, get the latest update that was made OTA, but remain rooted. You don't want to just accept the OTA if prompted, your root will go away.
Once you've downloaded it (and the radio update as well), follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=14933526&postcount=31
Click to expand...
Click to collapse
kc8emd said:
Thanks, but I do not need to go that route. My method will update as normal and I wont have to wipe my phone.
Click to expand...
Click to collapse
And you won't be rooted anymore. There are only about 3 thousand posts telling people this, and most AFTER they found out the hard way. There are stock Rooted ROMS based on the recovery, as in STOCK! but still rooted, and up to date.
BTW, there are also a lot of posts detailing how the OTA made their phones worse, but if you want to be a hard head, go ahead and bury yourself, but don't come back crying when you figure out.
how come every other incompetent noob can manage to get their phone back to stock and permanently locked/unrooted, yet I cannot manage this feat intentionally?
if I intentionally flash the 4.22 zip from shipped-roms will this eliminate my root and recovery?
well install the 4.22 update from recovery didn't work... it aborted with some error.
ARGHHH!!! SOMEONE HELP ME LOCK MY PHONE PLEASE!!!
I appreciate the heads up, but if done correctly, it does work and has worked great for me the past few OTA updates.
I am aware of all the potential problems and am not the only one successfully installing OTA updates on a rooted evo and staying rooted.
HipKat said:
And you won't be rooted anymore. There are only about 3 thousand posts telling people this, and most AFTER they found out the hard way. There are stock Rooted ROMS based on the recovery, as in STOCK! but still rooted, and up to date.
BTW, there are also a lot of posts detailing how the OTA made their phones worse, but if you want to be a hard head, go ahead and bury yourself, but don't come back crying when you figure out.
Click to expand...
Click to collapse
Bottom line is if you change back to S-ON, and apply the OTA you lose root forever (or until Unrevoked finds a new backdoor). If you leave S-OFF then you can downgrade, and reload a recovery. The stock ROM's you'll find here (ex. Sprint Lover's) are stock, and rooted. They pretty much the same thing you get over the air. Don't be a lid..
I downloaded a from shipped roms the last rom for my evo and downloaded the s-on tool. Ran the tool then connected my phone to the computer and ran the RUU i donloaded. Fully stock unrooted locked phone
I am a noob
First learn the correct terminology for what you are tying to achieve. There is no 4.22 recovery that you can just flash, there is a 4.22 ROM and a 4.22 RUU.
Then check out the WIKI and FAQs these both contain the info you are looking for .
Not trying to be mean. Just do some research before you mess up your phone and come here asking for stuff that doesn't exist.
4.22 ROM = just the ROM
4.22 RUU = .exe that runs on your PC to FLASH your PHONE with new radio, recovery, hboot, rom, etc
exabrial said:
well install the 4.22 update from recovery didn't work... it aborted with some error.
ARGHHH!!! SOMEONE HELP ME LOCK MY PHONE PLEASE!!!
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Supersonic
http://unrevoked.com/rootwiki/doku.php/public/forever
cddmh said:
I downloaded a from shipped roms the last rom for my evo and downloaded the s-on tool. Ran the tool then connected my phone to the computer and ran the RUU i donloaded. Fully stock unrooted locked phone
I am a noob
Click to expand...
Click to collapse
Well said
This is what you want to do to get to the latest OTA STOCK no root
* if you leave S-Off you can re-root *
For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin
zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin
Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!
Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!
HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance
If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk
G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.
Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.
Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.
Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk
I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.
My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.
Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk
Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.
How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...
Hello all.. I am tryin to install the engineering bootloader and the file I need from the wiki page is not there anymore. Does anyone know where I can obtain a true copy of it. I d/l one and its not right, the md5sum was incorrect. It should be md5sum: df4fd77f44993eb05a4732210d2eddc6. Thanks if you can help. Im just trying to be thorough as i am learning all this. I have it rooted with s=off but I want to install eng. bl ....Thanks
**It is for MyTouch 4g**
Use this. Its the eng h-boot and clockworkmod recovery.
https://rapidshare.com/#!download|...|3930|R~C053B71776B49869847E4E328CF8DEC4|0|0
I got it from one of the stickies in the dev section.
Also, I have 2 Mt4g. One of the has the bootloader unlocked via HTCdev. I keep trying to flash a Stock 2.2.1 rom to it so I can do the Perma Root method on it. I have a custom rom on it currently, but it has s=on. Now the other one was stock 2.3.4 and I just got finished rooting it, for practice. Now back to the one with the bootloader unlocked by HTC, will traditional methods still work on it? I cant seem to get the adb/fastboot method to install the 2.2.1 rom on it. what would you recommend I do to get s=off on it if Im bent on doing it?
jjbadd385 said:
Also, I have 2 Mt4g. One of the has the bootloader unlocked via HTCdev. I keep trying to flash a Stock 2.2.1 rom to it so I can do the Perma Root method on it. I have a custom rom on it currently, but it has s=on. Now the other one was stock 2.3.4 and I just got finished rooting it, for practice. Now back to the one with the bootloader unlocked by HTC, will traditional methods still work on it? I cant seem to get the adb/fastboot method to install the 2.2.1 rom on it. what would you recommend I do to get s=off on it if Im bent on doing it?
Click to expand...
Click to collapse
I know NOTHING about the unlocked bootloader, so forgive me. Will flashing the froyo PD15IMG.zip from bootloader not replace your bootloader with the stock S-On bootloader that the rooting w S-Off guides are written for? Or has HTC figured out some way to bone you on that?
PD15IMG method of downgrading should take you to the older OS.
It won't necessarily take you to the older bootloader.
Not sure that being on the older bootloader is required for gfree to work. The older OS is indeed required.
Ok I'll tell you what I did this morning. I read a bunch last night. I am trying desperately to grasp & understand things. Its just there are so many different ways to acheive what I want to accomplish. Im doing this in small goals. My goal at this point is to get this MT4G, that is bootloader unlocked by HTC, to flash the Stock 2.2.1 Rom.But for some reason, it wont. Ive tried using my PC ADB/fastboot method, with no success. This morning I tried Recovery Clockwork, which I did wipe/factory reset, wipe cache, wipe davli cache, and then I choose the write zip from sd card, PD15IMG, and it wont do that either. I know I could be more helpful if I gave the exact errors but I forgot what they are, and at this point I am beginning to think that because its HTCdev unlocked, its not going to let me flash the 2.2.1. It does everything fine, until I attempt to flash the 2.2.1. The md5sum is ok too. If it were you, and you were running a custom ROM (ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12), and your device was HTC unlocked, but you wanted to get s=off, with engineer boot, how would you begin, and what method would YOU use? Give me some of your excellent advice for my birthday, which is today.
pdimg.zip files are flashed through the bootloader, not recovery. To do this, put zip on root of SD card power off phone hold volume down and power until bootloader appears and follow onscreen prompts.
HTC-Dev-unlocked bootloader 100% allows downgrading, because someone already did it before you. If you fail achieving it - means you're doing something wrong again and again, not realizing it. If I were you, I would think - why is it that your attempts to flash PD15IMG fail - and correct what you're doing wrong. But obviously, this excellent advice was given to you some time before your birthday, and still didn't help.
So, here's another advice:
Go download a PRE-ROOTED 2.2.1-based ROM.
Assuming you find one: flash it in recovery and flash boot.img from it separately.
Reboot to ROM.
Run gfree.
Flash Eng HBOOT.
If you don't find any 2.2.1-based ROM available, then you're out of luck. Sit down and find out what you're doing wrong that doesn't let you downgrade with PD15IMG.
Or just keep your phone as it is, and flash kernels manually, until you understand more.
Ok,I understand what you are saying. But when I put it on the root of my SD card as I have done multiple times, I pwr up in hboot, I wait on the blue progress bar, then a gold progress bar, then I get an error, I think it was "older version" if I remember correctly. There's not much I can do wrong to mess up a simple hboot flash of PD15IMG,you boot your phone up and wait ...
Sent from my HTC Glacier using Tapatalk
To avoid this error, you need to flash the MISC partition to "fool" the phone into thinking it's older than it is.
Read the downgrading guide, and since you're rooted - execute the "misc_version" part only:
> adb push misc_version /data/local/tmp/misc_version
> adb shell chmod 777 /data/local/tmp/*
> adb shell
Click to expand...
Click to collapse
If you see "$", it means you're not running in root shell. Then execute "su" and verify that you get "#" to continue.
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0
Click to expand...
Click to collapse
You should see:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Click to expand...
Click to collapse
Then attempt downgrading again.
Jack_R1 said:
To avoid this error, you need to flash the MISC partition to "fool" the phone into thinking it's older than it is.
Read the downgrading guide, and since you're rooted - execute the "misc_version" part only:
If you see "$", it means you're not running in root shell. Then execute "su" and verify that you get "#" to continue.
You should see:
Then attempt downgrading again.
Click to expand...
Click to collapse
Everything went well until I got to the flashing part again. I did it 2 times, one time with fastboot and i got this:
C:\adb>fastboot-windows oem rebootRUU
... OKAY
From my PC:
C:\adb>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
From my phone:
The next time, I did it in hboot from the handset and it returned an error that said "wrong zip file"
**I think I am going to be content flashing roms and the boot.img seperately until I find someone with this problem that figures it out. Besides I have another mt4g that I perm rooted s=off, so I truly feel like I have followed instructions well, since my 2nd phone worked out. Its just this one with the HTC unlocked b/l giving me problems.
Thank You for your help...
You insist on NOT following the guide, so I won't help you anymore.
FOLLOW THE DAMN GUIDE UNTIL YOU UNDERSTAND WHAT YOU'RE DOING!
Because obviously, you're doing lots of basically wrong stuff, like trying to flash a PD15IMG.ZIP by fastboot, or using fastboot oem commands.
I understand u getting frustrated, but I have followed the guide. It don't work that way either. It tells me " wrong zip file" in hboot when I do, & I know its the right one because I checked the md5sum. If its lettin me flash any Rom in CWM recovery, why can't I flash a 2.2.1 Rom in recovery? But just to let u know, I have followed the guide to the t, more than once. Sorry if u r getting frustrated but I have tried everything u told me, & thanks for helping.
Sent from my HTC Glacier using Tapatalk
Ok it says
***UNLOCKED*** (by HTCdev)
GLACIER PVT SHIP S-ON
HBOOT-0.89.0007
MICROP-0429
RADIO-26. 13.04.19_M
eMMC-boot
Dec 13 2011 21:07:39
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMG CRC
I do have Visionary and a stock unrooted 2.2.1 (PD15IMG). I also have Recovery CWM 5.0.2.0 and 4ext, just to let u know what resources I have. I think I have d/l everything under the sun..lol
Sent from my HTC Glacier using Tapatalk
Anglgodes19 said:
Good, now that makes it easy as I deleted my modified stock rom last year which I made specially for rooting, so lets move on...
1) Gain TempROOT via VISIONary+
2) On terminal.
adb shell [enter]
su [enter]
dd if=/dev/block/mmcblk0p17 of=/sdcard/msicold.img [enter]
3) Access /sdcard/msicold.img and open it in hex editor.
4) Find MSIC value XXX.XXX.XXX.XXX (ex: 2.09.1800.1) and change it to OTA "1.17.531.2" and save the file as msicnew.img on SDCard.
5) Now back on adb terminal:
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17 [enter]
sync [enter]
6) Now reboot in to bootloader and flash PD15IMG.zip as you would normally do.
Report back if you have issues or problems or can't find it in that case I suggest you upload your msicold.img and ill edit for you so you can replace it.
Click to expand...
Click to collapse
Ok I did that and opened the msicold.img in hex editor, and honestly I dont have a clue as to what i was doing, but i think i located the value and because i followed the downgrade guide, i beleive its 1.00.000.0, but i dont know how to change it. Any way i can email it to u and have u change it? my email is [email protected] if you will send me a blank email, I'll reply back with the attatched file...Thank you..
jjbadd385 said:
Ok I did that and opened the msicold.img in hex editor, and honestly I dont have a clue as to what i was doing, but i think i located the value and because i followed the downgrade guide, i beleive its 1.00.000.0, but i dont know how to change it. Any way i can email it to u and have u change it? my email is ****** if you will send me a blank email, I'll reply back with the attatched file...Thank you..
Click to expand...
Click to collapse
You may want to edit this post. Ask anyone interested in helping to PM you. Posting your email address on an open forum isn't a good idea.
estallings15 said:
You may want to edit this post. Ask anyone interested in helping to PM you. Posting your email address on an open forum isn't a good idea.
Click to expand...
Click to collapse
Wonder what happened to Anglgodes19 and all his posts? He disappeared like a theif in the night!!
1.00.000 is the correct value.
If bootloader doesn't accept PD15IMG.ZIP - it either means you're doing something wrong even though you're 100% sure you're not, or that HTC-Dev-unlocked HBOOT doesn't accept the image for downgrading, which I highly doubt.
In any case, as I wrote you, you can download and flash any 2.2.1 pre-rooted ROM, if you find one with working link, and continue the guide from there.
I don't think I can help you with anything beyond this point.
Jack_R1 said:
1.00.000 is the correct value.
If bootloader doesn't accept PD15IMG.ZIP - it either means you're doing something wrong even though you're 100% sure you're not, or that HTC-Dev-unlocked HBOOT doesn't accept the image for downgrading, which I highly doubt.
In any case, as I wrote you, you can download and flash any 2.2.1 pre-rooted ROM, if you find one with working link, and continue the guide from there.
I don't think I can help you with anything beyond this point.
Click to expand...
Click to collapse
Ok then, one last question. If I cannot get my phone to flash via hboot, Is it possible to flash the 2.2.1 rom through CWM like I am flashing other roms? Or if I flash a rooted 2.2.1 rom could I the proceed in getting s-off/ eng hboot? Or does it have to be done through hboot only with a stock rom? Or possibly a modified 2.2.1 rom that has been made to flash in recovery?
'