I'm running CM 11 nightlies on a S-Off HTC One S with hboot 2.15.
I would like to upgrade the radio, because I have no 3G data connection atm.
Most guides which I found are for the case of having no S-Off, i.e. S-On.
My best guess therefore is just to flash firmware.zip using fastboot.
However, I am unsure how to get the radio only from the latest OTA's. Inside there is the firmware.zip (in ROM.zip), which has much more than only radio.img. As far as I understand the how-to's, it is not possible to directly flash radio.img, but flashing a zip with fastboot is possible (I also tried flashing the radio.img directly, fastboot gives me 'not allowed' as expected).
The firmware.zip from the OTA is correctly packaged (it has a android.txt or so and is signed). Can I extract the radio.img, put it in a firmware.zip with the extra android file and sign it myself somehow?
Much thanks for your time!
Dooxed said:
Most guides which I found are for the case of having no S-Off, i.e. S-On.
My best guess therefore is just to flash firmware.zip using fastboot.
Click to expand...
Click to collapse
1) With S-Off, any partition is writable if you use the trick described here.
2) Firmware.zip from OTAs and RUUs also contains other stuff next to radio, such as bootloader (hboot), recovery etc. Get the firmware.zip from the OTA or RUU and extract the radio parts: radio.img, wcnss.img, and adsp.img and follow instructions at 1.
3) Can anyone explain what wcnss.img and adsp.img exactly are?
Related
I'm having stock 1.45 ROM S-ON (completely unaltered) with 1.18 HBOOT which is not "compatible" with fr3evo.
The idea is to move back to stock HBOOT 1.17 which I obtained from TMobile UK stock ROM and which will allow me to run fr3evo to obtain temp root.
If anyone would ask: why would I do that? The answer is simple: I want to make temp root and backup the device stock ROM (T-Mobile CZ) which has no corresponding RUU available for download.
Can't downgrade without S-OFF
OK, suppose I will run revolutionary and will s-off the phone.
Then the next questions:
- What will be my next steps?
- Should I install CWM recovery and run a backup?
- Will it be possible to flash stock recovery and hboot later in hypothetical situation of recovering backup of stock ROM for warranty return?
- In case of flashing stock recovery and hboot I will use TMobile UK instead of my native TMobile CZ thus the question is whether they contain CIDs (UK in my case) which will differ from backup's CID (CZ in my case)?
The idea is to leave system internals as much unaltered as possible to be able to return to branded stock 100%.
Yep, S-OFF and install CWM and then take a backup of the stock ROM (don't add root). Then in future, restore the backup, reflash the stock recovery/HBOOT and S-ON and you're good to go
EddyOS said:
Yep, S-OFF and install CWM and then take a backup of the stock ROM (don't add root). Then in future, restore the backup, reflash the stock recovery/HBOOT and S-ON and you're good to go
Click to expand...
Click to collapse
So far, so good... Sound like a plan.
Could you be more specific in how to do these steps: "reflash the stock recovery/HBOOT".
I've extracted the following files from TMobile Germany OTA (which is of the same version as my updated ROM 1.45):
android-info.txt
boot.img
hboot_8x60_1.18.0000_20110802_signedbyaa.nb0
pg2fs_spcustom.img
radio.img
rcdata.img
recovery.img
rpm.img
sbl2.img
tz.img
I think I've highlighted recovery and hboot correctly
Could you be so kind and help me with adb command lines for flashing recovery and hboot in correct order. I really DO NOT WANT to screw up my phone.
Thanks in advance.
Is the following correct?
Could anyone confirm that the following fastboot command lines are correct ones for my scenario:
Code:
fastboot flash recovery recovery.img
fastboot oem mb [B][I]9C068490[/I][/B] 1 30
fastboot flash hboot hboot_8x60_1.18.0000_20110802_signedbyaa.nb0
fastboot reboot
I am really not sure about the magic oem numbers since I found it on Wildfire related threads, so could anyone confirm correct value for Sensation?
Edit:
I've found on different forums that when S-OFFed by Revolutionary fastboot oem mb will not work, could someone confirm?
Anyone?
I would really appreciate the answer of competent power user and/or developer.
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.
Does anybody know where to get an hboot image v1.09 or below?
Can it be extracted from an RUU file (not shure about this)? Any instructions on this anywhere? (I'll go and search myself after this post - but any hints are welcome).
rootrider said:
Does anybody know where to get an hboot image v1.09 or below?
Can it be extracted from an RUU file (not shure about this)? Any instructions on this anywhere? (I'll go and search myself after this post - but any hints are welcome).
Click to expand...
Click to collapse
Its in the T-Mobile 1.84 ruu. Search how to extract ROM packages from ruus. Its a fairly easy process and you will end up with a ROM.zip that contains everything, including that hboot version.
Sent from my HTC One S using Tapatalk 2
You can extract hboot images from RUUs and OTAs. In RUUs it is directly in rom.zip, in OTAs it is in firmware.zip. I posted some here: http://forum.xda-developers.com/showthread.php?p=31108359#post31108359 It includes 1.06.
Your hboot sits in mmcblk0p12. I doubt we can write to it, and if we can I fear brickage. Be careful.
-Jobo
is there any known issues with flashing recovery onto a device with 1.09?? I have 1.09 and i cant get any recoveries to stick.
Here is the hboot you requested. The link will last until I clean up my dropbox folder.
https://dl.dropbox.com/s/qjtzpt4eu7ts4xp/hboot_8960_1.09.0000_20120402_signedbyaa.img?dl=1
Enzopreme said:
is there any known issues with flashing recovery onto a device with 1.09?? I have 1.09 and i cant get any recoveries to stick.
Click to expand...
Click to collapse
I had this issue when I first tried to flash a new recovery. I had to flash the interim CWM recovery by Paul Brian first then updated to twrp at a later time. Below is a link to the recovery that worked for me when I had the problem.
http://forum.xda-developers.com/showthread.php?t=1579584
Help
I'm trying to return my old HTC One XL (Telstra) back to stock. It's current state is:
S-Off
CID = 11111111
TWRP
hboot: 2.15
I've found the latest full RUU from this thread (all the links to newer RUU are broken):
http://forum.xda-developers.com/showthread.php?t=2119610&page=5
3.17.841.2
File Timestamp: 04/12/12
Publically Seen: 24/12/12
Android: 4.1.1
Kernel: 3.4.10-g240d4d5
hboot: 2.14.0000
radio: 0.23a.32.09.29_10.128.32.34a
First, can I us this RUU even though I have a newer hboot (2.15) installed?
Second, do I need to change my CID back? (using fastboot oem writecid TELST001). Will changing the CID loose my S-Off?
Third, is this the process:
1) Flash the stock recovery:
fastboot flash recovery recovery.img (taken out of the RUU)
fastboot reboot-bootloader
fastboot erase cache
2) Flash the stock boot.img
fastboot flash boot boot.img (taken out of the RUU)
fastboot reboot-bootloader
fastboot erase cache
3) Re-lock the boot loader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4) Load RUU
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
After all this, I assume I'll loose TWRP etc. but will have a stock phone, and the ability to load OTA updates from the carrier.
THANKS
That 3.17.841.2 file isn't an RUU, it's an OTA. It's a zip file, an RUU is always an exe program. There's only one Telstra RUU available and it's a much earlier version. You can't flash that file using fastboot, an OTA can only be applied via stock recovery, and it requires the correct previous OS to be already installed on the device. If you want to return the device to stock you just run the latest actual RUU (1.89 from memory), and follow this process:
1) Run RUU exe via Windows.
2) Revert to Telstra CID.
Code:
fastboot oem writecid TELST001
3) Lock bootloader.
Code:
fastboot oem lock
4) Go back to s-on.
Code:
fastboot oem writesecureflag 3
5) Take OTA updates via Settings/About Phone/Software Updates until you reach the point you wavy to be at.
Sent from my Evita
timmaaa said:
That 3.17.841.2 file isn't an RUU, it's an OTA. It's a zip file, an RUU is always an exe program. There's only one Telstra RUU available and it's a much earlier version. You can't flash that file using fastboot, an OTA can only be applied via stock recovery, and it requires the correct previous OS to be already installed on the device. If you want to return the device to stock you just run the latest actual RUU (1.89 from memory), and follow this process:
1) Run RUU exe via Windows.
2) Revert to Telstra CID.
Code:
fastboot oem writecid TELST001
3) Lock bootloader.
Code:
fastboot oem lock
4) Go back to s-on.
Code:
fastboot oem writesecureflag 3
5) Take OTA updates via Settings/About Phone/Software Updates until you reach the point you wavy to be at.
Sent from my Evita
Click to expand...
Click to collapse
Won't running the exe RUU before changing the CID fail?
And I thought you could still get the RUU as a ZIP (although most are just smaller OTA updates). The ZIP is 700Mb.
DACcer said:
Won't running the exe RUU before changing the CID fail?
Click to expand...
Click to collapse
No, you have s-off. Having s-off bypasses all security checks.
DACcer said:
And I thought you could still get the RUU as a ZIP (although most are just smaller OTA updates). The ZIP is 700Mb.
Click to expand...
Click to collapse
No, an RUU is always an exe file. Just like an OTA is always a zip file.
Sent from my Evita
timmaaa said:
No, you have s-off. Having s-off bypasses all security checks.
No, an RUU is always an exe file. Just like an OTA is always a zip file.
Sent from my Evita
Click to expand...
Click to collapse
Sweet, cheers timmaaa .
Now, I just need to find the RUU, all the links are either broken, or to the HTC website which has gone.
Any suggestions?
And would I need to downgrade HBOOT before RUU?
DACcer said:
Sweet, cheers timmaaa .
Now, I just need to find the RUU, all the links are either broken, or to the HTC website which has gone.
Any suggestions?
And would I need to downgrade HBOOT before RUU?
Click to expand...
Click to collapse
Answer my own question:
http://androidruu.com/index.php?developer=Evita
Does this sound right:
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
You'll find the RUU here:
http://androidruu.com/?developer=Evita
You don't need to do anything before running the RUU, just connect in fastboot mode and get it cracking.
PS. We press the thanks button to show our gratitude on XDA [emoji2]
Sent from my Evita
timmaaa said:
You'll find the RUU here:
http://androidruu.com/?developer=Evita
You don't need to do anything before running the RUU, just connect in fastboot mode and get it cracking.
PS. We press the thanks button to show our gratitude on XDA [emoji2]
Sent from my Evita
Click to expand...
Click to collapse
All worked . Thanks!!
You're welcome, glad to help.
Sent from my Evita
I got the HTC One S (S4) with Hboot 2.15 carrier is Virgin Mobile Canada (Bell Mobility, CID: BM_____1) with bootloader unlock via HTC Dev. I have been using CyanogenMod for quite some time and have no nandoird backup. My phone was updated to JellyBean via an OTA prior to unlocking and installing custom rom.
My reason from wanting to restore to stock is that I can't facepalm s-off but discovered that Moonshine s-off is compatible with my phone and stock OTA from carrier. I want s-off mainly to flash custom kernel. I've been just using fastboot to flash the boot.img thus far but seems that I can't do this with customer kernels.
I looked on the RUU thread in the development section and there is no RUU for my phone (ally RUU's for my carrier are older and don't work). The signed OTA for BM is available as a zip. There is no .exe here. Inside the OTA zip there is a firmware.zip which contains things like the radio, recovery, and boot.img. The zip for the OTA also includes a folder for /system. This is not a system.img but just a folder. There are some other small files also.
I tried locking the bootloader via fastboot and then flashing the OTA zip that doesn't work. If I extract the firmware.zip from the OTA's zip and after running "fastboot oem rebootRUU" I am able to flash the firmware.zip successfully. This however doesn't allow the phone to boot as nothing is flashed to /system.
I'm not sure how to get this to work. I read that what I need to do is rename the OTA's zip to update.zip and place is sdcard partition and then I can from the stock recovery flash this. I am able to get in the stock recovery but when there it displays and error saying that it can't mount sdcard (both CWM and TWRP can mount SD card). How do I flash this to restore to stock. How can I get the /system part of the OTA to flash?