February security patch installation field - Xiaomi Mi A2 / 6X Questions & Answers

hey guys i have bootloader unlocked and unrooted my phone today havent updated January security patch still using December patch but i cant install February security patch it says "Installation problem"
also i have enabled CameraApi2
anyone can help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Relock yout bootloader and try to update.
I was in the same situation, I solved it by relocking the bootloader.

but if i lock bootloader again then i will loose all data on the phone. also when i unlocked bootloader everone said ota keeps updating even if bootloader stays unlocked

ota updates will only work if all the partitions on the device are untouched !
magisk can to restore your original boot.img but if you modified "for example the system partition" in any way such as manually editing "build.prop" ota will refuse to install.
Is very important the way you followed to root on your device,and what you did after that....
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
sry for english

Maharram said:
anyone can help me?
Click to expand...
Click to collapse
Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones.

I will loose all data when I flash stock rom?

daitalos said:
ota updates will only work if all the partitions on the device are untouched !
magisk can to restore your original boot.img but if you modified "for example the system partition" in any way such as manually editing "build.prop" ota will refuse to install.
Is very important the way you followed to root on your device,and what you did after that....
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
sry for english
Click to expand...
Click to collapse
I have enabled CameraApi2 haven't changed anything on system if ı found original build.prop and change it with my edited one I will get ota updates right? after the update i can enable CameraApi2 again

Maharram said:
I have enabled CameraApi2 haven't changed anything on system if ı found original build.prop and change it with my edited one I will get ota updates right? after the update i can enable CameraApi2 again
Click to expand...
Click to collapse
If you have already backup with default settings of buildprop and restore it & If you did root via magisk with correct way , maybe yes you can.But ! the better solution is the way from post above (flash stock rom etc)
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913

Maharram said:
I will loose all data when I flash stock rom?
Click to expand...
Click to collapse
No, u won't loose data if u use "flash_all_except_data.bat" command file (is inside archive with fastboot image). If u use "flash_all.bat", then u'll erase /data partition.

Aerobatic said:
No, u won't loose data if u use "flash_all_except_data.bat" command file (is inside archive with fastboot image). If u use "flash_all.bat", then u'll erase /data partition.
Click to expand...
Click to collapse
thanks a lot

Maharram said:
thanks a lot
Click to expand...
Click to collapse
Hi..I am facing the same issue. I am on Jan security patch..unrooted..unlocked bootloader and Camera 2api enabled...I get the same error while updating to Feb security patch...did the above method resolve your issue? If yes, can you please provide a stepwise rundown of how you did it?
Your help is much appreciated!

S Advance User said:
Hi..I am facing the same issue. I am on Jan security patch..unrooted..unlocked bootloader and Camera 2api enabled...I get the same error while updating to Feb security patch...did the above method resolve your issue? If yes, can you please provide a stepwise rundown of how you did it?
Your help is much appreciated!
Click to expand...
Click to collapse
hi. I haven't resloved that issue im waiting for major update ı dont want to root remove CameraApi2 and unroot update and root enable CameraApi2. if you want just root your phone remove CameraApi2 and unroot the u can update you phone also u can use other method

Maharram said:
hi. I haven't resloved that issue im waiting for major update ı dont want to root remove CameraApi2 and unroot update and root enable CameraApi2. if you want just root your phone remove CameraApi2 and unroot the u can update you phone also u can use other method
Click to expand...
Click to collapse
Other method? Which one is that?

S Advance User said:
Other method? Which one is that?
Click to expand...
Click to collapse
"Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones."
thanks @Aerobatic for this solution

My device downloaded and placed automatically the february path, however, it didn't installed it - it shows "restart now". I'm really scared about Xiaomi's updates and don't want to install this one based on users reports, however, I rebooted the device (power button - reboot) sometimes and the update didn't installed (thanks God).
I need to know if it will eventually install automatically, or, if I wait enough to the next update, the current update will be overwritten by the new one.
Does anyone know about this?

Maharram said:
"Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones."
thanks @Aerobatic for this solution
Click to expand...
Click to collapse
I am going to carry out this method tonight...If I do this method...will I loose camera 2api?

S Advance User said:
I am going to carry out this method tonight...If I do this method...will I loose camera 2api?
Click to expand...
Click to collapse
yeah becouse this method will reset your system. Your data files will stay (ex: photos, music, app datas etc.)

Related

[Q] [XT1064]Wifi not working after reflashing stock

Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Bl00dyMurd3r said:
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
Click to expand...
Click to collapse
Did you download your XT1064 firmware from here:
http://sbf.droid-developers.org/phone.php?device=36
We are not supposed to install XT1069 firmware on XT1064
rafaelbrunner said:
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Click to expand...
Click to collapse
me too xt1068
Thanks for the link, but i did not flash XT1069 firmware, I followed the guide steps to flash "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US" as I have the US gsm model
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
MiguelPT said:
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
Click to expand...
Click to collapse
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Bl00dyMurd3r said:
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Click to expand...
Click to collapse
According to Q18 from this page you need to select full unroot option from the Super Su:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
pleomaxell said:
According to Q18 from this page you need to select full unroot option from the Super Su:
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
Click to expand...
Click to collapse
Thanks, I'll give it a shot!
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Bl00dyMurd3r said:
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Click to expand...
Click to collapse
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
pleomaxell said:
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
Click to expand...
Click to collapse
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Bl00dyMurd3r said:
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Click to expand...
Click to collapse
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
rafaelbrunner said:
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
Click to expand...
Click to collapse
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Bl00dyMurd3r said:
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Click to expand...
Click to collapse
me the saame....i think there isnt solution.....:crying:
WIFI fix
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
IT WORKS!!! Tested here on XT1069!
Thank you once is not enough... Thanks a MILLION, brother! :good:
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
Oh my god thank you so much!! My phone is back to life!! :laugh:
I am glad that all of you found a solution to this problem.
in case anyone lands here from google...
I successfully upgraded to 5.02 and WiFi was working initially.
but then i had to change the custom recovery and superSU, and changed the logo.bin, now the WiFi is no longer working.
--- EDIT ---
after careful examination, found out it was caused by xt1064_lollipop_boot.img
in the end I flashed back to the stock boot.img from 5.02
and then flashed twrp-2.8.6.0-titan.img
now everything is great!

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Won't this wipe everything?
jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.
coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
So 6.23.651. 10 is not patched for "stagefright"?
Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk
links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on
santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.
santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!
yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"
Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.
BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.
gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.
Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse
ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro
Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page
there is already something new on this topic?
not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse
some good news
good news
Rooted on 9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls
mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent
mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)
Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse
notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?
notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.
notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.
parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission
Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.

Categories

Resources