QHC0216226001093 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (28738 KB)...
OKAY [ 0.617s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.189s
target reported max download size of 471859200 bytes
sending 'cust' (16381 KB)...
OKAY [ 0.350s]
writing 'cust'...
FAILED (remote: sparse flash write failure)
finished. total time: 0.379s
target reported max download size of 471859200 bytes
sending 'recovery' (43578 KB)...
OKAY [ 0.934s]
writing 'recovery'...
OKAY [ 0.865s]
finished. total time: 1.803s
target reported max download size of 471859200 bytes
sending sparse 'system' (452422 KB)...
OKAY [ 10.092s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.143s
i'm totally stuck.
my phone is c432
I was on twisted rom b386, update to noguat b521 succesfully completed but after reboot i got bootloop. Tried everything and nothing works. Phone won't boot any version anymore. also i cannot install twrp 4.1 again. I can install just stock recovery. When i flash twrp i get stucked on "your device is now booting". Tried to flash through dload doesn't work either.
any suggestion is apreciated.
thx
Flash stock nougat revovery. Download C185B320. Extract update.app into the dload folder of your sdcard. And do the dload update. Try it and let us know.
looks like huawei removed from his website.
is there some mirror?
found
https://drive.google.com/file/d/0BxOdJKPsTEZZZk4ybFdHUXNNd1E/view
software installation failed! Incompatibility with current version. Please download the correct update package.
tried to extract files to debrick with italian knife and i got a partition error. is there a way to redo partitions?
Try rollback package.http://forum.xda-developers.com/mat...-to-downgrade-mate-8-emui-5-to-t3515202/page1
ok, i was able to rollback just with the asian one. now i'm trying to download stock asian firmware and i'll try to flash. i hope this works because i wasted 1 day and half to get it fixed..
it's weird that i was able to rollback just with c900
no luck. it doesn't boot. stuck on huawei logo.
ok, wiping system and cache did the trick.
thanks everyone
Icchan said:
ok, wiping system and cache did the trick.
thanks everyone
Click to expand...
Click to collapse
did you wipe in twrp? and what did you do next?
wisepy112 said:
did you wipe in twrp? and what did you do next?
Click to expand...
Click to collapse
Can you reply please i have the same problem.
please aswered i have the excacy same problem
feplau said:
please aswered i have the excacy same problem
Click to expand...
Click to collapse
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Related
Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.
Same here unfortunately
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.
Try to flash again TWRP and boot to recovery.
By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands
As I said, can you boot to TWRP?
Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See
hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>
Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot
Do not enter recovery, still on black screen, can tell me which software I can flash it
I already told you like three times.. try both TWRP and stock recovery..
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.
479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.
Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?
If I have the sd, and inside the Dload folder, update.app, but it does nothing.
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom
Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed:
What about friends, it happens that I wanted to install TWRP to my OP6T, but it did not go well ... I followed the steps and when I gave "Reboot Recovery", I entered the fastboot mode, and it did not happen there, it did not allow me to flash the rom, the stock recovery, or the TWRP, tells me the following ...
This happens when wanting to boot the twrp.img:
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
PS C:\Users\vhr07\Desktop>
--------------------------------------------------------------------------------------------
This happens when you want to install the recovery stock:
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.518s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.536s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
I install the recovery by means of "boot" and it says OK, but when wanting to boot I get error:
PS C:\Users\vhr07\Desktop> fastboot flash boot recovery.img
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.518s]
writing 'boot'...
OKAY [ 0.271s]
finished. total time: 1.794s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.506s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.547s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
These were my last attempts ...:
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (30948 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.734s
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.508s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.525s
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16849 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.406s
PS C:\Users\vhr07\Desktop> fastboot flash recovery_b recovery.img
target reported max download size of 536870912 bytes
sending 'recovery_b' (65536 KB)...
OKAY [ 1.523s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 1.538s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b recovery.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.517s]
writing 'boot_b'...
OKAY [ 0.301s]
finished. total time: 1.824s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.511s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.549s
PS C:\Users\vhr07\Desktop> fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (30948 KB)...
OKAY [ 0.714s]
writing 'boot'...
OKAY [ 0.154s]
finished. total time: 0.874s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30948 KB)...
OKAY [ 0.717s]
writing 'boot_b'...
OKAY [ 0.181s]
finished. total time: 0.904s
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
----------------------------------------------------------------------------
Please, I need your help I promise not to ROOT again the hahaha team
I would pay if necessary
PD: already tried with bootloader unlocked and blocked
UPDATE: MSMTools, stuck on "PARAM PREPROCESSING"
https://imgur.com/qiaF8oh
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
foobar66 said:
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
Click to expand...
Click to collapse
Same situation
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.500s]
writing 'boot_a'...
OKAY [ 0.308s]
finished. total time: 1.814s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.498s]
writing 'boot_b'...
OKAY [ 0.345s]
finished. total time: 1.849s
PS C:\Users\vhr07\Desktop> fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.505s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.537s
PS C:\Users\vhr07\Desktop>
Seem look like usb debug not authorize pc
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
efebe said:
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
Click to expand...
Click to collapse
MSMTools stuck on this
https://imgur.com/qiaF8oh
Vlodayax said:
MSMTools stuck on this
https://imgur.com/qiaF8oh
Click to expand...
Click to collapse
Click "stop" then "exit" and kill the program and start over. Keep trying. I was down a whole day and a half after trying to flash a Rom. I made it worst after wiping the system and the MSM tool saved my a$$.
Sent from my OnePlus6T using XDA Labs
So I was trying to rollback to stock rom from Pixel Experience since it was still buggy and not complete imo. So I tried flashing the stock Indian rom ( miui_DAVINCIININGlobal_V10.3.8.0.PFJINXM_207eaee662_9.0 ). But was stuck on boot screen. Although I could start fastboot mode. So I installed TWRP again & thought it must be a firmware issue & tried installing firmware from this post from Indian archive ( https://forum.xda-developers.com/mi-9t/development/firmware-xiaomi-mi-9t-redmi-k20-t3955314 ). But now I'm still stuck and cant possibly install twrp back. I tried flashing all the image files from the .tgz file as it had soled my earlier similar issue i had while installing twrp. But now while flashing dummy.img, dummy_devinfo.img, dummy_fsc.img, dummy_modemst.img, system.img & persist.img it shows an error in cmd. Which previously flashed successfully. And now I'm stuck with just the fastboot screen without any recovery. I also tried using MiFlash Tool but it ends up on Antirollback Check error although I have installed it in C:\MiFlash.
It'd be great if someone would help me out from here. TIA!
EDIT-
SOLVED!
Flash TWRP after manually flashing the files. To install persist incase you get an error like me saying persist is write protected/Unable to mount persist, try flashing persist.img from twrp in "Install Image". Might have to flash the rom again after that (I had to for some reason). Works fine then.
L:\K20 root\New folder (3)>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (131072 KB)...
OKAY [ 2.835s]
writing 'boot'...
OKAY [ 0.657s]
finished. total time: 3.492s
L:\K20 root\New folder (3)>fastboot flash cache cache.img
target reported max download size of 805306368 bytes
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (128 KB)...
OKAY [ 0.015s]
writing 'cache'...
OKAY [ -0.000s]
finished. total time: 0.031s
L:\K20 root\New folder (3)>fastboot flash cust cust.img
target reported max download size of 805306368 bytes
sending 'cust' (213156 KB)...
OKAY [ 4.618s]
writing 'cust'...
OKAY [ 0.000s]
finished. total time: 4.618s
L:\K20 root\New folder (3)>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (32768 KB)...
OKAY [ 0.704s]
writing 'dtbo'...
OKAY [ 0.157s]
finished. total time: 0.861s
L:\K20 root\New folder (3)>fastboot flash dummy dummy.img
target reported max download size of 805306368 bytes
sending 'dummy' (8 KB)...
OKAY [ 0.000s]
writing 'dummy'...
FAILED (remote: (dummy) No such partition)
finished. total time: 0.000s
L:\K20 root\New folder (3)>fastboot flash dummy_devinf dummy_devinfo.img
target reported max download size of 805306368 bytes
sending 'dummy_devinf' (4 KB)...
OKAY [ 0.016s]
writing 'dummy_devinf'...
FAILED (remote: (dummy_devinf) No such partition)
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash dummy_fsc dummy_fsc.img
target reported max download size of 805306368 bytes
sending 'dummy_fsc' (4 KB)...
OKAY [ 0.016s]
writing 'dummy_fsc'...
FAILED (remote: (dummy_fsc) No such partition)
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash dummy_modemst dummy_modemst.img
target reported max download size of 805306368 bytes
sending 'dummy_modemst' (8192 KB)...
OKAY [ 0.188s]
writing 'dummy_modemst'...
FAILED (remote: (dummy_modemst) No such partition)
finished. total time: 0.188s
L:\K20 root\New folder (3)>fastboot flash logo logo.img
target reported max download size of 805306368 bytes
sending 'logo' (26980 KB)...
OKAY [ 0.588s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.733s
L:\K20 root\New folder (3)>fastboot flash misc misc.img
target reported max download size of 805306368 bytes
sending 'misc' (4096 KB)...
OKAY [ 0.094s]
writing 'misc'...
OKAY [ 0.031s]
finished. total time: 0.125s
L:\K20 root\New folder (3)>fastboot flash persist persist.img
target reported max download size of 805306368 bytes
sending 'persist' (65536 KB)...
OKAY [ 1.406s]
writing 'persist'...
FAILED (remote: Partition is write protected)
finished. total time: 1.421s
L:\K20 root\New folder (3)>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.421s]
writing 'recovery'...
OKAY [ 0.336s]
finished. total time: 1.757s
L:\K20 root\New folder (3)>fastboot flash system system.img
error: cannot load 'system.img'
L:\K20 root\New folder (3)>fastboot flash userdata userdata.img
target reported max download size of 805306368 bytes
sending 'userdata' (198244 KB)...
OKAY [ 4.278s]
writing 'userdata'...
OKAY [ 0.000s]
finished. total time: 4.278s
L:\K20 root\New folder (3)>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.016s]
writing 'vbmeta'...
OKAY [ 0.000s]
finished. total time: 0.016s
L:\K20 root\New folder (3)>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
sending sparse 'vendor' (786428 KB)...
OKAY [ 18.024s]
writing 'vendor'...
OKAY [ -0.000s]
sending sparse 'vendor' (558016 KB)...
OKAY [ 13.004s]
writing 'vendor'...
OKAY [ -0.000s]
finished. total time: 31.043s
There is probably problem with the official ROM. I have managed to get to the same situation with EU version. I have tried some beta and end up with barely working twrp. Sideload didn't work etc.
So I bought USB-C flash disk and instaled custom ROM LineageOS and everything is working fine so far.
Non of the official ROM have worked, so for some time I will have to function LineageOS and wait for some properly working recovery and ROM...
Reep1324 said:
There is probably problem with the official ROM. I have managed to get to the same situation with EU version. I have tried some beta and end up with barely working twrp. Sideload didn't work etc.
So I bought USB-C flash disk and instaled custom ROM LineageOS and everything is working fine so far.
Non of the official ROM have worked, so for some time I will have to function LineageOS and wait for some properly working recovery and ROM...
Click to expand...
Click to collapse
Do u get an error saying "Failed to mount '/persist' (Invalid Argument)?
No. Everything looks ok, but then I got Bootloop or it goes straight to Recovery. Using the russian and greek one. Oficial ROM, EU rom and Lineage. Nothing works now...
Have you tried flashing magisk? Had the same problem where I couldn't launch official rom (I was coming back from xiaomi.eu). Flashing magisk in TWRP resolved the problem. You can OTA after that to get back to stock rom (as without TWRP or magisk).
nega_tive said:
So I was trying to rollback to stock rom from Pixel Experience since it was still buggy and not complete imo. So I tried flashing the stock Indian rom ( miui_DAVINCIININGlobal_V10.3.8.0.PFJINXM_207eaee662_9.0 ). But was stuck on boot screen. Although I could start fastboot mode. So I installed TWRP again & thought it must be a firmware issue & tried installing firmware from this post from Indian archive ( https://forum.xda-developers.com/mi-9t/development/firmware-xiaomi-mi-9t-redmi-k20-t3955314 ). But now I'm still stuck and cant possibly install twrp back. I tried flashing all the image files from the .tgz file as it had soled my earlier similar issue i had while installing twrp. But now while flashing dummy.img, dummy_devinfo.img, dummy_fsc.img, dummy_modemst.img, system.img & persist.img it shows an error in cmd. Which previously flashed successfully. And now I'm stuck with just the fastboot screen without any recovery. I also tried using MiFlash Tool but it ends up on Antirollback Check error although I have installed it in C:\MiFlash.
It'd be great if someone would help me out from here. TIA!
EDIT-
SOLVED!
Flash TWRP after manually flashing the files. To install persist incase you get an error like me saying persist is write protected/Unable to mount persist, try flashing persist.img from twrp in "Install Image". Might have to flash the rom again after that (I had to for some reason). Works fine then.
Click to expand...
Click to collapse
Hi,
I cant boot in to stock Indian ROM. But, i was able to flash 10.3.9 global.I have tried ll methods. flash tool, recovery nothing works. Everytime i do something it will break on to bootloop, cant get the stock indian ROM back. Always come back to global stable.
Matthas said:
Have you tried flashing magisk? Had the same problem where I couldn't launch official rom (I was coming back from xiaomi.eu). Flashing magisk in TWRP resolved the problem. You can OTA after that to get back to stock rom (as without TWRP or magisk).
Click to expand...
Click to collapse
It's already solved. And yes, I have tried all combinations possible.
In the end I have decompressed .tgz file (6,5GB) and flash it thru 2017 version of MiFlasher.
This phone have probably softbrick or hardbrick and bootloop and intro to recovery (no erecovery) gets a rescue mode screen
I have tried with the "potatonv" tool and trying to flash a stock rom and a custom recovery but none work and I have the bootloader unlocked but I get these following results:
>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 471859200 bytes
sending 'RECOVERY' (36118 KB)...
OKAY [ 0.986s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 1.012s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (36118 KB)...
OKAY [ 1.000s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.468s