Database Info

[Q] P5113 Can't boot to CWM recovery

Followed root guide http://forum.xda-developers.com/showthread.php?t=1657056 to the letter.
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
I have downloaded the files several times, made sure the drivers are updated and installed and I still get the same result.
When in download mode, it says Custom Binary Download: Yes (10 counts)
Any help would be appreciated. Thanks!

Try the updated CWM recovery in my guide.

No joy! Downloaded your CWM recovery on a different pc and after flashing with Odin, I still can only boot to the stock android recovery.
My counter went up one more time. Pure frustration at this point!

I'm having the same problem on my 3113. I tried several times, odin says everything is good, count goes up and still Android recovery.
sent from my Samsung Galaxy Tab 2 7.0

i have same proglem on GT-P5100.. what should i do.. :crying:

I can't guarantee this will fix it, buy you should try restoring to stock 4.0.3.

Rolled back to 4.03 and everything works great! Big thanks for your help!

How to rollback to 4.0.3?
I see folks talking about rollback to 4.0.3, yet no one explains how to do it or where to get the firmware image from! As far as I can tell, I have to have root access before I can flash anything. My device is reporting that it is not properly rooted. What do I do next? I've successfully rooted my EVO and my Galaxy Nexus, but the GTab2 has me stumped.
Widedomain said:
Rolled back to 4.03 and everything works great! Big thanks for your help!
Click to expand...
Click to collapse

Same but with Heimdall. Well at least it is awesome Windows users experience the same troubles. This improves chances that somebody has enough rating here to post to the ClockworkMod recovery thread.
Widedomain said:
Followed root guide http://forum.xda-developers.com/showthread.php?t=1657056 to the letter.
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
I have downloaded the files several times, made sure the drivers are updated and installed and I still get the same result.
When in download mode, it says Custom Binary Download: Yes (10 counts)
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse

Look in the general thread. Links to 5110 and 5100 are in a guide thread that includes returning to stock in the title. The 5113 is in a different thread titled something like 5113 stock firmware
Sent from my XT860 using xda premium

Widedomain said:
Rolled back to 4.03 and everything works great! Big thanks for your help!
Click to expand...
Click to collapse
4.0.3 - no joy

Endoroid said:
Look in the general thread. Links to 5110 and 5100 are in a guide thread that includes returning to stock in the title. The 5113 is in a different thread titled something like 5113 stock firmware
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The problem appears to be that Samsung has gotten cute and restores stock recovery during the boot.
This isn't very nice -- they did the same thing with a recent update on their SGS-II phones as well, and I don't remember how I got around it.

Genesis3 said:
The problem appears to be that Samsung has gotten cute and restores stock recovery during the boot.
This isn't very nice -- they did the same thing with a recent update on their SGS-II phones as well, and I don't remember how I got around it.
Click to expand...
Click to collapse
I noticed this first on my Thrive tablet, then noticed it again on the 4.0.4 update. Once you are rooted, you can rename (If memory serves) /system/etc/install-recovery.sh to something like /system/etc/install-recovery.bak
Then go back into download mode and reflash cwm recovery.
I incremented my flash count by about 5 before I remembered about this.
If you do not rename that script, by the time you see your boot animation, the stock recovery will have already overwritten your custom recovery..

MultipleMonomials said:
Try the updated CWM recovery in my guide.
Click to expand...
Click to collapse
I was going to follow your guide, which is well organized, but the firmware download for my p5113 is no longer supported by that site.

Widedomain said:
(...)
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
(...)
Click to expand...
Click to collapse
That´s the trick:
Uncheck "Auto-Reboot" in Odin.
If Odin finished flashing: wait one minute.
Now DIRECTLY boot from Downloadmode into Recovery - don´t reboot into System!
Now enjoy CWM - no need to do this again

No recovery mode/factory reset

ok i have open root with htcdev went smooth second used superboot also flashed first time
after flashing namleless v1.1 starting going wrong
problem im having now is the phone loads normaly when i try clockwork recovery it hangs on logo screen same for factory reset
software is as follows
android version 4.0.3
htc sense version 4.0
software number Nameless v1.1
htc sdk api level 4.21
htc extension version _403_1_ga_9
kernal version 3.0.16-g8149866 [email protected]#1
baseband version 10.08.98.09h_1.05.98.11m3
build number 1.45.401.4 cl65553
browser version webkit/534.30
***unlocked***
golfu pvt ship s-on rl
hboot-1.28.0000
radio-1.05.98.11m3
emmc-boot
is there away to get clock work bk working have tryed reflashing it says complete but still will not load recovery or factory reset
is there a compatable ruu i can use or maybe some other flash
regards

I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.

theGekkoST said:
I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.
Click to expand...
Click to collapse
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??

Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did you compare the MD5 sum? How are you flashing recovery?

orangekid said:
Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did yo the MD5 sumu compare ? How are you flashing recovery?
Click to expand...
Click to collapse
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls

spiderx1972 said:
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls
Click to expand...
Click to collapse
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.

orangekid said:
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.
Click to expand...
Click to collapse
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol

spiderx1972 said:
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol
Click to expand...
Click to collapse
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot

orangekid said:
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot
Click to expand...
Click to collapse
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help

spiderx1972 said:
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help
Click to expand...
Click to collapse
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM

orangekid said:
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM
Click to expand...
Click to collapse
flashed Slim Sense 1.0 for HTC Desire C works fine got my wireless working aswell lol
But i have another question maybe me but when i used other roms in the past i couldnt use htc sync strange i no but i tested the roms to see if it was them causing the problem even formated pc but still no joy stuck at loading Apps from my pc ??
connection from phone is there when i pick drive my sd card pops up on pc when i sync phone is saying unable to open htc sync manager on your computermake sure the application is installed and open witch it is ??

Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app

orangekid said:
Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
still trying been hours now running at like a bull but no joy yes ive used the same drivers as when it worked before think ive tryed every version of htc sync must be some think saft knowing me

spiderx1972 said:
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??
Click to expand...
Click to collapse
Yea it is, but I think it's more for Motorola devices. I don't know what HTC uses if anything different. But my phone would boot to the OS so I could still install apps via the SD card. Once I got that properly reinstalled I could access the boot menu again.
Seems like you got that issue solved by I still wanted to follow up.

[Q] Force OTA udpate?

Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!

Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.

Delete Data from Google Framework Apk and then start the Update Checker.

UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:

Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...

I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"

chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!

fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.

chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.

fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...

chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?

desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be

Moto G (1st gen) OTA to Lollipop fails

Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks

Same problem here

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.

A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...

Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.

A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.

Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.

A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?

Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.

A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.

Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least

Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...

To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.

update to latest OTA and recovery issue

HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks

Disregard the message.

Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg

All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?

Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L

I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update

Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official

Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365

thanks! Ah OK I see so that's the whole ROM there as opposed to just an update

davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?

Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse

The file I quoted is not a whole ROM, it's 31 MB.

AH OK, sorry I thught you referred to the 500mb file

Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.

I'm having the same issue. Anyone?

Got the same problem. Any idea?

duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?

Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658