Reboot and Bootloop (CM10) - HTC One X

Hey all,
I really hope I'm posting this in the right forums, and I did do a google search/xda search prior to this, but I unfortunately did not find anything relevant to my situation.
Anywho, I flashed CM10 on to my phone but ended up in a bootloop. Coming from the S3 and never before using an HTC, I did do the mistake of not flashing the boot.img included with the zip through fastboot initially. After realizing what I forgot to do, I did it and ta-da! It works now and seems to be functioning perfectly.
I seem to have a new situation now though, where my Hox will enter a bootloop whenever I reboot my phone. It's not a huge issue with me, as I can just enter fastboot and flash the boot.img again to get it working. But if I'm not at my computer by any chance, then I would be sort of SOL. So I was just wondering if any of you guys could possibly chime in with a reason why this is happening and how I could fix it.
Once again, I apologize deeply if I just forgot to do something, or if the answer is as clearcut as it can possibly be. Thank you all, regardless.

sleepyhills said:
Hey all,
I really hope I'm posting this in the right forums, and I did do a google search/xda search prior to this, but I unfortunately did not find anything relevant to my situation.
Anywho, I flashed CM10 on to my phone but ended up in a bootloop. Coming from the S3 and never before using an HTC, I did do the mistake of not flashing the boot.img included with the zip through fastboot initially. After realizing what I forgot to do, I did it and ta-da! It works now and seems to be functioning perfectly.
I seem to have a new situation now though, where my Hox will enter a bootloop whenever I reboot my phone. It's not a huge issue with me, as I can just enter fastboot and flash the boot.img again to get it working. But if I'm not at my computer by any chance, then I would be sort of SOL. So I was just wondering if any of you guys could possibly chime in with a reason why this is happening and how I could fix it.
Once again, I apologize deeply if I just forgot to do something, or if the answer is as clearcut as it can possibly be. Thank you all, regardless.
Click to expand...
Click to collapse
fastboot erase cache

did you do fastboot boot boot.img or fastboot flash boot boot.img?
sounds like you may have done the first one which would load the kernel one-time and then on next boot it wouldnt be there because it wasnt actually flashed.

I had the same. Just come from Stock rooted Sense 4.1 ROM to viperX. Followed the instructions on their setup but got just a reboot boot loop. If I went to fastboot, shutdown then booted up from cold - no probs. Did the above with the boot.img from the ROM zip, and the erase cache thing. 2 successful reboots later n it seems OK!

Related

Stuck in a boot loop

Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
I had issues flashing CWM recovery via fastboot... I was able to "fastboot boot recovery.img" From there, you can flash a ROM with ROM Manager and reflash your recovery.
Let me know if you run into the same issues.
steviewevie said:
Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
Click to expand...
Click to collapse
You might have to flash a rom via bootloader/fastboot. Just remember you can't flash one with a older hardboot version. If you have the eng bootloader, you shouldn't have a problem. What a pain though, I hope it isn't the radio either as I flashed a different one earlier tonight also, lol!
Crap, I flashed the same damned radio as you did too. Ha! Although, I do find this ironic after our little debate about the forum merge yesterday I'm sure you can try reflashing recovery via fastboot and if that fails reflash stock rom through fastboot. Its not bricked for sure...
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Lennyuk said:
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Click to expand...
Click to collapse
He must have had a bad flash... I flashed the same radio with no problems and several powering off attempts and reboots, checking compatiblity, and backups. No issues and have already reflashed a few roms and kernels. The radios are safe... at least the lastest desire z one from Eygpt and the two stock tmobile usa ones are too.
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
steviewevie said:
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
Click to expand...
Click to collapse
Sounds like it... I've seen this happen on some old WM phones before.
Well my phone has exactly the same problem this morning after being left powered off overnight.
I tried flashing the recovery image and radio image again, via fastboot, like last time, but it didn't help.
Going to reflash the stock ROM. I'm starting to think there is something wrong with my phone and it's going to have to go back
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
ddotpatel said:
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
Click to expand...
Click to collapse
No I didn't use Visionary lol.
Yesterday, after first having the problem, all I did was flash CW recovery and flash the new (Egypt) radio again. Then the phone was back to life, I rebooted it several times and all was 100%.
This morning though it was stuck again but flashing CW recovery and the radio (both via Fastboot) didn't help at all.
So I've just flashed the stock UK/Europe ROM. Will root again via rage, install ROM Manager, flash Clockwork and restore the nandroid backup I did last night.
I will stay back on the stock ROM/radio combination for a bit because I'm starting to wonder if my phone has a problem. No-one else has reported an issue with this radio.
Edit - back up and running fine now after doing the above.
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
AnyDone said:
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
Click to expand...
Click to collapse
Yeah I know what you mean. I'm going to stick with the stock radio (even though it's worse than the newer one) for a while to check that the problem goes away. Then I will probably try flashing it again to see if the problem comes straight back again.
I also did wonder about whether I can just "dd" the new radio to the correct partition instead of using fastboot to flash it, though I'm not going to do that unless someone can confirm that's ok.

[Q] S On Unlocked Dinc2 stuck at HTC screen

I am a noob, I have made several mistakes.....but I am literally begging for help.
I unlocked my Dinc2 through the HTC dev site....I know now this was mistake #1. I tired flashing a few roms, none of them worked....they all got hung up on white HTC screen. I was able to get into recovery and get back to my stock rom before I tried installing anything.
The last rom I tired, I tired doing it through adb and command prompt...it looked like it worked, but when I booted...it got stuck again. I tired recovery and this time the restore wont even boot.
I have read all the posts similar, and the only difference is I am S On so I cant flash a RUU.....please help.
I have taken so many pieces of advice I dont know what to do, thank you in advance.
KobeKane said:
I am a noob, I have made several mistakes.....but I am literally begging for help.
I unlocked my Dinc2 through the HTC dev site....I know now this was mistake #1. I tired flashing a few roms, none of them worked....they all got hung up on white HTC screen. I was able to get into recovery and get back to my stock rom before I tried installing anything.
The last rom I tired, I tired doing it through adb and command prompt...it looked like it worked, but when I booted...it got stuck again. I tired recovery and this time the restore wont even boot.
I have read all the posts similar, and the only difference is I am S On so I cant flash a RUU.....please help.
I have taken so many pieces of advice I dont know what to do, thank you in advance.
Click to expand...
Click to collapse
When you flash a custom ROM on an locked bootloader, you then extract the boot.img contained in the ROM's zip file and flash it in fastboot mode using the command:
fastboot flash boot boot.img
I may have extracted the wrong boot.img..... if I try this over again and get the right one should it work?
KobeKane said:
I may have extracted the wrong boot.img..... if I try this over again and get the right one should it work?
Click to expand...
Click to collapse
Yes that is the procedure you need to do with the unlocked bootloader.

Help urgent!!!!!!! Gn stuck on google symbol

So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.

Nexus 5X Bootloop/Brick Help

Hello, I apologize if many people have already asked for help with this issue but I have looked over the forum many times and none of the solutions have applied to me.
I was running 7.0 and my Nexus 5X had a random crash and went into BootLoop. I being stupid, flashed the wrong boot.img at first but not sure if that has damaged the phone. I upon realizing my mistake, cleared the original one and flashed all the right imgs. One thing i'm not too sure about is whether to lock the oem after flashing everything even though it will wipe everything or leave it unlocked till it actually boots, or does this make no difference. Regardless, open flashing everything I still encounter bootloop. I am able to go to the fastboot menu, I am not able to run recovery successfully, I am able to go to the download and firmware update screen. My laptop detects the device as an Android.
Here's what I need:
Can someone please tell me what I need to do to start fresh, in case I went wrong anywhere to fix any partitions any kernels and then reflash all the ROMs in order to have my phone working again. Also, does it matter what firmware I am flashing?
If you have any questions let me know,
Thanks!

Question Soft brick no backup

Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here
RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know
You have to download the firmware and paste it into the platform tools folder and click flash all.bat

Categories

Resources