Related
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.
pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
try do it on another pc
AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?
Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.
pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S
Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.
Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.
ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
rigel1326 said:
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Toolkits or cmd prompt the result is the same. Bootloader acts like it is going to unlock but doesn't.
Sent from my SGH-M919 using Tapatalk
dareino said:
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Click to expand...
Click to collapse
I too have this same issue.....
Once I get the unlock screen (using tool kit) and select yes.... it goes to reboot, but the tablet never comes back on...
Once I turn it back on, I never get passed the "Google" screen....
The tool kit ADB see's the tablet and runs through the "unlock" yet it never takes....
I assume that USB debugging is not turned on... but I can't get the tablet to start it up to turn it on...
Been trying SKIPSOFT ANDROID TOOLKIT.
Can anyone help?
Try the other toolkit.
Sent from my Nexus 4 using XDA Free mobile app
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Erovia said:
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Yes... I have attempted to unlock the device 3 times...
I have used 2 different tool kits and adb fast boot....
They attempt to unlock the device.... but as the unit goes to unlock, it goes to reboot and the unit doesn't come back on... If I manually turn it on, it still shows the unit as locked...
When using abd, the unit does try and unlock and then when it reboots it shows that it unlocked the device yet the device still shows locked..
I'm at a loss right now as to what I should do....
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Erovia said:
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Click to expand...
Click to collapse
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
In that case, it's most likely a hardware failure.
Legobricke said:
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
Click to expand...
Click to collapse
That's normal
I got the Same thing when I try to boot to stock recovery
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!
Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk
DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:
You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk
5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.
How to : Xiaomi Mi A2 Bootloader Unlock
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Text Guide
How to : Xiaomi Mi A2 Bootloader Unlock
1. Turn phone on. Go to Settings - System - About Phone. Scroll down to build number. Tap on it seven times. You will see a message "You are now a developer".
2. Go back, click on developer options. Enable OEM Unlocking and USB debugging.
3. Download MiUnlock tool zip file from downloads section. Unzip the file. Double click to execute the file called "miflash_unlock".
It will open the application, click on settings icon on top right of the application.
Click on check and follow the instructions. Once drivers have installed we can close the application.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Download and unzip adb & fastboot linked in downloads section.
8. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
9. Unlock the bootloader.
Windows
Code:
fastboot oem unlock
Mac & Linux
Code:
./fastboot oem unlock
10. Phone screen will now ask to confirm the unlock. Use volume keys to highlight the correct option, and power to select. Once you press power button bootloader will unlock. Phone will reboot two-three times.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Hi,
I just received my Mi A2 6Gb 128GB device (EU-Device). Followed your guide (Windows) and on the command "fastboot oem unlock" I get the response "FAILED (command write failed (no such file or directory)) Finished. Total time : 0.002s". On the devices screen just comes the message "Press any key to shutdown".
The device runs on August Security Patch.
Do you have any idea what could be the problem? Do I have to unlock with the official Xiaomi tool?
der_daab said:
Hi,
I just received my Mi A2 6Gb 128GB device (EU-Device). Followed your guide (Windows) and on the command "fastboot oem unlock" I get the response "FAILED (command write failed (no such file or directory)) Finished. Total time : 0.002s". On the devices screen just comes the message "Press any key to shutdown".
The device runs on August Security Patch.
Do you have any idea what could be the problem? Do I have to unlock with the official Xiaomi tool?
Click to expand...
Click to collapse
what happens when you do fastboot devices?
have you enabled oem unlock and usb debugging in developer options?
munchy_cool said:
what happens when you do fastboot devices?
have you enabled oem unlock and usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I enabled OEM Unlock and USB debugging. Fastboot devices just shows the device number (just like with my Nexus 5). ADB devices first showed "unauthenticated" but I fixed that.
Never had an error like this unlocking/flashing my Nexus 5
der_daab said:
Yes, I enabled OEM Unlock and USB debugging. Fastboot devices just shows the device number (just like with my Nexus 5). ADB devices first showed "unauthenticated" but I fixed that.
Never had an error like this unlocking/flashing my Nexus 5
Click to expand...
Click to collapse
do you have latest fastboot from google (linked in downloads)?
munchy_cool said:
do you have latest fastboot from google (linked in downloads)?
Click to expand...
Click to collapse
Yes. I did all the steps mentioned in the guide, including downloading fastboot from Google. Maybe I will try tomorrow again from my Linux-Desktop...
der_daab said:
Yes. I did all the steps mentioned in the guide, including downloading fastboot from Google. Maybe I will try tomorrow again from my Linux-Desktop...
Click to expand...
Click to collapse
yes, please try on Linux if you have a Linux machine.
was trying to help someone else with a Moto X4 with a similar issue. turned out to be the usb controller on their computer.
https://forum.xda-developers.com/moto-x4/help/fastboot-receiving-complete-commands-t3831357
Hey!
Great Tutorial. Followed it (windows version with adbdriver dot com already installed), unlock + root + magisk + module api2 enabler + arnova V1.4 in about 10min there is a huge difference in terms of picture quality for anyone wondering.
Yeah.. loving every bit of my Xiaomi curently
++
dodjob said:
Hey!
Great Tutorial. Followed it (windows version with adbdriver dot com already installed), unlock + root + magisk + module api2 enabler + arnova V1.4 in about 10min there is a huge difference in terms of picture quality for anyone wondering.
Yeah.. loving every bit of my Xiaomi curently
++
Click to expand...
Click to collapse
glad to be of help
munchy_cool said:
yes, please try on Linux if you have a Linux machine.
was trying to help someone else with a Moto X4 with a similar issue. turned out to be the usb controller on their computer.
https://forum.xda-developers.com/moto-x4/help/fastboot-receiving-complete-commands-t3831357
Click to expand...
Click to collapse
Thank you very much for your help. It really worked like it should once I used my linux desktop. :good:
Sorry for the inconvenience.
Got lazy starting up my linux machine lately - this will be a lesson for me to stick with Linux instead of Windows
dodjob said:
Hey!
Great Tutorial. Followed it (windows version with adbdriver dot com already installed), unlock + root + magisk + module api2 enabler + arnova V1.4 in about 10min there is a huge difference in terms of picture quality for anyone wondering.
Yeah.. loving every bit of my Xiaomi curently
++
Click to expand...
Click to collapse
Do you have a tutorial for rooting, magisk and enabling cameraapi2? Thanks
der_daab said:
Thank you very much for your help. It really worked like it should once I used my linux desktop. :good:
Sorry for the inconvenience.
Got lazy starting up my linux machine lately - this will be a lesson for me to stick with Linux instead of Windows
Click to expand...
Click to collapse
glad you got it worked out.
for your boot.img thing.
once you have flashed please boot into Android, install Magisk Manager and see how it goes.
Thanks a lot, followed your video and it worked perfectly. Using windows 10
bartoloandre98 said:
Thanks a lot, followed your video and it worked perfectly. Using windows 10
Click to expand...
Click to collapse
awesome :highfive:
how can I lock bootloader again?
thx
How to ulock bootloader without wipe data ?
I Just unlock my data is wiped.
Norisrahman said:
How to ulock bootloader without wipe data ?
I Just unlock my data is wiped.
Click to expand...
Click to collapse
It's impossible unlock/lock bootloader without wipe data
pack21 said:
how can I lock bootloader again?
thx
Click to expand...
Click to collapse
fastboot oem lock
data will be wiped
I unlocked the bootloader and then It started looping
So i flushed a rom with mi flush now im stuck on android logo what can i do?
Tomas... said:
I unlocked the bootloader and then It started looping
So i flushed a rom with mi flush now im stuck on android logo what can i do?
Click to expand...
Click to collapse
Me too.. all I did was unlock the bootloader.
---------- Post added at 03:10 AM ---------- Previous post was at 02:48 AM ----------
Tomas... said:
I unlocked the bootloader and then It started looping
So i flushed a rom with mi flush now im stuck on android logo what can i do?
Click to expand...
Click to collapse
Try the "fastboot -w" command while booted into fastboot. It will wipe all data but you'll get back into the OS.