Related
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?
Hey,
So I updated my Nexus 9 with today's OTA, after which I'm greeted with the dead android 'No command.'.
I've attempted to wipe the cache data and factory reset from the recovery menu, and factory reset from the power + volume down menu.
My boot-loader is locked as I've never felt the need of rooting or running custom roms - so the tablet is entirely stock.
I also attempted to run fastboot which is throwing errors due to the boot-loader being locked.
I tried to re-apply the patch using adb from the recovery menu, however after the patch is verified I'm receiving this error: system partition has unexpected contents
Is there anything I can do to fix this myself at this point?
I've contacted Google but haven't heard back from them yet.
Any help is greatly appreciated or guidance!
Kind Regards,
Since you already factory reset your device (and lost your data) the best way to recover is flashing the whole factory image.
Just unlock the bootloader and flash the latest factory image following the instructions from here:
https://developers.google.com/android/nexus/images
The problem is, I never enabled USB debugging so my bootloader is locked or am I missunderstanding this?
Cellzor said:
The problem is, I never enabled USB debugging so my bootloader is locked or am I missunderstanding this?
Click to expand...
Click to collapse
It's not USB debugging that is necessary in your case. It's the option to "enable OEM unlock".
PS: Two hints for future success on XDA: 1) don't post questions in the General Section. 2) Don't double post the same question.
I was rooted and tried to do a flash stock plus unroot with no wipe using the new LM48YI image on a n9 wifi with lmy48x using the wug toolkit and ran into the same issue yesterday. In my case, multiple restore to stock/reset did not help and the device hard bricked during a reset. The fact that this happens on stock unrooted devices is very very worrying to say the least.
add me to the list of completely factory N9's getting bricked from the OTA. All I can do is get into fastboot and any reboot will just sit at the spinning dots forever. Most fastboot commands just get denied since the device is locked. Thanks google. Looks like it is email to google time or just throw it away.
My wifes Nexus 9 is now in the same boat. From what I can tell, you cannot run the "fastboot oem unlock" command successfully unless you had previously checked the "allow oem unlock" button in Settings. When trying this I get this:
<bootloader> ability is 0
<bootloader> Permission denied for this command!
OKAY [ 0.031s]
finished. total time: 0.031s
I tried sideloading the OTA instead of flashing the factory image, but it got to 48% and then said this:
error: system partition has unexpected contents
Because the bootloader is locked, I can't flash, and sideloading the OTA seems to be a no go.
Does anyone have any suggestions as to what I could try next?
@Rigger007
Return it for repair/replacement. RMA.
Due to a bug, I have been able to get root on my OnePlus 2 running Oxygen 2.1.1 without a wipe.
DISCLAIMER: This may not give you root on yours, and obviously it may also loose you data, so don't do it unless you know you can cope with that. YMMV, but I've documented here for posterity how to do it!
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
The basic steps are :
Encrypt your device
Unlock the bootloader (this won't wipe because of encryption!)
Boot TWRP
use adb to push SuperSu to your device and then flash it
Then you will have root. Step by step instructions below.
Note that TWRP currently doesn't support encryption on our devices, so you'll have to use something other than that to back up your data if you want to use a custom rom. This simply gives you rooted stock Oxygen.
After rooting :
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Step 1: Encrypt your device.
This is irritating but fairly simple. You have to have fully charged your device AND keep it plugged in, and it takes ~50 minutes to complete. It's the standard android encryption, so follow any guide for this, such as https://support.google.com/nexus/answer/2844831?hl=en-GB
Step 2: Unlock the bootloader.
Again, this is well documented - here's a guide : http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568 - The important thing is that if you're encrypted, this does not do a wipe, in my experience.
Step 3: Boot TWRP
Download TWRP from https://dl.twrp.me/oneplus2/ and save it somewhere you can find it later - I'm going to assume you're on linux and have saved it in ~/Downloads/TWRP.img
Reboot into bootloader mode (Power and Volume up) and start TWRP by issuing the following command (substituting your path to twrp) :
Code:
~$ fastboot boot Downloads/twrp-2.8.7.0-oneplus2.img
Step 4: Root it!
This is a bit tricky because once you're encrypted you can't access the SDCard, so you need a bit of magic to flash the zip.
First, do the swipe to enable modifications, then in mount, tick the /system option.
Then, on your PC, download SuperSU's .zip update from https://download.chainfire.eu/696/supersu/ (similar to above, assuming same download location) and use adb push to put it on the device in /tmp :
Code:
adb push Downloads/UPDATE-SuperSU-v2.46.zip /tmp/su.zip
Next, from the main TWRP menu, select Install. Navigate up (you start in sdcard that is empty) and into tmp, then select the su.zip file in there.
Swipe to install the zip - TWRP will complain because it can't access /data, but handily, /data is not needed to root!
Select Reboot, and viola, you have SuperSU and root! Now you can install Titanium Backup and back up your device.
Cool, perhaps renaming the title like "Unlock and root without wiping" could make more sense?
ranyardm said:
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
Click to expand...
Click to collapse
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Spannaa said:
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Click to expand...
Click to collapse
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
ranyardm said:
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
Click to expand...
Click to collapse
Maybe my post should have said "OTAs don't re-lock the bootloader since 2.1.0"
Anyway, if your method works then great :good:
There's another way to do it here.
Can everyone who's done this attest that the data indeed doesn't get wiped?
cheekrox said:
Can everyone who's done this attest that the data indeed doesn't get wiped?
Click to expand...
Click to collapse
I'd also be very happy to have this confirmed by another party!
Confirmed. Data does NOT get wiped.
cheekrox said:
Confirmed. Data does NOT get wiped.
Click to expand...
Click to collapse
Confirmed on 2.2.0 or still on 2.1.X?
Can confirm, this still works on 2.2.0.
i didnt try this tutorial, but when i rooted my phone, my data didnt got wiped either.
will root on 6p running android n dev preview wipe phone?
Any chance this works also on 1+1? I'm desperate for a way to root without unlocking so I can install titanium/nandroid and do a full proper backup before wiping clean (battery life is utter crap). Running latest stock 6.01 COS. Never unlocked, never wiped since 15R.
Thanks!
anyone tried this on OOS 3 ?
Yeah, bump!
Now my OP2 is on Oxygen 3.0.2, and Android 6.0.1 - stock.
My phone had always been (bootloader) unlocked and rooted, since the day after I got it.
But to get the new OTA update to Oxygen 3, I tried a different method this time, where some people said you can do a temporary un-root, get the stock OTA update, and then re-root.
I followed their instructions, but I can't re-root as simple and easy as they said.
Before the process, I didn't do a nandroid backup because my sdcard doesn't have room :-|
So now I need to re-root without losing data.
And I've tried helium before, many times, and it never works for me.
Any other ideas, or has anyone tried this encryption trick yet with Oxygen 3?
Thanks!
tried it on oos 3.1:
everything worked until a bootloop at the last restart.
also twrp asked me to unlock the phone, i did that.
what to do now?
Did anyone ever have any success with this approach on 3.1?
LoL How do you boot/flash TWRP on locked bootloader?
aIecxs said:
LoL How do you boot/flash TWRP on locked bootloader?
Click to expand...
Click to collapse
Lol, you can't.
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Problem:
This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.
Consequence:
Before your device begins to start it will be shown:
Android system
There’s an internal problem with your device. Contact your manufacturer for details nexus 6p
Also:
The camera may be no longer properly work
Fixxed:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
mfastboot flash system system.img
reboot bootloader
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Important:
fastboot flashing lock_critical
Enjoy!
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Code:
fastboot format userdata
Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
sandfreak said:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
Click to expand...
Click to collapse
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
Thanked @Heisenberg
Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
Heisenberg said:
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Click to expand...
Click to collapse
I have for sure made this mistake before... One lesson learned the hard way
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
That's exactly right, locking the bootloader means you can't flash anything to the device.
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
dontbeweakvato said:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
Click to expand...
Click to collapse
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
Dissmeister said:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Click to expand...
Click to collapse
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Rovaine said:
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Click to expand...
Click to collapse
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Heisenberg said:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Click to expand...
Click to collapse
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Gorgtech said:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Click to expand...
Click to collapse
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
Rovaine said:
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Click to expand...
Click to collapse
Rovaine said:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
Click to expand...
Click to collapse
Flash the factory images, instructions are in my guide.
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.