Related
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
stevemacer10 said:
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
Click to expand...
Click to collapse
Stevemacer10 Hello, I hope to be keen to help, because it happened to me the same thing, with two days of stomach ache for it. In wanting to load Android on my Nougat Huawei P9 Plus VIE-C02, with VIE-L09C605B354 and VIE-L29C185B320 I went into semi-brick or brick, or was only in bootloader, the screen with the green man to speak. No avail various ways, including via microSD-Fastboot or ADB to do restart your phone. Then, to my previous experience with a Huawei tablet, I logged on to the 'https://www.dc-unlocker.com/' site, and essend already registered, I bought 15 credits (15 Euros), for the 'option' DC Phoenix Firmware write ', valid for 72 hours, in addition to the program and downloaded the' DC program Phonix v29 '(https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial) following the related tutorial. Obviously procured the original firmware 'VIE-L09C02B133' or even lower versions, you'll have to unpack in a folder of your preference. Unfortunately, despite having used with DC Phoenix the original firmware was always also blocked me. At that point I wanted groped with a firmware that you can find on the same site of the DC-Unlocker (https://files.dc-unlocker.com/user.html?v=files/57694006a60d7) by downloading the firmware 'VIE_AL10B_M00A063_Factory_firmware_China_Nonspecific_Android_6.0_EMUI_4.1 .dgtks', which I loaded with DC-Phoenix on the phone. Rebooting of a minimal mode of andorid, I did not see well either. I went back into bootloader, as well as devone be made the previous steps that I have already described to you, and this time with DC-Phoenix I loaded on the phone firmware L09C02B128 and everything went well. Attention and keep in mind that just as I happened to me, the serial number of your phone is changed, to me has happened in '0123456789ABCDEF' and there was no way to change it, so as, while having the unlocked bootloader can not longer charge the TWRP recovery in order to then have root permissions. Until reading the paragraph '(Optional) Phone numbers REPAIR', I went to that point on the site 'http://hcu-client.com/'. Also here are sadly bought 8 credits (8,00 Euro) in order to work with the program 'HCU-Client v1.0.0.0115', you need to download and unpack, then follow the various instructions, which are not difficult when you have to be walked through the modding, otherwise you do even more damage. Let me know what you did and how it went to the method. I hope also good for you. In summary we want Euro 15 for Phoenix whose duration of operations applies to 72 hours and 8 Euro per HCU-Client, it can only use this for 24 hours.
P.S .: Obviously if you follow my instructions and all these signs you do so at your own risk, esonerandomi from every possible and accidental deterioration of the situation and the damage to your phone. Sorry for my English, whose translation has made Google translator.
---------- Post added at 12:59 AM ---------- Previous post was at 12:33 AM ----------
I wanted to say that the change of the serial number does not work well. The serial number has been changed from what I've shown you above, but was not put one I added that I had from the sales box. I write support and maybe let you know what they tell me. See you soon.
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
stevemacer10 said:
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
Click to expand...
Click to collapse
Stevemacer10 hello, I'm glad you've solved the problem. Unfortunately I'm still fighting because, for now I can only and even to load its firmware, but if you want to try to load the TWRP recovery for later obtain root permissions, it always fails. From what seems to understand me and certainly due to the fact that the bootloader unlock code now is different from what I have, because as I told you the serial number has changed and if I request a new unlock code, it stops notiziandomi the procedure that there is inconsistency between this number and the IMEI. For now I do not know what to do and how to proceed. I hope that over time can still solve my problem. A good evening to you :good:
i'v been throw it
after updating my p9 plus with a firmware that is not sutable to my area
my phone restarted and ask for an account wich ok but the problem was that the software not working properly and missing a keyboard.
and will not go to recovery mode to try another software.
this sloved by downloading a sutable correct software and unzip it into an SD card folder (i create) called dload, then swich off the device and turn it back on while holding three bottons (power+v up+v down) 10 to 15 sec. and the phone directly read from the SD card and start updating a new firmwarw.
try it.
it success with me , hope it work wth u
So 3 months after I got the phone, I tried to unlock the bootloader about 2 weeks ago, and got the timer (168 hours). Now when I tried to unlock it again, it's mostly giving me (Like 9.5 out of 10 times) a "Couldn't verify device: Can't get info" Error at 50%. There are rare instances when it goes beyond 50% and stops at 99% it will give me the following error (please see attachments).
I've tried everything from:
1. Re-linking my account in "Mi Unlock Status"
2. Removing fingerprints and lockscreen
3. Running unlock tool with admin rights
Could this be because I may have disabled some background apps or some of the apps I installed? I did leave Mi Cloud and Mi Account Sync on along with Find my device. If yes, then would a factory reset solve this problem?
I don't know what to do anymore :crying: . If anybody could help that would be greatly appreciated
Xiaomi sucks i had the same problem i got my phone 1 month earlier and everytime i tried to unlock they doubled the wqiting time in total im gettingv2 months of waiting and still im not sure after thzt, they will not add more time. They ducks with their unlock process, we want it to unlock this **** why making it complicated ? Chinese bastards
jceey15 said:
So 3 months after I got the phone, I tried to unlock the bootloader about 2 weeks ago, and got the timer (168 hours). Now when I tried to unlock it again, it's mostly giving me (Like 9.5 out of 10 times) a "Couldn't verify device: Can't get info" Error at 50%. There are rare instances when it goes beyond 50% and stops at 99% it will give me the following error (please see attachments).
I've tried everything from:
1. Re-linking my account in "Mi Unlock Status"
2. Removing fingerprints and lockscreen
3. Running unlock tool with admin rights
Could this be because I may have disabled some background apps or some of the apps I installed? I did leave Mi Cloud and Mi Account Sync on along with Find my device. If yes, then would a factory reset solve this problem?
I don't know what to do anymore :crying: . If anybody could help that would be greatly appreciated
Click to expand...
Click to collapse
Download an earlier version of the unlock tool from here and try unlocking with the earlier version https://c.mi.com/thread-2262302-1-0.html
Some people have reported that using an older version works in these cases.
Use the miflash_unlock-en-2.3.803.10 version, it'll work!
Regards,
acervenky
You probably need to use a VPN service. I had similar problem with my MIX 2 and I had used Plex VPN and then only could unlock bootloader
Thank you to everybody who gave advice. It was weird, since what I did was:
1. Logged into the Mi Cloud website with my Mi Account
2. Checked if my phone was online
3. Tried the Find Me option, and was able to locate it (scary stuff and one of the reasons why I'm unlocking my bootloader)
4. Left it for a day and when I tried to unlock the following day, I was able to unlock it immediately
Seriously, the unlocking process of Xiaomi phones is a bit tedious and varied.
jceey15 said:
Thank you to everybody who gave advice. It was weird, since what I did was:
1. Logged into the Mi Cloud website with my Mi Account
2. Checked if my phone was online
3. Tried the Find Me option, and was able to locate it (scary stuff and one of the reasons why I'm unlocking my bootloader)
4. Left it for a day and when I tried to unlock the following day, I was able to unlock it immediately
Seriously, the unlocking process of Xiaomi phones is a bit tedious and varied.
Click to expand...
Click to collapse
Thank you, using Find Me I was eventually able to unlock
I will agree on the tedious unlocking process. The last phone I will buy from them will be the Android One ones (A1/A2/A3). I had a fuss-free experience with my A1.
Hey guys, recently I broke my A2's screen (again) and ordered a replacement from China.
I installed it, booted the system and updated to Android 10 immediately.
Everything seemed to be working, but I noticed that the GPS is now useless.
I mean, it manages to pinpoint exactly at my house, but If I set a route, it just doesn't work, it remains stuck.
If I leave the house (and, therefore, begin to rely on mobile data), the precision vanishes completely and it just won't find me.
This behaviour is strange, since mobile data is working normally, and he can pinpoint my location at home quite precisely, compass apparently working, but outside it won't work at all, it can't detect any kind of movement, even if placing me somewhere else.
I have two hyphotheses:
1) The sensor broke?
The screen broke in the bottom of the phone, nasty break, but it wasn't a fall. An item pressed against it in a purse.
Maybe this time the sensor broke? Is it possible to buy parts and fix it?
2) Could this have something to do with this update? I reseted the phone to factory, but it's still Android 10...
Any other report like this? I should try downgrading to Android 9 right?
What do you guys think?
Just some updates:
I tried Android 9 and GPS still doesn't work.
The sensor is probably fine, but something happened while changing the screen.
I saw a report that says that changing back to old screen fixed the GPS issue. I can't do this because I throwed the broken screen in the trash.
Hey guys, can anyone say which replacement piece must be used to fix this issue?
Could it be the lower dock board, or the mainboard, or a single module? I could try to buy it from aliexpress and repair the phone...
Both GPS and Bluetooth don't work. I need to know which part of the hardware is related to these functions. Can't find anything online.
Edit: bluetooth is ok actually.
valp88 said:
Hey guys, can anyone say which replacement piece must be used to fix this issue?
Could it be the lower dock board, or the mainboard, or a single module? I could try to buy it from aliexpress and repair the phone...
Both GPS and Bluetooth don't work. I need to know which part of the hardware is related to these functions. Can't find anything online.
Click to expand...
Click to collapse
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
KevMetal said:
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
Click to expand...
Click to collapse
I see. Even a stock update from 9 to 10 could've broken my persist data then?
I went back to Pie stock and had no luck, then stock-updated to 10 again.
If this were software/corruption related, then going back to Pie stock would've fixed right?
I'll try to flash that persist data, but I have no backups.
I searched for your posts and couldn't find your guidance, but found this:
https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
I'll give it a try.
KevMetal said:
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
Click to expand...
Click to collapse
By the way, can I restore the persist from the file you provided in https://forum.xda-developers.com/mi...mi-a2-4-32-t4100729/post82612405#post82612405
in the latest OTA (11.0.6 if I'm not mistaken)? Or could that mess up the system?
valp88 said:
By the way, can I restore the persist from the file you provided in https://forum.xda-developers.com/mi...mi-a2-4-32-t4100729/post82612405#post82612405
in the latest OTA (11.0.6 if I'm not mistaken)? Or could that mess up the system?
Click to expand...
Click to collapse
sure go ahead , doesn't touch system nor data
KevMetal said:
sure go ahead , doesn't touch system nor data
Click to expand...
Click to collapse
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
PsK2010 said:
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
Click to expand...
Click to collapse
my suggestion is using the recovery image(,twrp) i provided and not any other
reason: because it will allow you to flash an image directly to persist..
furthermore the correct or best procedure is to download a fastboot stock rom of whatever version STOCK not custom is on your phone but that matches exactly ..then unzip with 7zip and take the persist.img file ..put it on your pc or internal storage and flash with the recovery i provided by choosing
install ..select image option ..browse to image ...select persist partition
failing this (error message) the ACTUAL and best solution that works ?% but is not easy is to take a fastboot stock rom and then using fastboot put your phone into edl mode :
fastboot oem edl
then flash the whole stock rom using Xiaomi miflash ..in fastboot mode miflash doesn't have the required permissions to flash secure partitions ..in oem edl mode ( Qualcomm) it is deep flash .. NOW the bigger problem and difficult part is that xiaomi themselves modified the flash xml ( that tells miflash what to flash NOT to flash persist EVEN if there is a persist.img in the folder ) so you need to manually modify certain lines in the xml so miflash flashes the persist img files
**although the flashable persist restorer zip works occasionally it has failed in others or worked only temporarily and if you went from pie to Q the chances of failure are even higher
and by the way if the persist restore is done successfully it does fix gps issues
as a workaround ...if gps works but not well ..use magisk gps module to replace global gps file ..
if gps shows 0 action you need to do the miflash option ..there is always also the possibility that you damaged hardware while replacing screen or that you disconnected something and failed to reconnect it properly ..
---------- Post added at 02:17 PM ---------- Previous post was at 02:02 PM ----------
so 100% fix ... following on my previous post do this using a pie fastboot stock rom for your device together with my miflash
Download XiaomiADBFastbootTools.jar https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/3.0.2 Credits: Saki-EU
Java run-time environment is required https://java.com/en/download/
Now extract the fastboot rom and locate rawprogram0.xml inside images folder. Edit it with Notepad++ and search for persist. You will see it among line 57 with filename="" . Add persist.img inside quotation marks. So final will be like filename="persist.img"
Now save it.
Now power on the phone while pressing volume down button in order to get into fastboot menu.
While in fastboot menu, connect your phone to pc and run XiaomiADBFastbootTools.jar
Click on menu--> Check for device , when device is found click menu-->Reboot device to edl
Now run XiaoMiFlash.exe and press refresh. device will be detected as com , where n is the port number. If device is not detected, click on driver menu on miflash and reinstall driver.
Now select the extracted fastboot rom folder. click clean all and click flash.
It takes some time to flash and when flashing is done reboot device by long pressing power button for 10-20 Seconds.
---------- Post added at 02:21 PM ---------- Previous post was at 02:17 PM ----------
***keep in mind that the phone only starts working correctly after 4-5 reboots and a 1 day or 2 after restoring persist and so random sensor stuff is usual ...give it a day or so and be patient with random behaviour for a day ..like reboots and wifi or gps trouble ...this is regardless of the root you took
PsK2010 said:
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
Click to expand...
Click to collapse
duh stupid ...i forgot to mention that if you have jasmime 2x of all partition ...you need to flash the persist in both A&B slots
so after flashing in slot A select slot b in reboot section..reboot to RECOVERY ..then flash persist again ...the in reboot section select slot A amd revoot to recovery then when you are now safely back in slot A choose reboot to boot your phone normally
i failed to mention this because im on wayne which is the same phone but with a A only partition ..
:silly:
Yeah I think I did flash the persist on both A and B slots, anyway, I tried it again, but even if it seems to flash I have an error 'unable to mount storage', maybe it's due to the "twrp-3.3.1-5-jasmine_sprout-unofficial.img" I'm booting on (I boot from the img file, with fastboot boot command).
If I still have the GPS fix issue, I'll try flashing persist on both slots but this time using the default twrp (twrp-3.3.1-3-jasmine_sprout.img).
Again, thank you for your time!
PsK2010 said:
Yeah I think I did flash the persist on both A and B slots, anyway, I tried it again, but even if it seems to flash I have an error 'unable to mount storage', maybe it's due to the "twrp-3.3.1-5-jasmine_sprout-unofficial.img" I'm booting on (I boot from the img file, with fastboot boot command).
If I still have the GPS fix issue, I'll try flashing persist on both slots but this time using the default twrp (twrp-3.3.1-3-jasmine_sprout.img).
Again, thank you for your time!
Click to expand...
Click to collapse
if your gps problem continues I would suggest flashing the whole stock rom in edl mode with xml modified to flash persist and then it will definitely work but as we're both aware that is a mission you probably don't want to have to do d
the reason the unofficial twrp exists is because the official one has problems and has never "officially" been fixed entirely to support encryption on both pie and Q
I'm also pretty certain it can't "see" nor backup or mount and definitely not write to the persist partition but i haven't checked recently
if you go to the backup tab or mount tab and persist doesn't appear as an option the recovery can't write or flash anything to that partition usually
the recovery i linked was modified by a Russian over at 4pda to specifically support .img files and also mount and write to persist partition
you can change the language from Russian in the settings tab ..second from the bottom right
Hey, after reverting back to Stock Pie (with flashing the persist from the official stock image thanks to @KevMetal's instruction), I still didn't got a good GPS reception (0/40 satellites) and noticed that bluetooth reception was weaker than before I replace my screen.
I then dediced to disassemble the phone again to check the antenna and other connections, and then realized : some parts were missing in the replacement frame I bought!
As you can see on the picture, some metallic contacts were were missing on the new screen support frame (old frame below the new one), I just got them off my broken screen support, stick them in the new support frame and BOOM : I FINALLY GOT BACK GPS SIGNAL + awesome bluetooth signal too!
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.