Hi,
After running with revolutionary and my rooted stock rom 1.47.401.4, I got yesterday a new OTA with 2.10.401.4 (2.3.5 and sense 3).
When trying to install it, it failed (blue android with big "!" on my screen)
First I downgraded my hboot back to 0.98.0000, but than I did something stupid .
I flash my hboot to the one provided with the OTA 2.00.0002, incl radio and all other stuff from the firmware.zip.
Now I ended up with a *** LOCKED *** HBOOT 2.00.0002, but also a 1.47.401.4 rom with android.
I tried to use the RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe from windows, but that fails as the hboot has the incorrect version.
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
I also searched for an RUU_Sage_HTC_Europe_*2.10.401.4*.exe as that might work because the HBOOT has the right version, but I could not find anything like that
Does anyone have an idea how I can go forward or how to go back ??
My phone is alive again as used the recovery.img procedure below and installed Saga3D 3.0. After that, I tried also the RUU installation to fully go back to stock, but that doesn't work. It complains about a security failure in hboot screen. I locked it back with 'fastboot oem lock', but that doesn't make the RUU work either.
lessimp said:
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
Click to expand...
Click to collapse
did u try that or u think that wont work?
Before I updated to 2.00.0002, I created a dd-backup on the sdcard for the 0.98.000
when I however use adb to connect, I don't see how I can restore that back without root. I also didn't see the sdcard mounted
I was also thinking ....
Would it maybe also be possible to create a PG88IMG.zip with all the right software for 1.47.401.4 ? and restore that via recovery ? would the current hboot allow a downgrade ?
Today I was able to get the **LOCKED*** off to UNLOCKED via htcdev.com
In the thread http://forum.xda-developers.com/showthread.php?t=1299438
I found this (identical to my problem)
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
I don't unserstand what I have to do next. ADB does not work anymore, and only fastboot is available. I downloaded an EXT4 recovery (4EXTRecovery_v2.1.0_saga.zip) which have me an recovery.img and a META-INF folder.
When I name the zip image update.zip, and run
C:\android>fastboot.exe update update.zip
it fails with ...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
How to I proceed to get it working ?
BTW, HBOOT is UNLOCKED but still S-ON
Please help
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
budingyun said:
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
Click to expand...
Click to collapse
You can RUU with that correct version or follow my instructions to achieve custom recovery/rom since you are already "unlocked":
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
From here on you can now flash custom ROMs that you would like that is compatible to Desire S.
Hello guys
my phone recently gots back from reparation and is in the fully stated
S-OFF & more
Locked
Pyramid pvt ship S-OFF RL
h-boot 1.27.0000
radio 11.22.3504.07_m
openADSP-v02.6.0.2226.00.0131
Recovery Locked
Stock android 4.0.3 HTC sense 3.6 rom (software version 3.32.401.5)
Click to expand...
Click to collapse
My question is what do i have to do to go back in too the state of S-OFF, unlocked recovery, Rooted, and custom rom. (the one in my signature)
IMarks said:
Hello guys
my phone recently gots back from reparation and is in the fully stated
My question is what do i have to do to go back in too the state of S-OFF, unlocked recovery, Rooted, and custom rom. (the one in my signature)
Click to expand...
Click to collapse
you are already SOFF...so not much hassle to do now
i assume you already have adb/fastboot setup..otherwise set it up suing this guide
guide to adb/fastboot setup
1.first we need verify whether you are supercid or not
if you don't know that then chk it via fastboot first
steps:
1.keep your device in fastboot mode and connect it to pc(mobile reads fastboot usb after this)
2.go to your adb folder and type this command
fastboot getvar cid
if the output is 11111111 then you are supercid
if not then do it (you can revert back to your original cid whenever you wanted just remember your original cid or save it somewhere)
command to supercid
fastboot oem writecid 11111111 (eight ones)
2.flashing firmware
get 3.32.xx.x fw from here firmware thread
its a PG58IMG file
for firmware flashing..just keep the PG58IMG file(name should be checked) on top of sdcard and boot into bootloader...the bootloader itself will identify it and will ask for update .say yes and the fw will be updated...after that you should remove the PG** file from SDcard otherwise you cant boot into bootloader (coz everytime you boot into bootloader it'll find the file and ask you whether you want to update or not..it'll be a recursive process)
(this firmware flashing is to just get the revolutionary eng HBOOT as your HBOOT state is now locked)
3.then
flashing recovery again
get latest 4EXT from here RECOVERY DB LINK
extract and put the recovery.img in your adb folder(pc)
then flash it via fastboot
command
fastboot flash recovery recover.img
then get the whatever ROM you want into Sdcard
go to recovery
first do a backup (safe keep)
then the important step(which solves petty issues if any like wifi error and all)
go to wipe|format and do "format all partitions except sdcard" this is powerful than superwipe...so superwipe is not required (i highly recommend this step when changing roms ...for upgrading roms this step is not required)
then flash the rom via recovery and ...enjoy
i tried to flash [ROM] | 04 Jun 2013 | AOSP | 4.2.2 | JellyFireBeanv2 Summer Edition | StrikeX Updated onto my desire s and now its just stock on the htc booting screen
i need to get this phone working as soon as possible and i dont mind if that means going back to stock
got these details before i started rooting yesterday
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011,15:22:15
<<<< Identifier Token Start >>>>
250906DC50D151520747FAF59C165CA6
965338ACCDA31327AE1DDED427752287
651FC922F0632A08387B492FB08F903E
61C61A41805EE625536A127B1E709089
3A773759C1726F54E125A46C96F4D7D5
D74FBAB768FEADE626A5B9CC1C72B95B
654C78049E871ECA29656ED91E3FFFDE
807096C2263F86E3620424FC1B601A52
58A45EEDC468BC30832CCFB3DDC4A4D2
A89C50576B7814E419627E6658F6B6DE
DE76E3C897D1413153A92A2302DCAA94
F2BFA661FDFDE40FF603170FF5DDFC75
DF2FE0BB83B20BF5E23D98F4DC9E1C8E
19803C6AF2105B9BEF1B09EE21077CA3
9D0DFE0BBA25B140F2ABEC03A3FBC2BD
C75641FC02117BC8CA6D57697BAD56DA
<<<<< Identifier Token End >>>>>
please help someone
Did you flash the boot.img (from the rom) in fastboot? This is necessary if the phone is htcdev unlocked (and still s-on).
theres a boot image? probably should not have rushed into this haha
teadrinker said:
Did you flash the boot.img (from the rom) in fastboot? This is necessary if the phone is htcdev unlocked (and still s-on).
Click to expand...
Click to collapse
i dont know where it is, haha thanks for replying,
1. do i need to flash it via cwm.
2. where can i find it.
3. the phones currently got the bootloader relocked haha but i should be able to unlock it again as its useless atm, its just been entirely formatted via cwm.
You can find the boot.img in the zip file of the rom (extract it from the rom you're flashing).
No, you have to flash it in fastboot mode. You must have adb and fastboot set up on your pc, reboot the phone into bootloader, and use the command :
fastboot flash boot boot.img
There are guides in the desire s general section that include more exact instructions.
teadrinker said:
You can find the boot.img in the zip file of the rom (extract it from the rom you're flashing).
No, you have to flash it in fastboot mode. You must have adb and fastboot set up on your pc, reboot the phone into bootloader, and use the command :
fastboot flash boot boot.img
There are guides in the desire s general section that include more exact instructions.
Click to expand...
Click to collapse
Thanks so much, yes i am a newbie. i have rooted a tablet and used to flash it like weekly but never had to flash the boot seperately haha
so i unlocked my bootloder again using the unlock bin file from before and the all in one toolkit, done, booted into cwm, wipe cace, wipe data/factory reset, wipe dalvvik, install the rom, gapps and beats.
then pressed power off, rebooted into fastboot ad flashing using a guide (sorry cant post a link but i will say its called [Tutorial] How to flash a new boot.img via Fastboot)
all done the guide worked perfectly, it seemed so easy, its booted into android setup now thanks so much for getting me into the right direction
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
Hi all!
First of all: I know. I am a dumbass for not doing a backup. (and several other things)
Second: Thank you for your time! I really appreciate it- thats why I tried for two days to solve the problem by searching the internet for guides to restore my phone and not stealing your time.
If you just want to help me - skip the first part ("The story"). I just had to write it down, because I am that desperate and hopeless...
The story
Beside my Nexus 5 I wanted a spare phone to go outdoors and have a nice small phone - other than the huuuuuuge Nexus.
My last phones were the HTC Sensation, a Desire GSM and the Wildfire. So I decided to get a Desire S and do what I did to all my phones and tablets yet: root it.
Because I had the dumb idea that rooting a couple of phones makes me an expert I skipped the "reading guides"-part and jumped right to the "beeing an idiot"-part and downloaded the Revoked-tool.
After I got the TWRP-recovery I also skipped the "making a backup"-part and that is where my disaster began....
The problem
I tried to root my phone, but I did not reverse the Hboot. So now my phone IS NOT s-off, but I've got a working recovery installed and I can get into Fastboot and the Bootloader.
But because my partitions are wiped I can neither boot normally nore can I install a custom recovery (because of the "s-on").
My phone has got an O2-branding, so I can't install the normal Android 4.0 RUU. Neither works the O2 RUU. I suppose, because it still is the Android 2.4 - Version ( the name of the file is "RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe") and it does not work with my phone....
Is there any chance to get a working Desire S again?
Thabks for your time....
u have stock recover. and u have (i suppose) an unlocked bootloader.
have u tried flashing the recovery through fastboot command ?
fastboot flash recovery recovery.img
download TWRP or 4EXT touch zip file - then unpack it and copy the recovery.img inside it to fastboot or android-tools folder
open cmd there (preferably with admin rights)
and run that command.
if it is able to flash a custom recovery, then u can try to flash a rom.
u might need to check if u have a sony or hitachi screen panel though (but that should have been before u tried rooting, i think)
Hi rht_sg,
thanks for your answer!
Right. My Bootloader is unlocked.
The problem is the "S-ON" I think.
I've got a recory installed, but I can not intall any custom ROM because of the "S-ON"-Mode.
Here the important things I have foregotten in my first post:
In FASTBOOT my phone says:
"
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
"
...and my recovery is TWRP v2.4.0.0
You can install a custom rom without being s-off, but you have to flash the boot.img (from the rom) manually in fastboot after installing the rom in recovery (fastboot flash boot boot.img).
I would recommend updating your recovery to either twrp 2.7 (from the thread in this forum) or the latest 4ext touch. One reason being that older recoveries fail when trying to flash kit-kat roms (error 7).
To update your recovery while still s-on, use fastboot (fastboot flash recovery recovery.img)
Thanks!
That solved it. - Now I could install a custom ROM again.
Now I follow your advice to flash the latest recovery.