Database Info

Difference between RUU & OTA

Hi Friends,
Have a few questions pls, Thanks in advance.
1 What is the difference between official OTA update & RUU update?
2 Is it required to have a rooted phone to make RUU?
3 In case a phone is rooted already, will it be able to be updated by official RUU?
4 Are there any diff betwee n OTA & RUU in terms of settings, regional configuration, stability.. .etc?
Sent from my HTC Desire S using xda app-developers app

1. OTA is incremental and doesn't erase anything. RUU is complete and erases everything.
2. No.
3. Yes.
4. Completely different things, since OTA is incremental and upgrades your existing ROM. Can't compare apples to oranges.

Thanks, but what is the major disadvantage of RUU, I understand it will erase all my data & will have to restore data & applications, is there anything else that make it a second choice?
Sent from my HTC Desire S using xda app-developers app

Why is it second choice? It's not about choice, it's about picking the right tool for the job. When you want to get OS upgrade, OTA is better - because you get the upgrade without extra pain (without starting everything from scratch). When you suspect your phone is misbehaving, or for some other reason want to restore your phone to the stock state - RUU is the way to go. They're not "better" than each other, they're different, for different occasions.

And im new to this stuff and if you can say or give the link to the thread where i can find what ota is it would be perfect, i searched xda but all i found was roms with ota
Sent from my GT-I9300 using xda premium

OTA is "Over-The-Air", so unless it arrives to your phone automatically, as it's supposed to - I believe people aren't keeping OTAs anymore. Once, when Nexus One was still considered a new phone, they did - but not anymore, for a long time now. In the forum you'll only be able to find RUUs, I believe.

In case a phone is rooted already, will it be able to be updated by official OTA?
It seems that OTA does not work for me anymore after I S-OFF'd and rooted.
I know also flashed a new radio. Does that affect the possibility of OTA in any way?
Cheers.

OTA doesn't care about rooting or S-OFFing. If there is OTA standing - it'll be delivered to the phone. Installing it might be problematic (can't be installed by custom recovery without disabling signature check), but the delivery WILL happen. S-OFF doesn't affect OTA in any way. If you don't get OTA - that's because there is no OTA, the servers are stopped.

I see. Signature check be the problem. Any solution for that?

This is only relevant if you have stock rooted ROM and custom recovery.
In that case, you need to locate the ZIP file downloaded by system update, and install it manually in recovery, skipping signature detection.

After reading...
nodeffect said:
5. I've just received this system update OTA - 1.47.61.1 or later. If I install it, will I loose my S-OFF and root?
- Yes, you will lose both S-OFF and root once you update because it will update the hboot to 0.98.0002. However, you can try following this guide http://forum.xda-developers.com/showpost.php?p=16110608&postcount=5 to update the OTA but not the hboot. Check this one out also http://forum.xda-developers.com/showthread.php?t=1190992 and http://forum.xda-developers.com/showthread.php?t=1194488 to S-OFF and root if you have updated the OTA.
Click to expand...
Click to collapse
I decided that it is probably not a good idea to go down to OTA route.

Hi,
I had the stock rom RUU​_Saga​_S_HTC​_ARA​_2.14​.415​.3_Radio​_20.4801​.30.0822U​ and I wanted to install the European RUU​_Saga​_S_HTC​_Europe​_2.10​.401​.9_Radio​_20.4801​.30.0822U​. But in the install process there was an 155 error. I tried some times but the same result. I read here a lot and finally I unlocked the phone HTCDEV as my hboot is 2.00.0002 and flash 4EXT_Recovery_v2.2.7_RC5 and ICE_DS_4.4 rom.
I experience some problem with this rom, so is it possible to install the european ruu of GB?

Yes, if you use goldcard or if you're SuperCID (which can only happen on this phone if you unlock it with XTC-Clip).
If you didn't understand something from the above - Google it.

Jack_R1 said:
Yes, if you use goldcard or if you're SuperCID (which can only happen on this phone if you unlock it with XTC-Clip).
If you didn't understand something from the above - Google it.
Click to expand...
Click to collapse
I know the words goldcard and supercid. I saw few threads name them . Thanks for the reply I will try the goldcard.

So i made my sd card Goldcard. what's next, in order to install stock european ruu GB? some guidance maybe?

Relock your bootloader and immediately install (without exiting FASTBOOT USB mode).

Jack_R1 said:
Relock your bootloader and immediately install (without exiting FASTBOOT USB mode).
Click to expand...
Click to collapse
I relocked the phone and when i try to install the european ruu it gives me the error 140, and stuck in bootloader. Then I install the ARA ruu and all gone well the phone runs well.
The problem though exists. I want the european ruu and not the ara ruu. Any ideas?

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

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.

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good:

Several questions to understand hboot update on HOX evita

So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.

zain910128 said:
So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.
Click to expand...
Click to collapse
In response to your first question, SuperCID is a generic CID that unlocks your device from being identified and restricted to a certain carrier or region.
You don't need to worry about rooting methods for any specific version, you already have an unlocked bootloader and s-off, and your phone will stay like that unless you deliberately change it.
You don't want to update just the hboot. The ROMs look for a certain hboot version to be present during installation, but this is actually to verify that you have the right firmware installed, so you need to update your firmware, not just the hboot.
Luckily you don't need to mess around with any RUU at all. There's a much better and easier solution to your problem and that's simply to flash the 2.15 firmware package. There's a download and full instructions in my guide thread, you'll find the link in my signature.
Transmitted via Bacon

I have hboot 1.14 and built 2.20
You've mentioned installing firmware 2.15 package. Isnt that a downgrade ?
Also, can you explain the relation between hboot-firmware-built-RUU ?
timmaaa said:
In response to your first question, SuperCID is a generic CID that unlocks your device from being identified and restricted to a certain carrier or region.
You don't need to worry about rooting methods for any specific version, you already have an unlocked bootloader and s-off, and your phone will stay like that unless you deliberately change it.
You don't want to update just the hboot. The ROMs look for a certain hboot version to be present during installation, but this is actually to verify that you have the right firmware installed, so you need to update your firmware, not just the hboot.
Luckily you don't need to mess around with any RUU at all. There's a much better and easier solution to your problem and that's simply to flash the 2.15 firmware package. There's a download and full instructions in my guide thread, you'll find the link in my signature.
Transmitted via Bacon
Click to expand...
Click to collapse

zain910128 said:
I have hboot 1.14 and built 2.20
You've mentioned installing firmware 2.15 package. Isnt that a downgrade ?
Also, can you explain the relation between hboot-firmware-built-RUU ?
Click to expand...
Click to collapse
No it isn't a downgrade, the 2.15 refers to the hboot that's contained in the firmware package. Here's a brief explanation:
RUU: contains the ROM, recovery, firmware. An automated process which installs all of these items.
Firmware: contains the hboot, modules for Wi-Fi, media, etc.
ROM: the operating system (this is what is referred to by the build number).
Trust me, I'm very experienced with this device, all you need to do is what I outlined in my initial reply.

1095
timmaaa said:
No it isn't a downgrade, the 2.15 refers to the hboot that's contained in the firmware package. Here's a brief explanation:
RUU: contains the ROM, recovery, firmware. An automated process which installs all of these items.
Firmware: contains the hboot, modules for Wi-Fi, media, etc.
ROM: the operating system (this is what is referred to by the build number).
Trust me, I'm very experienced with this device, all you need to do is what I outlined in my initial reply.
Click to expand...
Click to collapse
Thanks a bunch !
Successfully running CM11.
A couple of more things id like your thoughts on:
1. Can you tell me how i can get rid of the splash screen message ?
Or is it possible to use my own splash screen ?
2. When i go to settings to customise slider lock shortcuts, it is pre set to unlock on right and various other shortcuts on the other 4 slots. I wanted to have unlock on top and the other shortcuts on either side. However, im unable to edit the right side shortcut.

zain910128 said:
Thanks a bunch !
Successfully running CM11.
A couple of more things id like your thoughts on:
1. Can you tell me how i can get rid of the splash screen message ?
Or is it possible to use my own splash screen ?
2. When i go to settings to customise slider lock shortcuts, it is pre set to unlock on right and various other shortcuts on the other 4 slots. I wanted to have unlock on top and the other shortcuts on either side. However, im unable to edit the right side shortcut.
Click to expand...
Click to collapse
Do you mean the red text? You can flash a modified hboot but they can cause problems, my advice is just deal with the text. You can only have the unlock target on the right, you can't modify that.
Transmitted via Bacon

How to rollback from Oreo to 7.1?

Hello, I just installed Oreo but don't like it and am looking to rollback to the most recent Nougat update on my U11. I have not flashed an Android device before. I have looked at these guides:
https://forum.xda-developers.com/u11/how-to/guide-htc-u11-how-to-return-to-stock-t3628452
https://forum.xda-developers.com/showpost.php?p=72831916&postcount=3
Though I don't quite understand them. I have download the 1.27.401.11 firmware for EMEA from the spreadsheet (since my device was bought unlocked and I put a Three SIM in it), and also the adb installer. How do I go about using these to install the older firmware?

I believe the first step is going s- off then flashing the appropriate nougot ruu if available. Just my 2 cents hopefully others will chime in. Hth

You must flash ruu correct cid for comeback nougat.

newyesor said:
You must flash ruu correct cid for comeback nougat.
Click to expand...
Click to collapse
If you upgraded to Oreo via ota
I don't think you can go back to nougot without going s- off, at least not from what I read.

https://forum.xda-developers.com/u11/help/how-to-rollback-oreo-to-nougat-htc-u11-t3729046
I am sorry because i am answer not clearly.
I was s-off for change supercid for update oreo.
I was s-off again and flash ruu for rollback from oreo to nougat.

You can do it without S-Off. I did it last week... BUT, you must do it with same CID/MID for it to work.
The guide is located here.
https://translate.google.com/transl...pic=830013&view=findpost&p=68392379&sandbox=1
please be mindful that you will need to remove spaces for it to work... I think it should look like this from memory
Code:
adb shell "dd if=/dev/block/sde1 bs=1 skip=2208 count=16"
I also don't recommend it if you dont know what you are doing...

miffymiffy said:
You can do it without S-Off. I did it last week... BUT, you must do it with same CID/MID for it to work.
The guide is located here.
https://translate.google.com/transl...pic=830013&view=findpost&p=68392379&sandbox=1
please be mindful that you will need to remove spaces for it to work... I think it should look like this from memory
Code:
adb shell "dd if=/dev/block/sde1 bs=1 skip=2208 count=16"
I also don't recommend it if you dont know what you are doing...
Click to expand...
Click to collapse
I have a question. Can this be done with super cid? Or must the cid and mid match the ruu?

Okay so I found my MID (2PZC10000), do I need to unlock my bootloader before doing anything else?

hammered58 said:
I have a question. Can this be done with super cid? Or must the cid and mid match the ruu?
Click to expand...
Click to collapse
If you're supercid, you have s-off so you can do whatever you like... Read the other thread about downgrading.
Versicarius said:
Okay so I found my MID (2PZC10000), do I need to unlock my bootloader before doing anything else?
Click to expand...
Click to collapse
No idea,,, My bootloader is unlocked.

I have installed ADB and verified it works with 'adb devices'. How do I go about loading the .zip Nougat file to modify it in the command prompt? Also I assume the 'TWRP Flash' button on the TWRP app restarts the device into Download mode? Lastly, once the commands to modify the RUU have been executed, how do I actually install it to the U11?

Supercid is no longer valid. Your cid must match one in the list of cids that the firmware is compatible with or it won't flash.
If you are dirty flashing you can expect bricks. You are best going the s-off route rather than forcing the firmware on. At this moment in time the U11 is a very expensive paperweight.

shivadow said:
Supercid is no longer valid. Your cid must match one in the list of cids that the firmware is compatible with or it won't flash.
If you are dirty flashing you can expect bricks. You are best going the s-off route rather than forcing the firmware on. At this moment in time the U11 is a very expensive paperweight.
Click to expand...
Click to collapse
My CID and MID match the firmware from the spreadsheet so I should be fine, what is dirty flashing?