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
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
Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.
It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app
Thanks. Is there any way to update the software?
Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc
With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app
exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One
ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb
Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb
Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't
AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.
alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app
exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium
Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app
Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium
31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.
So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?
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