Related
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.
Same thing here, always installation failed
Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables
Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???
@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
veroby said:
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
Click to expand...
Click to collapse
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
k.s.deviate said:
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
Click to expand...
Click to collapse
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
veroby said:
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
Click to expand...
Click to collapse
I did do this last night as I was greeted with the same Verity error after flashing the beta.
k.s.deviate said:
I did do this last night as I was greeted with the same Verity error after flashing the beta.
Click to expand...
Click to collapse
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Seems a little weird as the fastboot oem disable_dm_verity commands have only just come onto xda this morning. Seems weird because its working for most which would assume most are on 4.0.2 firmware. Meaning they havent update for a long time.
Updated - I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither. Thankyou..:good:
veroby said:
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Click to expand...
Click to collapse
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
k.s.deviate said:
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
Click to expand...
Click to collapse
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
veroby said:
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
Click to expand...
Click to collapse
Glad my explanation helped.
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
xtacb4 said:
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
Click to expand...
Click to collapse
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
veroby said:
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
Click to expand...
Click to collapse
Hi, last message mine in this thread talking about this here, don't want to be offtopic, I purchased it yesterday, came home installed the usual (twrp[i love how fast the backups are made], CM14.1) and delivered the Nexus 6 to a friend (he bought it from me).
Thanks!
Hi all, I see there is an update listed on this page link V12.0.2.0.QFAEUXM.
Can someone confirm if this has been released as stable already? And if you received it, how is this an improvement over V12.0.1? I am holding on to V11 as I heard V12s initial release was not that well polished and strains the battery.
Thanks!
it's only security update for August
Sent from my MI 9 using Tapatalk
LubbeSGS said:
Hi all, I see there is an update listed on this page link V12.0.2.0.QFAEUXM.
Can someone confirm if this has been released as stable already? And if you received it, how is this an improvement over V12.0.1? I am holding on to V11 as I heard V12s initial release was not that well polished and strains the battery.
Thanks!
Click to expand...
Click to collapse
- I have received this OTA update and it's stable.
- Everything work's more or less stable, at least I didn't find any issue until now.
- What I have noticed is that Weather app is replaced with G version in his name and now one can update this app manually without previous notorious "authorisation" issue.
- Mi Global Browser is still there and still can't be uninstalled ( Failed [-1000] error in adb shell during uninstall).
- In Indian Forbes site I have seen that they will release update which will allow uninstalling MiBrowser and few other apps because Indian government have banned all of these apps.
- Battery life is a little better from previous ROM.
- There is no more stuttering in Chrome browser.
- That's my humble experience so far.
Thanks @Jehonan I think I may give it a shot then.
Cannot flash the update
I am on miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM.
I did not get the OTA yet and my battery life is very poor so I am eager to upgrade, I tried to update manually from the updater to either files:
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM
but I always get the "Sorry, flash to this stable version is not allowed".
Any ideas what is the problem?
meroupow said:
I am on miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM.
I did not get the OTA yet and my battery life is very poor so I am eager to upgrade, I tried to update manually from the updater to either files:
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM
but I always get the "Sorry, flash to this stable version is not allowed".
Any ideas what is the problem?
Click to expand...
Click to collapse
Which update procedure did You follow?
Did You make folder on root of the internal drive, copied appropriate downloaded ROM inside this folder and start upgrade from there?
I went to the Rom version in settings. Cliqued on the 3 dots. Select rom to install. Then tried to import the files from download, root, dowloaded_roms folders. Same result: "flash to this stable version is not allowed".
With the same procedure I am able te reflash miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM as much as I want. But no way to upgrade.
I also tried from recovery. But there is no option to flash update.zip.
meroupow said:
I went to the Rom version in settings. Cliqued on the 3 dots. Select rom to install. Then tried to import the files from download, root, dowloaded_roms folders. Same result: "flash to this stable version is not allowed".
With the same procedure I am able te reflash miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM as much as I want. But no way to upgrade.
I also tried from recovery. But there is no option to flash update.zip.
Click to expand...
Click to collapse
Did You tried with OTA version of this update?
Same procedure, in root of the drive in downloaded_rom folder copy OTA update and start update from there.
Here is a link to ROM's.
P.S.
I believe that You must first go with OTA version of the firmware because of the downloaded ROM decrypting procedure. After that You can go with recovery type of ROM (full ROM upgrade).
Yes, I tried the update file as well.
Both files give the same error ("Sorry, flash to this stable version is not allowed"):
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM_44dcb66933_10.0.zip
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM-789914bb83-10.0.zip
I am able to flash V12.0.1 from the same site so I am sure to be on the right ROM:
- miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM_4d28c84f58_10.0
Something else is preventing the upgrade.
Well, I found out that I needed to change the region settings from France to Belgium... now it updates.
How stupid!
Hi all, I'm having a strange behaviour after the update: the quick charge ( using a wireless charger ) isn't working anymore.
Does anyone have the same issue?
stocaprimo said:
Hi all, I'm having a strange behaviour after the update: the quick charge ( using a wireless charger ) isn't working anymore.
Does anyone have the same issue?
Click to expand...
Click to collapse
Nope!
Mine is working as it should, without any issue what so ever.
Strange!
Did You check wireless charger itself?!
---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------
meroupow said:
Well, I found out that I needed to change the region settings from France to Belgium... now it updates.
How stupid!
Click to expand...
Click to collapse
Excellent!
I'm glad it worked for You!
Good luck in the future!
P.S.
There is nothing stupid about this so don't blame yourself!
I would rather call this Xiaomi's stupidity and theirs mumbo jumbo with all of these "special" update procedures !
What is yhe exact solution to this problem
I already tried to change my region it didn't work for me im using redmi note 8 pro Indonesia rom
I've been trying to root my redmi9 for a couple of days now, with no luck. Downloaded the relevant firmware for my version to my pc, extracted it and copied the boot img over to my phone and copied over magisk manager APK too. On my phone I opened and installed magisk manager and proceeded to the install process then selected patch file and clicked install. Unfortunately each time that I do this I get the same outcome the message reads-
-Device platform: arm64-v8a
-Copying images to cache
! Process error
! Installation failed
I've uninstalled magisk and reinstalled, with the same outcome. Then I've downloaded my phone's firmware directly to my phone and tried to patch the boot IMG like that, but exactly the same outcome. Re-checked that I have the correct firmware for my version and it is, so I can't really understand what is going wrong and why I can't select a patch to send back to pc? Points of note, I haven't got my sim inserted and wondered if this could be a problem as I can't select the other two debugging settings on my phone without my sim inserted ( install via USB and usb debugging (security settings) options) but USB debugging is selected to on. My miui version is Miui global 11.0.7 stable 11.0.7.0(QJCEUXM)
If any body has an already patched IMG file that I can use, or can help me achieve this myself it would be very much appreciated.
Philtyj said:
I've been trying to root my redmi9 for a couple of days now, with no luck. Downloaded the relevant firmware for my version to my pc, extracted it and copied the boot img over to my phone and copied over magisk manager APK too. On my phone I opened and installed magisk manager and proceeded to the install process then selected patch file and clicked install. Unfortunately each time that I do this I get the same outcome the message reads-
-Device platform: arm64-v8a
-Copying images to cache
! Process error
! Installation failed
I've uninstalled magisk and reinstalled, with the same outcome. Then I've downloaded my phone's firmware directly to my phone and tried to patch the boot IMG like that, but exactly the same outcome. Re-checked that I have the correct firmware for my version and it is, so I can't really understand what is going wrong and why I can't select a patch to send back to pc? Points of note, I haven't got my sim inserted and wondered if this could be a problem as I can't select the other two debugging settings on my phone without my sim inserted ( install via USB and usb debugging (security settings) options) but USB debugging is selected to on. My miui version is Miui global 11.0.7 stable 11.0.7.0(QJCEUXM)
If any body has an already patched IMG file that I can use, or can help me achieve this myself it would be very much appreciated.
Click to expand...
Click to collapse
New version of magisk has this error.if you have another phone then you use it to patch your boot.img..it will work...I am also doing this...for a unknown error magisk manager cannot patch boot.img in redmi 9....then I try to patch my boot.img on another phone and it can patch....follow the link.....
https://forum.xda-developers.com/showpost.php?p=83419803&postcount=1
Hi, thanks for the reply. I'm not fully understanding what you're saying. How do I do this using another phone? Do I download magisk onto my other phone, then copy the boot IMG to the phone and patch the image? Then send the patch back to my pc to then flash the patch onto my redmi 9 via fastboot?
In your link, are these steps to follow to flash my redmi9 after creating the patch on my other phone?
Sorry for all of the questions, I'm new to this, it's my first attempt to root a phone and it seems that I've picked the hardest one to unlock and root!!
Philtyj said:
Hi, thanks for the reply. I'm not fully understanding what you're saying. How do I do this using another phone? Do I download magisk onto my other phone, then copy the boot IMG to the phone and patch the image? Then send the patch back to my pc to then flash the patch onto my redmi 9 via fastboot?
In your link, are these steps to follow to flash my redmi9 after creating the patch on my other phone?
Sorry for all of the questions, I'm new to this, it's my first attempt to root a phone and it seems that I've picked the hardest one to unlock and root!!
Click to expand...
Click to collapse
Yes...you can use any device to patch your boot.img file...there is no problem to do so....you can patch any boot.img in any device.....this new version of magisk manager has some issue with our redmi 9 ..so use another device and patch it..then flash patched boot.img via fastboot and follow the tutorial which I give you....
Shas45558 said:
Yes...you can use any device to patch your boot.img file...there is no problem to do so....you can patch any boot.img in any device.....this new version of magisk manager has some issue with our redmi 9 ..so use another device and patch it..then flash patched boot.img via fastboot and follow the tutorial which I give you....
Click to expand...
Click to collapse
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.
Philtyj said:
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.
Click to expand...
Click to collapse
You do not need to install any custom ROM your stock ROM is ok. But you can try the gsi ROM...
Follow the link you can install GSI without any problem...
https://forum.xda-developers.com/showpost.php?p=83533901&postcount=1
EEA version have call recorder or not? i try global version not have call recorder
adiyanto said:
EEA version have call recorder or not? i try global version not have call recorder
Click to expand...
Click to collapse
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim
aasiaasi said:
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
maybe u can try Indonesia version. this version have call recorder. but i need for recorder my whatsapp phone.... ill try Any Call Recorder
aasiaasi said:
Hi Adiyanto,
Hope You're Doing Great..
Yes, You Are Right,
I Have Global Version It Doesn't Have Call Recorder And I Have Also Tried And Flashed EEA Version ROM And It Also Doesn't Have Call Recorder. So I Flashed The Redmi 9 Prime ROM Since It Has Call Recorder And Working Perfectly.
Note That, You Need To Unlock The Bootloader For This Activity. Or You Can Unlock Your Device Bootloader Then Root The Device Then Install Any Call Recorder In Any ROM That Works Perfectly.
Hope This Will Help You ...
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
Hi Qasim,
Would you please share the complete process of rooting and new img file restoration as I am new to this redmi9 am using this device in pakistan. Looking forward for your kind response
Regards nauman
Philtyj said:
Hi there, thanks for the help, I've finally rooted my redmi9! One more thing that I wanted to ask. It's about the ROM. I've tried to find information on Google, but nothing comes up that replies to my question. After rooting with magisk, do I need to install a ROM or is my original Xiaomi ROM still ok and working? I'm not interested in installing a custom ROM, root was simply to gain access for installing a program/app. So I'm hoping my original rom is in tact and I'm good to go.
Click to expand...
Click to collapse
Can you share your magisk_patched.img ? Cause I tried to patch the image on another device, but the created image boot-loops only
Tried patching the image on the redmi directly, but the resulting patched image is only 10MB and obviously boot-loops.
Thanks.
naumanakram said:
Hi Qasim,
Would you please share the complete process of rooting and new img file restoration as I am new to this redmi9 am using this device in pakistan. Looking forward for your kind response
Regards nauman
Click to expand...
Click to collapse
Dear Nauman,
Greetings !!!
For Rooting Your Device Please Refer To This LINK. Or If You Just Want Call Recording Feature Then Flash Redmi 9 Prime ROM To Your Mobile.
Thanks,
MUHAMMAD Asif Qasim
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