Related
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 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!
Hi
I have a Samsung Galaxy S9 (SM-G960F) Exynos, branded under Australian Optus and have been trying to load the latest Lineage Rom onto it but have ran into a multitude of issues. I'm going to list all of the things I've done and the Errors I've recieved
Developer Tools Enabled -> OEM Unlock Enabled (Forced Wipe) -> Developer Tools Enabled -> OEM Already Enabled -> USB Debugging Enabled -> ADB Tools installed and enabled (Computer trusted)
From Heimdall I tried flashing Lineages own bootloader from their website. I ended up getting the error "Failed to Receive Session End Confirmation"
My phone would also display the message "Only Official Released Binaries Are Allowed To Be Flashed"
I was also told RMM State played a part in this and if it was Prenormal, it wouldn't work. I went to check and sure enough, my phones RMM State was Prenormal
Despite this, I tried sideloading the packages anyway because I was told that just because it said that message, didn't mean it failed. Those ended up also failing, telling me the installation was aborted because of a validity error
From there, I was told to use Odin. That failed. I ended up switching to TWRPs bootloader instead and that also failed
After that I tried Flashing the Stock Android 10 Rom but that didn't solve any of the issues
I also tried downgrading to Android 8 Oreo to see if I could load everything from there but got the error SW REV CK FAIL
Dr Ketons Guide did not work as I was unable to Flash TWRP so I couldn't follow that route
I have the no Verity File downloaded but no way to apply it. Same with Magisk and Magisk Manager
Does anyone know what I can possibly do to try and get these things loaded onto my phone. I really would like to get them working as my main sim card is Vodafone so I'm unable to use it with this phone. Flashing the Stock unbranded XSA rom didn't seem to fix this issue either. The phone isn't under any contract or warranty, however I have no idea if its locked or unlocked.
Thanks
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
B1nz said:
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
Click to expand...
Click to collapse
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
CrashSpyro said:
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
Click to expand...
Click to collapse
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
B1nz said:
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
Click to expand...
Click to collapse
Unfortunately I have already tried that and it ended up not working
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Latest OTA for le2123 is in the screenshot, are you updating using oxygen updater?
Are you out of file space on your phone?
@Appreciative I'm not out of space. 80Gigs are free.
@AndyC76 the system settings want to update to C.47, oxygen updater to C.64. The C.64 Full ROM shows an Error when I try to do a local update.
@nurbs999 what hardware version is your phone? You'll find this in the box.
I am puzzled, the screen shot i posted earlier shows c64 is the current version of oos A12 that has been pushed ota to my le2123.
AHH so I read from your message you're using oxygen updater attempt a local update c64 update
Before we go any further, which working version is currently installed on your phone, we know it's not c47, as you got an OTA update asking you to upgrade
Very strange, something got confused
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
There is an OOS 12 update before the Oxygen Updater app update. Use the OOS system update and not oxygen updater app
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
just let the system do what it has to do.
Update thru OTA System. Even if it fails once, do the updates again until you reach lastest official OTAs
fiskhest said:
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
Click to expand...
Click to collapse
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
And for me, I've probably tried the OTA update 20 times over a span of six months before I did a complete reflash with latest msmtools, hoping that would solve my issue. After reflash, I did five more tries before I started looking for alternative solutions. Are we supposed to just bash our heads on the failing OTA update until it (hopefully) succeeds?
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
I have the same problem
Unlock bootloader, flash rom via recovery (you will not be able to relock it after updating)
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
Are you able to reflash the latest Android 11 (10.10 version)?. This ways you would make sure you have the latest on both slots. From there just OTA system to get the latest
@Steve0007 I just tried that. I downloaded the image from here
The OTA update still fails. Same behaviour as before.
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
What you have furnished is the OOS version. What we are asking for is the initial hardware version viz. whether China, India, Global etc. As the user you are replying to says, it will be on the box the phone came in.
nurbs999 said:
I'm not out of space. 80Gigs are free.
Click to expand...
Click to collapse
That is for the data partition. What is the space left in the system partition since the OS will install to that?
Hm, this is the only label I can find.
nurbs999 said:
Hm, this is the only label I can find.
View attachment 5726527
Click to expand...
Click to collapse
There it is, it is a LE2123. It is a EU model and it seems to be flashed with the EU version of OOS as stated by you. Now let others more knowledgeable than me reply to you.
I've posted here for you,
One option you have is to use the MSM tool and go back to full and working stock.
Post in thread 'OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)' https://forum.xda-developers.com/t/...ick-tools-tmo-eu-glo-in.4272549/post-87526839
@AndyC76 thank you.
Well.. That is the one I've reflashed and tried with on my end, with no change in behavior. I'll have to wait a couple of days until I am able to reflash again. Hoping you have better results than me @nurbs999 !
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: