Hello, I'm a new user here. Lately I've been trying to root my Redmi Note 8 Pro. Following the standard procedure, I unlocked bootloader in the first place. Then, I downloaded usb and adb/fastboot drivers, searched for a twrp image compatible with my device and placed it in the adb folder. My problem is that after flashing the recovery, my phone sometimes goes into a bootloop, sometimes just boots normally and won't let me get in recovery. What am I doing wrong? I tried everything to make it work, even different versions of twrp and orangefox. Thanks :3 (if you need further information I'll kindly provide it to you).
read the instructions
https://twrp.me/xiaomi/xiaomiredminote8pro.html
aIecxs said:
read the instructions
https://twrp.me/xiaomi/xiaomiredminote8pro.html
Click to expand...
Click to collapse
Thanks for the response. I tried disabling avb before flashing twrp, but still, there's no way I'm booting into recovery after the device reboots. I also tried to temporarily boot twrp but it shows me an error:
Sending 'boot.img' (29152 KB) OKAY [ 0.641s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
fastboot boot can't work for SAR that's expected. flash TWRP recovery + vbmeta again, then press and keep holding Vol+ up button, type fastboot reboot, once you see TWRP release Vol button, swipe to allow modifications
aIecxs said:
fastboot boot can't work for SAR that's expected. flash TWRP recovery + vbmeta again, then press and keep holding Vol+ up button, type fastboot reboot, once you see TWRP release Vol button, swipe to allow modifications
Click to expand...
Click to collapse
Nothing seem to work. Holding the vol button just makes my phone bootloop. I really don't know what I'm doing wrong.
if the flashed custom recovery just bootloops then try another recovery
I believe there is a typo at TWRP page, try (reboot with holding Volume Up)
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash recovery twrp-3.7.0_9-0-begonia.img
fastboot reboot
Related
Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
timandjulz said:
Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
Click to expand...
Click to collapse
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Bricked!
TheYoz said:
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Click to expand...
Click to collapse
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
timandjulz2 said:
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
Click to expand...
Click to collapse
No bootloader menu at all now ?
flumpster said:
No bootloader menu at all now ?
Click to expand...
Click to collapse
Nope. Based on what I have read, it is now thoroughly bricked.
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!
Hi guys, I'm trying to install a custom rom on my G power 2021 and Im at the step where I need to install TWRP but version 3.2 doesn't support touch for me and I don't know where to look to find a newer version, now I'm stuck in a bootloop :/
Thanks !
If you are installing a GSI (generic system image) you can use fastbootd for now until someone gets touch working Hold down the power and volume down button till you get into the bootloader it should show basic information about the phone then type "fastboot reboot fastboot" then should boot into fastbootd usually when flashing a system gsi image from stock rom it would say "
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed"
then type "fastboot delete-logical-partition product_a"
these commands won't work if not booted into fastbootd
This requires Motorola's USB drivers it's good to have the stock firmware downloaded before continuing just in case, backup anything important before doing anything I am not responsible for anything that goes wrong I've used these steps on my RETCA never had a problem.
Forgot one thing DO NOT SWITCH TO SLOT B as it will not boot.
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Ok, small update - in hope to help others...
I went ahead and used 'XiaoMiTool V2'to see if it might help to load a different ROM. When starting the app, I choose the 'Bricked' device option, even it wasnt bricked. I choose the Global ROM 12. (The phone showed up as unknown and I didnt sign in with the Mi Account).
After the new ROM was on it, phone started normally and went through the setup. Had to re-enable Developer Options, USB Debugging, but even so it still didnt work - installing the TWRP just kept bringing me back to Fastboot.
However, the TWRP from this page did work: https://twrp.me/xiaomi/xiaomi-mi439.html
I also took no chances and held the Volume up button pressed and with the Command window open and 'fastboot reboot'typed out, hit the Enter key at the same time as pressing the Power button on the phone.
Worked for me!
Try to install PitchBlack Recovery it's very compable PBRP-pine-3.1.0 _OFFICIAL
Timesnaps said:
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Click to expand...
Click to collapse
You are trying to install onclite (Redmi 7) recovery on pine (Redmi 7A) ???
mi439 TWRP works for me as well & even successfully flash the rom/gapps. but when it comes to rooting with Magisk, i failed to flash nor install it properly. hope someone/somebody would make a tutorial for flashing/installing Magisk.