Related
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Problem is my phone can't boot into system,
pmbldc said:
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Click to expand...
Click to collapse
Hi,
What exactly are you trying to do?
malybru said:
Hi,
What exactly are you trying to do?
Click to expand...
Click to collapse
My phone can't boot into system and now s-on, so i want to do something to make it work
pmbldc said:
My phone can't boot into system and now s-on, so i want to do something to make it work
Click to expand...
Click to collapse
Hi,
Were you s-off before?
What did you flash to make you s-on?
Last night I unlocked the bootloader n been having the same problem but mind say S-on n I don't know what's next
Sent from my HTC Sensation 4G using XDA App
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
malybru said:
Hi,
Were you s-off before?
What did you flash to make you s-on?
Click to expand...
Click to collapse
Sorry to reply so late.
Previously, my phone was eng s-off and got super cid.
After i flash ICS firmware, bootloader was then locked.
After that i did some stupid things, the bootloader turned into "locked", "security warning" and s-on. I succeeded to unlock bootloader by htcdev and get rid of "security warning", at that time i can boot into recovery normally and wipe or flash roms. But it just can't boot into system. I tried fastboot commands to flash but failed just because "it is not allowed in the remote devices".
i tried PG58IMG files but the bootloader shows no image or wrong image.
Can you give me some advice? Thank you very much
ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
My phone had been rooted and end s-off before things happened.
i flash IMG.zip to try to flash a rom( Somebody post that ICS rom can be flash by IMG.zip) or fix the bootloader problem. It's almost the only way to flash a rom for me
I checked the cid and it is still 11111111(Got super cid before) although bootloader is s-on.
Now the state of the bootloader is
1, unlocked
2,s-on
3,cid is 11111111
4,can boot into recovery
5,can't install PG58IMG.zip
6,fastboot command can't write anyting
7,if flash some rom, phone will be stuck at the splash screen which seems splash partition is writable
Thank you!
greenhtc982 said:
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
Click to expand...
Click to collapse
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
ilostchild said:
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
Click to expand...
Click to collapse
I format the sdcard in fat32 format and place img that revert to hboot 1.17 in sdcard. Reboot into bootloader, but it shows "no image or wrong image".
I also try fastboot command but i don't know the command format. Would you give me an example please? Just a fastboot command to install img no matter s-on or s-off. Such as "fastboot flash hboot hboot.img".
My device is now s-on.
pmbldc said:
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
Click to expand...
Click to collapse
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
greenhtc982 said:
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
Click to expand...
Click to collapse
You mean you can flash leedroid now, don't you?
Can you boot into system？
pmbldc said:
You mean you can flash leedroid now, don't you?
Can you boot into system？
Click to expand...
Click to collapse
Yes its working, but i would like to flash other ROM's
Same Problem
Hi, I can't flash PG85IMG.zip wither except that I have S-Off??
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Phateless said:
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Click to expand...
Click to collapse
nandroid backup wont have recovery (it just has the backup of ROM)..so it wont work
as far as flashing recovery via Pg58IMG.zip file from bootloader
you need to make sure that android-info.txt inside the zip has your cid and mid
if it doesn't match..just edit and replace with yours
to get your cid and mid---fastboot commands
fastboot getvar cid
fastboot getvar mid
Phateless said:
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Click to expand...
Click to collapse
I hope you are still on an ENG Hboot, if not, please get user friendly firmware corresponding to your CID and flash it.
Now, I've attached a recovery.img, this is your stock recovery.
Connect fastboot usb
fastboot flash recovery recovery.img
fastboot reboot
Then apply OTA.
PS: Being a senior member I assume you don't need more help than that, if you do, please post back
ganeshp said:
nandroid backup wont have recovery (it just has the backup of ROM)..so it wont work
as far as flashing recovery via Pg58IMG.zip file from bootloader
you need to make sure that android-info.txt inside the zip has your cid and mid
if it doesn't match..just edit and replace with yours
to get your cid and mid---fastboot commands
fastboot getvar cid
fastboot getvar mid
Click to expand...
Click to collapse
kgs1992 said:
I hope you are still on an ENG Hboot, if not, please get user friendly firmware corresponding to your CID and flash it.
Now, I've attached a recovery.img, this is your stock recovery.
Connect fastboot usb
fastboot flash recovery recovery.img
fastboot reboot
Then apply OTA.
PS: Being a senior member I assume you don't need more help than that, if you do, please post back
Click to expand...
Click to collapse
Thanks for your help guys.
I'm not trying to apply ota, I've already done that. I'm already at bone stock ics, and trying to flash clockwork recovery so I can restore a nandroid of cm7, but the new Hboot doesn't like any of the files that used to work fine.
Unfortunately I am not on an engineering Hboot, but I am still S-off. Will fastboot still work?
The phone boots and runs fine, but I might be stuck with no way back to root.
This thread is about the sensation, but I'm using the glacier because it still has cm7 on it.
Sent from my HTC Glacier using xda premium
Phateless said:
Thanks for your help guys.
I'm not trying to apply ota, I've already done that. I'm already at bone stock ics, and trying to flash clockwork recovery so I can restore a nandroid of cm7, but the new Hboot doesn't like any of the files that used to work fine.
Unfortunately I am not on an engineering Hboot, but I am still S-off. Will fastboot still work?
The phone boots and runs fine, but I might be stuck with no way back to root.
This thread is about the sensation, but I'm using the glacier because it still has cm7 on it.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Mate, just go my tool (link in description), there is a recovery.img for 4EXT in the attachments.
Flash it like I told you. If it fails , you will need to get an ENG boot by flashing appropriate fw.
Hope this helps.
kgs1992 said:
Mate, just go my tool (link in description), there is a recovery.img for 4EXT in the attachments.
Flash it like I told you. If it fails , you will need to get an ENG boot by flashing appropriate fw.
Hope this helps.
Click to expand...
Click to collapse
I think you misunderstand. I am not trying to apply the OTA because I have already done that. I am currently stuck at stock rom, with stock recovery, but s-off, and I'm trying to get my custom recovery back so I can restore a cm7 build, or maybe flash cm9.
Right now I'm installing drivers so I can try your fastboot commands.
It worked! I just had the wrong mid/cid in the script. Thanks guys, I'm back in business!
Phateless said:
I think you misunderstand. I am not trying to apply the OTA because I have already done that. I am currently stuck at stock rom, with stock recovery, but s-off, and I'm trying to get my custom recovery back so I can restore a cm7 build, or maybe flash cm9.
Right now I'm installing drivers so I can try your fastboot commands.
Click to expand...
Click to collapse
4EXT is a custom recovery. You will be able to restore your NANDROID backup through that recovery.
I don't know how to make this any clearer mate.
kgs1992 said:
4EXT is a custom recovery. You will be able to restore your NANDROID backup through that recovery.
I don't know how to make this any clearer mate.
Click to expand...
Click to collapse
The problem was that the hboot wasn't accepting my pg58img.zip. I was using that to try to flash cwm5. I think you were misunderstanding the problem I was having.
Phateless said:
The problem was that the hboot wasn't accepting my pg58img.zip. I was using that to try to flash cwm5. I think you were misunderstanding the problem I was having.
Click to expand...
Click to collapse
Yes, because you need an unlocked Hboot for pg58img to be flashed.. so instead of solving the problem, I gave you a workaround of installing 4ext instead of cwm mate..
Sent from my HTC Sensation XE with beats audio
kgs1992 said:
Yes, because you need an unlocked Hboot for pg58img to be flashed.. so instead of solving the problem, I gave you a workaround of installing 4ext instead of cwm mate..
Sent from my HTC Sensation XE with beats audio
Click to expand...
Click to collapse
I have a locked hboot, but S-OFF prevailed because I had done that before applying the ICS ota update.
The issue wasn't which recovery I was installing, the issue was that my hboot wouldn't accept my pg58img.zip file because I didn't have the correct cid and mid in there. Once I corrected that I was able to flash cwm recovery 5.
Your solution of using fastboot to confirm my mid and cid did help, I just chose to use a different recovery. Does that make more sense?
Hi, I want to flash a development RUU, but everytime I try, I get Error [155]. This RUU is supposed to have 1.13.0000 bootloader version, but I don't know how to update from 1.06.0000 and if it may cause the error.
Any suggestion about it? Thanks in advance.
You're talking about ONE S, right?
Right, HTC One S
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
azzledazzle said:
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
Click to expand...
Click to collapse
Yes, I have the same CID that is inside the RUU.
Could you tell me how to run it from fastboot?
I'm trying almost everything I can (locked, relocked, unlocked, stock recovery...), even I'm trying now to update to the latest OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2 (now I have 1.53.401.2 from Orange Spain) as it has a firmware update (maybe hboot 1.13.0000?) what I think that can be one of the reasons why I can't flash the rom I need.
Thanks in advance!
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
azzledazzle said:
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
Click to expand...
Click to collapse
Yes, it's something I've already tried. Another problem I'm trying to solve is when installing from stock recovery, cause it says sdcart can't be mounted...
What are you trying to install from Stock Recovery ?? you cant flash an RUU and all flashable zip files MUST be signed otherwise it will fail..
I also had the cant mount sd card error in stock recovery, But when i tried CWM i didnt.. Dont know much about how stock recovery works, I just know i dont like it lol
lol, me neither!!!
I'm trying to install a stock rom, so I am supposed to do it from stock recovery, that's the matter. But I can't do it because it can't mount sdcard. I'm getting crazy, but now it is something personal, between the phone and me!!! I'll try to be patient and find the solution.
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
azzledazzle said:
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
Click to expand...
Click to collapse
Ok, it is the third option, and evidently, I'm not S-OFF. I had read a thread where they dissected this zip and I thought it was useful. Now I have found the RUU, I will try to install it. I've changed the zip and relocked it but I'm still finding Error [155]
Its useful if you are S-OFF, You just extract the ROM.zip from the RUU, Rename it to the phones model number, So in our case it would be PG40100.img ( i think) and then flash it in bootloader. However ignore this option as it wont work with a S-ON device...
If you still get the Error 155 message and you're positive you've done everything correctly, Maybe download the same / another RUU, Chances are it could have been a bad / corrupted download It happens to us all !
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
rpachecoh said:
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
Click to expand...
Click to collapse
I have done exactly (!!) the same, but you know, I have Hboot in version 2.15. And I can run none of RUUs, because I think they are not compatible with this version of Hboot (And this is that Error 155 for me). Well, so what can I do for installing the Stock RUU to my One S ?
Recently I tried out a custom rom on my T-mobile branded One S, but I want to revert back to stock in order to do a S-OFF.
Before flashing the custom rom I ran the latest official t-mobile firmware, non rooted, original recovery, h-boot 2.16 and radio 1.15, S-ON. I unlocked the phone with an HTC-dev unlock token, flashed TWRP recovery and flashed a custom rom but left the phone S-ON.
Now I want to revert back to stock so I can do a S-OFF (which is needed for certain roms). I picked a RUU corresponding my CID t-mob101, in this case the only one I could find was:
Code:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
I wanted to try this one, but the download link is dead:
Code:
RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_si gned.exe
I flashed back the original recovery, relocked the phone and tried to run the RUU. However when running the RUU I get an 155 error, which means the RUU isn't corresponding to my CID?
Does this mean i'm out of any options reverting to stock? I don't have a nandroid backup..
Thanks in advance!
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
First: S-off using facepalm follow this:
1) update your android sdk by clicking android sdk manager and then update from there.
2) after the update finished, shut down your computer and then turn it on again.
3) turn off your phone, just leave it off for like 5 minutes then go to recovery, wipe cache and dalvik cache, then fix permissions then reboot to system.
4) using ONLY the oem htc usb cable, plug in your phone to a usb 2.0 port.
5) just before doing anything else, first check if your phone is recognized by typing "adb devices", there you should see your devices' serial number if it's recognized correctly.
6) then proceed to the steps of facepalm.
Just remember to NOT do the fastboot flash firmware again after error 92. Then after finishing "fastboot oem boot", your computer should then recognize again your phone, then you could proceed to the last three commands.
This is how i managed to have s-off using facepalm. At first i was really frustrated of that error 99, but a little reading and searching won't hurt you.
Take note that the steps i just said may or may not be required to do so, and i don't know if all these steps are really necessary but i just want to share to you guys that have had the same problem as mine. Good luck guys. Hope this helps.
Click to expand...
Click to collapse
hongha_222 said:
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
Click to expand...
Click to collapse
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
mk13139 said:
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
Click to expand...
Click to collapse
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
hongha_222 said:
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
Click to expand...
Click to collapse
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
mk13139 said:
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
Click to expand...
Click to collapse
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
hongha_222 said:
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
Click to expand...
Click to collapse
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
cyberusman said:
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
Click to expand...
Click to collapse
I was on HBOOT 2.15 (from JB OTA). With that hboot, you can not get SuperCID only by altering it in mmcblk0p4, so I had to do s-off first. If you have SuperCID, why dont you try facepalm s-off method? http://forum.xda-developers.com/showthread.php?t=2155135
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
rolo143 said:
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Have you tried my instructions that are on this page? http://forum.xda-developers.com/showpost.php?p=46939498&postcount=7
I haven't. Can I use that method and install the backup doesn't matter which firmware version I have?
Sent from my One S using xda app-developers app
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
When you had this problem were you on hboot 2.16? I have super cid but when i try to flash the zip file for face palm s-off it gives me error 99 unkown fail
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