Hello everyone,
After an OTA updates on phone, the phone phone got struck on "NO command" screen, but after some research i am able to get into bootloader.
Tried below solutions but failed:
1.Tried a factory reset, after this it restarted the device on struck on ERASING screen...waited for a long time it got into the loop of erasing mode.
2. tried fastboot options but no luck..
In fastboot screen it shows DEVICE IS LOCKED Status code: 0
Tried to unlock the phone with the unlock code but it says "Allow OEM enable" on the developer settings option but i cant as it got struck on fastboot screen...
Any help can be much appreciated.Thank you
mahi515 said:
Hello everyone,
After an OTA updates on phone, the phone phone got struck on "NO command" screen, but after some research i am able to get into bootloader.
Tried below solutions but failed:
1.Tried a factory reset, after this it restarted the device on struck on ERASING screen...waited for a long time it got into the loop of erasing mode.
2. tried fastboot options but no luck..
In fastboot screen it shows DEVICE IS LOCKED Status code: 0
Tried to unlock the phone with the unlock code but it says "Allow OEM enable" on the developer settings option but i cant as it got struck on fastboot screen...
Any help can be much appreciated.Thank you
Click to expand...
Click to collapse
Do the factory reset again, and just let it sit until it finishes which can be 20 minutes or more, some users have even claimed it takes an hour but I have never seen that personally... although you only really needed to clear the cache partition but it is too late for that now.
Related
I need help in recovering a two year old Nexus 4 to usable state.
It went into a loop while in use. Background and symptoms are as follows:
1. OS was OTA updated to Lollipop and was used for several days before problem occured.
2. Now, on powering on, the device remains indefinitely (checked for 30-40 minutes) in the loop displaying 4 coloured shapes going in circles.
3. At first, I tried factory reset, but that failed showing errors like failure to mount /cache etc.
4. Device can be put in fastboot mode (showing product, variant etc.), but always with "locked" state.
5. I used Nexus root toolkit 2.0.4 for attempting recovery. The device is detected in fastboot mode.
6. I tried to unlock bootloader. But it fails to unlock. After selecting unlock option with volume-up and pushing power button, device seems to unlock, but it then boots into the loop similar to the one after power-on. Powering off and putting the device in fastboot mode shows the device state as "locked" again.
7. "Flash stock + unroot" with "soft-bricked/bootloop" option attempts to write to the device but fails at every step with the reason: FAILED (remote: not supported in locked device). This happens 7 times during flash and once during postflash boot. I repeated the exercise with "force-flash mode" and "post-flash factory reset" checked as well, with same failure messages.
8. FYI: I have downloaded the factory image "occam-lrx22c-factory-86c04af6.tgz". It is verified by NRT as OK.
Based on this, I feel that unless the device can be "unlocked", writing to it and recovering it will be difficult.
Can anyone suggest a different set of steps / different recovery program, which may help?
I have read similar threads on this forum, but could not get a complete set of "instructions + working links to tools" from those threads.
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
kyuuku said:
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
Click to expand...
Click to collapse
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
dottat said:
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
Click to expand...
Click to collapse
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
kyuuku said:
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
Click to expand...
Click to collapse
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
dottat said:
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
Click to expand...
Click to collapse
Ahh that's too bad. It was what I expected though.
Thank you anyway for the help!
Hi everyone. A friend of mine gave me this falcon to revive.
He just unlocked the bootloader and never booted again. When it starts, it gets frozen after the world bootanimation in this retroiluminated black screen.
When i go to the fastboot screen and reset the device to factory state, the phone stays the same. When i go to Recovery mode appears there's no command. And i got to press power+up several times 'til 'Recovery' pops out. But when it does, none options makes any difference (factory reset, cache and data user reset, etc).
I tried to push a rom or install with adb from this recovery, and tried to install a new rom in fastboot. No matter what i do, it always stays in this black screen after the bootanimation.
I left it turned on for a day and nothing, i charged and nothing, i try some other versions (5.0, 4.4) and nothing.
If there's something that isn't clear or any question and solutions, tell me.. i will give you any information. Thanks.
Thanks all for reading and please help!.
Recently I found out my device having battery drain quicker than normal, then I decided to do a factory reset. But the factory reset is taking much longer than usual (usually its around 4-5minutes but this one takes more than 10 min). I thought there must be something wrong and I decided to do a factory image flash.
When I tried to unlock the bootloader the device freezes at the screen where there's two option (unlock or do not unlock) after I selected the unlock option. Waiting did not help so I did the good ol power up + volume down combo and the device arrive at bootloader mode unlocked. I then proceed to do the factory image flash and at the end of the it says
Erasing 'userdata' FAILED ERR(Check device console) <-- something along those lines
and the device does not auto reboot after the flashing is done like it normally does
It took a few reboot to get the device to setup screen and after the setup the device is working fine (for now) and the battery drain still persists.
Any idea on what is going on with my devices? I've tried factory image flashing and sideloading ota updates with no problem and this is the first time I encountered one. Any help would be appreciated :fingers-crossed:
Did you read this https://developers.google.com/android/images especially the part that starts with For Pixel 2 XL only. I would also make sure you have the latest platform tools and try a 2.0 usb port and maybe a different cable .
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device