Database Users

[Q] Nexus 7 2012 Wont boot after update

I have been working with Android for a few years now. My Nexus 7 has no problems. A friend tried to update her 7 to 4.4.4 via the standard system update. Hers was completely stock, not rooted, not unlocked. She ended up stuck in the bootloader afterward.
The bootloader is locked. When I try to unlock it I get the following error.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (unknown error code))
finished. total time: 5.299s.
I have tried 2 computers, 3 usb cables. I have tried WUGS toolkit as well without luck. Nothing seems to get this bootloader unlocked.
Is there anyway to flash the factory files with a locked bootloader?
Any other options?

@gotbeer: Have you tried unlocking it with fastboot?

Sadly the string above is what I get when I used fastboot to unlock.
fastboot oem unlock
I have completely drained the battery and am going to try again. Three other Nexus 7's and a Galaxy Nexus and Ive never had a problem with unlocking the bootloader. Im beginning to suspect a hardware failure on this one.
Is there another way besides fastboot to unlock the bootloader I can try? The system partition is erased so I cant get into there to do anything. Im sure she never enabled USB debugging, so ADB is out of the question?

[Q] Nexus 7 - bootloader unlock fails

My N7 may be on the way out, but I'd like to give it one last try:
For the last couple weeks it's been intermittently shutting off, or just freezing. This was happening in safe mode, too.
I did a factory reset, that seemed to help for a few days. It started acting up again, also in safe mode.
I tried one more factory reset, but that seems to have failed. I couldn't get past the Google splash screen.
I got into recovery mode and tried another reset, but couldn't get any farther than a message that said "erasing cache..." ( I have the exact message written down somewhere).
I then attempted to reflash everything. Because it's locked, I needed to unlock it first. But unlock fails.
This is what I get at "fastboot oem unlock".
I see in the upper left corner "Unlocking now......"
On the CMD window I get this:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) erasing userdata...
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: xxx s
The N7 fails to unlock. I've searched some other forums and there are some who think that it's a hardware failure. Are there any other things I can do to troubleshoot?

Try another cable, Another port on your PC... And lastly perhaps a different pc.

KJ said:
Try another cable, Another port on your PC... And lastly perhaps a different pc.
Click to expand...
Click to collapse
Have tried some different combinations - will try a few more.

No joy,
Multiple computers, multiple USB ports, multiple cables.
All result in the same thing - unable to unlock:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) erasing userdata...
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: x.xx s

Then it unfortunately sounds like hardware...

That's the direction I'm leaning. I am able to communicate with it via USB, and can get to the "are you sure you want to unlock" screen. When I select "yes" there is no data being transferred via USB, it's all an internal function that should run. But it will always fail with "unknown error".

Possible Bricked?

Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"

i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?

Use the Qualcomm recover method mentioned many times over in this forum.

try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?

Re-unlocking bootloader problem

I have a OnePlus 2 phone which has its boot-loader unlocked at some point and I accidentally re-locked the bootloader and was unable to flash through fast-boot and I'm now unable to root the phone.
I have TWRP ready because I flashed it earlier before i re-locked the bootloader.
I am able to boot to the OS, fastboot and TWRP recovery mode.
However rooting seems impossible for now.
Whenever I tried to unlock bootloader it shows:
C:\adb>fastboot oem unlock
...
OKAY [ 0.122s]
finished. total time: 0.122s
However, after trying to check if the device is unlocked, it shows that I didn't actually unlocked the device, rather:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.063s]
finished. total time: 0.063s
This is the only problem that I've received from my other phone, I used to root my 1+1 and it went well without a single problem.
And this is my first post (not like you guys care anyways) and I don't really know where to post my troubles so I apologize if I posted this in the wrong place.
Any suggestions / help would be very much appreciated.
Thanks in advance~
Kev.
[EDIT]
I have tried various methods to restore the phone when soft-bricked with SuperSU, and it works, however it doesn't allow me to reset the bootloader's status and I'm not capable of doing so.

Did you enable OEM unlocking in Developer settings?

moto g4 play stuck in bootloop after official motorola update.

Hi, i updated my moto g4 play (xt1602) to the android update in india. Unfortunately it is in bootloop and wont start to lock screen. Oem is locked and usb debugging is disabled. developed options also not enabled. i used LMSA (Lenovo moto smart assistant) to recover it by flashing original firmware but it is still in bootloop. i have searched on google and forums and found that due to these i.e.(Oem is locked and usb debugging is disabled) i cannot flash any recovery and cannot install any rom through fastboot. Also "adb devices" command does not recognise but "fastboot devices" command shows serial number of my device. i also got oem unlock code from moto website but it said remote failed for "oem unlock" command in fastboot.
(Also i was wondering is there any way that i can edit oem.img and bootloader.img file in official firmware that LMSA downloads and flashes in the device and can that unlock the oem and bootloader )
Is there any way to recover the device or is it bootloop bricked to eternity.
Note: i had my screen replaced and after that i did the update. can it be the issue. (i' ve kept the old broken screen module, can it help recover the device if it is connected.)
Thanks in advance

Can you paste the code of the error?

IkerST said:
Can you paste the code of the error?
Click to expand...
Click to collapse
fastboot oem unlock
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.031s
Now since its bootloop i cant do anything

Try this, and then flash firmware
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase system
If it doesn't work contact me on telegram (so it's easier to communicate) @IkerST

IkerST said:
Try this, and then flash firmware
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase system
If it doesn't work contact me on telegram (so it's easier to communicate) @IkerST
Click to expand...
Click to collapse
fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.283s]
finished. total time: 0.286s
fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.148s]
finished. total time: 0.153s
fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.133s
so system erase failed.
further flashing firmware with LMSA. phone still in bootloop.

I'm having same issue with my Moto G4 Play. Have you found any solution?

sreekanthpp said:
I'm having same issue with my Moto G4 Play. Have you found any solution?
Click to expand...
Click to collapse
Unfortunately its a paperweight to me now. After having tried all i could, I gave to 4 mobile repair shops and after about half a day trying, they have all given up.
If anybody does find a solution kindly let us know.