So I think I know the answer but wanted to validate. If I leave the bootloader locked on my device and download a factory image from Google, cannot I just put the zip on the sdcard storage and run it through recovery to update? I don't think that I need to unlock the bootloader do I? I am trying to keep everything stock for now, but updates are a big reason I wanted this phone. Also don't want to break Android Pay.
View 4 RepliesI'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 came from getting my nexus 6P and I wanted to install twrp and etc... So I went to into developer mode, I check USB debugging and enable OEM unlock.
I head to my computer open a commend prompt that's has the fastboot and adb drivers. I connected my nexus 6p and I enter the following commends
Adb reboot bootloader
Fastboot devices
(Showed me my devices)
Fastboot OEM unlock
And just after I hit that I got the following
...
Failed ( remote : commend not found)
Finish 0.18
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
C:adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
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
[Code] .....
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 ?
View 3 Replies View RelatedOk, 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 ...
Is there a way to remove the warning on boot, after the bootloader has been unlocked.
View 8 Replies View RelatedI 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.
View 2 Replies View RelatedI 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.
View 2 Replies View RelatedAfter i unlocked my bootloader and rooted my phone, everytime i boot up my phone i have this msg and then the phone start, how do i get rid of this msg?
View 10 Replies View RelatedI noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main:
finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
View 5 Replies View RelatedCannot seem to flash factory image from Google. Trying to do it via adb but cannot push onto device. Says "cannot open no such file or directory". What can I try?
View 7 Replies View RelatedWith root/unlocking, the finger print sensor will be somehow disabled?
View 2 Replies View RelatedLast 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.
Is it possible to unlock bootloader, root, flash twrp and somehow flash the stock rom? If yes, where can I get the rom files for flashing with twrp?
View 9 Replies View RelatedThe Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button. Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame. This is no easy task, so the question: is there a way around this so that the phone can boot?It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
If I was to unlock my bootloader and root my phone, should I still grab ota updates?
View 4 Replies View Related128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, how to get it out of this.
View 10 Replies View RelatedJust 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.
View 5 Replies View RelatedI won a Nexus 6P at work but I have a device locked message when trying to enable USB debugging. Seems I have a demo handset but how I remove it?
View 3 Replies View RelatedI know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
So never had this problem on another phone before. I noticed a couple times this week where I doing something on the phone, and look up and my clock is like 15 min (or whatever) behind. Not sure if it's related but it seems to happen when I lose connectivity in so much as everything says I'm connected to WIFI or LTE but no data is moving. I'll have to keep an eye for that one but the time thing has me concerned.
View 5 Replies View RelatedMy phone is a HTC M7 ... My phone went flat one day after i charged battery and turned phone on it now goes straight to the boot loader screen which says LOCKED for some reason ... I can't seem to get passed this screen now.
View 1 Replies View RelatedThe whole range not just the bell vibrant. Is the bootloader on these things open? Anyone running froyo on it yet? Or any custom roms? Thinking of getting the TMobile version, but it'd be pretty useless with a locked bootloader
View 1 Replies View RelatedRooting (or Jailbreaking if you're used to the iPhone) is pretty awesome - it enables you to use a whole bunch of apps that are previously offlimits (such as Titanium Backup - a piece of software that will back up all of your .apks. It also enables you to remove some of the built-in bloat that Sony stuffed onto the Xperia Play which frees up a bit more space for new apps (Who honestly needs the Chinese keyboard on their phone?!)The classic way to root a phone is to first unlock the boatloader and then through that, install a version of your ROM that allows root access. However, although SE are providing a way to unlock the bootloader on a Play, this is not ideal because:Unlocking the bootloader automatically invalidates your warrantyWhen you have unlocked your bootloader, the software update function on your phone stops working as SE consider your phone to be "modified"Most phones are SIM-locked to a particular network and are therefore not even candidates to be bootloader unlocked The solution is to root your phone without unlocking the bootloader. How? A new application called Gingerbreak does it all for you! Literally, all you need to do is download the Gingerbreak .apk, run it and enjoy your new rooted Play. I can confirm that it is 100% working and took about 5 minutes from start to finish.
View 9 Replies View RelatedThe world knows updates in a Motorola phone is very slow! This leaves power users with no other option but to go for custom ROMs. Even there locked bootloader is always a very big problem! Moto promised long back to unlock bootloaders. Defy and Defy+ are now quite old phones and will receive no update either! So now is there any hope that the bootloaders will be unlocked? This deters most devs and power users from getting Moto phones inspite of an excellent build quality. Hope we get a reply and this thread don't die without any use!
View 6 Replies View RelatedI have purchased a S6 from Amazon, but the device is branded with Swisscom, with an awful boot logo and sound, and a few specific apps. I'm waiting for a nano sim, so for now I don't know if the phone is also simlocked.
I intend anyway to install custom roms, so I don't care much about this, however I can't find out whether the bootloader is locked or not (in which case, I'll have to send it back to Amazon I guess).
The device is a SM-920F, I made the OTA update to 5.1.1 upon powering it. Not sure what the bootloader and rom exact versions are, but I will add them to the post if necessary.
I accidentally deleted os of my ray. It is rooted with a locked bootloader, what can I do to boot it again. It was running on gingerbread.
View 3 Replies View RelatedMy Dad's HTC One M7 is stuck in the bootloader screen and is unable to boot to the main OS.
The phone has never been unlocked or rooted, I've never even seen the bootloader screen until now. The first thing it says in the bootloader screen is ****LOCKED****.
The only information I know is that prior to this, he was prompted for a system update which (he says!) looked official.
I've tried every option in the boot menu (fastboot, bootloader, recovery, recovery reset) and it just goes back to the main screen.
Is there a key combination that I'm missing? Was the system upgrade corrupt? I know next to nothing about Android bootloaders.
I have tried Googling for hours but all the results are from people trying to load a custom ROM or unlocking the bootloader - nothing about a 'normal' installation.
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
