Related
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
DarknessWarrior said:
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
Click to expand...
Click to collapse
You can (i did as well) but any tweaks to system files etc will be overwritten and it will go to stock kernel.
to do this. follow the directions at the below link. the step about changing the flash-all file is crucial as if you don't do that then it will wipe your data as well.
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
y2whisper said:
You can (i did as well) but any tweaks to system files etc will be overwritten and it will go to stock kernel.
to do this. follow the directions at the below link. the step about changing the flash-all file is crucial as if you don't do that then it will wipe your data as well.
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
Click to expand...
Click to collapse
Thank you. I don't really care about the tweaks and the kernel I'll flash later, I just don't want to wipe and have to reinstall/reconfigure everything.
DarknessWarrior said:
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
Click to expand...
Click to collapse
Because I've also modified too many system files I usually open up the factory image and pull the images I need and flash those, or you could flash the boot and system images from 4.4.2 and do the OTA. For the update to 4.4.3 you would need the boot, radio and system images. The bootloader image stayed the same. Scenario 2 in this link will show what I'm talking about. Really only takes a few minutes. ; )
Wanted to add that at the end instead of doing fastboot reboot I would unplug your phone and use your volume and power button to get into recovery and flash the supersu zip.
Updated my N5 and N7 Monday night and everything is working well!
Not a great idea
Most likely you'll wind up with issues from the dirty flash and have to reset the device anyway in my experience.
I tried flashing 4.4.3 I'm on stock rooted but it won't install when trying to flash gives me a error status 7. Anyone please help!
Dirty flashing a new android version is a bad idea. In my opinion.
Clean flash.
---------- Post added at 07:54 PM ---------- Previous post was at 07:51 PM ----------
Maybe they tweaked location services to not suck so much juice.
I always toggle it off. Will have to try it on after I update.
Clean flash only for a new version has always been the golden rule!
Lol, what? Clean flash only if you're switching ROMs. If you're on the factory rom, flashing a factory image is perfectly fine. I've upgraded 4 different devices through many versions of Android with out a single issue.
galaxys said:
Clean flash only for a new version has always been the golden rule!
Click to expand...
Click to collapse
Completely agree. Regardless of how many problems other people haven't had. The exact same principles apply as custom ROMs. Legacy data and settings can interfere between versions so I would always recommend a wipe, at least before reporting any "bugs"
Sent from my Nexus 5 using Tapatalk
GldRush98 said:
Lol, what? Clean flash only if you're switching ROMs. If you're on the factory rom, flashing a factory image is perfectly fine. I've upgraded 4 different devices through many versions of Android with out a single issue.
Click to expand...
Click to collapse
Many can't say the same. Clean flashing the firmware is always better than dirty flashing or updating by OTA.
Yup
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
I was trying to flash Exodus-Vanir on my OnePlus One. But it gives me error on
Code:
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"
E: Error executing updater binary in zip '/sdcard/Vanir ROM/exodus-vanir_bacon_5.0.2.031015.zip
I'm not sure about what to do in this case. I have tried to remove the line from the updater script but figured I need to get some ideas beforehand. Anybody got a workaround for this?
I know you need to update the firmware but EVERY SINGLE LINK I FIND IS DEAD! Someone, please give me a working link to the CM12 firmware.
You need the updated firmware and modem.
Firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modem:
https://docs.google.com/file/d/0B98G0KTJwnBFMThZUjhndGJlc1U/edit?usp=docslist_api
Transmitted via Bacon
Hi. How can we update them? Just flash them the through recovery?
Also, is there available a beginner guide how to install Exouds/Vanir Rom? Im currently on Liquidsmooth 5.0 and I want to switch to Vanir rom, but im not 100% sure what I have to do...
Thanks.
edzalv said:
Hi. How can we update them? Just flash them the through recovery?
Also, is there available a beginner guide how to install Exouds/Vanir Rom? Im currently on Liquidsmooth 5.0 and I want to switch to Vanir rom, but im not 100% sure what I have to do...
Thanks.
Click to expand...
Click to collapse
Just flash them in recovery. Flashing any ROM is the same, I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thank you very much for your quick reply. Ill give it a try now.
Ohh, one last thing. I have to Flash firmware and mode after I flashed new Vanir Rom, or I have to do it on my current Rom?
edzalv said:
Thank you very much for your quick reply. Ill give it a try now.
Ohh, one last thing. I have to Flash firmware and mode after I flashed new Vanir Rom, or I have to do it on my current Rom?
Click to expand...
Click to collapse
Perform a full wipe (system, data, cache, dalvik cache), flash firmware and modem, go to reboot menu and reboot to recovery, flash ROM + gapps, reboot phone into new ROM.
Transmitted via Bacon
timmaaa said:
Perform a full wipe (system, data, cache, dalvik cache), flash firmware and modem, go to reboot menu and reboot to recovery, flash ROM + gapps, reboot phone into new ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
Luv ya'
I have smillar problem,i flashed firmware update and modem files without problem.But there is no signal , checked 4634,sometimes it finds the signal but no network registration ,sometimes the signal is 0.Imei,baseband are okay.I can use it with 44s modem and sensor file.Any suggestion?
Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
I HAVE NOT TRIED THIS MYSELF:
I would say make a back up, wipe all partitions except for your internal storage, and then try flashing cm12 via twrp.
I went from oxygen back to stock rooted CM11s no problem. I heard Oxygen installs a modified TWRP, though, so you could reinstall the latest version just to be safe before re-flashing CM.
Edit: I didn't have to reinstall the recovery.
The hard is if you got no partition backups. If that is the case you will have to download stock cm11s XNPH05Q latest signed build. Unzip put OPO into fastboot mode. Find the file flash-radio.sh open it and manual flash every command that starts with fastboot. Then flash boot,cache,system, and depending on which data amount you have flash userdata images. Don't worry with the recovery you have twrp. Be ready to start over. Remember friends don't let friends flash CO2 OS. Good luck.
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
The oxygenOS zip installs a boot loader version that doesn't play well with CM11. If a person were to attempt to flash CM11 or restore a CM11 nandroid with that boot loader present it could cause serious complications.
To go back using recover one would need to flash a file that contained a good firmware/bootloader. CM12 from the CM website contains such a configuration. There are other files around that also apply non-bricking firmware. Fastboot flashing CM11S also would work if the device isn't bricked yet.
Once "bricked", recovery is possible but problematic and frustrating.
Flashing via TWRP straight from OxygenOS is not a good idea without preparation.
Hastily spouted for your befuddlement
xdoncam said:
Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
Click to expand...
Click to collapse
You need to flash the right firmware and modem first and then you can flash whatever you like.
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
Not the same at all. Oxygen uses completely different firmware, if you fail to flash the right firmware before going back to CM you'll fail dismally.
Transmitted via Bacon
If you want oxygen you use cm12 firmware
For cm11 you use cm11 firmware
For cm12 you use cm12 firmware.
Formatting system and data and not using tb would help to. I did state this in my first post. Also the bootloader...turns first boot screen red....it works OK on cm12. Had no problems booting
Sent from my A0001
---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
But I did get what you two are saying but people on xda should know this already really. Flashing is easy...fixing is not
Sent from my A0001
andrewwright said:
If you want oxygen you use cm12 firmware
Click to expand...
Click to collapse
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
SAFE way move back from oxygenos to CM11s
For those who havnt shifted back to cm11s.(and still on oxygenos) and want to move back to CM11s ofcourse not hardbricked your phone. THIS GUIDE Is FOR ONEPLUS ONE 64GB VARIANT . (ALSO VALID FOR INDIAN USERS)
This guide will happily and SAFELY get you back to cm11s(XNPH05Q. OTA Safe).
people have hardbricked their phone by simply flashing cm11s through fastboot, which ofcourse is not the appropriate procedure.
NOTE: MY PHONE WAS NOT ROOTED BUT I WAS RUNNING OXYGENOS WITH TWRP RECOVERY INSTALLED(BUT I PREFERRED FASTBOOT METHOD). ONLY DRAWBACK IS YOU NEED TO TAKE BACKUP FIRST . ELSE THIS METHOD IS SAFE.
You need to have the following files:
1. mediafire.com/download/78r7kes21exsnbh/Calkulin's_Stock_OPO_XNPH05Q_ROM_v1.0.zip
2. mediafire.com/download/94o0lb0pzdg1drw/XNPH05Q_Extras.zip
-Extract the first zip. Again extract the zip from the extracted folder.
-Extract the XNPH05Q in the same folder where the all above files were extracted .
-The folder should have fastboot cmd. and you should have fastboot drivers installed .
-put your device in fastboot mode by turning the phone off and pressing volume up+power key simultaneously .
-open cmd in the folder where all of the above files were extracted . press shift and right click in the flder and open command prompt .
- look whether your device is detected by fastboot. type fastboot devices
-You need to have unlocked bootloader.(if not, type fastboot oem unlock)
-TYPE THE FOLLOWING COMMANDS IN THE COMMANDS IN THE ORDER AS GIVEN :
IMP: DONT REBOOT IN BETWEEN COMMANDS
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
You are all done. Sit back and relax.
Lock the bootloader again. After you are done with setting up. type fastboot oem lock
timmaaa said:
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
Click to expand...
Click to collapse
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
andrewwright said:
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
Click to expand...
Click to collapse
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Where can I obtain the needed flashable zip files to revert back to cm11s?
Sent from my A0001 using XDA Free mobile app
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
andrewwright said:
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
Click to expand...
Click to collapse
I actually had it done already by the time I saw this but very much appreciated. I am sure it will come in handy for others.
timmaaa said:
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Click to expand...
Click to collapse
Just to clear this up I had to find out why this is happening. Okay so my home brew cm12 builds don't compile firmware file's. I didn't know this but now I do. So this must have been the reason why I was able to keep oxygen bootloader on cm.
Sent from my A0001
somehow I could just revert to cm12.1
FYI,
In case it helps someone, I tried out OxygenOS last night and while it is stable I dislike many things (email client, text client) and the biggest beef of all is neither text nor email show on my Mazda.
Soooo this is a nono I believe, but I could restore CM12.1.
I just did a backup in TWRP of OxygenOS> then I did a clean wipe> then was able to restore CM12.1 nightlies from June1 I think it was and it seems just fine.
I believe it is because the modem etc in 12.1 is the same as OxygenOS had all along?
I was on CM12 stock 5.0.2 (version 12.0-YNG1TAS2I3) and i wanted to root my phone , so I unlocked bootloader and rooted the phone but now I want to flash a new Rom but I ve read in a couple of rom threads that we have to flash another 5.1nightly before flashing a ROM and I am not sure I understand this part.
I would be grateful if someone could help me with the process of flashing a 5.1 rom and gaaps for the first time on a freshly rooted phone
P.S : ( I also want to use calaukin's gaaps modified by mohit (http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242).
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Heisenberg said:
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Click to expand...
Click to collapse
Thank you so much . I followed your guide too so thank you for the support .
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
davebugyi said:
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
Click to expand...
Click to collapse
I used to share your opinion. But, while a lot of ROM threads do provide a firmware zip, they aren't maintained, it's usually uploaded and forgotten about. Flashing the nightly ensures that you're on the very latest firmware available.