Related
Hello!
After a freak accident during which my DHD landed in our heater (see attached photo - mind you, still works perfectly!!!), I got myself a nice SXE. Proceeded to gutting it, installed Revolution HD ROM, then tried to update the radio but it wouldn't do it.
Curious, I checked the bootloader. Where it said something like UNLOCKED at the top (??), now it says LOCKED... The full text:
Code:
***LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011,12:14:25
My question is, what exactly has been LOCKED again, and how did it happen?
Thanks so much...
[EDIT]
...and, of course, I found this minutes after posting, even though I had searched like a madman:
[09Jan]Helo my HBOOT says **Locked** when I updated to the new firmware
Ignore it, its fine, your still S-off and the bootloader is still unlocked. The only thing thats locked with the new firmware is the ability to perform advanced fastboot commands so flashing splash screens, pushing a radio. It wont affect most normal users, so no need to worry
Click to expand...
Click to collapse
Still, strange I couldn't flash the radio... file was pushed, but writing was denied...
With the Hboot "Locked", your phone can react to some adb or fastboot commands (push, reboot commands for example), but it's impossible to write any img on it.
If you want to change your radio, I think you must downgrade your Hboot by executing an older RUU (2.08** or 1.73**) and then, you will be back on an Hboot "unlockable" (Hboot 1.18** or less).
I didn't try to change radio, 'cause this one, RADIO-11.19.3504.29_2, is the last one and it seems Ok for my usage on ICS 4.3.1.
Things seem to have changed a bit since the days I was unlocking my DHD...
First things first: how do I make sure hboot (thanks - this was my initial question, I didn't know what LOCKED referred to!) is locked? Because, as I quoted,it seems that when you update the fw it says 'locked' even though it's unlocked.
But, if I downgrade through a RUU, if I update the fw again in order to flash Mike's ROM, I guess the same will happen?
Thanks for your reply!
Yep, if after downgrading by RUU, you flash Mike's firmware, you will have again the problem, because this RADIO-11.19.3504.29_2 is included in the FW.
To confirm your Hboot is really locked (for writing), you can try to flash any radio.img, with fastboot command.
You will see in your terminal, the img is send but it stays impossible to be written.
Interesting. So, basically, you need to flash the radio before updating the fw and before flashing the ROM... ok, staying with the one I have right now
Thanks again!
NO, it's useless to flash any radio before, 'cause when you'll update with Mike's FW, you'll get this Radio version 11.19.3504.29_2 again !!!....
So the simplest way is to keep this Radio version !!!
IMO, it is a good radio, but if you want to flash any GB custom rom, you will need the RiL files corresponding.
you will find it HERE.
Heh, that's what I thought, and it seemed weird to me... then how come Mike recommends another radio though (the one I tried to flash)?
Anyhow, thanks for the input, really appreciate it!
For his ICS based ROMs (ARHD v6.0.x), Mike recommends "11.65.3504.00U_11.19.3504.29_2 radio".
wideopen4ever said:
For his ICS based ROMs (ARHD v6.0.x), Mike recommends "11.65.3504.00U_11.19.3504.29_2 radio".
Click to expand...
Click to collapse
Yeah, but flashing his ICS/3.5 ROM (6.02) apparently gave me 11.19.3504.29_2?
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Skipjacks said:
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Click to expand...
Click to collapse
No. I tried doing it with the Revolutionary tool, which supposedly uses the same method and it told me it does not support this version...
Not sure if it will work with HTC's tool directly, though.
Skipjacks said:
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Click to expand...
Click to collapse
When I upgraded to hboot 1.20 used htcdev to unlocked it. Then upgraded to hboot 1.23 and it remained unlocked
Sent from my Kindle Fire using Tapatalk
krakout said:
Yeah, but flashing his ICS/3.5 ROM (6.02) apparently gave me 11.19.3504.29_2?
Click to expand...
Click to collapse
yes that is the newest radio for ICS, when you flashed the ICS UPdate it gave you everything ICS from hboot to radio, now all you had to do is find and 4.0.3 rom and flash and everything would match the ril/radio and hboot needed to keep it stable
My Hox has been running CleanRom 5.1 for sometime now, but I wanted to make the jump to a JB rom. I'd been having trouble in the past where I'll flash a JB rom (doing all the other stuff with it too), and it will start up fine. However during a reboot, it will get stuck in a boot loop despite the correct boot.img being flashed. After some searching of the forums and the web, I figured it must be my hboot - I'm at 1.14.0002.
How does one go about upgrading / updating the hboot to 1.31 / 1.39, which from what I've read seems to be what I need to get a JB rom to work properly? I've seen bits and pieces saying to download a RUU or nandroid back up, but my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?
uncledoobie said:
My Hox has been running CleanRom 5.1 for sometime now, but I wanted to make the jump to a JB rom. I'd been having trouble in the past where I'll flash a JB rom (doing all the other stuff with it too), and it will start up fine. However during a reboot, it will get stuck in a boot loop despite the correct boot.img being flashed. After some searching of the forums and the web, I figured it must be my hboot - I'm at 1.14.0002.
How does one go about upgrading / updating the hboot to 1.31 / 1.39, which from what I've read seems to be what I need to get a JB rom to work properly? I've seen bits and pieces saying to download a RUU or nandroid back up, but my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?
Click to expand...
Click to collapse
if you have hboot 1.14, you can downgrade via JET. This will require a computer running linux and involves intentionally bricking and then debricking your device. This method is not everyone's cup of tea.
If you are flashing the boot.img and getting bootloops, I wouldn't think downgrading your hboot would help. Did you remember to wipe data from TWRP (and the cache/dalvik of course)?
codeprimate said:
if you have hboot 1.14, you can downgrade via JET. This will require a computer running linux and involves intentionally bricking and then debricking your device. This method is not everyone's cup of tea.
If you are flashing the boot.img and getting bootloops, I wouldn't think downgrading your hboot would help. Did you remember to wipe data from TWRP (and the cache/dalvik of course)?
Click to expand...
Click to collapse
Yep, do the wipes of everything, plus factory reset. I flash the boot.img properly from each rom every time. Is going to 1.31/1.39 a downgrade from 1.14? or an upgrade?
uncledoobie said:
Yep, do the wipes of everything, plus factory reset. I flash the boot.img properly from each rom every time. Is going to 1.31/1.39 a downgrade from 1.14? or an upgrade?
Click to expand...
Click to collapse
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.
codeprimate said:
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.
Click to expand...
Click to collapse
holy ****e, i think that's it. i've been doing just the latter. i forgot the "flash".
i will try this and report back.
Update: Success!
uncledoobie said:
holy ****e, i think that's it. i've been doing just the latter. i forgot the "flash".
i will try this and report back.
Update: Success!
Click to expand...
Click to collapse
LOL, glad to hear you have it sussed.
uncledoobie said:
my CID is 1111111 (The generic one) and I can't find a RUU to match it. Is that what I even need to do to update the hboot?
Click to expand...
Click to collapse
That CID is not "generic", its called SuperCID, which basically bypasses all CID check.
The problem is version check, in which the RUU will not run if it detects a newer (higher number) hboot version already on the device. So that is why downgrading by "unofficial" means is the only way to move down to a previous (lower number) hboot version.
redpoint73 said:
That CID is not "generic", its called SuperCID, which basically bypasses all CID check.
The problem is version check, in which the RUU will not run if it detects a newer (higher number) hboot version already on the device. So that is why downgrading by "unofficial" means is the only way to move down to a previous (lower number) hboot version.
Click to expand...
Click to collapse
ah ok good to know.
so only downside of 1.14 comparing to 1.09 is that on 1.14 you have to flash kernels/radios manually via fastboot and 1.09 doesn't require that procedure?
codeprimate said:
From 1.14 to 1.39 would technically be an upgrade, but most people want to downgrade their hboot to 1.09 (as 1.09 allows flashing of kernels/radios).
Just quickly, when you are flashing the boot.img, are you writing
"fastboot flash boot boot.img" this will flash the kernel, so it persists it through boot.
or
"fastboot boot boot.img" this will load the kernel at startup, but will not persist it through a reboot.
Click to expand...
Click to collapse
For1n said:
so only downside of 1.14 comparing to 1.09 is that on 1.14 you have to flash kernels/radios manually via fastboot and 1.09 doesn't require that procedure?
Click to expand...
Click to collapse
I don't think the device firmware was changed from 1.09 to 1.14 (as it was from 1.14 to 2.14), so I believe that is correct. I may be wrong, there may have been firmware upgrades, but they don't seem to be as drastic as the 2.14 update (which changed the touchscreen firmware to the point that old kernels had no touchscreen functionality).
I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!
exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!
Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes
exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor. Currently service provider is Koodo - a division of Telus (in Canada).
CID: ROGER001
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
arjundas86 said:
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor.
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
Click to expand...
Click to collapse
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
LS.xD said:
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
Click to expand...
Click to collapse
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
arjundas86 said:
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
Click to expand...
Click to collapse
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
LS.xD said:
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
Click to expand...
Click to collapse
Thanks for the toolkit.
cid: ROGER001
Btw, what's the purpose of going SuperCID?
Also, I don't want to install lower hboot. I am on hboot 1.08 and I think I need to install hboot 2.15. Right?
I guess S-OFF isn't absolutely necessary, but would be nice to have. Would you recommend using the S-OFF command from the toolkit you linked?
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
With superCID you can switch to other CIDs e.g. for unbranding your device Also it's needed for "Facepalm S-OFF" (Was the only working method for me)
Sent from my loved HTC One S using (most time buggy) Tapatalk
LS.xD said:
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
arjundas86 said:
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
Click to expand...
Click to collapse
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
LS.xD said:
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
Click to expand...
Click to collapse
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
arjundas86 said:
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
Click to expand...
Click to collapse
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
LS.xD said:
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
Click to expand...
Click to collapse
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
arjundas86 said:
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
Click to expand...
Click to collapse
To run a RUU NOT MATCHING your stock CID you need S-OFF // SuperCID. You cant install TMobile RUU at first :/
I would act like this:
Run latest Rogers RUU --> READ FACEPALM GUIDE CAREFULLY. There is how to gain SuperCID and then S-OFF. Once done you can change CID to whatever you want and run a (unbranded) RUU with HBoot 2.15.
But that is just what i thought about it. I suggest to let someone else CONFIRM the way suggested by me first.
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
@Rapier
thank you for the provided help as usual
Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
LS.xD said:
...Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
Click to expand...
Click to collapse
For you? NO. You're better than me
The story is like this. I bought the phone in 2012. At that time, the highest hboot was 1.14 I believe (don't remember exactly) and there was no S-Off method available (they appeared later). There was something else tho. The lower hboots (1.09 and lower) permitted to write in the kernel partition or radio partition like an S-Off device. HTC then covered this in the higher hboots. So even if there was no S-Off method, there was a downgrade method that was used to downgrade the hboot from whatever you had to 1.09 or below. I downgraded mine to 1.06...don't ask why I didn't choose 1.09, I thought that was the RUU I considered to be fine for me at that time.
Now being on hboot 1.06 I can do anything except I cannot flash firmwares directly. So I cannot flash a new hboot with red letters removed for example. But I don't care about this...I can flash radios or kernels or splash screens like any S-Off user. The procedure for getting latest firmware and S-Off seems a little bit risky and I've read about alot of issues or problems from people who failed or tried countless times to reach that. So I've asked myself why should I do that if I don't need it?
Then it came the rumor and there were some brick cases of devices that were having some Android 4.3 ROMs and were not on latest firmware (in the meantime 2.13 and 2.15 hboots arise and also the S-Off method). It proved to be not the firmware fault after all. But CM team has included a check in the updater script of the ROM ZIP, to validate if the hboot was 2.13 or 2.15...if not, the flash won't happen. It's a simple assert command present there at the beginning of the script that do the check. As CM team was the pioneer in having the newest Android version ROMs available, everybody based initially their ROMs/builds on CM...so the check in the script was automatically carried over to all the ROMs out there. And it's still here.
As I've tested and I could run fine those ROM's (by removing the check before flash), I noticed that this requirement does not apply to everyone. Some could run fine the ROMs even if they're not on the "latest" firmware.
So that's why I am on 1.06...cause I don't know why should I go through some risky procedures when I don't need to.
Rapier said:
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
Click to expand...
Click to collapse
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
Rapier said:
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
Click to expand...
Click to collapse
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
LS.xD said:
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
Just IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
Click to expand...
Click to collapse
Yes, you're right. That's what I meant. I will delete the updater-script lines that Rapier mentioned before trying to install CM11.
If it doesn't work, at least I can restore to my backup, without risk of bricking.
Then I can try the hboot update and s-off if required.
Thanks.
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444....
Click to expand...
Click to collapse
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't want
arjundas86 said:
...I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
It's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
BUT, if you're NOT going to upgrade your firmware and you'll be lucky to have the ROM working, you won't need to S-Off since your current hboot is lower than 1.09 and allows you to flash radios and kernels directly from recovery.
And at this point, as you said, it worth a try like you are now and only if it's not working like this you should upgrade and do S-Off. I guess is much easier and less risky to remove 4 lines from that script and flash the ROM to see if it's working, than to go through the firmware upgrade & S-Off procedures
Rapier said:
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't wantIt's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
Click to expand...
Click to collapse
Hey Rapier,
I'm having trouble doing getting the zip signed.
I tried the zip signer you had in your guide, as well as a bunch of other zip signing programs, but none of them seem to do the job. I keep getting Error: Status 7.
Not getting bootloops or anything like that, so I was able to restore to my backup. No harm done.