So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Pilz said:
So I'm restoring my old Nexus 6 that is being sent back for RMA and I encountered an issue. I have flashed things so many times I should remember how to fix this, but I haven't encountered it since my Nexus 7. I flashed all of the images and wiped the userdata as per the usual order. Everything boots fine until I lock the BL. When I re-locked the BL and restart the phone it goes to wipe its self and encrypt. The issue is that the stock recovery which it boots into during this process just has a android with a hexagonal floating blue orb in his chest and sits there for what seems like indefinitely. Its been sitting like that for a hour or so now and when I check what its doing using the "hold power press and release vol up" it says formatting data. I also tried booting into the stock recovery via the BL menu and its doing the same thing. I tried both 5.0 and 5.01 images with the same result. The last time I did this I didn't encounter this issue. I just want to make sure it boots normally so I can send it back in. If I unlock the BL it boots just fine after I format userdata and cache, but it won't go past the above mentioned state when I lock it.
This is what I did as far as fastboot flashing goes (LRX21O) the 5.0 stock rom:
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot oem lock
fastboot reboot
I'll try to re-download both images to see if maybe something changed but its odd because I have done this so many times its second nature. I think the issue lies with the encryption because I was unencrypted before and maybe it just takes forever.
Edit: after 2+ hours of it sitting there the phone finally booted. I thought it would never go past that screen but I guess encryption just takes forever.
Click to expand...
Click to collapse
After all of this, did you test the recovery? I've been having the same issue today, but my recovery still isn't coming up. Every time I try, I still get the dead android with the triangle in the belly, but I am booted up and running.
Related
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 got a message saying that an update is availible and i tried to download and install it but it failed two different times so i gave up. Now after several power cycles due to normal use my razr i is stuck in a boot loop (static red moto symbol then boot animation with intel inside repeating).I got the phone into fastboot mode and then I downloaded and installed rsd-lite and all motorola drivers. 2 different computers that ive tried rsd lite does not detect the phone however fastboot does. Factory option just resumes the boot loop. I dont know how to procede from here?
Edit: Phone is locked bootloader unrooted
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
megamit said:
Okay i guess this thread can be left incase anyone else gets in my position. I was able to fix my phone as fastboot was able to detect. i simply typed
Code:
fastboot -w reboot
and it wiped my userdata and cache and allowed the phone to boot.
Click to expand...
Click to collapse
It really works!
Thank you!
So I am having random soft reboots that shows the boot animation for a few seconds and then it returns to the lock screen. I am getting this on ROMs like Euphoria OS and Chroma. Is there any way to track the cause of these reboots? kmsg/last_kmsg isn't supported (or not enabled by default) by our phones if I checked correctly.
IntenseColor said:
So I am having random soft reboots that shows the boot animation for a few seconds and then it returns to the lock screen. I am getting this on ROMs like Euphoria OS and Chroma. Is there any way to track the cause of these reboots? kmsg/last_kmsg isn't supported (or not enabled by default) by our phones if I checked correctly.
Click to expand...
Click to collapse
last_kmsg shows why something rebooted, they wont help on soft bootloops(or similar. first tjing to do is uninstall your apps, but i wont ask you to do that. instead, you should boot into safemode, and run that way. then youll see if its an app causing issues.
simms22 said:
last_kmsg shows why something rebooted, they wont help on soft bootloops(or similar. first tjing to do is uninstall your apps, but i wont ask you to do that. instead, you should boot into safemode, and run that way. then youll see if its an app causing issues.
Click to expand...
Click to collapse
Thanks for you reply, but the soft reboots are very random. The last one was after an uptime of 100 hours. I'll do some further research...
When I had this issue a factory reset from TWRP fixed the issue for me. Happened multiple times per day prior and hasn't happened at all since.
I had a few soft reboots today and I'm currently on another kernel and it shows good results so far.
Zen hotlplug?
IntenseColor said:
I had a few soft reboots today and I'm currently on another kernel and it shows good results so far.
Click to expand...
Click to collapse
How are you installing your ROMs? Are you doing the recommended wipes before installing? Have you tried wiping cache and dalvik from recovery? Have you tried the aforementioned booting to safe mode? Also, consider a fresh start by flashing an entire factory image.
One more thing, you mentioned previously, that you had 100 hours uptime before a random reboot. That's a long time for continuous uptime. A regular, user initiated reboot is good for clearing memory. I usually try to do it once every 24-48 hours.
d08speed3 said:
Zen hotlplug?
Click to expand...
Click to collapse
I was always using the default settings.
Evolution_Tech said:
How are you installing your ROMs? Are you doing the recommended wipes before installing? Have you tried wiping cache and dalvik from recovery? Have you tried the aforementioned booting to safe mode? Also, consider a fresh start by flashing an entire factory image.
One more thing, you mentioned previously, that you had 100 hours uptime before a random reboot. That's a long time for continuous uptime. A regular, user initiated reboot is good for clearing memory. I usually try to do it once every 24-48 hours.
Click to expand...
Click to collapse
I always install the ROMs as clean as possible (I think) by doing the following:
I grab the latest factory image from Google and edited the flash script a little to the following:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot format userdata
fastboot flash bootloader BOOTLOADER.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio RADIO.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot format userdata
Then I fastboot flash the latest TWRP recovery, go to the recovery, format all partitions and then I flash the ROM and Gapps via a USB stick. I'm pretty sure the first part is not needed. But yeah I like having a clean phone.
I haven't gone to safe mode yet. The new kernel (leanKernel) I am using is showing great results so fat, no soft reboots yet. After I got the soft reboot today, I was getting it more frequently. So I am suspecting the kernel for the soft reboots. Chroma is using a tweaked version of HellsCore if I recall correctly.
I am not sure if this has something to do with the reboots but I am seeing this exception a lot after reboot:
Code:
E/AndroidRuntime(3617): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime(3617): java.lang.NullPointerException: Attempt to invoke interface method 'void o.CK.D()' on a null object reference
While I was sleeping I was getting another soft reboot, and found the same exception in the logcat. I'm not sure what to do now....
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
Old post, I'm guessing you've moved on, but...
What ROM was on the device before you flashed the 6.0? The boatloader updates with stock ROMs. I there is a 7 bootloader, it may interfere with the boot of a 6 ROM.
If you are unsure, you should always go with the newest stock release.
SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
I would try clearing the caches and/or userdata before manually installing the system partition again.
1.) Reboot to the bootloader. (reboot and press and hold the volume down button until booted)
2.) plug-in the usb cable
3.) Open your terminal and type:
Erase cache
Code:
fastboot erase cache
Erase dalvic-cache
Code:
fastboot erase dalvic-cache
Erase userdata
Code:
fastboot -w
Unlocked bootloader a year ago and using perfectly alright a week back try to flash stock rom through fastboot
When i flash fastboot it work fine for first 30sec then it's freezing not taking fastboot commands and just stays in fastboot logo
If i flash small files like boot.img, recovery .img, and few other files is working fine for first 30sec then it start freezing
Tried EDL too same happening in EDL mode also
what to do
Any know answer for this