[Q] how to downgrade to stock rom from cm 12 nighlies - ONE Q&A, Help & Troubleshooting

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.

Related

[Q] flash rom with TWRP recovery failed - full wipe! no more sistem files! HELP

I flash MOKEE rom with TWRP recovery - failed - full wipe! no more sistem files! HELP
HELP please
My OPO is empty! How do I install a rom? I have a mac:crying:
I reboot in fastboot mode and connect to the mac
I use OneToolkit:
I unzip on desktop: cm-11-20140709-SNAPSHOT-M8-bacon
I have chosen: 6. Do some basic ADB and Fastboot commands.
result:
Flashing your OnePlus One back to stock. Please wait...
-----------------------------------------------
target reported max download size of 536870912 bytes
sending 'boot' (5614 KB)...
OKAY [ 0.179s]
writing 'boot'...
OKAY [ 0.084s]
finished. total time: 0.264s
error: cannot open '/Users/jak/Desktop/cm-*/userdata.img'
error: cannot open '/Users/jak/Desktop/cm-*/system.img'
error: cannot open '/Users/jak/Desktop/cm-*/recovery.img'
error: cannot open '/Users/jak/Desktop/cm-*/cache.img'
target reported max download size of 536870912 bytes
sending 'modem' (56289 KB)...
OKAY [ 1.768s]
writing 'modem'...
OKAY [ 0.762s]
finished. total time: 2.531s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.010s]
finished. total time: 0.024s
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
target reported max download size of 536870912 bytes
sending 'aboot' (375 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.011s]
finished. total time: 0.026s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.012s]
writing 'tz'...
OKAY [ 0.010s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.303s]
writing 'LOGO'...
OKAY [ 0.135s]
finished. total time: 0.438s
Congratulations the phone should now be stock!
PLEASE HELP!
Try this http://www.androidheadlines.com/2014/07/android-flash-oneplus-one-stock-cyanogenmod-11s.html
SUPER THANKYOU nneves! OPO was resurrected!:laugh:

[Q] Unable to flash ROMS/OTA updates

I received my OnePlus One a few days ago and attempted install the 05q OTA update, however when the phone rebooted it was stuck in a bootloop where various artifacts would appear on screen before rebooting. I managed to flash back to the 44s firmware via fastboot and install TWRP and root the device.
I have tried to update the firmware via fastboot and TWRP but each time it ends up bootlooping. I have also tried to flash the CM12 nightlys, and although the install is successful, the same issue is present when trying to boot. Attempting to flash different kernels (eg. Franco kernel) has the same issues.
I'm not sure if this is a common problem or if I've just managed to get a dud phone. The phone I received seems to be the Chinese variant (Missing LTE bands), but it arrived with CM11S installed. Not sure if that would affect the ability to update?
Any help or information would be much appreciated
You shouldn't have any problems flashing regardless of which variant you have. Are you checking the md5 of downloaded files before flashing? Which firmware did you try to update? Saying "the firmware" is like saying nothing at all. Are you remembering to wipe properly before flashing CM12? Which version of which kernel was flashed on which ROM? There's a theme here, please provide more detailed information.
My first attempt was the OTA update from XNPH44S to XNPH05Q. This caused the device to get stuck at the OnePlus logo.
Then I proceeded to unlock the bootloader and attempt to flash the 05Q fastboot image located at http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746. It's appears to have successfully installed, but again, bootloops.
Flashing the 44S update from the link above worked.
As for CM12, a factory reset was performed before attempting to flash the cm-12-20150121-UNOFFICIAL-bacon.zip found here https://basketbuild.com/devs/klvnhng/cm-12.0_bacon. Successful install, but bootlooping persists.
Attempted to flash Franco kernel r35 found here http://kernels.franco-lnx.net/OnePlusOne/4.4/ over stock XNPH44S firmware. No luck.
If any more information is required do not hesitate to ask.
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
timmaaa said:
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
Click to expand...
Click to collapse
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
samskies1 said:
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
Click to expand...
Click to collapse
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
timmaaa said:
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
samskies1 said:
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
Click to expand...
Click to collapse
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
timmaaa said:
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
Click to expand...
Click to collapse
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
samskies1 said:
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
Click to expand...
Click to collapse
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
timmaaa said:
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
Click to expand...
Click to collapse
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
samskies1 said:
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
Click to expand...
Click to collapse
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
timmaaa said:
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
Click to expand...
Click to collapse
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
samskies1 said:
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
Click to expand...
Click to collapse
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
timmaaa said:
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
Click to expand...
Click to collapse
If this return to a third party seller goes though I think I may use that method to buy one directly from OnePlus.
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...??
johnsin5393 said:
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...
Click to expand...
Click to collapse
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
samskies1 said:
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
Click to expand...
Click to collapse
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
johnsin5393 said:
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
Click to expand...
Click to collapse
Would you happen to have a link to what you flashed?

OnePlus One Stuck In Bootloop After Flashing CyanogenMod From OxygenOS

HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
dirtylife2011 said:
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
Click to expand...
Click to collapse
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Click to expand...
Click to collapse
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
dirtylife2011 said:
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
Click to expand...
Click to collapse
Please try again and copy/paste the text from the command prompt here so I can see.
Heisenberg said:
Please try again and copy/paste the text from the command prompt here so I can see.
Click to expand...
Click to collapse
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
dirtylife2011 said:
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]alihk-VPCEB3MFX:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Hmm, can you boot into recovery?
Heisenberg said:
Hmm, can you boot into recovery?
Click to expand...
Click to collapse
yes .now its boot to cyanogen recovery
dirtylife2011 said:
yes .now its boot to cyanogen recovery
Click to expand...
Click to collapse
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Heisenberg said:
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Click to expand...
Click to collapse
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
dirtylife2011 said:
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
Click to expand...
Click to collapse
Yes that message is normal. Did the flash succeed or fail?
deleted
Heisenberg said:
Yes that message is normal. Did the flash succeed or fail?
Click to expand...
Click to collapse
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
dirtylife2011 said:
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
Click to expand...
Click to collapse
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
thank you for step by step help....
and sorry for my bad English language
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
dirtylife2011 said:
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
Click to expand...
Click to collapse
Oh hell yeah!! Awesome news
Thank you so much for this guide to fixing a corrupt persist.img. I just learned how to use cmd.exe and fastboot to flash this to my phone that was messed up. This guide saved my phone!!

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??

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

Categories

Resources