I made sure everything is up to date. I'm trying to flash the 5.0 OTA, but it keeps failing and I don't know why. I went into platform tools and pasted the extracted lollipop download, held shift and right clicked, opened up the command prompt and did the following. I made sure USB debugging was enabled. I've also tried it by using the command adb reboot bootloader from the homescreen to get into fastboot. It doesn't matter what I do, it always fails the same way. I have never had this issue. What the hell is going on?
C:\Users\Raistlin\ADT\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb
devices
List of devices attached
C:\Users\Raistlin\ADT\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>flas
h-all
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.295s]
writing 'bootloader'...
OKAY [ 0.481s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.121s
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.662s]
writing 'radio'...
OKAY [ 3.127s]
finished. total time: 4.793s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.111s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...
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.
Hey,
I could install Kitkat 4.4.2 EMUI 3.0: Cofface Custom Recovery, but could find any os what would install from zip. Getting error 7
today I tried to flash TWRP-3.0.2-r4 for the 4C. So I unlocked the bootloader flashed the new recovery img and then restarted and couldn't access the recovery menu. It freezes right at the Huawei logo.
Then I tried to flash the latest 4C android, so I extracted the boot.img, recovery.img and system.img from the update.app.
Flashing was successful I guess?
Code:
λ fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (23486 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.566s]
finished. total time: 2.098s
λ fastboot flash recovery RECOVERY.img
target reported max download size of 524288000 bytes
sending 'recovery' (33548 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 1.742s]
finished. total time: 2.501s
λ fastboot flash system SYSTEM.img
target reported max download size of 524288000 bytes
sending sparse 'system' (510886 KB)...
OKAY [ 12.234s]
writing 'system'...
OKAY [ 12.280s]
sending sparse 'system' (497530 KB)...
OKAY [ 12.190s]
writing 'system'...
OKAY [ 11.563s]
sending sparse 'system' (511911 KB)...
OKAY [ 12.414s]
writing 'system'...
OKAY [ 12.407s]
sending sparse 'system' (509238 KB)...
OKAY [ 12.379s]
writing 'system'...
OKAY [ 12.039s]
sending sparse 'system' (362252 KB)...
OKAY [ 8.826s]
writing 'system'...
OKAY [ 8.523s]
finished. total time: 114.883s
But I tried to boot into the stock recovery but it freezes at the huawei logo again and I can't boot into android either.
After that I tried to erase the cache and userdata but I am getting the message that I am not allowed to do so.
Code:
λ fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
Does anybody knows a workaround or a possible fix ?
Regards Artur
any updates ??
Up up..
Help guys
Hallo,
Please, I need help with a bricked Huawei Honor 6.
I have almost no knowledge about unbricking and the like.
I tried to update my Smartphone Firmware and used Huawei Update Extractor
combined with cmd Commands.
My Smartphone is in an eternal bootloop and I can only access Fastboot&Rescue Mode.
I ve tried to install another firmware, but there is this command lines in CMD (Huawei Fastboot Flasher):
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending sparse 'cust' (459730 KB)...
OKAY [ 48.349s]
writing 'cust'...
OKAY [ 16.092s]
sending sparse 'cust' (16208 KB)...
OKAY [ 1.711s]
writing 'cust'...
OKAY [ 0.532s]
finished. total time: 66.689s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.416s]
writing 'recovery'...
OKAY [ 0.439s]
finished. total time: 1.857s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10596 KB)...
OKAY [ 1.091s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.102s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (431287 KB)...
OKAY [ 45.667s]
writing 'system'...
OKAY [ 16.017s]
sending sparse 'system' (446975 KB)...
Can some one of u see what's wrong and how to solve this problem? There is one FAILED line and maybe that's the Problem?
In my fastboot mode there I can read in red letters: PHONE Unlocked.
As I said, there is only one mode possible to enter, holding Volume up and then I get into Fastboot&Rescue Mode.
Unfortunately I've got almost zero flashing knowledge.
Pls help me.
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 bReboot 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