Related
My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..
So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.
no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .
I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview
After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?
Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.
Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?
Here you go
google.com/android/beta
do you remember what you did to get it to boot?
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.
http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.
So I upgraded to Nougat on my P9 Lite, unlocked boot loader, used twrp, flashed roms and everything went smooth. Saw a more up-to-date version with no bugs, so I had to downgrade to MM first.
I followed a guide, but I messed up somewhere and ended up having my bootloader locked, and I can't access the OS to enable developer options and oem unlock from settings. The reason why I can't access the OS is that I am stuck in the setup. I am stuck at the part where I have to sign in to my google account. It doesn't show a keyboard, only a microphone, and I can't use that for my password (it won't let me).
Any ideas?
TL;DR messed up during downgrading from Nougat to MM, now TWLR is gone, bootloader is locked and my main issue is that when I get to the google account sign in part during OS setup, there is no keyboard (I can only use dictation) so I can't sign in... So I'm stuck
Also, can I unlock bootloader without access to OS, without being able to navigate to settings, enable developer options and then oem unlock?
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Jagiel88 said:
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Click to expand...
Click to collapse
It is obligatory, I couldn't skip it. I tried to use other methods of signing in, but then it asked me to reset password at the end.
Both Phone and FRP are locked
I think I have missed this, but I can't do it via fastboot because I keep getting "Command not allowed" whenever I try to unlock bootloader or do anything via fast boot.
Also, thank you so much for your time and input. It is much appreciated.
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Jagiel88 said:
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Click to expand...
Click to collapse
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
No problem, unfortunately I haven't tried Nougat yet, so search for help on down/upgrade Nougat beta <-> Marshmallow threads .
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
Click to expand...
Click to collapse
There is 1 thing to unlock in settings . U have OEM lock
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
ScaleneVirus288 said:
There is 1 thing to unlock in settings . U have OEM lock
Click to expand...
Click to collapse
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
Click to expand...
Click to collapse
Unlock bootloader, after that you able to flash rom.
You use this command?
fastboot oem unlock YOUR_OEM_CODE
If you tip:
fastboot devices
What's you see?
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry
Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?
bad luck !! Test point method is the only way ? i faced the same situation ... please don't go to the service centre , they will tell you that the motherboard of your device needs a change .. and ask for a big amount of money if your phone is out of warranty ..!! search for the test point method here .. follow the video , and then follow the steps to go back to stock oreo from pie .. that's the only way ??
Same problem happened with me
My internal storage gets full and mobile automatically got switched off and bootloop
I tried to flash my self with adb command fastboot oem unlock
And successfully unlocked the bootloader & flashing process started but it keep flashing for long time whole night
So i decided to go near shop and gave him he tried with EDL test point and then phone goes in black screen He gave up :crying:
Now I'm thinking to go mi service centre but i get to know their ans is to change motherboard
PepeDaFrog said:
Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?
Click to expand...
Click to collapse
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?
i just flashed the device for my wife with stock fastboot and locked the bootloader and of course it ends in bootloop.
i removed sim and micro sd and it boots up.
cheffy11 said:
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?
Click to expand...
Click to collapse
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
did you try fastboot oem unlock?
Gamestrav said:
did you try fastboot oem unlock?
Click to expand...
Click to collapse
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.
PepeDaFrog said:
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.
Click to expand...
Click to collapse
What recovery do u have?
PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.
barrack1 said:
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.
Click to expand...
Click to collapse
Hi! Does testpoint method works here?
I'll try with a home made EDL cable, if this does not work I'll have to drive to the office for tools and try the test point. I'll update, but if anyone knows if this or that works and see this post on time, let me know!
UPDATE:
- EDL cable didn't work.
- Test point method worked fine, I thought that opening this phone would be harder, search for dissasembly tutorials on youtube and for test point method, the brick got back to life and it's fully working!