Database Users

I think I have bricked it :(

Hello guys,
I think I bricked my nexus 10 while trying to factory restock.
Here's what I did/tried:
Downloaded mantaray-jop40c-factory-0d641789.tgz and ran ./flash-all.sh
Code:
erasing 'boot'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'system'...
OKAY [ 0.041s]
finished. total time: 0.041s
erasing 'userdata'...
OKAY [ 0.224s]
finished. total time: 0.224s
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.119s]
finished. total time: 0.281s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB02ZYQT
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4606 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.128s]
sending 'recovery' (5106 KB)...
OKAY [ 0.641s]
writing 'recovery'...
OKAY [ 0.136s]
sending 'system' (528847 KB)...
OKAY [ 59.771s]
writing 'system'...
OKAY [ 14.660s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.036s]
rebooting...
finished. total time: 76.192s
Nexus rebooted into the google X, stuck there for 30 minutes ....
I read some posts, decided I needed to wipe data/factory reset, so booted in fastboot mode and launched recovery ... got the droid with the triangle but no amount of volume up + power would boot me into the stock recovery.
Then I flashed CWM recovery
Code:
fastboot flash recovery ../recovery-clockwork-touch-6.0.2.3-manta.img
and could boot into recovery .. tried to do a factory reset and got:
Code:
Error mounting /cache!
Done.
--Wiping data ...
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure
Skipping format...
Data wipe complete
and needless to say I got the same result ..... I have tried this procedure multiple times .. verified the md5 of the factory image, tried re-locking and unlocking the bootloader to no avail ... so I am stumped.
Did I in some way manage to wreck the partition table ? is it even possible ? or am I missing something much simpler?

madmatt71 said:
Hello guys,
I think I bricked my nexus 10 while trying to factory restock.
Here's what I did/tried:
Downloaded mantaray-jop40c-factory-0d641789.tgz and ran ./flash-all.sh
Code:
erasing 'boot'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'system'...
OKAY [ 0.041s]
finished. total time: 0.041s
erasing 'userdata'...
OKAY [ 0.224s]
finished. total time: 0.224s
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.119s]
finished. total time: 0.281s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB02ZYQT
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4606 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.128s]
sending 'recovery' (5106 KB)...
OKAY [ 0.641s]
writing 'recovery'...
OKAY [ 0.136s]
sending 'system' (528847 KB)...
OKAY [ 59.771s]
writing 'system'...
OKAY [ 14.660s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.036s]
rebooting...
finished. total time: 76.192s
Nexus rebooted into the google X, stuck there for 30 minutes ....
I read some posts, decided I needed to wipe data/factory reset, so booted in fastboot mode and launched recovery ... got the droid with the triangle but no amount of volume up + power would boot me into the stock recovery.
Then I flashed CWM recovery
Code:
fastboot flash recovery ../recovery-clockwork-touch-6.0.2.3-manta.img
and could boot into recovery .. tried to do a factory reset and got:
Code:
Error mounting /cache!
Done.
--Wiping data ...
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure
Skipping format...
Data wipe complete
and needless to say I got the same result ..... I have tried this procedure multiple times .. verified the md5 of the factory image, tried re-locking and unlocking the bootloader to no avail ... so I am stumped.
Did I in some way manage to wreck the partition table ? is it even possible ? or am I missing something much simpler?
Click to expand...
Click to collapse
.. and after half a day banging my head I realized I was using an old version of adb and fastboot ... downloaded the latest version from google and .... restored withouth any problem .....
sorry for the waste of bandwidth

madmatt71 said:
.. and after half a day banging my head I realized I was using an old version of adb and fastboot ... downloaded the latest version from google and .... restored withouth any problem .....
sorry for the waste of bandwidth
Click to expand...
Click to collapse
nonesense. Someone else who is having similar issues might find your answer of updating adb and fastboot incredibly useful.

EniGmA1987 said:
nonesense. Someone else who is having similar issues might find your answer of updating adb and fastboot incredibly useful.
Click to expand...
Click to collapse
Err, yes, it could be useful.
What tipped me off was an apparently unrelated post on google groups from a google developer who stated that in the latest versions of fastboot they added some features to query the devices with respect to partition types/layout in order to be able to decide whether to format or erase a partition depending on what was needed, and since it looked like my partition table was wasted I finally got on about checking which version of fastboot I was using ....

madmatt71,
Please add "[SOLVED]" to the beginning of this threads title so as to alert people to your solution. It really helps when viewing search results. Only the orginal poster can make this change. Just edit your original post.

[Q] 5.0 not booting after factory image installation to lrx21t

Hi all,
I have just done a complete factory reset...which looked ok first...
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.04
Serial Number........: 00254a42d4XXXXXX
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
mars:/tmp/google/occam-lrx21t
...but the bootlogo (flying balloons or whatever it is) stays there forever, waited 70 minutes on the first attempt, then did another factory reset ... and I am waiting again for more than 45 minutes ... what am I doing wrong? Any help is welcome.
Kind regards, mistersixt.

mistersixt said:
Hi all,
I have just done a complete factory reset...which looked ok first...
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.04
Serial Number........: 00254a42d4XXXXXX
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
mars:/tmp/google/occam-lrx21t
...but the bootlogo (flying balloons or whatever it is) stays there forever, waited 70 minutes on the first attempt, then did another factory reset ... and I am waiting again for more than 45 minutes ... what am I doing wrong? Any help is welcome.
Kind regards, mistersixt.
Click to expand...
Click to collapse
if possible, go to stock recovery or TWRP recovery and do factory data reset.
it does not work then, edit the flash-all.sh file and remove the last like which says fastboot -w update xxx...
Extract the zip file xxx... and move all the img files to current folder(flash-all.sh file folder).
add below lines
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
if you need userdata and cache add below lines
fastboot flash userdata userdata.img
fastboot flash cache cache.img
save the flash-all.sh file and try to boot now. it should boot with in 10 to 15mins.

moorthidaniel said:
if possible, go to stock recovery or TWRP recovery and do factory data reset.
it does not work then, edit the flash-all.sh file and remove the last like which says fastboot -w update xxx...
Extract the zip file xxx... and move all the img files to current folder(flash-all.sh file folder).
add below lines
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
if you need userdata and cache add below lines
fastboot flash userdata userdata.img
fastboot flash cache cache.img
save the flash-all.sh file and try to boot now. it should boot with in 10 to 15mins.
Click to expand...
Click to collapse
Tried that:
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
sending 'userdata' (98413 KB)... OKAY
writing 'userdata'... OKAY
sending 'cache' (13424 KB)... OKAY
writing 'cache'... OKAY
mars:/tmp/google/occam-lrx21t#
I have still the same thing though, the boot logo with the jumping bubbles is there for 30 minutes ...
...damn, what is wrong with it?

mistersixt said:
Tried that:
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
sending 'userdata' (98413 KB)... OKAY
writing 'userdata'... OKAY
sending 'cache' (13424 KB)... OKAY
writing 'cache'... OKAY
mars:/tmp/google/occam-lrx21t#
I have still the same thing though, the boot logo with the jumping bubbles is there for 30 minutes ...
...damn, what is wrong with it?
Click to expand...
Click to collapse
It happened to me as well. After doing this way, i tried again factory data reset which worked for me.

I'm stuck with the bootloop over one hour now. Tried locking the bootloader, but didn't work. Is factory reset the only solution? Hate to lose the data...

mj56gt said:
I'm stuck with the bootloop over one hour now. Tried locking the bootloader, but didn't work. Is factory reset the only solution? Hate to lose the data...
Click to expand...
Click to collapse
Factory reset is the only solution to get out of bootloop. if you want to take backup before doing factory reset, try flashing twrp recovery and enable MTP. now take backup. Enabling lMTP does not help you, try flashing stock or any other kitkat rom and take backup and then install Lollypop.

pm_dsp_ra said:
Factory reset is the only solution to get out of bootloop. if you want to take backup before doing factory reset, try flashing twrp recovery and enable MTP. now take backup. Enabling lMTP does not help you, try flashing stock or any other kitkat rom and take backup and then install Lollypop.
Click to expand...
Click to collapse
I finally managed to get 5.0 on my Nexus-4 device by installing the latest twrp recovery and installed one of the stock stock-rom images via adb sideload.
Regards, mistersixt.

Stuck in a bootloop from restore

I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?

I would go into Heisenberg's guide which is stickied in the general section. Flash stock images and TWRP via fast boot. Read the guide in its entirety.

Random Barnics said:
I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?
Click to expand...
Click to collapse
Your phone shouldn't loop from restoring a vendor image, as long as it's the right vendor image that was backed up with the ROM. Exactly what did you backup/restore? You haven't really given enough information here.

I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.

Random Barnics said:
I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.
Click to expand...
Click to collapse
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.

Heisenberg said:
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.
Click to expand...
Click to collapse
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now

Random Barnics said:
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now
Click to expand...
Click to collapse
Alright, do what I said and only restore system, data, boot, and vendor.

Heisenberg said:
Alright, do what I said and only restore system, data, boot, and vendor.
Click to expand...
Click to collapse
As noted in the initial post, I can't do anything as neither the rom nor the recovery load,

I went with the dude's advice about flashing the rom and recovery through fastboot, and they're not working.
This is the terminal output I get when trying to flash the recovery.
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash recovery twrp-3.0.0-1-angler.imgtarget reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.246s]
finished. total time: 0.756s
It still freezes and doesn't load when I try and access it.
The following results are what I get when trying to flash a rom in fastboot
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash zip DU_angler_6.0.1_20160301-2335.v10.0-OFFICIAL.zip
target reported max download size of 494927872 bytes
sending 'zip' (432013 KB)...
OKAY [ 11.485s]
writing 'zip'...
FAILED (remote: Permission denied!)
finished. total time: 11.491s

Don't flash a ROM flash Stock Images and go from there.

dratsablive said:
Don't flash a ROM flash Stock Images and go from there.
Click to expand...
Click to collapse
Ok. Why though? Not doubting your advice. Just wondering.

Random Barnics said:
Ok. Why though? Not doubting your advice. Just wondering.
Click to expand...
Click to collapse
Because you want to get your phone to boot normally. Once you can boot to stock, you can then flash TWRP, then custom rom and then only restore the /data portion of your backup.

My mistake, I missed the part where your recovery won't boot. Flash the factory images as the other fella said, that'll get your phone booting at least. Don't restore the data portion of your backup over the stock ROM though, that'll cause major problems.
PS. You can't flash ROM zips with fastboot.

Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
OKAY [ 0.207s]
finished. total time: 0.327s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.265s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.439s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (12977 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.046s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 1.232s
[email protected]-3-11:~/Android/Sdk/platform-tools$ reboot fastboot
reboot: Need to be root
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.117s]
writing 'bootloader'...
OKAY [ 0.208s]
finished. total time: 0.325s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.328s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.502s
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 1.109s]
writing 'boot'...
OKAY [ 0.190s]
sending 'recovery' (12977 KB)...
OKAY [ 0.829s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.312s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 2.823s

Random Barnics said:
Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
*snipped
Click to expand...
Click to collapse
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks.
I'll try again when I get up, as it's almost 2.30am here.

Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly

Random Barnics said:
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly
Click to expand...
Click to collapse
Excellent, great to know

He probably restored boot system system image vendor vendor image data efs recovery......

dontbeweakvato said:
He probably restored boot system system image vendor vendor image data efs recovery......
Click to expand...
Click to collapse
Yeah we already established that.

Help p9 lite, black screen how to fix it

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.

Redmi K20/ Mi 9T Bricked?

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.