Hey,
I attempted installing Android Revolution on my HTC One - but it rebooted the phone for some strange reason during the install - i am now stuck on the HTC white boot screen - it was looping but i cleared the cache. I can still enter fastboot mode but don't know how to get the phone back to a state where i can actually get past the boot screen.
The phone is a 3 UK one.
Any help would be greatly appreciated.
Zack.
can you try flashing the rom again or want it get that far?
ant78 said:
can you try flashing the rom again or want it get that far?
Click to expand...
Click to collapse
To be honest i am pretty new at this. I can access the recovery menu and enable fastboot and also access Clockworkmod T. Unsure where i am going from here.
Currently as it stands the phone will not get past the white HTC loading screen.
Right, i have an original ROM dump (system.img, boot.img, recovery.img) - I presume this would be the best way forward? I issued the following:
fastboot flash recovery recovery.img OK
fastboot flash boot boot.img OK
fastboot flash system system.img > load_file: could not allocate 1946156032 bytes, error: cannot load system.img, not enough space.
Can anyone help me? My phone is just stuck on the HTC boot screen
Related
a while back i encountered some sort of error that caused my boot1 partition to disappear, leaving a gear-type-image on bootup
i believe i was doing something with adb. I know there is a command in adb to delete a partition, however i could not find one to recreate a partition, so i have been stuck with this gear since then
it's not a major issue, as it has no real effect on performance, and it doesnt show up unless i boot my phone, which i never turn off, however if there is a way to fix it, i would like to.
anyone got any ideas on how i could restore my boot1 partition?
is it the first image that appears on your phone or after that where the animation should be?
it's the first image.
it appears where the "Rogers" logo would be
if you can find the original rogers boot image, it may be in the rogers real root thread by haykuro, you can fastboot flash splash1 nameofsplashimage.rgb565 and that should fix it. the first image when your phone boots up is called splash1.
that is exactly the issue, when i try to flash my splash1, it tells me the partition does not exist
just wanted to bump this one, kuz im still lookin for the answer
1)find a splash image on these forums (it should be in .rgb565)
2)then boot into bootloader mode, and press back until youre in fastboot mode
3)connect the phone to USB, the screen should not show fastboot USB
4)On PC open console and type in adb fastboot flash splash1 [Directory to your splash image file eg C:/Android/Mysplash.rgb565]
5)Reboot the phone
or if you just want to flash the stock splash image follow these instructions
http://forum.xda-developers.com/showthread.php?t=473248
you need to have a non perfect SPL for this to work but since you managed to delete it im assuming you already have one lol
i think i bricked my device. it stays on fastboot screen and hboot screen. i can get to recovery screen but when i wipe and flash rom and reboot it just goes back to fastboot screen. also when i tried to flash new recovery image from computer using command prompt it would not recognize the device. please someone help me fix my nexus one.
I picked up my nexus after hiking, found it froze on a screen and VERY hot. I pulled the battery, let it cool, and now its stuck at the boot loader.
I can access fastboot, but i can not get into recovery.
i tried:
1) reflash revocery via fastboot - no go
2) Tried to restore nexus to stock by
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img - All flashed, but still end up in a stuck bootloader
Phone is STILL stuck at bootloader screen. Any help? I had the phone for only 3 months. I dunno if HTC will cover it. Honestly i don't even know what went wrong besides it overheated
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Try flashing CWM as well and see what happens ...
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
redbull123 said:
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
Click to expand...
Click to collapse
I can't get to settings. It hangs at the HTC logo.
v-b-n said:
Try flashing CWM as well and see what happens ...
Click to expand...
Click to collapse
I did try that. It hangs at the "Entering Recovery..." screen.
dlbarron said:
I did try that. It hangs at the "Entering Recovery..." screen.
Click to expand...
Click to collapse
did u "fastboot erase cache" after flashing the recovery?
kibmikey1 said:
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Click to expand...
Click to collapse
Is that the right recovery?
Don't I have to be able to boot into recovery to run the RUU? Where can I get it?
What are some of the other options?
nkk71 said:
did u "fastboot erase cache" after flashing the recovery?
Click to expand...
Click to collapse
Yes, I tried erase cache before and after, no difference.
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
xxmorph3u5xx said:
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
Click to expand...
Click to collapse
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Looks like I have no choice but to try the RUU. I have been hesitant because I have yet to find a good explanation and good downloads of all the parts I need. Is there something like that available?
all right, this will certainly add to the confusion.
I flashed recovery_m7_att_stock and was able to get into it a little. Then I went back to the bootloader and flashed openrecovery-twrp-2.5.0.0-m7 and actually get into it.
WHAT?
I pushed the CM nightly rom to it and it installed, although there were some errors about not being able to mount some things data and cache. But it did install and I was able to get into CM.
I'm almost afraid to try anything else at this point.
dlbarron said:
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Click to expand...
Click to collapse
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
nkk71 said:
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
Click to expand...
Click to collapse
After rebooting I'm still able to get into TWRP. I've been able to flash a couple of ROMs (very carefully) and I'm no longer seeing any errors about not being able to mount.
Looks like what ever was wrong has been corrected. Now all we have to do is figure out what went wrong and what I did to fix it.
Thanks everyone.
Apologies if this is a repost, I couldn't find anything that was specifically related. My Nexus 6 updated to 6.0.1 recently, worked fine. Next day, battery had run out of charge, plugged it in and it would only boot up to the bootloader menu. It won't boot up fully, or won't boot up recovery mode either. In the bootloader logs I get the following;
'failed to validate boot image: ret=-1'
If you try to run recovery mode;
'failed to validate recovery image: ret=-1'
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Edit - Nexus 6 fully working again! For whatever reason, I took out the SIM card tray and it worked first time. Thank you for all the responses!!
benjackson26 said:
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Click to expand...
Click to collapse
What does fastboot say?
benjackson26 said:
Apologies if this is a repost, I couldn't find anything that was specifically related. My Nexus 6 updated to 6.0.1 recently, worked fine. Next day, battery had run out of charge, plugged it in and it would only boot up to the bootloader menu. It won't boot up fully, or won't boot up recovery mode either. In the bootloader logs I get the following;
'failed to validate boot image: ret=-1'
If you try to run recovery mode;
'failed to validate recovery image: ret=-1'
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Click to expand...
Click to collapse
Have you tried booting directly to your recovery? Try the following command without the quotes and replace "xxx.img" with the name of your custom recovery: "fastboot boot xxx.img". example.. fastboot boot twrp.img
istperson said:
What does fastboot say?
Click to expand...
Click to collapse
It says it's sending 'recovery', writing 'recovery' and then finished. I restarted bootloader after it had done and tried to enter recovery mode but the same thing happened. It does say now in bootloader logs 'invalid boot image header'.
Then try booting to recovery.
http://forum.xda-developers.com/nexus-6/help/flash-n6-t3422968
May you find some solutions here
Okay, I took the SIM tray out, as I read that on the thread suggested, and I've been able to flash all the images necessary. Just booting up now, I'll let you guys know if it works! Thank you to everyone for the responses!!
This makes no sense as to why it works but it did just fix my spare nexus 6 that wouldn't turn on after sitting in a drawer for a week