Google Nexus 5 :: Bricked Phone - Cannot Unlock The Bootloader
Oct 1, 2015
My nexus 5 just turned off and is stuck on the boot animation. I am able to access the bootloader and have already tried to wipe cache and performed factory data reset but the phone is still stuck on the boot animation. I have tried to unlock the bootloader with 1-click-nexus-5-bootloader-unlock as well as CF-Auto-Root-hammerhead-hammerhead-nexus5 tools but after I accept to unlock the bootloader, the phone reboots and gets stuck on the boot animation. The bootloader status remains locked.
I forgot my unlock pattern and I don't have my device in ADM ... But the bootloader is unlocked, so I think I can install any image I want, right? Could this be a way to get into my device? So any solution to unlock my device without doing a hard reset?
Bought a nexus 5 for the youger bro last year and rooted so he could install kodi.What ever messing about he has done there is no image on the phone so is soft bricked.The phone waas rooted and the boot loader unlocked also you can access twrp.What can i do to restore from a nexus 5 image as i have no backups.
I have a nexus 5 that I was preparing to hand down to my wife. I had transfered everything over to my new phone, and initiated a factory reset. It rebooted to the "erasing" screen, and sat there for about 20 minutes, before switching to the dead android screen (w/ red triangle.) I thought that was odd, did some searching, and tried the recovery mode from the bootloader. That produced the same results. So now I'm stuck.
From the boot loader I can access the following options:
Start -> Erases for ~20 minutes, then dead android Restart Bootloader -> Screen goes blank, phone vibrates, and then back to the bootloader screen Recovery Mode -> Erases for ~20 minutes, then dead android Power off -> turns off the phone
I called Google, and the tech support hadn't heard of anything like this. Because it's almost two years old, he transferred me to LG's tech support, who basically said find a local repair shop, or they could RMA it for an unknown cost.I'm pretty sure the phone is bricked at this point, which is frustrating, because it was running stock android - completely unmodified. I think I might have rooted it once, months ago, but I can't imagine that that would have caused this issue. I had even received and installed Marshmallow OTA, and it was running perfectly.
Anyway, some program I might be able to use on the PC to regain access to my device.
Literally the only information I can provide about the phone at this point in time is as follows: Product_Name - hammerhead Variant - hammerhead D820(H) 32GB HW Version - rev_11 Bootloader Version - HHZ12k Baseband Version - H8974A-2.0.50.2.27 Carrier Info - None Serial Number - 047.... Signing - Production Sercure Boot - Enabled Lock State - Unlocked
so I was trying to flash the latest Nexus build to my Nexus 6, but the bootloader was taking 10+ mins to flash, so I tried closing out of cmd and then restarting my phone into bootloader. Unfortunately, now, my computer doesn't recognize my phone, saying that the drivers are no bueno, so that when i type fastboot devices nothing shows up.
I'm sure many of you have heard that when you enter an incorrect pattern/PIN/password, eventually the phone asks for Google account credentials to unlock it. My Nexus 5 on 5.1.0 does not do this. Does yours? If my lock screen is set to PIN, I can enter as many incorrect attempts as I want, it never asks and never stops me. If I have a pattern set it will let me enter 10 incorrect attempts after which it simply stops me from trying for 30s, but it never asks for Google account credentials.
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:adb>fastboot devices ertyugg(this edited for privacy) fastboot
commands: update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition
[Code] ....
Message shown :
options: -w erase userdata and cache (and format if supported by partition type) -u do not first erase partition before formatting -s <specific device> specify device serial number
Just wanted to upgrade my sisters phone which was running an old 5.1 version (custom rom, so the phone was unlocked and rooted already) to an android 6.0.1 custom rom. So I flashed newest twrp and flashed 6.0.1 bootloader and radio.img via fastboot using wugfresh tool and the files from the thread on here. now when trying to get into recovery, I am stuck at the google logo.
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
I haven't received mine yet, but probably one of the first things to do is unlock the bootloader. Does the fingerprint verification/ unlock still works with an unlocked bootloader.
I am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
Last year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.
From last week my phone got stucked at boot(Google logo). I went to recovery mode-twrp and clicked factory reset..it failed saying that unable to mount storage.
And I also tried nexus tool kit, To flash lollipop stock rom, It say flash write failure..
And tried fastboot flash all.bat method also but not works...
I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not: Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there.
my Nexus 5 has recently run into a problem where it suddenly decided to get stuck in a bootloop. I figured I could just reflash the stock rom via the boot loader with the wugfresh root toolkit but that unfortunately didn't work. But by doing this I noticed that my bootloader was not staying unlocked when I try to unlock it. Every time I unlock the boot loader and it restarts the bootloader automatically re-locks. I then proceeded to try and manually flashing the stock rom files individually and unlocking the bootloader each time I flash a file which was really annoying. It still hasn't worked and I'm starting to get worried because I've also started to notice my recovery can't really factory reset or wipe the cache. Instead I get this message at the bottom of the screen:
E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/log E:Can't open /ache/recovery/log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_log E:Can't open /ache/recovery/last_log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_install E:Can't open /ache/recovery/last_install E:failed to mount /cache (Invalid argument)
So now I'm completely stumped, could this be the end of my Nexus 5?
I wanted to test marshmallow so I decided flash xtra smoth rom by daniel84cs.as I am coming from lollipop so I flashed bootloader and radio of marshmallow but then I stuck into bootloop somehow I managed to get my backup restored now I am back to lollipop as I have done a factory rest before restoring so I should need to flash lollipop bootloader and radio again or I am good to go?
Will rooting my nexus 5 without unlocking the boot-loader void my t mobile warranty? My Phone is an LG Nexus 5 running the latest Version of lollipop and the only reason i want to root it is to be able to connect my ps3 controller to it and play emulators or minecraft...
My phone used to ask me to unlock to start the android operating system when I would turn it on and after it booted up. I did a safe boot and now since then, it no longer asks me to unlock it upon turning the phone on. It just asks me to unlock it after it boots to the main screen.
Which is the norm? And if its normal to ask to unlock when it first turns on, how can I get that to come back? I'm stock/not rooted.
step 4 is where things get funky, when I tell bootloader to load recovery mode the phone restarts and then boots normally.I've been hacking at this for a few hours, and ended up loading the boot.img file more than once (see steps below) -- the original attempt worked and would access recovery mode the "load from zip" option wasn't available to I started tinkering, at one point I told it to restart from recovery mode -- it listed updating 7 files after which it had flashed itself back to factory defaults.I then flashed the boot loader a 2nd time it stopped accessing recovery mode
since then I've tried - download Quick Boot app (crashes when trying to load recovery mode) - flashed with fresh factory image - numerous attempts to restart into bootloader - voodoo chanting (not really but that's next)
after the reboot the only thing my screen ever displays is garbled colored pixels even after pulling the battery. Fastboot still works just fine, so I tried wiping everything and reflashing but it still never shows anything but this screen. I even tried reflashing older versions of the bootloader and nothing works.
After OTA update device got stuck on Google logo and somehow recovery is missing, Android on it's back with red triangle. Is there way to fix it with locked bootloader ?
I've a Nexus 5, stock rom 4.4.4, rooted. Since 3 or 4 days I have unwanted reboots. And today, my nexus powered off and didn't want to reboot.
Even I press the power button for a long time (more than a couple of minutes) , nothing happened. The only thing I got, is when the device is plugged on usb charger : the nexus boot on the google logo then switch off and boot again on the google logo then switch off again and again and again....
I can't access bootloader or recovery... If the device is bricked, I just want to recover my. Is the flash memory could be recovered?
Is it possible to make a backup of bootloader? If it is, how? I am not talking about kernel (boot.img is the kernel, correct?), system, recovery, or data. Bootloader.My Nexus 5 came with bootloader version hhz11n. The factory image from Google (4.4.4) has bootloader version hhz11k.
How different these two are, but since hhz11n image can't be found anywhere, I want to back it up before flashing to Lollipop or Marshmallow.
My Nexus is still running 4.4.4, bootloader unlocked, rooted, with TWRP installed.
So, I turned on my phone and now it goes straight to the bootloader. So, when I select "Start" option, screen turns black (can still see backlight shining though). It was sitting there for hours, but screen stayed black.
I did have a rooted phone, but I hadn't tinkered with it for about 6 months.
Is there anyway on kitkat 4.4.2 to root the phone without opening the bootloader or setting my device on USM (USB Mass STorage)?I think not as I'm searching on google since 2 days but still maybe some genius around here has something for me ?I need to do some recovery on my device but I can't because I'm not root.
