So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?
Cbaird said:
So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?
Click to expand...
Click to collapse
Yes, you can install an ROM you wish, but depending on hboot you may have to flash the boot.img in fastboot. There is an easy method of getting stuff in the original android development section of this phones forum, so do that and you won't have to work. Happy flashing
Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium
S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863
ECEXCURSION said:
Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4
mirGantrophy said:
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4
Click to expand...
Click to collapse
Why aren't sense kernels in original development? I could be wrong but aren't they built from source
a box of kittens said:
Why aren't sense kernels in original development? I could be wrong but aren't they built from source
Click to expand...
Click to collapse
To prevent confusion
Sent from my Nexus 4 using xda app-developers app
Wubbz said:
S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863
Click to expand...
Click to collapse
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?
Cbaird said:
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?
Click to expand...
Click to collapse
Since your on a Hboot lower than 1.14 you shouldn't have to downgrade anything, Hboots or the touchscreen firmware, But I would still recommend doing the S-OFF still. If you do, read through the instruction before you start then give it a go. Once your device is S-OFF you can downgrade or upgrade to any Hboot or change to what ever Radio you wish and no more flashing boot.img on Hboots 1.14 and up.
TIP for S-OFF I was getting error 99 with cm10.1 so i had to backup and wipe my phone and goto Viper XL 3.2.3 and then restore my cm10.1 rom from trwp recovery, there is a post about this in the S-OFF thread it might be in the OP now not sure though.
Also if you move to a 4.2.X based rom from 4.1.X or lower you will probably need to upgrade your adb folder if you haven't made it with googles newest build
Related
Hi All,
I have a Telstra one xl with the OTA update (ie hboot 2.14)
I unlocked the bootloader using HTCdev.
Installled TWRP
Installed CM10.1 nightly (from a night ago)
Now because I have the most recent touch screen firmware the screen doesn't work in non sense ROM's
So I tried loading the following Sense ROMs:
Telstra_Stock_1.89.841.9.zip
OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip
CleanROM 6 R2.zip
radavs-pablo11-TelstraJB-stock.zip
ViperX3.4.0.zip
But it always fails.
So I tried using the RUU (1.89 or 1.81) and that fails as well
So I tried using the RUU method to flash the OTA update (the one above) and that also fails.
I am assuming this is because I am S-ON and HBOOT 2.14...
I can load up CM10.1, but the touch screen doesn't work, which means I cant get into a ROM to SOFF and downgrade the HBOOT to flash the TP firmware...
Suggestions/Ideas?
Regards
D
I had an idea.
Is there a way to enable USB debugging in the ROM ZIP?
That way I can flash up CM10.1 with USB debugging already enabled... So I dont need the touch screen...
Then I can do all the normal ADB stuff...
So in the zip, what file do i need to modify to have USB debugging enabled from boot?
tephra said:
Hi All,
I have a Telstra one xl with the OTA update (ie hboot 2.14)
I unlocked the bootloader using HTCdev.
Installled TWRP
Installed CM10.1 nightly (from a night ago)
Now because I have the most recent touch screen firmware the screen doesn't work in non sense ROM's
So I tried loading the following Sense ROMs:
Telstra_Stock_1.89.841.9.zip
OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip
CleanROM 6 R2.zip
radavs-pablo11-TelstraJB-stock.zip
ViperX3.4.0.zip
But it always fails.
So I tried using the RUU (1.89 or 1.81) and that fails as well
So I tried using the RUU method to flash the OTA update (the one above) and that also fails.
I am assuming this is because I am S-ON and HBOOT 2.14...
I can load up CM10.1, but the touch screen doesn't work, which means I cant get into a ROM to SOFF and downgrade the HBOOT to flash the TP firmware...
Suggestions/Ideas?
Regards
D
Click to expand...
Click to collapse
One thing I noticed is that you tried to install viperx3.4.0.zip which is an international rom made for the quad core onex and not the dual one x like you have. Im sure team viper has implemented some form of protection to keep you from flashing the wrong version of the rom on the wrong phone.
yeah I realised that mistake, and got the ViperXL-3.2.6 ROM - which is for the XL...
That installs ok, but just goes into a boot loop - ie white htc screen, viperxl screen, viper animated graphic, reboot .... ...
By flashing CM10.1, you have an AOSP kernel. You can't run Sense roms on top of that. Flash the stock Sense kernel or one of the custom Sense kernels.
Once you do, that, you should be able to boot up. Then you can s-off an downgrade your touchscreen firmware.
im not entirely sure how todo that...
is the kernel the boot.img?
edit - seems like it is. So I have flashed the boot.img inside ViperXL.. Reinstalling Viper now.
hopefully I get a usable phone - lol
yay - its working!!!
boot.img from the viperxl zip gave me a working phone
supercid let me s-off
s-off let me downgrade the touch panel firmware
just flashing up CM10.1 now...
tephra said:
yay - its working!!!
boot.img from the viperxl zip gave me a working phone
supercid let me s-off
s-off let me downgrade the touch panel firmware
just flashing up CM10.1 now...
Click to expand...
Click to collapse
Glad you got it working!
Sent from Xparent Red using my Venomized Evita
Can you assist on how to downgrade touchscreen firmware, and link to the right one for HTC One XL?
keithkulinga said:
Can you assist on how to downgrade touchscreen firmware, and link to the right one for HTC One XL?
Click to expand...
Click to collapse
There are multiple threads in the development section explaining what you need to know, though I have real doubts any of the links are still working for firmware files after all these years.
Be very careful what you're doing as there are different One X models and flashing the wrong stuff can hard brick your phone with no hope of recovering it.
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
S1pk3 said:
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
Click to expand...
Click to collapse
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
S1pk3 said:
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah. It is just recommended that you are s-off.
As the guy said before you need to flash boot.img (the kernel) afterwards.
Sent from my One S using xda app-developers app
Will give it a try. Thanks.
Sent from my HTC One S using xda app-developers app
Stuck while flashing firmware in htc one s
I got stuck while installing htc one s with maximus hd..
http://forum.xda-developers.com/showthread.php?t=2445392&highlight=sense+5
I did till fastboot flash recovery TWRP2.6.1.0.img ...but aftr fast boot reboot it dint take memory...without that i cant copy ROM to memory...i did unlock bootloader not s off.... i got an error99 while flashing firmware.. icant on the device now....please help me...
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
sylvantino said:
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
Click to expand...
Click to collapse
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
sylvantino said:
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
Click to expand...
Click to collapse
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
tivofool said:
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
Click to expand...
Click to collapse
thanks for the information. i read through magiorom thread. trying to download now.seems a flaky webhost
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
Hi would moonshine work for hboot 2.16 ?
cyberusman said:
Hi would moonshine work for hboot 2.16 ?
Click to expand...
Click to collapse
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
tivofool said:
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
Click to expand...
Click to collapse
Well i have hboot 2.16 and i need to s-off i get this error when trying to flash the ruu its error 99 unknown fail i get it twice
tivofool said:
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Click to expand...
Click to collapse
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
santo_2k said:
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
Click to expand...
Click to collapse
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
rolo143 said:
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I tried Maximus with CWM, did i using sideload and them flash the boot.img file. but it was a disaster as my device didn't connect to wifi and had some call drops then I tried flashing twrp and then sideloaded magicrom 4.0 and flas boot.img, it looks lot better now but only issue right now is my phone keeps on rebooting and am still waiting for a stable rom to be released.
I read MagioRom comments and they say with that ROM phone reboots a lot. So I think the only way is with MaximusHD. The WiFi problem I think it can be fixed. I don't know about the call drops, but many have this ROM as daily use so I guess it's ok. I will try S-off with moonshine method, then try install Maximus. Hope my phone survives.
Sent from my One S using xda app-developers app
I had s-off on my htc one s. When i s-offed my hboot automatically got upgraded to 2.16. I ran a command the changes the secrity flag to s-on but all the software on my htc is for s-off/ Is there a fix besides jtaging
I gues you're stock with hboot 2.16 for now. Just use any Rom that runs on that hboot like magio, maximus or source.
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
I gues you're stock with hboot 2.16 for now. Just use any Rom that runs on that hboot like magio, maximus or source.
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
But i didnt install the original firmware all i did was change the flag from on-off doesnt this mean im still s-off?
cyberusman said:
But i didnt install the original firmware all i did was change the flag from on-off doesnt this mean im still s-off?
Click to expand...
Click to collapse
What do you mean by "original firmware"? You meant you've flashed firmware.zip from maximushd to upgrade for 2.16 and then run the s-on command? If so and you have 2.16, radio 1.20?
Just make sure you haveflashed modded recovery that works with 2.16 firmware, then adb push maximushd rom zip to your sd card, flash from recovery, make sure you fastboot flash boot.img and you're good to go.
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
What do you mean by "original firmware"? You meant you've flashed firmware.zip from maximushd to upgrade for 2.16 and then run the s-on command? If so and you have 2.16, radio 1.20?
Just make sure you haveflashed modded recovery that works with 2.16 firmware, then adb push maximushd rom zip to your sd card, flash from recovery, make sure you fastboot flash boot.img and you're good to go.
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
yes thats what happend
will s-off work with maximusrom?
So you have fully working rom on your phone?
Sent from HTC One S using android 4.2.2 sense 5
cyberusman said:
will s-off work with maximusrom?
Click to expand...
Click to collapse
You got it little bit confused. You need s-OFF for upgrade to 2.16 or for downgrade the firmware back to 2.15. If you got upgraded your phone to 2.16 and then put your phone to s-on then that's it. There may be a way to gain s-OFF again but you just have to try or the guys that brought us facepalm and moonshine need to add support for new 401.xx firmware. You can ask them nicely on IRC (link to their IRC channel is in the OP of their thread) and see what they say/can do.
But for now you're stocked with hboot 2.16 so you can only run roms that use the same partions layout. (maximus, source, magio and I could see some CM 11 builds already as well).
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
You got it little bit confused. You need s-OFF for upgrade to 2.16 or for downgrade the firmware back to 2.15. If you got upgraded your phone to 2.16 and then put your phone to s-on then that's it. There may be a way to gain s-OFF again but you just have to try or the guys that brought us facepalm and moonshine need to add support for new 401.xx firmware. You can ask them nicely on IRC (link to their IRC channel is in the OP of their thread) and see what they say/can do.
But for now you're stocked with hboot 2.16 so you can only run roms that use the same partions layout. (maximus, source, magio and I could see some CM 11 builds already as well).
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
Okay Thank you for the information! Im going to flash the maximus rom tomorow.
EDIT: What is the fastest most stable rom from the list you gave above? Because i want a stock rom that everything works. Any Advice? Thanks in advance
Another EDIT: Will i have to follow the same instuctions that are on the rom forum page, or do i just install the rom and flash the boot?
Dude why are u over complicating everything it's not hard. If you don't understand what your doing you should have never rooted your device a bit stupid to upgrade to 2.16 and then go s-on
Sent from my HTC One S using xda app-developers app
Accountban said:
Dude why are u over complicating everything it's not hard. If you don't understand what your doing you should have never rooted your device a bit stupid to upgrade to 2.16 and then go s-on
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well i do know what im doing. I just want to know if i have to follow the exact instructions, or if i have to just flash the rom and flash boot img
cyberusman said:
Well i do know what im doing. I just want to know if i have to follow the exact instructions, or if i have to just flash the rom and flash boot img
Click to expand...
Click to collapse
Just flash rom and boot.img
Sent from HTC One S using android 4.2.2 sense 5
THANKYOU tominozh, YOUR THE BEST!
Thanks for all the help tominozh, I really appreciate it, best of luck in the future. I will click thank button on all your posts. You are the best person ever! Thank you for all your time and effort
Sincerely, cyberusman
tominozh said:
Just flash rom and boot.img
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
Thanks i flashed the rom. Everything is working. I just turned off my phone now it is boot looping! What do i do?
Instructions are there for a reason follow them idiot all of them end off... If you only needed to use a few steps the developer wouldn't add extra ones
tominozh said:
Just flash rom and boot.img
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
I have successfully installed maximus rom 10.00. The problem is when i power off the phone it boot loops about 2-7 minutes give or take a minute , then it goes android into after boot looping for about 2-7 minutes . So i cant shut off the phone and also how would i fix this whole boot looping problem?. Any ideas?
I was thinking...how about we all devise a list of compatible ROMs for each hboot version?? That way it would lessen the confusion on compatible hboots.. Maybe even a recovery list as well. Any thoughts?
Sent from my One X using Tapatalk
It isn't even the hboot that matters, it's the firmware that the hboot is a part of that matters. You can flash just the hboot all you like and it won't achieve anything without the rest of the firmware.
It'd be a short list anyway; any current aosp ROM requires at least the 3.18 firmware which includes the 2.14 hboot. Any Sense 5 ROM requires at least the 5.08 firmware that includes the 2.15 hboot. Any Sense 4 ROM it doesn't matter.
I'm pretty sure this information is mentioned in my Evita FAQ thread already but I'll double check and revise it if necessary.
Sent from my Evita
OK. Cuz I keep trying to flash ROMs and getting prop boot errors. Lol
Sent from my One X using Tapatalk
The ONLY difference I have ever noticed was the 1.09 hboot and all the others. 1.09 is the only hboot that would allow me to shell restart/hot reboot in stock 4.1.1. If I had any other hboot with stock 4.1.1, it would just get stuck on the boot animation.
But this was the ONLY difference I found.
chrisb906 said:
OK. Cuz I keep trying to flash ROMs and getting prop boot errors. Lol
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
It's pretty simple. If you want to run an aosp ROM you need to at least run the 3.18 RUU. If you want to run a Sense 5 ROM you need to flash the 2.15 firmware. The 2.15 firmware is compatible with both so you may as well just flash that and you're safe either way.
If you've been flashing just hboots you've been doing it wrong and probably have a major mismatch between your firmware and your hboot. Also, if you have a modified hboot (red text removed) it can cause problems.
Sent from my Evita
If you want to run the latest Hboot and firmware with many of the AOSP Roms you basically have two choices:
1. Modify the install script to accept the HBoot version #:
http://forum.xda-developers.com/showthread.php?t=2627309&page=5
2. Downgrade to 2.15 and move back to 2.18 after Rom install:
http://forum.xda-developers.com/showthread.php?t=2517148
then
http://forum.xda-developers.com/showthread.php?t=2651052
You must be SOFF to do any of this!
So far CM 11 supports the new Firmware and Hboot. Any Rom using CM as the base (after they introduced support) will work with no problems.
Absolutely. It remains to be seen whether there's actually any benefit to changing from 2.15 to 2.17 or 2.18 though.
Sent from my Evita
timmaaa said:
Absolutely. It remains to be seen whether there's actually any benefit to changing from 2.15 to 2.17 or 2.18 though.
Sent from my Evita
Click to expand...
Click to collapse
I flashed it after the "reduced" version was released by 24ky. So far I can't tell the difference between them. The only difference I have noticed is a slight bit better signal but it's nothing to write home about and it may only apply to me in my cell coverage area. So I'll stick with it for now.
timmaaa said:
It isn't even the hboot that matters, it's the firmware that the hboot is a part of that matters. You can flash just the hboot all you like and it won't achieve anything without the rest of the firmware.
It'd be a short list anyway; any current aosp ROM requires at least the 3.18 firmware which includes the 2.14 hboot. Any Sense 5 ROM requires at least the 5.08 firmware that includes the 2.15 hboot. Any Sense 4 ROM it doesn't matter.
I'm pretty sure this information is mentioned in my Evita FAQ thread already but I'll double check and revise it if necessary.
Sent from my Evita
Click to expand...
Click to collapse
so a long story short...what is the best firmware to flash almost any rom?
chrisb906 said:
so a long story short...what is the best firmware to flash almost any rom?
Click to expand...
Click to collapse
is this 2.15 on this list somewhere? lol
Edit: I mean the ruu with the 2.15
http://androidruu.com/?developer=Evita
timmaaa said:
It's pretty simple. If you want to run an aosp ROM you need to at least run the 3.18 RUU. If you want to run a Sense 5 ROM you need to flash the 2.15 firmware. The 2.15 firmware is compatible with both so you may as well just flash that and you're safe either way.
If you've been flashing just hboots you've been doing it wrong and probably have a major mismatch between your firmware and your hboot. Also, if you have a modified hboot (red text removed) it can cause problems.
Sent from my Evita
Click to expand...
Click to collapse
What about aokp? I can't flash that with 2.15
Sent from my One X using Tapatalk
chrisb906 said:
is this 2.15 on this list somewhere? lol
http://androidruu.com/?developer=Evita
Click to expand...
Click to collapse
Lol, this dead horse refuses to go away. There's literally nothing left to beat....
It's this simple really:
Sense based Roms 4.2.2 and higher = 2.15 (for now) You can try 2.17 or 2.18...who knows. I haven't seen any reports yet.
AOSP based Roms 4.2.2 and higher = 2.14 (unless the Rom's updater script is modified to allow higher, in which case it really doesn't make much of a difference.)
Should you want to go with an AOSP Rom with a higher firmware and Hboot and the Rom's updater script hasn't been updated see my post above.^^
Make sense?
Yea..fully. Lol
Sent from my One X using Tapatalk
Just asking cuz I couldn't flash any aokp Roms. That's all
Sent from my One X using Tapatalk
And I did do the hboot 2.15 on the resurrected pandasa op. Haha
Sent from my One X using Tapatalk
I've flashed both AOKP and AICP with the 2.15 firmware installed. Anyway, like madcat said, kinda beating a dead horse here now, it should be simple.
Sent from my Evita
Yea. It is simple. I know this..but I still can't flash the aokp ROMs..even with appropriate versions. Just saying
Sent from my Desire HD using Tapatalk
I think that's because you've messed something up in flashing all these things without really knowing what you're doing.
Run the 3.18 RUU, flash the modified version of TWRP 2.6.3.0 or the new official TWRP 2.7, and flash the ROM. Do nothing but those. Report back.
Sent from my Evita
OK. But to let u know I ran 3.18 ruu then flashed 2.15 hboot.. Was that a bad idea?
Sent from my Desire HD using Tapatalk
If you flashed just the hboot, yes it was a bad idea. Like I said earlier in the thread, flashing just the hboot achieves nothing.
Sent from my Evita