Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?
Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?
No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)
bro how did you booted into fastboot i also in same situation
how did you fixed i also in same situation
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;
Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.
Related
I try updating via abd, Now hard brick, as it cannot update boot.img
Use Vol Down + Power to attempt to get to bootloader, it boot the Teamwin screen this reboot back Google logo then reboot back to Teamwin screen again, cannot get into trwp at all.
On the Teamwin sreen it saying wiping something, but I cannot read it quick enough.
Abd No luck as well, help please.
Can you please explain what to do now, I would greatly appreciate your help, or I going to throw it in the bin.
Edit: Managed to get into Bootloader now problem below
C:\adb>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.138s]
writing 'bootloader'...
OKAY [ 1.426s]
finished. total time: 1.570s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.016s
error: update package missing boot.img
Press any key to exit...
I check the zip file it has boot.img inside it?
Ok how to flashboot manually as I've unpack the zip what the procedure?
Ok I found flash manual.bat
Here the script:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-flo-flo-04.05.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
exit
echo Press any key to exit...
pause >nul
exit
Anyway cross fingers I rebooting now, and hope to see Android I let you in 15 minutes,
Well it won't boot into Android 6? what now?
right got it going again when back to mra58k, i found nrt 2.06 has issue which cause my problem in the first place.
I did a CM nightly Update, which relocked my phone. I tried to unlock it but something went wrong. I can flash partitions but somehow can't boot into anything besides fastboot. When I try to boot into any recovery (even Stock) the phone just restarts after showing the Oppo logo for a moment. (Just as if I was trying to boot a custom rom from a locked device)
OEM-Info:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Booting a recovery.img (Same reaction for every recovery):
Code:
fastboot boot twrp-2.8.7.2-find7.img
downloading 'boot.img'...
OKAY [ 0.355s]
booting...
OKAY [ 0.013s]
finished. total time: 0.368s
Phone Just reboots into a boot loop.
Flashing anything works fine but I'm getting boot loops again.
A strange thing that happens is that if i try
Code:
fastboot oem lock
the process just get's stuck showing three dots. (Same on Windows and Linux) That probably means that the bootloader is in some buggy way half way locked. (That sadly doesn't explains why the stock recovery won't work)
No idea how to fix it. Thank you in advance!
Jakob
Amazing tool here: forum.xda-developers.com/find-7/development/recovery-recovery-installer-7-t2819794
Hey !! I solved the pblm!!! what I did was just hit and trial but it worked. Now I will give the method:
Follow these steps and see if u are lucky enough!
step1: go to fastboot mod in your oppo f1
step2: flash stock recovery using adb. Type in "fastboot flash recovery stock.img"
step3: do not reboot your device and type in "fastboot flashing lock_critical".
step4: type in "fastboot reboot"
After these 4 steps I was able to boot back in Project spectrum. I haven't checked until that if I m able to go to recovery mode but I will update once I check. Check if you can boot.
Note: keep the stock.img file in the same folder in which you have your adb installed.
And I am not sure if this will work for you also.. but it is safe so go give a try!!!
THIS WORKED FOR OPPO F1f YOU CAN TRY YOUR LUCK BY USING THIS METHOD
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Blasmuskant said:
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
Doesn't sound so bad. And of you had searched the forum before panic posting, you would have easily found at least 3 similar threads already started.
Not knowing what you had wiped from twrp before, leaves the best option for you is to flash the factory fastboot ROM, and then start over.
There is a thread here about fastboot ROM i beleive.
just miflash
Blasmuskant said:
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from here or here..
then download latest platform tools.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Thank you for your fast answers! I tried already the search function but it seemed to me beeing different problems!
wsdyleon said:
just miflash
Click to expand...
Click to collapse
How can I do it in fastboot mode with Linux?
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from ...
then download ...
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Blasmuskant said:
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Click to expand...
Click to collapse
Was your phone connected in fastboot?
the_weird_aquarian said:
Was your phone connected in fastboot?
Click to expand...
Click to collapse
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Is it working now? Why don't you try flashing the stock firmware again?
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Download the latest platform tools and try again once
It works!
[email protected] said:
Is it working now? Why don't you try flashing the stock firmware again?
Click to expand...
Click to collapse
It worked, I installed the Stock recovery and then TWRP (all with fastboot) and so it was possible for me to install LineageOS!
Thank you very much for your support!
Hi, Possibly noob question here...
I have successfully unlocked the bootloader on my redmi 9T and downloaded the corresponding twrp, it flashed successfully and returned the output
Sending 'recovery' (65536 KB) OKAY [ 1.985s]
Writing 'recovery' OKAY [ 0.258s]
Finished. Total time: 2.261s
however, I got stuck on fastboot mode, tried "fastboot reboot" command as well as using hardware keys but it boots into fastboot mode again
how can I get out of the fastboot mode or at least recover the phone to the factory state
MukbanianiDavit said:
Hi, Possibly noob question here...
I have successfully unlocked the bootloader on my redmi 9T and downloaded the corresponding twrp, it flashed successfully and returned the output
Sending 'recovery' (65536 KB) OKAY [ 1.985s]
Writing 'recovery' OKAY [ 0.258s]
Finished. Total time: 2.261s
however, I got stuck on fastboot mode, tried "fastboot reboot" command as well as using hardware keys but it boots into fastboot mode again
how can I get out of the fastboot mode or at least recover the phone to the factory state
Click to expand...
Click to collapse
Hey bud, did you try to format data?
oscarmaldonado said:
Hey bud, did you try to format data?
Click to expand...
Click to collapse
do you mean using "fastboot erase data" command? because I cannot boot into the system or recovery
MukbanianiDavit said:
do you mean using "fastboot erase data" command? because I cannot boot into the system or recovery
Click to expand...
Click to collapse
Oh shoot, how about bootloader, can you boot into it? This particular one by pressing power and vol down until you see this screen.
oscarmaldonado said:
Oh shoot, how about bootloader, can you boot into it? This particular one by pressing power and vol down until you see this screen.
Click to expand...
Click to collapse
turns out I have flashed the wrong TWRP image that caused the loop so I had to flash stock ROM to be able to use my phone. Thanks for your time ❤
I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back
Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.
Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz
Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.