Hi guys, i performed an all in one update to 4.2 from stock non rooted 4.1, it didnt work properly and now im stuck in fast boot screen with a locked bootloader.
i see the START button with the google icon, i can switch it between power off, recovery mode, restart bootloader. Start does nothing, power off works, restart bootloader works, recovery mode does nothing and says booting failed.
nothing works on the tablet its self, no matter what option i try i cant get out of that part.
I then downloaded WugFresh's all in one toolkit, ADB options are out of the question as that doesn't recognise in this part of the N7. fastboot stuff works, i tried pretty much ever option including the softbrick/bootloop recovery options and they don't even work.
When doing that, the command prompt that starts up spits this out:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.021s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.41
Baseband Version.....: N/A
Serial Number........: 015d2ea4d02c0812
--------------------------------------------
checking product...
OKAY [ 0.029s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4896 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.161s
what do i do? am i screwed?
I think you might want to unlock the boot loader first.
You would need to run the command
fastboot oem unlock
And that will unlock the boot loader which should mean that you can flash the ROM.
And then if you want to lock the boot loader again after flashing the ROM you would need to run
fastboot oem lock
Another example of why toolkits suck. If you can't do it manually don't, otherwise you will struggle with problems like this.
The update failed in some way because you still have the bootloader from 4.1.2. So long as you can get into the bootloader, you are not bricked though. Just got to unlock it and flash manually the update using the fastboot, method and you'll be sweet.
Sent from my Nexus 7 using Tapatalk 2
dr.m0x said:
Another example of why toolkits suck. If you can't do it manually don't, otherwise you will struggle with problems like this.
The update failed in some way because you still have the bootloader from 4.1.2. So long as you can get into the bootloader, you are not bricked though. Just got to unlock it and flash manually the update using the fastboot, method and you'll be sweet.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
This :thumbup:
Sent from my SPH-D710 using Tapatalk 2
If your tablet turns on, it's not bricked.
So many people use that term with no clue as to what it means.
Related
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
pmikec said:
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Click to expand...
Click to collapse
I don't know why it refuses to relock but another question: why do you want it to be relocked? It is adviced to only relock a bootloader when it is absolutely needed (warranty case, resale...)
Face_Plant said:
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
Click to expand...
Click to collapse
This did the trick. I'm not sure why I didn't just try the old command myself before asking. Thanks!
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
alryder said:
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
Click to expand...
Click to collapse
to condense, summarize and make clear what i have already tried, and to seek further troubleshooting to my issue. there must be someone with an idea of how to fix this. if not, does it really hurt the forum? i am a person with a problem, seeking advice.
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
alryder said:
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
Click to expand...
Click to collapse
how is that even possible?
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
automatic update of some sort. it crashed my phone as soon as it was finished updating. didnt know a background app update could relock my bootloader and brick my phone. not sure why some are suggesting the bootloader is locked when it still displays status code 3 device is unlocked.
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
scottshebs said:
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Click to expand...
Click to collapse
i guess all the time i devoted to you yesterday means absolutely nothing to you, and you learned nothing.. thanks
RMarkwald said:
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
Click to expand...
Click to collapse
forgive me, but how can the phones bootloader lock itself? this is the fastboot screen still saying code 3 unlocked. sorry if i am stubborn, just refusing to believe my 300 dollar device bricked itsself while i literally did nothing. never seen anything like this.
31ken31 said:
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
just posted, still status code 3.
Thread closed.
Not sure why the OP started 2 similar threads (like THIS) and ignored the help provided already....
I have a review phone of the P9 (the 09 version). I'm trying to put a nougat beta on it. Bootloader came unlocked- see attached photo. When i go into bootloader fastboot devices sees it no worries. I ran the bat file to check and yes the bootloader is unlocked according to it.
Problem is that when I try to flash TWRP i get:
Code:
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery" (22368 KB)...OKAY [ 0.655s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.667s
I am not a noob to hacking android etc that is for sure but this is doing my head in. Is there an issue with the bootloader unlock? I've sent an email to Huawei support people as well. I had issues getting a bootloader unlock code anyway as being in Australia it doesn't allow be to do anything in Huawei ID, so i cannot get the code. I also tried using the beta app but even when using a VPN it was geoblocked.
ideas on what is going wrong?
thanks
Make sure OEM unlock is enabled in developer settings. If you have an app called "Phone Finder" or any other phone tracker app, disable it. If that doesn't work, you can try restoring phone to factory settings and enable OEM unlock again then try again.
I tried the above stuff mate- unfortunately it did not work. only phone finder is android device manager and it is turned off (phone is basically stock). OEM unlock is enabled correctly etc. even factory reset and did it all over again. oh well. i give up for now. i would love root on this too...
hi have a bricked p8 lite in front of me. when i start the phone im in rescue mode and get the rror:
func no 7(teeos image)
error no 1(security verify failed)
with power button + vol+ i cant boot into recovery. phone does nothing. just blinks red.
booting into fastboot is possible. bootloader is apperently locked(phone locked). if its possible to install twrp with a locked bootloader then ive done so via this tutorial. if not, am i f+++ed because huawai doesnt give out unlock codes?
i guess it doesnt work with a locked bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp1.img
target reported max download size of 471859200 bytes
sending 'recovery' (31572 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.830s
is it possible to reboot into recovery via fastboot? fastboot reboot recovery dosnt seem to work.
any suggestions what i could try next?
with locked bootloader, you're pretty fu****d... but, some third party app/sites give bootloader codes for some money... had something similar long time ago, fortunately for me, I had my bootloader unlocked... I guess there aren't other solutions... and from fastboot, you can't go to recovery...
---------- Post added at 10:13 ---------- Previous post was at 10:10 ----------
k2828 said:
hi have a bricked p8 lite in front of me. when i start the phone im in rescue mode and get the rror:
func no 7(teeos image)
error no 1(security verify failed)
with power button + vol+ i cant boot into recovery. phone does nothing. just blinks red.
booting into fastboot is possible. bootloader is apperently locked(phone locked). if its possible to install twrp with a locked bootloader then ive done so via this tutorial. if not, am i f+++ed because huawai doesnt give out unlock codes?
i guess it doesnt work with a locked bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp1.img
target reported max download size of 471859200 bytes
sending 'recovery' (31572 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.830s
is it possible to reboot into recovery via fastboot? fastboot reboot recovery dosnt seem to work.
any suggestions what i could try next?
Click to expand...
Click to collapse
okay found this, you can try it... I too got my code this way, but back then Huawei was open to unlocking bootloaders, now cannot say... but you can still try
unfortunatly the led just blinks red when i press all 3 buttons. flashing a stockrom or parts of via fastbootin locked bootloader also isnt possible i guess?
today i unlocked ale-l21 with dc-unlocker for 4 euros.
You need to install stock android 5 and root it with kingroot, then open a bash terminal and get the bootloader code with grep, there's a tutorial on how to do all of this, and it's free. This should also unbrick your phone. If you have an sd card you should be fine. If not, you may encounter complications but you should be able to do it too.
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com