Database Info

Moto g stuck in bootloop! Tried flashing etc!

I have tried everything possible! The phone just keeps rebooting, it will show the warning bootloader unlocked display and then goes to a lighted black screen and repeats. I managed to relock my phone but it did not help fixing the problem. I have also tried different cables because I heard it might be the cable.
I found the firmware that gives me no error which is my service provider stock firmware:
Code:
TELUS-CA_FALCON_KXB20.9-1.10-1.39_cid14_CFC_1FF.xml
When I run the flashing processor it all works fine but when I go to the phone to choose recovery it will just reboot and not go into recovery same with factory.
Code:
(bootloader) Device is already locked!
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.040s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.460s]
finished. total time: 0.500s
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.570s]
finished. total time: 1.670s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
sending 'logo' (619 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
sending 'boot' (10240 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.350s]
writing 'recovery'...
OKAY [ 1.070s]
finished. total time: 1.420s
target reported max download size of 536870912 bytes
sending 'system' (260912 KB)...
OKAY [ 8.191s]
writing 'system'...
OKAY [ 18.244s]
finished. total time: 26.445s
target reported max download size of 536870912 bytes
sending 'system' (239152 KB)...
OKAY [ 7.546s]
writing 'system'...
OKAY [ 14.515s]
finished. total time: 22.064s
target reported max download size of 536870912 bytes
sending 'system' (226897 KB)...
OKAY [ 7.161s]
writing 'system'...
OKAY [ 23.304s]
finished. total time: 30.469s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.557s]
writing 'modem'...
OKAY [ 2.380s]
finished. total time: 3.954s
erasing 'modemst1'...
OKAY [ 0.078s]
finished. total time: 0.078s
erasing 'modemst2'...
OKAY [ 0.109s]
finished. total time: 0.109s
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.114s]
writing 'fsg'...
OKAY [ 0.083s]
finished. total time: 0.198s
erasing 'cache'...
OKAY [ 0.156s]
finished. total time: 0.156s
erasing 'userdata'...
OKAY [ 0.299s]
finished. total time: 0.299s
...
(bootloader) Device is already locked!
OKAY [ 0.016s]
finished. total time: 0.016s
rebooting...
finished. total time: 0.016s
Press any key to continue . . .

[Q] how to downgrade to stock rom from cm 12 nighlies

I recently upgraded to android 5.02 using twrp and installing cm 12 nighlies and gapps . Now i want to go back to my stock rom . I downloaded cm-11.0-XNPH44S-bacon-signed-fastboot.zip . have copied it to the phone . do i need a gapps file for this build . what is the procedure to downgrade using twrp . please guide .

You best way to go back is to make a backup before you flash a new ROM, but I'm guessing you didn't do that. You don't need gapps for CM11S, they're built in. Go to my guide thread and follow the instructions in section 8 on how to flash the fastboot images.
Transmitted via Bacon

timmaaa said:
You best way to go back is to make a backup before you flash a new ROM, but I'm guessing you didn't do that. You don't need gapps for CM11S, they're built in. Go to my guide thread and follow the instructions in section 8 on how to flash the fastboot images.
Transmitted via Bacon
Click to expand...
Click to collapse
thank you so much for the reply . am almost thru but somehow stuck at the last command that installs the zip . can u please guide .
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash modem NON-
HLOS.bin
< waiting for device >
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.897s]
writing 'modem'...
OKAY [ 0.696s]
finished. total time: 2.593s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash sbl1 sbl1.
mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.030s]
finished. total time: 0.043s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash dbi sdi.mb
n
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash aboot emmc
_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.031s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash rpm rpm.mb
n
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
OKAY [ 0.013s]
finished. total time: 0.026s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.027s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash LOGO logo.
bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.324s]
writing 'LOGO'...
OKAY [ 0.135s]
finished. total time: 0.461s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash oppostanvb
k static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.340s]
writing 'oppostanvbk'...
OKAY [ 0.137s]
finished. total time: 0.478s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot update -w cm-11.
0-XNPH44S-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot update -w cm-11.
0-XNPH44S-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>

Have you tried rebooting?
Transmitted via Bacon

rustamg said:
thank you so much for the reply . am almost thru but somehow stuck at the last command that installs the zip . can u please guide .
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash modem NON-
HLOS.bin
< waiting for device >
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.897s]
writing 'modem'...
OKAY [ 0.696s]
finished. total time: 2.593s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash sbl1 sbl1.
mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.030s]
finished. total time: 0.043s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash dbi sdi.mb
n
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash aboot emmc
_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.031s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash rpm rpm.mb
n
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
OKAY [ 0.013s]
finished. total time: 0.026s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.027s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash LOGO logo.
bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.324s]
writing 'LOGO'...
OKAY [ 0.135s]
finished. total time: 0.461s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot flash oppostanvb
k static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.340s]
writing 'oppostanvbk'...
OKAY [ 0.137s]
finished. total time: 0.478s
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot update -w cm-11.
0-XNPH44S-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>fastboot update -w cm-11.
0-XNPH44S-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
C:\Users\HP\Desktop\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Hi there, i had the same problem, but guess what, you just have to wait a bit longer.
What happened to me was, the first time i click flashall.bat, i got the following error too,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
So i close it again. and try open another time. This time it's the same error, but i decided to wait. Then it works perfectly fine. Using One plus one. I upgrade to CM12 2 days ago but it sucks a lot of my battery. So i decided to revert back to cm11

Can't see a thread to revert to stock with my One Plus One. The other guide in forum is too confusing. Can some one please help me some easy links and a faster downloadable image for stock. TIA.

anshumangoyal said:
Can't see a thread to revert to stock with my One Plus One. The other guide in forum is too confusing. Can some one please help me some easy links and a faster downloadable image for stock. TIA.
Click to expand...
Click to collapse
This is the recommended link. Please read the guide carefully. Section 8 of that guide with help you.
I don't recommend you to use toolkit. If you still want to use it, use the link that I provided.

Oneplus One stuck at recovery

Hello,
I've got a OnePlus one and it's stuck in the recovery. First it was in a bootloop, i managed to fix that. If i'm flashing a rom, it will come in an endless bootloop. I've tried several tools but i managed to fix my phone. My pc does reconize the phone, but if i boot it up, it shows multiple ports or something. I can also move files over to the phone. Does anyone know how to fix my OnePlus one?
Thanks a lot!

Try it out..
The best way to resolve your problem is to return to Original Stock ROM via FASTBOOT MODE. In my opinion, firstly you must return to the stock ROM and at least turn on your phone. After that you might try out other custom ROMs.
Search for " Return your OPO to 100% Stock ROM " in google and open xda link.

er.naman said:
The best way to resolve your problem is to return to Original Stock ROM via FASTBOOT MODE. In my opinion, firstly you must return to the stock ROM and at least turn on your phone. After that you might try out other custom ROMs.
Search for " Return your OPO to 100% Stock ROM " in google and open xda link.
Click to expand...
Click to collapse
I've done it, the phone is now still booting for 10 min. I don't think it's going to work

Buddy.. DID YOU INSTALLED THE OS USING COMMAND PROMPT FROM YOUR PC??

er.naman said:
Buddy.. DID YOU INSTALLED THE OS USING COMMAND PROMPT FROM YOUR PC??
Click to expand...
Click to collapse
yes i did, i even have the results of it.
C:\adb\cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB>flash-all.bat
target reported max download size of 536870912 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.831s]
writing 'modem'...
OKAY [ 0.856s]
finished. total time: 2.757s
target reported max download size of 536870912 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.015s]
finished. total time: 0.031s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.013s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.018s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.036s
target reported max download size of 536870912 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.010s]
writing 'rpm'...
OKAY [ 0.013s]
finished. total time: 0.026s
target reported max download size of 536870912 bytes
sending 'tz' (325 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.015s]
finished. total time: 0.034s
target reported max download size of 536870912 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.017s]
finished. total time: 0.035s
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.332s]
writing 'oppostanvbk'...
OKAY [ 0.161s]
finished. total time: 0.499s
target reported max download size of 536870912 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.323s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.497s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.246s]
sending sparse 'system' (518095 KB)...
OKAY [ 23.630s]
writing 'system'...
OKAY [ 11.179s]
sending sparse 'system' (515575 KB)...
OKAY [ 23.366s]
writing 'system'...
OKAY [ 24.083s]
sending sparse 'system' (184033 KB)...
OKAY [ 8.313s]
writing 'system'...
OKAY [ 8.754s]
finished. total time: 99.603s
target reported max download size of 536870912 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.236s]
writing 'boot'...
OKAY [ 0.118s]
finished. total time: 0.361s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.035s]
sending 'cache' (10432 KB)...
OKAY [ 0.335s]
writing 'cache'...
OKAY [ 0.442s]
finished. total time: 0.820s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.882s]
sending 'userdata' (141075 KB)...
OKAY [ 4.478s]
writing 'userdata'...
OKAY [ 12.394s]
finished. total time: 18.760s
rebooting...
finished. total time: 0.006s
Press any key to exit...
I don't know why it doesn't work

Whole process seem to be fine to me. What error is popping up now??

System image using up 109GB

Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967

Pluisje89 said:
Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967
Click to expand...
Click to collapse
That only seems to add up to 4 GB. Open up a root Explorer and see what it tells you.

Bricked OnePlus 6

Hello,
several weeks ago I bricked my oneplus 6 during the approach to install lineage 16.0. I also tried to fix it, based on some articles I found, but without success.
Error - most likely I have coincidently wiped the partitions a/b...
A) So, some weeks later I want to bring it back to life. Current status following the lineage instructions:
1) unlocking bootloader
is unlocked
2) temporarily booting a customer recovery using fastboot
- sudo ./fastboot devices
977d3806 fastboot
- sudo ./fastboot flash boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
target reported max download size of 536870912 bytes
sending 'boot_a' (28728 KB)...
OKAY [ 1.076s]
writing 'boot_a'...
OKAY [ 0.115s]
finished. total time: 1.192s
Result: power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
Result: power off, volume down + power, same result
B) Alternative
- sudo ./fastboot boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
downloading 'boot.img'...
OKAY [ 1.037s]
booting...
OKAY [ 0.077s]
finished. total time: 1.114s
Result: automatic power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
C) I also tried [ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6 – also without success. Basically everything seemed to be ok but after the end I had to manually reboot it: nothing happens - only dark screen and white light close to front camera.
Flashing looked good:
target reported max download size of 536870912 bytes
sending 'aop_a' (180 KB)...
OKAY [ 0.015s]
writing 'aop_a'...
OKAY [ 0.004s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'aop_b' (180 KB)...
OKAY [ 0.014s]
writing 'aop_b'...
OKAY [ 0.007s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (748 KB)...
OKAY [ 0.030s]
writing 'bluetooth_a'...
OKAY [ 0.007s]
finished. total time: 0.037s
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (748 KB)...
OKAY [ 0.029s]
writing 'bluetooth_b'...
OKAY [ 0.010s]
finished. total time: 0.039s
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.259s]
writing 'boot_a'...
OKAY [ 0.252s]
finished. total time: 2.511s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.075s]
writing 'boot_b'...
OKAY [ 0.272s]
finished. total time: 2.347s
target reported max download size of 536870912 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 1.088s]
writing 'dsp_a'...
OKAY [ 0.143s]
finished. total time: 1.231s
target reported max download size of 536870912 bytes
sending 'dsp_b' (32768 KB)...
OKAY [ 1.178s]
writing 'dsp_b'...
OKAY [ 0.127s]
finished. total time: 1.305s
target reported max download size of 536870912 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.279s]
writing 'dtbo_a'...
OKAY [ 0.045s]
finished. total time: 0.324s
target reported max download size of 536870912 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.277s]
writing 'dtbo_b'...
OKAY [ 0.031s]
finished. total time: 0.308s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_a' (344 KB)...
OKAY [ 0.017s]
writing 'fw_4j1ed_a'...
OKAY [ 0.005s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4j1ed_b'...
OKAY [ 0.006s]
finished. total time: 0.024s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_a' (344 KB)...
OKAY [ 0.015s]
writing 'fw_4u1ea_a'...
OKAY [ 0.005s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4u1ea_b'...
OKAY [ 0.007s]
finished. total time: 0.025s
target reported max download size of 536870912 bytes
sending 'modem_a' (120916 KB)...
OKAY [ 4.347s]
writing 'modem_a'...
OKAY [ 0.598s]
finished. total time: 4.945s
target reported max download size of 536870912 bytes
sending 'modem_b' (120916 KB)...
OKAY [ 4.249s]
writing 'modem_b'...
OKAY [ 0.640s]
finished. total time: 4.889s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (952 KB)...
OKAY [ 0.037s]
writing 'oem_stanvbk'...
OKAY [ 0.009s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'qupfw_a' (64 KB)...
OKAY [ 0.011s]
writing 'qupfw_a'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'qupfw_b' (64 KB)...
OKAY [ 0.006s]
writing 'qupfw_b'...
OKAY [ 0.004s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'storsec_a' (24 KB)...
OKAY [ 0.003s]
writing 'storsec_a'...
OKAY [ 0.004s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'storsec_b' (24 KB)...
OKAY [ 0.010s]
writing 'storsec_b'...
OKAY [ 0.005s]
finished. total time: 0.015s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system_a'...
OKAY [ 0.137s]
sending sparse 'system_a' 1/6 (460753 KB)...
OKAY [ 15.731s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (524285 KB)...
OKAY [ 21.336s]
writing 'system_a' 2/6...
OKAY [ 0.007s]
sending sparse 'system_a' 3/6 (508111 KB)...
OKAY [ 18.622s]
writing 'system_a' 3/6...
OKAY [ 0.007s]
sending sparse 'system_a' 4/6 (482530 KB)...
OKAY [ 18.322s]
writing 'system_a' 4/6...
OKAY [ 0.005s]
sending sparse 'system_a' 5/6 (481413 KB)...
OKAY [ 17.874s]
writing 'system_a' 5/6...
OKAY [ 0.006s]
sending sparse 'system_a' 6/6 (218712 KB)...
OKAY [ 9.743s]
writing 'system_a' 6/6...
OKAY [ 0.006s]
finished. total time: 101.799s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system_b' 1/6 (460753 KB)...
OKAY [ 16.083s]
writing 'system_b' 1/6...
OKAY [ 0.006s]
sending sparse 'system_b' 2/6 (524285 KB)...
OKAY [ 20.273s]
writing 'system_b' 2/6...
OKAY [ 0.006s]
sending sparse 'system_b' 3/6 (508111 KB)...
OKAY [ 18.702s]
writing 'system_b' 3/6...
OKAY [ 0.007s]
sending sparse 'system_b' 4/6 (482530 KB)...
OKAY [ 18.282s]
writing 'system_b' 4/6...
OKAY [ 0.017s]
sending sparse 'system_b' 5/6 (481413 KB)...
OKAY [ 17.782s]
writing 'system_b' 5/6...
OKAY [ 0.006s]
sending sparse 'system_b' 6/6 (218712 KB)...
OKAY [ 9.483s]
writing 'system_b' 6/6...
OKAY [ 0.007s]
finished. total time: 100.653s
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta_a'...
OKAY [ 0.005s]
finished. total time: 0.011s
target reported max download size of 536870912 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.011s]
writing 'vbmeta_b'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' 1/2 (521885 KB)...
OKAY [ 17.719s]
writing 'vendor_a' 1/2...
OKAY [ 0.005s]
sending sparse 'vendor_a' 2/2 (265685 KB)...
OKAY [ 12.415s]
writing 'vendor_a' 2/2...
OKAY [ 0.006s]
finished. total time: 30.145s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_b' 1/2 (521885 KB)...
OKAY [ 17.638s]
writing 'vendor_b' 1/2...
OKAY [ 0.006s]
sending sparse 'vendor_b' 2/2 (265685 KB)...
OKAY [ 12.434s]
writing 'vendor_b' 2/2...
OKAY [ 0.005s]
finished. total time: 30.083s
target reported max download size of 536870912 bytes
sending 'LOGO_a' (3160 KB)...
OKAY [ 0.100s]
writing 'LOGO_a'...
OKAY [ 0.028s]
finished. total time: 0.128s
target reported max download size of 536870912 bytes
sending 'LOGO_b' (3160 KB)...
OKAY [ 0.106s]
writing 'LOGO_b'...
OKAY [ 0.027s]
finished. total time: 0.133s
Any idea what I can do with my bricked OnePlus6?
Thanks Martin

Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.

I have had the same issue while trying to install LineageOS 17 and AOSiP, haven't tried any other rom. I booted to twrp, flashed rom and flashed twrp zip and I tried to reboot into twrp, it didn't boot instead gave black screen and white LED. I repeated the process after restoring using msmtool multiple times yet no solution.

I had a similar problem, I fixed it by flashing the "criticals" partitions from this thread. You need TWRP access to do it. The OP says they used that thread but it doesn't look like they flashed "criticals". I'm not sure if whatever msmdownloadtool flashes includes these critical partitions or not.
Also, one of my slots was working OK, the other one wasn't. Some low-level partitions had got corrupted on the other one and it was this one I was (initially) booting into, leading to the white LED, black screen. I was able to fix things temporarily by changing the active slot like this:
Code:
fastboot getvar current-slot
then you can change it to the other slot with
Code:
fastboot --set-active={"a" or "b" whichever isn't active}
fastboot reboot {recovery|bootloader}
That may get you TWRP or even full Android access. However you should be able to boot TWRP from fastboot anyway.

tiga016 said:
Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.
Click to expand...
Click to collapse
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...

+1 for MSM Download Tool

martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
Use blu_spark twrp 9.101

martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
With a Win-PC it was working and the factory rom is working again. Now twrp (org and blue) are not working...
Again unbrick was successful!

I bought a used OP6 that bricked when I applied the latest OTA, so I had to figure out what was wrong and get it working again. This is my first A/B phone. I worked out the steps below to unbrick the phone and get it on the latest OxygenOS, so I thought I could share this process with others in the same dire situation I was in.
Current as of 2019-11-12
Based on https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Download:
MsmDownloadTool V4.0 International (with Oxygen OS 5.1.5) https://mega.nz/#F!CfBG0IgZ!Gmnu6B-a7yFyvMLNw_pz8w
Qualcomm driver: https://androidfilehost.com/?fid=24052804347798730
Latest full OS from OnePlus (Oxygen 9.09 currently): https://www.oneplus.com/support/softwareupgrade/details?code=8
Notes:
The MSM tool is for writing the base configuration, below recovery and fastboot.
These instructions worked on Win 7 x64 and Win 10 x64.
ADB and fastboot must be installed on PC.
OTA must bring phone to the same version as the downloaded OOS (for example, OTA must update to 9.09, and download must be OOS 9.09).
This process will return the phone to stock OOS (with stock recovery).
Unzip the Qualcomm driver and MSM Tool packages into their own folders on the PC
Install Qualcomm driver (only needed the 1st time on the PC):
Boot the phone into Bootloader
Go to Device Manager on PC and uninstall the Qualcomm entry under COM Ports
Unplug phone and power it down
Enter test mode on PC (to keep Win from installing default drivers): cmd prompt, enter "bcdedit /set testsigning on", reboot PC
Boot phone: press power and then Vol Up for at least 5 seconds (to enter basic config mode), plug into PC
Device Manager, look for "US8_BULK", Update Driver with extracted Qualcomm folder, new entry in Device Manager should be a Qualcomm COM port (YT video: https://www.youtube.com/watch?v=PpLvmID1wdI)​Run MSM Tool as Administrator, click Start, let process run until Complete, reboot phone
Run OTA updates on phone
Reboot to System
Reboot to Bootloader
Check active slot:
Command: "fastboot getvar all", look for "(bootloader) current-slot:x" entry and note a or b​Reboot to System
Update other slot:
Copy downloaded OnePlus OS zip file to phone Internal Memory
Go to Settings > System > System Updates
Tap "gear" (settings) icon in upper-right corner, select "Local upgrade"
Select copied file, and "Install Now"​Reboot to System
Reboot to Fastboot and verify that slot is different than previous check
Choose desired slot (optional):
Command: "fastboot set_active other"​Reboot to System
Exit test mode on PC: Cmd prompt, enter "bcdedit /set testsigning off", reboot PC
Troubleshooting:
For "Sahara" error in MSM Tool, unplug, power on, power off, hold Vol Up for 5 seconds, plug in again