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
Related
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Mob_Dev said:
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Click to expand...
Click to collapse
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
OTAs will never work on a system which is modified in some way, because they contain only bytes which were changed between two Android versions. If files on the device are changed (custom ROM, different kernel, MultiROM-injected init, sometimes even root), OTA simply can't be applied. Everyone who roots his device should be aware of that.
Wait for the flashable ZIPs,
Click to expand...
Click to collapse
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
Aha, i see. So maybe because i've rooted my nexus 7, and i've also got a different kernel for MultiRom( I've installed ubunto touch on my device). ... Those the reasons that leads the installation to be failed?
Anyway, my system auto downloaded the update, it name was "nakasi".
I tried to go to Recover mode, and tried to flash the nakasi ZIP file and flash it,,, but the operation was failed!
What should i do?
How i get auto update installation for kitkat on my nexus 7?
Another question, if i downloaded the Factory image from the link you gave me: https://developers.google.com/android/nexus/images#nakasi and flash it in Recovery Mode... Let say it will success? then i''ll lose auto system update on my nexus in future - because it will be installed manually.
=========
Please Copy the questions in your reply, and post the reply below each one.
Thanks
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
khaytsus said:
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
Click to expand...
Click to collapse
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Another 4.4 Upgrade failure
I am having problems with the OTA upgrade too. However I am running a unmodified/rooted version of 4.3. I have also tried sideloading the factory zip and doing OTA and sideload from a factory reset.
I get the dead android and red triangle error and if I go to the restore menu then this is the error report I get each time
{
"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"
}
/system/apps/hangouts.apk produces some type of verfication error.
I can then reboot and I am back to 4.3
Any thoughts on solutions are gratefully recieved
Mob_Dev said:
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Click to expand...
Click to collapse
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
dbgeek said:
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
yusopa said:
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
Click to expand...
Click to collapse
I am following this guide to install Android kitkat on my nexus 2012 (Wifi only): http://www.droidviews.com/install-kitkat-factory-image-on-nexus/
But if you can see the last step satisfy that i need to flash the 4.4 Factory Image, type, using the following command:
fastboot -w update image-nakasi-krt16s.zip
Click to expand...
Click to collapse
The problem is that, the nakasi file i downloaded from here: https://developers.google.com/android/nexus/images
is not a ZIP file!. It's (.tar) file. And i can't process that command!!
Let me know what is the problem.
Thanks in advance
topet2k12001 said:
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
Click to expand...
Click to collapse
My bad. I read the "different kernel..." as an example of mods that might be made, that could cause failure, not a specific listing of mods that would cause a failure (implying that if the mod's not on the list then it wouldn't be a problem).
So i have the same problem, but aditionally my Windows 8 is unable to recognize my Nexus 7 while in recovery mode and i can't mount the sdcard to install a new rom. Only recognizes it as "grouper". Any advice?
I think Wug Fresh for nexus toolkit can help you guy to bring back your nexus to life. I use from the start.
Sent from my Nexus 7 using XDA Premium 4 mobile app
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!
I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Please try this patch
https://review.lineageos.org/#/c/152083/
josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"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 MI 5 using Tapatalk
p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.
I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk
AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.
Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:
Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk
I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.
What this thread is for:
Booting into TWRP Recovery for the Moto Z2 Play Retus Variant
Rooting the Z2 Play Retus Variant with Magisk
Things you will need:
IMPORTANT: You WILL need a USB C OTG cable and USB Thumbdrive (or a USB C Thumbdrive)
Magisk Zip 13.3 Mod uploaded by Junior Passos: https://www.androidfilehost.com/?fid=889764386195922735
Magisk Manager v5.1.1 apk: https://github.com/topjohnwu/MagiskManager/releases/download/v5.1.1/MagiskManager-v5.1.1.apk
DM Verity and Forced Encryption Disabler v5.1: https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
My modified TWRP: https://www.androidfilehost.com/?fid=673368273298983327 md5: ebcecfaf2e00725561555dd398f883dc
Magisk ZIP and DM Verity ZIP must be put on a thumbdrive. Installing from (external) SD Card will not work with this version of TWRP.
Things you will need to keep in mind:
Make sure you fully update your device before unlocking and rooting as it likely will break OTAs. You'll likely have to rely on stock images posted by users to this forum from now on.
In order to be able to do what you need to do in TWRP, you will need to format data due to forced encryption. You won't be able to root and boot your device otherwise.
My version of TWRP is a hacky build. It works, but one feature in particular does not work: External SD card mounting. Until an updated build is made to fix this issue (of which I will require the assistance of people MUCH better at this than I am), you will need to use a USB C OTG cable and a thumbdrive to be able to back up your device and to flash ZIPs.
Try booting (not flashing) the TWRP build here first: https://forum.xda-developers.com/z2-play/development/twrp-3-1-1-0-moto-g5-plus-albus-t3622593 - If it doesn't work (hangs on logo), then try mine.
DO NOT install SuperSU from within TWRP.
These instructions assume you know how to use ADB and Fastboot Android tools. If you need the utilities, you can download the Windows versions from here: https://forum.xda-developers.com/showthread.php?t=2317790
How to boot into TWRP, make backups and root your device:
0) Your device must already be bootloader unlocked.
0a) DO NOT install SuperSU from within TWRP!!
1) Boot into Fastboot (powered off, hold down Power and Vol Down)
2) Plug your USB C cable into your computer and phone, make sure you have the Android tools installed.
3) Use fastboot command to boot into TWRP (NOT flash): fastboot boot albus_twrp.img
3a) I do not recommend flashing this version of recovery to the device because, as I said before, it's a hacky build. I don't want people to rely on it as their permanent recovery in case issues are found and fixed later.
4) Swipe to allow modification, click Cancel when it asks for passphrase to read encrypted partition.
5) Press Wipe on main screen, slide to wipe. This will wipe Data, Cache and Dalvik partitions. You will need to do this because the partitions will have to remain unencrypted after you flash DMVerity and Encryption Disabler.
5a) Yes, you have to wipe. DM Verity and forced encryption will cause your device to fail to boot if you don't disable them.
6) Back up your device. Attempting to back up System Image may fail because the partition is over 4GB and nearly every thumbdrive will be formatted in Fat32. Back up System, Boot and Recovery.
7) Install DM-Verity ZIP.
8) Install Magisk ZIP linked in this thread.
9) Reboot into system. Anticipate a longer first boot.
10) Sideload Magisk Manager.
Magisk running on Z2 Play:
{
"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"
}
What I did:
Extracted kernel, img_info and dt.img from the retus albus system image and dumped it into a harpia twrp build. I suspect the other version of TWRP was built against a different AOSP version, triggering a SELinux boot block. In my version of TWRP, fstab paths are correct but for some reason MicroSD won't mount. I'll leave that to the professionals. Everything else that I did (as described above) worked and was my exact method for doing so.
Finally:
Special thanks to Dees_Troy for TWRP. Without you, devices would suck.
Here's the Moto Z2 Play Albus boot.img for anyone who wants to take on the task of doing an official TWRP build for the device. https://www.androidfilehost.com/?fid=889764386195927416
You're the man. I'll give this a shot today and report back.
Great tutorial! One question: Does your device pass the "SafetyNet check"?
romhippo.com said:
Great tutorial! One question: Does your device pass the "SafetyNet check"?
Click to expand...
Click to collapse
In my case... it does not fully pass. Passes Safetynet Request and Response Signature... but fails on the Basic Integrity and CTS Profile Match tests. I also did modify /system (ad away, removed bootanimation.zip, moved Magisk apk and Substratum apk into /system) so that could be why.
https://i.imgur.com/u9OVkUq.png
Followed the directions to the letter and everything is working for me. Thanks a lot, twelfth!
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Just a heads up guys. Flashed Magisk 14.0. Passed safetynet. Can't download/install modules though, gives Parse Error or something. Haven't tried installing modules through TWRP to see if it works.
atheart said:
Can't download/install modules though, gives Parse Error or something.
Click to expand...
Click to collapse
I have had the same issue with Magisk 13.3 ...
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
cantsingh said:
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Click to expand...
Click to collapse
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
cmjester6421 said:
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
Click to expand...
Click to collapse
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
twelfth said:
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
Click to expand...
Click to collapse
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Cameras not working post root
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Can you make this alittle more simple like in steps, I recently got this phone and I want to root it
cantsingh said:
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Click to expand...
Click to collapse
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
ihatevz said:
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
Click to expand...
Click to collapse
Haha, we've all been there! :good:
Alabamajackhammer said:
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Click to expand...
Click to collapse
What's wrong with the camera, after root?
Are there no images to restore out yet?
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Pooper22 said:
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Click to expand...
Click to collapse
Yes. I'm surprised that this surprises you.
Is there a specific reason why op says not to flash SuperSU? Will it not work or damage something?
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.