Apologies if this has already been asked, couldn't find it in search.
I want to dirty flash over the stock rom, but I get an incompatible rom error from twrp.
I've always been able to do this with previous versions and never had an issue. I even dirty flashed the stock Google build via fastboot on top of cm12 so I wouldn't have to set up again, and the phone has been running fine ever since.
My question is how to disable this security check so I can dirty flash cm13 over stock marshmallow without wiping?
Flashed CM Recovery and it let me dirty flash no problem. Phone is booting now.
Related
Hello,
I keep trying to update to the latest nightly to get cyanogenmod 12 on XT1302. However they don't work. I get weird scan lines, even during the boot logo and animation. Everything is slow and unstable. During installation it always says root access possibly lost, fix, yes or no. Thankfully I have a working backup, but it's stuck on an old 2014 cm 11 snapshot and I want to upgrade
I suspect there is a problem with gapps since I get incessant "X app has stopped working error" messages and it's always a google service. However I do not know what the procedure is. I downloaded the cm12 gapps and flashed them after flashing the nightly as said in faq but it doesn't seem to work. Sometimes even Trebuchet stops working, making the phone totally unusable.
Any help would be greatly appreciated. :good:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
audit13 said:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
Click to expand...
Click to collapse
I've been googling this and I think you have correctly identified the issue. If I install the lollipop bootloader, will I be able to go back to my cm11 backup in case of an emergency?
Just to confirm, to update the bootloader, you have to flash the brazil lollipop rom and it should work?
If you unzip the stock ROM, the bootloader is the motoboot.img file.
I don't think you need to flash everything, just the bootloader file. If that doesn't allow you to use CM12, you may have to restore your CM11 nandroid and then flash CM12.
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Roxkyp said:
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Click to expand...
Click to collapse
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Mr hOaX said:
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Unfortunately these methods did not work for me, I can get on 12.1, but when I want to flash something else (resurection rom in this case) I get the error.
Its a firmware issue you need the correct firmware
Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
PhilRattlehead said:
Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
Click to expand...
Click to collapse
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
i7vSa7vi7y said:
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
Click to expand...
Click to collapse
I tried flashing the modem and bootloader, not the entire firmware. I ended up installing the stock firmware in the end. I am doing the updates now and will install CMRemix shortly after
I always go stock before I flash a new ROM. Best way unless directed otherwise
Hi all. I'm a bit of a noob who just really started digging into custom roms and rooting this month. A friend helped me root Lollipop when I first got this phone and I've been putting off updating to marshmallow for 6 months, but learned how over the past weekend and I'm loving it! Small problem, though, and I don't know if it's even a real one, but here it is. After all is said and done flashing the XstreStoLite 3.3.1 rom and Aroma add on pack, everything works fine, but the arter97 kernel is no longer listed as the active kernel, even though in XstreStoLite's settings when presented with the overwrite kernel option I always selected No. Is there a reason this is happening? Can I just reflash the kernel now, and is it safe to do so without brick in the phone? Does this rom or any other necessary apps/root features require the custom kernel? Thanks! This was my process in getting my phone up and running:
Factory reset
Flash stock 6.0.1 with Odin
Flash arter97 recovery with Odin
Recovery mode to flash arter97 kernel and superSU
Flash XstreStoLite in recovery, factory reset
Flash aroma addon
Additional random question I had: at what point, if any, should I be flashing the custom bootloader and modem, and does a factory reset/cache wipe delete those or is it one and done? Thank you!
The bootloader and modem flashing is needed if you want to move from 5.x lollipop to 6.x marshmallow.
If you are allready on 6.x there is no need.
If you lost your custom kernel you can reflash it in twrp and after wipe cache/dalvik cache.
If you flash the corect version of kernel the is no problem of softbrick.
Flash a 6.x kernel on a 6.x rom
Hello guys for some reason i stocked my OPO to CM11S through that link:https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 and it went succesfull. After that i just flashed official TWRP 3.0.2.0 and try to install custom ROM(tried lineage os 14.1 and tugapower N18)(both nougat) but i just cant install either. i just get updater process ended with error=7 message and nothing happens. Please help me.
UPDATE:Next time if you wat to go stock and flash Android N build after that, first flash cm13 via fastboot. Then you can flash every ROM you want with out a hitch.