Related
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
simms22 said:
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
Click to expand...
Click to collapse
Is there a way to get the factory img onto the phone via TWRP?
Does the bootloader still work?
BirchBarlow said:
Does the bootloader still work?
Click to expand...
Click to collapse
Yes, I'm able to get into TWRP/recovery mode.
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then, you are fine, friend:victory:, just do what the guy upstairs said. (simms22)
wipe system, caches, Flash another Rom/kernel for N5
Fastboot flash /boot boot.img
Sent from my Nexus 5 using XDA Premium 4 mobile app
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then what's the problem?
He's safe. He just needs to flash using fastboot.
This is the reason why Nexus devices are awesome.:angel:
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
The point in the bootloader is for this very thing. Just plug it into your pc and fastboot it
Unless you have a kernel/ rom zip or backup already in the memory then just use recovery
Sent from my Nexus 5 using Tapatalk
gee2012 said:
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
Click to expand...
Click to collapse
Thank you, everyone. Disaster aborted.
I unlocked, rooted, installed the new AOSP on my OPO and now it won't boot past the Logo and Powered by Android screen.
I can still get into the recovery, but that's about it.
I'm newish. Help please.
Did you make a nandroid backup before flashing the new ROM?
Transmitted via Bacon
timmaaa said:
Did you make a nandroid backup before flashing the new ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope. I followed a tutorial and it didn't even mention that. I can get into recovery and still see the AOSP.zip and the GAPP.zip, but don't know where to go from there.
Ok, well lesson learned I guess, always make a nandroid backup and keep it on your phone in case of emergencies like this. You can either adb push another ROM zip to your phone and flash that, or you can fastboot flash the CM11S fastboot images.
Transmitted via Bacon
---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------
You'll find the CM11S fastboot images here:
https://cyngn.com/products/oneplusone/
Flash those, then get it booting, then make a nandroid.
Transmitted via Bacon
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
Or you can follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=2826541
But, stop after step 3 because step 4 will relock your bootloader.
Transmitted via Bacon
GMoore34 said:
I unlocked, rooted, installed the new AOSP on my OPO and now it won't boot past the Logo and Powered by Android screen.
I can still get into the recovery, but that's about it.
I'm newish. Help please.
Click to expand...
Click to collapse
I'm guessingnyou didn't the a complete wipe in twrp before installing AOSP? Because same happened to me, got stuck at boot screen. As previous person Said: download CM11S rom zip File again On Ur pc. Then boot phone into twrp recovery. Then connect to pc, and push the CM11S zip file into Ur phone using CMD. I trust u know how to do this.
Sent from my SGP512 using Tapatalk
If you have a USB OTG cable you can mount a usb storage device from the recovery and push the rom file to the internal storage of your device.
Anyways...Read twice, flash once. Do you even know what a nandroid backup is?
Probably not, the guide thread in my signature explains how to do it in detail.
Transmitted via Bacon
timmaaa said:
Probably not, the guide thread in my signature explains how to do it in detail.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks all!
I used fastback and flashed the stock image back and all is good. Now to figure out how I screwed it up...
Any roms really worth flashing at the moment?
GMoore34 said:
Thanks all!
I used fastback and flashed the stock image back and all is good. Now to figure out how I screwed it up...
Any roms really worth flashing at the moment?
Click to expand...
Click to collapse
All of them are worth flashing. It just depends what kind of rom you're looking for. And all of them are stable so you won't have to worry about stability.
The most popular rom? Probably Mahdi by forum post views. Mahdi is a mix of every gesture from all roms while maintaining performance. The choice is yours though.
Sent from my One using Tapatalk
GMoore34 said:
Thanks all!
I used fastback and flashed the stock image back and all is good. Now to figure out how I screwed it up...
Any roms really worth flashing at the moment?
Click to expand...
Click to collapse
They're all worth flashing. Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so we shouldn't be answering that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Transmitted via Bacon
I flashed a custom rom on my oneplus one and since then i am unable to boot ,The logo comes and after that the screen keeps on blinking. I cannot even boot into recovery mode. please help.
Tahakhasam said:
I flashed a custom rom on my oneplus one and since then i am unable to boot ,The logo comes and after that the screen keeps on blinking. I cannot even boot into recovery mode. please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/one...return-opo-to-100-stock-t2826541/post54365948
So as the title said no matter what i tried to do to the phone, reflash the stock and everything (it is my friend 1+1 so i dont know how it happen) and still i stuck in a bootloop.
anyone know how to fix it? if you do please help, thanx ahead!
Without knowing what caused the problem it's a bit difficult to help. Why isn't your friend posting? We need to know what he did to the phone.
Transmitted via Bacon
timmaaa said:
Without knowing what caused the problem it's a bit difficult to help. Why isn't your friend posting? We need to know what he did to the phone.
Transmitted via Bacon
Click to expand...
Click to collapse
He said that he was with the phone in the toilet and it just started to boot loop, he didn't flash anything (he doesn't know about those kind of things) so the phone had a stock kernel with stock frameware
Sent from my One using XDA Free mobile app
Ok, well you should be able to hold the power button to force it to shut down. Once it's off you can use the volume up + power button combo to get it into fastboot mode (hold volume down, then hold power, it should boot directly into fastboot mode). Once in fastboot mode you need to unlock the bootloader, and then flash the fastboot images, I have detailed instructions for both in my guide thread (link in my signature).
Transmitted via Bacon
timmaaa said:
Ok, well you should be able to hold the power button to force it to shut down. Once it's off you can use the volume up + power button combo to get it into fastboot mode (hold volume down, then hold power, it should boot directly into fastboot mode). Once in fastboot mode you need to unlock the bootloader, and then flash the fastboot images, I have detailed instructions for both in my guide thread (link in my signature).
Transmitted via Bacon
Click to expand...
Click to collapse
Ye actually i tried it already with no success, any different idea?
solokiller11 said:
Ye actually i tried it already with no success, any different idea?
Click to expand...
Click to collapse
You tried which part?
Transmitted via Bacon
timmaaa said:
You tried which part?
Transmitted via Bacon
Click to expand...
Click to collapse
to unlock the bootloader and flash the fastboot images again, it didnt work
Please provide more information, I need specifics, details, anything and everything that's relevant, otherwise it's virtually impossible to help you.
Transmitted via Bacon
timmaaa said:
Please provide more information, I need specifics, details, anything and everything that's relevant, otherwise it's virtually impossible to help you.
Transmitted via Bacon
Click to expand...
Click to collapse
what info shuold i provide? like what files?
What files you used, what steps you did, how did the phone react, everything in details. the more info you give Timmaaa the more he will be able to zero in on your problem .
timmaaa
The steps i did:
1. unlocked the bootloader
2. flash the stock cm11s 44s
3. the fastboot showed that eberything is ok
4. the phone booted and after 2 sec it start to bootloop again
5. thats it! i did nothing more
solokiller11 said:
timmaaa
The steps i did:
1. unlocked the bootloader - How did you do this ? command lines ? Toolkit ?
2. flash the stock cm11s 44s - What files exactly did you use ?
3. the fastboot showed that eberything is ok - What was the message ?
4. the phone booted and after 2 sec it start to bootloop again
5. thats it! i did nothing more
Click to expand...
Click to collapse
1. unlocked the bootloader - How did you do this ? command lines ? Toolkit ?
2. flash the stock cm11s 44s - What files exactly did you use ?
3. the fastboot showed that eberything is ok - What was the message ?
Cholerabob said:
1. unlocked the bootloader - How did you do this ? command lines ? Toolkit ?
2. flash the stock cm11s 44s - What files exactly did you use ?
3. the fastboot showed that eberything is ok - What was the message ?
Click to expand...
Click to collapse
1. fastboot oem unlock
2. https://www.androidfilehost.com/?fid=95784891001613103 those files
3. after each flash the message was that the flash was ok (the normal message after flashing the file, nothing spacial)
solokiller11 said:
timmaaa
The steps i did:
1. unlocked the bootloader
2. flash the stock cm11s 44s
3. the fastboot showed that eberything is ok
4. the phone booted and after 2 sec it start to bootloop again
5. thats it! i did nothing more
Click to expand...
Click to collapse
This is the information I needed. Check this out:
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
I'm not sure if that'll help but it's worth a try.
Transmitted via Bacon
timmaaa said:
This is the information I needed. Check this out:
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
I'm not sure if that'll help but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
Man!!!! Tank You Very Very Very Much for your help!!!! It worked like a charm!!!!
solokiller11 said:
Man!!!! Tank You Very Very Very Much for your help!!!! It worked like a charm!!!!
Click to expand...
Click to collapse
Oh sweet [emoji106]
Transmitted via Bacon
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.
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