Related
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Someone more knowledgeable than myself can give you step by step instructions to get you out of this pinch. But in the mean time read the link I posted about flashing with s on. It will help in the future. Best wishes not to worry I'm sure you can fix this.
Sent from my HTC Sensation using xda premium
daz1uk said:
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Click to expand...
Click to collapse
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
realsis said:
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Yes it should
Also some roms require 4ext it's a super easy touch recovery to use. You can download from here or the playstore.
Sent from my HTC Sensation using xda premium
Skipjacks said:
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
Click to expand...
Click to collapse
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
It is universal 3.33 let me get link also 3.32 will work on most ics roms but 3.33 is the newest I'm running jelly bean and use 3.33
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation using xda premium
daz1uk said:
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Click to expand...
Click to collapse
If you are s-off you shouldn't have to flash boot.img separately. It will do all that with the ROM flash.
Maybe that's what's screwy. Though a borked up ROM still shouldn't affect SD card mounting in recovery...that is really weird. Do you have a card reader that you can use to check the card out in your computer? I'm wondering if somehow you screwed up the card when flashing the ROM. Maybe it wont' mount because the card isn't formatted properly anymore. Stuff like that has happened before.
daz1uk said:
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
Click to expand...
Click to collapse
Hi,
What does your bootloader say?
hboot etc.
Yes if your s off you simply flash from recovery without boot img. But do update your firmware.
Sent from my HTC Sensation using xda premium
malybru said:
Hi,
What does your bootloader say?
hboot etc.
Click to expand...
Click to collapse
Bootloader says:
S-ON
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
daz1uk said:
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
Click to expand...
Click to collapse
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
malybru said:
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
Click to expand...
Click to collapse
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
Click to expand...
Click to collapse
Hi,
It is a pity you went to HTC to unlock your phone.
I wonder if you can still s-off using revolutionary.
You are going to need to run a RUU,and hopefully get a working phone again.
Try and find a RUU HERE that matches your area and carrier.
daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
Click to expand...
Click to collapse
Yup. If you have the 1.18 hboot you have Gingerbread firmware, which won't support Jellybean or ICS.
The good news is that you can flash a gingerbread rom and get the phone back to a working state right away if you need to get the phone back to the owner.
The RUU to restore is pretty simple. Then Revolutionary s-off proceedure is also extremely painless.
Reverting back to stock and starting over to s-off shouldn't take more than 15 minutes if you do it right. Then flashing the ICS/GB firmware (3.32 or 3.33) takes 3 minutes. Then the new rom takes 3 more minutes.
Just make sure you RUU to gingerbread and not to ICS. The ICS Hboots are harder to s-off. It's worth adding the extra step to flash the ICS/JB firmware later.
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Hi,
Are you Sensation,or Sensation XE?
daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Doh, my fault forgot to re-lock it, update is installing as I type, phew!
Sent from my HTC One X using Tapatalk 2
Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM
RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.
If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9
subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729
absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware
absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.
jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.
^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1
I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!
you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?
So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD
Does this hboot have any flashing restrictions like hboot 1.14?
Tmobile HTC One™ S
fmedrano1977 said:
Does this hboot have any flashing restrictions like hboot 1.14?
Tmobile HTC One™ S
Click to expand...
Click to collapse
Ya thay the same, only 1.06 and 1.09 are the good ones.
Do any off EU ruu's have 1.06 or 1.09
Tmobile HTC One™ S
You can't downgrade hboot with ruu..
Sent from my HTC One S using xda premium
Not trying to downgrade, I've done that already, currently on 1.09. Trying to rid myself of T-Mobile US firmware, tired of the signal drops that sometimes require reboot to reaquire. Didn't have that symptom while I was on HBOOT 1.14.0002
Tmobile HTC One™ S
fmedrano1977 said:
Not trying to downgrade, I've done that already, currently on 1.09. Trying to rid myself of T-Mobile US firmware, tired of the signal drops that sometimes require reboot to reaquire. Didn't have that symptom while I was on HBOOT 1.14.0002
Tmobile HTC One™ S
Click to expand...
Click to collapse
Have you tried flashing radios?
Darknites said:
Have you tried flashing radios?
Click to expand...
Click to collapse
Two latest, same story
Tmobile HTC One™ S
fmedrano1977 said:
Two latest, same story
Tmobile HTC One™ S
Click to expand...
Click to collapse
Hmm not sure why the Hboot would mess with that. Did you try 1.06 Hboot?
Ok well im on HBOOT 1.14. How do i get to one of the good ones/ Ones that wont give me any problems. Also Do I HAVE to upgrade my radio. Because its at 1.11t. I honestly really need help
tjsinghlion said:
Ok well im on HBOOT 1.14. How do i get to one of the good ones/ Ones that wont give me any problems. Also Do I HAVE to upgrade my radio. Because its at 1.11t. I honestly really need help
Click to expand...
Click to collapse
You have to downgrade the Hboot here.
please help
Darknites said:
You have to downgrade the Hboot here.
Click to expand...
Click to collapse
So is there any other way to get My Hboot downgraded easier. Also What is the restrictions on 1.14. Can i still download and flash roms with 1.14. I know i have alot of questions but i just really want to be safe
tjsinghlion said:
So is there any other way to get My Hboot downgraded easier. Also What is the restrictions on 1.14. Can i still download and flash roms with 1.14. I know i have alot of questions but i just really want to be safe
Click to expand...
Click to collapse
You can flash roms but you have to flash boot.img separately either with fastboot while in bootloader or with app called flash image GUI just befor you flash Rom. You can also change radio using Temporary radio instaler. The only problem for you could be the WiFi not working on sertain roms. But that does not happen to everybody.
Sent from my HTC One S using xda app-developers app
Wait so all I have to do is that flash boot boot.IMG process before I flash a Rom. And do I use the app while on my stock Rom . And when do I use boot.IMG processes
Sorry I just did a little research and answered my own question. Oh and is temporary radio installer an app or what
Sent from my HTC VLE_U using xda app-developers app
Yes look for Flash Image GUI App. You can flash boot.img before rebooting to recovery. Just open app, browse for your Rom, select it, wait until the app extract the boot.img, select flash boot.img, wait, the you'll get a toast message succesfull, then press reboot recovery, wipe everything a few times, flash Rom, wipe cache and dalvik cache again, reboot system.
The temporary radio installer its a zip, you can flash it in custom recovery if you need to change radio.
I also recommend to get a wiping script from ..Awesome.. ( its in devepomnent forum as well) its a zip file, flash from recovery, it will "full wipe your phone" .
I find it better then wiping in twrp recovery.
Good luck.
Sent from my HTC One S using xda app-developers app
tominozh said:
Yes look for Flash Image GUI App. You can flash boot.img before rebooting to recovery. Just open app, browse for your Rom, select it, wait until the app extract the boot.img, select flash boot.img, wait, the you'll get a toast message succesfull, then press reboot recovery, wipe everything a few times, flash Rom, wipe cache and dalvik cache again, reboot system.
The temporary radio installer its a zip, you can flash it in custom recovery if you need to change radio.
I also recommend to get a wiping script from ..Awesome.. ( its in devepomnent forum as well) its a zip file, flash from recovery, it will "full wipe your phone" .
I find it better then wiping in twrp recovery.
Good luck.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
No need for the script. You only need to factory reset and wipe system in TWRP which formats it and not delete it.
Yes, no need, but wiping in twrp did not work for me sometime so if I change roms, I run script as well. If twrp would work 100% no need to do it 2 - 3 times isn't?
Sent from my HTC One S using xda app-developers app
tominozh said:
Yes, no need, but wiping in twrp did not work for me sometime so if I change roms, I run script as well. If twrp would work 100% no need to do it 2 - 3 times isn't?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
TWRP has always worked for me and had no issues but ya wiping more then once is even more of wasted time.
Sent from my HTC One S using Tapatalk 2
TWRP has always worked for me as well. CWM has also always worked for me (on my other devices).
The only thing I wipe more than once is cache and dalvik-cache (before and after rom installation, a total of 2 times wasting ~5sec or so), and I've never had any issue, on ANY of my devices (I have access to an Xperia P in addition to the ones listed in my sign., and Ive helped a couple of friends with flashing/rooting/etc as well)
I have been searching ALL day and can't find it I have hboot 1.14 on my new replacement One S, and I desperately need to update the radio. My room is an absolute dungeon with service, but my wife's T989 works great, so it's my stupid phone not Tmobile.
I have S-OFF with 1.14HBOOT, superCID 11111111
How can I downgrade to 1.09? When I search it, I can only find for the One X/XL
theratdude64 said:
I have S-OFF with 1.14HBOOT, superCID 11111111
How can I downgrade to 1.09? When I search it, I can only find for the One X/XL
Click to expand...
Click to collapse
If you're S-Off, you can flash radios on any hboot. If you want to change your hboot anyway, you can extract an image from a RUU or OTA and dd it into mmcblk0p12. (Be careful with that.)
Find recovery-flashable radios here: http://forum.xda-developers.com/showthread.php?t=1998270
Find recovery-flashable hboots here: http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Hi everyone,
I don't quite have 10 posts yet, so I can't post in the UrDroid thread.
I had UrDroid 1.8, and it worked just fine, had some wifi issues (sometimes after turning the wifi off, it wouldn't turn on again unless I rebooted), so I upgraded to 1.9
Now I have a few issues:
It stays "connected" to a wifi network even after losing connection
Occasionally, after rebooting, my Beautiful Widgets go away and my default keyboard reverts to the stock keyboard (from swype)
occasionally I cannot turn the wifi back on after turning it off without a reboot
That's about it. If anyone has any ideas, please let me know. Thanks! :good:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
I really wish I could try other roms, for some reason UrDroid is the only one that actually works, I have no idea why this is!
For instance, when flashing any verison of CM, after flashing and rebooting, it stays stuck on the loading screen, and doesn't go further, even after waiting a half an hour. AOKP and the others basically brick my phone. I think it has something to do with the UrDroid using Aroma Installer that seems to work well with my phone and twrp. I'm a bit of a n00b, so don't know for sure.
Was hoping someone else had these issues and could tell me how they fixed them.
Herc08 said:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
exad said:
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
choeffe said:
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
Click to expand...
Click to collapse
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
exad said:
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
Click to expand...
Click to collapse
choeffe said:
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
Click to expand...
Click to collapse
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
choeffe said:
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
Click to expand...
Click to collapse
Yes
choeffe said:
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
Click to expand...
Click to collapse
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Thanks for your help thus far! I'm going to give it a try and see how it goes.
Yeah, I definitely wish I would have started with a Nexus or Sony device, but I changed from T-Mobile (worse decision of my life to go with them in the first place) to Straight Talk SIM with AT&T, and the HTC One X looked so pretty! Next phone is going to be a Nexus!
exad said:
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
Yes
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
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