soft brick bootloop after twrp flash - Redmi Note 8 Pro Questions & Answers

Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>

liltechie said:
Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>
Click to expand...
Click to collapse
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)

Kirasu2080 said:
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)
Click to expand...
Click to collapse
Thank you. Helped solving the bootloop issue.

Related

[Q] m8 possibly corrupt hboot

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s
Try fastboot erase cache

Saving Data from locked, bricked device

Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...

fastboot erase cashe

HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
1. What/why M7 recovery for M8
fastboot flash recovery NameOfRecovery.img is correct command
https://twrp.me/htc/htconem8gsm.html
2. cache not cashe
fastboot erase cache is correct command
Kharbas said:
HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
Click to expand...
Click to collapse
Dude that's a m7 recovery
Sent from my HTC One (M8) using XDA Labs
Always check your command syntax is exactly right, when performing fastboot and adb commands.
And yeah, the proper TWRP for your phone would help.

Loop at Fastboot

case : i wanna tryin to install twrp,
log :
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (39920 KB)...
OKAY [ 1.269s]
writing 'recovery'...
OKAY [ 0.285s]
finished. total time: 1.558s
but after tryin to reboot, it always looping to fastboot, any solution?
device : redmi 7 4/64
Hi hanselfermin,
Did you eventually find a way to boot into TWRP ?

Fastboot not working

Im trying to flash a rom and get errors. I'm not sure why.
I have the most up to date adb drivers, usb debugging is on.
Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'vendor' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Sending 'boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'boot_a' OKAY [ 0.385s]
Finished. Total time: 3.219s
Sending 'dtbo' (24576 KB) OKAY [ 0.585s]
Writing 'dtbo' OKAY [ 0.085s]
Finished. Total time: 0.689s
Sending 'odm' (102400 KB) OKAY [ 2.414s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
Nvm Fixed by using FastbootD

Categories

Resources