Note: This is an old thread and the information in here may not be up to date.
This thread is intended mainly for people who have phones with SLCD displays. Please take a minute to read it before attempting to run any updates, downgrades, or applying any RUUs.
There have been lots of posts and confusion about HBOOT 0.83, 0.92 and SLCD over the last few weeks. These newer versions of the bootloader are installed by certain official updates, and come pre-installed on most new phones. To get straight to the point: HBOOT 0.83 is not a problem. Quite a few people have ended up breaking their displays by trying to downgrade, when it isn't necessary.
Q. I applied an RUU/downgraded to HBOOT 0.80 and now my screen doesn't work.
A. You can recover by upgrading to stock froyo. Just insert your goldcard and run this generic RUU: http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
Q. Which RUUs are safe to use with an SLCD screen?
A. All froyo RUUs are safe (release beginning 2.x). Otherwise do not attempt to use any other RUU that isn't listed in this post.
Q. How do I upgrade to stock unbranded froyo (without root)?
A. Use the RUU for froyo in question 1.
Q. I have upgraded to froyo, but want to downgrade/root.
A. Don't try using old methods as they will break SLCD screens. You can use a tool I have developed. Read the thread here: http://forum.xda-developers.com/showthread.php?t=768256
Q. How do I know if my screen is SLCD or AMOLED?
A. A black background in low light, at certain angles, will have a slight grey sheen to it if your screen is SLCD. On an AMOLED screen it will remain the same black. If you got your phone before July 2010 it is AMOLED.
Q. Does HBOOT 0.83 mean I have an SLCD screen?
A. No.
Q. Can I root my phone on HBOOT 0.83 and use custom recovery?
A. Yes! Use unrevoked3. http://unrevoked.com/recovery/
Q. My screen goes blank when I use custom recovery with unrevoked3.
A. You are using an old version of unrevoked3. Please try again with the latest version.
Q. Can I use AmonRA custom recovery instead?
A. Yes, it has now been updated to support SLCD. Install via unrevoked3 with this image: http://amonra-mod.googlecode.com/files/recovery-RA-desire-v1.7.0.1-R5.1.img
Q. What is the difference between HBOOT 0.83 and 0.92?
A. 0.92 is installed currently only if you apply the official froyo update or if you buy an unbranded phone with froyo. You cannot directly root running froyo yet, but this will soon be available. In the meantime you must downgrade to Android 2.1.
Q. How do I downgrade to HBOOT 0.80 from 0.83?
A. Don't - there is absolutely no reason to. If you want to root or use a custom ROM or debrand you should not try to downgrade.
Q. Can I debrand my phone with HBOOT 0.83?
A. Yes. What's important is your software release, not your bootloader version. If your software version is 1.21.405.2 or lower (for example, branded O2 phones), you can simply use this generic RUU with a goldcard to debrand and install stock 1.21.405.2. You can then root or upgrade to froyo if you wish to. This RUU will also flash your HBOOT to 0.83. http://shipped-roms.com/shipped/Bra...1.00.32U_4.08.00.09_release_137222_signed.exe
Q. My software version is higher than 1.21.405.2 (e.g. I applied the Vodafone branding update). Can I debrand?
A. If you want Android 2.1 you need to use the downgrade tool. If you want froyo, just apply the froyo RUU as described in the first question.
Q. I have an SLCD screen. Can I run custom ROMs?
A. The latest ones will work. The pre-rooted version of official froyo works fine including all custom ROMs based on it (kernel 2.6.32.15).
Q. Can I rebrand my rooted/debranded SLCD phone?
A. You will need a branded froyo RUU. Currently available: O2 2.14.207.1
Actually, I have just managed to downgrade and debrand my SLED Desire from Vodafone's hboot 0.83 & 1.24 firmware to HTC stock 0.80 and 1.21.405.2 (without wrecking my screen in the process). I'll post a detailed description after I'm done doing the victory dance.
@bloodmeg - you must have an AMOLED screen. SLCD will NOT work on HBOOT 0.80.
Ah, you're right, I got a bit carried away there. I did not downgrade the HBOOT, just the firmware to 1.21 (with 1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09 which was reported to work with SLCD).
Thanks for correcting me.
The RUU flash process usually checks the installed software version and refuses to work if it's higher than what you're trying to install. This is why the froyo downgrade reports itself with a fake version.
edit: Although thinking about it, it would be possible to root the phone, put in a fake version into the misc partition (e.g. 1.21.405.2), and then that should trick the RUU checker into thinking you have that version installed.
teppic74 said:
edit: Although thinking about it, it would be possible to root the phone, put in a fake version into the misc partition (e.g. 1.21.405.2), and then that should trick the RUU checker into thinking you have that version installed.
Click to expand...
Click to collapse
Which is exactly what I did.
bloodmeg said:
Which is exactly what I did.
Click to expand...
Click to collapse
Can you post the precise steps you used so that other people can do the same?
Added minor edits to take into account the procedure for rooting the phone without a screen.
Thank you
Thanks. Finally got my phone debranded. It was bought 2 days ago, branded to O2 Ireland. Don`t have it rooted, but now I'm downloading froyo on my phone. Don't have to wait for the O2 to release it.
I've realised to downgrade from Vodafone branding (or any software version higher than 1.21.xx) you just need to run the update.zip fix rather than mess around with the misc partition yourself. It sets your software version to 1.15.405.3, so any RUU with later software will work. Obviously with an SLCD screen you still have to flash the correct RUU.
How do I implement the .img linked to in Question 2? Do I put it on the root of my SD card before I run unrevoked3?
zakkain said:
How do I implement the .img linked to in Question 2? Do I put it on the root of my SD card before I run unrevoked3?
Click to expand...
Click to collapse
No, it must be on your computer when you run unrevoked3. Select it from the file menu - you have to do this before you plug the phone in.
Hi How can become 100% stock with Asia_WWE RUU with a SLCD screen.. current Asia_WWE does not currently compatible with SLCD
This is a good informative FAQ and I wish I had found it last week before OTA'ing my SLCD. This IMO should be sticky, have an additional question for determining AMOLED or SLCD, have a question for determining HBOOT and be renamed slightly so as not to alienate 0.92 HBOOT users.
Of course, you're welcome to just ignore me, whadda I know?
Many thanks for your work,
debully.
I've added a couple of bits. The thing about HBOOT 0.92 is that you only get it at the moment if you upgrade to froyo yourself - I don't think phones are being shipped with froyo yet. As for being sticky, I don't know who decides those things.
Hello Teppic
Thanks for the write up in post 1, Im thinking of unrooting my desire and downloading OTA Froyo, can you give me a link to a "generic RUU" in order to do this.
Many Thanks
You can find the links in the first post. If you want froyo (no rooting) just install the froyo RUU directly.
lasitha85 said:
Hi How can become 100% stock with Asia_WWE RUU with a SLCD screen.. current Asia_WWE does not currently compatible with SLCD
Click to expand...
Click to collapse
+1
looking for this too
As it states:
Q. Which RUUs are safe to use with an SLCD screen?
A. The two mentioned here. All other currently available RUUs will stop the screen from working.
my software number is
1.30.415.3
and Hboot is
0.83....
i rooted my phone (i see Super Permission app. on the menu) when i want to recovery update.zip, i get status 7 error?
what can i do? can anybody help?
Related
Hi!!
I just got a Desire S, i' am new to rooting... so i need to know whether i can go back to the stock ROM (2.3.3 with sense 2.1) after i root the device.
This is the only dilemma holding me back from rooting my desire s.
Thank you for your Time! : )
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
rusor123 said:
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
Click to expand...
Click to collapse
Let me guess - when you power on your device you have the T-Mobile logo
Your current software version is higher then the T-Mobile RUU provided here (RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_3 8.03.02.11_M_release), so to restore Stock you will have to downgrade and then update via the Software actualization option in your settings (if such OTA is available) to return it to the current state. This is more tricky process, that can be done flawlessly if your device is healthy. But if you get in trouble and some system components are not responding (brick, bootloop) there is a great change that you will be not able to S-ON again. Happened to a lot of branded devices, reported here.
So my advice is to keep using it that way - it is still a great phone even with Stock software. You can S-OFF and root it of course at your own risk.
It is up to you
Dude you are right man... the T-mobile sign does come up, thanks for the heads up, appreciate it... don't want to brick ma phone... i' ll keep using it this way.
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
rusor123 said:
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
Click to expand...
Click to collapse
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
thnx!!!!!!!!!!!
amidabuddha said:
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
Click to expand...
Click to collapse
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
rusor123 said:
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
Click to expand...
Click to collapse
Yes you should receive the update, because the update check from your phone settings is made on a central server (both on WiFi and Mobile data, the phone connects to the same place in the Internet)
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
hey im kinda a noob so what u said means i can or not, i have a desire s and i cant wait for the sense 3.0 update so if i download a custom rom for now, and when the official update comes in my region can i go back to the stock android then update it normally??????
Hello
I know this has been discussed alot. But i just want to check in before doing this to my phone.
So i have upgraded to 5.11 Bootloader unwillingly and now i want to downgrade back to a 1.xx bootloader and install a HSPL So i could install a Custom full unlocked WP7 phone
First of all here is my phone's current status:
HTC 7 Mozart (1st gen) TMO branded with no sim lock
OS:7.10.7720.68
Firmware: 2250.21.50401.111
HW revision: 0004
Radio: 5.71.09.02a_22.51.50.21U
Bootloader: 5.11.2250.1(133065)
Unfortunately I have no access to any Android/WM 6.5 phone and i have no SD/micro-SD card (I can buy them, but i'd rather not because they have no use to me) But i do have a 8GB USB flash.
So, from what i have read, Since i have a TMO_DE (111) phone, I cannot use ansar's ROMs to downgrade and my only option would be the goldcard method.
The only thread about downgrading 5.xx SPL that i meet their requirements is This
So a few questions:
1. Do i have to use the Goldcard.IMG provided in that thread or i need to make myself one for Mozart as said in other threads?
2. Im going to use "RUU_Mozart_TMO_DE_1.30.401.01_Radio_5.54.09.21_22.33b.50U_NoDo_Signed_by_ansar" ROM. Is this correct ROM to do a downgrade with?
3. Just checking in, After a successful Downgrade (If i don't brick my phone) Im going to first Install HSPL as instructed in [DFT][Updated!#3] HSPL / RSPL for HTC WP7 First Generation And then Install a Custom ROM in [update][DFT Freedom ROM] Mozart mango 7720 V2 version. Is this right to get a FULL unlocked device?
4. After i Downgrade my phone using Goldcard, Do i get a working OS so i can resume the work later?
Thank you all. And let this topic stay to answer some newbies like me
Ad. 1. You can use Goldcard.img from that topic (post #5).
Ad. 2. I think so it's ok ROM, but you have to try.
Ad. 3. Yes.
Ad. 4. After downgrade you can install other stockROM or (if you have HSPL) costomROM. If you install stockROM you lost HSPL.
You can try that downgrade method (SLSPL by Ansar): http://forum.xda-developers.com/showthread.php?t=1196183 for HTC Mozart you have link in #2 post.
Question 4: Yes. Downgrading the SPL (even breaking it, which is what a "half-bricked" phone has) does not limit the ability of the OS to operate.
Note, however, that any official updates installed during this time may also include a new SPL, forcing you to downgrade it again if you want to use a custom ROM.
Ad. 1. You can use Goldcard.img from that topic (post #5).
Ad. 2. I think so it's ok ROM, but you have to try.
Ad. 3. Yes.
Ad. 4. After downgrade you can install other stockROM or (if you have HSPL) costomROM. If you install stockROM you lost HSPL.
You can try that downgrade method (SLSPL by Ansar): http://forum.xda-developers.com/show....php?t=1196183 for HTC Mozart you have link in #2 post.
Click to expand...
Click to collapse
Hello
Thank you for your answers
about ansar's downgrade thread, Im not sure if i can use those roms for my phone. Can you confirm that they will work on my device?
I'd love such a easy method instead of creating a Y cable
Question 4: Yes. Downgrading the SPL (even breaking it, which is what a "half-bricked" phone has) does not limit the ability of the OS to operate.
Note, however, that any official updates installed during this time may also include a new SPL, forcing you to downgrade it again if you want to use a custom ROM.
Click to expand...
Click to collapse
Hello
So i assume that i won't get a full brick even if i get a failure update or even power loss in the middle of updating process?
Thank you
arman34r said:
Hello
Can you confirm that they will work on my device?
Click to expand...
Click to collapse
Are you read Ansar topic (point 3 - bold)?
The process is as simple as of these 3 steps
1. Download the proper SLSPL ROM for your branded device operator, see post #2
2. Flash the provided SLSPL ROM and will re-boot in tricolor Bootloader screen, see post #3
3. Flash ANY Stock ROM of your branded device operator and finish the story of 5.10 Bootloader
Click to expand...
Click to collapse
Budniu said:
Are you read Ansar topic (point 3 - bold)?
Click to expand...
Click to collapse
Yes, but i don't understand what it does mean exactly
Do you mean that those roms will work on my device (to downgrade it) but i need to have a Stock rom to install on it? (but i can install HSPL on top of it to get custom roms, right?)
I can't think of any other definition right now
And i'm sorry my english is not that good, so maybe you can clear it up for me if it's not that?
1. Install SLSPL ROM for Mozart: RUU_Mozart_HTC_Europe_5.11.401.01_SLSPL_Signed_by_ ansar.zip
2. Install branded stockROM=originalROM for Mozart. Download this one: RUU_Mozart_TMO_DE_1.25.111.05_5.50.09.18_22.24.50_RELEASE.exe
(source from @Football: http://forum.xda-developers.com/showthread.php?t=1427893)
3. Install RSPL/HSPL
4. Install customROM (what you want)
Now, it's clear ?
Budniu said:
1. Install SLSPL ROM for Mozart: RUU_Mozart_HTC_Europe_5.11.401.01_SLSPL_Signed_by_ ansar.zip
2. Install branded stockROM=originalROM for Mozart. Download this one: RUU_Mozart_TMO_DE_1.25.111.05_5.50.09.18_22.24.50_RELEASE.exe
(source from @Football: http://forum.xda-developers.com/showthread.php?t=1427893)
3. Install RSPL/HSPL
4. Install customROM (what you want)
Now, it's clear ?
Click to expand...
Click to collapse
Thanks for clearing things up
Trying this now.
I have downloaded RUU_Mozart_HTC_Europe_5.11.401.01_SLSPL_Signed_by_ansar.zip And tried to flash my Mozart. But got the "INVALID VENDER ID" error (My phone is not branded). I live in Middle East. Does this mean that I can't use the Europe version (which ansar provided) to flash my Phone?
Apologies for the kind of naive question. I'm still a newbie in these stuff.
Hmmm I don't know why, but I think so you have to ask Ansar why you can't install that ROM.
Hello folks, sorry for the dumb questions but this is new for me. I have HTC One X (AT&T) phone, bought in USA. This is my first android phone and I barely know android as a software. I unlocked the phone buying an unlock code from ebay and I am using the phone on another carrier. My question is, how can i manually update my phone (what is the newest update?) since AT&T is not a carrier in my country and I cannot update automatically.
At the moment my software information are:
Android version 4.0.3
HTC Sense version 4.0
Software number 1.85.502.3 710RD
Kernel version 3.0.8-01155-gca24d1eroo[email protected] # SMP PREEMPT (why is there root in the kernel version, my phone has never been rooted?)
Build number 1.85.502.3_R2 CL63811 release-keys
Doing this manual update if possible will the phone be locked to AT&T again, or my phone will remain unlocked?
I'm sorry for my bad english and sorry if there is already a question like this (I watched the noob video and did use the search button)
Thank you in advance
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
redpoint73 said:
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
Click to expand...
Click to collapse
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
StoleMacuk said:
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
Click to expand...
Click to collapse
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
I have a doubt. As I'm no from USA, I'll have no option to update the firmware over the air. How must I proceed in this part of the manual method?
Won't I have any issues with this?
Thank you guys in advance...
galitore said:
How must I proceed in this part of the manual method?
Click to expand...
Click to collapse
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
iElvis said:
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
Click to expand...
Click to collapse
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
galitore said:
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
Click to expand...
Click to collapse
Whoops! Sorry about that.
As far as I know, the only way is to flash a custom rom with the base you want, or to run the RUU for that base, which will leave you relocked and unrooted.
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).
Would somebody please advise me about the pro's and cons of changing my HBOOT version.
I can successfully root my phone via The Revolutionary method after downgrading using an earlier RUU etc.
What I am not clear about is whether I then need to flash an ENG HBOOT after this process .... which version.... why I should do this ?
If I have the "wrong" HBOOT installed will that prevent certain ROMs from running correctly ?
Do I need a specific "level" of HBOOT for a GB based ROM to run and another for an ICS based ROM
Choosing your HBOOT Version
I don't know absolutely everything about this, but since you've waited over a month with no replies, I'll tell you what I know. It should be enough to answer your question, if you're looking for something more advanced then you may need to keep looking!
The original HBOOT version is 0.98.00000, this is the HBOOT version that you need if you want to S-OFF your phone as the later version, 2.000.00002, blocks the vulnerability that allows the Revolutionary exploit to work. S-OFF unlocks root level access to the phone permanently, allowing you to flash new ROMs directly from the SD card without having to use ADB and USB Debugging to flash the boot image every time.
Basically, if you want S-OFF you may need to downgrade your HBOOT to 0.98.0000 if that's not the version you already have.
The phone originally shipped with Android Gingerbread 2.3, this can be upgraded to a certain point, beyond which, the newer version of HBOOT is required. I don't know which version is the crossover point but I'm sure a quick search of the forums will provide the answer, I'll leave that up to you (I think the main reason you haven't had any replies is that ALL this info is already available in the various guides in the forum, so people think you're being lazy not looking for it!).
So....
Unless you're trying to do something out of the ordinary, the most common approach is a follows;
Unlock bootloader on HTCDev.
Downgrade to HBOOT 0.98.00000 (f necessary).
Use Revolutionary to gain S-OFF.
Upgrade to HBOOT 2.000.00002 (not necessary for Android 2.3 but later versions require this)
Download and flash new ROMs directly from the SD card using custom recovery, such as TWRP or Clockworkmod.
I hope this helps, I do understand that it's not always easy piecing things together from multiple forum threads to learn about something new, but ALL the info you needed IS already available on here.
There are some excellent guides and tutorials here on XDA Developers, both official and unofficial. I would say if you don't already have a bit of knowledge then stick to the official guides and you can't go wrong.
Hint: Try searching the forum for [Guide]