Okay so it looks like there is a problem with applying the current perm root instructions to the Telus Desire HD... soliciting input here on how to make a proper root guide for Telus.
Something about the RUU downgrade to an earlier firmware is causing the DHD to lose sound (headset, speaker, everything). The perm-root and radio S-OFF proceeds as normal but sound is gone.
I've suggested that the next step could be to try and flash the Telus Ace RUU after getting radio S-OFF. Still awaiting confirmation as to whether this fixes the sound problem. One person attempted to flash back the Telus radio and this did not fix it. So it's got to be something else. HBOOT maybe?
So my question is, if you're on a higher build number (1.84.661.1) but you also have already achieved radio S-OFF, is there now any way to root the phone or install custom recovery? Without downgrading by RUU again?
Those of you who have experience with the DHD already might have some brilliant ideas, so I thought I'd ask =)
The first thing would be to look at the TELUS firmware and see if there are any drivers that are specific for the phone.
Sent from my Desire HD using Tapatalk
link to the file? thx
Look in the Dev forum for the one with Telus in its name.
This thread is falling off topic though... I'm specifically asking for people who can tell me more detail about what Radio S-OFF does and doesn't allow.
Let's forget this thread and go to the Telus thread in this QA section. The problem is not in hboot or radio, those have nothing to do with sound. The problem is in the ROM, and it's drivers most probably.
There is no way to properly root Telus ROM, so it is not possible to install custom recovery while you are using it. Please check the downgrade thread for my recommendations.
Okay fine, forget I ever mentioned Telus in this thread. Can someone just help me understand the limits of what Radio S-OFF does and doesn't allow?
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
jkoljo said:
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
Click to expand...
Click to collapse
Okay... so let's say you have radio S-OFF and you're using a newer build that normally wouldn't be rootable. Could you:
- Get the temporary rootshell (which is part of the downgrade instructions anyway)
- From the temporary rootshell, flash_image the custom recovery (which should be writable due to S-OFF)
- Reboot into custom recovery?
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
jkoljo said:
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
Click to expand...
Click to collapse
Well it's a conceivable scenario. Suppose you get your S-OFF, and then later on you have a reason to want to go back to stock RUU. The next time you want to be rooted or flash a custom ROM, wouldn't this be faster than doing a full downgrade first?
Well, ok, but who would want to go back to stock when there are custom roms..
Sometimes flashing a pure stock ROM is the only cure for having gotten a little too exuberant in one's hacking
Sent from my Nexus One using XDA App
Well, full wipe does the same trick.
Sent from my Desire HD using Tapatalk
Related
Hey guys, I'd like to know how to uninstall clockwork recovery from my T-Mobile G2 in case I need to bring my phone in for repair.
I know this is an FAQ, but the method to do it with each phone seem to vary slightly.
My T-Mobile G2 has the following:
Persoshoot's OC kernel
Stock post-OTA ROM with permroot
S-OFF
Latest Clockwork Recovery
What would be the easiest and most straightforward way to restore clockwork recovery back to stock (without nuking everything else in the process)? I see threads saying to run flash_image and flashing the OTA_bootv2 Recovery, but IIRC that program isn't installed on the stock ROM by default.
Your help would be greatly appreciated!
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
If you have the eng hboot and you have adb setup on your PC, then you can use fastboot to flash the stock recovery image (which you can extract from the stock PC10IMG.zip.
Sent from my HTC Desire Z
It never hurts to erase the recovery before you flash a new one... rather than flashing a new one in over top of the old one. Sometimes stuff breaks and thats one reason why.
tazz9690 said:
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
Click to expand...
Click to collapse
To get permroot, I initially used an old method, but then unrooted. The unroot method I used is actually what's shown in the post you linked to. After unrooting, I did permrooted the "clean" way (the one that's documented on the wiki) using rage to get temproot, then using gfree to do the rest.
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
I didn't install the engineering hboot since the instructions said I didn't really need it unless I was a developer.
Keirnoth said:
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
Click to expand...
Click to collapse
Yes, that's right, except it shouldn't be called "update.zip", you want to call it "PC10IMG.zip" and place it on the root (top) folder of your SD card, then go into hboot where it should find it and ask if you want to flash it (give it a few seconds to open the file and check it first).
It is safe if you have full radio S-OFF via gfree, because that bypasses a lot of these checks, e.g. the "version is older" check, and also because when it flashes the stock hboot you will still have S-OFF.
It seems as though the OP has had his question answered but I'm also wondering the same question. I have gotten full root by the rage method. What do I do in my situation to get back to stock recovery while maintaining s-off and root. I actually just want to calibrate my battery and go back to clockwork
Lithium Ion batteries cannot be calibrated. There is no need. They dont have a memory like older battery types did, for example, nickel cadiums.
If at all possible, all you would be doing is retraining your phone with that process, not the battery. It is bad for li-ion batteries to be ran completely empty and it is not recommended if you care about the longevity of the battery.
Sent from my HTC Vision using XDA App
Thanks for your reply. I was told by someone that flashing your phone while it is plugged in kinda throws the battery off. I have noticed extremely short battery life after making this mistake so I thought it was needed. Would you still recommend doing it train the phone itself tho? I mean, my battery life is ridiculously short. Like six hours and my battery always depletes while I'm asleep.
Sent from sweet G2
I've been having some issues with my screen recently, probably due to a cable being loose or something like that so I want to send my phone back to be repaired. I have S-OFF and am running CM6.1.1. I have a nandroid backup for the original stock rom, but this is obviously rooted. So have to i get to back to S-On with the original stock room un-rooted so my warranty isn't technically void??
edit: Its a EU desire z,
Restore the backup of the stock ROM that you have.
If you have S-OFF via gfree then you need to un-do that via "gfree -s on".
If you have the eng hboot then you need to dd back the stock hboot (get it out of a PC10IMG.zip file.
Finally you can remove root. Removing the Superuser app will almost certainly be enough, no-one is going to notice anything more.
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
jakbjak said:
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
Click to expand...
Click to collapse
Yes, extract the stock hboot from the correct PC10IMG.zip file, then you can dd it to your hboot partition just like you originally did with the eng boot.
Or if you just flash a complete stock ROM over the top (the same version as your backup, once the backup has been restored), it will install the stock hboot anyway.
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
jakbjak said:
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
Click to expand...
Click to collapse
If that stock ROM is the same version as your rooted backup that you restored, then yes, that should be fine because the stock ROM will include the stock hboot, to put you back to S-ON via hboot.
If however the stock ROM is an earlier version than your backup, you will have to go through an additional downgrading procedure to safely be able to flash an earlier ROM (or you could end up bricked).
No, you don't flash it via Clockwork. You put the ROM image (not RUU) onto the root folder of your SD card, called "PC10IMG.zip", then boot into hboot (with the phone powered off, hold Volume Down and then press Power until it switches on) and it will open the ROM and ask if you want to flash it.
Cool, that makes sense. Thanks
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
(This RUU is exactly the one used in the 1.72 root procedure to downgrade to 1.34)
Like I plan to just execute it on the computer and let it do its thing.
My baseband version:
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
djfoo000 said:
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Like I plan to just execute it on the computer and let it do its thing.
My baseband version
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
Click to expand...
Click to collapse
I belive this is the RUU for the Europe Vision only, so if your Desire Z is not the Europe Vision I would not run this RUU.
Edit: I found this thread on your RUU, I would check it out first before flashing:
http://forum.xda-developers.com/archive/index.php/t-822908.html
In skimming the thread I see someone flashed this on a Bell Desire Z, but they super-cid with gfree first.
Edit 2:Cant you just find the stock recovery.img and then flash it to your phone using the flash_image method from terminal emulator? Since you dont have fastboot. Then re-run gfree with the -s option to get S-on again.
Heres the link to the Flash_image method:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
djfoo000 said:
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
Click to expand...
Click to collapse
Just download it myself, good question, not quite sure myself on an RUU since it wants to exe. , thought it might be a simple a unzipping it but ?
Edit : found this:http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
djfoo000 said:
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
Click to expand...
Click to collapse
Im not gonna lie, I really dont know if the G2 and the Desire Z recovery.img are the same, I know theres a link to the stock G2 recovery image here:
http://forum.xda-developers.com/showthread.php?t=834545&highlight=unroot
hrmm... Just a thought, is that issue worthy of a thread? That whether stock recoveries of G2 and Desire Z are the same, regardless of location of origin (ie Asian/European etc).
You just need to run the RUU but then not press any buttons on the screen, then find the folder where the RUU has extracted temporary files. There will be a standard location on this that depends on your exact OS. Look for the most newly-created folders at this location, and a couple of levels down from there you will find the extracted files, including rom.zip.
Sent from my HTC Desire Z
The same version of Clockwork recovery is used on the G2 and all Desire Zs. So I would have thought you'd be absolutely fine to flash the stock recovery from that DZ RUU onto your own DZ.
Sent from my HTC Desire Z
Need to return my leedroid 2.2.2 to stock.
Somehow i have lost eng s-off. Tried to install different radio but it wouldnt allow me, as bootloader says ship s-off. So have been advised that i need to downgrade again, and go through the s-off / root process again - Here
How do i go back to the easy rooted 1.32 stock again. I have an RUU for that version, but its not seeing the phone. Found a workaround - Here - but it only got so far before the phone froze, and the installer said it couldnt find phone.
Thought for a minute i had bricked the phone, so after crapping myself, decided to seek help here on how to return to 1.32!
Look at the rooting tutorials for 1.72.
AFAIK, you need to change the version number for this to work (to allow downgrade).
Do you have ship s-off or you do not?
You can't flash a radio because you don't have eng s-off, therefore no fastboot commands.
Just flash any ruu you want using the pd98img.zip method and all shall be stock. Launching an ruu update from your pc is notoriously unreliable and I would never recommend it.
Here is a guide to the method if you have no idea whet I'm talking about.
http://forum.xda-developers.com/showthread.php?t=826465
-----
Sent from my pimped up Desire HD in association with Rcmix HD v3.3.
caddish12 said:
i downt know
Click to expand...
Click to collapse
Thanks!
dr.m0x said:
You can't flash a radio because you don't have eng s-off, therefore no fastboot commands.
Just flash any ruu you want using the pd98img.zip method and all shall be stock. Launching an ruu update from your pc is notoriously unreliable and I would never recommend it.
Here is a guide to the method if you have no idea whet I'm talking about.
http://forum.xda-developers.com/showthread.php?t=826465
-----
Sent from my pimped up Desire HD in association with Rcmix HD v3.3.
Click to expand...
Click to collapse
Had tried to flash pd98img from my sd card but kept getting some error (cant remember what it was now, will check again later). So thought maybe needed to use the RUU to go back to a stock ROM, but was just guessing at that. Will have another go at PM98IMG when i get home from work.
You have Radio S-OFF, so you do not have to use the downgrade guide. Just flash 1.32.405.6 stock ROM using PD98IMG.zip (get that from the downgrade guide), and then you can use my Radio S-OFF tool to go S-ON. You can also check the S-ON instructions in my tool thread.
jkoljo said:
You have Radio S-OFF, so you do not have to use the downgrade guide. Just flash 1.32.405.6 stock ROM using PD98IMG.zip (get that from the downgrade guide), and then you can use my Radio S-OFF tool to go S-ON. You can also check the S-ON instructions in my tool thread.
Click to expand...
Click to collapse
Thanks. I tried last night to do this (though i was going to go the full downgrade route) but couldnt get it to install. But i was selecting the zip from sd card, which i think is wrong? (hboot will pick the zip up itself?)
Can you briefly explain to me what S-ON is? Im a total noob here, and always thought we were looking S-OFF to flash Kernels, Radios etc.
I owe you a thanks. Already handed out 5 today and cant give any more!
jkoljo said:
You have Radio S-OFF, so you do not have to use the downgrade guide. Just flash 1.32.405.6 stock ROM using PD98IMG.zip (get that from the downgrade guide), and then you can use my Radio S-OFF tool to go S-ON. You can also check the S-ON instructions in my tool thread.
Click to expand...
Click to collapse
hmm having problems. Have got back to stock ok. But when i try to run your tool i keep getting connection error. Have tried in XP and win 7, and from root of drive as some others have suggested worked for them. Any ideas?
EDIT: Think i have it sorted.
So I recently put Virtuous Unity on my unbranded Desire Z and now I'd like to go back to stock and unroot the phone.
Wiping the system with Clockwork Recovery and flashing my backup stock ROM created by ROM Manager.
After that I'd probably have to replace partitions 7 and 17 with the respective stock versions and finally make it S-ON only since the phone came unlocked anyway. Flashing the recovery image may come last.
Correct me if I'm wrong but wouldn't that work and once the stock ROM is on there again it should be plain sailing. No?
EDIT: Before anyone mentions using the wiki unrooting guide, I'm probably missing something here but the the PC101IMG.zip files I can get from there may not be of any help.
I would say pc10img it back, then temp root with the included psneuter on the wiki and use gfree to turn s back on. All done.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I would say pc10img it back, then temp root with the included psneuter on the wiki and use gfree to turn s back on. All done.
Click to expand...
Click to collapse
Isn't there a potentially high chance that I might brick it if the wrong PC101 is used though?
Finally managed to unroot it, temp root just wasn't doing it for some reason so instead of running around in circles I tried this.
Involved
1. Re-flashing the Stock ROM provided in this guide.
2. Following the WHOLE guide linked above.
3. To make it S-ON again we do this:
Code:
adb shell
/data/local/tmp/gfree -s on
exit
adb reboot bootloader
Should now say 'S-ON' at the top of the bootloader.
4. (Optional)
Covering up the evidence with one last flash.
The CID still shows up as "super CID" when I run 'fastboot oem boot' via ADB, but its the next best thing if you want to squeeze a free warranty repair out of HTC.
This took me all day to figure out so I'm making a guide. The 2 Big problems I had were getting the S-on patch to work and the newer Hboot that came with gingerbread refusing to downgrade to an older PC36IMG.zip.
The main reason I wanted to return to stock was for a repair, last time i did everything except s-on and the guy noticed it and black listed my esn.
Make sure you are prepared before you continue! Once you flash your radio your phone wont boot into the OS.
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Download this file I got this off a youtube video for the incredible and replaced the files with their EVO specific counterparts
Open the zip and move flash_image and mtd0.img to your sdk/tools/ folder
boot into your custom recovery and mount /system/
open up a command prompt in your tools folder
(in windows7 hold shift and right click on /tools/ there will be an option to "open command window")
Run the commands in the commands.txt file. FYI you can paste into command prompt with right click.
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Click to expand...
Click to collapse
After this you can move your stock PC36IMG.zip to the root of your SD card and reboot into your Hboot Bootloader. If everything was done correctly it should now accept PC36IMG and downgrade to stock.
Great job! Do you think there will be an easier way in the future? I don't think I would be able to do this.
Sent from my PC36100 using Tapatalk
If you run the 3.70 RUU while still s-off, will it replace the hboot with an older version? It seems like it should, but I'm confused by the 6.16 hboot.
I haven't actually ran revolutionary, so this is all theory, but I thought unrooting/s-on would work like this:
Run the RUU for 3.70. I don't have much experience with RUUs, but if they don't include radios, you would then need to reflash recovery and downgrade the radio. After reflashing etc, then flash the s-on zip. Then rerun the RUU for 3.70 to get rid of your custom recovery, or run the RUU for 4.24, since once you're s-on you can't downgrade & every RUU will be a downgrade from 6.16 hboot.
Now this may be entirely wrong, but I was just curious if it would work. I've been rooted for a while, and unrooting and s-on would be much easier for me. Even though it sounds like a pain, it still sounds more noob friendly than the version in the OP.
Either way, great job on putting this together. I know that a lot of people are curious about unrooting from revolutionary, so hopefully you've cleared some confusion.
Sent from my PC36100 using Tapatalk
Sfork said:
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Click to expand...
Click to collapse
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.
Captain_Throwback said:
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.
Click to expand...
Click to collapse
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk
plainjane said:
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?
Captain_Throwback said:
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?
Click to expand...
Click to collapse
Hboot 6.16 will not downgrade or flash S-ON currently.