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
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
xatomicx said:
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
Click to expand...
Click to collapse
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
31ken31 said:
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
xatomicx said:
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
Click to expand...
Click to collapse
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
31ken31 said:
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
xatomicx said:
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
Click to expand...
Click to collapse
Did you verify the md5 of the downloads? Could be a corrupted file
Sent from my HTC One XL using xda premium
timmaaa said:
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
Click to expand...
Click to collapse
Yes i am
I tried Cyanogen, just for fun of trying another room, i get the same boot freeze as with Sense 5
I don't know why it's looping, it shouldn't be if you're following the correct procedure. Are you doing a full wipe, then flashing the ROM, and then flashing the boot.img from that ROM in fastboot?
Sent from my Evita
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
31ken31 said:
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
So you're wiping system/factory reset/cache/dalvik cache? Then flashing ROM, then rebooting to bootloader and flashing boot.img?
Sent from my Evita
xatomicx said:
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
31ken31 said:
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, i am always flashing the boot included in roms, but somehow my bootloader always show 2.14 after flashing ... that might be why i cant get it to work
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
timmaaa said:
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Well anyone knows what's the solution? flashing the embedded boot.img did not help.
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
timmaaa said:
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
Click to expand...
Click to collapse
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
xatomicx said:
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
Click to expand...
Click to collapse
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
31ken31 said:
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i tried nightly 10.1
And sense 5 3.6,
i am now on sense 5 3.6, flash the 3 first, then 3.6 and 3.6.1
ill see for your "scott's clean rom", never heard of it, will try.
Hi all, I've been at this for a few hours now, trying to find a solution but I've come up with nothing.
Right now I am stuck in a boot loop after I've successfully gotten S-off on my device. I can enter bootloader and recovery (TWRP) just fine. I'd been running CM 10.0.0 prior to this and I've tried the whole shebang with reflashing my ROM and also flashing boot.img through fastboot. Nothing seems to be working and I can't seem to find the reason why. I just need to get my phone working again.
Thank you for your assistance.
Please provide more details. Post the first five lines of your bootloader screen. Also post which ROM you flashed.
Sent from my Evita
timmaaa said:
Please provide more details. Post the first five lines of your bootloader screen. Also post which ROM you flashed.
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
I've attempted flashing CM 10.0.0 as well as 10.1.3 to no avail.
Where are you downloading the ROMs? And what recovery version are you on?
Sent from my Evita
download.cyanogenmod.org/?device=evita
And I am using TWRP v2.3.1.0
It seems like you're doing everything correctly. Now that you have s-off you don't need to flash the boot.img with fastboot anymore though. Maybe try without doing that, I don't think that's what the problem is though. Also try flashing a different ROM maybe.
Sent from my Evita
lyendsc 259
Right, I've tried with and without flashing boot.img multiple times, clearing caches/doing a factory reset before each time, I'm at a loss right now. I'll try another ROM, but if that doesn't work, what would you suggest I do?
Ruu reflash twrp reflashing rom. Check md5 of everything.
Sent from my HTC One XL using xda app-developers app
exad said:
Ruu reflash twrp reflashing rom. Check md5 of everything.
Click to expand...
Click to collapse
Will do these after I try flashing another ROM.
Your md5 matches on the downloads right?
Sent from my Evita
timmaaa said:
Your md5 matches on the downloads right?
Click to expand...
Click to collapse
I haven't been forcing an MD5 check, should I be?
Update, I've successfully flashed ViperXL 4.0.0 and I can now use my phone, thank you for the replies
You should ALWAYS do a manual md5 check using an md5 app/program on anything you intend to flash. The md5 for the file is listed on the download page, then you use the app to make sure it matches the md5 of the downloaded file. This ensures that the file isn't corrupted.
Sent from my Evita
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
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