Hey guys, I'm having trouble with my nexus device, I was watching youtube on it and it froze and now doesnt boot. I can access hboot, but recovery just shows the X logo and restart. I've tried reflashing boot.img, reflashing the recovery, reflashed stock hboot, flashed new roms from fastboot. I've also tried passimg.zip, and flashing a different radio but it stops 90% the way through, and it gets stuck in loading passdiag.zip if I use the volume down button to boot instead of the trackpad button.
The graphic abnormality is like an artifacting. If you search youtube its called "Nexus one stuck on X, can't boot to recovery.", I cant however post a link.
Anyone encountered this before? Any insight is appreciated.
well I've managed to remove blackrose at least, and to get to the blackrose menu. You have to access it from command prompt with "blackrose.exe skip" while in fastboot. Though I'd put it here incase it helps someone else in a similar circumstance.
Related
Ok so I rooted my hero, but i accidentally tried to load a custom rom with out flashing a recovery image. So when i tried to do that, i forgot to uncheck the debugging setting. so basically its stuck on the htc screen. i can boot into recovery mode if i hold down the volume down button, but if i hit reboot, it goes back to the htc screen.
when i went into recovery mode, i read one of the lines and it says that there is no recovery image. i tried to run the stock RUU, but my computer will not recognize the device so the RUU wont run. does anyone have any ideas?
any help is appreciated. thanks
have you install HTC sync? if not go to sprint.com/download and then smartphone then pick your phone you should see HTC sync
Sent from my HERO200 using Tapatalk
yeah, i got that. i was able to flash the RUU, but it didnt solve my problem. still gets stuck at the htc screen.
good thing is that i can still get to the recovery screen.
i even tried flashing the sprint 2.1 ruu, but the problem remains. now the htc screen is white with green letters.
EDIT:
a couple of things i noticed. when the recovery mode first starts running, it says something like checking sd card...then its says no image.
also, up at the top left of the screen, third line. it says "touch panel-fail" struck me as odd.
Try this. Not sure if it will work since you flashed the 2.1 RUU, but it's worth a try.
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
I am having quite a problem. I had unlocked the bootloader and rooted my ONE. Suddenly it decided to freeze on the lockscreen so i tried to reboot. It would not reboot and was stuck on the HTC ONE screen. I tried booting into recovery and sideloading the stock rom which did not work. and now i can not even boot into the recovery. please help. When i try to boot it up regularly it gets stuck on the Quietly Brilliant screen.
Daking12794 said:
I am having quite a problem. I had unlocked the bootloader and rooted my ONE. Suddenly it decided to freeze on the lockscreen so i tried to reboot. It would not reboot and was stuck on the HTC ONE screen. I tried booting into recovery and sideloading the stock rom which did not work. and now i can not even boot into the recovery. please help. When i try to boot it up regularly it gets stuck on the Quietly Brilliant screen.
Click to expand...
Click to collapse
This will sound weird but seems to be helping people in the dev sections:
Put the phone under a bright light, and hold the power and volume down buttons.
I haven't had to use this particular method myself, but supposedly it works.
XT1092 flashing (as in on screen flashing) recovery "no command" screen. Bricked?
Apparently I did something stupid. I had 5.1 which didn't OTA on its own to 6.0. So I thought it maybe had something to do with a past root i had and TWRP recovery. As solution I went and flashed a stock 5.1 rom in fastboot, which worked fine. Still no OTA though, and adb sideloading gave a status 7 error. Then I fastbooted the 6.0 stock rom, but that wouldn't boot (phone would hang in the white "unlocked bootloader" warning screen. I re-flashed 5.1 in fastboot.
Probably not a smart move, cause now I'm stuck in a bootloop to recovery mode where it's flashing the "no command" recovery screen for a fraction of a second, then black screen for 4 seconds, repeating over and over. I can trigger some orange log error by pressing VOL*UP like when you go to recovery mode, but it disappears in the bootloop. (it says qe 1/1 though, which suggests its rooted I read somewhere). So I can't do anything with it anymore. I read tons of threads here of which I found 2 with a similar problem:
http://forum.xda-developers.com/moto-x-2014/help/xt1092-flashing-command-boot-attempt-to-t3259287
http://forum.xda-developers.com/moto-x-2014/help/possibly-soft-bricked-moto-x-flashing-t3195103
It's the same problem I have now, and one of them says that "with some luck" he got into fastboot, but doesn't describe how.
Googling "flashing" related to recovery and/or "no command screen" in this context does'nt yield much result unfortunately.
For the love of god, I can't get it into fastboot mode anymore to do something/anything about it. I pressed, hold, tapped POWER and VOL*UP on countless ways, and it does a "deeper" reboot with appearance of the white unlocked bootloader screen, but it just keeps bootlooping.
How can I fix this? Did I brick it by fastboot flashing 6.0 and then fastboot flashing 5.1? Is it hard bricked and useless?
What do I have to flash when I manage to get in fastboot?
OK, I fixed it. Discovered it when the battery was drained. When the phone is OFF, holding POWER+VOL*UP+VOL*DOWN for 5 seconds and then releasing triggers the fastboot. Problem then is that you can't flash anything cause the battery is nerely depleted. So I let it charge in the bootloop for a bit and I found out I can hard reboot and get into fastboot by holding POWER+VOL*UP+VOL*DOWN for about 10 seconds and then releasing it. It probably turns off and then triggers the fastboot/bootloader mode.
Afraid of bricking it with OTA as I've downgraded to 5.1 from a (non-functioning) 6.0 I've manually flashed a 6.0 stock ROM in fastboot using this guide including mfastboot. So no sideloading or anything. Now it properly boots and I've got a stock 6.0.
Hopefully this helps someone in the future.
As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.