Related
Ok was trying to install a ROM and got an error that there was no OS installed and now the phone wont boot up
I rooted it via Bacon root toolkit and I took a back up before I rooted but I cannot get it to reboot. The back up is saved on the PC and phone not getting picked up by PC
Anyone tried to restore android back up file and went to ab file on pc but it wont load. Can go into fastboot and recovery but not showing on PC
HELP
Delete duplicate post
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
timmaaa said:
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
funkyirishman said:
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
Click to expand...
Click to collapse
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
timmaaa said:
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
Click to expand...
Click to collapse
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have the files saved in the download folder.
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
funkyirishman said:
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
funkyirishman said:
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
Click to expand...
Click to collapse
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
funkyirishman said:
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
Click to expand...
Click to collapse
CM12 does do that, but no other ROMs do.
funkyirishman said:
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Click to expand...
Click to collapse
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
funkyirishman said:
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Click to expand...
Click to collapse
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
funkyirishman said:
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
Click to expand...
Click to collapse
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
timmaaa said:
CM12 does do that, but no other ROMs do.
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
Click to expand...
Click to collapse
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
funkyirishman said:
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
Click to expand...
Click to collapse
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
timmaaa said:
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
Click to expand...
Click to collapse
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
funkyirishman said:
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
Click to expand...
Click to collapse
You have nothing to check it against though.
Transmitted via Bacon
timmaaa said:
You have nothing to check it against though.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
funkyirishman said:
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
Click to expand...
Click to collapse
Well yeah, if you can't reach the download page there's no way to see what the md5 is. Not all download pages have it anyway, they should, but not all do.
Transmitted via Bacon
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?
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
6andro said:
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
Click to expand...
Click to collapse
Just follow this...
STEPS:
1. Download http://builds.cyngn.com/cyanogen-os...263178b74/cm-12.0-YNG1TAS0YL-bacon-signed.zip
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Shankar9822 said:
Just follow this...
STEPS:
1. Download [lurl]
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Click to expand...
Click to collapse
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Update twrp first then flash. You will not loose personal data when doing the wipe.
Sent from my A0001 using XDA Free mobile app
6andro said:
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Click to expand...
Click to collapse
I think you are using the wrong version of TWRP.
http://dl.twrp.me/bacon/
Use the above link, download the latest version 2.8.6.0-bacon.img and flash it...
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
striker280 said:
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
Click to expand...
Click to collapse
It's normal for the stock recovery to be flashed during an OTA update. Yes you can flash it again. No it won't relock your bootloader.
Transmitted via Bacon
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
ChainFires Son said:
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
Click to expand...
Click to collapse
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Renosh said:
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Appreciate the the reply! I'm going to restore to stock, and do it all over and update the baseband/firmware from there. Just to be safe ?
My phone is currently on 13.0-ZNH0EAS26M and I want to update to cm-13.0-ZNH0EAS2JK as it is the incremental update. I rooted my phone and have TWRP. Before, I had to redownload my phone's current images and flash it thru fastboot to go back to "stock" and update my phone thru OTA. Now, I plan on doing that again but I can't find the images for 13.0-ZNH0EAS26M, all I could find are cm-13.0-ZNH0EAS2JK, can I just download the flashable zip and just go from there? Will I lose any data from this? Thanks
FadedAce said:
My phone is currently on 13.0-ZNH0EAS26M and I want to update to cm-13.0-ZNH0EAS2JK as it is the incremental update. I rooted my phone and have TWRP. Before, I had to redownload my phone's current images and flash it thru fastboot to go back to "stock" and update my phone thru OTA. Now, I plan on doing that again but I can't find the images for 13.0-ZNH0EAS26M, all I could find are cm-13.0-ZNH0EAS2JK, can I just download the flashable zip and just go from there? Will I lose any data from this? Thanks
Click to expand...
Click to collapse
If you have TWRP you can just flash to the latest cm-13.1-ZNH2KAS1KN directly using the signed flashable zip found here.
Its the full ROM so there is no need to go from OTA to OTA till the latest.
Simply download, go to recovery and wipe system, dalvik and cache then flash the ROM and you're on the latest build
please close this thread as i already flashed it and everything is ok. thank you
Renosh said:
If you have TWRP you can just flash to the latest cm-13.1-ZNH2KAS1KN directly using the signed flashable zip found here.
Its the full ROM so there is no need to go from OTA to OTA till the latest.
Simply download, go to recovery and wipe system, dalvik and cache then flash the ROM and you're on the latest build
Click to expand...
Click to collapse
Thank you sir, please disregard the previous message as i thought nobody replied to my post. Thank you very much