After flashing my phone in Amon RA's recovery the phone will go to the black HTC screen and just stay there. Immediately after flashing I rebooted within recovery and the phone began to reboot, but then shut off. I had to remove the battery to get it to power on again, and it's just stuck at the HTC screen.
Tried to flash boot, recovery, and misc images, but on boot I get no space on device write error. Help?
When you flashed something did you wipe first?
Yes, I wiped, and have wiped the several times I have attempted to do it again.
Related
I tried to flash cyanogenmod onto my vodafone 32B HTC Magic and now it's stuck on a boot loop. I rooted it with super one click, then used amon-ra recovery to load up cyanogenmod. It got to the vodafone red screen then just keeps restarting once every 20 secs or so. I suspect it's because I didn't do a full wipe before flashing, I only clearled dalvik cache. So I tried booting up to recovery but amon-ra isn't loading up and its going back to the android default recovery, which I cant use to reflash another rom. I can't communicate with the phone via ADB (does not recognise device). fastboot can recognise the phone but I can't push anything onto it since I didn't update my SPL (it's at s-on).
So is there any way for me to get amon-ra recovery back onto it or otherwise boot up my phone again?
Find a sappimg.zip and flash that and start over is what I would suggest
I concur :0)
Hey guys, I'm temporarily coming over here from the Inc2 section to help out a friend with the OG Inc. He was originally running CM7... Out of nowhere, his phone decided not to boot up one day and is now stuck in a loop.
What happens is that the phone splashes the "htc incredible" image, goes black, vibrates once, splashes it again, and the process repeats. Now, the strangest part is that I can enter HBOOT but not recovery. What happens is it will load recovery, show the Clockwork menu for about two seconds, then immediately shut off and bootloop again.
I've already tried flashing the stock IMG file through HBOOT - the only change that I can see is that now when I select either "Factory Reset" or "Reboot Recovery" it shows stock recovery for 2 seconds before bootlooping again.
Any thoughts?
skafan2 said:
Hey guys, I'm temporarily coming over here from the Inc2 section to help out a friend with the OG Inc. He was originally running CM7... Out of nowhere, his phone decided not to boot up one day and is now stuck in a loop.
What happens is that the phone splashes the "htc incredible" image, goes black, vibrates once, splashes it again, and the process repeats. Now, the strangest part is that I can enter HBOOT but not recovery. What happens is it will load recovery, show the Clockwork menu for about two seconds, then immediately shut off and bootloop again.
I've already tried flashing the stock IMG file through HBOOT - the only change that I can see is that now when I select either "Factory Reset" or "Reboot Recovery" it shows stock recovery for 2 seconds before bootlooping again.
Any thoughts?
Click to expand...
Click to collapse
If your s-off i would back uo your sdcard and then format it fat32. Then flash cwm recovery thru hboot. If cw works after flashing i would wipe everything and then resore a known working nandroid or flash a fresh rom.
Alright, thanks, I'll give that a try and get back as to whether that works.
I decided to unroot my S4 seeing as though a rom I had flashed was screwing around with my system. I eventually was able to flash a stock rom via kies, but now the phone is stuck at the boot screen (Samsung logo with blue light).
I have tried booting into recovery mode, but for some reason after 5 seconds, it just ignores it and goes into standard boot, something that it has done since I flashed the bad rom.
Would anyone know a fix for this?
Thanks in advance.
An update. I managed to get into recovery mode but instead of the normal android with the blue square, the android is on the ground with a red triangle. I've wiped cache and data, but still getting stuck at the boot screen.
Some help would be appreciated.
re: reset
Pyroaves said:
An update. I managed to get into recovery mode but instead of the normal android with the blue square, the android is on the ground with a red triangle. I've wiped cache and data, but still getting stuck at the boot screen.
Some help would be appreciated.
Click to expand...
Click to collapse
There is a 50/50 chance that if you go back into twrp/cwm custom recovery
and do a "factory reset" it would boot up normally unless you also wiped
"system".
Good luck!
Pyroaves said:
I decided to unroot my S4 seeing as though a rom I had flashed was screwing around with my system. I eventually was able to flash a stock rom via kies, but now the phone is stuck at the boot screen (Samsung logo with blue light).
I have tried booting into recovery mode, but for some reason after 5 seconds, it just ignores it and goes into standard boot, something that it has done since I flashed the bad rom.
Would anyone know a fix for this?
Thanks in advance.
Click to expand...
Click to collapse
Flash a stock firmware using odin in download mode then see if it reboots
If not go to stock recovery after that factory reset and wipe cache reboot
So I've wiped the Dalvik Cache, Data, Internal Storage, and System, but I forgot to flash before rebooting. Now it's stuck in the WARNING BOOTLOADER UNLOCKED screen and everytime I tried resetting to recovery mode it would turn off then turn back on at the same screen. ADB is not detecting the devices also. Is there anything I can do or is it bricked?
the_onlyhope said:
So I've wiped the Dalvik Cache, Data, Internal Storage, and System, but I forgot to flash before rebooting. Now it's stuck in the WARNING BOOTLOADER UNLOCKED screen and everytime I tried resetting to recovery mode it would turn off then turn back on at the same screen. ADB is not detecting the devices also. Is there anything I can do or is it bricked?
Click to expand...
Click to collapse
Boot into bootloader by holding down vol down and power together. The timing can be a little tricky when it is stuck or looping. Hold power until the screen goes dark and it tries to reboot, usually about 8 seconds. Then let go and immediately hit vol down + power together. Hold them until the bootloader screen comes up, should be pretty fast. Might take a few tries to get the technique down with it bootlooping.
From there you can flash firmware directly with fastboot, or boot it into TWRP to flash something from recovery. If TWRP fails to boot for some reason then fastboot flash it again.
It should not be a brick just from wiping everything. Well, just a soft brick anyway.
Thanks!
I was able to get into recovery!!
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me