ICS ROM won't boot - HTC Desire S

I just try to flash ICS MIUI Rom, but I stay frozen on HTC logo.
is it a problem with Hboot version (I recently updated it to 7.00.1002)
Is there something else to update before to flash this ROM?
Thanks for your help
M.

Did you S-Off your phone with HTC-Dev? If so then have you flashed you boot.img?

SimonTS said:
Did you S-Off your phone with HTC-Dev? If so then have you flashed you boot.img?
Click to expand...
Click to collapse
No, S-OFF has been done with Revolutionnary.

Hang on a minute. Which version of MIUI are you trying?
If you're trying the latest (.27) then it won't ever work - read the thread and you'll see that the build was bad. Run .13 and it is fine - I use it as my daily.

Try a different build! If it doesn't work report back!
Sent from my Nexus 7 running Froyo.

Some ICS roms won't work correctly with the revolutionary HBOOT. Read some guides about how to upgrade your boot and try it, always understanding what are you doing to avoid a horrible brick. In my case it works with reingeniered Hboot that is relocked.

Related

which stable ICS rom

Hi guys,
After a lot of effort i managed to:
unlock bootloader
install CW 5
root the device
Now i need a reccomendation for an ICS or JB rom.
I need everything completely stable, that is highest priority, and after that comes the speed.
Please advise also about which kernel if i do need to change it?
I'm currently on GB.
I want to upgrade only with install zip from sd card if possible, from CW5 or whichever.
THANKS!
If you want an ics rom you will have to update your firmware to ics firmware which is 3.33 or 3.32.I believe you must be s off in order to do this. If your on gb right now to load any ics rom firmware must be updated.then once your ready I recommend to try out several roms for yourself and see which meets your needs best. Depending on your Rom, different kernels can be tired with the different roms. I'm running paranoid Android by Dragun Korr, it's jelly bean. My kernel is 3.0 51 by Dragun. I really love this rom. It's smooth fast and stable. However I suggest you try out several because everyone is different and has different opinions. It's always best to try for yourself and make your own conclusion. Hope this is helpful. Best wishes. Remember to do your nandroid backup before flashing so you can return to your old rom if need be. As long as firmware matches.
Have fun and experiment. I also recommend 4ext recovery. Some roms require it. And it's really a great recovery!
Sent from my HTC Sensation
thanks a lot, i will try paranoid
can you please tell me how to upgrade to firmware 3.3? can i do it now while i'm still on GB?
Astral07 said:
thanks a lot, i will try paranoid
can you please tell me how to upgrade to firmware 3.3? can i do it now while i'm still on GB?
Click to expand...
Click to collapse
see here http://forum.xda-developers.com/showthread.php?t=1459767
i suggest you first flash 3.32fw then 3.33fw
but you must be S-OFF in order to ugrade your fw version
hm, when i tried to flash 3.33 i got installation aborted
didn't i s-off when i unlocked the bootloader? is it a different thing?
Astral07 said:
hm, when i tried to flash 3.33 i got installation aborted
didn't i s-off when i unlocked the bootloader? is it a different thing?
Click to expand...
Click to collapse
yes it is different
edit:i saw that you are still in GB rom, that means it cames with 1.17-1.18 hboot version
you can S-OFF with this method http://revolutionary.io/
yes, it was 1.18
i did it now and when it asked me to install recovery, i skipped it since i already have it, i hope that is ok
gonna try to flash RUU now
Astral07 said:
yes, it was 1.18
i did it now and when it asked me to install recovery, i skipped it since i already have it, i hope that is ok
gonna try to flash RUU now
Click to expand...
Click to collapse
flash ruu for what reason?
what is your hboot version now?
did you achieve S-OFF?
i ment flash firmware
1.7 hboot
it looked like s-off was good, how can i check?
again i got installation aborted for firmware
Astral07 said:
i ment flash firmware
1.7 hboot
it looked like s-off was good, how can i check?
again i got installation aborted for firmware
Click to expand...
Click to collapse
ok then
switch off your device
remove battery
insert it again
then hold power button and volume down together until it shows you the bootloader screen
in the top of the screen it will say S-OFF
now to upgrade firmware just follow the instructions in the link that i provided you
at the top it says PYRAMID PVT SHIP S-OFF RL
i went into recovery again and tried with the 3.32 as suggested and again, installation aborted, what am i doing wrong?
by the way, i really appreciate the support, it's a lot easier with this kind of help, and i work as a support member for other stuff so i know how it is..
Astral07 said:
at the top it says PYRAMID PVT SHIP S-OFF RL
i went into recovery again and tried with the 3.32 as suggested and again, installation aborted, what am i doing wrong?
by the way, i really appreciate the support, it's a lot easier with this kind of help, and i work as a support member for other stuff so i know how it is..
Click to expand...
Click to collapse
that is your mistake.see the bold one as marked
upgrading the firmware version it can be done only via bootloader
it is not like roms or kernels.
see again the steps in the link on how to upgrade the firmware.you missed something
and yes you are S-OFF
yeah, it should find the new zip automatically, the problem is that i didn't get that
but you are correct, i tried again and now it worked!
installing new ROM now, finally
hopefully that will go without problems
thanks again
Hi also 4ext recovery is recommended. You can get download on xda or play store. It's really a great recovery and almost all use it. Its very easy to use and I believe some roms require it. You can download after installation of rom. If you have issues with download try 4ext. You won't be sorry. It's a great recovery
Sent from my HTC Sensation
thanks,
yes i've been using it since the first guy responded i should try 4ext
not bad, i admit
Hi there.
I strongly suggest Android Revolution HD. I've been using it now for almost 2 weeks and its rock solid.
Its very smooth with decent battery life and you get some sick mods for it!
There is a link to the ROM in my signature.

[Solved] Soft Brick - Disaster after flashing firmware.zip

Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
S-OFF
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip
4. fastboot reboot
Click to expand...
Click to collapse
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Solved signal issue by disabling fast dormancy lol !
vatsaman said:
Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Someone please help me!
Click to expand...
Click to collapse
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.
mjsheldon4 said:
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.
Click to expand...
Click to collapse
Thanks a ton for the help!!
What Hboot does the latest Tmob JB RUU contain ?? And why lower hboot in specific ?
Any particular reason ??
The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium
Love you bro!! :good::laugh:
My baby is up now.. And I'll stay on stock for quite a few days!! Hufff..
mjsheldon4 said:
The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Can I download the OTA update and apply it on SuperCID ??
Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium
mjsheldon4 said:
Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks a lot! But I still have problems regarding signal reception. Any fix ??
That's where the lower HBoot comes into play. You are still able to flash a different radio. In the dev thread is the new 1.15 radio. Works great.
Sent from my Xoom using xda premium
vatsaman said:
Can I download the OTA update and apply it on SuperCID ??
Click to expand...
Click to collapse
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me
This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium
Yeah!! Revived to phone back completely to normal! Thanks a ton for your helo folks.
ryanshew said:
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me
Click to expand...
Click to collapse
Thank god I din't go for it :good: :laugh:
mjsheldon4 said:
This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I have random signal drops now :crying:
vatsaman said:
I have random signal drops now :crying:
Click to expand...
Click to collapse
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.
real187 said:
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.
Click to expand...
Click to collapse
I did the RUU later.. yet to progress
vatsaman said:
I did the RUU later.. yet to progress
Click to expand...
Click to collapse
So you still stuck then?
Verstuurd van mijn One S met Tapatalk
real187 said:
So you still stuck then?
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
I'm not stuck. Everything is fine except that random signal loosing thing.
vatsaman said:
I'm not stuck. Everything is fine except that random signal loosing thing.
Click to expand...
Click to collapse
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?
real187 said:
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?
Click to expand...
Click to collapse
Yes.

Most Roms Boot Loop - How to correct?

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.

How to obtain s-off for One S(S4) Hboot 2.15

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

[Q] Rogers HTC One X ISSUES

Hey guys,
I have been looking everywhere and I know there are tonnes of threads on this but I cannot seem to find anything that will work for me.
Here is my dilemma:
My current Rogers HTC One X is on a PACMAN ROM, the last few days it has been awful. Several bootloops and it will not stay on. My current setup is this:
Unlocked
S-off
HBOOT - 2.14
Radio - 0.23a.32.09.29
I feel that the issue is maybe I need to be using firmware 3.18 and HBOOT 2.15, but for the life of me cannot find anything for Rogers to get me to this point.
Like I said, I am sure there are hundreds of threads but I have looked and cannot seem to find what I am looking for.
I am wondering if i should go to stock and start over....if so, I hear that I cna use the AT&T RUU....again, whatever info or direction that anybody can point me will be greatly appreciated.
Have you tried clean flashing the ROM again? Have you tried flashing another ROM? You show that you have the 2.14 hboot but then mention you have the 2.15 hboot, which one is it?
Sent from my Evita
timmaaa said:
Have you tried clean flashing the ROM again? Have you tried flashing another ROM? You show that you have the 2.14 hboot but then mention you have the 2.15 hboot, which one is it?
Sent from my Evita
Click to expand...
Click to collapse
I have 2.14, I cleaned flashed with the Beanstalk ROM, seems to be ok, a couple of freezes and reboots still.
I've experienced the same issues with Beanstalk, try flashing the Torched kernel and those issues should stop.
Sent from my Evita
uyndot different
timmaaa said:
I've experienced the same issues with Beanstalk, try flashing the Torched kernel and those issues should stop.
Sent from my Evita
Click to expand...
Click to collapse
I flashed the kernel, everything was working ok for a bit.
I rebooted the phone and it stuck at the Beanstalk flash screen, so I had to reflash everything again. Started to reinstall everything and it did it again. So my phone is now stuck at the Beanstalk flash screen.
I updated the ROM to 10/27 as well.
I would like to flash it back to stock and start over but cannot find the stock RUU for Rogers, I have looked but everything seems to be AT&T RUU's.
http://androidruu.com
Sent from my Evita
Perfect
So i will download the stock firmware and the 2 OTAs
Flash back to stock, will I need to flash the OTAs or will they just automaticlaly download once I am back to stock. I did this once before but cannot remember??
I know there is a link on this site showing how to flash back to stock, I use to have it as a favorite but I formatted the pc, so i dont have it any longer. Would you happen to have a link??
Hate to bug you for this, just want to get my phone back up and running.
Thanks for all you help
You can try using the "search for updates" tool in settings, it may or may not work. I don't have a link but there really isn't much to using an RUU, just connect your phone in fastboot mode and start the exe program in Windows. Make sure no other programs are running and make sure screen saver / hibernation is turned off. Follow the prompts once the program has initiated and that's it.
Sent from my Evita
timmaaa said:
You can try using the "search for updates" tool in settings, it may or may not work. I don't have a link but there really isn't much to using an RUU, just connect your phone in fastboot mode and start the exe program in Windows. Make sure no other programs are running and make sure screen saver / hibernation is turned off. Follow the prompts once the program has initiated and that's it.
Sent from my Evita
Click to expand...
Click to collapse
Awesome.....for some reason i thought there were a bunch of fastboot commands that had to be done for RUUing. If the phone doesnt automaticlaly find the OTAs, then i can do each one separately the same way as the stock firmware.
If it doesn't find the OTA's and install them automatically, you can install them manually through the stock recovery.
Sent from my Evita
timmaaa said:
If it doesn't find the OTA's and install them automatically, you can install them manually through the stock recovery.
Sent from my Evita
Click to expand...
Click to collapse
Alright, was able to flash back to stock and then it automatically updated the OTAs
I am now back at firmware 3.17.631.2(4.1.1), hboot 2.14, with s-off
Everyone is taking about being on 3.18 and hboot 2.15, does that make a big diference?
I havent reflashed my ROM yet....will also flash the kernel at the same time
anything else i should do before i flash my ROM
mikeyb1974 said:
Alright, was able to flash back to stock and then it automatically updated the OTAs
I am now back at firmware 3.17.631.2(4.1.1), hboot 2.14, with s-off
Everyone is taking about being on 3.18 and hboot 2.15, does that make a big diference?
I havent reflashed my ROM yet....will also flash the kernel at the same time
anything else i should do before i flash my ROM
Click to expand...
Click to collapse
Flashing 2.15 is only really suggested for sense 5 4.2 roms as it will eliminate any issues you might run into. While its often ok to flash both rom and kernel at the same time I always push for a full boot after a rom flash before flashing something else and factory reset prior to flashing the kernel.
3.18 software vs 3.17 is just carrier related and makes no difference.
exad said:
Flashing 2.15 is only really suggested for sense 5 4.2 roms as it will eliminate any issues you might run into. While its often ok to flash both rom and kernel at the same time I always push for a full boot after a rom flash before flashing something else and factory reset prior to flashing the kernel.
3.18 software vs 3.17 is just carrier related and makes no difference.
Click to expand...
Click to collapse
Good to know, i havent used any sense 5 ROMS, been using PACMAN, Beanstalk, ones like that
Since I am on Rogers, is there even a way to get to 3.18, would it have to be a different carriers firmware to get there??
mikeyb1974 said:
Good to know, i havent used any sense 5 ROMS, been using PACMAN, Beanstalk, ones like that
Since I am on Rogers, is there even a way to get to 3.18, would it have to be a different carriers firmware to get there??
Click to expand...
Click to collapse
The 2.14 firmwares are practically identical except the radio firmwares theres really no point but you could run an at&t ruu if you wanted. 3.18 is the software version which will be overwritten when you flash a new rom anyway so its beyond pointless.

Categories

Resources