Related
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
I've been trying to figure out if I should do UPGRADE or REFURBISH as well.
I found this: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-upgrade-downgrade-restore-t3738917
Says REFURBISH wipes user data, UPGRADE does not. If moving from one image say from AT&T, to the Unlocked firmware I'd assume you want REFURBISH.
So since I used refurbish to go to the ulm software from 7 to 8, do I still need to refurbish going to any of the ulm pie variants?
Shawnashley said:
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
Click to expand...
Click to collapse
That's what threw me for a loop on my first attempt. Since I'd successfully upgrade from the AT&T 7.0 firmware to I believe the Amazon 8.0 ULM firmware without issues, I thought the process would be the same going to 9.0. But I ran the upgrade through LGUP which was the modified version, and it crashed at 74% and sent me down a wonderful rabbits hole of brickage.
X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz.
I went from AWM12k to ULM10i choosing REFURB and all went well (I followed xatokk's post on the lgV35 subreddit).
When I try to get from ULM10i to ULM20d (Pie .kdz) I guess I only have to drag ULM20d kdz in LGUP window?
I just want to make sure that's not how you bricked your phone before I try REFURB from ULM10i to ULM20d
Any advice would help, I'm a noob at this.
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz
Click to expand...
Click to collapse
Sorry, Brainfart, I was completely out to lunch on that. I wanted to flash the latest available security update, but since I'm in Canada I could never get that from AT&T so I had to find a way to flash it and that led me to XDA and the whole LGUP process. So you were correct on that, and I did flash the Amazon 8.0 KDZ I believe without issue.
My brick happened when using the Amazon pie KDZ and using the same Upgrade process in LGUP. The update got to 74% and then crashed. I then tried to run the refurbish option but that crashed as well so by that time, my phone was beyond my knowledge of how to fix it
cmrntnnr said:
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
Click to expand...
Click to collapse
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?
Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo.
Click to expand...
Click to collapse
This phone launched with Oreo and had nothing prior. He's mistaken, confusing some other model.
That's what I did.
The error you experience may be due to a usb cable. a particular usb port on your computer, other software on your computer, and maybe bios settings. The v30 WTF and Frankenphone forums would be good places for background and solutions.
Fingers crossed for a successful flash.
Neophy said:
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?
Click to expand...
Click to collapse
Here's what I did if you don't already found a way. I also faced an error trying to flash to Pie ULM.kdz.
I don't know why but LGUP for developer patched from 9to5lg.com didn't work for me. I tried PARTITION DL it crashed at 91% and I also had to reboot my PC. I kept the phone plugged and reinstalled LGUP.
My V35 was on AWM12k when I got it. I followed xatokk's post on the lgV35 subreddit to get it to to ULM10i choosing REFURB.
I kept the same .dll I extracted from to ULM10i and I did a REFURB to ULM20d .kdz just dragging it to LGUP.
I hope this can help you.
To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.
Truth
MorningStarGG said:
To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.
Click to expand...
Click to collapse
@motogvasyag unbricked my AT&T V35 that was stuck in fastboot from a failed flash. Took care of it right away. Phone is now factory LG on Google Fi, Pie, wifi calling and all three carriers. Highly recommended!
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
In the same guide post if you look on page 6 you will find how people have updated to pie retaining fastboot.
It can also be used to use a pie vm rooted stock rom also.
MaitiuD2 said:
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Click to expand...
Click to collapse
Thank you very much for responding.
And that really sucks about fastboot and Pie, now I have to wonder how LameMonster82 did it in his guide . Someone else there tried installing that TWRP from Oreo, and got his phone bricked for it.
Halogen_03 said:
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Click to expand...
Click to collapse
Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot.
"Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot."
-----------------------------------------------------------------------------------------
I have the ULM model as well but the G710EM20d Model doesnt boot to fastboot. Could you tell me the KDZ file you used?
Example, "G710EM10b_00_0521.kdz"
I'd really appreciate the help
u should cross flash the ulm firmware by lg up and then boot ur device in to the download mode after erase laf partition
Hi guys. I got a G8 from a friend whose friend's dad is a radio tower engineer for AT&T that got this phone early. It's a prerelease phone (says "not for sale") on the back, and it comes with software that is seemingly far behind what shipped with the public version of the device. It's Android 9 with the December 2018 security patch, SW version G820UM04b. This version is pretty buggy and doesn't have some features like air motion. It seems like the initial software release for the public phone was G820UM10g.
Whenever I try updating the device, it just says the software is already up to date. I've done more factory resets and tried more tricks than I can even recount. Got a fresh new SIM card. Called AT&T and got them to manually push the update to my IMEI (which is correctly registered), waited a day for the update. Tried LG Bridge but it's incompatible with AT&T devices. Looked for kdz files online for the AT&T version that I can flash using LGUP, but there's no AT&T files available (pls tell me if anyone knows of any out there).
I'm at my wit's end guys. Anyone have any ideas as to how I can get this phone updated? I'm realizing that I really took the ability to just unlock and flash my old OnePlus for granted
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
minhthien0711 said:
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
Click to expand...
Click to collapse
Sorry, forgot to clarify that. I live in the USA and I use AT&T.
On the face of it it's not looking good. There aren't any KDZs for ATT as standard, and you can't update OTA - one thing to check here is the S/N field, pre-production LG phones are usually missing this, which is usually why OTAs don't work.
However, pre-production devices can, sometimes, be cross-flashed. You could try using LGUP to flash a more recent US unlocked build. It is likely to give you the IMPL lock / mismatch / crossflashing not allowed error, but it's worth a shot.
If that doesn't work, your best bet will be to ask your friend's dad to take it in to work (when he can...) for whoever looks after devices for his team to flash it to production as a favour.
Just checked My daughters mi 10t lite and to My surprise it still runs 12.0.8.0
It seems there are newer versions but her Phone says that No newer version is avalilable when searching.
Also it seems Android security level is december 2020 which seems very outdated.
IT seems that there are newer versions so why Will the Phone not find Them.?
Mine is the same. Its my first Xiaomi and it surprised me too.
New ROMs are available for download in the app "MIUIdownloader" and instructions on how to install them can be found here:
How to Install Android Updates on Xiaomi, Mi, Redmi, and POCO smartphones with MIUI
Follow these instructions install Android updates / Stock MIUI Recovery and Fastboot ROMs on Xiaomi, Mi, Redmi and POCO smartphones.
www.xda-developers.com
The article says however that the ROMs are available in either Recovery or Fastboot formats, but for mine (Gaugin EEA) there is an "OTA" version available also. Strange that the OTA update isn't actually available "OTA"...
I haven't installed any yet as I only started looking today but I'm a newbie with stuff like this so I'll wait and see if anyone else chimes in and gives us some more pointers. I don't really want to brick my phone!
here you can find the latest EEA roms (12.5.7.0) with 2021 october patchlevel
Redmi Note 9 Pro 5G / Mi 10i / Mi 10T Lite (gauguin) Europe (EEA) Fastboot & Recovery ROM | XiaomiROM.com
Xiaomi Redmi Note 9 Pro 5G / Mi 10i / Mi 10T Lite (gauguin) Europe (EEA) official ROM, include stable, weekly and beta MIUI firmware which can be …
xiaomirom.com
When you scroll up to the top of the page you can find all variants.
Always be sure you download the corresponding RECOVERY image!
Then copy it to your device.
Open settings/ about Phone
tap a couple of times on the middle of the screen, till you get the notification "additional update features on" or similiar.
When you go now to the upper right corner w. the 3 dots, you will now see some new entries, select "Choose update package", then select the downloaded recovery image, and install it.
In your case, since your Versions are heavy outdated I recommend a full backup prior - it can mess up some settings or files.
Overandout said:
Mine is the same. Its my first Xiaomi and it surprised me too.
New ROMs are available for download in the app "MIUIdownloader" and instructions on how to install them can be found here:
How to Install Android Updates on Xiaomi, Mi, Redmi, and POCO smartphones with MIUI
Follow these instructions install Android updates / Stock MIUI Recovery and Fastboot ROMs on Xiaomi, Mi, Redmi and POCO smartphones.
www.xda-developers.com
The article says however that the ROMs are available in either Recovery or Fastboot formats, but for mine (Gaugin EEA) there is an "OTA" version available also. Strange that the OTA update isn't actually available "OTA"...
I haven't installed any yet as I only started looking today but I'm a newbie with stuff like this so I'll wait and see if anyone else chimes in and gives us some more pointers. I don't really want to brick my phone!
Click to expand...
Click to collapse
If/When you do the update, please report back what version you selected and if it did indeed needed af factory reset to work properly.
To be honest i think it is pretty poor, that this not just works out of the box, i have never heard of another brand where the OTA did not work, it's such a bacis function and i must confess, that if it ends up, needing me to do manual upgrading, this will heavily affect my will to buy og recommend anyone to buy a Xiaomi phone.
It seems the expression "You get what you pay for" is right in this instance, and i would certainly rather have paid a bit more to get something that just works, if i had known that even this basic feature did no work.
I wonder, if i update the phone manually to the latest firmware, if it will get the next updates OTA or this is a recurring thing, to do manual upgrades every time ..
Check you full FW version (including letters) - some ROMs are provided by phone operators and these are well known to delay or block the updates. Global ROMs should not show this behavior, I receive all OTA updates on time (or I just download and apply them manually as described by y1nk0).
Thanks for the suggestions but it didn't work.
I pasted the zip file into the phone memory and selected it in the update menu. The error message was Not possible to verify the update. You cannot flash this ROM, or along those lines.
It isn't an operator branded phone and it was brand new out of the box a few days ago so I suppose its possible that it gets an OTA update in the future, but yeah, I'm pretty disappointed with the phone in general really and was hoping that some of the poor features would be improved with an update to Android 11.
Its a work phone so at least I didn't pay for it, but it also means that I can't really do anything which might brick it, I got it to replace a Samsung A50 which I dropped and killed so I have to be careful!
The current ROM is 12.0.8.0(QJSEEUXM) which seems to be an official Mi ROM dated 22 Dec 2021.
I will check the full firmware version and post it here when i get home, but my daughters phone was bought from a large generic electronic retailer and it was bought without any subscription to any phone company and it has no visible branding at all, so i highly doubt that it will be because of this.
But as said...I will post the exact firmware version of the phone later, it would be interesting to see if it is the same as "overandout" has.
I dont know if the phone has actually ever received any updates, but i doubt it, as the safety level is December 2020, and she bought the phone in 2021.
Maybe there is a bug in that particular firmware that prevents it from succesfully updating.
I am thinking of maybe returning the phone to the shop, and reporting it to be faulty, because of the inability to upgrade.
Nowadays firmware and firmware updates are a big part of keeping a phone in "good working order" so the inability to update is certainly in my book to be consideres a serious flaw / defect.
I dont mind to update it manually to be honest, but i would expect it to then begin, updating by itself, i dont want to have to do manual updating every x months.
xsatquest said:
I will check the full firmware version and post it here when i get home, but my daughters phone was bought from a large generic electronic retailer and it was bought without any subscription to any phone company and it has no visible branding at all, so i highly doubt that it will be because of this.
But as said...I will post the exact firmware version of the phone later, it would be interesting to see if it is the same as "overandout" has.
I dont know if the phone has actually ever received any updates, but i doubt it, as the safety level is December 2020, and she bought the phone in 2021.
Maybe there is a bug in that particular firmware that prevents it from succesfully updating.
I am thinking of maybe returning the phone to the shop, and reporting it to be faulty, because of the inability to upgrade.
Nowadays firmware and firmware updates are a big part of keeping a phone in "good working order" so the inability to update is certainly in my book to be consideres a serious flaw / defect.
I dont mind to update it manually to be honest, but i would expect it to then begin, updating by itself, i dont want to have to do manual updating every x months.
Click to expand...
Click to collapse
So did you try the method posted by y1nk0? What happened?
The problem with loading the new ROM any other way is that we will be voiding the warranty...
Overandout said:
So did you try the method posted by y1nk0? What happened?
The problem with loading the new ROM any other way is that we will be voiding the warranty...
Click to expand...
Click to collapse
Hi
No i did not try anything yet, y1nk mentions that since the version is very outdated to make a backup, and i have not had time to do this yet.
Will probably do it this weekend, but i kind of need to have her make a backup of her phone....And i dont even know if she thinks it's worth the trouble if she has to start the phone from scratch after the update.
Teenagers have a LOT of apps and stuff on their phone, it's not just a matter of 5 minutes and she is ready to have her phone potentially reset to factory standard
But seeing as you had no luck i am not holding my breath for that method tbh. : )
Fair enough, I didn't bother with the back up because the phone is so new I hardly have anything configured anyway.
Overandout said:
Fair enough, I didn't bother with the back up because the phone is so new I hardly have anything configured anyway.
Click to expand...
Click to collapse
If you're on V12.0.8.0.QJSEUXM, I would try updating to V12.0.1.0.RJSEUXM first. Sometimes it's not possible to skip one or more updates and you have to install them one by one.
Chronological list of updates with download links: https://xiaomifirmware.com/roms/download-latest-miui-roms-for-mi-10t-lite/
_mysiak_ said:
If you're on V12.0.8.0.QJSEUXM, I would try updating to V12.0.1.0.RJSEUXM first. Sometimes it's not possible to skip one or more updates and you have to install them one by one.
Chronological list of updates with download links: https://xiaomifirmware.com/roms/download-latest-miui-roms-for-mi-10t-lite/
Click to expand...
Click to collapse
That makes sense. I went the other way and tried to install the penultimate version (12.5.6.0) but that gave the same error as the latest..
I'll try the "sequential" approach later.
Overandout said:
That makes sense. I went the other way and tried to install the penultimate version (12.5.6.0) but that gave the same error as the latest..
I'll try the "sequential" approach later.
Click to expand...
Click to collapse
Well, it was worth a try!
Exactly the same result unfortunately.
Not too sure what to try next really.
So i tried a bit here.
What she has is a phone that has the following firmware installed
MIUI Global 12.0.8.0
Stable
12.0.8.0 (QJSEUXM)
So i tried downloading the MIUI downloader tool and selected older versions, and downloaded the firmware called miui_GAUGINEEAGlobal_V12.0.1.0.RJSEUXM_15bfbef742_11.0.zip
put it in a folder called "downloaded_rom", went to the install updates, pressed the MIUI logo to make the "install from package" appear, selected this file and then it chewed on the file for 10-20 seconds and then it just says :
"Can not confirm update"
"Sorry, flash to this stable version is not allowed"
It feels really strange that a phone that has a firmware version called QJSEUXM is unable to update to a version called RJSEUXM
The only difference is that Q has become R, and since R comes right after Q in the alphabet, i would assume that this is the next version.
I am at a loss here, and the posts i made on the official Xiaomi forum, has gone unanswered.
One weird thing though.
I would expext firmware version 12.0.8.0 to be newer than 12.0.1.0. The naming of version seems a bit strange ??
The 12.0.1.0 version is android 11 and the 12.0.8.0 is android 10, so the 12.0.1.0 is newer it seems.
Still, makes no sense that it can not be updated, the file i downloaded is 2,5 Gbyte, so clearly a full image, not just incremental
Try to change your region in system settings (you might even receive an OTA update), updates are sometimes blocked for whatever reason for a particular country. India/China are usually first to receive an update, so they might work.
MIUI sub-version numbers are reset after major Android upgrade, so V12.0.1.0.RJSEUXM (MIUI12 Android 11) is newer than V12.0.8.0.QJSEUXM (MIUI 12 Android 10).
Btw. it seems that there was one more ROM update before moving to Android R (V12.0.9.0.QJSEUXM), you could have more luck with its installation.
List of all ROMs (sort by date and look for EU ROMs): https://xiaomifirmwareupdater.com/archive/miui/gauguin/
_mysiak_ said:
Try to change your region in system settings (you might even receive an OTA update), updates are sometimes blocked for whatever reason for a particular country. India/China are usually first to receive an update, so they might work.
MIUI sub-version numbers are reset after major Android upgrade, so V12.0.1.0.RJSEUXM (MIUI12 Android 11) is newer than V12.0.8.0.QJSEUXM (MIUI 12 Android 10).
Btw. it seems that there was one more ROM update before moving to Android R (V12.0.9.0.QJSEUXM), you could have more luck with its installation.
List of all ROMs (sort by date and look for EU ROMs): https://xiaomifirmwareupdater.com/archive/miui/gauguin/
Click to expand...
Click to collapse
Thank you for the reply, i have succesfully downloaded and installed the 12.0.9.0 firmware version on her phone.
So now it says :
MIUI Global 12.0.9.0 (QJSEUXM)
The android security level is now 01-01-2021
I then tried changing region to a lot of different countries, including countries in the African region, and India which i believe is in the asian region, and also a few european, it said "Changing region" multiple times, but no matter what country i tried, it still said "No available updates". This was offcourse with 12.0.9.0.
I feel that the speed with which it says "There is no update" kind of suggests that it might not even check, but i dont know if it does, and just really quickly figures out that there is no updates.
So while she got a marginally newer firmware with a 1 month newer security date, it still refuses to find OTA updates with 12.0.9.0 Android 10 by itself.
I also tried re-running the downloaded 12.0.1.0 Android 11 version i had previously downloaded, but it still fails with the same message as before.
It seems the update routine for this phone is really screwed. It was able to do the manual update to the newer android 10 but it refuses to do anything with the android 11 firmwares.
If anyone has more succes, i would like to hear about it. My teenage daughter is not prepared to do a full factory reset, so unless someone finds a way to do this without having to reset the phone, i think she will just want to keep the phone on the current firmware.
PS. I also tried disconnecting from our wifi, in case our firewall was blocking, but on 5G it still does not find any updates, really fast.
I can report the same as xsatquest.
The update to 12.0.9.0 has worked but thats as far as it goes.
I would quite happily do a factory reset to get to Android 11 as long as it doesn't involve unlocking the boot loader or anything else that invalidates the warranty.
I swapped the regions a few times too, but it didn't make any difference.
I have tried to follow some youtube tutorials on using MiFlash Pro to load the recovery image, just in case.
I tried to flash the first Android 11 version of the ROM from here:
Download Redmi Note 9 Pro 5G / Mi 10i / Mi 10T Lite (gauguin) V12.0.1.0.RJSEUXM MIUI 12 Stable Full Rom | XiaomiROM.com
The Stable update V12.0.1.0.RJSEUXM has been officially released for Redmi Note 9 Pro 5G / Mi 10i / Mi 10T Lite (codename is gauguin). Before …
xiaomirom.com
but the MiFlash tool gave the same error as the phone gives (more or less), Sorry, flash to this stable version is not allowed".
So I tried flashing 12.5.7 from here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
But its exactly the same...
Overandout said:
I can report the same as xsatquest.
The update to 12.0.9.0 has worked but thats as far as it goes.
I would quite happily do a factory reset to get to Android 11 as long as it doesn't involve unlocking the boot loader or anything else that invalidates the warranty.
Click to expand...
Click to collapse
I know that bootloader unlocking could be a PITA, but it does not invalidate the warranty (at least in Europe).
Edit: could any of you capture logcat during failed attempt for ROM installation? This might provide additional info on why exactly is it failing. Also you might give ADB sideload a chance, I don't expect it to really work, but maybe there will be some extra info too.
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Adelino80 said:
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Click to expand...
Click to collapse
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
AsItLies said:
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
Click to expand...
Click to collapse
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Adelino80 said:
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Click to expand...
Click to collapse
I would suggest that you look at the bkerler edl tools. Don't do anything until you backed up the device completely.