Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
Related
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
When it asks you to install update, what if you say no, then you should be able to boot into recovery from the bootloader.
Sucks you're having issues.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
Take the PBxxxx.zip file off of your zip card
I was wondering the same thing; thanks for the info.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
Can't we do this in adb?
"adb reboot recovery"
g00s3y said:
Take the PBxxxx.zip file off of your zip card
Click to expand...
Click to collapse
Like g00s3y said, you must first remove the file you were trying (or successfully) flashed off your sd card. It's always best to remove this file once youre done with it. In your case you will probably need to use a sd card reader unless you can get your phone to mount.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
I got the exact same problem
I ran into the same problem last night. I hooked my phone up to my laptop which has adb installed. When you're stuck at the start up screen, in a command prompt just type:
adb devices
You should see your phone show up under devices. If it shows up, then just type:
adb reboot recovery
This will get you into your recovery, and I just started the whole process over again. The 2nd time through everything worked great.
Hope this helps. (my phone wouldn't hard boot in to recovery, which I'm assuming is your problems also)
To hard boot into recovery, just hold the volume up key and turn the phone on. (correct me if I'm wrong)
Now I went and did it!
OK, so I was loading a new ROM and something went terribly wrong. I got stuck on the HTC, quietly brilliant screen. I then tried to boot into recovery thinking I would just restore the back up I had made and for some reason it jumped right to the HBoot and ran through some sequence of commands. Next thing I know I don't have root! So I'm screwing around trying to get adb to work on my computer and having problems with that. I try to recover again on the phone (power button and down volume) and notice that I still have s-off. Doesn't that mean I have root? But I also can't find a super user on the phone and none of my 'rooted' only programs work, they all say I don't have root. What do I do now?
Hboot is vol down and power.. not recovery. What that did was look for an update file on your SD card and flashed it. When you rooted your phone did you use the 1 click root? If so you probably just need to do step 3 again.. which gives you root and the super user app.. hopefully that's all it takes. When your done go into your SD card and remove the PG05 (there's more to the name don't have the whole file name memorized) zip file that's on there so it doesn't happen again
Sent from my ADR6400L using XDA App
BobVS said:
OK, so I was loading a new ROM and something went terribly wrong. I got stuck on the HTC, quietly brilliant screen. I then tried to boot into recovery thinking I would just restore the back up I had made and for some reason it jumped right to the HBoot and ran through some sequence of commands. Next thing I know I don't have root! So I'm screwing around trying to get adb to work on my computer and having problems with that. I try to recover again on the phone (power button and down volume) and notice that I still have s-off. Doesn't that mean I have root? But I also can't find a super user on the phone and none of my 'rooted' only programs work, they all say I don't have root. What do I do now?
Click to expand...
Click to collapse
You will have to re-root now. This should teach you to be more careful and not just go randomly flashing and updating things. Read up some more before just trying things.
Yeah probably like he said your best bet is to re do the whole process.. Idk what you flashed on your phone or anything so just be careful and do your research before jumping into things.
Sent from my ADR6400L using XDA App
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
When flashing a new rom make sure you check the md5sum. You can do this in adb or dl a program, just google it. If the md5sum comes back with the correct number then you know the dl isn't corrupted and you have the correct dl.
But as far as your current problem, you need to re-root.
Research your steps before you do them. I'm NOT a fan of 1-click. If you do it manually, and one step seems not to go right, then stop and ask on the forums. Someone should respond.
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
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC
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.