Unofficial TWRP Recovery for Moto G7 Power
(XT1955-5/ocean/supra)
I didn't want to wait any longer for an official build of TWRP for the Moto G7 Power (ocean) so I ported it over myself following these directions . So far it appears to work with little to no issue with the exception of decryption of userdata on later rom buids...
I was even able to install fastboot(ed) image to ramdisk & flash Magisk-19.3 via TWRP. Hopefully this can hold some of you off until an official build comes out.
If you guys wish to try it out I have uploaded it to my Android file host here.
Latest attempt HERE
Installation Instructions:
1. You will need to boot image via fastboot initially
Code:
fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
2. Once TWRP boots push Magisk v19.3 to /tmp/ & flash if not installed or you will bootloop
a.
Code:
adb push Magisk-v19.3.zip /tmp/
b.
Code:
adb shell
c.
Code:
twrp install /tmp/Magisk-v19.3.zip
3. Push twrp-3.3.1-0-ocean-20190904-0715.img to /tmp/
Code:
adb push twrp-3.3.1-0-ocean-20190904-0715.img /tmp/
4. Install recovery to ramdisk via fastboot(ed) TWRP
Code:
Tap Advanced > Install Recovery Ramdisk > Navigate to /tmp/twrp-3.3.1-0-ocean-20190904-0715.img
5. If Magisk is installed prior you may bootloop back to recovery
Code:
Advanced > Fix Recovery Bootloop & Reinstall Magisk
NOTE:
When providing feedback please include the build date of port, carrier, security patch, and rom build number of your G7 Power. The last two items can be found in Settings > System > About phone > tap Android version .
E.g.
20190904-0715
Metro
March 1, 2019
PCO29.114-54-2
good, step 1 is in fastboot mode, the 2,3,4 is the pc? or how can I flash
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Geofferey said:
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Click to expand...
Click to collapse
install very well start but not let me do anything on the mobile screen does not respond
Alexhdavila said:
install very well start but not let me do anything on the mobile screen does not respond
Click to expand...
Click to collapse
yes, but when it is installed to the device Ramboot, the screen responds then. Use this image to boot TWRP, then use it to install G's build
---------- Post added at 08:10 PM ---------- Previous post was at 07:49 PM ----------
https://drive.google.com/open?id=1n2YwMJ0CcZU5rze6ibaOM68Ox6bxPL9M
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Scholeggo said:
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Click to expand...
Click to collapse
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/1Clvwof18aLCF8NQqqjvSCkNEpQAkp6tO/view?usp=sharing
Edit: ^ Touch screen works on initial boot and after for my device. Added driver /vendor/lib/modules/aw8624.ko to /sbin/load_drivers.sh. Though I'm not sure if that is a touch related device and a google of aw8624.ko returns nadda.
Geofferey said:
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/14JN1e8OlK_sj-AgpD5i97T-vrB5STOSJ/view?usp=sharing
Click to expand...
Click to collapse
Ok, I did send logs that should indicate that decrypting does not work.. I am using Phhusson's AOSP GSI for this test. My G7 Power is 1955-5 on Metro
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Scholeggo said:
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Click to expand...
Click to collapse
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Geofferey said:
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Click to expand...
Click to collapse
huh.. before flashing, i was last on the August build.. and yes, i flashed it to ramdisk and did not have an effect with decrypting the device.
no, touch screen does not work when fastbooting your build.
update: with your newer build (with datestamp), touch still doesn't work on fastboot
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Click to expand...
Click to collapse
No Hangouts, but what about Telegram? +561-800-8299
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP.
Click to expand...
Click to collapse
ok, maybe not decrypt like that, but at least have TWRP not mess up internal storage when wiping system?
On the test-v1 I sent, it does that when wiping system alone, rebooted or not. With yours, it does that only when rebooting recovery; as long as you flash another system right after wiping, internal storage seems to be unaffected with your build.
If not decrypting the storage, it shouldn't mess up internal storage at all when wiping system
I think it's a mechanism of the device. When I flash any GSI on top of any userdata that was created by stock rom it messes up that data, most likely intentionally. That happens with 'fastboot flash system system.img' as well. Can you help me with the touch issues?
Try Me!
LATEST ATTMEPT !
Edit:
My last attempt before I say I don't know what I am doing. I've attempted to include all the kernel modules this recovery should need inside the image. There should be no need for it to load modules from /vendor/lib/modules. Hopefully this fixes the touch screen for most users when fastbooting and installing to ramdisk.
your newest build works touch functions properly
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Geofferey said:
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Click to expand...
Click to collapse
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Hey man thank you so much for your work! Just wanna triple verify tho! This will work on the metro variant? Also is it possible do you know to flash rims from the other g7 series phones?
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
uHeash said:
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Click to expand...
Click to collapse
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
OGandroid said:
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
Click to expand...
Click to collapse
Sick man this is awesome I've been waiting for this! Now for some rims and it'll be smooth sailing!
Related
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
Reserved.
You are the man! Cant believe we have TWRP this early! Just in time for the next OTA!
Thank you for this! Great work, it feels like an early Christmas!
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Thanks you!
Is anyone having the touchscreen not work after a reboot?
Archangel said:
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Click to expand...
Click to collapse
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
On the Pixel 2 XL touch was broken unless you used a custom kernel. I guess it's the same on 3. If you boot TWRP using fastboot it should allow touchscreen.
You would think after buying the Pixel 1, 2 and 3 I would have this whole A/B slot thing down pat but I dont LOL. That did the same thing for me too. I just rebooted into recovery and flashed TWRP again and it has been fine since. I think sometimes it switches slots and that causes the bootloop. I messed around with changing slots and I think I am on slot A and all if fine for me.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
I had that happen I think once and I just rebooted back into TWRP and it was fine.
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
ktdt00 said:
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
Click to expand...
Click to collapse
No, only the current slot needs to be rooted.
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Is root
To Pixel 3 owners that succesfully rooted, can you share the build.prop here? /system/build.prop
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Carmenlove said:
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Click to expand...
Click to collapse
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
jsauder2 said:
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks! I will give it a try this morning after some coffee. I learned a cool trick last night to get my hotspot to work un-rooted, so I am less desperate than I was last night.
Carm
freebordjunky said:
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Click to expand...
Click to collapse
Just enter your PIN at the TWRP prompt and it will work.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
I have a similar problem. After installing twrp, I can boot to the OS, but Magisk isn't installed and I don't have root. After going back to Twrp and flashing the magisk zip, i can't get past the bootloader screen with a error saying something about failed to load boot.img.
Re-fastboot flashing the patched boot img to both slots brings me back to a rooted state with all magisk modules loaded and applied, but no more twrp. I technically don't need twrp for anything except for nandroid backups, but I guess i could just backup using the adb backup commands and get similar results, right?
Either way, I'm open to suggestions for how to get twrp and magisk working at the same time.
Code:
*** Disclamer * Your warranty is now void. * *
We are not responsible for bricked devices, dead SD cards, * thermonuclear war,
or you getting fired because the alarm app failed. Please * do some research if you
have any concerns about features included in this ROM * before flashing it! YOU are
choosing to make these modifications, and if * you point the finger at us for messing
up your device, we will laugh at you.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
How did you prepare this?
Do you also have flashable .img of TWRP for G6 Plus?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
Simple Great!
For me adb sideload dont work, even when i type "adb devices" or "sudo adb devices" just appear "no devices/emulators detected" but when I use twrp via "sudo fastboot boot twrp.img" all works propertly. Although i type adb kill-server and sudo adb start-server no fix that than in the another method it works. I think maybe is for version (3.2.3-0) works and in your (3.2.1-0) dont (?) or Is by in one Is installed on the devices and the another not (?)
Thanks in advance for an posible solution. Grettings from México
Many thanks in advance segra246x.
Unfortunately for me, every time I´ve flashed TWRP, then I do not know what may i do to reboot the phone. My phone is unlocked and I am root with Magisk, so I do not know which boot should I flash at the end, so that it starts again and does not stay in a loop with TWRP or in brick.
Couls you tell wich procedure are you using to can start the device normally?
i flashed patched boot image, Should i flash boot patched boot image and re-start again Magisck instalation? Should i flash boot boot.image from the regarding stocke version without loosing root satus?
Thank you, the twrp works fine installed with stock Oreo 8.0.
Worked on G6+ with Pie. Thank you!
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
Please explain your process & is it still working? What version are you on with 9.0?
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
This method still working for you?? And I don't see any credits so did you create this installer??
I used the exact file and the 5 step method outlined in the original post.
Hey did you create this?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooed with magisk!!
Click to expand...
Click to collapse
I can't find any credits.
---------- Post added at 08:11 AM ---------- Previous post was at 08:02 AM ----------
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
**I noticed that you have not been logged in here for
about a month. When you get back please inform me.
I have an error to flash the twrp, how did you do it?
Instructions..
HorryStorm said:
I have an error to flash the twrp, how did you do it?
Click to expand...
Click to collapse
Follow the directions. Couldn't be more simple.
First use our official TWRP 3-2-3-0 to BOOT into
There you flash this installer.
I have used this installer and can say it's good.
MPT works.. you can then reboot to recovery at
Anytime. Hope that's helpful. Good luck.
--Ken
the question is that when I try to make the flash it appears a maximum size error.
This is only for Moto G6 Plus. If that's your device
Then idk. I've installed it several times and never had
An issue.
Ok, thanks.
I dont have OS Pie9 after flashing twrp
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
---------- Post added at 01:29 PM ---------- Previous post was at 01:10 PM ----------
lavriiga said:
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
Click to expand...
Click to collapse
I fix it, First i flash PIE 9.0
Then i boot in twrp.img in fastboot
Then zip TWRP.zip and after that i install MAGISK 17.1 And it works ! Thanks for posts !!!:good::laugh::laugh::laugh:
Secure Startup Password
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G6-Moto-G6-Plus-Moto-G6/G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
roomfool said:
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G...G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
Click to expand...
Click to collapse
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Thanks
randomanonymousname said:
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Click to expand...
Click to collapse
OK I was not sure if this was more related to the ROM or TWRP, my bad for posting in the wrong place. I have tried the AOSPExtended 9 ROM and all 3 flavors of the phh treble 9 ROM with the same result. Have not had any luck installing Lineage or any of the 8.1 phh treble ROMs. I will keep digging to see if I can't find some info about this. Thanks.
Hi, my backups get stuck at 80-90% sometimes, does anyone have the same issue?
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
orozcore said:
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
Click to expand...
Click to collapse
There's a TWRP for pie
mr_reaper said:
There's a TWRP for pie
Click to expand...
Click to collapse
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Which TWRP version u running?
mr_reaper said:
Which TWRP version u running?
Click to expand...
Click to collapse
sorry for the late reply the version i'm using is recovery-TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Click to expand...
Click to collapse
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
EDIT: Also, the stock Pie release is good. I am currently on Pixel Experience but may switch back to stock rooted at some point. Until Xiaomi releases the Pie kernel sources, no custom ROM is going to be perfect.
lexridge said:
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
Click to expand...
Click to collapse
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go.
Click to expand...
Click to collapse
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
chan200606 said:
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
Click to expand...
Click to collapse
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
lexridge said:
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Not many people will shutdown their phones to test the restore guys. It's difficult, but we have to wait for someone to try this with the latest version of twrp. Nothing dusturbing here in my opinion. We will thank whoever tries this first that's for sure.
chan200606 said:
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Click to expand...
Click to collapse
Interesting. I did not know you can flash img files directly with TWRP. Haha. Color me stupid!! How does TWRP know which partition to write the .img to? Does it give you a choice?
Yes it does. Choose recovery.
lexridge said:
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
MetallicGR said:
Yes it does. Choose recovery.
Click to expand...
Click to collapse
good to know you can flash a img within twpr so i'll try when I update
mr_reaper said:
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
Click to expand...
Click to collapse
Yes is bad to wait so much time and there's nothing you can do I read about the version of the unlocker but with no luck. So I finally have unlocked bootloader.
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
If you didn´t read before a member linked to you In the post #6 both TWRP versions.
About your steps:
- No need to backup previous TWRP, just flash the new image and reboot to recovery again.
- If you already have Magisk no need to flash it again so you won´t lose root status nor any data/settings of the rom.
If you want to unroot the 0212 has this option in advanced menu.
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
You should probably update your TWRP first and foremost, otherwise no access to data after you flash the update.. You will also need the Magisk Manager as an apk somewhere on your microSD card. I edited your to-do list:
* Download Magisk Manager and store on your microSD card.
* Flash new TWRP (0212 or 0121).
* Make a full twrp backup and do a recovery only backup as well
* download the update
* let it update and hope no lost of data
* Reflash img or TWRP Recovery backup 0212 or 0121
* Reboot recovery, check that you can decrypt data
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
* After first boot, manually install your saved Magisk Manager app from microSD card. Run it. Check if all is good.
Do you use Titanium Backup? If so, make a full TB before doing any of this.
---------- Post added at 01:04 AM ---------- Previous post was at 12:42 AM ----------
SubwayChamp said:
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
Click to expand...
Click to collapse
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
lexridge said:
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
Click to expand...
Click to collapse
I never saw before this kind of weird behaviour btw is working generally speaking fine.
I´m not a fan of camera but the stock is so far better, I noticed that HavocOs rom has the feature to enable camera2 api and EIS, maybe you might try it. Regarding to use a custom launcher on stock miui rom there´s Poco launcher that keeps the same system icons than theme chosen and is very fast.