Related
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
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
Hey,
my proximity sensor is not working after:
-backing up my phone with twrp
-installing another rom
-restoring the backup with twrp
Now the proximity sensor is not working anymore. It's annoying, because my phone turns of while calling.
What can I do to fix this?
I downloaded an app to check the sensor values and it always showed "0" for the proximity sensor. I have no idea how to fix this. I rebooted my phone, installed the backup again, ...
Nothing helped
same problem happened with me today...
i also need solution..
devs plz help..
It's your modern causing the problem most likely. What ROM were you on? What ROM did you change to? What ROM did you go back to?
Transmitted via Bacon
hi,
i ve the same problem! Help......
1º i was the ROM euphoria CM12!
2º i make the restore of stock rom 44s oneplus
3º the proximity sensor dont work!!!!
hi,
Did you solved the problem? how?
thks.
c00l3rf4rm3r said:
Hey,
my proximity sensor is not working after:
-backing up my phone with twrp
-installing another rom
-restoring the backup with twrp
Now the proximity sensor is not working anymore. It's annoying, because my phone turns of while calling.
What can I do to fix this?
I downloaded an app to check the sensor values and it always showed "0" for the proximity sensor. I have no idea how to fix this. I rebooted my phone, installed the backup again, ...
Nothing helped
Click to expand...
Click to collapse
jeronimo.ribeiro.pedome said:
hi,
i ve the same problem! Help......
1º i was the ROM euphoria CM12!
2º i make the restore of stock rom 44s oneplus
3º the proximity sensor dont work!!!!
Click to expand...
Click to collapse
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Newer lollipop ROM are advising you to flash the new alpha modem. If you ever flashed cm12 official alpha, the new modem has been flashed to make proximity sensor on new cm12 code.
It'll break proximity sensor on older cm11s code. Answer is flash older modem like timmaaa said and problem fixed.
Sent From Lollipopified Bacon Goodness!
timmaaa said:
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Click to expand...
Click to collapse
Solved !! Thanks
YES!!
Rohitgomes said:
Solved !! Thanks
Click to expand...
Click to collapse
Dude! Thanks so much! I spent the whole day trying to find at least what had broken the proximity sensor and now it's fixed!!!!!
ek69 said:
Newer lollipop ROM are advising you to flash the new alpha modem. If you ever flashed cm12 official alpha, the new modem has been flashed to make proximity sensor on new cm12 code.
It'll break proximity sensor on older cm11s code. Answer is flash older modem like timmaaa said and problem fixed.
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
It's working again in my case!!! Thanks a lot :laugh:
timmaaa said:
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Click to expand...
Click to collapse
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
b0r0d1nsky said:
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
Click to expand...
Click to collapse
That's because if you're on a Lollipop ROM you need to flash a Lollipop modem.
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
timmaaa said:
That's because if you're on a Lollipop ROM you need to flash a Lollipop modem.
Transmitted via Bacon
Click to expand...
Click to collapse
I tried all modem at page you gave me - same problem.
I solved problem by flashing old cm12 nightly (cm-12-20150106-NIGHTLY-bacon) - it works, but if i'll try update it - it will cause problem again
P.S. I extracted NON-HLOS.bin (it's modem file, right?) from this old nightly , i flashed last cm12 nightly and after that i flashed extracted modem via fastboot - it didn't help me
b0r0d1nsky said:
I tried all modem at page you gave me - same problem.
I solved problem by flashing old cm12 nightly (cm-12-20150106-NIGHTLY-bacon) - it works, but if i'll try update it - it will cause problem again
P.S. I extracted NON-HLOS.bin (it's modem file, right?) from this old nightly , i flashed last cm12 nightly and after that i flashed extracted modem via fastboot - it didn't help me
Click to expand...
Click to collapse
Why try all of them? Most of those modems are KitKat modems. Are you on the right firmware? And yes, NON-HLOS.bin is the modem, but it's only part of what's required. The Lollipop modems from Boeffla and the Lollipop firmware should fix your problem.
Transmitted via Bacon
timmaaa said:
Why try all of them? Most of those modems are KitKat modems. Are you on the right firmware? And yes, NON-HLOS.bin is the modem, but it's only part of what's required. The Lollipop modems from Boeffla and the Lollipop firmware should fix your problem.
Transmitted via Bacon
Click to expand...
Click to collapse
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
b0r0d1nsky said:
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
Click to expand...
Click to collapse
b0r0d1nsky said:
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
Click to expand...
Click to collapse
There's no point in flashing the KitKat modems, they'll only cause the problem, not fix it. If the Lollipop modems didn't work for you, you're doing something wrong. Like maybe you're on the wrong firmware, you never answered my question asking which firmware you're on.
And no, you can't just edit the zip to remove the adaptive backlight feature, you'd need to fork the CM12 repo and remove that commit, and then build the ROM from source.
Transmitted via Bacon
timmaaa said:
ou never answered my question asking which firmware you're on.
Click to expand...
Click to collapse
i am on CM12 nightly (cm-12-20150106-NIGHTLY-bacon) now and i wanted to install the last nightly.
I found the solution - my friend with same OPOphone will disable "adaptive backlight" and he'll made TWRP backup, i'll flash it today.
thank you very much for help. :good:
UPD. Forgot to say - modem isn't the main reason, the adaptive backlite and my proximity sensor - are the problem... maybe sensor is broken
b0r0d1nsky said:
i am on CM12 nightly (cm-12-20150106-NIGHTLY-bacon) now and i wanted to install the last nightly.
I found the solution - my friend with same OPOphone will disable "adaptive backlight" and he'll made TWRP backup, i'll flash it today.
thank you very much for help. :good:
UPD. Forgot to say - modem isn't the main reason, the adaptive backlite and my proximity sensor - are the problem... maybe sensor is broken
Click to expand...
Click to collapse
The modem is the problem, the proximity sensor is governed by the modem. The way the proximity sensor is handled changed when they released Lollipop. Adaptive backlight has absolutely nothing to do with it, you're mistaking a symptom of the problem for the cause. Of course adaptive backlight is going to cause problems, it relies on your proximity sensor, which in turn relies on the modem. The cause of the problem is the modem, without doubt. Hundreds of people have had the exact same problem.
Transmitted via Bacon
timmaaa said:
Hundreds of people have had the exact same problem.
Transmitted via Bacon
Click to expand...
Click to collapse
but all that people solved this problem by flashing lollipop modem... why it doesn't helped me?
ok, lets start again
1) I had cm 11S
2) installed TWRP
3) flashed cm12 nightly from official site
4) i tried to flash other lollipop roms from xda
5) after all faults i returned to cm 11S
6) I posted my problem here
7) now I am on cm-12-20150106-NIGHTLY-bacon - it works... but if i'll go to settings -> screen and will enable the adaptive backlight - it will cause same problem!
b0r0d1nsky said:
but all that people solved this problem by flashing lollipop modem... why it doesn't helped me?
ok, lets start again
1) I had cm 11S
2) installed TWRP
3) flashed cm12 nightly from official site
4) i tried to flash other lollipop roms from xda
5) after all faults i returned to cm 11S
6) I posted my problem here
7) now I am on cm-12-20150106-NIGHTLY-bacon - it works... but if i'll go to settings -> screen and will enable the adaptive backlight - it will cause same problem!
Click to expand...
Click to collapse
That isn't what you said in your initial post. This is what you said:
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
Click to expand...
Click to collapse
In your first you went from CM11S to CM12 nightly and flashed an incompatible modem. Now you're telling me you went from CM11S to CM12 nightly to other ROMs and back to CM11S. Completely different scenarios. So which is it? It turns out you haven't been very accurate or specific with your information. I'm still waiting for you to answer my question about which firmware you're on (this is the third time I'm asking). If you can't even provide accurate and specific information about what you've done, then you can't expect anyone to be able to help you effectively.
So maybe it's better to ask this way; exactly which ROM do you want to be on? You tell me that and I'll give you links to the correct firmware and modem(s).
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 Guys,
Yesterday I revived notification that new update is available, so not thinking much I installed it. After update I realized that my phone is not getting service, or getting it only outside, for short time.
My current version of CM is 11.0-XNPH05Q. I rooted my phone today and now I am wondering if I can install this version of CM - cm-11.0-XNPH33R-bacon-signed-fastboot_16GB?
I know this might be silly question but I am complete newbie, please advice.
Thank you!
Just flash one of Calkulin's stock rooted ROMs from the dev section, he has one for each CM11S release.
Transmitted via Bacon
timmaaa said:
Just flash one of Calkulin's stock rooted ROMs from the dev section, he has one for each CM11S release.
Transmitted via Bacon
Click to expand...
Click to collapse
hey, I want to downgrade to 44s too (as I have bluetooth problems). I'm fully stock and not rooted at all( :cyclops: ), I updated to 05q manually by flashing zip in stock recovery... can I downgrade the same way? flashing 44s zip (I guess it's full and not incremental like 05q) without wiping anything to keep my data?
FreakyDR said:
hey, I want to downgrade to 44s too (as I have bluetooth problems). I'm fully stock and not rooted at all( :cyclops: ), I updated to 05q manually by flashing zip in stock recovery... can I downgrade the same way? flashing 44s zip (I guess it's full and not incremental like 05q) without wiping anything to keep my data?
Click to expand...
Click to collapse
No you can't, you need to unlock your bootloader and flash the stock images with fastboot to downgrade properly.
Will this void the warranty?
ashrafmansuri said:
Will this void the warranty?
Click to expand...
Click to collapse
Nope. It's pretty much impossible to void the warranty on one of these things. You can unlock the bootloader, you can root it, you can install custom recovery, custom ROMs, custom firmware, custom kernels. Pretty much the only things that void the warranty are bricking it, and physically opening the device up.
Transmitted via Bacon
timmaaa said:
Nope. It's pretty much impossible to void the warranty on one of these things. You can unlock the bootloader, you can root it, you can install custom recovery, custom ROMs, custom firmware, custom kernels. Pretty much the only things that void the warranty are bricking it, and physically opening the device up.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank You for the great info