Related
Hello,
I don't know exactly what happened, but at some point last week my phone started only booting to fastboot. I can't even access recovery, even after flashing a new one (clockworkmod touch, and then regular).
What is going on? Is the phone a complete brick?
Thanks in advance!
shwouchk said:
Hello,
I don't know exactly what happened, but at some point last week my phone started only booting to fastboot. I can't even access recovery, even after flashing a new one (clockworkmod touch, and then regular).
What is going on? Is the phone a complete brick?
Thanks in advance!
Click to expand...
Click to collapse
Use a RUU, then S-OFF and flash recovery.
I cannot use an RUU, since I am stuck in the fastboot/Hboot screen, which the utility does not recognize... :-(
Plan B?
Boot your phone in fastboot-mode and running RUU.exe on your PC should work completely fine.
But you asked for a Plan B, here you have one:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
First, thanks for the responses!
I don't know why, but the RUU did not recognize the phone in fastboot mode...
In either case, I followed the instructions in "Plan B", with the following RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
The problem is that during stage [6] SYSTEM, I get "Fail-PU" and am told that "partition update failed" (I am guessing that PU = partition update) and am asked to reboot.
Should I try a different RUU? something else?
I am happy to say that although the RUU did not work and I don't know why, I tried again flashing clockworkmod through fastboot, and now I am able to get to recovery!
I will try to install a ROM and see how it goes. Thanks to both for the help!
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Hi,
I followed this guide perfectly:
http://forum.xda-developers.com/showthread.php?t=2272706
Mainly because I'm new to this & was easy to follow, i did everything it said, i checked the cid & used the firmware update this guy suggested, purely because my phone is stuck on 0.95 hboot & i needed higher to be able to install the latest custom cyanogen version.
Everything worked fine, right up until the end, after i unlocked the bootloader at the end, the phone restarted & now it has been sat on the htc quite brilliant screen.
I can go into the recovery things, i've tried factory reset & clearing the cache, but it hasn't altered the fact the phone won't load up past that logo screen.
Could you please help me in any way possible to get the phone on, i don't care if i have to just leave trying to update it or if i can reset what i've done somehow & there's a straight forward way of just getting jelly bean 4.2.2 without any custom mod things, any option please.
Lastly could you please be specific with your solution, as I said i'm new to this & having this attempt fail & no idea why after following a step-by-step guide, I'd just be happy to get my phone back on.
Thanks for your time,
Regards,
Jay.
I'd just like to add, i've not got a custom recovery or anything else added on the phone, i just followed that guide & did exactly as it said.
jayitsimpossible said:
I'd just like to add, i've not got a custom recovery or anything else added on the phone, i just followed that guide & did exactly as it said.
Click to expand...
Click to collapse
post the result from command fastboot getvar all and delete S/N and IMEI from results
Did you flash cyanigen mod Rom or are you still on the stack Rom.
Thant said:
post the result from command fastboot getvar all and delete S/N and IMEI from results
Click to expand...
Click to collapse
Could you please tell me how to run the commands from the phone? If that's what you mean, I've only been running them on the PC from the command prompt when doing things previously, unless you can still connect with the USB cable & it will work? As i was seeing it wouldn't find the device when i was trying yesterday.
paulh1978 said:
Did you flash cyanigen mod Rom or are you still on the stack Rom.
Click to expand...
Click to collapse
No i didn't flash anything else except the firmware.zip which was needed to update the Hboot, so yes I'm still on the stock Rom. I just followed that guide exactly as it said, the Hboot has updated to 1.39, but the phone no longer goes past the HTC quietly excellent splash screen.
Originally the phone had Android 4.0.3 and Hboot 0.95, now from the bootloader menu screen it is saying the Hboot is 1.39. I've not changed or done anything else except clear the cache & factory reset options to try & get the phone to load.
Thanks for your time guys, I will post my result from the command if you can tell me how to run it, will see if it will run plugged in on USB, but yesterday it wasn't working to run commands from the PC, which is why I'm asking if i can run the fastboot commands from on the phone.
I have no custom recovery, rom or anything else flashed to the phone. My ideal outcome would be to get the jellybean 4.2.2 flashed & working, but i didn't get chance to go on & flash the recovery or rom, as the Hboot is as far as i got.
Thanks again,
Regards,
Jay.
jayitsimpossible said:
Could you please tell me how to run the commands from the phone? If that's what you mean, I've only been running them on the PC from the command prompt when doing things previously, unless you can still connect with the USB cable & it will work? As i was seeing it wouldn't find the device when i was trying yesterday.
No i didn't flash anything else except the firmware.zip which was needed to update the Hboot, so yes I'm still on the stock Rom. I just followed that guide exactly as it said, the Hboot has updated to 1.39, but the phone no longer goes past the HTC quietly excellent splash screen.
Originally the phone had Android 4.0.3 and Hboot 0.95, now from the bootloader menu screen it is saying the Hboot is 1.39. I've not changed or done anything else except clear the cache & factory reset options to try & get the phone to load.
Thanks for your time guys, I will post my result from the command if you can tell me how to run it, will see if it will run plugged in on USB, but yesterday it wasn't working to run commands from the PC, which is why I'm asking if i can run the fastboot commands from on the phone.
I have no custom recovery, rom or anything else flashed to the phone. My ideal outcome would be to get the jellybean 4.2.2 flashed & working, but i didn't get chance to go on & flash the recovery or rom, as the Hboot is as far as i got.
Thanks again,
Regards,
Jay.
Click to expand...
Click to collapse
I'm guessing that was ice cream sandwich you were on so if your still stock ie ice cream sandwich then I don't think it's compatible with the new hboot I could be wrong though maybe thant knows more. If I'm right you will need to download a custom jb Rom and recovery then flash them all.
jayitsimpossible said:
Could you please tell me how to run the commands from the phone? If that's what you mean, I've only been running them on the PC from the command prompt when doing things previously, unless you can still connect with the USB cable & it will work? As i was seeing it wouldn't find the device when i was trying yesterday.
Click to expand...
Click to collapse
Ok you are upgrade your phone to hboot1.39. Now download this recovery extract from zip arhiv the file recovery.img in your fastboot folder. Go with the phone in bootloader and conect to computer. after this run CMD and run the gomand fastboot flash recovery recovery.img after this go again in bootlader and choice the recovery.connect the phone and Mount the sd card you have option in this recovery copy your rom to sd card and flash it. Extract from the rom arhive boot.img in your fastboot folder. Go in bootloader and connect the phone and run cmd and the command fastboot flash boot boot.img and after this fastboot erase cache restart the phone and you have custom rom
Hi thanks for that guide, I'm all sorted now, basically did as you said, I flashed the CWM recovery, then the rom & finally the boot, it all works without a problem now PHEW!
I expected after doing the Hboot that the phone would still work as normal, however it wouldn't boot, probably because of what was suggested, the new Hboot would only allow Jelly Bean to work not ICS.
So with just flashing the new recovery & rom, it worked with no issues. Thanks again,
Regards,
Jay.
hi everyone
when i reboot my device by any means (from inside of android, recovery, even adb reboot-bootloader), the device never finishes the reboot. interestingly, when i have it plugged into windows by usb, when doing the reboot i hear the usb disconnect sound, then the usb connect sound, then it just stays black screen and is unresponsive. only fixed by holding power or power+down button.
some info:
bootloader v 4.02 // twrp 2.7.1.1 // liquidsmooth current nightly
however, this problem happens on stock rooted as well as all custom roms
i have included a logcat of the issue (never made one before but i think i did it right) if someone can please help me, i'm thinking i may need to return my model.
thank you! :fingers-crossed:
Vember31 said:
hi everyone
when i reboot my device by any means (from inside of android, recovery, even adb reboot-bootloader), the device never finishes the reboot. interestingly, when i have it plugged into windows by usb, when doing the reboot i hear the usb disconnect sound, then the usb connect sound, then it just stays black screen and is unresponsive. only fixed by holding power or power+down button.
some info:
bootloader v 4.02 // twrp 2.7.1.1 // liquidsmooth current nightly
however, this problem happens on stock rooted as well as all custom roms
i have included a logcat of the issue (never made one before but i think i did it right) if someone can please help me, i'm thinking i may need to return my model.
thank you! :fingers-crossed:
Click to expand...
Click to collapse
Have you tried flashing stock images using fastboot?
It seems like the system can't write to /data directory, maybe flashing everything again will fix that issue.
alresave said:
Have you tried flashing stock images using fastboot?
It seems like the system can't write to /data directory, maybe flashing everything again will fix that issue.
Click to expand...
Click to collapse
I did flash the stock images (the latest 4.4.4) and unfortunately still had the same problem. i'll give it another shot today though to see what happens
EDIT: performed the fastboot flash with the factory images and had the same issue. tried philz recovery and wouldn't turn back on after selecting reboot. checked permissions on /data and /system and everything was RW. i tried remounting both as well to no avail. must be a hardware issue i feel like at this point
*Try flashing through a different custom recovery.
* figure out how to use the flashall.bat script to flash a new recovery, bootloader, ROM and kernel.
*Try fastboot boot for the recovery as opposed to fastboot flash. (I'm not sure if this will do anything)
*try wugfresh toolkit soft brick unroot+flash stock
Ps: this is just a list of ideas. Flashing a working ROM should mount all of your directories.
mugzylol said:
*Try flashing through a different custom recovery.
* figure out how to use the flashall.bat script to flash a new recovery, bootloader, ROM and kernel.
*Try fastboot boot for the recovery as opposed to fastboot flash. (I'm not sure if this will do anything)
*try wugfresh toolkit soft brick unroot+flash stock
Ps: this is just a list of ideas. Flashing a working ROM should mount all of your directories.
Click to expand...
Click to collapse
Thanks for the suggestions, though trying those methods unfortunately hadn't done it either. Eventually, the ability to reboot simply showed up just the other day. I'm not too sure why it did and wasn't working before, but I kind of think it needed about 1-2 days of being powered on while connected to a charger. Previously, I would charge it only every few days with the power off and unplug it to use it. That's the only difference I can spot for anyone else who runs into this problem. Keep it connected to the charger for a day or two with the power on.
Hi guys – hoping you can help me following an issue with my M9 I bought a couple of days ago. Last night I unlocked the bootloader with HTC dev, rooted with TWRP/SuperSU, S-OFF’ed with SunShine, updated firmware to 1.40.401.5 per matanlevanon‘s thread, then flashed MaximusHD.
Up until the last step, everything went well – but I’m now stuck in boot loops. I can currently access both Download Mode and bootloader; but trying to launch recovery gets as far as the TWRP splash screen before my phone reboots again.
I've reflashed TWRP.img using fastboot; but when rebooting into recovery I still have the same result (TWRP splash screen before my phone reboots again)
I've also lost ABD - in Download Mode/bootloader, Windows Device Manager see’s my phone without issue and correct drivers – but ADB server doesn’t recognise my phone.
I’ve tried everything from HTC Sync bundled drivers, PdaNet drivers to generic ADB drivers – but ADB seems to refuse to see my phone regardless of what I try.
Seemingly if I can get a working recovery image / TWRP on and working I can wipe and try to flash again, but current images don't seem to be helping. Any suggestions / help please?
Got it, cache partition was corrupted! fastboot erase cache let me get back into TWRP and reflash my ROM.
Fingers crossed it's smooth sailing from here