System has been destroyed


G

ghostmode

Members
Nov 17, 2018
32
20
Redmi 6 Pro Sakura
I had unlocked bootloader Twrp 3.2.2 and xiaomi.eu 10.0 stable

I successfully updatet twrp to 3.3.0 and tried install xiaomi.eu 10.3 stable (pie)

RESULT: system has been destroyed !

fastboot was working but win7 not recognized device

I managed to run eld mode (vol + and - and plug pc cable)
I run miflash and flashed rom from screen



I took endless time...
after restar system is still destroyed,
I can run fastboot and edl

Fastboot now recognize device, bot cant flash recovery. Error device is locked now :(
Miflash by fastboot also returns error that device mismatch.

I flash again edl mode, but again it take 1000second and progeressing endless like before.

Please help ! ! !



24361
 
ghostmode said:
Maybe i can try miflash official china? stable or developer ? latest miui 10 or old 9 ?
Click to expand...

I don't think you can use miflash as long as the bootloader is locked.

You should only flash the same ROM type as your device - China or Global.

Stable or developer is not so important I think.
No old version I would think - Sakura has ARB.
 
In your first post you show miflash trying to flash a "india_global" ROM? "sakura_india".

I read somewhere that Xiaomi has started making special Roms for the Indian market.

You should probably only try to flash the same sort of ROM that was on your phone when it was new, but the latest version because of ARB.
 
E:\Redmi6Pro kopia>fastboot devices
4b908a5a9905 fastboot

E:\Redmi6Pro kopia>fastboot getvar anti
< waiting for device >
anti:
finished. total time: 0.004s

Looks like antirollback is OFF, but still locked bootloader


Tried to install china

by fastboot miflash but returns error
[20:58:55]:1 4b908a5a9905 0,5150294s [20:58:55 4b908a5a9905]:error:"error : Missmatching image and device"
[22:00:31]:1 4b908a5a9905 1,0210584s [22:00:31 4b908a5a9905]:error:FAILED (remote: device is locked. Cannot erase)

by EDL miflash but it is not progressing, full log:

[22:02:48 4b908a5a]:MiFlash 2018.5.28.0
[22:02:48 4b908a5a]:Thread id:8 Thread name:4b908a5a
[22:02:48 4b908a5a]:image path:C:\sakura_images_8.9.6_20180906.0000.00_8.1_cn
[22:02:48 4b908a5a]:env android path:"E:\Redmi6Pro kopia\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android"
[22:02:48 4b908a5a]:script :C:\sakura_images_8.9.6_20180906.0000.00_8.1_cn\flash_all.bat
[22:02:48 4b908a5a]:physical Memory Usage:1339392 Byte
[22:02:48 4b908a5a]:start process id 6792 name cmd
[22:02:48 4b908a5a]:info:$fastboot -s 4b908a5a getvar product 2>&1 | findstr /r /c:"^product: *sakura" ||
 
Sorry, I can't help you more, have no more ideas, time to go to sleep here.

Hopefully someone who knows Sakura can help you.
 
Tried to miflash in fastboot mode
china dev
[23:31:09]:1 4b908a5a9905 0,7900451s [23:31:08 4b908a5a9905]:error:FAILED (remote: device is locked. Cannot erase)
india global stable
[23:31:45]:1 4b908a5a9905 0,3100177s [23:31:45 4b908a5a9905]:error:"error : Missmatching image and device"
china stable
[23:32:19]:1 4b908a5a9905 0,8450483s [23:32:18 4b908a5a9905]:error:FAILED (remote: device is locked. Cannot erase)


Log for fastboot (mitu picture) flash:
[23:32:18 4b908a5a9905]:MiFlash 2018.5.28.0 [23:32:18 4b908a5a9905]:Thread id:5 Thread name:4b908a5a9905 [23:32:18 4b908a5a9905]:image path:C:\sakura_images_V10.0.2.0.ODICNFH_20180903.0000.00_8.1_cn [23:32:18 4b908a5a9905]:env android path:"E:\Redmi6Pro kopia\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android" [23:32:18 4b908a5a9905]:script :C:\sakura_images_V10.0.2.0.ODICNFH_20180903.0000.00_8.1_cn\flash_all.bat [23:32:18 4b908a5a9905]:Physical Memory Usage:126976 Byte [23:32:18 4b908a5a9905]:start process id 1924 name cmd [23:32:18 4b908a5a9905]:info:$fastboot -s 4b908a5a9905 getvar product 2>&1 | findstr /r /c:"^product: *sakura" || [23:32:18 4b908a5a9905]:info:product: sakura [23:32:18 4b908a5a9905]:info:$set CURRENT_ANTI_VER=2 [23:32:18 4b908a5a9905]:info:$for /F "tokens=2 delims=: " %i in ('fastboot -s 4b908a5a9905 getvar rollback_ver 2>&1 | findstr /r /c:"rollback_ver:"') do (set version=%i ) [23:32:18 4b908a5a9905]:info:$(set version=2 ) [23:32:18 4b908a5a9905]:info:$if [2] EQU [] set version=0 [23:32:18 4b908a5a9905]:info:$if 2 GTR 2 ( [23:32:18 4b908a5a9905]:info: [23:32:18 4b908a5a9905]:info: exit /B 1 [23:32:18 4b908a5a9905]:info:) [23:32:18 4b908a5a9905]:info:$if 2 EQU 2 (fastboot -s 4b908a5a9905 flash antirbpass C:\sakura_images_V10.0.2.0.ODICNFH_20180903.0000.00_8.1_cn\images\rbv.img || ) [23:32:18 4b908a5a9905]:err:target reported max download size of 534773760 bytes [23:32:18 4b908a5a9905]:err:sending 'antirbpass' (0 KB)... [23:32:18 4b908a5a9905]:info:$fastboot -s 4b908a5a9905 erase boot || [23:32:18 4b908a5a9905]:err:OKAY [ 0.030s] [23:32:18 4b908a5a9905]:err:writing 'antirbpass'... [23:32:18 4b908a5a9905]:err:OKAY [ 0.010s] [23:32:18 4b908a5a9905]:err:finished. total time: 0.040s [23:32:18 4b908a5a9905]:err:erasing 'boot'... [23:32:18 4b908a5a9905]:err:FAILED (remote: device is locked. Cannot erase) [23:32:18 4b908a5a9905]:err:finished. total time: 0.010s [23:32:18 4b908a5a9905]:info:"Erase boot error" [23:32:18 4b908a5a9905]:error:FAILED (remote: device is locked. Cannot erase) [23:32:18 4b908a5a9905]:process exit. [23:32:19 4b908a5a9905]:flashSuccess False [23:32:19 4b908a5a9905]:isFactory False CheckCPUID False [23:32:19 4b908a5a9905]:before:flashSuccess is False set IsUpdate:True set IsDone True [23:32:19 4b908a5a9905]:after:flashSuccess is False set IsUpdate:false set IsDone true



log for i suspect EDL (black screen, vol + and - and device is seen by desktop)

[23:33:40 4b908a5a]:MiFlash 2018.5.28.0 [23:33:40 4b908a5a]:Thread id:19 Thread name:4b908a5a [23:33:40 4b908a5a]:image path:C:\sakura_images_V10.0.2.0.ODICNFH_20180903.0000.00_8.1_cn [23:33:40 4b908a5a]:env android path:"E:\Redmi6Pro kopia\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android" [23:33:40 4b908a5a]:script :C:\sakura_images_V10.0.2.0.ODICNFH_20180903.0000.00_8.1_cn\flash_all.bat [23:33:40 4b908a5a]:Physical Memory Usage:143360 Byte [23:33:40 4b908a5a]:start process id 6628 name cmd [23:33:40 4b908a5a]:info:$fastboot -s 4b908a5a getvar product 2>&1 | findstr /r /c:"^product: *sakura" ||
 
drherdman said:
It walks you through it, it might work for you.
Click to expand...
This tool is working with ADB instruction. You need USB debug active on the phone.
Few people stay with it activated for long time.
Anyway it can be tested.
Unlocking the bootloader may be a way to go...
 
ghostmode said:
Redmi 6 Pro Sakura
I had unlocked bootloader Twrp 3.2.2 and xiaomi.eu 10.0 stable

I successfully updatet twrp to 3.3.0 and tried install xiaomi.eu 10.3 stable (pie)

RESULT: system has been destroyed !

fastboot was working but win7 not recognized device

I managed to run eld mode (vol + and - and plug pc cable)
I run miflash and flashed rom from screen



I took endless time...
after restar system is still destroyed,
I can run fastboot and edl

Fastboot now recognize device, bot cant flash recovery. Error device is locked now :(
Miflash by fastboot also returns error that device mismatch.

I flash again edl mode, but again it take 1000second and progeressing endless like before.

Please help ! ! !



View attachment 24361
Click to expand...
Go to cmd
Copy this into cmd : cd C:\adb
After that, connect you're phone in computer (fastboot mode) and try this: fastboot oem unlock
After that, I hope than unlock you're bootloader (I don't say if it work...)
 
ghostmode said:
Redmi 6 Pro Sakura
I had unlocked bootloader Twrp 3.2.2 and xiaomi.eu 10.0 stable

I successfully updatet twrp to 3.3.0 and tried install xiaomi.eu 10.3 stable (pie)

RESULT: system has been destroyed !

fastboot was working but win7 not recognized device

I managed to run eld mode (vol + and - and plug pc cable)
I run miflash and flashed rom from screen



I took endless time...
after restar system is still destroyed,
I can run fastboot and edl

Fastboot now recognize device, bot cant flash recovery. Error device is locked now :(
Miflash by fastboot also returns error that device mismatch.

I flash again edl mode, but again it take 1000second and progeressing endless like before.

Please help ! ! !



View attachment 24361
Click to expand...
Try this:
1-Open CMD
2-Copy that : cd C:\adb
3-Write that : fastboot oem unlock
4-I hope than unlock you're bootloader.
(I don't say if it work....)
 
I have the same problem. It turns out that when I used MiFlash, I forgot to mark only the first item, and I checked the option to lock the bootloader after installing a ROM, I will try to download the Chinese ROM (origin of my device) ie it is not the global version, and install the Chinese version by MiFlash. As soon as I have a comeback I post here. I believe it will be the only solution. Until you get the global version of it. And apparently, I will have to request a new bootloader unlock next to xiaomi. I'm using a K20 PRO.
 
You must log in or register to reply here.

Similar threads

R
The system has been destroyed
Replies
2
Views
4K
Questions & Answers
reptkeu
R
N
"The system has been destroyed" message shown on my Redmi 8
Replies
0
Views
1K
Redmi 8 / 8A
nikiforos8
N
I
Help Needed: Mi 11T Pro NVData Corruption and IMEI Loss – Tried All Standard Fixes
Replies
0
Views
379
Mi General
ImX0990
I
V
Xiaomi mi 10t pro "the system has been destroyed" (Data loss is not an option!) [closed]
Replies
2
Views
8K
Questions & Answers
Regis H
R
D
New Poco f3 system has been destroyed
Replies
0
Views
4K
Bugs
Decesarobd
D
Top Bottom
Back