Related
Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.
spagmuff said:
Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.
Click to expand...
Click to collapse
After you flash the custom ROM using CWM, you then have to extract the boot.img file from the ROM.zip file and manually flash it in FASTBOOT mode. That is the nature of the unlocked bootloader. The boot partition is not mounted R/W in recovery mode, it is only mounted R/W when you are in bootloader FASTBOOT mode.
Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.
spagmuff said:
Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.
Click to expand...
Click to collapse
Step 2 and 3 are not necessary. After you Unlock the bootloader, you could then simply flash ClockworkMod in FASTBOOT mode.
1. Unlock bootloader.
2. Flash CWM image in FASTBOOT mode.
3. Backup existing ROM with CWM.
etc.
Successfully installed latest nightly r2 yesterday night :O
All is fine, 3D performance is smoothly and fine...
Thanks for yours posts
I would also like to thank you tpbklake, haven't tried it yet, but I'm sure it'll work!
I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?
kjdfkvdjjndvldmv; awesome
xStreame said:
I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?
Click to expand...
Click to collapse
Either isn't possible without s-off, look at the index thread, it's all there.
Swyped from my desire s running damn sweet ice cream
I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??
Kayak83 said:
I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??
Click to expand...
Click to collapse
Download the latest su-3.0.x.zip file. Then boot into CWM recovery and install this zip file. This will root the current ROM you have installed and then ROM Manager and BusyBox will both be happy.
@korenisko
So you unlocked via HTC dev, flashed custom recovery, wiped all partitions, flashed cyanogenmod, rebooted into fastboot, flashed boot.img via fastboot (fastboot flash boot /pathtobootimg/boot.img, if i recall correctly) and then you were able to boot into cyanogen?
I did exactly these steps (only with 4ext instead of cwm, which shouldn't affect the result) and was stuck with the white bootscreen and no adb logcat output whatsoever.
Currently I am back on a prerooted official RUU (2.3.3), but it still performs really bad and I would like to have cyanogenmod.
Btw: I have a Desire S, hboot 2.00.0002, S-ON, no carrier branding.
Thanks,
wenzlern
The currect way
I Have HTC Desire S with original Rom 2.10.401.8 and HBOOT 2.00.0002 S-On
My goal is to install the Endymon
I read many thread and i understood that the curret way to do this is:
Downgrade My ROM from 2.3.5 ( 2.10.401.8 with HBOOT 2.00.0002) to a ROM 2.3.3 with HBOOT 0.98.00000 (Ex: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.exe)
To do this i need to follow the steps from 1 to 7 of this
http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
Now i need to change HBOOT, Change Recovery and Root the phone. To do this i need to use Revolutionary tool for Windows from http://revolutionary.io/ and follow the istruction.
Now i can download the custom Rom and install using this way:
http://forum.xda-developers.com/showthread.php?t=1257731
Is It right?
Thanks
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Congrats. XDA is really helpful.
Sarina,
No need to wipe dalvik cache?
bcoz few ROM's developers days it a must!!!!
I trying to flash CM7.1 stable version.
mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Many thanks for this it has helped me get S-off again after a very frustrating weekend.
I've got a HTC Sensation XE.
Build Number - 3.33.720.106
Kernel version 3.0.16-g31a4fc7
HBoot version 1.29
I've spent about 3 hours reading about Rooting, flashing custom roms and I'm still confused as hell.
From what I've read, S-OFF is a pretty complicated process for users with HBoot version 1.27+
We have to use the wire trick, etc.
I'm not sure if I should S-OFF for two reasons:
1. First time flashing a custom Rom I want to keep it as simple as possible.
2. To S-OFF, I must use HTCdev's bootloader unlocker process as well and I read somewhere that once I do that, my phone's IMEI will be added to HTC's banned-list for warranty claims. I do not want to do that till I'm absolutely sure on how to do it.(Is this true?)
Click to expand...
Click to collapse
So I have a few questions and need some help/guidance.
I wish to install a Custom Rom(Jelly Bean) without HTC's Sense as it takes up too much RAM and I want my phone to run smooth without lag. That is the priority.
1. Is it advisable to Root/Flash phone with S-ON?
2. What am I missing out on if I do not S-OFF my device?
3. If S-OFF is pretty advantageous, I am willing to read/learn more before Flashing a Custom ROM.
4. Which is the most stable and lag-free Custom ROM(Jelly Bean, No Sense)
4.a. With S-ON?
4.b. With S-OFF?
5. When you go to HTCdev.com->Bootloader unlocker, there is no Sensation XE, should I choose option Sensation 4g or go with All other devices?
Click to expand...
Click to collapse
I'm sorry if my questions are silly but I'm very confused, I've read like 15+ different links in the last 3hours and its all messed up in my head.
Please help me understand clearly and/or refer me to a few Beginner guides(with advanced guides followed).
in simple words you have 2 options:
1)unlock your bootloader with htcdev unlock method
see here http://www.htcdev.com/
and then root your device
see here http://forum.xda-developers.com/showthread.php?t=1632553 or
2)use the juopunutbear method to S-OFF and root your device
see here http://forum.xda-developers.com/showthread.php?t=1661631
now to answer to your questions:
1)with S-ON involves the first option.but then before flashing a rom,flash first 4ext recovery
so you can use the smartflash feature from it(only for S-ON DEVICES)
2)with S-OFF you are completely unlock your device and have the ability to flash firmware,radios,rils(which you can not do with S-ON)
3)it is more advantageous.
but before flashing a rom the only thing you have to do is read carefully any installation instructions(the same goes for S-ON)
4)it is the same i assume
5)go with All other devices
rzr86 said:
...
now to answer to your questions:
1)with S-ON involves the first option.but then before flashing a rom,flash first 4ext recovery
so you can use the smartflash feature from it(only for S-ON DEVICES)
2)with S-OFF you are completely unlock your device and have the ability to flash firmware,radios,rils(which you can not do with S-ON)
3)it is more advantageous.
but before flashing a rom the only thing you have to do is read carefully any installation instructions(the same goes for S-ON)
4)it is the same i assume
5)go with All other devices
Click to expand...
Click to collapse
1. How is firmware different from ROM?
2. I thought firmware was the same as ROM?
3. After unlocking my bootloader with S-ON, I can install any custom ROM right? or Are there only certain ROMS that are available for S-ON phones?
thetearer said:
1. How is firmware different from ROM?
2. I thought firmware was the same as ROM?
3. After unlocking my bootloader with S-ON, I can install any custom ROM right? or Are there only certain ROMS that are available for S-ON phones?
Click to expand...
Click to collapse
2)no they are different.firmware is flashing in a different partition and the rom in a different too
3)you can install any custom rom you want but you must have the appropriate fw version to boot a rom
if you have a gingerbread fw version you can install only gingerbread roms,if you have 3.32fw or 3.33fw you can install any ics or jb roms
but remember for S-ON devices use 4ext recovery to flash any rom and before flashing enable smartflash from it
edit:actually for S-OFF devices too it is better to have 4ext(but no need for smartflash)
about the first question i am still thinking the right answer
maybe someone else can tell you
rzr86 said:
2)no they are different.firmware is flashing in a different partition and the rom in a different too
3)you can install any custom rom you want but you must have the appropriate fw version to boot a rom
if you have a gingerbread fw version you can install only gingerbread roms,if you have 3.32fw or 3.33fw you can install any ics or jb roms
but remember for S-ON devices use 4ext recovery to flash any rom and before flashing enable smartflash from it
edit:actually for S-OFF devices too it is better to have 4ext(but no need for smartflash)
about the first question i am still thinking the right answer
maybe someone else can tell you
Click to expand...
Click to collapse
technical definition of a rom: Rom stands for Read Only Memory and technically speaking it refers to the internal storage of a device which is supposed to contain the operating systems instructions.the instructions are stored in read only memory,, firmware is the read only operating systems that stay firmly inplace without modification access to the users of the device, firmware in computing is a software that is embedded in a hardware device. it is often provided on flash roms or is a binary image file that can be uploaded onto a existing hardware by a user. firmware is identified as the computer program in a read only memory or ROM integrated circuit.a hardware part number or other configuration identifier is usually used to represent the software. firmware is required for the rom. basically the firmware is the operating system containing the android operating system .hope this helps .best wishes
Hello All,
Sorry for my lack of knowledge. I've been searching for answers for quite some time but all was getting a bit vague. So I have to put my questions here.
1. I have HTC One S S4, 4.1.1 stock, HBOOT 2.15.0000, Rooted with bootloader unlocked, CID = BM_001 (Bell Mob Canada), Software No. 3.16.666.9, TWRP Recovery, made a backup of System and Boot using TWRP
*Rooted and bootloader unlocked using AIO Tool by Hasoon
Now I have some questions regarding stock and custom ROM flashing.
2. If I have to "unroot" or revert to stock ROM, do I have to do the following?
- Lock Bootloader
- Flash stock recovery (I suppose extracting it from the OTA zip?)
- Flash the OTA zip (I downloaded stock OTA_Ville_U_JB_45_S_BM_3.16.666.9_1.11.50.05.28_10.27.50.08L_release_308167fun0bzhoz2tch0mh.zip, there was no RUU for this carrier)
- OR flashing the firmware.img from the OTA zip?
I am all confused about how I will flash stock firmware as there is no RUU for Bell Mobility JB, just the OTA which is 600+ MB.
Will that be all?
3. Can I flash a Stock ROM other than BM?
- Is there an International carrier free version that I can flash?
- Any drawbacks of this process?
4. If I want to go with flashing a custom ROM, will I have to something further? E.g
- S-off
- SuperCID (Not possible with HBOOT 2.15)
5. Other than battery Issue, I believe there’s this Camera issue which don’t understand in particular. Is there no ROM which can provide the same Camera functionality as Stock? What’s the ROM that provides the closest functionality to that of the Stock?
khan.orak said:
Hello All,
Sorry for my lack of knowledge. I've been searching for answers for quite some time but all was getting a bit vague. So I have to put my questions here.
1. I have HTC One S S4, 4.1.1 stock, HBOOT 2.15.0000, Rooted with bootloader unlocked, CID = BM_001 (Bell Mob Canada), Software No. 3.16.666.9, TWRP Recovery, made a backup of System and Boot using TWRP
*Rooted and bootloader unlocked using AIO Tool by Hasoon
Now I have some questions regarding stock and custom ROM flashing.
2. If I have to "unroot" or revert to stock ROM, do I have to do the following?
- Lock Bootloader
- Flash stock recovery (I suppose extracting it from the OTA zip?)
- Flash the OTA zip (I downloaded stock OTA_Ville_U_JB_45_S_BM_3.16.666.9_1.11.50.05.28_10.27.50.08L_release_308167fun0bzhoz2tch0mh.zip, there was no RUU for this carrier)
- OR flashing the firmware.img from the OTA zip?
I am all confused about how I will flash stock firmware as there is no RUU for Bell Mobility JB, just the OTA which is 600+ MB.
Will that be all?
3. Can I flash a Stock ROM other than BM?
- Is there an International carrier free version that I can flash?
- Any drawbacks of this process?
4. If I want to go with flashing a custom ROM, will I have to something further? E.g
- S-off
- SuperCID (Not possible with HBOOT 2.15)
5. Other than battery Issue, I believe there’s this Camera issue which don’t understand in particular. Is there no ROM which can provide the same Camera functionality as Stock? What’s the ROM that provides the closest functionality to that of the Stock?
Click to expand...
Click to collapse
-you cant flash ota trough twrp, you have to wait for a ruu
(or get s-off, then you can flash older ruu and do normal ota trough stock rom)
first flash recovery then lock
your CID allows what you can flash + if no s-off you can go lower than your current state/hboot
for flashing only custom roms s-off of supercid is not needed, you might need an updated firmware for the new kernel on asop.
if you want only stock, there are also stock custom roms (with/without bloatware) that are recovery flashable
try facepalm or moonshine if you want soff.
real187 said:
-you cant flash ota trough twrp, you have to wait for a ruu
(or get s-off, then you can flash older ruu and do normal ota trough stock rom)
first flash recovery then lock
your CID allows what you can flash + if no s-off you can go lower than your current state/hboot
for flashing only custom roms s-off of supercid is not needed, you might need an updated firmware for the new kernel on asop.
if you want only stock, there are also stock custom roms (with/without bloatware) that are recovery flashable
try facepalm or moonshine if you want soff.
Click to expand...
Click to collapse
Thanks. Maybe S-Off is the last resort.
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
808phone said:
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
Click to expand...
Click to collapse
Are you on hboot 2.15 too? Did you update your firmware?
No but there are sense 5.5 roms with android 4.3....
How did you get S-OFF? And which tutorial did you use to unlock etc?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Rapier said:
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Click to expand...
Click to collapse
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
MICH_** said:
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
Click to expand...
Click to collapse
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Rapier said:
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Click to expand...
Click to collapse
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
MICH_** said:
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
Click to expand...
Click to collapse
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Rapier said:
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Click to expand...
Click to collapse
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
MICH_** said:
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
Click to expand...
Click to collapse
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Rapier said:
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Click to expand...
Click to collapse
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
MICH_** said:
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
Click to expand...
Click to collapse
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Rapier said:
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Click to expand...
Click to collapse
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
MICH_** said:
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
Click to expand...
Click to collapse
Good choice, Viper is a fine ROM and close to the original since it's sense based...also has extra customization that the original ROM doesn't have.
For the radio, well I've answered to you in the Viper thread. I would advice not to flash another radio just now. Flash the ROM, play with it for a few days then decide. If you have no issues with signal reception, wifi and so on, you don't have real reasons to change it.
I had initially (when I bought the device) radio 1.06es (I think)...since then alot of newer versions came out including the 1.20 from the leaked 2.16 firmware and the newest 1.35a from the One XL. To be honest, after several days with each, I've switched back to 1.15 that was the best radio for me.
The only ROM for which you MUST flash a different radio will be Liberty by bilal_liberty. That is based on Android 4.3 and Sense 5.5 and the newest 1.35a radio is needed in order to get H/H+ (HSPA) mobile data connection. If you don't use that radio you'll get maximum 3G (UMTS) connection. The rest will work tho
I still don't understand why I had so many problems with Viper. Dropped calls, random reboots etc...
Once I got CM11 running - never looked back in terms of reliability.
Hi,
Looking for some help with flashing ROMs
My phone is HBoot 2.15
Using TWRP v2.7.1.0
Every ROM I flash seems to install correctly but when booting I get the white HTC screen then the screen goes black and/or reboots (into a loop)
I'm using the HTC One S All-In-One Toolkit 'ADB Sideload a ROM' option to flash ROMs.
Phone was on Orange UK, CID ORANG001
Any ideas if I'm missing something simple?
Rob
I assume you're S-On, aren't you? Did you flash the kernel (boot.img) via fastboot after flashing the rom? Since you're S-On roms won't boot without this step.
Flippy498 said:
I assume you're S-On, aren't you? Did you flash the kernel (boot.img) via fastboot after flashing the rom? Since you're S-On roms won't boot without this step.
Click to expand...
Click to collapse
Will help with this tool, use it to S-OFF http://forum.xda-developers.com/showthread.php?t=2155135