Hi everybody,
i have a new Mi A2 Lite. I purchased it from a private person, not a shop, but it was still in foil and opened by me. It works nicely, is fast, the phone feels fine, i like it. It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates. The same for the security patches - they are from nov. 2018, which is nearly a year ago, but there are no updates either.
I wanted to install android 9, so i did lots of tricks and things like using a VPN to poland and resetting the phone and so on, but to no avail - there are no updates.
so...
(1) is there something that can be done wrong? why wouldnt the phone find updates?
(2) is there a way to flash the official OTA zip without unlocking? I do not want a special kernel or rom, i dont want to modyfy anything on the os, i just want the official, latest os on the phone
(3) Any other ideas?
Thanks in advance
damaltor said:
It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates.
Click to expand...
Click to collapse
Hi!
Could you please share a screenshot showing your actual Android build number and kernel version? You might have a fake A2 lite (Redmi 6 Pro).
Edit: Don't flash anything before you're sure that your device is a geniue A2 lite, otherwise you will brick your device.
yep, i heard about that. unfortunately, i did flash it by now, but the flash worked perfectly. i unlocked the bootloader with fastboot, flashed the last fastboot package, and re-locked the bootloader. the device is now on android pie and it still works nicely. is there any way to find out if it is genuine after flashing?
So, now i can say the following:
- the deveice works still well with the flashed software.
- the device did just find and download the google security patches of sep 2019
- the imei of the device passes the xiaomi authentication test
so, i am somewhat sure that the device is an original.
still, i am interested why the device was stuck on the old version. maybe it could only handle incremental updates and the old incremental update was not available anymore?
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
My screens:
ibb.co/SKjNJ6D
ibb.co/YR4793D
Regards!
Facing The same in my Mi A1
The same thing is happening with my Mi A1, I have Android 8.1 an I hadn't update to Android 9. Every day the notification for Android 9 would appear in my phone, saying that is available.
Today that update didn't show and when I checked for updates, it said I was already up to date.
Sorry for my English, I barely know it
Well i could probably Help you to flash your device but you should be sure that the device is not a fake, too. I cannot help you with that though. I will look in here tomorrow and give you a few hints to the flashing process.
So, the screenshots of the A2 Lite look pretty mich exactly like mine did. for me the only way was to reflash the device. if you are interested, i can tell you how, but there is a risk of bricking your device if it is a fake a2 lite. i cannot tell by your screenshots, maybe @thorin0815 can?
Otherwise, do you want to try it and risk ist?
edit: you can put in your imei here to check your phone, though i would not entirely trust it.
https://www.mi.com/global/shield#imei_en
*Deleted* *replay *
chriss7777 said:
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
Click to expand...
Click to collapse
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
well, thats what i did. fortunately there is no longer the need to wait for hours or days to unlock the bootloader, it works in an instant now even without registration.
thorin0815 said:
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
Click to expand...
Click to collapse
I did not notice what update it was downloading. I unboxed it, then I connect to WiFi and it started downloading. Anyway it downloaded aprox. 1GB of data, then restart and update. And now it is stuck with 8.1. I thought it will be Android 9 after update with latest patches.
I validate IMEI's on site and it is valid, also it has all google logos, and so on.
Is there any comprehensive update manual for MiFlash for this model?
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Switch on your phone.
Go to settings, about phone.
Tap the build number multiple times until "you are a developer".
Open the developer options.
Switch on USB debugging.
Switch on "allow unlocking bootloader".
Leave settings.
Download this, and install it, answering yes to all three questions:
https://forum.xda-developers.com/showthread.php?t=2588979
Connect the phone and when asked, accept the adb debug question on your phone. Your computer is now allowed to debug your phone.
Also download your new os from here:
https://xiaomifirmwareupdater.com/miui/ (put your phone model in there and download the latest fastboot image)
Unpack it. Depending on your packing program you might have to unpack twice - you should have a few folders and files.
Download the mi flash tool here:
https://www.xiaomiflash.com/
Now you are ready. Take a deep breath. Make sure your phone is charged, 50% should be enough.
Disconnect and Switch off the phone. Hold volume down and power until a rabbit working on an Android robot is seen on the screen. Now reconnect the cable.
Open a command window on the computer by pressing windows+R and entering "cmd".
In that window, type "fastboot oem unlock" and press enter. You should get the answer "OKAY".
If your phone reboots now, hold volume down and power again until the rabbit is there again.
Start miflash. Show miflash the folder in which you unpacked the os files.
In the lower right select "clean and lock" and then press update, select your phone, and press flash.
Flashing now takes roundabout 5 minutes.
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
damaltor said:
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
Click to expand...
Click to collapse
It works like a charm. Also now it is updating with new security patch. Thanks damaltor!
No problem, good to hear that it worked!
Related
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
I have a Redmi Note 5, bought on UK Ebay in Summer 2018 with a Global MIUI 9. For over a week my phone informed me there was an update to MIUI 10. So today I decided to up it like I have done with previous MIUI 9 incremental updates.
My phone gave me an option to update and it downloaded the image and then asked to restart so I did like I have done in the past for v9 incremental updates.
It download the new ROM and I accepted the Restart Phone. After restarting I got a warning message at the bottom of the screen in red "This MIUI version can't be installed on this device" and the options are:
1. Reboot, which just brings me back to this same screen on startup.
2. Wipe Data. This goes through a wipe storage but it doesn't make any difference and just brings me back to the same screen after a restart.
3. Connect with MIAssistant. With MiPCSuite installed, it doesn't connect and just hangs.
Chatting to Mi Support, they tell me they don't recognise the phone even though I provided the IMEI number and the fact it is less than 1 year old. I bought it off Ebay new unused.
So now I have a bricked useless phone. Well done Xiaomi!
Any suggestion guys?
moby17 said:
So now I have a bricked useless phone. Well done Xiaomi!
Any suggestion guys?
Click to expand...
Click to collapse
Solution here
c.mi.com/thread-2251372-1-1.html
moby17 said:
I have a Redmi Note 5, bought on UK Ebay in Summer 2018 with a Global MIUI 9. For over a week my phone informed me there was an update to MIUI 10. So today I decided to up it like I have done with previous MIUI 9 incremental updates.
My phone gave me an option to update and it downloaded the image and then asked to restart so I did like I have done in the past for v9 incremental updates.
It download the new ROM and I accepted the Restart Phone. After restarting I got a warning message at the bottom of the screen in red "This MIUI version can't be installed on this device" and the options are:
1. Reboot, which just brings me back to this same screen on startup.
2. Wipe Data. This goes through a wipe storage but it doesn't make any difference and just brings me back to the same screen after a restart.
3. Connect with MIAssistant. With MiPCSuite installed, it doesn't connect and just hangs.
Chatting to Mi Support, they tell me they don't recognise the phone even though I provided the IMEI number and the fact it is less than 1 year old. I bought it off Ebay new unused.
So now I have a bricked useless phone. Well done Xiaomi!
Any suggestion guys?
Click to expand...
Click to collapse
Is it normal to just blame Xiaomi for all faults the user has done?
xell75 said:
Is it normal to just blame Xiaomi for all faults the user has done?
Click to expand...
Click to collapse
Kurumi best girl!
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Says "everyone" but then leaves out RM6R
Gunhawk32 said:
Says "everyone" but then leaves out RM6R
Click to expand...
Click to collapse
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
I did a completely clean update. I completely formatted it, deleted all partitions /even the "persist" by accident, but I managed to restore it, but that's another story/.
Then I reset the phone using the Mitool-EDL method and then updated the clean system to EUCommon-V5.10.
The only mistake is that it lists the battery as 3550 mah instead of 5050 mah.
What you write about not receiving calls on Wi-Fi, etc., also occurred to me on the V3.28 system. If I set the mobile network as preferred in the vowifi settings, the error disappeared. Now I haven't experienced this error, vowifi works normally even in wifi preferred mode.
So far, I have not experienced any errors apart from the incorrect listing of the battery, although I cannot test 5G because it is not yet installed at our place...:/
Pisti870923 said:
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
Click to expand...
Click to collapse
I doubt it since it took 7-9 months for the android 12 update to release globally for the RM6 & 6 pro after it came out in china.
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
bro i have the same issue
do you solve it
Please i
Pisti870923 said:
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
Click to expand...
Click to collapse
do you have instructions or video .i dont have experience with that
moatazamer83 said:
do you have instructions or video .i dont have experience with that
Click to expand...
Click to collapse
I'll describe how I did it, but I can't promise that everything will work the same way for everyone. I don't know if there are hardware differences between each phone because I could only test it with mine /RM6P/. If someone tries it, do it at your own risk!
Be sure to save the "persist" partition before doing anything!!! Also save Qcn, these two are very important!!!
1. Backup partitions:
2. Backup Qcn:
3. /Optional/ Erase ALL:
After backup, I entered the partition manager in qfil, and after right-clicking, I clicked on "erase entire flash". But it's not absolutely necessary, but I definitely wanted a clean install. When I returned from Chinese Android 12 to EU 11 and didn't do this, the first time I started it, the phone setup got stuck in the wizard and wouldn't let me continue. From this I realized that the Mitool-EDL method alone does not completely clean the phone.
If you have completely reformatted the phone with qfil, you will need to restore the "persist" partition and Qcn with qfil after Mitool is finished. If you haven't formatted it completely, you don't need to restore it, but you should still have a backup of them, you never know when you'll need them, believe me!
4. And here is the description of the much talked about Mitool-EDL method:
RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU
Hello guys, I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU. The process is super easy: 1) Download &...
forum.xda-developers.com
5. Update rom:
If you're done with Mitool, you download the ROM you want, copy it to the internal storage and install it with local update in system update!
I did it this way and still found no errors. (Except that it says the battery is 3550mah). I use the EU510.
After Mitool finished, any rom goes up with local update, I tried EU328, UN428, CN810, UN610 and EU510
This method did not require unlocking the bootloader.
According to my theory, I could root with qfil without opening the bootloader, but I haven't tested it yet. If I try it sometime, I will write about my experience.
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Pisti870923 said:
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Click to expand...
Click to collapse
oh my god i can't do it bro
but thx alot for your help should i wait fix from company
moatazamer83 said:
bro i have the same issue
do you solve it
Please i
Click to expand...
Click to collapse
Bro me to i don't have network for calling before it wasn't a probleem but android 12 is smooth tho sad Nubia has to present it like this
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
Bro i got same network problem it's really sad Nubia has to present android 12 like this tho do you know something more
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
thx bro i will wait for your feedback .should i reset before installing
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
moatazamer83 said:
thx bro i will wait for your feedback .should i reset before installing
Click to expand...
Click to collapse
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
I've installed it too the network problem seems to be fixed but I need time to to confirm if this is solved
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
An Droid said:
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
Click to expand...
Click to collapse
I have EU version the changelog is the same as v.5.10 idk why
I think only if you get it with an OTA update... This is what I see:
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
greypilgrim said:
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
Click to expand...
Click to collapse
The best way to clean up your phone is the MSM program.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
HolyHog said:
The best way to clean up your phone is the MSM program.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I've tryed... but It seem that doesn't work..
greypilgrim said:
Thanks, I've tryed... but It seem that doesn't work..
Click to expand...
Click to collapse
Make sure all your computer drivers are up to date including the optional ones.
Don't try to get in EDL mode. Start MSM and hit the start button so it will be looking for your phone. Plug it in to your computer and hold down volume up + volume down and the power key. It can be off or on when you start this. It should grab hold and start installing and then let go of the buttons. When you hard reset from an phone that's on, it puts in EDL mode automatically.
HolyHog said:
Make sure all your computer drivers are up to date including the optional ones.
Don't try to get in EDL mode. Start MSM and hit the start button so it will be looking for your phone. Plug it in to your computer and hold down volume up + volume down and the power key. It can be off or on when you start this. It should grab hold and start installing and then let go of the buttons. When you hard reset from an phone that's on, it puts in EDL mode automatically.
Click to expand...
Click to collapse
I've tryed as you said, but msn still has "param preload fail" . I'm tryng to use the package instantnoodlep_15_E.34_210201.
greypilgrim said:
I've tryed as you said, but msn still has "param preload fail" . I'm tryng to use the package instantnoodlep_15_E.34_210201.
Click to expand...
Click to collapse
That Param preload fail error cause you don't have the qualcomm driver. Check the MSM page for the download.
greypilgrim said:
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
Click to expand...
Click to collapse
There is a comment somewehere that says u have to mod of a newer rom a txt...
I think that's your solution. If u know the exact odel u have (and region) use oxygen updated to download the correct rom
Inside zip file (I open it in 7zip) open "payload_properties.txt" in Notepad and change one line from:
oplus_update_engine_verify_disable=0
to:
oplus_update_engine_verify_disable=1
And save it - I do it at computer so 7zip repack only this changed file.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
I am sure there is an xda link for this, but it is the same thing...
Jimger is right, one addition. Don't extract payload_properties file, but rather edit it in archive. Idk why, but only editing file while being in archive works for me. Additionally you MUST have OPLocalUpdateForAndroid12.apk to make it work. When i was on OOS12 i installed beta 2 of OOS13 this method, then upgraded to Global OOS 13 when it was out, then yesterday i flashed EU version (sincerely i don't see any difference, only for some reason in IN build i got... VoLTE somehow), so now i'm at OOS13 EU.
ShadoV90 said:
Jimger is right, one addition. Don't extract payload_properties file, but rather edit it in archive. Idk why, but only editing file while being in archive works for me. Additionally you MUST have OPLocalUpdateForAndroid12.apk to make it work. When i was on OOS12 i installed beta 2 of OOS13 this method, then upgraded to Global OOS 13 when it was out, then yesterday i flashed EU version (sincerely i don't see any difference, only for some reason in IN build i got... VoLTE somehow), so now i'm at OOS13 EU.
Click to expand...
Click to collapse
So, I've to download oo13 from op, edit that file and instal? Let's try!
Hi! I got a Samsung Galaxy A52s 5g that i bought from a store as second hand. They give a 14 days waranty but I don't really have the time to send the phone to service.
My problem is this... The phone right now has android 12 one ui 4.0 with Android security patch level from march 1, 2022. I want to upgrade it to android 13, but everytime I try thru OTA it fails at 25% and comes back to original saying Failed to install update, contact a samsung service center. Or something similar.
I found on the web that updating thru Samsung Smart Switch should work, but for me it doesn't. It downloads 7.3 gb of updates, after that phone enters download mode and I get after some time a NOTICE on the computer that "failed to recognize software update mode" and instructs me to reboot device and try again. I even enabled USB debug mode and I get the same NOTICE on the computer. And after that I reboot phone from downloading mode and everything is back to original.
The phone was charged 50%+ everytime i tried, also I got enough rom memory, I checked. Changed usb cable to another USB on the laptop and I get the same result from Smart Switch.
Phone model is SM-A528B/DS. I will provide more info if needed.
What I can do to succesfully update the software on my A52s 5g? I searched on the web to no result to my Smart Switch error. Also I've seen that are alot of cases where thru OTA the phone fails at 25%, but either they succesfully updated thru Smart Switch or no response.
I want to try installing the official rom from sammobile but I really don't know what firmware I should pick.
Thank you in advance!
A528BXXS2DWB5
Unreal_Hawkz said:
A528BXXS2DWB5
Click to expand...
Click to collapse
Does it matter from what carrier did the phone come from? The baseband is different from the file that you posted. Or doesn't matter? Anyway, downloaded it, now i'm looking for a tutorial on how to flash the rom. Thanks!
Unreal_Hawkz said:
A528BXXS2DWB5
Click to expand...
Click to collapse
Can I use update from SD card from recovery mode? It's easier i guess.
I just flashed the rom you provided. Hurray! It works just fine with odin. If anybody got the same problem with their phone, flashing with odin does a great job!
God bless you Unreal_Hawkz!