Related
for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock 4.0.4 image from google flash that:
Format System, data, cache, sd card, dalvik cache
Reboot into bootloader
flash bootloader, radio, update image
then flash cwm recovery and install superuser
after that my stock recovery just won't come back, any ideas?
I left the recovery on stock and the play store updated immediately, i also tried manually flashing the recovery from the stock image package from google that didn't help either.
The stock recovery has nothing at all to do with the market updating
You just need to run
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.
albundy2010 said:
The stock recovery has nothing at all to do with the market updating
Click to expand...
Click to collapse
i remember when i first started rooting and all that if you don't have the stock recovery you don't receive things like OTA updates also, thats why I wanted the stock recovery.
Also if i leave the recovery as stock the market updates immediately thats whats bothering me but when I root (flash CWM) it won't update even after hours of waiting it stays on 3.4.7
x ZackehSoul x said:
You just need to run using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.
Click to expand...
Click to collapse
i flashed the stock recovery it didn't help, for some reason. Thats why I posted this question, thanks for the suggestion though
Rooted with CWM as recovery. Shield Tablet has OTA update but obviously can't install with CWM. What is the simplest way to stay up to date and keep root?
Sent from my SHIELD Tablet using xda premium
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Scoobydumb said:
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Click to expand...
Click to collapse
That's not the way to go at all.
Whenever there's an update, flash the incremental OTA file HERE.
Flashing the stock recovery will not allow taking OTA's.
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Scoobydumb said:
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Click to expand...
Click to collapse
Um, just flash it in TWRP or CWM, only need to flash cache and dalvik cache, but that's optional.
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Singularity_iOS said:
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Click to expand...
Click to collapse
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
FoxyDrew said:
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
Click to expand...
Click to collapse
Ok thanks. One more question. How would I go about checking the rom version? Unless I'm missing it I can only see the Android version, which is 5.0.
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Singularity_iOS said:
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Click to expand...
Click to collapse
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Wouldn't the tablet be wiped then? And if this is the case everytime can't I just keep the stock recovery and sideboard a custom one?
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
NaminatoR1254jaime.sier said:
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
Click to expand...
Click to collapse
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
perky nerky said:
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
Click to expand...
Click to collapse
On my previous instructions I pointed out to (after flashing ota) to reflash custom rec and supersu.
NaminatoR1254jaime.sier said:
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Click to expand...
Click to collapse
With twrp I do it literally after flashing full ota. I leave recovery to reboot to system right when Im done flashing everything.
Hey guys!
I have the US 16GB WiFi only model of the SHIELD tablet, it's rooted, bootloader is unlocked, and I'm running 5.0.1 with a custom recovery.
I'm just a little confused as to how to updated to the 2.2.1 software that was recently released. I'm still on 2.1, and when I try to update it asks to update to 2.2 rather than the current, 2.2.1.
However it's been awhile since the last time I installed an update and I forgot the process in order to flash updates and make sure SuperSU is installed, etc.
Can anybody help me out and give me the few steps I need to take in order to make sure I still have root and my custom recovery installed as well as the 2.2.1 update? Thanks.
If you need anymore info just ask.
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
rogvid700 said:
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
Click to expand...
Click to collapse
Seems like your trying to upgrade from 1.2, to 2.2....
Are you currently on Android 4.4.4?
I can confirm that I am running Lollipop 5.0.1
But yeah I noticed that too. It thinks I'm running 4.4.2?
Anyone? Any ideas?
rogvid700 said:
Anyone? Any ideas?
Click to expand...
Click to collapse
Maybe there's just a glitch, or a ghost line of code preventing it from flashing.
My only advice would be to do a full wipe and just flash the full OTA instead of the incremental one.
What's the safest way of doing this?
I have Titanium Backup, and do I just use CWM to do a full wipe? Or something else?
And I'm sure it'll lose root if I do a full wipe. Would I just flash SuperSU after flashing the full OTA in order to get it back?
Sorry for all the questions. I'm not a total amateur, just not an expert.
rogvid700 said:
What's the safest way of doing this?
I have Titanium Backup, and do I just use CWM to do a full wipe? Or something else?
And I'm sure it'll lose root if I do a full wipe. Would I just flash SuperSU after flashing the full OTA in order to get it back?
Sorry for all the questions. I'm not a total amateur, just not an expert.
Click to expand...
Click to collapse
Exactly what you said. Full wipe, then reflash SuperSU.
You'll also have to reflash CWM, as flashing the full OTA in CWM, flashes the stock recovery.
Okay so, I need to put the full OTA on my device, and then wipe? Or vice versa?
Because won't the full wipe remove the full OTA if it's on my device?
So, full wipe, flash OTA, flash CWM, flash SuperSU? (Please correct me if this order is wrong)
rogvid700 said:
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
Click to expand...
Click to collapse
Because u cant do that. You cant flash an incremental OTA via custom rec.
If u are rooted you need to flash latest FULL OTA vía custom recovery, reflash supersu andnyou should be ready
There is no need to full wipe everything. Just "dirty flash" it. Make a nandroid just in case.
1- Make nandroid
2- Flash full ota
3- Wipe cache & dalvik
4- Flash custom rec
5- Flash supersu
That should do it.
So the nandroid backup just won't work through CWM, it fails when trying to backup /data.
I've tried wiping the cache and still nothing. If I just want to go ahead and do a full wipe, where would that be in the steps you gave me?
Thanks!
rogvid700 said:
Okay so, I need to put the full OTA on my device, and then wipe? Or vice versa?
Because won't the full wipe remove the full OTA if it's on my device?
So, full wipe, flash OTA, flash CWM, flash SuperSU? (Please correct me if this order is wrong)
Click to expand...
Click to collapse
Yes this is correct. And when I say full wipe, if it's not obious, DON'T wipe internal storage, or External SD card.
FoxyDrew said:
Yes this is correct. And when I say full wipe, if it's not obious, DON'T wipe internal storage, or External SD card.
Click to expand...
Click to collapse
Thanks you guys! Followed the steps, flashed the full OTA, then CWM, then SuperSU and i am now on 2.2.1 with root!
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
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