Develop Bugs

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!

I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk

When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?

vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success

I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?

stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!

dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look

During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...

Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

Total Nub's guide to rooting Qmobile Q Infinity & Micromax Canvas Inifinity

After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
Code:
D:
cd D:\Downloads\platform-tools
fastboot oem unlock-go
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
Code:
fastboot boot twrp-3.1.1-0-20171128-UNOFFICIAL-HS2.img
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy

Please port miui 9 or lineage os 15 for micromax canvas infinity hs2

NubbyMcNubNub said:
After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy
Click to expand...
Click to collapse
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do

Hem97 said:
Please port miui 9 or lineage os 15 for micromax canvas infinity hs2
Click to expand...
Click to collapse
I wish I could.
Sudhangshu said:
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do
Click to expand...
Click to collapse
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)

NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Hi, "flashboot boot twrp" wasnt working at all, so i tried "flashboot flash twrp" and all i have is a bootloop. So after flashing recoveru i booted my phone to fastboot and run the command, " flashboot boot recovery recovery.img" where recovery is the custom recovery image and it booted into recovery. Then there is one more step to do that allowed me to finally boot into my os. Its working fine and i still have twrp installed on my phone
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Btw i dont find any pastebin links, im sorry im just a noob too..... Lol

Want custom rom for Qmobile Qinfinity
I want a custom rom for Qmobile Qinfinity.
Because its own rom lags and does not have full features. Please give the rom like lineage os,RR,Or Stock
Please Help?:good:

hi bro,recently i just buy a new phone which is micromax canvas infinity.i have rooted my phone successfully,but there are no custom roms available for this phone.can you develop any custom rom for this phone?that will be very helpful...

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

AT&T Moto Z2 force (XT1789-04) can't access recovery mode

I got a brand new AT&T's Moto Z2 force XT1789-04 (updated to Oreo using an AT&T SIM) and got it SIM unlocked through unlockstone.com's service. After the unlock, I found the following problems:
(1) After every reboot, the device first goes to the fastboot interface (Android man down with box open, just like the figure below but shows "Start" on top right instead ), and I have to press power button to continue a normal boot.
https://www.hardreset.info/media/re...fd1b9659973ee877f48/motorola-moto-z2-play.jpg
(2) In fastboot, If I choose "recovery mode" using volume down/up and press power button, it will go back to the fastboot interface with "start". In another word, I can't see menu of recovery mode, such as "wipe data/factory reset", "Apply update from ADB" and so on.
(3) In addition, the model number has been changed from XT1789-04 to XT1601, but it shouldn't matter according to discussions of other unlockstone's users.
My first questions is, can anyone help me to explain the reason and possible fix to those issues? Would a flash of official AT&T's firmware (such as, NASH_ATT_OCX27.109-47_subsidy-ATT_regulatory-DEFAULT_CFC.xml) be able to fix it?
I understand AT&T locked the bootloader, but it is still possible to flash the firmware, according to:
"With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes." (see, https://forum.xda-developers.com/z2-force/help/updating-att-ota-issues-help-sideloading-t3864514)
So, I gave it an try on my Mac (I also tried on Windows 10, see below):
(1) install moto device manager (MDM Intaller_2.2.9.dmg) downloaded from moto
(2) install 15 second adb and fastboot installer (adb-setup-1.4.3.zip) from XDA
(3) copy files unzipped from (2) to a working folder, copy the firmware as an update.zip file to the same working folder
(4) turn on the device, open developer's options, turn on USB debugging
(5) connect the device to the MAC, choose "USB for file transfer" mode
(6) open a terminal and type the following commands
$ adb devices
List of devices attached
ZG224AGZPZ device
$ adb reboot recovery
Both work fine.
(7) Now the device is in fastboot's "START" mode, not "recovery mode". Since I cannot Select "Apply Update from ADB" from the device, the following command certainly failed:
$ adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
My second question is, can any help me how I can flash the device if the above methods doesn't work?
By the way, I also tried several methods on Windows 10:
(1) Similar to the above method, install moto device manager/or install moto USB driver, install 15 second adb and fastboot, open a CMD window, but "adb devices" couldn't find the device.
(2) Use Lenovo Moto Smart Assistant to "rescue" the device. However, since the device's model number has been changed from XT1789-04 to XT1601, it couldn't go through.
Any suggestions? Many thanks!

Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.

Great! The first problem (automatically paused at fastboot interface) is fixed! Thanks a lot!
This is what I did:
(1)
$ adb reboot recovery
$ fastboot devices
$ fastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.008s
(2) fastboot reboot or reboot the device manually, it will be brought a fresh start asking for account setting and so on.
In this step, the device got stuck at AT&T's Logo and "Checking for update", but can be solved by manual reboot.
(3) Soft reset works (Setting-->System-->Reset) and will show an "Erasing" screen during reboot.
Then a new but famous problem comes up: When use power+volume down to enter fastboot mode and then use volume key to enter "recovery mode", it shows a down Android robot with red exclamation mark + "no command" other then a menu of options.
There are multiple methods available online. What works for me is:
"it worked when pressing power button for 3 seconds then preesing volume up and released both together"
Then select reboot the system.
It can't remove the Android+Red exclamation+no command screen under the recovery mode but at least provides a method to access it.
However, I have to try it a couple of times before it can show me the recovery menu. I don't know why.
According to this (https://forum.xda-developers.com/z2-force/help/z2-force-booting-to-blank-screen-t3808222), this problem might be able to be fixed by "You should flash it back to stock.".
41rw4lk said:
Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.
Click to expand...
Click to collapse

I'm not sure what issue you're having. What you're describing is normal. In Nougat whenever you rebooted to recovery it went to recovery, in Oreo whenever you reboot to recovery you hit a post screen. When you see the android with 'no command' just hold power and tap vol_up, that will bring up the recovery menu like normal. That's the way it is.

XT1789-04 won't boot
Ok, here's my story. I have the very same problem here with the very same phone. Moto Z2 Force XT1789-04 from AT&T. Sim unlocked with same method as they unlocked yours. Converted to XT1601. Can't use Moto Assistant as it will find the mismatch.
Tried the fastboot commands shown here but looks like my problem goes deeper. I'm stuck on a black page that says "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device...."
Looks like they flashed a custom file or something and of course the boolotader is not unlocked and can't be. What are my chances of fixing it here?

Id like to beg for help with rooting my RN 8 Pro

Basically I have rooted my old Redmi Note 4 but that was past guarantee so I did not care that much.
My current RN 8 Pro is still 1 year in guarantee so I literally do not have the balls to do it on my own.
Is there any good soul who would help me out with rooting it, pretty please? Thanks very much in advance
btw. I do know stuff about Unlocking Boot Loader, installing TWRP trough Command Window and Flashing Magisk...that should be potentially enough but as I said above no balls and do not want to F things up and brick it.

Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]
Redmi Note 8 Pro [Begonia] [Global Version Only] WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT...
forum.xda-developers.com
A great guide is here :3
Not sure you need my help for that but yeah if ya run into any problems, ill be here to help ya

Ty for responding. I read that but Im still not sure about what TWRP use on my phone (im not sure if i have to use special one or just latest version) and because I want to only root my phone Im also not sure, if I need to get a different ROM or I can do that on this STOCK ONE I have.
I bought my RN 8 Pro in EU. Im gonna try to give you more information about my phone, if you would be able to link me TWRP what I need and other files to root it...that would be awesome (its not like i cant read or im lazy f**k, its more like i dont want to F things up).
Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
Thank you very much

1. UNLOCKING BOOTLOADER :
- Download the Mi Unlock app to PC, and sign in with your Mi Account;
- Enable Developer Option in your phone by tapping the "Build Number" 7 times
- Go to Developer Options "Settings > Additional Settings > Developer Options
- Enable USB Debugging and OEM Unlocking
- Aslo add account in Mi Unlock Status (Can be found in Developer Options
- Install all the required drivers (adb drivers, vcom drivers etc.) In your PC [I'll link these below]
- Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode
- Connect your phone to PC using USB cable and click "Unlock". In Mi Unlock Tool
- You will be given a specific time (168 hours mostly)
- Wait until that and redo Unlock process
- Your device’s bootloader is unlocked
2. FLASHING TWRP :
- Install Minimal ADB and fastboot on your PC [Link will be provided below]
- Download LR Team TWRP [This work for now, I'll provide link below and will update it after we have another proper TWRP]
- Put that TWRP in the file location of ADB and Fastboot (Right click on Minimal ADB and Fastboot icon on desktop and click on Open file location)
- rename that recovery to "twrp" for convenience (optional)
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode
- Type
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type
Code:
fastboot flash recovery twrp.img
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
- Done
3. ROOTING :
- In TWRP mount System
- Go to Advanced > file manager
- then go to system_root > system and delete "recovery-from-boot.p"
- Go home and again go to advanced and Select "Close AVB2.0" swipe to confirm.
- Go back and select "Install Root"
- Here you go magisk 19.4 will be installed (U can chose any other versions afterwards.)
- Reboot the device to system.
- Done!
LINKS
1. Mi Unlock tool
2. Minimal ADB and Fastboot
3. ADB Drivers for MTK
4. MTK USB Drivers
5. LR Team TWRP

Hello once again...I might need some help
I was following these steps but after flashing this TWRP I cant enter into the TWRP...so far Ive tried holding power button then pressing Volume +; holding power button and then holding Volume+; even holding them both but still without any result...any chance you might help me here, please?
*EDIT: Im flashing stock ROM

Go to the system then do
adb reboot recovery

I flashed TWRP recovery once again, then I went for "adb reboot recovery". This is what happened after I used "adb reboot recovery" (attached picture). There is no sign about TWRP. What am I doing wrong? I literally followed the guide the flash of the recovery TWRP is successful. Is there any chance that Im flashing wrong TWRP recovery? Or that Im doing it on stock ROM? Usually its problem between chair and keyboard but I dont know :-/.

So Ive tried to boot TWRP through after flashing it with "fastboot boot twrp.img". It went through but it booted like normal so I ended up in system like when you turn on your phone normally.

Anybody, anything please?

N00B92 said:
Anybody, anything please?
Click to expand...
Click to collapse
First: what version of miui?
If you're on miui 12.5 this method will cause reboot.
If your phone is < 12.0.X its okay.
It looks like flashing recovery worked.
Instead of trying to adb reboot recovery after flashing recovery try this:
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.

Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
I was already trying that, if I do it how you typed the screen is gonna keep blinking with MIUI logo.

I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.

N00B92 said:
I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.
Click to expand...
Click to collapse
First you need to enter recovery, i think you didn't flash boot.
Follow the method below exactly.
Original post and files can be found here.
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.

I dont have any boot.img in my folder so I cant flash the boot.img. Having stock ROM and I have no clue where to get it.

My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm

Id appreciate any help
Everything I did try is above.

N00B92 said:
My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm
Click to expand...
Click to collapse
madsponge26 said:
Redmi Note 8 Pro
[Begonia]
[Global Version Only]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community
Click to expand...
Click to collapse
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.

Kenora_I said:
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.
Click to expand...
Click to collapse
Thanks. I used the boot.img and I was following the guide which "donkyshot" sent. But I got stucked right after I did those commands in command Window. I disconnected the phone went for the power button hold and then when it was blank I stopped holding power button and I started holding the Volume+ button. The phone was bootlooped on Xiaomi logo...I was waiting several times but nothing. At the end I had to flash the phone with stock ROM I downloaded through MiFlash...I really dont know what I was doing wrong.