Related
I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.
Did you flash a signed stock recovery before locking the bootloader?
reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s
touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.
i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards
blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.
khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Yes I did, Thank you
mikeyinid said:
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
cid: VODAP001
Could you pleaase confirm how to change my CID?
Tried fastboot oem writecid HTC__001 and that blocked bootloader...
Thank you!
Error message
C:\fastboot oem writecid HTC__001
...
(bootloader) ville_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (Too many links))
finished. total time: 1.271s
Since I posted this morning
I also tried to change CID via adb shell but it doesnt work - error message = error: device not found
And I allowed USB debugging + fastboot recognise USB connection
Any idea? really lost now!!
Thank you very much
usaff22 said:
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Click to expand...
Click to collapse
Any luck? Haven't any progress...
Many thanks
cplessier said:
Any luck? Haven't any progress...
Many thanks
Click to expand...
Click to collapse
I had a similar problem with my orange branded one s but got it up and running by doing the following :
unlock bootloader
install twrp recovery
boot into recovery (must be in recovery not bootloader or adb shell will not work)
change orange cid to generic cid http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
flash stock recovery
relock bootloader
install latest european ruu
Hope this helps
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
If your sure the cid was sucessfully changed (i used HTC_001) and you flashed stock recovery then relocked bootloader im all out of ideas. thats what worked for me.
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
What is error 155?
usaff22 said:
What is error 155?
Click to expand...
Click to collapse
Error 155 gets when either your bootloader is locked or u r using the wrong RUU
If you updated to jelly bean , sense 4+ and then rooted your ONE S and then installed other roms like CM10, etc, you will get error 155 if you try to use any RUU. Thats because your hboot is updated when upgrading to sense 4+,JB.
Thus to revert back to stock....
1. get stock ICS Sense 4.1 ROM,
2. flash stock recovery.
3. Use OTA update to jelly bean,Sense 4+.
4. Factory reset your phone to remove any non-stock stuff from the ROM.
5. you have STOCK Sense 4+!!
6. then if you want you can relock boot loader .( but I havent tried it, might cause problem)
Your hboot won't be updated unless it's a ota or a ruu am I right eg I was on 4.04 then rooted and installed trickdroid but I am still on the hboot that came with 4.04 ruu.
Sent from my HTC One S using xda premium
Same problem: Error 155: Unknown Error
I'm on Vodafone IE.
Successfully changed CID to HTC__001, restored stock, relocked bootloader and I can't install any RUU, tried
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
Any ideas?
OK
managed to update with
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
cplessier said:
I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
Click to expand...
Click to collapse
Wipe everything.Should be able to flash CyanogenMod 10. After that, change back the CID to VODAP001 (mmcblk0p4 and build.prop).
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Have you changed your CID?
mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse
yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!
Can we use this as rollback from h-boot 2.16 ?
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.
flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?
I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?
kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes
I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?
dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S
I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
pyrocide said:
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
Click to expand...
Click to collapse
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
tivofool said:
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
Click to expand...
Click to collapse
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
pyrocide said:
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
Click to expand...
Click to collapse
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
tivofool said:
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
Click to expand...
Click to collapse
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
pyrocide said:
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
Click to expand...
Click to collapse
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
tivofool said:
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
pyrocide said:
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
Click to expand...
Click to collapse
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
tivofool said:
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
Click to expand...
Click to collapse
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
pyrocide said:
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
Click to expand...
Click to collapse
Yep, that is why. Unlock that bootloader.
tivofool said:
Yep, that is why. Unlock that bootloader.
Click to expand...
Click to collapse
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
pyrocide said:
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
Click to expand...
Click to collapse
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
tivofool said:
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
Click to expand...
Click to collapse
Thanks for the help, got it booting and charging. Gonna test the battery with the extended battery from the One X+ and see how much better this battery is vs CM10.1.3 and bootloops/reboots etc.
Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.
caris said:
Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.
Click to expand...
Click to collapse
actually why did you use a ruu.exe for flashing a custom recovery?
it was an unecessary step
nevermind
if you still are on S-OFF flash 3.33 iniversal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then you can install a custom recovery
another way is to install 4ext updater(link in my signature)
from the app download and install the latest version of 4ext recovery
edit: just to know when you are locked or relocked you are limited to some fastboot commands
I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?
caris said:
I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?
Click to expand...
Click to collapse
probably you can use it via fastboot command
but it would better to flash it directly from bootloader
I updated FW (PG58IMG.zip unlocked) via Bootloader, flashed CWM via fastboot tools and it works!
@rzr86, Thanks for advices. :good:
Greets.