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.
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!
Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!
First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img
If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app
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
2 days ago i woke up to my phone's screen already on, it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but when it turned itself back on the phone was now stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. I have unlocked the bootloader (also done critical unlock) but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this? It's not rooted and the bootloader had never been unlocked previously.
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
ricardohorta said:
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
Click to expand...
Click to collapse
"bluetoot_a" is the first thing it tries to flash through mi flash. Its also the first thing in the images.
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
ricardohorta said:
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
Click to expand...
Click to collapse
Im not able to boot into twrp, it just hangs on the splash screen.
It should load directly from the bootloader.
Maybe you can try different TWRP versions, maybe it helps.
Xiaomi Mi A2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There are some instructions also.
rxsta said:
Im not able to boot into twrp, it just hangs on the splash screen.
Click to expand...
Click to collapse
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Sorry @User699 I was out of town, but I'm back now. What's your current status ?
User699 said:
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Click to expand...
Click to collapse
When i boot this version of twrp, the screen goes black for a bit but then just reboots itself.
Finally booted but still hanging on splash screen.
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
User699 said:
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
Click to expand...
Click to collapse
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
rxsta said:
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
Click to expand...
Click to collapse
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
Doubt there's anything else I can do.
Think it's important I also mention that I can't get into the phone's recovery.
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Click to expand...
Click to collapse
Does your device display anything on its screen?
User699 said:
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Does your device display anything on its screen?
Click to expand...
Click to collapse
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
rxsta said:
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
Click to expand...
Click to collapse
I wish you the best of luck!