So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.
Related
Hi,
Now that ROMs are starting to come out for the Prime. The only thing that I would need if I was to unlock the bootloader and install a recovery is the capability to flash back to stock (Yes I know that the bootloader will still be unlocked).
So is it possible to flash a stock rom or ota using clockwork mod recovery?
boomtopper said:
Hi,
Now that ROMs are starting to come out for the Prime. The only thing that I would need if I was to unlock the bootloader and install a recovery is the capability to flash back to stock (Yes I know that the bootloader will still be unlocked).
So is it possible to flash a stock rom or ota using clockwork mod recovery?
Click to expand...
Click to collapse
No, you cannot restore a stock Asus-provided update. It will, apparently, brick your Prime.
However, given that the first thing anyone would/should do is take a nandroid backup, you can always restore that and be back on your stock ROM.
Will it be ever possible to flash stock so that we can get the latest updates still? Or is this a techical impossibility due to the way asus apply their OTA's?
boomtopper said:
Will it be ever possible to flash stock so that we can get the latest updates still? Or is this a techical impossibility due to the way asus apply their OTA's?
Click to expand...
Click to collapse
No. That is one of the things explicitly states in the waiver you have to agree to in order to unlock the bootloader.
From the bootloader unlock terms:
" the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates"
Yes I had read and understood that part but I was alluding to whether the community could work out a way or whether it's completely impossible?
Well someone will put up a stock zip you can flash which is just a different way of getting the stock ROM. Usually it takes a few days for one to show up after an ota though. There is a stock .15 zip in development now. You'll still have root.
Thanks.
I've found the thread about the stock .15 which is installable with unlocked bootloaders.
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
aophyz said:
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
Click to expand...
Click to collapse
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
Click to expand...
Click to collapse
Terribly sorry, but I meant to write "not out" instead of "now out"
And yes I have read that and keep checking back every couple of days to see if the AT&T one ever shows up.
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Reverted back to "Locked" bootloader, but still get error when updating to 5.1.1 OTA
I just used Nexus Root Toolkit 2.0.5 to revert back to an OEM "Locked" state which I ahd confirmed by rebooting into bootloader. The reason I did this was so I would be able to update my device with OTA updates, but I keep getting an error every time I try to update to 5.1.1.
What are my options?
Unlock, flash Nexus Factory Images.
From what I've read if you get a failed OTA install it won't let you un-root, re-lock, etc... and take the OTA. This is to protect your device.
ETA: Do you even have to have the BL flag locked to take an OTA? I don't think so...
livinginavacuum said:
I just used Nexus Root Toolkit 2.0.5 to revert back to an OEM "Locked" state which I ahd confirmed by rebooting into bootloader. The reason I did this was so I would be able to update my device with OTA updates, but I keep getting an error every time I try to update to 5.1.1.
What are my options?
Click to expand...
Click to collapse
NEVER NEVER NEVER NEVER NEVER LOCK YOUR BOOTLOADER!!!!
1) This does not in ANY WAY impact OTAs.
2) This has the potential to *LOCK YOU OUT*.
Get your updates here:
https://developers.google.com/android/nexus/images
So then how can I go back to being able to update via OTA?
livinginavacuum said:
So then how can I go back to being able to update via OTA?
Click to expand...
Click to collapse
If you want to get OTA's, fastboot flash the stock system.img and boot.img > https://developers.google.com/android/nexus/images
But if you're going to do that, why not just fastboot flash the 5.1.1 factory images?
As posted above, do not relock your bootloader. It does not impact your ability to accept OTA's and can end up bricking your device.
cam30era said:
If you want to get OTA's, fastboot flash the stock system.img and boot.img > https://developers.google.com/android/nexus/images
But if you're going to do that, why not just fastboot flash the 5.1.1 factory images?
As posted above, do not relock your bootloader. It does not impact your ability to accept OTA's and can end up bricking your device.
Click to expand...
Click to collapse
Is there an idiot's proof guide to this?
And besides helping me unlock my device once again as you guys recommend, can the Nexus Root Toolkit make my life easier by flashing the the stock system.img and boot.img so that I can get OTA's?
livinginavacuum said:
Is there an idiot's proof guide to this?
And besides helping me unlock my device once again as you guys recommend, can the Nexus Root Toolkit make my life easier by flashing the the stock system.img and boot.img so that I can get OTA's?
Click to expand...
Click to collapse
Here's a guide. Note: use the "Long method" > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Toolkits are OK if you understand how to fix a problem when you run into trouble. I'd suggest that you use the manual method, but it's your decision. There's a thread in the Development section for NRT if you choose to go that way.
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands