Related
Hi- I had my phone rooted with s-off and stock 2.1 ROM with a few mods. I have managed to flash a stock 2.1 ROM that also put back stock recovery but it would not run unless I was s-off. Now how do I get s-on? The stock recovery would not accept it.
UnrEVOked Forever now supports going back to S-ON
http://unrevoked.com/rootwiki/doku.php/public/forever
Here is the link to the tool, just read up on that link if you are unsure of anything.
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
Yes I used the s-on tool. Now I am stuck at s-on with clock mod recovery. I need to get back to stock recovery but I can't get run a stock recovery update with s-on.
Just run the 2.1 RUU stock zip again.
I tried the 2.1 RUU It is an .exe and I was told I needed HTC sync to run it. I installed HTC sync and it would not run.
How do I run the "RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe?
I installed htc sync, got it running, plugged in my phone, chose htc sync option, then tried to run the .exe
I'll try again now on another machine.
I can extract the stock recovery and other files out of the ruu.exe file but what do I do with it. In only need the boot loader. As I said I have stock ROM and s-on.
Damn. I titles this thread wrong. I have s-on and stock rom, I need stock recovery. I also need to get this done before I leave town. I'm going to post the question with a proper title for the thread. My apology and moderater please remove this thread.
Resolved
Problem solved with the PB13img file provided with Diego Mejia's 2nd video. Worked perfectly. Did not even have to do all the adb pushing of sys files since I never put in the leaked OTA. His file version was just accepted by hboot. Awesome!
I have the latest OTA update and using ruu file was able to downgrade to an earlier version of GB which I guess was the leaked one. I tried to go back an earlier ruu (RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed) but it gave me an error about the bootloader.I have not had S-Off or root done to the phone and is just stock.
I would like to go back to the original ruu/image that was shipped with the DINC2. In worst case I will just apply the latest ruu that is the same as the latest ota.
Any suggestions?
thx
just rename any RUU to PG32IMG.zip and put onr oot of sd card and flash in hboot. since it's signed HTC you don't need root.
Were you able to do this successfully?
Sent from my ADR6350 using XDA App
andybones said:
just rename any RUU to PG32IMG.zip and put onr oot of sd card and flash in hboot. since it's signed HTC you don't need root.
Click to expand...
Click to collapse
In HBOOT I see the message saying its Loading pg32img.zip then after awhile it says it is checking pg32img.zip and then returns back to the Main screen where you can choose fastboot, recovery etc.
After booting phone backup, I attempted again to run the ruu form from windows pc and got this error "ERROR[140]:BOOTLOADER VERSION ERROR"
I did run RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed RUU. (unbranded desire)
Looks like everything worked fine, i had no errors whatsoever, system is booting fine but:
1. i'm still S-OFF
2. my hboot is 6.93.1002 (i was cm7r2, but i did run downgrader and flashed stock hboot)
3. radio is 5.11.05.27 (it keeps scanning when i turn it on, and i cannot connect to WIFI at all, it see my channel and others but just wont connect)
What's wrong?
Edit:
I fixed WIFI issue, point 1 & 2 are still to fix any ideas?
Edit2:
After flashing downgrade.img again the hboot is 6.93.9999 now.
you seemed to do everything correctly, okay, flash the stock bravo HBOOT from alpharev, then flash the downgrade utility. Extract rom.zip (you know how to do that right) from the RUU, and then extract the HBoot.nb0 file (from rom.zip).
Once you've got that, put it in a zip with the android-info.txt file and name the .zip file PB99IMG.zip... this is EXACTLY what I did and it gave me the stock S-ON Hboot Then obviously put it in root of sd
Try that, hope it helps
EDIT: sorry I dunno why I gave you that info.txt when it's in rom.zip as well :s and just remembered it won't work for you since it for Vodafone :L ahh I'm an idiot sometimes
You need to flash downgrade HBOOT in order to go S-ON.
I did even twice, prior to flashing stock hboot and also after RUU did it job, went back to see if i'm still s-off. Was still s-off so i flashed downgrade.img again but still s-off and alpharev hboot (6.93.9999)
I will try what bortak suggested though.
yeah when you flash the downgrader it wiull say "Alpharev Unlock", and HBoot version is 6.93.9999
Try the method I told you about, worked for me.
okay I just realised what you did wrong.. you said you flashed the downgrader BEFORE you flashed bravo_stock, which means you still had a normal alpharev Hboot which could not be overwritten. You need to flash the downgrader THEN run the RUU, without any other steps in between. (or again, you could just flash the stock HBoot.nb0 that you can find in rom.zip with the android-info.txt in a PB99IMG.zip)
I had to flash downgrader first because i had CM7r2 hboot originally, and i wouldnt be able to flash stock without downgrading hbooot i think.
Nope, you can flash alpharev Hboots over each other no problem. Only need to flash the downgrader when you want to use the RUU to get S-ON
Did you try my method? did it work? are you S-ON now?
sorry to bump this thread after it's been dead for so long..I have a HTC Desire that I've just unrooted to o2_uk 2.14. I used FastbootCommander v 1.1 to flash HBOOT_Downgrade then I ran the o2_uk ruu but I'm still with AlphaRev Unlock 6.93.9999 s-off HBOOT on PVT1. I tried Bortak's method of downgrading the hboot, I took the rom.zip from the ruu gingerbread 2.3 found in my temp folder, copied it to the desktop then deleted all files other than android-info.txt and copied hboot_8x50_1.02.0001_SF.nb0 to it then copied it to the root of my sdcard as pb99img.zip rebooted but recovery wouldn't flash it....can someone help me please? Even a way of flashing *.nb0 file to the phone.
live_0978 said:
sorry to bump this thread after it's been dead for so long..I have a HTC Desire that I've just unrooted to o2_uk 2.14. I used FastbootCommander v 1.1 to flash HBOOT_Downgrade then I ran the o2_uk ruu but I'm still with AlphaRev Unlock 6.93.9999 s-off HBOOT on PVT1. I tried Bortak's method of downgrading the hboot, I took the rom.zip from the ruu gingerbread 2.3 found in my temp folder, copied it to the desktop then deleted all files other than android-info.txt and copied hboot_8x50_1.02.0001_SF.nb0 to it then copied it to the root of my sdcard as pb99img.zip rebooted but recovery wouldn't flash it....can someone help me please? Even a way of flashing *.nb0 file to the phone.
Click to expand...
Click to collapse
PB99IMG.zip files are not flashed with recovery, they are flashed using the bootloader. Load into the bootloader (vol down+power) wait for it to search and find the PB99IMG.zip file, press vol up when they say: 'apply update? Vol up to confirm, vol down to cancel' and then press the power button to confirm it.
Sent from my HTC Original Desire using Tapatalk
in the bootloader..that's what I meant, it never asked me if I wanted to apply the update, it just did it's check og pb99diag, pb99img etc but didnt recognise the pb99img as an update file. but nevermind, i've solved it using fastbootcommander v1.5.1..i flashed pb99img_bravo_stock then pb99img_downgrade then the 2.14 o2_uk ruu and i now have back 0.93.0001 happy days!!
I'm also trying to S-On my desire through this method but after flashing downgrade zip from alpharev, my RUU gives hboot version error.. Please help..
same here.... flashed bravo_downgrade to get Alpharev Unlock and hboot version 6.93.9999 ...
this is what I see
AlphaRev Unlock (in pink)
BRAVO PVT4 SHIP S-OFF
HBOOT 6.93.9999
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO 5.17.05.23
Aug 10 2010, 17:52:19
RUU
guys, found this thread on my mission to restore ruu, s-on and unroot my device.
guess why? because i'm also s-off after the whole procedure.
i was running CM7r2 with Hboot 6.93.1002 before and then flashed alpharev stock hboot, then alpharev bravo downgrader. i installed the ruu and everything works out fine. i just always stay with s-off, no matter what i try.
tried bortak's solution from this thread too. didn't help.
now that i can't send fastboot commands and have no recovery either i have to keep flashing things via PB99IMG.zip method. i try the downgrader from alpharev and it says "alpharev unlocked". i then install another ruu but afterwards it will stick with s-off.
please help!
thx,
v.
Could try the 2.3 RUU...
phone was not branded, so i need to stick with the WWE versions.
right now i just rooted the phone again and will try everything once over.
am i correct if i
1. flash alpharev stoch hboot
2. flash alpharev downgrader
3. install ruu from pc
thx,
v.
---------- Post added at 04:53 PM ---------- Previous post was at 04:28 PM ----------
after 2nd try nothing changed.
i rooted, then flashed the 2 hboots in the exact order, but after ruu i still have s-off.
what's going on?
v.
vercetti said:
phone was not branded, so i need to stick with the WWE versions.
right now i just rooted the phone again and will try everything once over.
am i correct if i
1. flash alpharev stoch hboot
2. flash alpharev downgrader
3. install ruu from pc
thx,
v.
---------- Post added at 04:53 PM ---------- Previous post was at 04:28 PM ----------
after 2nd try nothing changed.
i rooted, then flashed the 2 hboots in the exact order, but after ruu i still have s-off.
what's going on?
v.
Click to expand...
Click to collapse
Hence why I said to try the 2.3 RUU, because it's different from the 2.2 ones...
BTW that RUU is the last thing your phone will ever see if it goes wrong, so do it at own risk.
hehe, first you only had "3" written there, so i thought you meant the network provider "3".
ok, so a 2.3 ruu. sure i'll try one, do you have a link?
and why would it be the last one? could i not go back to a 2.2 ruu afterwards?
greetz,
v.
vercetti said:
hehe, first you only had "3" written there, so i thought you meant the network provider "3".
ok, so a 2.3 ruu. sure i'll try one, do you have a link?
and why would it be the last one? could i not go back to a 2.2 ruu afterwards?
greetz,
v.
Click to expand...
Click to collapse
there is only one. There is a link on my guide.
If the process goes okay, then yes you may, however you need to S-OFF first, then flash the alpharev downgrader, then the 2.2 RUU.
hey bartok,
flashing 2.3 also didn't get rid of my s-off.
how come i can't get s-on? what could be the problem with my phone?
my warranty ends in 2 days and i would really like to send it in for repair. what's causing all the trouble here? everyone just seems to flash the downgrader and then install the ruu. but i'm always stuck with s-off.
please help,
thx,
v.
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.
I've done a lot of reading and see where Alpharev has a hboot downgrader but does this work with CDMA version BravoC?
I rooted using Revolutionary after having hboot 1.06 for a USCC Desire. Phone is out of standard warranty but I need to send phone in for repair under extended warranty. When I flash 2.2 RUU it cannot roll back hboot version.
Thanks!
I still haven't found anything. Thanks for the help.
what was your original Hboot number?
see alpharev page, if your model is supported try this -
flash HBOOT bravo_downgrader and right after that run appropriate RUU wich contains default hboot to protect extended warranty
as a result of this process you become S-ON again with stock Hboot
i think this may work even for CDMA version but i am not 100% sure
google it and you will find the answer
Here is about GSM Desire...
Actually I just use revolutionary to s-off my phone and it work. I test several new ROMs right now, then I try to flash stock ROM back when found this thread. I can flash the RUU HTC Froyo successfully. but...
the hboot is not overwritten. it still revolutionary. I am very sure the stock ROM I use contain hboot. because I can see it upgrade my hboot from 0.8.000 to 0.93.0001 during I flash this ROM before I s-off it yesterday.
revolutionary claim that we can get the original hboot if we flash stock ROM that contain hboot but it not working for me. maybe you need to tell them about this.
CallMeLaNN said:
Here is about GSM Desire...
Actually I just use revolutionary to s-off my phone and it work. I test several new ROMs right now, then I try to flash stock ROM back when found this thread. I can flash the RUU HTC Froyo successfully. but...
the hboot is not overwritten. it still revolutionary. I am very sure the stock ROM I use contain hboot. because I can see it upgrade my hboot from 0.8.000 to 0.93.0001 during I flash this ROM before I s-off it yesterday.
revolutionary claim that we can get the original hboot if we flash stock ROM that contain hboot but it not working for me. maybe you need to tell them about this.
Click to expand...
Click to collapse
Yeah, I flashed my carriers ruu and everything worked but the hboot.
have you guys flashed downgrader before RUU (in case you were using custom hboot off course) strange hmmm
AssassinSvK said:
have you guys flashed downgrader before RUU (in case you were using custom hboot off course) strange hmmm
Click to expand...
Click to collapse
Yeah so I first flashed the bravo_downgrader and after that the RUU and I finally got my hboot to show S-ON again! thanks alot
I asked in their IRC channel and they do not support rolling back hboot at this time.
outbackpaul said:
I asked in their IRC channel and they do not support rolling back hboot at this time.
Click to expand...
Click to collapse
but I personally just did roll back from Revolutionary hboot to stock hboot with AlphaRev's bravo_downgrade file..
velu- said:
but I personally just did roll back from Revolutionary hboot to stock hboot with AlphaRev's bravo_downgrade file..
Click to expand...
Click to collapse
Did you do that with a CDMA Desire? I don't see that listed the the devices supported list.
outbackpaul said:
Did you do that with a CDMA Desire? I don't see that listed the the devices supported list.
Click to expand...
Click to collapse
Yah, the alpharev hboot are only for GSM desire (bravo), not CDMA (bravoc)
I think u cant go back to s-on in no way at the moment..u will need a bravoC downgrader hboot
Sent from my HTC Desire
andQlimax said:
Yah, the alpharev hboot are only for GSM desire (bravo), not CDMA (bravoc)
I think u cant go back to s-on in no way at the moment..u will need a bravoC downgrader hboot
Sent from my HTC Desire
Click to expand...
Click to collapse
Ah!! Ok, I hadn't seen anything but I really appreciate you confirming this.
[8]STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-OFF"
Cause:
- Alpharev's Hboots are write protected, so that they can not be overwritten by a RUU
HOW TO S-ON
METHOD 1#
[STEP1]- Visit Alpharev and download the "Downgrader"
[STEP2]- Flash the downgrader over fastboot. This can be done with Android Flasher, cmd, or fastboot commander (Note: android flasher is the only program that does not require third party software such as Android SDK or Java JDK)
[STEP3]- You should now notice the title on the bootloader screen is "Alpharev Unlock", run the RUU again and you will have S-ON'd your device.
#METHOD 2#
[STEP1]- Instead of running the RUU again, and putting your phone at risk once more, you can simply upgrade just the bootloader manually, with the PB99IMG.zip method.
[PHASE1]- we need to extract rom.zip from the RUU.
[P1/STEP1]- Run the RUU (BUT DO NOT PLUG IN YOUR PHONE OR CONTINUE), move it to the side as it cannot be minimised.
[P1/STEP2]- go to start menu, and use the "run" feature. Type in %temp%
[P1/STEP3]- select "date modified" to "today" (to make it easier to find). There are should now be 2 folders with long names of random characters.
[P1/STEP4]- search the folders for rom.zip and extract it to the desktop.
[P1/STEP5]- delete everything EXCEPT "hboot_8x50_0.93.0001_20100810.nb0" and "android-info.txt"
[P1/STEP6]- rename the zip to PB99IMG.zip (make sure it is not PB99IMG.zip.zip)
[PHASE2]- now we need to update the bootloader
[P2/STEP1]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER). After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE.
[P2/STEP2]- Once the process is finished, you will now be S-ON.
http://forum.xda-developers.com/showthread.php?t=1275632