Database Users

[Q] Boot loader stuck on unlocking now

I cannot unlock my bootloader. I have a Nexus 16 wifi with 4.2.1 and no other hacks or mods applied. Bone stock.
When attempting this through the Nexus root toolkit or Nexus 7 tool kit or through a fastboot command line device says unlocking now but does not reboot afterwards. When manually rebooting device is not unlocked. I will also add that my device is encrypted through the software provided on the device. Also I cannot factory reset the device through the UI or through the bootloader. Again it says it's doing these tasks but upon boot up I am still asked for my storage unlock password and the device is still back the way it was pre wipe attempts.
Other strange behaviors indicating a wipe attempt are random reboots, Andriod OS process consuming > 40% of my battery. Also device installs the same app updates every time I reboot or if the device reboots on it's own.

I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7

No dice
duffieldj1 said:
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
Click to expand...
Click to collapse
Unfortunately the only way to un-encrypt device is to reset it to factory spec again which it will not do no matter the method tried. The drivers are correctly installed via the toolkit. The tool kit shows that device serial number. I have installed the SDK and have tryed that method via fastboot 'fastboot oem unlock'. I then follow the directions on device and press the power button. Device is stuck at 'Unlocking now.....' However nothing happens. It does not automatically rebooot or wipe device. When I push the power button the device boots normally as if nothing had happened. Also bootloader is still locked. If I can get it unlocked I think I should be able to wipe it.
Output from command:
C:\Users\Scot\Downloads\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platfo
rm-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 31.029s

Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.

bftb0 said:
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
Click to expand...
Click to collapse
Wondering too if this is an unintended consequence of encrypting the device. So now that it is encrypted if the device is lost or stolen it's no good to anyone as there is no way to reset it back to a functional device. There has got to be a way to around this. I travel quit a bit for work and that is the only reason I chose to encrypt was in the event it was lost or stolen.
I have an RMA number open with Asus in the event that this cannot be figured out. Really though it is not a hardware issue, it's definitely software related.

Encryption and infinite loop

Save save technology myths, to with a very big problem here, once the XDA released the preview of Android L for the Nexus 4 I installed on my machine, everything went well for quite a while, until one day the phone opened an APP "encrypt" the machine, and restarted, the process lasted about 40 minutes, and then it ended, I called the appliance and to my surprise was the following message: "type passowrd to decrypt storage", and a place for me to enter the password.
Was the beginning of my despair, I had not entered any password or PIN, or those design patterns android... The device simply was encrypted with a password which I did not know what it was.
To tackle started with the basics: with the recovery already installed I did the procedures to restore factory defaults, and connect to my surprise, the message was still there, then went back to recovery and wipe gave in practically all I knew I could give, I called, and again the message was there. Not knowing what to do and already pissed off, I left the cell phone away, and another time when I connect it to my surprise it was an infinite loop.
That's when the idea to install android again, and when I went to "install zip from sdcard" received the following message: "and can not mount / sdcard".
Today I have done the installation procedures via fastboot and ADB or where they do not recognize the device for his fact not be connected with USB debugging.
Anyway, do not know what else to do, I've used all my knowledge and nothing to solve this problem.
Please, help-me

You're going to want to flash the factory image in fastboot. Google 15 second adb install. That had usb drivers. Once you install it boot your phone into the bootloader and connect it to the pc. Type
fastboot devices (in a command window).
If your device is recognized proceed to flashing the factory image.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You're going to want to flash the factory image in fastboot. Google 15 second adb install. That had usb drivers. Once you install it boot your phone into the bootloader and connect it to the pc. Type
fastboot devices (in a command window).
If your device is recognized proceed to flashing the factory image.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much! I had tried all the fastboot and adb and nothing to fix.
I found a good video that explains how to do an installation via fastboot and unable to solve.
Note: It was 15 days without cell

Nexus bricked: What to do?? / What to do if computer turns off in the middle of flash

Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!

This can be done without a toolkit, Flashing factory image with fastboot instead.
Toolkits cause many of the issues on here, learning to do it manually with fastboot can both avoid issues, and fix issues. And teach people valuable skills.... As adb/fastboot are essential tools, especially with a Nexus. ?
But thanks for the info. Contributions like this are always good. ?

Problems with "Boot Failed"
visnkmr said:
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
Click to expand...
Click to collapse
Well I had a different kind of problem.
My Nexus was running fine in 4.4.4 when I rooted it since it was out of warranty. It upgraded to Lollipop 5.0 without a problem and continued to function in rooted state.
It made several attempts at updating to 5.0.2 but always ended with "Failed" message. I figured unrooting the device might help with the OS upgrade. It did not and screwed up everything. I then Set it to Factory default and it went to wiped 5.0 state. Then disaster struck. I tried rooting it , unfortunately with older Chainfire which bricked the device and would not let me install 5.0. So I tried to force install 4.4.4 and then the device got bricked. I simply get the message "Boot Failed" I boot into fastboot mode and I get the basic display with green start in the upper right corner, large Android icon in the center of the screen and the standard fine text on the lower let side. Unfortunately Windows ( x64 - Ultimate) insists on recognising the device as "Unknown Device" and when I go into properties this is is what is states ...
"Windows has stopped this device because it has reported problems. (Code 43)"
Do you think I might have better luck if I tried this on a Win XP machine ? I have both, x86 and x64.
Now, can you please tell me how I can get around this problem ?
BTW I do remember olden days of Cassiopeia PDAs before the flash memory came on the stage. The original OS would be on a plugged in masked rom daughter board in the event of losing all battery power. You could always force it to load it and get to factory mode. I think it is high time Android device manufacturers reverted to this process. I believe it can live side by side with the current system at a very marginal higher cost but have a whole lot of satisfied and LOYAL customers. It would give the user ability to go to factory mode albeit without any OS updates/upgrades but a fully functional device.
Would very much appreciate your feedback.

Failure during rebooting Nexus 7 2012 wifi while downgrading from Lollipop to 4.4.4

Hi there,
I need help with my Nexus 7 2012 wifi (grouper). I tried to downgrade it from Lollipop to Kitkat 4.4.4 but I had a problem during the rebooting process and the screen froze while uploading the system files to the tablet. I think the problem was due to my usb cable. All I get now is a black screen with Google written in the center and an unlocked lock in the bottom. Is there anyone there able to help me?
Let's go through the entire process.
I downloaded the original factory image for my device from Google Developer's. The image I used was the nakasi 4.4.4 (KTU84P).
After downloading the files and putting them all in the same folder, I started the process.
Here is the step by step, followed according to Factory Images page instructions:
1. Enabled USB debugging mode in the tablet
2. Connected USB cable
3. Ran Command
4. "adb devices" to check if the device was connected, which was listed as "unauthorized"
5. "adb devices" again to authorize the device, now I read "device"
6. "adb reboot bootloader"
7. "fastboot oem unlock"
8. "flash-all"
9. screen frozen at command line "sending 'system' (6nn.nnn KB)..."
So, at step 9, while flashing the device, the screen got frozen at that command line, nothing else happened, it seemed that the device had lost connection with the computer (usb port was kinda loose actually). So, after waiting more than 10 minutes, I unplugged the usb cable (I know we should not do it while restarting, but everything seemed lost already). I tried "adb devices" several times, but nothing. Then, I reset the device using the power and volume down buttons, but now all I see is a black screen written Google in the center and an unlock lock in the bottom.
Does anyone there have an idea of how to recover the tablet?
Thanks,
Alex

Hi,
After a couple of hours of trial, I finally managed to access the reboot mode again in my Nexus 7 using power+vol down buttons BUT only after keeping power button pressed until reboot mode was loaded (I was releasing the buttons after screen went off). Although the first reboot was stopped during system upload, I was able to start it all over again following the steps in the Developer's instruction.
This time, I lefted it processing, with the same apparently frozen screen, and after almost 20 min system installation was finished. In the end, it was only a matter of time. Shouldn't have unplugged the cable the first time after only 10 min.
So, problem solved, case closed.

alexrock82 said:
So, problem solved, case closed.
Click to expand...
Click to collapse
And now the tablet is fast as new with Kitkat 4.4.4 instead of the slow turtle upgraded Lollipop.

BIG PROBLEM! Moto C without solution! Throw it away? Or is there a Bad#@ there to help me?

I think I have an unsolved problem. I know it doesn't exist, but it's very hard to find it.
I know it's not the Plus, but the Model is the Moto C XT1754 (NAMATH) Android 7.0 Nogaut - NRD90M.060
And there is no specific topic for it, but they are very similar and I thought I could post it here.
It's a very complicated problem, so I'll explain in detail what happened and why I had to come here to solve it.
(translated)
- STARTING:
I installed a TWRP through the app, without unlocking the Bootloader.
Whenever I turned it on, at boot still, the message appeared:
'red state
Your device has failed verification and may not work properly
Your device will boot in 5 seconds'
But it called normally.
I installed 'Magisk Manager 24.2' by zip and app afterwards.
I activated 'Zygisk' and in DenyList I activated/hidden from Google Play Services completely. All.
I restarted the smartphone and Sitema started having numerous errors. Most of the apps that I opened, closed with error, and other apps in the background too, mainly Google Play Services.
I tried to solve this but I couldn't because the smartphone was unusable.
I decided to format by TWRP.
But when I tried to restart the device, I always entered TWRP and continued that message in Boot ('Red State Your Device...')
I decided to reinstall Stockrom from Moto C XT1754.
When I tried to install Stockrom through flash_tool, I couldn't.
It always gives error.
'BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
[HINT}:'
or this one is the most common:
'BROM ERROR : ?? (0x1)
[HINT];'
I even tried installing a Custom Rom via Sdcard , 'Viper-namath-20171206-Coral-v3.1.1-UNOFFICIAL' with the GAPPs, etc.
I can install the ROM. (but the GAPPS gives an error at the end of the installation) 'open_gapps-arm64-7.1-micro-20220215'
But I think this case is because it is not installing the Custom ROM correctly. (Because of the Locked Bootloader? Maybe... I'm kind of a layman on the subject)
Because when I restart the device after installation it goes back to TWRP.
I can't get into Fastboot mode with the command by the buttons on the device, only by TWRP when I access 'Reboot>Bootloader'.
Reboot and go to fastboot (Black screen, down there written '=> FASTBOOT mode...'
I've already tried to recover/rescue the device by Motorola/Lenovo's 'Rescue and Smart Assistant'. But when I try to rescue it (with it connected to TWRP) it asks to accept the message to enable USB debugging.
But I don't have access to this window through TWRP.
Here comes the big question, why I am not able to solve my problem:
I think my 'USB Debugging' was off/disabled before I erased everything (formatted).
I'll try Stockrom's Flash through TWRP to see if it solves the problem, but I don't think it will.
I think the problem may be with the 'USB Cable' as well. He's old. I tested with a non-original USB cable that I had to see and I can't either, the errors persisted.
I plan on getting another original to test as well.
Just an observation.
My device is being recognized as 'USB MTP Device' (under 'Portable Devices')
If anyone can save me, I'd really appreciate it!
Thanks in advance for all the help! Every opinion matters!

And when I give the command 'ADB Devices' my device appears 'unauthorized'
'ZW3223CGWK unauthorized'