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?
Related
Updated for more serious reference. Hope this info helps you!
Procedure:
Once you have updated to Nougat, you would have to unlock your bootloader
The APK that unlock the bootloader works (Even though is marked as M version). (Remember that this will wipe your device!) For ULBL -> Version UnlockTool_2017_0803(android M) (FROM ASUS) https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/
Zenfone will reboot and you will able to see a new splash screen that informs you that your device is unlocked giving you boot options Don't press anything. (You will see this everytime you reboot). The next screen will show an erase process. Phone will reboot.
Once booted enable developer options and adb via usb.
You can find TWRP builds right here: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w (Special thanks to: @shakalaca) Use the latest one.
Go to fastboot mode and install TWRP. (fastboot flash recovery (nameoffile).img)
Let fastboot do it's magic, once you finish press volume buttons till you find reboot recovery press power button to select. It will boot again to the first splash. Do not press anything, let it work. It will boot TWRP in a whistle.
Once in TWRP make a backup. You know it's necessary, and will save your ass in case of a softbrick.
Flash latest magisk (Current Ver: 13.3) Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot, check drawer for magisk manager, magisk and root should be enabled.
Voila. Safetynet test passed :good:
what version was twrp are you using and what steps did you take to get magisk to work.
smariob said:
So today finally I got my Asus Zenfone 3 Zoom. I couldn't contain myself to start playing with it.
My very first surprise was that the phone requested for an update. I've done it. I ended with a stock 7.1.1 AZ3Z.
This is my experience:
The APK that let you unlock bootloader works. (Remember that this will wipe your device)
After auto reboot I cheched safetynet. At this point test failed (Little bit obvious)
I was able to go to fastboot mode and install TWRP (The same you can find right here at the forum)
Let fastboot do it's magic, press volume buttons till you find reboot recovery. It will boot TWRP in a whistle.
Once in TWRP I made a backup. You know if necessary.
The next step was a crossfinger procedure. Just flashed latest magisk Beta (13)
Reboted checked for magisk manager on drawer.
It was there and root also. Enabled magiskhide, and voila. Safetynet test passed :good:
Hope this Info help you.
Click to expand...
Click to collapse
Do you know if this works with Android Pay?
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It should work with it, im able to login intoy bank account with no problem with this method, I will give it a try for you though.
mr573162 said:
what version was twrp are you using and what steps did you take to get magisk to work.
Click to expand...
Click to collapse
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It's twrp 3.1.0
It should work as it passes CTS profile and Basic Integrity I can't test it myself because I live in Mexico and Android Pay is not avialable here yet.
Will edit OP
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
GarGarStinks said:
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
Click to expand...
Click to collapse
Everytime you reboot the pone starts into boot loader. It has a countdown to boot into whatever is commanded.
Once you flashed succesfully the recovery img you just have to select option to boot recovery with vol keys and power.
Phone will reboot into bootloader agin let it boot on contdown (don't press any key)
Then it will boot into twrp.
Hello, on nougat i am trying to install the twrp, I downloaded the official bootloader release program (after installing the message "unlocked device") but trying to install the twrp via fastboot me by an error message. ... but I think the problem is the unlocking of the bootloader (if I turn the ze553kl in fastboot mode I see my device is "locked") ... there is another version of the bootloader release software? The one available on asus site would look for android M ... maybe there is one for Nougat? Thanxs
Wop. I used the M version apk on Nougat. It worked with no issues, the unlock of boot loader is successful when all the content of your smartphone is wiped.
For reference: https://www.youtube.com/watch?v=hg77b8o8Jk4 Min 1:29
Thank you! But running the software, does not run any wipe, it only displays an "unlocked" message without having to restart anything else. I also tried to make a "factory reset" and repeat lab process but the result does not change ...
TWRP tip!!
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
Updated, never had mirror issues but is always better to have latest recovery.
Edit. Jimbo, I got an anwer from the source it notes: "please use 'fastboot flash recovery' instead of 'fastboot boot' to avoid up side down screen"
I've also tried installing from scratch with Asus flash tool, but I still can not unlock bootloader ... Anyone know if there is also an unofficial method for unlocking the bootloader?
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Double posted... (Don't know for what reason this is happenning)
smariob said:
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Click to expand...
Click to collapse
Ze553kl. WW_Z01H
bizzino said:
Ze553kl. WW_Z01H
Click to expand...
Click to collapse
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
smariob said:
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
Click to expand...
Click to collapse
Locked
Works just fine, thank you
But how would I go about setting the phone back to stock if needed in the future? (Removing Magisk, and replacing TWRP with the original recovery software).
@bizzino No news for you i wasn't able to find more info I'm sorry. Maybe change it for warranty? @subsector you should flash original recovery via fastboot and then sideload the stock rom
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Hello thanks for your guide but i think we first need to unlock bl And for the twrp recovery to stick and not to be replaced by xiaomi recovery we need to flash something called "dm-verity " it basically removes that check, which replaces any other recovery by xiaomi recovery
Have a nice day and thanks for your work
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Sent from my MI 8 using Tapatalk
Fastboot flash recovery Command should do it ..
mekaziah said:
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Click to expand...
Click to collapse
Skickat från min MI 8 via Tapatalk
what issues do you get with magisk? I was able to flash it without any issues.
superior8888 said:
Fastboot flash recovery Command should do it ..
Skickat från min MI 8 via Tapatalk
Click to expand...
Click to collapse
Yes it does. Don't know why anyone would run SuperSU though.
mekaziah said:
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Click to expand...
Click to collapse
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
-fluffy- said:
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Would you mind stating the version of Magisk?
Strange Guide no Attention for Unlok Bl.
barrielui said:
Would you mind stating the version of Magisk?
Click to expand...
Click to collapse
16.4
magisk has been working fine for me for a while
samwise110712 said:
what issues do you get with magisk? I was able to flash it without any issues.
Click to expand...
Click to collapse
What's your ROM version? I flash twrp then magisk, bootloop...
-fluffy- said:
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
omek07 said:
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
Click to expand...
Click to collapse
simple put twrp.img on ur storage
then flash img from twrp
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Could you please tell me what rom you have ???
Thank you
omek07 said:
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
Could you please tell me what rom you have ???
Thank you
Click to expand...
Click to collapse
u choose recovery
im using miui eu
magisk is running without any issue.
i am on the newest xiaomi eu beta rom and flashed magisk 16.7 without any issue right now
(after waiting horrible 15 days for unlocking the bootloader)
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
omek07 said:
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
Click to expand...
Click to collapse
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
felixrao said:
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
Click to expand...
Click to collapse
My friend i changed to the Xiaomi eu and everything worked. You dont have to flash the Chinese Version first you can go from Global to Xiaomi.eu. Just dont forget to do FORMAT data and not only Wipe Data.
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!
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
gbetous said:
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
Click to expand...
Click to collapse
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
totalnoob34 said:
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Yes !
I used the official LG tool for recovery (see www.lg.com). The magic key is "vol UP + USB plug" and the phone switches in some specific recovery mode. Nothing particular to do, the tool is automatically downloading the latest offical firmware and flash it.
Thanks !!!
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
I think that Magisk Manager already patched the boot image, I don't know whst will happen if you patch the 20.2 version with the 20.1. I would suggest you to check in /data/ folder for the boot image backup, copying them to pc if they are there, and then trying to reboot directly into recovery (Magisk Manager>Modules>Menu>Reboot to recovery) and from there flash back the old boot image. In case after reboot you get into fastboot, you can just flash the backup boot image with fastboot flash boot boot.img
tremalnaik said:
Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
tremalnaik said:
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
SrZambie said:
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
Click to expand...
Click to collapse
Yes, stock Oreo ROM with MK2000 kernel.
tinyspeck said:
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
Click to expand...
Click to collapse
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
Click to expand...
Click to collapse
I looked around and found that this isn't LG specific. Someone with the Razor Phone 2 had their partitions wiped aswell. It sounds like it's having issues installing with certain ROMs which would explain why I wasn't affected. It's best to stay with 20.1 on stock ROMs for right now until it's fixed.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
Click to expand...
Click to collapse
It was stuck on static LG logo. I reflashed the same kernel which I installed last July (mk2000 v2.1). I also wiped cache and dalvik (kernel shouldn't need this but just in case...). It is strange that it stuck on static LG logo because later, I followed your advice and I installed the boot.img from /data/magisk_123... and the phone is back, working as new
So magisk is not so bad as it has a backup solution.
Thanks for your support
Static logo is loaded before system, so the problem wasn't the system partition. Probably my phone couldn't load boot partition at all, falling back to fastboot, while yours was loading boot partition but an error was occourring the meanwhile, leaving it at the logo. I'm glad that you solved the problem.
While reinstalling Magisk after the kernel, don't forget to check if the torch is still working: if it's not working, just flash once again the kernel and it should be ok.
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
devil1 said:
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
Click to expand...
Click to collapse
It's not possible to switch from stock ROM to custom without doing clean install. You will have to root again.
First update to latest Official Stock ROM, then take backup of your files to your PC or to SDCard (if you have one) , flash to latest Official TWRP and check my POCO F1 Ultimate Collection & Guides. You can find everything there. I have awarded recommended ROMs in my collection.
Feel free to ask if you have any question regarding the guides.
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
devil1 said:
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
Click to expand...
Click to collapse
First you need to take backup of your files to PC or External SDCard.
Then you should update to latest version of MIUI via OTA if it's possible or via TWRP (you can use the stock recovery rom to do it via twrp). (You can also use my guides for clean install stock rom)
Then you should unlock your bootloader if it's not already unlocked.
Then flash latest Official TWRP.
Then flash latest firmware (not vendor) just to make sure you are on the latest. (You should be on latest firmware after updating to the latest MIUI version)
Then Wipe everything + format data according to my guides and flash the ROM you want. If you choose A12 Pixel Experience or crDroid keep in mind that these ROMs use their own recovery because these are encrypted by default ROMs and TWRP can't handle the decryption of A12 encrypted ROMs yet. So to make OTA updates and that stuff work correctly devs of these ROMs decide to use their own recovery which can handle the decryption of encrypted roms and as result to make OTA update work fine. Check the installation instructions of these roms in their threads. (Afterwards you can use adb sideload to flash stuff using these recoveries)
After that, flash Magisk since you want root.
Then you can restore titanium backup if you want.
OK i follow your instruction.Thanks
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
i have find this video.This is not the good phone but i think that the installation is the same:
devil1 said:
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
Click to expand...
Click to collapse
Yes use Fastboot Method to flash TWRP. No problem with encryption.
After that follow my clean install custom rom guide to flash the ROM you want. Also please check the instructions in the threads of ROMs you want to flash. A12 crDroid and PE use their own recoveries.
Basically tell me which ROM you want to flash to help you exactly with steps.
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
devil1 said:
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
Click to expand...
Click to collapse
Send a screenshot what you type in cmd and where you have the twrp.img
Or you mean you can't find it in your device while you are booted on TWRP?
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
devil1 said:
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
Click to expand...
Click to collapse
Are you sure you select Install Image?
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
devil1 said:
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
View attachment 5549731
Click to expand...
Click to collapse
I have all the steps on my guide. Please read it carefully. It boots back to mi recovery because you haven't flash TWRP yet just booted into. After boot into TWRP u need to flash twrp in recovery section so it will stay after reboot.
Please read the steps.
Download portable Minimal ADB and Fastboot and latest Official TWRP recovery.
Open cmd from minimal adb and fastboot and write:
fastboot boot and the path you have TWRP.
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.0_9-0-beryllium.img
Then proceed with the rest steps in my guide. Connect ur device to pc while u are booted into TWRP and copy TWRP.img to your device. Then in TWRP press Install Image and select the twrp.img u just copied into ur device. Select recovery and done.
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
devil1 said:
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
Click to expand...
Click to collapse
Hmm strange, probably of MIUI. Anyway since you are going to flash custom rom, when u flash twrp in recovery go back and select wipe and wipe everything (read my clean install guide), go back press format data type yes, and then reboot to TWRP.
EDIT: I just saw u rebooted to system. That's not what we want. Press reboot to recovery.
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
devil1 said:
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
Click to expand...
Click to collapse
The TWRP flashed correctly. You overlap it again by pressing reboot to recovery from MIUI updater.
Don't do that...do the combination to boot to TWRP after flashing it. Power+Volume Up.
And continue with clean install steps in my guide to flash custom rom.
In my guide I write nowhere to boot to MIUI and press from MIUI Updater reboot to recovery, please stick to my guide and you will be fine.
Poco f1 update not