Redmi 6 Pro sakura
miałem działające twrp 3.2.2 + xiaomi.eu 10.0 stable
zachciało się aktualizacji
wgrałem z sukcesem twrp 3.3.0 uruchomiło się i zrobiłem instalację xiaomi.eu 10.3 (pie)
Po restarcie bootloader zablokowany, recovery nie wstaje, i komunikat SYSTEM HAS BEEN DESTROYED.
-------
getvar anti nic nie pokazało - więc chyba nie ma antirollbacka
Fastboot widzi urządzenie.
Próbowałem zrobić MiUnlock - ale dobija do 100% i sypie komunikatem Can't unlock bez żadnych dodatkowych informacji
Miflash przez fastboot:
fastboot 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)
Pełny log z próby:
[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
przytrzymałem vol + i - podpinając w tym momencie kabel do kompa,
uruchomił się w dziwnym trybie, bo ekran czarny ale miflash zauwazył urządzenie (być może to EDL)
w moim komputerze pokazało sie chyba jako quallcom diagnostic
jednak wisi w nieskończonosć podczas mi flash 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]hysical 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" ||
Tryb "czarny" i fastboot różnia się końcówką identyfikatora w logu mi flash.
@Acid
Da radę to ogarnąć w domu?
Wysłać do mi center?
czy cegła i tylko do kosza?