Related
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...-unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
mumith3 said:
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
Click to expand...
Click to collapse
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
mumith3 said:
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
MrKnight230 said:
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
Click to expand...
Click to collapse
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
mumith3 said:
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
Click to expand...
Click to collapse
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
MrKnight230 said:
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
Click to expand...
Click to collapse
No mate, You'll need a SD card.!!!
mumith3 said:
No mate, You'll need a SD card.!!!
Click to expand...
Click to collapse
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Phone works again now! I love all of you!!!
MrKnight230 said:
Phone works again now! I love all of you!!!
Click to expand...
Click to collapse
Enjoy and do come back
Just kidding...
Sent from my PLK-L01 using XDA Labs
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
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.
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Thank you so much!! Very happy to finally have write access to /system! Nice work!
I'm just hoping we get some ROM support on this phone. I always run gappless. Lol.
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Yo just curious can you explain to me how you built this i cant seem to get it build rigjt or send me your source files
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
arkansawdave74 said:
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
Click to expand...
Click to collapse
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Here is a updated TWRP with everything working use at your own risk
treesus said:
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Click to expand...
Click to collapse
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
I now have the phone I meant to get in the first place, the Moto G9 Power with an official TWRP build.
arkansawdave74 said:
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
Click to expand...
Click to collapse
I used lolinet files on my 2021, no touch issues, but mine uses the Ilitek display. But since you seem to be familiar with Linux as you put it, you could unpack and repack yours and ramdisk, having pulled files like I outline in https://ilitekforum.xda-developers....ased-updated-11-4-2021.4354855/#post-85885471, so you may be able to make your TWRP have touch, unless you meant damaged so much that's broken too.
I posted a fixed twrp file for you all
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Onoitsu2 said:
unless you meant damaged so much that's broken too.
Click to expand...
Click to collapse
It's out of there. I'lI maybe get another one though because I really want to try Visible Wireless Service and this G9 Power doesn't have esim capability. True unlimited with no hotspot cap for $40/month. Maybe too good to be true, but I gotta check it out. Until then, Check ya laters borneo dudes.
treesus said:
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Click to expand...
Click to collapse
I dont make change logs this is twrp 3.4
svoc said:
I dont make change logs this is twrp 3.4
Click to expand...
Click to collapse
I build for myself then when it working I give it away I do t keep track of what I do to get it working I just get it working then give it out sorry I'm working on LineageOS right now I got the device trees working last night I got my first build working but still a lot to test out before release
Excited to follow development for the Borneo. Thank you.
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
svoc said:
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
Click to expand...
Click to collapse
No fluff - just stock. thanks for your hard work.
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
4xc7xy said:
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
Click to expand...
Click to collapse
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Onoitsu2 said:
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Click to expand...
Click to collapse
No I did not, let me try that right now and then do a follow up reply to tell you how it goes
I am trying to patch the bootloader of T2B2.221216.008 but every time I flash it and reboot Magisk says it is not rooted.
I have tried the Factory image bootloader as well as the OTA bootloader and nothing works.
Am I missing something? Thanks.
You have to use the boot.img from pixel 7 still
ne0ns4l4m4nder said:
You have to use the boot.img from pixel 7 still
Click to expand...
Click to collapse
Ugh, I remember reading this ages ago - must have forgotten. Thanks!