Database Info

[Q] cm11 -> cm12 flashing issues

so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?

ItsDeadEnd said:
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
Click to expand...
Click to collapse
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?

Heisenberg said:
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Click to expand...
Click to collapse
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked

ItsDeadEnd said:
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
Click to expand...
Click to collapse
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.

Heisenberg said:
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Click to expand...
Click to collapse
what commands would you suggest i do then? because those are the only things i used other than the wipe command

ItsDeadEnd said:
what commands would you suggest i do then? because those are the only things i used other than the wipe command
Click to expand...
Click to collapse
Well it depends on what you're trying to do. As I said, the "fastboot flash boot boot.img" command will only flash a kernel. You really shouldn't be messing around with fastboot if you don't actually know what you're doing, that's how phones get bricked. Go to my guide and follow the instructions in section 8:
http://forum.xda-developers.com/showthread.php?t=2839471

[SOLVED]
apparently sometime between me instlling cm11 and installing cm12, my oem got re-locked. which prevented me from flashing anything new.
i ran:
fastboot oem unlock
and fastboot flash boot boot.img
and voila
help thread for those with the same problem
http://forum.xda-developers.com/show....php?t=2839471
thank you for the help!

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

Revert from OxygenOS to Cyannogen - problem with recovery

Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:

sylvainsjc said:
Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:
Click to expand...
Click to collapse
download the latest COS12.1.1 factory image to your pc, boot into fastboot mode and install the factory image via fastboot (flash aboot FIRST and do a "fastboot reboot bootloader" before you flash the rest ).
After that (or during, just replace recovery.img) you may install any custom recovery
Gesendet von meinem A0001 mit Tapatalk

Yes :good:
You brought me on the right track
I have successfully applied this method.
I nearly lost my phone because I had a power outage during the recovery but finally all is fine : I am back on COS 12.1.1 :victory:
A big thank-you

Revert from OxygenOS to Lineage - problem with recovery
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?

[email protected] said:
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?
Click to expand...
Click to collapse
Flash twrp with fastboot , then flash the lineage os :good:

Azhar_Fahry said:
Flash twrp with fastboot , then flash the lineage os :good:
Click to expand...
Click to collapse
Yes I am trying to flash TWRP
However, when I follow the below mentioned steps this is what i end up with :
List of devices attached
dc1c2a16 unauthorized
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb devices
List of devices attached
dc1c2a16 device
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb reboot bootloader
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot oem unlock
< waiting for device >
And on the device screen it just reads "Fastboot mode"

So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?

wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk

Azhar_Fahry said:
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.

[email protected] said:
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
Click to expand...
Click to collapse
try to reinstall all the driver from this link ( https://goo.gl/MxKLjH ) and follow the instruction , i use that method and it worked

arashsh2002 said:
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
Click to expand...
Click to collapse
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)

giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
Thank you for your response. I tried doing that but it gives me an error saying that there is already a twrp installed. I used Twrp Manager

giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?

arashsh2002 said:
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?
Click to expand...
Click to collapse
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.

giaur said:
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.
Click to expand...
Click to collapse
it is unlocked

Fastboot loop oneplus 6

I really have no clue how I got here but i had everything going well and then there was an oxygen os update. I installed and lost root functionality so I did the whole twrp install thing all over again which was a mistake. I got stuck in a twrp boot loop and now im stuck in a fastboot loop. I have tried to sideload a stock image but it says phone is not in adb mode.... Help!

david.baquerizo said:
I really have no clue how I got here but i had everything going well and then there was an oxygen os update. I installed and lost root functionality so I did the whole twrp install thing all over again which was a mistake. I got stuck in a twrp boot loop and now im stuck in a fastboot loop. I have tried to sideload a stock image but it says phone is not in adb mode.... Help!
Click to expand...
Click to collapse
Try fastboot install Rom from here. Match the version you last had installed. Give it few minutes to get going once you start the process.

chazey2 said:
Try fastboot install Rom from here. Match the version you last had installed. Give it few minutes to get going once you start the process.
Click to expand...
Click to collapse
Thanks!

I'm in the exact same situation as OP, only my phone is a OP6T @david.baquerizo did you manage to install the fastboot Rom without problems? I'm wondering how it will be able to install if you can't see your phone in fastboot. My plan is to try different computers and go into windows testmode in order to get fastboot access to the phone. If I'm able to do that, it should be possible to flash a twrp.img and get back into action (fingers crossed)

Can't flash twrp

Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly

Gosick1337 said:
Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly
Click to expand...
Click to collapse
What version rom is currently installed

MrSteelX said:
What version rom is currently installed
Click to expand...
Click to collapse
Oxygenos 10.3.0 on my oneplus6.

https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 has everything you need to install twrp