HELP! Wi-Fi won't turn on - Xiaomi Mi A2 / 6X Questions & Answers

Hi, guys
I ran the following commands in fastboot
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
The phone was stucked in that screen where there is a colored line changing from left to right.
So I entered again into fastboot and type to go back to slot B.
fastboot set_active b
fastboot reboot
It started normally, but Wi-fi and fingerprint are not working.
Any fix? Factory reset?
I'm afraid of doing that and lose all data and wi-fi don't work again to restore.

Hello, I would backup all the data trough usb then perfom a factory reset, maybe try a different rom, Havoc is bug free for me, much better than stock. It's a software issue, so software can fix it.

i am also facing same problem after flashing pie rom,help me

[email protected] said:
i am also facing same problem after flashing pie rom,help me
Click to expand...
Click to collapse
Factory reset solved for me.

Factory reset did not help me..

Related

[Q] How do I fix this

I tried to install a Viper rom (the latest one) but it kept saying error and when I went back to reboot it said that my phone might be unrooted and there was a button that said FIX and a button that said No, reboot and another one that said go back. Through hesitation, I clicked go back on accident and it rebooted. I don't know why but it got stuck on bootloop. Now I stopped the boot loop by holding down the power button and the down volume key at the same time to go back to the bootloader. Now, my problem is, how can I fix everything? I can't boot back to recovery because it goes on a boot loop and I can't factory reset either. I tried using HTC One All in one toolkit but it doesn't recognize my device. It keeps saying "Error: device not found" but my phone clearly says Fastboot USB. I need help ASAP
MySlimey said:
I tried to install a Viper rom (the latest one) but it kept saying error and when I went back to reboot it said that my phone might be unrooted and there was a button that said FIX and a button that said No, reboot and another one that said go back. Through hesitation, I clicked go back on accident and it rebooted. I don't know why but it got stuck on bootloop. Now I stopped the boot loop by holding down the power button and the down volume key at the same time to go back to the bootloader. Now, my problem is, how can I fix everything? I can't boot back to recovery because it goes on a boot loop and I can't factory reset either. I tried using HTC One All in one toolkit but it doesn't recognize my device. It keeps saying "Error: device not found" but my phone clearly says Fastboot USB. I need help ASAP
Click to expand...
Click to collapse
First of all, don't use a toolkit. They rob you of the understanding you need to fix problems like this.
- You should be able to use fastboot to boot recovery. Can you?
- Did fastboot/USB connection ever work for you? How about adb?
- If you get fastboot working (drivers?), you can clear the cache with "fastboot format cache".
- If you can't boot recovery to do the other steps (factory reset and wiping the dalvik cache), you have bigger problems. But I think these steps CAN be done from the bootloader. Maybe not all of them--I'm not sure what will work and what won't, as far as various combinations of "fastboot erase dalvik / fastboot format userdata / fastboot erase userdata", etc.
- First, focus on booting recovery. Get fastboot working and clear the cache if you need to.
- Note that IF you can factory reset through fastboot (I'm not sure you can), it will wipe /sdcard as well.
adb doesn't recognize my device. I don't know why. I can't boot to recovery either.
Same problem
Hi mate i got the same problem as you
this is my thread
http://forum.xda-developers.com/showthread.php?t=2738505
I did the same thing like you.
Adb only works within a working os or in recovery.
If you PC is not recognizing fastboot/adb drivers, install them from here
http://koush.com/post/universal-adb-driver
and also read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Once setup enter bootloader
fastboot flash recovery your recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Adb only works within a working os or in recovery.
If you PC is not recognizing fastboot/adb drivers, install them from here
http://koush.com/post/universal-adb-driver
and also read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Once setup enter bootloader
fastboot flash recovery your recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try installing it and if it all works, you get a thanks from me
EDIT: THIS WORKED FOR ME. THANK YOU SO MUCH I CAN NOT THANK YOU ENOUGH <3 If anyone has this problem, do what this guy said
MySlimey said:
I'll try installing it and if it all works, you get a thanks from me
EDIT: THIS WORKED FOR ME. THANK YOU SO MUCH I CAN NOT THANK YOU ENOUGH <3 If anyone has this problem, do what this guy said
Click to expand...
Click to collapse
Your welcome. Glad you now have a working phone
Sent from my HTC One using XDA Premium 4 mobile app

Nexus 6 stuck - Google logo/Unlocked symbol

Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
Old post, I'm guessing you've moved on, but...
What ROM was on the device before you flashed the 6.0? The boatloader updates with stock ROMs. I there is a 7 bootloader, it may interfere with the boot of a 6 ROM.
If you are unsure, you should always go with the newest stock release.
SonyXperiaS said:
Hi,
So I flashed a stock rom 6.0.1 from google website using a standard procedure, the device booted for the first time, signed in and set up. Then when I restarted the device, it is not stuck on google screen with bootloader unlocked.
Can anyone help me how to fix this?
Click to expand...
Click to collapse
I would try clearing the caches and/or userdata before manually installing the system partition again.
1.) Reboot to the bootloader. (reboot and press and hold the volume down button until booted)
2.) plug-in the usb cable
3.) Open your terminal and type:
Erase cache
Code:
fastboot erase cache
Erase dalvic-cache
Code:
fastboot erase dalvic-cache
Erase userdata
Code:
fastboot -w

Bootloop after October security update on rooted device.

Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.
until the moment it completely discharged its battery
Click to expand...
Click to collapse
same here! I am not rooted and not unlocked.
Exactly the same here...
fly23 said:
same here! I am not rooted and not unlocked.
Click to expand...
Click to collapse
This was 2 days ago. It worked again after about 150 reboots. Or i pushed a special button combination, I don't know.
In betweet I did one "fastboot reboot".
Now I have the same problem again after empty battery. Bootloop.
This is the worst android phone I ever bought after HTC desire, Galaxy Nexus, Nexus 5, 5X. I will never again buy a budget phone or a xiaomi.
I did a factory reset this morning, and itgot stuck on an Android One screen. I am trying to figure out how to reflash it, but it doesn't seem to like the firmware. Not sure if I have to unlock the bootloader? I am not family with any of this stuff. I was supposed to ship the phone to the buyer today, but I guess I may have to kill the deal and refund them. This may be the last Xiaomi I buy.
https://imgur.com/a/5J51w3D
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
Yeah, I wonder that as well.
The arrow down + power button combination just keeps the phone frozen on a fancy picture with "fast boot" written at the bottom of the screen.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
You need PC for that
Boot into fastboot (vol - + PWR)
Then use fasboot from terminal
First look which slot is active by typing
fastboot getvar current-slot
Then we can change active slot using this commands
fastboot --set-active=a
or:
fastboot --set-active=b
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Aerobatic said:
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Click to expand...
Click to collapse
I think this is why my phone is completely bricked. It does not have an unlocked bootloader, so it seems I can't flash firmware on it. I will likely never buy Xiaomi again after this. I just was doing a factory reset since I had sold the phone.
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
ngohoainam said:
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
Click to expand...
Click to collapse
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
clocks11 said:
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
Click to expand...
Click to collapse
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
ngohoainam said:
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
Click to expand...
Click to collapse
Unfortunately, I think I am screwed, as the phone was not unlocked prior to my boot issue. So I am not sure there is anything I can do. I can get to fastboot though.

MI A2 stuck in bootloop after soft reset

2 days ago i woke up to my phone's screen already on, it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but when it turned itself back on the phone was now stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. I have unlocked the bootloader (also done critical unlock) but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this? It's not rooted and the bootloader had never been unlocked previously.
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
ricardohorta said:
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
Click to expand...
Click to collapse
"bluetoot_a" is the first thing it tries to flash through mi flash. Its also the first thing in the images.
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
ricardohorta said:
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
Click to expand...
Click to collapse
Im not able to boot into twrp, it just hangs on the splash screen.
It should load directly from the bootloader.
Maybe you can try different TWRP versions, maybe it helps.
Xiaomi Mi A2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There are some instructions also.
rxsta said:
Im not able to boot into twrp, it just hangs on the splash screen.
Click to expand...
Click to collapse
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Sorry @User699 I was out of town, but I'm back now. What's your current status ?
User699 said:
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Click to expand...
Click to collapse
When i boot this version of twrp, the screen goes black for a bit but then just reboots itself.
Finally booted but still hanging on splash screen.
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
User699 said:
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
Click to expand...
Click to collapse
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
rxsta said:
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
Click to expand...
Click to collapse
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
Doubt there's anything else I can do.
Think it's important I also mention that I can't get into the phone's recovery.
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Click to expand...
Click to collapse
Does your device display anything on its screen?
User699 said:
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Does your device display anything on its screen?
Click to expand...
Click to collapse
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
rxsta said:
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
Click to expand...
Click to collapse
I wish you the best of luck!

Black Screen

Hello,
My phone droped but the screen was fine and working, but suddenly after opening an app the screen went completly black. I had this problem already and a reboot would help. Now not even that was working. I thought maby the screen was broken, and ordered an replacement from ifixit since they have genuie Pixel Screens. But the new screen wasn't working either.
The touch is working I was able to to unlock the phone and unlock the usb debugging.
Could it be software related? Is it possible to make a full reset over usb debugging.
Try Android Flash Tool. Otherwise yes you can try via adb commands:
recovery --wipe_data or wipe data
Or via fastboot:
fastboot erase data
fastboot erase cache
or fastboot -w

Categories

Resources