Related
I've successfully set S-OFF for my HTC Wildfire using AlphaRev X Beta after doing these steps:
1- Downgraded HBOOT version from 1.01.0002 to 1.01.0001 (My Arabic based stock HBOOT version didn't work with AlphaRev X)
2- Using AlphaRev X Beta tool to set S-ON to S-OFF
3- Doing backup for ROM and Bootloader
4- Installing ClockWorkMod custom recovery
5- Doing stock ROM Nandroid backup.
6- Installing custom ROM: CM7
For some reason, I'd like to perform a complete stock factory reset, thus, I got the following:
1- Original HTC Wildfire 2.2.4 RUU (Arabic Locale): "RUU_Buzz_Froyo_HTC_ARA_2.37.415.1_Radio_13.55.55.24H_3.35.20.10_release_166943_signed.exe"
2- Extraction of the existing RUU EXE file for rom.zip extraction.
3- Stock HBOOT 1.01.0002: "hboot_7225_1.01.0002_101227.nb0", extracted from stock rom.zip
The Question is: 1- How can I revert back to the original Wildfire for both: Stock ROM, Stock Recovery and Stock HBOOT?
Current HBOOT version: AlphaRev 6.01.1022 HBOOT
This means that installing RUU directly will fail as current HBOOT v. 6.01.1022 is too newer (apparently) than the included 1.01.0002 with the package.
In a question to the AlphaRev X Developer team, I only get one answer to overwrite HBOOT and it was:
Code:
fastboot oem mb 9C068490 1 30
fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
I'm not sure of those commands at all and I'm afraid doing those to brick my android.
2- I'd like also to know when should I use those fastboot commands?
3- Should I remove clockworkmod to do the fastboot commands?
4- What will happen to the bootloader and the custom ROM after executing those commands?
5- Can anybody explains what does the command fastboot oem mb 9C068490 1 30 mean?
I think all I need is just to overwrite HBOOT with stock one then perform the normal RUU from PC, so I just need help with this point!
I'm very appreciated for your help!
Afaik there's no way to get hboot 1.0 back yet.
Interesting, this probably implies a downgrader wont be needed!
I cant understand by "when" you should. The answer is obviously when you need to get your Stock HBoot! But, I would recommend you remove your Custom ROM and Clockworkmod before you attempt to restore your Stock HBoot. The Stock HBoot doesnt support Custom Recoveries and ROMs, and may lead to issues. Both can be removed by simply flashing any Wildfire RUU, which will restore your Stock ROM, Stock Recovery, but not your Stock HBoot.
Once that is done, follow the 2 commands given to you. But, I would recommend you to extract the HBoot from WWE Froyo 2.22.405.1, since it seems the commands are specifically for that HBoot. Not the 2.37 Arabic one you have extracted. While it should work with the Arabic ROMs HBoot, I wouldnt take chances.
For Fastboot commands, you will need the Fastboot and ADB Binaries for Windows. You can get them here:
http://forum.xda-developers.com/showthread.php?p=14693680
Then, place the nb0 file in the folder where you have placed your Fastboot binary, Open Command Prompt, Browse to it, and execute the commands. The first command obviously is some sort of command which allows "downgrading" of the HBoot.
Disclaimer Note - What all I have written above are from my understanding of your post. HBoot flashing is a very sensitive process, and, I am not responsible if you brick your phone.
Thanks 3xeno for the quick reply. I meant by when was in your reply (Firstly I have to restore stock recovery and stock ROM using the RUU then using fastboot commands).
I understand also that RUU I should use to restore stock recovery and ROM must have the HBOOT.nb0 removed in order not to get any HBOOT error during this process, is that true?
In another way, will the AlphaRev X HBOOT 6.01.1022 with S-OFF allow running stock recovery and stock ROM without needing to overwrite the HBOOT (some would prefer to overwrite to stock HBOOT for warranty stuff... etc)?
And my original stock ROM was Arabic based one, so the commands above won't work with me? (Note that second line will be hboot_7225_1.01.0002_101227.nb0 as from my information that HBOOT 1.01.0002 supports locale options.
Thanks!
ahmedmelm said:
Thanks 3xeno for the quick reply. I meant by when was in your reply (Firstly I have to restore stock recovery and stock ROM using the RUU then using fastboot commands).
Click to expand...
Click to collapse
First restore the stock things and then use those fastboot commands. You can also restore stock things (except hboot) from fastboot flashing or pc49img process.
I understand also that RUU I should use to restore stock recovery and ROM must have the HBOOT.nb0 removed in order not to get any HBOOT error during this process, is that true?
Click to expand...
Click to collapse
I think some people even used ruu without removing hboot.nb0 (just for rooting after alpharevx). But I haven't done it (not willing to get back to stock). For me alpharevx s-off and cm7 are more than enough. And you can also remove nb0 file from rom.zip and use the rom.zip with pc49img process to get back to stock things except hboot.
In another way, will the AlphaRev X HBOOT 6.01.1022 with S-OFF allow running stock recovery and stock ROM without needing to overwrite the HBOOT (some would prefer to overwrite to stock HBOOT for warranty stuff... etc)?
Click to expand...
Click to collapse
Yes, it will.
And my original stock ROM was Arabic based one, so the commands above won't work with me? (Note that second line will be hboot_7225_1.01.0002_101227.nb0 as from my information that HBOOT 1.01.0002 supports locale options.
Thanks!
Click to expand...
Click to collapse
You need to really have clarification before doing this. Better contact the team again.
You have got 2 fastboot commands right. I think the 1st command may be specific to hboot 1.01.0001. . This needs to be clear. And also confirm whether it can be flashed on wildfire with previous Arabic based stock rom. I think better to use WWE stock rom to restore stock recovery and os. Then using hboot 1.01.0001.nb0 from wwe ruu.
NOTE : I'm not responsible for any brick of your phone. I just tried to make things clear.
Sent from my HTC Wildfire using XDA App
- No, it is not necessary to remove the HBoot file from an RUU before flashing it. You can normally flash an RUU on your AlphaRev S-OFF'ed Wildfire. It will not touch the HBoot, but, it will remove your Custom Recovery and Custom ROM.
- Yes, AlphaRev will allow you to run with Stock recovery and Stock ROM. This is exactly what happens immediately after you complete running AlphaRev X. Your phone has a new HBoot, but the Recovery and ROM are untouched. (Which is why you have to follow additional procedures to get Custom Recoveries and ROMs)
- The above commands *should* work for you, provided you replace the values with the appropriate one, but, I am not too confident in you doing that because AlphaRev didn't support all versions of HBoot 1.01.0002, and, I think the Arabic official ROM was among them. Which is why I am suggesting you follow the above commands with the WWE 2.22.405.1 HBoot. In any case, after that, you will have a Stock Recovery, ROM, and HBoot, and you can again run the Arabic RUU as normal, and get back your phone in your stock condition, with the Arabic locales, and on version 2.37
Last Question
Thanks everyone for the quick and effective answers, I decided to perform an installation of stock RUU (Recovery and ROM) with AlphaRev X HBOOT 6.01.1022 without needing to overwriting HBOOT version (except if I need to get help from HTC Support - warranty purposes ).
Yes, the first step after setting S-OFF is that I get a stock ROM and recovery before trying to get custom recoveries and ROMs, but what I have used was WWE ROM which was included in the guide
Last question is: After installing stock ROM and Recovery over patched S-OFF HBOOT 6.01.1022, is it possible to overwrite it with stock HBOOT 1.01.0002 in the future using fastboot commands, or it won't go through because stock ROM/recovery are not rooted?
Thank you!
It should go through, because Fastboot is a function enabled by the Bootloader (HBoot). The Recovery / Root has got nothing to do with it.
Nvm...
Presently Fastboot flashing on wildfire is a feature of alpharevx hboot s-off only. It should be there as long as alpharev hboot is there.
it works!!!! my gosh! back to original h boot 1.01 WWE FROYO extracted
Is S-ON comes back? If not, it still will not have warranty.
Yes. S-on is back.
fastboot oem mb 9C068490 1 30
Click to expand...
Click to collapse
What is it for? My buzz is ukrainian so is it right for me ? Sorry for my english
Well if overwriting hboot with fastboot is possible. then why not overwrite it with
HBoot 0.08.0008 so if you want, one can use Unrevoked to gain s-off in the future no matter what version of Rom you are using. (possible)???
As long as you have alpharevX s-off to start with..
I will try... later
Fr3ddY303 said:
Well if overwriting hboot with fastboot is possible. then why not overwrite it with
HBoot 0.08.0008 so if you want, one can use Unrevoked to gain s-off in the future no matter what version of Rom you are using. (possible)???
As long as you have alpharevX s-off to start with..
Click to expand...
Click to collapse
Has anybody tried this yet? Really interested to know if it's possible.
Can you help me with the hboot file? I downloaded the priginal ruu, but i didnt found a thing. Thanks
adrianplacinta said:
Can you help me with the hboot file? I downloaded the priginal ruu, but i didnt found a thing. Thanks
Click to expand...
Click to collapse
You have to extract the ROM.zip from the RUU's EXE file. Anyway, I have attached it from the WWE 2.22.405.1 RUU. Remember to unzip/rename before use.
Standard Disclaimer applies - I am not responsible for bricks. You are doing this at your own risk.
Marurban said:
Is S-ON comes back? If not, it still will not have warranty.
Click to expand...
Click to collapse
Yes! S-ON is back very successfully! I've got my phone as if I got it from HTC distributor! I'll post a full thread for a step by step guide to S-OFF then S-ON back ASAP!
I`ve done it. The H-Boot is 1.01.0001 and ii is also s-off. Interesting
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.
When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!
Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app
To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?
sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!
Your welcome...
Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app
Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.
It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse
Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.
when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery
Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!
Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
designflaw said:
Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Click to expand...
Click to collapse
You have to downgrade your hboot. to 2.10
FinZ28 said:
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
Click to expand...
Click to collapse
Thank you.
accessing said:
You have to downgrade your hboot. to 2.10
Click to expand...
Click to collapse
How do I downgrade my hboot to 2.10?
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
UPDATE: Found answer: http://forum.xda-developers.com/showthread.php?p=16949711#post16949711
gellybelly said:
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
Click to expand...
Click to collapse
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Thank you
nice thread guys..been looking for this..:good:
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
Jsparta26 said:
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
Click to expand...
Click to collapse
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
designflaw said:
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
Click to expand...
Click to collapse
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
chickipaul said:
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Click to expand...
Click to collapse
Captain_Throwback said:
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
Click to expand...
Click to collapse
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Hi Design Flaw. I just read your current post about what you tried. It sounds like something got corrupted in system files of the phone, that's why your phone is crashing. Question can you get to your bootloader screen by removing the battery for a few seconds, reinstalling the battery then hold volume down and the power button at the same time. If you can get into the bootloader screen where it says on the top of your screen has the Hboot version 2.18 and the S-On. I recommend to unlock the bootloader with your unlock_token file from htc dev first. I will borrow my wife's evo 4g and let her have my evo 3d and try to duplicate the same concern on her phone to help you figure out your phone. Post back here when you have time to work on your phone. I will help you out.
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Captain_Throwback said:
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Click to expand...
Click to collapse
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
designflaw said:
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
Click to expand...
Click to collapse
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Captain_Throwback said:
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Click to expand...
Click to collapse
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
designflaw said:
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
Click to expand...
Click to collapse
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Captain_Throwback said:
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Click to expand...
Click to collapse
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
designflaw said:
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
Click to expand...
Click to collapse
I have no idea. It should really work either way. Not sure why it doesn't. Though . . . It could be because the device can't reboot into RUU mode because you're not running it from a stock Gingerbread ROM (like I keep saying you need to flash).
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.
Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.
RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456