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)

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?

Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium

Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back

Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)

merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time

Unable to boot into TWRP

Hello everyone,
I really need help from you guys.
Yesterday I successfully flashed LineageOS 17 but unfortunately I forgot to flash Gapps using TWRP. I booted into system and then only few seconds afterwards I realized that I forgot to flash Gapps.
Then I tried to boot into recovery but the problem is I got forced to boot into stock recovery instead of the TWRP that I managed to flash in the first place. After that I tried to re flash the TWRP but then I got booted into the stock recovery everytime. Here is what I did and still failed to boot into TWRP:
1. adb reboot bootloader
FastBoot Mode
PRODUCT_NAME - ZS620KL
BOOTLOADER VERSION - WW_90.11.162.72
SERIAL NUMBER - J8AZB760J064ADX
SECURE BOOT - yes
ACTIVE SLOT - b
DEVICE STATE - unlocked
2. fastboot --set-active=a
3. fastboot reboot bootloader
4. fastboot flash boot boot.img
5. disconnected my usb cable
6. press volume keys to change the START to RECOVERY MODE
7. long press power key
8. press volume down and power key at the same time until Bootloader Warning Message appear
9. and then "POWERED BY android" appear
10. my phone is now booted into STOCK RECOVERY.
Please help me guys
I really need to install Gapps

Question Rooting - anyone successful?

I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com

Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks

I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.

sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.

dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance

Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.

I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)

chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).

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.