I accidentally flashed system rom image to recovery partition.
The problem is that my system is not starting up (stucked after "htc - quietly brilliant" at "htc one tm" screen.
It is not booting up to the phone, and it is not booting to recovery (as it is system itself now).
When I try boot into bootloader using command prompt (cmd) screen it says "error: more than one device and emulator"
Could someone please kindly assist me how to get my phone back to normal?
{ Sorry to bother the forum with my stupid question, it was too late at night yesterday and could not boot into bootloader. But after a good sleep I am now able to do that. You may discard and delete this topic. Sorry again. }
Related
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
did you erroneously flash the boot.img to the recovery partition? that would be the only thing that would cause that i'd think..
i would retry the following.
fastboot flash recovery clockworkmod-5.8.4.0.img
fastboot flash boot boot.img
fastboot erase cache
with boot.img being the kernel provided with your cm10 rom and clockworkmod-5.8.4.0.img being the name of your CWM recovery image.
as for fastboot working intermittently I would check to make sure the cable is snugly plugged into the computer and try another cable if possible.
Vorphs said:
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
Click to expand...
Click to collapse
I have just overcome a similar problem myself.
Start over, and do factory reset (after nandroid). Then flash the latest clockwork recovery to your phone (CWR 5.8.4.0) using
"fastboot flash recovery <filename.zip>" in the command line
then, boot into recovery, insert usb cable and choose mount usb. simply drop CM rom zip file onto your phone form the PC.
then unmount, go back to recovery menu and select install zip from sd card, then choose your zip file. after this, select reboot system from recovery. it should work fine.
I think you may have acidentally installed the CM10 rom as recovery using the wrong syntax in fastboot.
Hope that helps
Thx for the reply's, unfortunately whenever i try to flash something using fastboot, i get "error: cannot load imagename.img". Only the erase cache command works...
Fixed it using fastbootflasher!
hey guys
I just rooted my HTC ONE X using a Mac and tried to install CM 10 onto the phone. After loading the boot.img file onto the phone, the phone is now not starting up.. it keeps turning on and going as far as the screen that says, 'htc quietly brilliant'..
i am unsure on how to get the phone back to just functioning normally. I am using a Mac and finding it hard to find help on how to revert back to original
any tips?
cheers
Did you do the command 'fastboot erase cache' after you flashed the boot.img file??
Get into fastboot reflash the boot image most of the time the error is the user not typing in the correct procedure to flash ie : fastboot flash boot boot.img hence you get the white screen simply restarting the process in fastboot always seems to work , fastboot wipe cache , then head to recovery to install Rom , you should be fine from there.
try another Kernel, it will fix my solution
So here's how it all started. After installing cyanogenmod 10 on my htc one x, it would not boot up anymore. (Btw, I have the clockwork recovery mod) I'm not sure if I followed the steps correctly. I thought that doing a hard reset would erase the rom that was in the sd and that it would boot from the stock sense 4.0.3 rom but it didnt. Whenever I turn it on it always shows the "HTC quietly brilliant". It doesnt do anything after that. What do I do?? PLEASE HELP! IF YOU FIX THIS ISSUE I WILL AWARD YOU WITH $$ (Paypal) THX
amilajack said:
So here's how it all started. After installing cyanogenmod 10 on my htc one x, it would not boot up anymore. (Btw, I have the clockwork recovery mod) I'm not sure if I followed the steps correctly. I thought that doing a hard reset would erase the rom that was in the sd and that it would boot from the stock sense 4.0.3 rom but it didnt. Whenever I turn it on it always shows the "HTC quietly brilliant". It doesnt do anything after that. What do I do?? PLEASE HELP! IF YOU FIX THIS ISSUE I WILL AWARD YOU WITH $$ (Paypal) THX
Click to expand...
Click to collapse
there's even a video tutorial on how to do it, is it so hard to follow it!?!?!
http://www.youtube.com/watch?v=elDvcVot7qo
and for the 1000000000th time, you have to flash the boot.img!!!!!!!!
amilajack said:
So here's how it all started. After installing cyanogenmod 10 on my htc one x, it would not boot up anymore. (Btw, I have the clockwork recovery mod) I'm not sure if I followed the steps correctly. I thought that doing a hard reset would erase the rom that was in the sd and that it would boot from the stock sense 4.0.3 rom but it didnt. Whenever I turn it on it always shows the "HTC quietly brilliant". It doesnt do anything after that. What do I do?? PLEASE HELP! IF YOU FIX THIS ISSUE I WILL AWARD YOU WITH $$ (Paypal) THX
Click to expand...
Click to collapse
with cm10 download you have you need to extract boot.img to where you have adb drivers (contains adb shell and fastboot) saved. if not need to download android sdk. Once done need to get phone into hboot/fastboot vol. down + power (will show hboot and option hboot highlighted in blue press power once to enter fastboot) and then connect usb.
Go to pc and then go to start>run and type cmd (command prompt will appear) change path to where adb is saved (In my case its in my documents so it would be cd my documents ENTER cd adb ENTER and path will show C:\Users\Administrator\My Documents\adb>) once your path is correct type fastboot flash boot boot.img ENTER and it will write to phone. Then type fastboot reboot ENTER phone will reboot and boot into cm10. Hope this helps!
PS: By me tying ENTER I am instructing you to press the Enter key. Sorry if it sounds pedantic by thought I'd mention it. Thanks!
The problem is that there is no cyanogenmod file on my device because I formatted my sd. Is there a way that I can transfer the whole cyanogenmod file to my one x while it is still in recovery/fastboot?
amilajack said:
The problem is that there is no cyanogenmod file on my device because I formatted my sd. Is there a way that I can transfer the whole cyanogenmod file to my one x while it is still in recovery/fastboot?
Click to expand...
Click to collapse
Boot into recovery, connect to your computer and select "mount USB storage" in recovery.
Remember, you MUST flash the boot.img through fastboot as well as flashing the rom
As title says, in last steps after unlocking device but won't let me flash "recovery.img" file
error: cannot load 'recovery.img': Unknown error is what it keeps showing me. Tried erasing cache already as well to no avail
Is the name of the recovery file recovery.img? Have you put the recovery.img file in your fastboot folder?
Make sure you enable extensions on filenames in windows before renaming a recovery to recovery.img because it will be named recovery.img.img !
Got that issue fixed but now when I try to boot the phone into recovery it just black screens me then normal boots back to the main screen. It's the latest version of cwm, but I couldn't get twrp to boot up either. So strange because I didn't really run into much trouble rooting my HTC One so I'm feeling really silly that I can't figure out what the issue here is. :'(
Sent from my HTC One X using xda app-developers app
Do
Fastboot erase cache
Then enter the recovery
Mr Hofs said:
Do
Fastboot erase cache
Then enter the recovery
Click to expand...
Click to collapse
sorry for the late reply just got home from work not too long ago, tried that and it starts like its going to boot into recovery and stays on the HTC screen for about 20 seconds then, goes to black and reboots back normally again. Think I need to just reinstall clockwork recovery again?
Brodrick said:
sorry for the late reply just got home from work not too long ago, tried that and it starts like its going to boot into recovery and stays on the HTC screen for about 20 seconds then, goes to black and reboots back normally again. Think I need to just reinstall clockwork recovery again?
Click to expand...
Click to collapse
Yeah flash this recovery : https://www.dropbox.com/s/p35p0tqf41jbj8b/recovery.img
try naming the file recovery, delete the .img part, then type into cmd : fastboot flash recovery recovery.img
might not work but worked for me
I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.