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.
Related
Quick fast post. Fix it up later.
Unofficial TWRP for the SM-G360T1
Step 1:
You should know how to flash twrp by now.
Step 2:
Profit
Download link:
https://www.androidfilehost.com/?fid=24052804347820600
Known issues:
Usb otg not working. Will fix later.
Enjoy. Hit thanks or donate and all that good crap [emoji14]
Mine
THANK YOU ONCE AGAIN @ShinySide!!! Not only for root, but now for a working custom recovery. Truly the 2 most important tools we could have for our phone.
FOR EVERYONE ELSE:
As usual, be sure to give @ShinySide your Thanks/Donations/etc.!!! He deserves it! Also, now that you have TWRP you might be wondering what to do next. Here are a couple of suggestions of things that I've already done and that I am quite happy with.
1) Theme it! - Here are some themes you can try out that will not only make TWRP more beautiful, but also provide a layout that is more intuitive and user friendly. These are listed in a Galaxy S2 thread yes, but I've attached a picture of the one that I'm currently running and I'm happy to say that it works on our phone like a charm. I've also used these themes on other phones in the past. Just follow the instructions in the OP of that thread and give the guy some thanks on that thread if you like them. There is no risk in this btw. Either it works or it doesn't and to get rid of it if you don't like it you just have to delete the theme folder that you placed in TWRP. (Try to use the files that say "480x800" as that's the resolution of our screen.) Here is the link: http://forum.xda-developers.com/galaxy-s2-plus/themes-apps/theme-materialised-t2933979
2) Add the Xposed Framework - Go to this link here: http://forum.xda-developers.com/showthread.php?p=62377731
Then, install the Xposed app from the link on that thread. After that, you're going to want to pick the file attached to the OP of that thread that is called "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip" and save it to the root of your external SD card. (Do not download the one that says "ARM64" in it. Just the one I mentioned.) Then, just flash it via TWRP and reboot. You should now have the Xposed Framework installed. Once, again be sure to give the OP thanks on that thread too!
NOTE: After flashing Xposed it may hang on the MetroPCS screen on the next reboot for up to 15-20 mins or so while it's doing stuff. If it's any longer than that, then just pop the battery out and reboot. It will boot properly after that while it reoptimizes some apps.
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Deandre7452 said:
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Click to expand...
Click to collapse
2.8.7.0 is right. The picture I attached of my themed one I just downloaded from the theme thread because I couldn't take a screenshot from TWRP. Everything is good. No need to worry.
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Deandre7452 said:
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Click to expand...
Click to collapse
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Deandre7452 said:
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Click to expand...
Click to collapse
Again, it is supposed to be 2.8.7.0 . Don't go by the picture I posted it was just a sample of what I had. Not a screenshot. Also, it doesn't need to look like mine to work. Theming it was just for fun and should only be done after you've successfully installed TWRP. Anyhow, try flashing this stock recovery file here. Then, boot into stock recovery and make sure you can still reboot to Android from there. If so, then go back and try flashing the TWRP recovery file again instead and see if that fixes the problem. No one else should flash this file by the way unless they are trying to go back to stock recovery for whatever reason. Thanks!
Sent from my SM-G360T1 using Tapatalk
Good job
Awesome! Goood job dude, can't wait till you write up the proper instructions. I'm a noob so don't want to do something wrong.
Another masterpiece By @shineside....
A great BIG Thank you @Bogarty For helping to bring this all together.
We have root, we have TWRP, and that's all thanks to @ShinySide! Great work!
Ok yall I just did a splash screen if anyone don't know but everyone have the color theme already go to the page here http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 scroll down to the change the recovery splash screen download the AIK file First when it finish flash it before anything download the splash set zip when it finish unzip that file then u download the trap kernel root are if u already have it on the device use any root explore renamed the tar.md5 to .img now go to recovery flash that AIK before you start anything hit where u change your theme color but click on change splash then u put the trap kernel.img on the first slot then the second slot click inside the splash set folder choose what color u want then flash it then there u go a new splash screen set......this for anyone that don't know
bogarty said:
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Maybe we could get another youtube video? What do you say, "TheDerek"?
xRaZeR_FuZioNx said:
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Click to expand...
Click to collapse
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
i am oblivion said:
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
Click to expand...
Click to collapse
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
It has to be something you guys are doing during the flashing process that is causing it to boot into TWRP instead of Android. I would try flashing the Trapkernel again from download mode to see if that gives you boot, then if so, try flashing TWRP again. Both should be flashed in AP slot of ODIN. Make sure OEM Unlocking is checked in developer options, etc.
If that doesn't work and it still boots to TWRP, then you may have messed something up in there somehow. Try flashing back stock boot and stock recovery and make sure boot and stock recovery were restored. Once that's working, then you can try reflashing Trapkernel and TWRP. Use this link for more info on restoring your phone and for links to the stock files if you need them.
http://forum.xda-developers.com/showthread.php?p=62906680
Sent from my SM-G360T1 using Tapatalk
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
cmurder61 said:
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
Click to expand...
Click to collapse
Try reinjecting TWRP using the option in settings.
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
UPDATE: Confirmed, this method does work to update to DP5 from DP4.
Reserved
I'm going to try this.
Really want root on my sh**t.
But, theoretically, when DP5 is out, you'll have to do everything again, but with the Vendor image from DP5?
asj0422 said:
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
Click to expand...
Click to collapse
By how some people roll around these forums, I'd remove the lines from the copy/paste box-thingy you did... haha.
Edit: fell on my a**. Reminder for me to be more helpful
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Edit: fell from my pedestal, note to self: be more helpful.
asj0422 said:
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
Click to expand...
Click to collapse
Kudos. Always good to have a write up with steps for folks. Thanks for contributing. [emoji6]
Thanks for this post; I think it really helps having a quick reference for something like this. I can confirm that if you need to re-access TWRP, you can just flash the marshmallow vendor.img over adb, boot to TWRP, do what you have to do, return to bootloader, flash the nougat vendor.img in adb, and continue using your device. I had to use TWRP to flash the Adaway systemless support zip and doing that sequence I listed above worked as expected. It's not as ideal as having TWRP function with an encrypted device as it does on marshmallow, but at least it works.
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
benleonheart said:
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Click to expand...
Click to collapse
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
SyCoREAPER said:
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
Click to expand...
Click to collapse
Worry not, dear friend as I was also a noob back in '08/'09.
We all learn new things every day. I'm just saying that there are dedicated threads to help with newcomers and guide them step by step.
Edit: You're right. Thanks.
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Sweet! This was easy peasy and didn't lose my data. No serious issues, either. Thanks for sharing this info.
Cheers
Sent from my Nexus 6P using XDA-Developers mobile app
crossen0 said:
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
To be honest, I'm not sure. I've never had to deal with twrp and no password. I wouldn't think it would reset anything; I assume you just won't have to enter a password..?
What do you normally do for twrp?
thanks for the guide. Do you think if I'm already on DP4 I could flash the vendor image from an M build and continue from there?
edit: it worked!
Thank you this worked like a charm! Switched from a rooted+busybox stock build to rooted DP4. Now waiting for DP5
No problem! Glad it worked for you!
asj0422 said:
No problem! Glad it worked for you!
Click to expand...
Click to collapse
Just upgraded from my stock M + rooted + busy boxed + xposed build to DP5. TWRP and SU both working. Thanks for the guide.
Just updated to DP5 using this method (all flashes but vendor and recovery, flash M vendor, boot into TWRP, root, reboot to bootloader, flash DP5 vendor). Works perfect.
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
mtw4991 said:
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
Click to expand...
Click to collapse
Thanks for the extra info!
Question: doesn't twrp work with N as it did with M if you're not encrypted? I thought the issue with twrp and N was due to twrp's code not being able to decrypt - and that was the whole reason people were using the modified boot.img and decrypting was so twrp would work.
I can also confirm that this works with DP5. Will be updating OP shortly.
This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?
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