Database Info

Stuck at "Google Logo" on boot (after Carbon Rom update)

I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?

Towelie90 said:
I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?
Click to expand...
Click to collapse
Have you tried reflash the rom or restore an eariel backup?
Read this how to send a rom to your phone if you are in recovery http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273

bitdomo said:
Have you tried reflash the rom or restore an eariel backup?
Read this how to send a rom to your phone if you are in recovery http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Click to expand...
Click to collapse
Thank you. It turned out, the nightly had a Problem. I flashed the previous Rom instead

Towelie90 said:
Thank you. It turned out, the nightly had a Problem. I flashed the previous Rom instead
Click to expand...
Click to collapse
Same issue with the same version of Carbon ROM. I tried to OTA update to 20140706 and was stuck at google logo. After reflashing 20140706 downloaded directly from carbon website with verified MD5 match, still no go.
Only reverting back to 20140705 did the trick. With 20140705 it booted first time with no problems, and, did not require a factory reset. All userdata still in tact.
Using TWRP 2.7.1.1
Thanks!

Towelie90 said:
I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?
Click to expand...
Click to collapse
Vihsadas said:
Same issue with the same version of Carbon ROM. I tried to OTA update to 20140706 and was stuck at google logo. After reflashing 20140706 downloaded directly from carbon website with verified MD5 match, still no go.
Only reverting back to 20140705 did the trick. With 20140705 it booted first time with no problems.
Using TWRP 2.7.1.1
Thanks!
Click to expand...
Click to collapse
If you check the file size of that nightly it was smaller than the previous one. I would recommend making a backup before updating nightlies since sometimes these things happen.

Lethargy said:
If you check the file size of that nightly it was smaller than the previous one. I would recommend making a backup before updating nightlies since sometimes these things happen.
Click to expand...
Click to collapse
Yup. Always a good idea. Sometimes we get lazy though.

Vihsadas said:
Yup. Always a good idea. Sometimes we get lazy though.
Click to expand...
Click to collapse
And then come here and ask stupid questions
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
And then come here and ask stupid questions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Whoa easy there on the full out attack. It's unnecessary.
And, I did not actually ask any questions. Just offered my experience for others that might have had the same problem.
Relax.

Hey,
Sorry if I'm a bit late here, but they actually left out some of the firmware from the release. If you download the 07/06 zip, then merge the 07/07 with it (of course, replacing anything that exists) and zip the combination up and flash it, you'll be all set with the newest nightly.

I have the same problem. Unfortunately, I updated about 10 minutes before I was leaving for work so now I'm without a phone until I can get back and flash yesterday's nightly. I usually only update in the evening in case this happens but I haven't had any issues with Carbon up until now so I figured, what the hell... Guess that'll teach me to do that again.

Flashing problems

OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!

Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?

krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.

Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?

krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966

Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8

krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!

krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.

Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/

krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.

krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.

Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616

krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion

Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.

krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!

Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development

Have you tried a RUU?

young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??

Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.

Thanks!
GNU con Linux

Cannot install 9MB OTA update

Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.

oscarandjo said:
Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.
Click to expand...
Click to collapse
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.

Dzhedaj said:
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.
Click to expand...
Click to collapse
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?

oscarandjo said:
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?
Click to expand...
Click to collapse
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon

timmaaa said:
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon
Click to expand...
Click to collapse
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?

oscarandjo said:
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
It's probably something you installed from xposed. But your solution should work.

apristel said:
It's probably something you installed from xposed. But your solution should work.
Click to expand...
Click to collapse
I'm going to try uninstalling xposed and my modules before reflashing all of that.

oscarandjo said:
I'm going to try uninstalling xposed and my modules before reflashing all of that.
Click to expand...
Click to collapse
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.

oscarandjo said:
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.
Click to expand...
Click to collapse
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.

playya said:
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.
Click to expand...
Click to collapse
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup

oscarandjo said:
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup
Click to expand...
Click to collapse
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users

playya said:
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users
Click to expand...
Click to collapse
I see, thanks.

oscarandjo said:
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon

Does anyone have a 25R mirror? Mega.co.nz would be best. Cyanogen's servers are being awfully slow.

timmaaa said:
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon
Click to expand...
Click to collapse
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?

oscarandjo said:
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?
Click to expand...
Click to collapse
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas

playya said:
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas
Click to expand...
Click to collapse
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
I guess I'll have to do this...
Flash system.img of 25R, update to 30O and then the mini 30O patch. Then re-root using TWRP, then restore my stuff using Titanium Backup and set everything up as it was, wasting an hour or two. :/
Anyway, I understand this is the best way to do it, thanks for the help.

oscarandjo said:
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
Click to expand...
Click to collapse
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:

playya said:
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:
Click to expand...
Click to collapse
Yeah, does Titanium Backup backup large sideloaded apps?

oscarandjo said:
Yeah, does Titanium Backup backup large sideloaded apps?
Click to expand...
Click to collapse
Pro version will restore all at one time. That's not recommended especially if you are restoring from a different version of android. Its all at your own risk. I been there and for me shortcuts were not worth it always for me at least...
1+1 Homie......

Semi-bricked OPO, need help restoring

Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You

Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon

timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?

You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon

EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.

Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)

Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon

timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)

Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.

OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?

Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon

No mobile data / Baseband Unknown [SOLVED]

Hi,
My mobile data no longer works. I've done a lot of research, tried every fix, to no avail. My WiFi works, it's only my mobile data.
Things I've tried:
Following this guide: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Completely reverting to stock
Flashing a stock, rooted 44S + radio files
Flashing ColorOS, and then flashing CM11S using this guide: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Sticking the SIM card in my Galaxy S3 to see if it works (spoiler: it does)
Restoring previous nandroid while data was working fine
Under ColorOS, I have a notification that says "The NV partition is invalid!". Just thought I'd mention that.
Stupid me didn't backup my EFS. No APNs, unknown IMEI, unknown baseband, etc.
I'm at a loss guys. I'd greatly appreciate your help.
Thanks,
Niko

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon

timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
Yup. Sadly didn't work.

You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon

timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
You think it would be worth trying to get a new sim card from my carrier?

It isn't the SIM that's the problem, your EFS partition is corrupt.
Transmitted via Bacon

If my EFS partition was corrupt, why does my Wifi work?

That's normal.
Transmitted via Bacon

I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot

NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
Click to expand...
Click to collapse
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?

grneyez said:
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
Click to expand...
Click to collapse
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.

NikoZBK said:
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
Click to expand...
Click to collapse
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.

grneyez said:
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
Click to expand...
Click to collapse
Please post back how it goes.

NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
I will thanks.

NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
Worked like a charm, thanks so much for your help.

timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?

Rkr87 said:
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon

NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash 44S (Pre-Rooted)
Click to expand...
Click to collapse
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?

DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
44S is short for XNPH44S, which is the latest build of CM11S (the stock firmware) for this phone.
Transmitted via Bacon

DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
No, I did this for the global version, but the steps should work for you as well.