Hi everyone,
As most of us that update our Mi A2 lite to Android Pie downgrade to Android Oreo.
Beside the problems with Sim swap and Sim2 not working i 've notice that in Google Play app i don't see anymore the 3 dots for everyapp, i used the 3 dots shortcut to start the install of an app before entering in its page.
Thank all and keep up the good work.
I hope someone can help with this issue because reverting back to pie does not fix it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ahh! That isn't an issue because you downgraded, it's just the way Google Play has been recently updated (server side I believe), just press and hold on the app and it should do the same as the 3-dots button
Sent from my Xiaomi Mi A2 Lite using XDA Labs
i think now solved
Thank for feedback.
After many tries of update and downgrade i think now is ok, long night :|
I will see again after upgrade with the most recent android pie that hopefully will solve the wifi issue.
So what i did is to put the phone not on fastboot oem unlock or fastboot oem unlock_critical,
but on fastboot oem edl then modified rawprogram0.xml with adding dummy.img and persist.img in the specied lines from this guide https://forum.xda-developers.com/mi-a2-lite/help/sim-card-issue-downgrading-pie-9-0-t3874350/page5 and now i have the 3 dots on the apps.
Again thank you for support.
florinellu said:
Thank for feedback.
After many tries of update and downgrade i think now is ok, long night :|
I will see again after upgrade with the most recent android pie that hopefully will solve the wifi issue.
So what i did is to put the phone not on fastboot oem unlock or fastboot oem unlock_critical,
but on fastboot oem edl then modified rawprogram0.xml with adding dummy.img and persist.img in the specied lines from this guide https://forum.xda-developers.com/mi-a2-lite/help/sim-card-issue-downgrading-pie-9-0-t3874350/page5 and now i have the 3 dots on the apps.
Again thank you for support.
Click to expand...
Click to collapse
What the hell Dude three dots were gone because of an update to Play Store, nothing like a bug or something
Just tap and hold and the shortcut apears
Related
I received an OTA update for miui on the device. I proceed to download the update from settings where the update is displayed. I reboot to install update, and It bricked . on the screen i have mi recover 3.0 with 3 options which are reboot, wipe data and connect to miAssistant. I've clicked all its not coming up. I've tried to use testpoint method to flash fastboot ROM and its not working. Screen now blank and rebooting. Help
Did you unlock it's BL?
tharejamohit said:
U need to mi auth account to solve the issue
Click to expand...
Click to collapse
Do you also have to put it in 9008(COM) EDL mode by shorting it after opening it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to get mi authorized account is the guy's challenge so far.
Has anyone tried this (2nd) method to put your Xiaomi 6 Pro in EDL mode?
https://www.xiaomigeek.com/edl-mode-xiaomi.html
Not lots of traction in this Redmi 6 Pro forum yet but I figure I will put it out there, I didn't want to open my phone to put it in EDL mode.
I went to a service centre, they accepted to fix my phone without charge, I thought they will be able to flash it on the spot but they rather send it back to swap the motherboard.
Sethide said:
Not lots of traction in this Redmi 6 Pro forum yet but I figure I will put it out there, I didn't want to open my phone to put it in EDL mode.
I went to a service centre, they accepted to fix my phone without charge, I thought they will be able to flash it on the spot but they rather send it back to swap the motherboard.
Click to expand...
Click to collapse
that is just how the service centre works, don't know for what reason they swap mobo instead of flashing it back, they have the tools.
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
Hi everybody, big newbie here. Can someone explain to me step by step how to do this ? I think its the only way to make the Mi A2 Lite work correctly again ...
Yes, it's possible and go for EDL mode and then flash it via MiFlash. I've tried downgrading some time ago and that's the safest way to not mess up connectivity. Search for it, it's here on the forum. But frankly, why would you want to do that? I've been through many custom ROMs, tried many kernels, settings, etc., but I always come back to the official one. The reason is in the attached screenshot. It wasn't possible on any custom and until the official update to 11.0.7.0 (I was getting max 3 days on earlier builds). My method: install/update, clean all through the built-in recovery (mind that it's tricky to get into), then restore everything from Google cloud.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Mi A2 Lite using Tapatalk
locovibe said:
Yes, it's possible and go for EDL mode and then flash it via MiFlash. I've tried downgrading some time ago and that's the safest way to not mess up connectivity. Search for it, it's here on the forum. But frankly, why would you want to do that? I've been through many custom ROMs, tried many kernels, settings, etc., but I always come back to the official one. The reason is in the attached screenshot. It wasn't possible on any custom and until the official update to 11.0.7.0 (I was getting max 3 days on earlier builds). My method: install/update, clean all through the built-in recovery (mind that it's tricky to get into), then restore everything from Google cloud.View attachment 5080065
Sent from my Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
how is this possible ? most people including myself have huge battery/ram problems with android Q
RAM has always been huge. Here's mine.
Sent from my Mi A2 Lite using Tapatalk
Well I taught myself to turn off stuff I don't need at the moment, especially mobile data, when I'm on WiFi. BT always on.
Sent from my Mi A2 Lite using Tapatalk
I have a Mi 11 lite 4G . I was using Indian rom and switched to global rom recently to try out Android 12 and miui 13.now here I am not able to use Google apps like gplay,mail,chrome. And even camera isn't working .I want to go back to older rom but it shows this error which I have attached here. Please someone help me ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey bro you somehow softbricked your device. make sure you have a backup and flash latest firmware through mi flash tool. This wil format complete storage and reinstall it as new.
if you have unlocked the bootloader before you should not use the relock option in mi flash tool.
Download Xiaomi Flash Tool - Xiaomi Mi Flash Tool Download
Download Xiaomi Flash tool is for Xiaomi smartphone and tablet device users that runs on Windows PC platforms to flash fastboot firmware files on Xiaomi smartphones. All versions of Xiaomi Mi Flash Tool download is available here
www.xiaomiflash.com
Unless modded, patched or worked around, SafetyNet wouldn't pass on that device.
Certification could... if the Play Store doesn't take ctsProfileMatch into account because that part would be false, at the very least because of the unlocked bootloader.
In any case, the usual procedure should suffice:
Set phone to Fastboot mode (Vol- pressed at power on).
Flash the appropriate ROM either manually or using any of the Fastboot GUIs (e.g. Mi Flash).
That's about it, re-lock bootloader if you wish, don't think it's necessary.
Besides, if you get the same outcome after the procedure (say the unlocked bootloader mattered and you don't want to root or patch anything), you can always lock it, and then clear the data of the Play Store and Google Player Services (for good measure haha); it should force it to reevaluate its certification status.
And yeah, clearing user data is probably appropriate when flashing.
Don't be so hasty with MIUI 13, you're not missing much
I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them
yenzenko said:
I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them
Click to expand...
Click to collapse
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/
NOSS8 said:
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/
Click to expand...
Click to collapse
I fixed it with another method thanks for reply
yenzenko said:
I fixed it with another method thanks for reply
Click to expand...
Click to collapse
how you fix it? i have same issue
Here is the way I fixed it
1. the main instruction is here. You need to download your firmware (in my case it's V13.0.2.0.SGDMIXM | 12.0 GLO), and flashtool.
2. Also you need tool to disable SLA authentication. The instruction has its own link to guide, however I decided to use different tool, MTK Auth Bypass Tool V44 from here. You click disable auth, then press volume up+down and connect phone to computer. You need to do it while phone screen is black
Spoiler: screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. then you are flashing with sp flashtool. Choose your scatter xml file, then press download (you need to do previous step every time you are trying to flash firmware). In my case I've got error about wrong value of combo_partsize_check, so I edited all "<combo_partsize_check>true</combo_partsize_check>" to "<combo_partsize_check>false</combo_partsize_check>", and after that it worked just fine. At least I could boot phone to fastboot mode and recovery, haven't decided what to do next