It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse
Related
hi guys.i have nexus 9 with unlock bootloader, rooted mmb29s lte and twrp installed.do i need to flash all mmb29r stock rom or there are another method how to flash update from google.
thanks in advance
Sent from my Nexus 9 using Tapatalk
As no one else replied.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image/
Can be done without wiping data if needed.
Also checkout Chainfire's Flashfire App, if you have systemless root and an unmodified system, which can update by ota.
Can also be used to flash factory images.
Alternatively just flash boot, system and vendor images.
Reboot to recovery, wipe cache and dalvik cache, flash, reboot system = dirty flash.
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
TheMuffnMan said:
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
Click to expand...
Click to collapse
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are you hoping to update by OTA or using it to flash factory images?
corkiejp said:
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are hoping to update by OTA or using it to flash factory images?
Click to expand...
Click to collapse
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
TheMuffnMan said:
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
corkiejp said:
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
Click to expand...
Click to collapse
I say brick, I actually mean like boot loop - where I'd need to do a full erase and rebuild. Not an actual creation of a paperweight.
it hard to flash whole rom for every update.and i once have brick my tab.twrp not recognise internal storage,it state internal storage 0mb.
Sent from my Nexus 9 using Tapatalk
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Then I just did my usual process, extracted each file, flashed each - except recovery which I flashed with TWRP 3.0.0.2 and then rebooted into Recovery where I flashed SuperSU 2.6.6 Beta, wiped Dalvik/cache and then booted tablet.
Retained all my data and it seems to be running fine.
TheMuffnMan said:
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Click to expand...
Click to collapse
Any chance you still have access to the logs? Try posting to the linked thread.
Chainfire said:
In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.
Click to expand...
Click to collapse
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
corkiejp said:
Any chance you still have access to the logs? Try posting to the linked thread.
Click to expand...
Click to collapse
I'm sure I could probably dig them up!
corkiejp said:
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
Click to expand...
Click to collapse
Didn't know about the 2.67! Already had the 2.66 Beta on the device so I just flashed that guy.
Here is the ROM
all links should add"" by yourself
For 2.15:https://dlsvr04.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-5.14.44.1898-user.zip
UL-Z016-WW-5.14.44.1898-user.zip
For 2.40:https://dlsvr04.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016_1-WW-5.14.44.1898-user.zip
UL-Z016_1-WW-5.14.44.1898-user.zip
Both of them are from Chine office website
Install Guide:
1.Download both 6.0 and 7.0 Firmware (for your model)and put them into your SD card
2.flash office recovery
3.Enter recovery and choose "Apply update from SD card" and flash 6.0 first and 7.0 firmware in order
4.Wipe Cache partition (not necessary but advice to do it)
5.Have fun with your android 7.0
there is still no twrp for android 7.0 now,so no root right now but will come soon.(TWRP now is in beta)
2.flash office recovery
where do I find this?
samson1357924 said:
there is still no twrp for android 7.0 now,so no root right now but will come soon.(TWRP now is in beta)
Click to expand...
Click to collapse
I look forward to a twrp for Android 7. I already updated to Android 7 but lost my root and I would like to reinstall/flash magisk through twrp. The lasty twrp versions I tried in Android 6, showed upside down on my phone when I booted twrp, but the touchscreen was at the "regular" spot, so it was very very difficult to navigate. I hope I do not have that problem with the next twrp.
palgo47 said:
2.flash office recovery
where do I find this?
Click to expand...
Click to collapse
Here come the stock recovery from Z016-WW-4.12.40.1698
For 2.15Ghz
https://drive.google.com/file/d/0By3NdBos6w6JQ2ZTWi1pMTdYWE0/view?usp=sharing
For 2.4Ghz
https://drive.google.com/file/d/0By3NdBos6w6JWXZOanJDbmI0akU/view?usp=sharing
this article came from Taiwan Asus office Forum:
https://www.asus.com/zentalk/tw/thread-185884-1-1.html
blahforme said:
I look forward to a twrp for Android 7. I already updated to Android 7 but lost my root and I would like to reinstall/flash magisk through twrp. The lasty twrp versions I tried in Android 6, showed upside down on my phone when I booted twrp, but the touchscreen was at the "regular" spot, so it was very very difficult to navigate. I hope I do not have that problem with the next twrp.
Click to expand...
Click to collapse
Here come the ZS570KL twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Forum link:https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=220546&extra=page=1&page=3&mobile=2
samson1357924 said:
Here come the twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Thank you very much. The twrp still loaded upside down, but I was able to carefully navigate it to install magisk v11.1 again to regain my root and be able to use Android Pay once again. Thank you again!
You think by now that the twrp would be back to normal after all these updates. Is there something missing in there, that making it upside down?
blahforme said:
Thank you very much. The twrp still loaded upside down, but I was able to carefully navigate it to install magisk v11.1 again to regain my root and be able to use Android Pay once again. Thank you again!
Click to expand...
Click to collapse
You are welcome~
So glad to help you^^~
samson1357924 said:
Here come the ZS570KL twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Forum link:https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=220546&extra=page=1&page=3&mobile=2
Click to expand...
Click to collapse
Thanks... doesn't reboot anymore on mine and I can interact with the screen... but it is still upside down. Makes it very difficult.
jnmacd said:
Thanks... doesn't reboot on my and I can interact with the screen... but it is still upside down. Makes it very difficult.
Click to expand...
Click to collapse
Ummm......Maybe you are S821 model?The twrp maker seem doesn't have S821 model,so this recovery mightn't work on 6G/256G
samson1357924 said:
Ummm......Maybe you are S821 model?The twrp maker seem doesn't have S821 model,so this recovery mightn't work on 6G/256G
Click to expand...
Click to collapse
I have the non-pro version.. 2.15Ghz
I am using the sd 820 64GB version and twrp shows upside down for me.
jnmacd said:
I have the non-pro version.. 2.15Ghz
Click to expand...
Click to collapse
Well,I didn't have this problem...
But there is a new version release,maybe you should try!
twrp-3.1.0-0-Z016D-20170317-N.img
In the same link!
There is no need for all these complicated steps. My phone(Z016D) was also rooted. I just downloaded the Nougat ROM, copied it over to the root of the internal drive. As soon as you disconnect the phone from PC, you will get a notification "New System Update detected". Click Update and you're good to go. After installation, I would suggest to do a factory reset.
Sent from my ASUS_Z016D using Tapatalk
rynaus said:
There is no need for all these complicated steps. My phone(Z016D) was also rooted. I just downloaded the Nougat ROM, copied it over to the root of the internal drive. As soon as you disconnect the phone from PC, you will get a notification "New System Update detected". Click Update and you're good to go. After installation, I would suggest to do a factory reset.
Sent from my ASUS_Z016D using Tapatalk
Click to expand...
Click to collapse
It's a good news!You mean that you update to 7.0 with twrp?!!!It is awesome!
However I want to know that how did you root?with superSU?system-less superSU?magisk?or another?And did you change your system?like install Exposed,viper4Android,or delete some system app?I think these actions might make you meat some problem when updating.So I think my method might be almost 100% to update success.
Whatever thanks for your advice,and enjoy your root
I think these actions might make you meat some problem when updating.
Click to expand...
Click to collapse
How exactly can they create problems. There reason you can't have OTA updates is unlocked bootloader. That however, shouldn't really prevent you from flashing rom through recovery via SD card or sideload or just dropping it into internal storage and doing what rynaus did.
_Kuroi_ said:
How exactly can they create problems. There reason you can't have OTA updates is unlocked bootloader. That however, shouldn't really prevent you from flashing rom through recovery via SD card or sideload or just dropping it into internal storage and doing what rynaus did.
Click to expand...
Click to collapse
I think that you can try rynaus first.Because it's more easier.If it isn't work ,try what I say.
How exactly can they create problems. →It may cause update fail, usually just can't update success.(from my experience from my ZF5 and ZF2)
samson1357924 said:
Well,I didn't have this problem...
But there is a new version release,maybe you should try!
twrp-3.1.0-0-Z016D-20170317-N.img
In the same link!
Click to expand...
Click to collapse
I can confirm that the twrp-3.1.0-0-Z016D-20170319-N does not show upside down for me. I hope you all have the same result.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
blahforme said:
I can confirm that the twrp-3.1.0-0-Z016D-20170319-N does not show upside down for me. I hope you all have the same result.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Thanks for your reply^^~
0319-N works right for me too.. no longer upside down. Was able to root with Magisk
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Edit: This works on 2.0 as well!
Unroot: https://www.youtube.com/watch?v=C77cHOjXo_g
Poebat said:
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Click to expand...
Click to collapse
Could use some help--i can get TWRP installed fine, even install Supersu. It just doesn't "take". https://forum.xda-developers.com/zenwatch-2/help/tried-everything-to-root-sparrow-twrp-3-t3614177
jaysonic88 said:
Could use some help--i can get TWRP installed fine, even install Supersu. It just doesn't "take". https://forum.xda-developers.com/zenwatch-2/help/tried-everything-to-root-sparrow-twrp-3-t3614177
Click to expand...
Click to collapse
Resolved it. Had to mount system to get it to stick.
@Poebat
Nice tutorial?
yash92duster said:
@Poebat
Nice tutorial?
Click to expand...
Click to collapse
Thanks!
can I use this guide also for Android Wear 2.0 ?
milanored said:
can I use this guide also for Android Wear 2.0 ?
Click to expand...
Click to collapse
No, I think the SuperSU I used in the video is for AW 1.5. You can try just make a backup before you do it
but the recovery should work with AW2.0 ?!
milanored said:
but the recovery should work with AW2.0 ?!
Click to expand...
Click to collapse
Correct
I confirmed that the recovery still works with AW2.0. The SuperSU and busybox zip fails to flash. I flashed the latest stable SuperSU zip and it flashes completely, but the SuperSU app does not open and the watch hangs up when asking for root. I flashed the latest Stericson busybox zip, but obviously I can't test if it installed without su.
Poebat said:
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Click to expand...
Click to collapse
Everytime I try to install I keep getting an error and this is after flashing to stock, reinstalling twrp and trying again.
Keep in mind I'm trying to root 1.5 not 2.0
GTDarthYoda said:
Everytime I try to install I keep getting an error and this is after flashing to stock, reinstalling twrp and trying again.
Keep in mind I'm trying to root 1.5 not 2.0
Click to expand...
Click to collapse
What are you trying to install?
Poebat said:
What are you trying to install?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
GTDarthYoda said:
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
Click to expand...
Click to collapse
That's really odd. Are you running a stock ROM? How much free space do you have? Can you flash busybox?
Stock, wiped, stock, still nothing.
Edit:
Busy box installed
Edit:
Tried SuperSU again. no luck
I have the same problem with AW2.0. Root works after flashing the latest SuperSU but the SuperSU app itself won't open.
Gfhoihoi72 said:
I have the same problem with AW2.0. Root works after flashing the latest SuperSU but the SuperSU app itself won't open.
Click to expand...
Click to collapse
Zip from this post did the trick.
https://forum.xda-developers.com/showpost.php?p=73165371&postcount=66
It appears the issue stems from the filesystem being squashfs. I've dealt with squashfs in the past, and it doesn't allow modification due to it's structure. The system needs to be un-squashed, modified, then re-squashed. There is a ROM for the LG watch where the developer converted it to ext4, but that requires editing partitions on the watch. I'm considering converting this to ext4, but I'm not thrilled with the idea of a hard brick.
Hmmmm very very strange, after some reboots the twrp recovery is gone.
The watch boots in the stock recovery.
Is it because this is an 1.5 version?
Hey guys.
The below is my full experience of how I flashed TWRP, the Xiaomi.eu rom and rooted with Magisk. Whilst it essentially is a step-by-step, it also contains not only how I succeeded but also how I encountered issues and so...
*UPDATE!*
Here is a slightly condensed verison with thanks to @airwebber
Get the latest xiaomi.eu rom from here or here, just scroll down and find the "xiaomi.eu_multi_MI9..." version.
https://sourceforge.net/p/xiaomi-eu...ty/?page=0&limit=100#5cb9f96ee8ba7c44716e87ff
Get the latest magisk (magisk v19 works at the time of writing this post):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Some versions of twrp may not work on older builds other than the latest (9.4.25) and so use this one with:
https://mega.nz/#!CH5jgYTB!yNqOiVoo3cf0_15jIwZ-btO52cvpOG7iZrRCe19V2Nc
Once the waiting time elapses (usually 360 hours) use the MiFlash tool to unlock the bootloader. Warning: this wipes your phone entirely, so be sure to backup anything of importance.
Unlocking takes a few minutes and once 100% complete your Mi 9 will reboot. Your phone will say “unlocked” on the first splash screen while booting up.
Your Mi 9 will boot, and you will need to either perform/skip the initial setup stuff. Once ready, power off your device in order to flash TWRP.
Press both the volume down key and power key to boot into Fastboot Mode.
Once in Fastboot Mode, use the following command to install TWRP: “fastboot flash recovery XXXX” (XXXX = the pathway to your TWRP.img file). However, I find it best using Minimal ADB and copying the TWRP file and renaming it to “twrp.img” for ease) in the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”.
Once flashed, disconnect the USB cable and boot to TWRP recovery by holding down both the volume up and the power buttons. This sometimes will bring you to the stock recovery and NOT TWRP! If it does, boot back to Fastboot and reflash TWRP.
Once you can boot to TWRP, push both the rom and magisk via CMD line:
adb push rom.zip /tmp/
adb push magisk.zip /tmp/
For ease, I suggest copying both files to the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”. And renaming them to: “rom.zip” and “magisk.zip”.
This step is very important!! You must go to the Wipe menu and select: Format Data, then type “yes” to continue and then: do a Factory reset, which also wipes: Data, Caches and Format Data. If you skip this step you won’t be able to install a lot of important apps and will have to start over.
Now that you have pushed both the rom & magisk and wiped everything you needed to. Install the ROM immediately after install magisk.zip (in that order) both located in /tmp/.
The installation will take a couple of minutes (if your screen dims, don’t worry that’s just TWRP screen dimming, touch the screen to keep it awake!) once finished with no errors, then reboot and chose Do Not Install the TWRP app when prompted.
The phone will take a few seconds to reboot and show the first MI splash screen, but it should start booting. After a couple of minutes, you should see the initial boot screen! Perform the setup (connecting to Wi-Fi, adding my Google account etc.).
Once finished setting up, you may notice that magisk was not installed, if that happens, you can install the APK version and follow the prompts and reboot.
Once rebooted, confirm that magisk is now installed. If it is, I suggest installing SafetyNet and confirming your phone passes!
If it passes, you have successfully installed and rooted the Xiaomi.eu rom!
Also, when updating with each weekly I recommend the below as an alternative to using the built in Updater app. The reason being is I believe the updater app automatically reboots after it installs, which if you're rooted means you'll lose it. That then means you have to reboot back to twrp, reflash magisk, reboot, reinstall modules, reboot again etc.
Therefore to update a weekly:
Download the rom manually
Reboot to twrp
Wipe system and caches
Flash the rom and magisk
Reboot
Optional: I also disable my substratum theme too before updating and reapply afterwards. Whether it's needed or not I'm not too sure, so give it a try either way
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
The Dutchman said:
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
Click to expand...
Click to collapse
Thanks, first post updated!
cd993 said:
Thanks, first post updated!
Click to expand...
Click to collapse
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
*justintime* said:
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
Click to expand...
Click to collapse
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
cd993 said:
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
Click to expand...
Click to collapse
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
*justintime* said:
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Click to expand...
Click to collapse
Thanks, updated!
Rommco05 said:
Good stuff for early roots without not tested stuff like twrp and magisk but I would hide that middle part coz some people can get be confused. Or make a short version which working in order and another with your all step's but separately
edit: still 46h left
Click to expand...
Click to collapse
Yeah I agree it's kinda overkill, being a a full run down - when I get time I'll make a shorter condensed version
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it all logical and fine, thanks! Except one thing that I'm not sure... Is xiaomi.eu a 'full rom' (on all Xiaomi that I had I always jumped straight to something different than MIUI and so I never tried it ahahah )?
If so, I think it would be better to wipe the system too before installing the rom. That's because doing so it will do 100% 'clean' installation and not a an update on the normal global miui
perryano said:
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
Click to expand...
Click to collapse
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
mr-mauro said:
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it is more or less everything fine except one thing that I'm not sure. is xiaomi.eu a full rom? If so, I think it would be better to wipe the system too before installing the rom because instead it will try to to an update on the normal global miui rather than a 100% 'clean' installarion
Click to expand...
Click to collapse
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
cd993 said:
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
Click to expand...
Click to collapse
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
mr-mauro said:
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
Click to expand...
Click to collapse
Let us know
cd993 said:
Let us know
Click to expand...
Click to collapse
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
Click to expand...
Click to collapse
Great!
Ahh I did see 1 random app. But then I debloated a went away
cd993 said:
Great!
Ahh I did see 1 random app. But then I debloated a went away
Click to expand...
Click to collapse
Luckily in those two waiting-weeks I had time to test all the debloat that I wanted to come with a stable configuration today It's just a pity that we can't get rid completely of the Security app It is integrated too much in the system!
One quick question for who has installed Xiaomi EU with Magisk: does it pass SafetyNet to you? (to me no )
cd993 said:
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
Click to expand...
Click to collapse
So once bootloader is unlocked I can install TWRP and flash the EU rom without rooting?
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
Click to expand...
Click to collapse
Yeah, to change the device name back to mi 9, just install "Find my device" app from Google play store, sign in with google account, there's an option in the setting to rename the device (this device).
That's the only place you can change the name back, I did try all, but only this one worked.
Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post