Hello guys.
I need help on rooting my Asus Zenfone Selfie (ZD551KL). I have followed this tutorial:
https://forum.xda-developers.com/android/development/root-asus-zenfone-selfie-zd551kl-z00t-t3443595
I came across 2 problems. First problem is regarding the oficial ASUS bootloader unlocker tool. My phone came with Android 6 installed. I first tried to install the app on Android 6 and the app crashed. So after searching I discovered this tool is for Android 5.
So I downgraded to Firmware UL-Z00T-WW-51.15.40.1582-user (Android 5). Then I installed the unlocker app (UnlockApp_1211_ZD551KL), now the app did not crash. It did open, i clicked on agree, then I pressed the blue button to unlock device.
It asked me something about device PIN (you did not insert PIN to verify device, are you sure want to unlock).
I click ok then it reboots. However the ASUS logo screen did not change to white. I have adb installed (and fastboot tools), so whenever i check fastboot oem device-info it shows that my phone is still locked. It`s like the unlocker tool does not work.
Second problem is when flashing TWRP Recovery. I downloaded the last twrp from official site (https://dl.twrp.me/Z00T/), and I was able to successfully flash it:
fastboot flash recovery twrp.img
According to twrp site, I typed fastboot reboot but before clicking on enter it says you need to hold the key combo to enter recovery mode (which in my phone is volume down + power). So I do this, however, it keeps looping and blinking on ASUS logo, I stay more then 15 minutes but it does not do nothing. I then released the power and kept holding only volume down. Same thing, just stuck on ASUS Logo.
So then I release all and it boots normal to Android.
So my 2 problems are: unlocker tool is not working and I can`t enter twrp recovery even after successfully flashed it.
Please help me guys!!!
No one has any ideas? I tried this method:
asus-zenfone.com 2015 05 one-click-root-for-zenfone-series.html
But this did not work. My phone continues as it is, no root access no bootloader unlocked.
Please anyone can help me?
Related
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
Download and install "minimal adb and fastboot"
Just type on the command line without pressing Enter:
Code:
[COLOR="Blue"][B][I]fastboot [COLOR="Plum"][STRIKE]boot[/STRIKE][/COLOR] recovery.img[/I][/B][/COLOR]
you should place your recovery image file in "minimal adb and fastboot" directory
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds - in my case the phone is restarting)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery command line
Click to expand...
Click to collapse
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
i must extract "flashrec TWRP v2.7.1.2 this file on phone or where? can u explain a
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Please explain me. idont know how to do
prxzero said:
Please explain me. idont know how to do
Click to expand...
Click to collapse
What Is your problem?
Is your phone stuck on logo screen? what were you doing to get the problem??
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Hi..
i just try to install CM12 to this device, with twrp 2.8.6.1 from master lie.
First time its working well, but suddenly this device restarting and stuck on the "lenovo" logo screen.
Every time i presh power button always restarting (like ON-OFF-ON-OFF forever).
when i connectto charger also restarting....
i cant go to twrp using vol- & pwr, when i use minimal adb cannot detected..
Can you help me...
Help
hi.
i try to do something to enable notifications on my lenovo vibe z.
i install new rom from needrom, but it didn't help. So i try to install other one, but i wipe my phone and restart without installed system.
Now when i go to twrp have just flashing teamwin logo, and only when phone is in this mode i can communicate through adb
i have checked many forums and try allot stuff to fix it but nothing works
Please Help!
U are not alone I also in same stage
Is there any one plz help
As long as the hardware is not physically broken, your K910 is unbrickable
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
nowbo said:
Is there any one plz help
Click to expand...
Click to collapse
Thanks for your reply
I will apply today. Hope for the best.
Will inform you as soon as this applied..
Have you fixed that problem?
Still at same stage
EcoDan said:
Have you fixed that problem?
Click to expand...
Click to collapse
Hi,
I am still on same stage (Black screen with lenovo logo). Try several ways but can't get out of this. Please help me If any one successful to startup this device or can get on the boot screen where I can do factory reset.
---------- Post added at 07:25 AM ---------- Previous post was at 07:21 AM ----------
wxppro said:
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
Click to expand...
Click to collapse
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks
[/COLOR]
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks[/QUOTE]
You need to carefully follow each steps in the method - if you short that magic pin and then connect the USB cable (with battery disconnected), your computer will report seeing the device at either COM port 9008 or 9006. Then you can download the factory image to revive the phone. Of course you need to have the right device driver installed. Like I said, as long as the hardware is not broken, this procedure will succeed for sure.
I love you man!
I love you man! I wish you all the happiness and wealth!:victory::victory::victory::angel::angel::highfive::highfive:
I was forwarded tot this subforum, maybe someone could help me here?
I tried to root the tablet, and thought I had all the steps required to do so. I just rooted my OPO without problems and wanted to do the same with the Asus. As I've said, I thought I had all the steps but saw I missed some things and followed a mix of different tutorials on xda-developers.com. I had downloaded the ASUS v5.0.11 update and the 5.0.11 root. I could get into bootloader with Vol-Up + Power, it opened the android with helmet-bootloader without problems. I used the fastboot commands: - fastboot erase cache - fastboot erase system - fastboot flash update "updatename".zip
there it failed to flash the zip
Then I saw I had to use the fastboot 4.7.3 and not the 5.0.11 one. So I tried to flash that one I found somewhere. Then I installed recovery 4.7.3 and then I got a bricked asus
I have no idea in what order I did things, and I'm sure I did a lot more than I've described. But now I can't get into bootloader with Vol-Up + Power, and when I try to access the bootloader with adb reboot bootloader, I don't see the android with helmet anymore, but just the usb-icon with a red gauge. When I try to start the tablet, it hangs on the bootscreen 'Asus, in search of incredible'.
I want to get into bootloader again so I can play with fastboot-commands again, or if someone knows what to do by the things I've just tried to describe.
I would cry if only I could get into the OS again.
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
I install an service full repair stock via dload
http://androidhost.ru/v5
it is working right now.
oblivion2222 said:
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
Click to expand...
Click to collapse
You can always re-unlock your phones bootloader again, the key is always same, then flash or boot twrp with fastboot.
Some developers says the command for oreo is: fastboot flash recovery_ramdisk [file name] but I used this: fastboot flash recovery_ramdisk_a [file name]
You even can try to just boot twrp without flashing it to your recovery by simple typing: fastboot boot [file name]
If fastboot can flash twrp, turn your phone off then hold volume up/+ and power button same time and hold them until the state of unlocked warning appears.
You can use dload method or you can use HuRupdater method to flash firmware. You'll find introduction for how to do it.
Just search on xda
Hello. I Factory reset my Mi A3 while in my Google account not through recovery. Now when I boot the phone I get an error saying unable to connect to wifi when phone is connected to wifi and the when I try to add my Google account I get a message the The Google servers are unavailable and try again later. I did some looking and tried a few suggestions on line, about deleting Google app caches and delete account and add account. I deleted the phone in my Google account in my desktop and can't add it again, I turned off two step verification...it's seems like the phone isn't behaving at all right. I can get into the phone and a message will tell me to finish setting up and when I tap the message I go to the start up page. The phone isn't currently rooted but the bootloader is unlocked.
Thank you in advance for reading this far, please any help is appreciated.
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Thank you for your reply. I was thinking about that and wasn't sure if it would help. I will try that and let you know how it goes.
bjlabuk said:
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Click to expand...
Click to collapse
I was able to download files and flash however its ion a boot loop stuck on android one screen and ther fix at the end of the directions say to execute command to get a active however my computer return with fastboot is not a internal or external command or file. Please advise. I will look on here for fix too. Thank you
bjlabuk said:
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Click to expand...
Click to collapse
Well I have gone from bad to worse. Now stuck on fastboot screen and bootloader locked. Ugh!
If you google "mi a3 stuck on fastboot screen etc" you should get a couple of suggestions. Can you boot into recovery? Press the power key and the vol. up key at the same time. Keep holding until phone restarts, then release the power key and wait for the Recovery menu screen to appear.
Also did you read the Important Note at the bottom of the instructions?
If the device fails to boot into the OS and keeps bootlooping, connect it to the PC while in fastboot mode, and execute the following command:
.\fastboot set_active a
bjlabuk said:
If you google "mi a3 stuck on fastboot screen etc" you should get a couple of suggestions. Can you boot into recovery? Press the power key and the vol. up key at the same time. Keep holding until phone restarts, then release the power key and wait for the Recovery menu screen to appear.
Also did you read the Important Note at the bottom of the instructions?
If the device fails to boot into the OS and keeps bootlooping, connect it to the PC while in fastboot mode, and execute the following command:
.\fastboot set_active a
Click to expand...
Click to collapse
Thank you for you reply. I did see the instructions and tried the script while connected in fastboot mode. I tried the miui tool and relocked my device while and now I am in fastboot with locked bootloader. I was reading about EDL mode help however the first attempt came back unable to enter EDL because bootloader locked. I decided to step away for a few days to take a beat before going further.