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
Related
Hi all,
I have searched the web, but haven't found an exact answer to my question.
I have a Nexus 5, currently on 4.4.2 (KOT49H). I am unlocked, rooted + Xposed and have TWRP. I want to update to 4.4.4 preferably OTA, officially. I would like to be able to use OTA updates from now on if possible.
Currently, if I disable Xposed, and use Suvival Mode in SuperSU and try to install the OTA update, TWRP intervenes and doesn't let me.
I would like to replace TWRP with the stock recovery so I can update OTA in the future. I don't want to wipe the phone to achieve this if possible. If this isn't possible, could someone step through how to update to 4.4.4 with TWRP installed — I'm on a mac also.
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
providedbike said:
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes, extract the image and then the zip file
Sent from my Nexus 5 using XDA Free mobile app
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
rootSU said:
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
Click to expand...
Click to collapse
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
providedbike said:
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
Click to expand...
Click to collapse
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
rootSU said:
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
Click to expand...
Click to collapse
Does this apply for the stock rom? I'm rooted, but still stock...
providedbike said:
Does this apply for the stock rom? I'm rooted, but still stock...
Click to expand...
Click to collapse
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
rootSU said:
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
Click to expand...
Click to collapse
Ok great that's very helpful, thanks!
providedbike said:
Ok great that's very helpful, thanks!
Click to expand...
Click to collapse
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
rootSU said:
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
Click to expand...
Click to collapse
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
providedbike said:
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
Click to expand...
Click to collapse
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
rootSU said:
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
Click to expand...
Click to collapse
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
providedbike said:
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
Click to expand...
Click to collapse
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
rootSU said:
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
Click to expand...
Click to collapse
Great I'll do it tonight
i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...
Updating your recovery to the latest TWRP (2.8.1.0) should solve your problem.
It's a known issue.
What's the exact error you get please?
Transmitted via Bacon
babbo96 said:
i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...
Click to expand...
Click to collapse
if your rooted why are messing around with an ota anyways. Download one of Calkulins completely stock zips and your done
timmaaa said:
What's the exact error you get please?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah we need the exact error to see what's going on. Other than that, ota zip flashing with twrp will work but u might have to manually select the zip...
Download the ota zip yourself into your phone is available in a thread here somewhere search for it, reboot into recovery, select "install zip", browse to the correct ota zip, swipe to flash, clear dalvik then clear cache.
//edit
Just saw you're on 33r. Download ota zip for 38r and 44s. Make sure you flash them in the correct order don't mix them up!
Sent From Bacon
solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?
babbo96 said:
solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?
Click to expand...
Click to collapse
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon
I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon
ek69 said:
I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon
Click to expand...
Click to collapse
i know how to use fastboot(i'm not a genius but i know how to use it basically)
the fact is that i didnt know how to flash factory images so i used it. and i also learned how to do it couse i read the log of toolkit...
FASTBOOT FLASH (modem/system/recovery/logo/etc...) modem/system/recovery/logo/etc.img
timmaaa said:
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon
Click to expand...
Click to collapse
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?
babbo96 said:
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?
Click to expand...
Click to collapse
Yes, all of the gestures are present. It's essentially the exact same ROM but without the fancy lockscreen and camera. The main difference being that it receives merged fixes and commits sooner than CM11S. The best kernel? Stock.
Transmitted via Bacon
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.
It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!
The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!
Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?
playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1
Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon
timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?
Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.
timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.
Hi there,
So my new OPO came with a build of CM11S which doesn't appear to have any OTA updates, or the OTA function has been disabled. I have heard about this new CO12 update (YNG1TAS2I3) which is supposed to fix the touchscreen issues once and for all, and I would like to move up to this latest official build. I would like to keep all of my data partition intact if it can be done because without root, there doesn't seem to be any way of backing up data/apps. I am not rooted so I only have the original stock recovery.
I just want to point out that I don't have any touchscreen issues on this OPO, my first One had these issues and I sent it back and was given a replacement. With this 2nd OPO, I wanted to stay away from lollipop until the issue was fixed in a new update, which seems to have happened now.
My question is, which official build should I flash/install?, and which would be the best method to do this? (without rooting ) I was thinking, flash the latest CM11S and see if the OTA updates will take me up to the latest build
Im currently on CM11.0-XNF9XBS28K - Build No. KTU84Q.
Thanks
See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
donk165 said:
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
Click to expand...
Click to collapse
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Heisenberg said:
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Click to expand...
Click to collapse
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
donk165 said:
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
Click to expand...
Click to collapse
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Heisenberg said:
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Click to expand...
Click to collapse
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
donk165 said:
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
Click to expand...
Click to collapse
Cool, so you're all good?
Heisenberg said:
Cool, so you're all good?
Click to expand...
Click to collapse
Yeah man, all good now, thank you for pointing me in the right direction. That CM11 I started on was weird having no OTA updates, and I was very wary after CO12 on my first OPO and then getting touchscreen problems. I'm glad this new build is out with the fixes. Hopefully I'll never see those issues on this phone now.
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
cesarp3791 said:
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
Click to expand...
Click to collapse
Just unlock your bootloader now, the longer you leave it the more difficult it'll be to backup your internal storage beforehand. You should really have it unlocked anyway as insurance against anything going wrong with your phone. Once you have unlocked it you can flash TWRP recovery, then the correct procedure to go back to CM11S would be to perform a full wipe (system, data, cache, dalvik cache) and then just flash the zip. As far as custom ROMs for this device go, there are many excellent options to choose from that offer extra customisation that you won't find on the stock ROM.
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
uansari1 said:
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
Click to expand...
Click to collapse
The firmware is contained in the official zip.
Heisenberg said:
The firmware is contained in the official zip.
Click to expand...
Click to collapse
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
uansari1 said:
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
Click to expand...
Click to collapse
You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thanks!
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
cesarp3791 said:
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
Click to expand...
Click to collapse
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
uansari1 said:
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
Click to expand...
Click to collapse
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Heisenberg said:
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Click to expand...
Click to collapse
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
uansari1 said:
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
Click to expand...
Click to collapse
That modem should be fine.