On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
stealthj said:
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
Click to expand...
Click to collapse
Let me download it again. Hope it works. If this does work, I will feel a lot better about updating my awesome phone in the future. Coming from Samsung on AT&T hopefully ASUS keeps the updates fairly regular.
Nope, still not working. Oh well, guess I can wait for the raw version.
But if anyone has any ideas on what I am missing, please chime in.
jkeener88 said:
On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Click to expand...
Click to collapse
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
xxBrun0xx said:
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
Click to expand...
Click to collapse
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
skromnia said:
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
Click to expand...
Click to collapse
Thanks, ya learning a lot on this phone. Just got figure it all out without bricking my ROG!
xxBrun0xx said:
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
Click to expand...
Click to collapse
Thank you so much for pointing me in the right decision, and also although I don't see that many Subaru vehicles in Houston, I plan on getting one this year or maybe next year. Thanks again, up to 1908 now. :good:
Chinese 8gb Tencent q
I'm on 1906 ww. I understand this phone needs a manual flash each time, do I need to flash with every update using raw files and will this also wipe the phone so every update means a wipe?
Can I root, install twrp and simply update the firmware no issue or is it bs?
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
viper98 said:
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
Click to expand...
Click to collapse
i just update to to latest one
u need twrp
put twrp and magisk and the update on root of ur device
flash twrp it will crash first time the next restart will work without any problem
flash and select the latest ota update that u downloaded from asus it take some time
then flash twrp again then flash magisk after all done reboot
work for me no problem
Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.
I just downloaded A10 firmware from Asus Website. I want to update but there was not any instruction on how to do that Please help me how to update. Also i want to know if update will wipe my internal data & Apps?
just put on internal storage then reboot your phone, your data is safe ?
It doesn't wipe but I would suggest to back it up anyway. I assume you have a tencent version?
Download the 2.5gb update, cut it and paste on your root folder (usually called internal storage). Reboot then it should prompt that there's updates available and just follow onscreen instructions..which is really just reboot after. This ONLY works if you have ww fw and ww fingerprint
This is what i did on mine coming from A9. Hope this helps. Again back up your data.
Napilitan said:
It doesn't wipe but I would suggest to back it up anyway. I assume you have a tencent version?
Download the 2.5gb update, cut it and paste on your root folder (usually called internal storage). Reboot then it should prompt that there's updates available and just follow onscreen instructions..which is really just reboot after. This ONLY works if you have ww fw and ww fingerprint
This is what i did on mine coming from A9. Hope this helps. Again back up your data.
Click to expand...
Click to collapse
Mine is WW fw and WW fingerprint but cannot update to A10, it shows that update failed after i reboot it.
Hey guys, same problem. Have WW for firmware and fingerprint but get update failed after reboot. Any ideas?
cant manual update too from .64 to latest android 10.someone,please help
cant manual update too from .64 to latest android 10.someone,please help
Be sure you are on the latest Android 9 version (1910.64) before trying to manually update to Android 10. So if you're not on the latest Android 9 yet (check under Settings > System > Software information), first download the 1910.64 USER zip, put in your internal storage main folder, reboot the phone, upgrade when it prompts you, then reboot. Then download latest Android 10 USER zip and repeat the process.
If for some reason that does not work, you can try updating through fastboot. You have to use the RAW firmware zip file. Though this may wipe your phone; I have not tested, so not 100% sure.
Upgraded 2 times didn't wiped but always backup and if you ever want to use the downgrade 10 to 9 firmware it will wipe your data.
Update.
PierceSirens said:
cant manual update too from .64 to latest android 10.someone,please help
Click to expand...
Click to collapse
You have to move up in updates 1 step at a time. I was having the same problem. You have to update each update one at a time you can't skip any.
Lonewolf007ljp said:
You have to move up in updates 1 step at a time. I was having the same problem. You have to update each update one at a time you can't skip any.
Click to expand...
Click to collapse
No dude, that's not entirely correct... If you only download the small incremental updates (about 180-300MB), then yes, you have to update one at a time because they are just small 'addons' if you like to update to the next rom version from the previous version.
However, if you download the full update zip (about 2.2GB) you can directly update from latest A9 1910.64 to latest A10 2004.60.... You can get it from here
https://dlcdnets.asus.com/pub/ASUS/..._I001_1-ASUS-17.0230.2004.60-1.1.162-user.zip
If that still fails for some reason then you'll have to update using the raw rom which can be found here
https://androidfilehost.com/?fid=4349826312261813058
Try the first link, download it, put it in the root of storage and reboot phone. It should automatically detect the update and prompt you to update. Post back here if that fails and I'll walk you through updating using the raw rom on the second link. Saves having to download and update a whole bunch of times like the other guy suggested just to get to the latest version. (no offence to Lonewolf, I appreciate you are simply trying to help, but just thought I'd clear that up ?)
Tried time and time again all from Asus website full zips around 2 gb wouldn't work until I went through them in order just finished. It would not update any other way I swear.
Lonewolf007ljp said:
Tried time and time again all from Asus website full zips around 2 gb wouldn't work until I went through them in order just finished. It would not update any other way I swear.
Click to expand...
Click to collapse
Oh OK dude. Thanks for letting us know and your help . Totally believe you, no need to swear on it! Strange though, I've advised several people to update straight from A9 1910.64 to latest A10 2004.60 using this method and everyone's reported back that all went well.
Were you initially updating from a version earlier than 1910.64?
If so then it would fail. 1910.64 was the last A9 update, you needed to be on that before it updates straight to latest A10 using the full zip.
Ww_zs660kl_16.0631.1910.64
reg66 said:
Oh OK dude. Thanks for letting us know and your help . Totally believe you, no need to swear on it! Strange though, I've advised several people to update straight from A9 1910.64 to latest A10 2004.60 using this method and everyone's reported back that all went well.
Were you initially updating from a version earlier than 1910.64?
If so then it would fail. 1910.64 was the last A9 update, you needed to be on that before it updates straight to latest A10 using the full zip.
Click to expand...
Click to collapse
Was coming from the WW_ZS660KL_16.0631.1910.64 from the convert from cn to ww thread which I believe is the raw. Been trying for a week or so to figure it out always said system update failed until I went through them one at a time.
Lonewolf007ljp said:
Was coming from the WW_ZS660KL_16.0631.1910.64 from the convert from cn to ww thread which I believe is the raw. Been trying for a week or so to figure it out always said system update failed until I went through them one at a time.
Click to expand...
Click to collapse
Oh OK, fair enough. Glad you've got it updated now bud, which ever way works! ?
Ok, so I read through this, and it did not work.
I have the WW version, and matched it. I am currently still on 16.0631.1910.35_0. I placed the zipped 1910.64-1.1.253 upgrade on the internal storage, and nothing. Just assuming I am an idiot, I am going to try unzipping it so the payload.bin is no longer compressed and see if it works then. My bootloader is still unlocked and my tencent phone is not rooted. Please let me know what I am doing wrong.
RichDoe252 said:
Ok, so I read through this, and it did not work.
I have the WW version, and matched it. I am currently still on 16.0631.1910.35_0. I placed the zipped 1910.64-1.1.253 upgrade on the internal storage, and nothing. Just assuming I am an idiot, I am going to try unzipping it so the payload.bin is no longer compressed and see if it works then. My bootloader is still unlocked and my tencent phone is not rooted. Please let me know what I am doing wrong.
Click to expand...
Click to collapse
Did you reboot after placing uncompressed zip to root of internal storage?
After reboot it should detect the update
Edit:
SOLVED!!!!
finally figured out the issue, will share just for information as unlikely to happen with anyone else.
When i installed xiaomi.eu, i cannot remember which partition it was installed at, was it slot A or B. and when i flashed back to official rom, i left it by default.
This has messed up my partitions when i was back to official rom. so whenever i update my system, it would just fail all the time because it is over writing the booted partition.
dont know how, and dont ask me how i fixed it, all i can explain is the following:
checked on fastboot the slot and it was A. so i tried to change it to B and it didnt work with all available commands. So, i used TWRP to boot into fastboot slot B and installed fresh ROM 12.5.4. bootloader unlocked just to be safe. then updated and it went through without any issues.
i cannot explain what exactly happened and if what i did was correct and if my theory is correct, but it worked!!!!.
Thanks to everyone contact me and gave me any idea.
Hi All,
"Couldn't update Miui"
"download rom and try updating again"
i have an issue with my device, it all started after i install eu rom and then flashed back original rom and locked bootloader.
i was on 12.5.2 when i unlocked bootloader the first time, and install eu. version. tried it for a week, and it was really bad. so i switched back to original rom 12.5.4 when it was released and locked bootloader, after that, since then, i was not able to update my device to the following roms. i tried the first time 12.5.6 and it didnt go through when device rebooted. as deviced auto restarted for a few times, (it boot to miui logo for 3 sec's then blink green then restart, happens for a few times like 6-10 times) then device reboots back to version before update but really really really slow.
in the begining, i thought it was faulty update, but i found that several people did it successfully,
Then i thought they have their bootloader unlock and 12.5.6 was a beta version, so that was the reason, until stable 12.5.7 showed up. so i've unlocked bootloader and updated, same issue.
Then i thought, maybe 12.5.4 version downloaded is corrupt somehow, so i've installed 12.5.2 and updated, failed again. same result.
all all cases above, i tried locked and unlocked bootloader and i still get green blinking a few times then a very slow version before update.
Anyone familiar with this case? i really need your help.
Your device original rom is?
hungragezone said:
Your device original rom is?
Click to expand...
Click to collapse
yes, just going with original global rom, my device is global MI version (global global)
5th try now just failed again. i really need help please.
hassanaliyeh said:
5th try now just failed again. i really need help please.
Click to expand...
Click to collapse
I think u should reflash and lock your BL using fastboot method from beginning
hungragezone said:
I think u should reflash and lock your BL using fastboot method from beginning
Click to expand...
Click to collapse
the problem is, i did that a few times now. doesnt work.
seems like there is something blocking in the update after reboot.
the error i am getting after every failure is the following:
"Couldn't update Miui"
"download rom and try updating again"
could it be a reason of installing xiaomi.eu using twrp that the partition has changed and caused this problem? just a thought.
Are you trying to install it via the OTA? Because the problem can be the unlocked bootloader
xNAPx said:
Are you trying to install it via the OTA? Because the problem can be the unlocked bootloader
Click to expand...
Click to collapse
OTA and local upgrade through the 3 dots. any other way?
btw, just tried again with locked bootloader
Well that's weird. I can push the installation with the 3 dots and everything goes well
xNAPx said:
Well that's weird. I can push the installation with the 3 dots and everything goes well
Click to expand...
Click to collapse
How large was your file?
3.2 I think
xNAPx said:
3.2 I think
Click to expand...
Click to collapse
Do you have an idea what would be the issue?
Any help would be great
xNAPx said:
3.2 I think
Click to expand...
Click to collapse
Where can you download 12.5.6 from ?
hassanaliyeh said:
OTA and local upgrade through the 3 dots. any other way?
btw, just tried again with locked bootloader
Click to expand...
Click to collapse
My gf have a unit on global 12.5.4 and it doesn't get ota updates either , very weird
Where did you get the 12.5.6 from?
speedtripler said:
My gf have a unit on global 12.5.4 and it doesn't get ota updates either , very weird
Where did you get the 12.5.6 from?
Click to expand...
Click to collapse
here is your 12.5.6
https://bigota.d.miui.com/V12.5.6.0.RKAMIXM/miui_STARGlobal_V12.5.6.0.RKAMIXM_e0b20eed12_11.0.zip
could you please report if it goes through? also, is the bootloader locked and device not rooted?
Thanks
hassanaliyeh said:
here is your 12.5.6
https://bigota.d.miui.com/V12.5.6.0.RKAMIXM/miui_STARGlobal_V12.5.6.0.RKAMIXM_e0b20eed12_11.0.zip
could you please report if it goes through? also, is the bootloader locked and device not rooted?
Thanks
Click to expand...
Click to collapse
Will try flash in 15 minutes and update
Update file seems ok.....
speedtripler said:
Update file seems ok.....
Click to expand...
Click to collapse
how will it go? after you finish update
Everybody trying to flash/boot and everthing that couild work.
But how many have get the eu-version or global?
Have it work for nobudy?
Or that is am that doesnt get what some happen.
Are that money some waiting på Andriod 13, it should couils change language to every app.
I waiting on that, i dont come longer then unlock boatlooder.
Or are that somebody that have any simple instructures ?
I only understand from your message, that you are asking if there is anyone who is using global/eu ROM, correct? So I do use it.
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
zelma83 said:
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
Click to expand...
Click to collapse
I have OP10P which is global unlocked at all so I didn't need to switch from chinese coloros to global/europe OOS.
Ok, that was nice
I have eu op10pro unlocked and rooted.
I've got a guide on how to root, plus the stock and patched boot images, I'll release them on each new update.
All will be EU
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
zelma83 said:
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
Click to expand...
Click to collapse
You'd need windows..
So if you're on a Mac like I am for work then you could use boot camp and have a dual boot or just get parallels, have an OS within an OS, it's £70 a year but it works extremely well..
mxmda said:
I have eu op10pro unlocked and rooted.
Click to expand...
Click to collapse
I've also
Me too
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
zelma83 said:
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
Click to expand...
Click to collapse
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Ultimatum99 said:
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Click to expand...
Click to collapse
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
dladz said:
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
Click to expand...
Click to collapse
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Ultimatum99 said:
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Click to expand...
Click to collapse
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
dladz said:
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
Click to expand...
Click to collapse
Correct, NE2210_11_A.13 is the Chinese version. I'm attempting to simply install an OxygenOS official ROM but it's not allowing to. I have an OP8 Plus and it worked very easily, simply pick the original ROM, local upgrade (now the option is called "Local install" instead) and then clean cache and good to go. This is not working now for whatever reason. I tried both in A.12 CN to A.12 EU and A.13 CN to A.12 EU.
dladz said:
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
Click to expand...
Click to collapse
It didnt work.
But look here you can se update is availble but not install.
It is in full mode.
I think that i most find something else.