[GUIDE] Want to use AOSP-based ROMs but on hboot 2.14 and no working touchscreen? - AT&T, Rogers HTC One X, Telstra One XL

All credits belong to MirGantrophy (if you wanna donate)
Thanks!
--------------------------------
Requirements:
1. must be s-off (see link)
2. must install this hboot 1.09 from this guide
3. ICS RUU file (see this link). In my case, I downloaded the earliest version for the Telstra RUU so I'm sure it's ICS.
4. working adb/fastboot files (this one worked for me)
5. twrp recovery (link). you can use the recent cwm I suppose but I haven't tested that.
steps:
1. open a command prompt/terminal
2. follow the steps in requirement 2
3.. boot into android
4. adb shell
5.. su
6. dd if=/dev/block/mmcblk0p23 of=/sdcard/p23
7. get out of adb shell (run exit twice)
8. adb pull /sdcard/p23
9. make a copy of p23
10. open p23 in a hex editor
11. look for a sequence that that start with 3.17 (complete format is 3.17.xxx.x. x are numbers)
12. replace 3.17.xxx.x with 1.00.000.0 and save the changes to a new file. In my case I saved it as p23mod.
13. adb push /sdcard/p23mod
14. adb shell
15. su
16. dd if=/sdcard/p23mod of=/dev/block/mmcblk0p23
17. get out of adb shell
18. execute RUU as let it run its course. Took about 10 minutes in my case.
19. install your chosen recovery (boot into fastboot and then fastboot flash recovery my-recovery-here.img)
20. repeat step2 (only if you want to remove the red text in the startup screen)
Notes:
1. These are the exact steps I followed to get it working on my phone.
2. steps 1 to 17 might be optional but the RUU install checks for previous version and I'm not sure if it'll go through if it finds a higher version is installed already. You can obviously experiment on your own.
3. A nice surprise after reinstalling stock ROM via RUU is that the "Tampered" text was removed and never appeared again even after I flash TWRP.
GOOD LUCK!

mrjayviper said:
20. repeat step1 (only if you want to remove the red text in the startup screen)
Click to expand...
Click to collapse
Shouldn't this be repeat step 2 not step 1? Otherwise, this looks great. Thanks to you for writing this up and to Grim also.

this actually worked? this is pretty much the same as [INFO] Downgrading firmware i tried using the old guide to downgrade hboot 1.14 and it didn't work and it didn't work for many others.
also if you have s-off you can run any ruu you want the checks do not matter and because of s-off you do not get the "Tampered" flag again so if you were s-off when you did this then this does not work.

DvineLord said:
this actually worked? this is pretty much the same as [INFO] Downgrading firmware i tried using the old guide to downgrade hboot 1.14 and it didn't work and it didn't work for many others.
also if you have s-off you can run any ruu you want the checks do not matter and because of s-off you do not get the "Tampered" flag again so if you were s-off when you did this then this does not work.
Click to expand...
Click to collapse
This is for s-off users who took the ota firmware update. I didn't know ruu didn't care about firmware versions if s-off so I told him to downgrade the stuff and then run the RUU to give the old firmware for working touchscreen on aosp ROMs

Related

[MISC] Flashing ENG HBOOT | Rolling back to S-ON - The Noob Way

Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread and no single unified noob proof solution for flashing Revolutionary's S-Off 'ed+ Rooted Desire S all the way from HBOOT version 6.98.1xxx to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (read ROM Update Utility AKA the stock ROM installer) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again (though theres a link to youtube step-by-step video tutorial of how to do it in the update section below; Do NOT ignore the video's ending ) but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000).
For more updated info please refer to "UPDATE" section below:
UPDATE:
Regarding the "Returning to Stock/making your phone S-ON" issue:
ok..I have not tried this but this right here guides you of how to S-ON and return your phone to total* factory like condition by installing an RUU thereby removing just everything..revolutionary, CWM..u name it; just like a real stock phone
But pls note that using an RUU (read ROM Update Utility AKA the stock ROM installer) will erase all your data! as you are flashing a stock RUU
And for this you need to change your HBOOT to 6.98.2000 (PG8810000) (as in the video linked above) OR to 0.98.2000 (PG8810000); so thats one of the other advantages of my guide..
Hope this helps..
Also, a lot of good folks here have been asking/suggesting me over why this method..? and why not the "dd commands method" / adb command(s) method? (all manually )
ok here's my take on this
Click to expand...
Click to collapse
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
DesireFanatics for his step-by-step tutorial video here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.
MODS pls sticky this thread as newbie/newcomers really won't get it the first time they look at the [index] @ XDA
And this right here is the solution for Flashing their HBOOTs almost painlessly
Regards,
sky770
- Reserved for future use -
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
:|..*gulp*
ok..as am a newbie so I would be needing experts in here
btw..have you gone through the Index/threads? coz thats what i did
esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
You have the latest hboot. If you don't want to s-on and unroot your phone again there is no need for you to downgrade the hboot (afaik )
Edit: accidentally pressed thanks.. never mind
sky770 said:
Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread for flashing Revolutionary's S-Off 'ed+ Rooted Desire S to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (umm noob translation for this would be original stock ROM?) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000)
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.
Click to expand...
Click to collapse
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks
If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
How about other eng hboot?
Sent from my HTC Desire S using XDA
muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems
The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process
Thanks to the OP!
Just got a Desire S and so far done this little lot:
I've downgraded the ROM to 1.28 to get HBOOT 0.98
S-OFF'ed using Revolutionary.
Installed 4EXT Recovery 1.0.0.5 Touch RC3
Flashed VanillaICE ROM
and just followed this guide to get off the Revolutionary HBOOT and to the ENG HBOOT 0.98.2000.
And it worked flawlessly!
Thanks again!
EDIT: and somewhere in that lot I have also updated the radio to the latest one from the Radio thread!
htc-phones said:
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks
Click to expand...
Click to collapse
Hi,
The fastboot method gets bypassed if we try to flash it by directly picking up the *.zip file from SD Card's root (that good 'ol PG88IMG.zip method).
Using the above method (my method at post#1) we are just literally pushing it through fastboot>>adb>>phone to get it flashed.. no questions asked from phone's side
srry abt the newbie/layman terms answer but this is how it actually works
Also regarding, the "dd commands" are never meant to be used for "noobs" as they are quite dangerous...more..more dangerous than to use fastboot instead of directly using adb commands.
Just because dd commands method exist doesn't mean we should go to that extent to brick our phone (a noob can easily do that while sipping beer and typing some command as bik instead of blk)
And hence I would not like newbie(s) coming in here, bricking their phones and stalking me
UPDATE:
Excerpt taken from here
There are actually two levels of S-OFF. The Bootloader (HBoot) and the Radio. Getting S-Off on the HBoot gives us everything we need, but doesn't actually turn off the @secuflag which is set in the radio. What it is possible to do is to flash a HBoot that believes the Radio is set to S-OFF, as the HBoot is responsible for setting that flag. Once the HBoot on the phone is S-OFF, we can write to all the partitions and basically do whatever we want, but it is possible to go one step further. Flashing a radio that is S-OFF and actually setting the @secuflag off gives 100% total access to every part of the phone and it's software, as it becomes network unlocked allowing to you to use any SIM and also allows you to flash a ROM from any carrier (known as Super CID). It also makes it nigh on impossible to permanently loose root no matter what you flash. Once you have radio S-OFF, it makes it much easier to flash new HBoots and ROMs even if you flash something that is locked down tight.
Setting the Radio to S-Off is not necessary, and gaining S-OFF on the HBoot is more than most people will ever need. Radio S-Off is just the last step of the puzzle, but it is worth noting the only points you can permanently brick your phone is flashing a radio or a HBoot, if either of these go wrong you will end up with a shiny expensive paper weight so there is risk involved.
Click to expand...
Click to collapse
So pls pls suggest newbie(s) to flash with caution :|
muselmann88 said:
If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!
Click to expand...
Click to collapse
As it looks to me, if you're running hboot-6.98.1002 already then you must have used revolutionary's tool to S-off your phone.
Therefore you are eligible to use the above guide to re-flash your hboot.
Infact you're having the same hboot version as I had after using revolutionary.
changing your hboot version to 0.98.2000 (PGI880000) will make sure that you can flash any RUU (official stock ROM) so that you could be s-off again
Though I am still getting working on it to have a simple 1-click solution for this too for ya noobs
Also, make sure you're rooted (though I would like some expert to comment on this; but AFAIK root is needed to flash the *.img file over fastboot; just search around forum as to be sure.)
Do it now! and you won't regret..
Regards,
sky770
marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I would not really recommend using "dd commands" please see my reply over here
Regards,
sky770
muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
Sense 4 requires you to have umm... HBOOT version 2.xxx and above? (experts?) anyways.. that cannot be categorized as "problem" its just another "prerequisite" for sense 4 based ROMs though am not sure if its an "official prerequisite" or a non official non
Also, please read my post abt dd commands here.
Regards,
sky770
Dreamtheater2003 said:
How about other eng hboot?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Can take some time here to try some custom(s) ROMs first
Anyways, now that am here on XDA lets get started..
Regards,
sky770
htc-phones said:
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems
Click to expand...
Click to collapse
any ROM?
you sure about RUU (stocks) ??
if yes then plz forward tht PM to me too pls
Regards,
sky770
amidabuddha said:
The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process
Click to expand...
Click to collapse
aha! Right on point
And thats one more reason I won't really..really recommend using dd commands to a noob/newcomers just for flashing from 6.98.10xx -over to-0.98.2000 (PGI880000).
Regards,
sky770

[Q] RUU Installation

Ok, so I can't find a compatible boot.img to flash via cmd in bootloader to restore my 2.3.5 original nandroid backup.
All I want to do is return to stock rom after which I will attempt downgrade and s-off because I'm tired of the restrictions and I couldn't care a less about my warranty etc.. I'll use either zerg rush or taco root depending on my software version which atm I have no idea of obviously..so I know to downgrade it's a different story..
Currently S-ON, HBOOT 2.00.0002 HTC UNLOCKED, REAPER 3.0(CM7) ROM Installed. 4EXT Recovery.
I have downloaded a compatible RUU which in my case is
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
Checked by running fastboot getvar main-version: C:\WINDOWS\system32>fastboot getvar version-main
version-main: 2.15.1113.2 (and) CID HTC__058
So that is equal to what I have now on the phone (I also have another older RUU with hboot 98.00.000 for use with S-OFF'ing later...)
So becaue the RUU version is the same as my original can I just run the INSTALLER and let it do it's thing? And do I need to relock my bootloader first?
I have been reading and searching guides for hours, but nothing is clear to me, my wife is at my throat as well saying I've married my PC *you've probably heard it*
Has anyone done this before?
To save you some unnecessary steps:
1) Change the misc_version (look it up, it's a step in downgrading guide) under your current ROM (I assume you're rooted).
2) Lock the bootloader.
3) Flash the older (0.98 bootloader) RUU.
The correct answer for Jack_R1.
[GUIDE] Official HBOOT 2.00.0002 Downgrade to OLD HBOOT thanks Skanob
Some extra optimizations on the guide that bring it to my short version:
1. If you're using the correct RUU for your region - you can skip GoldCard step.
3,4. You don't have to flash stock rooted ROM if you know that you can reboot to bootloader and run the RUU while in fastboot mode. Your phone might not load the OS after locking the bootloader on non-stock firmware, but it won't matter, since all you need is fastboot.
If you're not familiar enough with what things do - follow the guide exactly, don't take shortcuts.
Now I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 10 2011, 14:58:38
I still didn't understand how things worked and was up another 4 hours mucking around, in the end after succeeding, I can't believe how easy it was.
I never even knew what zergrush and tacoroot were for exactly or which misc version number i should use.
In the end I went back to stock rom, unlocked again using my original token, flashed recovery and then Superuser. After that I didn't need zergrush etc to gain temp root(obviously), just changed misc version, rebooted, revolutionary to s-off and 'Bob's your Uncle'. Now I guess I should learn about the things I can do with s-off...(apart from not needing to fastboot flash boot.img every rom change)
I will elaborate on the things that confused me for others later, but right now, I'm off to work.
Thanks again Jack,
Now you might discover that unless you made some steps you didn't list, S-OFF won't work for you, and you'll still have to flash boot.img manually. If you didn't relock the bootloader and flash the RUU, that is. But I assume you did, and just skipped it on the list of things.
Zergrush or tacoroot are means to get temporary root - which is no good, since it doesn't stick after reboot, but it allows you this one time to change misc_version to allow downgrade. And any misc_version would do, as long as it's below the one you're flashing for downgrade. On MT4G, we usually set it for 1.00.000, that way you can't go wrong.
Glad you made it.
Embarrassingly, I do have problems still. After relocking and flashing the older RUU(HBOOT 0.98.000) successfully, I used Revolutionary to S-OFF. During the process the software asked me if i wanted to install clockwork Recovery, to which I answered 'no'. After that I tried to manually flash 'ext recovery' which I had before, so then I can flash 'Superuser.zip', but get an error message, I'm not sure why?
So I don't have root.
I'm at work now, when I get home all I can try is flash clockwork and see if that works.
*EDIT* Successfully flashed recovery-clockwork-5.0.2.0-saga.img and then superuser, perhaps the version of 4EXT recovery wasn't compatible or something...!? I can't be sure.
Restored Nandroid of previous Reaper 3.0, all is well.
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
kyeeliu said:
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
Click to expand...
Click to collapse
Thanks for the lead kyeeliu, but I have little idea what that can provide, I heard upgrading HBOOT can S-ON your phone again as well. Although I'll have a read and try to garner what I can...
My phone upgraded, but the S-OFF.
Because our mobile phone software unlock.If you use the official RUU upgrade will become S-ON.
We use modified HBOOT, there is no problem.
I currently use, and indeed as vampire36 said, the flash ROM no problem.
My Experience with S-OFF
First of all I want to thank Jack_R1 for his input and wisdom, even though I didn't really understand some things he mentioned, it all made sense in the end) as well as kyeeliu for his comments.
At first I didn't really trust many guides enough to follow possibly bricking my phone. I see too many people[READ:Beginners] with opinions and problems because some guides are not explained from a beginner point of view often offering instructions but little in the way of explanations for steps...., but in all fairness, this is also due to inexperience, or the users own failure to to make sure they followed everything correctly. Such is life...All in all happy to HAVE Guides, we can't really complain, just feel lucky ppl take time to write. And writing in DEPTH is bloody tiring when you hate typing as I do...
I believe NOONE should be attempting, however, to mess with their phone's inner workings until they've tried their best to assimilate all the information they can[ie:SEARCH]. I know it's time consuming and frustrating sometimes, but that onus is on you when you chose to 'take the plunge' so to speak..
I read for so many hours, wading through a disorganised sea of excited opinions READ:misinformation, good advice and hidden gems, but I was unable to discern what was best simply because I only had opinions and a sense of logic to dissasemble everything. In the end I followed a guide HERE by Skanob, it worked A-OK!
So this this is my Story of how I S-OFFED my Phone. By NO means extraordinary, :laugh:
Desire S - S-ON - HBOOT 2.00.0002 - CM7 ROM[Reaper 3.0]
*Note: I nandroid restored my original rooted rom first*
First of all the RUU. Noobspeak: It's just a version of your phones operating system in installer format, just like Windows XP is different[read:updated] to Windows 7, so is 1 RUU from another. Some are branded (have the carrier's logo) some are not (unbranded) Mine in particular was unbranded.
First you need to find out YOUR phones RUU, so to do this reboot your phone into Bootloader - Fastboot and then open command prompt on your PC and navigate to where you have adb and fastboot files located (I have copies of these files in windows\system32\ folder. When there type C:\WINDOWS\system32>fastboot getvar all. In this list of information look for these:
INFOversion-main: '2.15.1113.2' (and) INFOcidnum: 'HTC__053'
version-main is your phones current operating system version CID is your particular phones region(eg: HTC__058 = Thailand)
So This was my phone's current RUU:
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
My current version has HBOOT 2.00.0002. I will need to downgrade this number to 98.00.000. I can do this by installing an older RUU that has HBOOT (98.00.000) I didn't know WHICH RUU that was so I just looked for an older RUU done by checking my current version_main '2.15.1113.2' and looking for something lower. I found: [RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I wasn't sure which HBOOT was inside (silly me) so i ran the installer just letting the first screen open up (which extracts all the files from the RUU to temp) and going NO further.. After that I went to 'Run' and typed in %temp% and looked for a recent folder with a long name which had the contens of the installer extracted. Amongst these files I found 'rom.zip' I opened it and inside could see the HBOOT file version 98.00.000_'other numbers'. This was my ticket :highfive: lol...
Now because my stock ROM was already rooted and I had previously flashed recovery all I needed to do was the -Modify the version of your phone- step in Skanob's Guide: (obviously I downloaded the attached misc_version file and as instructed created a new folder on C: called 'downsaga' and dropped misc_version inside)
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
This part of the code
Code:
./misc_version -s [COLOR="Blue"]1.27.405.6[/COLOR]
sets your phone to accept any RUU with a higher version than that number. I had no idea which number to put there exactly so I used 1.27.405.6 as well, noting it was lower than the RUU version I was going to install[1.35.1113.2] So it would be accepted.
Later Jack_R1 advised me to put 1.00.000 instead, and as he stated, "you can't go wrong". :good:
After setting the new version, I Re-locked my phone via command again using fastboot oem lock. I do not need root privileges anymore as I have already changed my misc_version [lower version] And the RUU installation needs phone to be relocked again before proceeding.
After that it's simply connect your phone to the PC and run the installer:
[RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I now had HBOOT 98.00.000. After that, a trip to http://revolutionary.io/ to S-OFF, and flash recovery file. If you choose during the S-OFF process to not install recovery you can do it manually afterwards as I did(I used recovery-clockwork-5.0.2.0-saga.img, because for some reason I got an error trying to flash 4EXT_Recovery_v2.2.7_RC5 which I previously had) Then I simply dropped Superuser-3.0.7-efghi-signed.zip on my SDCARD and installed via recovery, all done. Nandroid restore of my CM7, and that was it...
I remember many weeks ago just trying to achieve root was bewildering, trying superoneclick and 1 or 2 others methods that also failed me. Only to find all i had to do was flash a recovery file in fastboot, then install superuser. ... all the time I wasted...lolz.. thx to n0elite for that http://forum.xda-developers.com/showthread.php?t=1525100
On a side note: Please think again before reporting an error, and retrace your footsteps first. I have seen people reporting errors in forum such as: can't re-unlock my phone(yes, with the same Unlock_code.bin) simply because they were unwittingly in HBOOT instead of FASTBOOT, etc....
Now I'm well aware I could have done 'this or done 'that' etc differently and saved time etc..blah blah, and opions are welcome. I did not ,however, write this as a step-by-step Guide. Only as my personal experience, and yes, to many seasoned members minds I may have over explained, but this is because your so 733T and obviously I'm a slow learner perhaps, but I was mind-boggled so tried to write this from my own perspective as a 'virgin' flasher.
Peace!
twIIce
ok, THAT I can understand. Thanks a million!!!
yeeeeeeee, I've made it!!!
it was soooo simple! thank you mate!!!

[Resolved] Downgrade Hboot 2.xxxxx of a Branded Desire S

Pardon me if there is already a thread for this. However, I couldn't find a helpful one. Please let me know if there is one.
I bought an HTC Desire with CID VODAP001. I have boatloader that says "Relocked" and S-ON and hboot is 2.xxxxxxx and it is running ICS 4.0.4 at the moment
I want to downgrade my hboot to 0.98.xxxx to gain S-Off. However, I don't know how exactly should I do that to downgrade my branded DS. I have RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe with me. I also have extracted PG88IMG.Zip out of this RUU. I also know how to create a Goldcard.
However, I am unsure whether I should run RUU.exe (hboot 0.98.xxxx) directly or create a Goldcard and put that PG88IMG.Zip in SD Card (remember my phone is S-ON) and boot into bootloader or would either of these methods will be wrong?
Please let me know. Help would much appreciated :good:
Cheers
1) Unlock again (via HtcDev)
2) Flash a Custom recovery (like 4EXT to have a root adb shell)
3) Reboot to recovery, connect to PC and use the misc_version (you can find it in any of the downgrade guides in the Index thread) Change the version to something below 1.32.161.1. For example 1.27.161.1
4) Reboot to bootloader and relock it (fastboot oem lock)
5) Run the RUU.exe while connected to the PC (you can do it the bootloader, just be sure that there is FASTBOOT USB written on the screen of the device)
6) When flashing is done wait for the OS to load, go to the Developer Settings and enable ADB Debugging. Disable the fastboot option in the Power Settings
7) Use Revolutionary
8) Download and install the 4EXT Recovery updater app. Use it to flash the latest touch version of the Recovery (trust me on this). You will need root for this, so do it after you flash a custom ROM
9) Do whatever you want with your freshly S-OFF'ed device
Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
amidabuddha said:
1) Unlock again (via HtcDev)
2) Flash a Custom recovery (like 4EXT to have a root adb shell)
3) Reboot to recovery, connect to PC and use the misc_version (you can find it in any of the downgrade guides in the Index thread) Change the version to something below 1.32.161.1. For example 1.27.161.1
4) Reboot to bootloader and relock it (fastboot oem lock)
5) Run the RUU.exe while connected to the PC (you can do it the bootloader, just be sure that there is FASTBOOT USB written on the screen of the device)
6) When flashing is done wait for the OS to load, go to the Developer Settings and enable ADB Debugging. Disable the fastboot option in the Power Settings
7) Use Revolutionary
8) Download and install the 4EXT Recovery updater app. Use it to flash the latest touch version of the Recovery (trust me on this). You will need root for this, so do it after you flash a custom ROM
9) Do whatever you want with your freshly S-OFF'ed device
Click to expand...
Click to collapse
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
And step# 8) Download and install the 4EXT Recovery updater app from market?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
farazhassankhan said:
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
Click to expand...
Click to collapse
The RUU will fail to flash on everything with higher that its own version. Which in your case is 1.32.161.1. So we have to trick the RUU to think that it is flashed over software with the same or lower version. This is achieved by the misc_version binary.
But in your case you are running the ICS software which has a version of 14.01.401.2 (11 symbols). The misc_version binary will replace only the symbols that you give it so for 1.32.161.1 it will replace 10 symbols. So the following will happen:
14.01.401.2
1.32.161.1
-------------
1.32.161.12 -> the resulting version will be higher! And the RUU will refuse to flash
Setting a lower number will produce a lower version (as per the example above it will be 1.27.161.12), the RUU will detect a lower version, although with more symbols and will flash successfully.
farazhassankhan said:
And step# 8) Download and install the 4EXT Recovery updater app from market?
Click to expand...
Click to collapse
http://4ext.net/ - it is at the top
Here is a direct link
farazhassankhan said:
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
And step# 8) Download and install the 4EXT Recovery updater app from market?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1318919 see step 4 or just reed the whole thread carefully
u can download the app from here
Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
amidabuddha said:
The RUU will fail to flash on everything with higher that its own version. Which in your case is 1.32.161.1. So we have to trick the RUU to think that it is flashed over software with the same or lower version. This is achieved by the misc_version binary.
But in your case you are running the ICS software which has a version of 14.01.401.2 (11 symbols). The misc_version binary will replace only the symbols that you give it so for 1.32.161.1 it will replace 10 symbols. So the following will happen:
14.01.401.2
1.32.161.1
-------------
1.32.161.12 -> the resulting version will be higher! And the RUU will refuse to flash
Setting a lower number will produce a lower version (as per the example above it will be 1.27.161.12), the RUU will detect a lower version, although with more symbols and will flash successfully.
http://4ext.net/ - it is at the top
Here is a direct link
Click to expand...
Click to collapse
Let me say thanks to you two for helping me out. I am gona try it as soon as I reach back to my town as I am in highway righr now. But seriously thanks a million. I'll report back if I get atuck somewhere. Cheerals
glacier1122 said:
http://forum.xda-developers.com/showthread.php?t=1318919 see step 4 or just reed the whole thread carefully
u can download the app from here
Click to expand...
Click to collapse
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Guys this worked. However there is a bit of change in procedure. You have gota be booted while executing misc-ver commands instead of being in recovery.
Thanks any way guys
Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
farazhassankhan said:
Guys this worked. However there is a bit of change in precedure. You have gota be booted normally while executing misc-ver commance instead of being recovery.
Thanks any way guys
Click to expand...
Click to collapse
Can you mark thread title as solved
We are what we repeatedly do; excellence, then, is not an act but a habit.
—Aristotle
jugg1es said:
Can you mark thread title as solved
We are what we repeatedly do; excellence, then, is not an act but a habit.
—Aristotle
Click to expand...
Click to collapse
Done
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[GUIDE][TOOL]FUU/Firmware HTC One Mini

General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
Prerequisites:​All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).​
FUU How To​
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
ZIP Flash HowTo​
Step-By-Step:​1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.​
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)​
Update: added Firmware For Sense 5.5 4.3 FUU
Download
MD5: 4cc050c25d2006600dfdbcc186789ef0
This FUU is Stock. Contents: Firmware from vrvr And So You should be good to Go. This package does wipes SDcard.​
Update: added Modifyed Hbbot No Red Text FUU
Download
MD5: 3918b9ca578f6f117a96e39f14873cd2
This FUU is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does wipes SDcard.​
Update: added Firmware For 4.4 KitKat FUU
Download
MD5: 701f1b7c07356e3fd7aaacf2e777d666
This FUU is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom​
Fastboot ZIP Downloads​
Update: added Firmware For 4.4 KitKat
Download
MD5: a0a05707fdbbdc7b7b162a7f6d76c4c8
This package is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does Not wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom
Update: added Firmware For Sense 5.5 4.3
Download
MD5: 1f9f200cf468dc40ddd3c5415c639823
This package is stock. Contents: Firmware from vrvr And So You should be good to Go. This package does Not wipes SDcard.
Update: added Modifyed Hbbot No Red Text
Download
MD5: 2f5467f6fdcc854198a95d6ed7146c7f
This package is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does Not wipes SDcard.​Credits​Thank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
tr1gg3r84 - For Testing
vrvr For The OTA Witch I Modify Of off
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.​
XDA:DevDB Information
[GUIDE][TOOL]FUU/Firmware HTC One Mini, a Tool/Utility for the HTC One Mini
Contributors
Flashalot
Version Information
Status: Stable
Stable Release Date: 2014-02-23
Created 2014-02-23
Last Updated 2014-02-23
For me
Update for 4.4 Firmware has been released enjoy
Thanks for this I'll have a look
coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader
leungalv said:
coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader
Click to expand...
Click to collapse
Have you tried wiping cache and davik cache
Sent from a potato running Android
Flashalot said:
Have you tried wiping cache and davik cache
Sent from a potato running Android
Click to expand...
Click to collapse
Yup tried wiping cache & davik. Fixing the permissions. Nothing works. Just goes HTC -> black screen -> off -> HTC -> black screen -> off.
Re-flashing the 4.3 boot.img will get it to boot back into 4.3.
i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/
kabalah89 said:
i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/
Click to expand...
Click to collapse
Flash stock firmware and stock ROM
After if you want to go back to s-on run this command
fastboot oem writesecureflag 3
Please make sure you are in stock hboot if not you will be in a permanent brick
Sent from my SPH-L710 using Tapatalk
Hello,
I;ve tried this and got into a bootloop. i don't know what to do now?
The phone is ocked en not S-off
I know i must flash the RUU, but i cannot find a european RUU.
Please help?
A little confused
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!
PuffDaddy_d said:
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!
Click to expand...
Click to collapse
@PuffDaddy_d, can you help me:
1. what method did you use?
2. what firmware did you use to get hboot 2.21 to flash stock 4.4?
3. if you used the 1st method that wipe sdcard, how can you flash the Rom?
pls help, I really want to have stock KitKat on mine. thx.
S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
gramateas said:
S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
thx @gramateas. you helped me with sideload method, but I really need a clear answers (as help) of my other 2 questions.
You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app
Zoeriva said:
Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
whay hboot are you on?
I am on 2.21 hboot
Sent from my HTC One mini using xda app-developers app
gramateas said:
You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx
edimonoarfa said:
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx
Click to expand...
Click to collapse
Well you could have as long as your on stock hboot then your OK but if not and your on a modded hboot you could brick
Also I'm looking in to see why every one is getting bootloops on firmware and I will be makeing no red text soon for Kitkat hboot
Sent from my SPH-L710 using Tapatalk

[DISCUSSION][GUIDE][S4] Liberty MAX - Innovation is Here | Flashing Instructions

This is a general discussion thread for Liberty ROM
Please ask any question you may have and I'll try to answer it as best I can.
Somebody asked for instructions on how to install Liberty ROM and New Firmware so here they are:
Installation of leaked firmware (HBOOT 2.16) and Liberty ROM
WARNING - This WILL wipe your SD Card so back up your files before proceeding
Make sure HTC Sync is REMOVED and drivers are installed. Get drivers: Here
Charge your phone to AT LEAST 60% just in case
If you are S-OFF proceed to step 3, if not continue to step 2.
If your phone is from T-Mobile (US & Germany), Telus or Boost Mobile use Moonshine S-OFF
If you have the international model use: Facepalm S-OFF, Firewater S-OFF or Rumrunner S-OFF (Rumrunner is the easiest in my opinion)
Note that people with the T-Mobile, Telus or BM model CAN use Facepalm, Firewater and Rumrunner as well but international users CANNOT use Moonshine
Now use one of these methods to S-OFF (You cannot proceed if you are S-ON)
Now download the new firmware: Here
Extract the file to a convenient location (Like Desktop)
Open the Install Package folder, press the Shift key, Right-Click while holding Shift and select Open Command Window Here
If your phone is on type:
Code:
adb reboot oem-78
and hit enter
If you are in the bootloader, select Fastboot and type:
Code:
fastboot oem rebootRUU
and hit enter
Now type:
Code:
fastboot flash zip firmware.zip
and hit enter
You should get a message like this: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)". Do not panic just type the command above again.
The green bar on the screen should stop at about 80-90% but do not worry, this is normal.
Now to flash the required recovery type this:
Code:
fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.zip
and hit enter.
Now reboot into the bootloader by typing:
Code:
fastboot reboot-bootloader
and hit enter.
Once in the bootloader select Recovery
When you are in recovery go to Advanced then ADB Sideload
Now you download the ROM: Here. (Latest release is V3)
Now place LIBERTY-S4-Vx.zip into the Install Package folder (The x represents version number, e.g V4
Now open a new command window by holding Shift and Right-Click at the same time and selecting Open Command Window Here
Next you must type:
Code:
adb sideload LIBERTY-S4-V3.zip
and hit enter.
Make sure the screen is on when the sideload is almost 100% complete as TWRP freezes for some reason.
Now follow the instructions in the installer, make sure you select Wipe Data during installation and Reboot when the installation process is finished.
Finished
Alright, I'll try it again here:
Does this ROM enable Bluetooth 4.0 (LE) on the One S?
floppes said:
Alright, I'll try it again here:
Does this ROM enable Bluetooth 4.0 (LE) on the One S?
Click to expand...
Click to collapse
yes it does
Could you maybe post more detailed installation instructions? Do we have to be S-OFF? Should we full wipe before installing?
v3 isnt boot ..
im in hboot 2.16 and soff.
I flash boot_2.16.img and the boot file of v2 again in fastboot and nothing changed
but in v2 it boot like a charm
help
mizutany1996 said:
v3 isnt boot ..
im in hboot 2.16 and soff.
I flash boot_2.16.img and the boot file of v2 again in fastboot and nothing changed
but in v2 it boot like a charm
help
Click to expand...
Click to collapse
Try re downloading the rom
Buembel said:
Could you maybe post more detailed installation instructions? Do we have to be S-OFF? Should we full wipe before installing?
Click to expand...
Click to collapse
hboot 2.16 and liberty rom instructions posted
What are the advantages of sense 5.5 coming from Maximus hd?
Sent from my HTC One S using xda app-developers app
Jeeza said:
What are the advantages of sense 5.5 coming from Maximus hd?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You can change Blinkfeed country location now and possible power drain fixes.
TheEndHK said:
You can change Blinkfeed country location now and possible power drain fixes.
Click to expand...
Click to collapse
What do you mean with "possible"?
Jeeza said:
What do you mean with "possible"?
Click to expand...
Click to collapse
He means that there could be battery drain fixes but he is not sure
i'm on MaximusHD 10.1
twrp 2.6.1.0
hboot 2.16
can i directly flash rom with full wipe ?
yatin kumar said:
i'm on MaximusHD 10.1
twrp 2.6.1.0
hboot 2.16
can i directly flash rom with full wipe ?
Click to expand...
Click to collapse
yes
Jeeza said:
What are the advantages of sense 5.5 coming from Maximus hd?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
If I remember correctly in sense 5.5 you can use blinkfeed to reed RSS news instead of only a few selected sources!!
But I haven't used the rom yet so I'm not sure, someone should confirm
What differences from a 4.2.2 rom? Better smoothness? Someone try it?
tommy92tc said:
What differences from a 4.2.2 rom? Better smoothness? Someone try it?
Click to expand...
Click to collapse
so far version 4 is slightly less laggier than v3 but not smooth enough yet and sense 5.5 has new blinkfeed features and some interface tweaks in various apps
Superuser
Hi folks
I used this to install Superuser on Liberty V-5 . Flashed thru recovery. It's for the HTC One M7 but seems to work on ours.
Thanks to @nkk71 for the link.
http://forum.xda-developers.com/showthread.php?t=2506954 Post No# 2
HTC One S
S4
S-off
2.16 Bootloader
TWRP
fgw3987 said:
Hi folks
I used this to install Superuser on Liberty V-5 . Flashed thru recovery. It's for the HTC One M7 but seems to work on ours.
Thanks to @nkk71 for the link.
http://forum.xda-developers.com/showthread.php?t=2506954 Post No# 2
HTC One S
S4
S-off
2.16 Bootloader
TWRP
Click to expand...
Click to collapse
Its for all devices and the latest version download is here: SuperSU v1.94.zip
dd98 said:
This is a general discussion thread for Liberty ROM
Please ask any question you may have and I'll try to answer it as best I can.
Somebody asked for instructions on how to install Liberty ROM and New Firmware so here they are:
Installation of leaked firmware (HBOOT 2.16) and Liberty ROM
WARNING - This WILL wipe your SD Card so back up your files before proceeding
Make sure HTC Sync is REMOVED and drivers are installed. Get drivers: Here
Charge your phone to AT LEAST 60% just in case
If you are S-OFF proceed to step 3, if not continue to step 2.
If your phone is from T-Mobile (US & Germany), Telus or Boost Mobile use Moonshine S-OFF
If you have the international model use: Facepalm S-OFF, Firewater S-OFF or Rumrunner S-OFF (Rumrunner is the easiest in my opinion)
Note that people with the T-Mobile, Telus or BM model CAN use Facepalm, Firewater and Rumrunner as well but international users CANNOT use Moonshine
Now use one of these methods to S-OFF (You cannot proceed if you are S-ON)
Now download the new firmware: Here
Extract the file to a convenient location (Like Desktop)
Open the Install Package folder, press the Shift key, Right-Click while holding Shift and select Open Command Window Here
If your phone is on type:
Code:
adb reboot oem-78
and hit enter
If you are in the bootloader, select Fastboot and type:
Code:
fastboot oem rebootRUU
and hit enter
Now type:
Code:
fastboot flash zip firmware.zip
and hit enter
You should get a message like this: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)". Do not panic just type the command above again.
The green bar on the screen should stop at about 80-90% but do not worry, this is normal.
Now to flash the required recovery type this:
Code:
fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.zip
and hit enter.
Now reboot into the bootloader by typing:
Code:
fastboot reboot-bootloader
and hit enter.
Once in the bootloader select Recovery
When you are in recovery go to Advanced then ADB Sideload
Now you download the ROM: Here. (Latest release is V3)
Now place LIBERTY-S4-Vx.zip into the Install Package folder (The x represents version number, e.g V4
Now open a new command window by holding Shift and Right-Click at the same time and selecting Open Command Window Here
Next you must type:
Code:
adb sideload LIBERTY-S4-V3.zip
and hit enter.
Make sure the screen is on when the sideload is almost 100% complete as TWRP freezes for some reason.
Now follow the instructions in the installer, make sure you select Wipe Data during installation and Reboot when the installation process is finished.
Finished
Click to expand...
Click to collapse
i tried to achieve S-Off with Rumrunner , said ERROR : your are not rooted , although i unlocked my bootloader ! and it says in the prereq : unlocked bootloader OR rooted , not both ... what to do now ? help anybody ?
Hiken_Ace said:
i tried to achieve S-Off with Rumrunner , said ERROR : your are not rooted , although i unlocked my bootloader ! and it says in the prereq : unlocked bootloader OR rooted , not both ... what to do now ? help anybody ?
Click to expand...
Click to collapse
I would root and try again

Categories

Resources