Hi, my AT&T HTC One X is running CM10.2 with S-ON. However, on boot, sometimes the device puts itself into a boot loop. You then need to reflash the boot.img from the computer to the phone. Is there any way I can stop this? Thanks.
Nope, not with your current setup. If you're s-on you need to flash the boot.img with fastboot every time you flash a ROM. Don't even bother trying to boot into a ROM after flashing it without first flashing the boot.img via fastboot. If it has booted sometimes without flashing the boot.img, it's because the boot.img that was left over from the previous ROM is somewhat compatible with the new ROM you flashed, this is not optimal of course. If you don't want to have to flash the boot.img anymore, get s-off. Having s-off removes the restriction that causes the boot.img to not be flashed in TWRP when flashing the ROM.
Sent from my Evita
timmaaa said:
Nope, not with your current setup. If you're s-on you need to flash the boot.img with fastboot every time you flash a ROM. Don't even bother trying to boot into a ROM after flashing it without first flashing the boot.img via fastboot. If it has booted sometimes without flashing the boot.img, it's because the boot.img that was left over from the previous ROM is somewhat compatible with the new ROM you flashed, this is not optimal of course. If you don't want to have to flash the boot.img anymore, get s-off. Having s-off removes the restriction that causes the boot.img to not be flashed in TWRP when flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
You misunderstood me. I did flash boot.img and I'm still having boot loops.
Sent from my SGH-I337 using Tapatalk
Have you read the cm10.2 thread? There have been major problems with getting that ROM to boot recently.
Sent from my Evita
timmaaa said:
Have you read the cm10.2 thread? There have been major problems with getting that ROM to boot recently.
Sent from my Evita
Click to expand...
Click to collapse
Where is the CM10.2 thread?
Sent from my SGH-I337 using Tapatalk
Really? It's in the development section. If you don't even know where the thread is I think I can pretty safely assume you haven't read it. If you're having problems with a ROM please read the ROM thread before cluttering up the forum with an unnecessary new thread. To be honest, recovering from a bootloop is about as simple as it gets, you should know how to do that before beginning to flash ROMs.
Sent from my Evita
Related
Installing MIUI rom from here http://forum.xda-developers.com/showthread.php?t=2034030
JB 3.1.25,
- wiped cache/dalvik cache
- wiped data/factory reset
Stuck on boot animation, wont boot..waited for 30 min and still..
Coming from ViperXL, S-ON
Any solutions? Anyone experienced?
doc_v15 said:
Installing MIUI rom from here http://forum.xda-developers.com/showthread.php?t=2034030
JB 3.1.25,
- wiped cache/dalvik cache
- wiped data/factory reset
Stuck on boot animation, wont boot..waited for 30 min and still..
Coming from ViperXL, S-ON
Any solutions? Anyone experienced?
Click to expand...
Click to collapse
I think it not work with JB 4.1.2
Metoo
Did you fastboot flash the boot.img
Sent from my HTC One X using Tapatalk 2
jerrycoffman45 said:
Did you fastboot flash the boot.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
No I did not..It said in the instructions and also i read it somewhere that we dont need to flash the boot.img
Do I have too?
Problem solved, flashed boot.img
If you are s-on you do if your hboot is 1.14 or higher s-off fixs that and it is easy to do
Sent from my HTC One X using Tapatalk 2
doc_v15 said:
No I did not..It said in the instructions and also i read it somewhere that we dont need to flash the boot.img
Click to expand...
Click to collapse
I know you got it booted. But just to clarify:
Maybe I'm missing it, but I don't see in the MIUI instructions where it says you don't need to flash boot.img seperately. It makes no mention of boot.img either way, which is not the same as it saying its not needed.
If you are hboot 1.14 or higher, and S-on, you should assume that you need to flash boot.img separately with fastboot, unless the instructions explicitly say otherwise.
AFAIK, ViperXL is the only current ROM that will flash boot.img in AROMA (plus older builds of CleanROM, but not the current CR6). Even with ViperXL, it doesn't work for everyone, and some folks have had to flash it from fastboot.
redpoint73 said:
I know you got it booted. But just to clarify:
Maybe I'm missing it, but I don't see in the MIUI instructions where it says you don't need to flash boot.img seperately. It makes no mention of boot.img either way, which is not the same as it saying its not needed.
If you are hboot 1.14 or higher, and S-on, you should assume that you need to flash boot.img separately with fastboot, unless the instructions explicitly say otherwise.
AFAIK, ViperXL is the only current ROM that will flash boot.img in AROMA (plus older builds of CleanROM, but not the current CR6). Even with ViperXL, it doesn't work for everyone, and some folks have had to flash it from fastboot.
Click to expand...
Click to collapse
Thanks, It was not mention on the instructions, but there was people who asked in the thread whether they need to flash boot.img for the rom, it was answered no . So i was assuming.
But then, it worked right away after I flashed the boot.img
Thanks again
Sent from my One X
Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.
I got s-off with viper
Sent from my VENOMized HoxL
area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.
Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP
The colors are all messed up as well when i boot in and its not just this rom but cyanogen mod as well but whats odd is if i use older versions of both cyanogen and this everything is fine its just versions that are from oct 15ish and later.
Are you using a custom kernel? What are your bootloader details?
Sent from my Evita
timmaaa said:
Are you using a custom kernel? What are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
Evita Put Ship S-On rl
Hboot-2.14.0000
Radio-0,24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC- boot
Im pretty sure im on the stock kernel
Ok, are you flashing the boot.img with fastboot each time you change ROMs?
Sent from my Evita
timmaaa said:
Ok, are you flashing the boot.img with fastboot each time you change ROMs?
Sent from my Evita
Click to expand...
Click to collapse
No i haven't't i have just been flashing them but the rom still works its just the colors are all messed up.
XSoloDolo said:
No i haven't't i have just been flashing them but the rom still works its just the colors are all messed up.
Click to expand...
Click to collapse
You need to extract boot.img and flash it manually in fastboot every time you flash a new ROM. What you are experiencing is likely due to a kernel mismatched with the ROM.
Sometimes a kernal mismatch will result in the ROM not booting. Other times, it causes random bugs like this.
redpoint73 said:
You need to extract boot.img and flash it manually in fastboot every time you flash a new ROM. What you are experiencing is likely due to a kernel mismatched with the ROM.
Sometimes a kernal mismatch will result in the ROM not booting. Other times, it causes random bugs like this.
Click to expand...
Click to collapse
Wow that worked thanks man! I should have thought of that earlier too.
As Redpoint said, you need to extract the boot.img and flash it each time you change ROMs. The reason you were having problems was because you still had the boot.img from a previous ROM installed. It turns out that it was kinda compatible (letting the ROM boot), but kinda incompatible (strange visual glitches). If you get s-off you don't have to worry about flashing the boot.img manually anymore.
Sent from my Evita
Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk
alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk
I was helping my friend switch to a custom rom and I messed up. His One XL was on 4.1.1 with 3.18 software. I managed to temporarily change the CID by followin guides and unlock the bootloader using htcdev.com. The problem began after I tried to flash boot.img, from an One X rom because I thought this is a One X(ATT's naming). Now the device is stuck in a recovery boot loop. Once in a while I can get out of it and get to the bootloader. From there I'd erase cache, flash new recovery (TWRP for One XL), flash correct boot.img, go into recovery and flash rom. However, upon finishing install the reboot will start the recovery boot loop again. The phone keeps trying to boot recovery instead of normal boot on restart and gets stuck. I've tried both CWM and TWRP, wiped many times, but it refuses to boot normally. Every time after the logos for the rom plays the phone reboots. Unlocked bootloader but no root or S-off. What can I do?
Thanks
What ROM are you tying to flash? And are you sure you're flashing the boot.img from that ROM zip?
Out of interest, is there a reason your friend isn't doing this himself? Handing an unlocked phone to someone who hasn't undergone the learning experience of actually unlocking the device and researching the ins and outs of a modified phone is a pretty terrible idea.
Sent from my Evita
Wouldn't it be advisable if he formatted and ran a ruu? Sounds like he messded up his bootloader with a incompatible ROM.
Sent from my Desire HD using Tapatalk
He can't run an RUU. The fact that he flashed a boot.img would suggest that he's s-on, he mentioned changing the CID which suggests that he has SuperCID. S-on + SuperCID + jb RUU = brick.
Sent from my Evita
Uh oh. Nothing can be done....?
?
Sent from my Desire HD using Tapatalk