Hi all,
Was wondering if anyone else is experiencing the same problem? My OPO has no backlight after it boots up. The backlight is fine during the initial boot up (the powered by android page) but it disappears right after that page. Everything else works fine! How do I know? I shine torchlight onto the screen and I can see the LCD pixel to be working but NOT the backlight. Any help? Thanks!
Unlocked and rooted with CM12 nightlies installed before backlight disappeared. Done everything suggested for corrupted memory, bootloop, hard bricked etc. I am currently on stock unrooted CM11s with stock recovery.
How did you flash CM11S back onto your device?
Transmitted via Bacon
Fastboot mode, unzipped CM11S and flash images.
You flashed everything from within the stock image zip?
Transmitted via Bacon
Yup I did. I followed the exact instructions for changing from colour OS to cm11s, I reckon that is the best way to restore the OPO to original state.
It definitely is. Seems like it's possibly a kernel issue, have you tried a custom kernel to see if it changes the situation?
Transmitted via Bacon
Sigh I tried both franco and boeffla and it still does not work. Thanks anyway!
If not working, I suggest you flash Calkulin's Stock CM11S XNPH44S. It's all stock with root. I always use this build when I need go back to stock, saves all fastboot hassle.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
That was what I did before creating this thread. Maybe I should play around with other CM11 roms+their other kernels see which one works
Does the backlight work in recovery?
And I assume (sounds like yes) you did a full factory reset?
Once had a similar problem caused by an 3rd-party app that controlled the backlight. If you did a factory reset that shouldn't be the case, though. logcat?
I tried franco and it works! Not sure why though. At first I was having system ui fc which is a bug with r37+cm12 roms. I reverted to cm11 roms+r37 and it worked. Still, no backlight while booting though, but the backlight turned back on once it finishes booting up. Thanks all!
Related
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.
I noticed recently that when booting up my OPO I see the 1+ logo, however there is a text in the bottom that is cut off.
I noticed this after flashing the Sabermod ROM, but now I have flashed back to BlissPop ROM. There is no issues with the phone or recovery, everything works fine, however its just that boot logo.
Is something wrong with my bootloader or is the boot logo corrupted? See the pic attached.
Don't worry too much, it's due to a bug in the recent CM12 code, I'm sure it'll be rectified soon.
Transmitted via Bacon
I had this issue also but it doesnt affect your phone...
Flash new firmware... I got it from katinatez server... works good...
Okay great! I thought some how I corrupted part of my phone's partition or something.
I thought I messed up my phone too lol but like timmaaa said it's normal, CM did this themselves don't worry about it [emoji106]
Sent From Lollipopified Bacon Goodness!
150206 night bulid had fixed it.
happens to me too with BlizzPop
I did a clean flash of BlissPop's latest ROM (2/11). The corrupted boot logo is still there... If BlissPop's 2-11-15 release is more recent than the CM 150206 nightly buid, doesn't that mean the bug should be fixed?
Hello,
I am facing a weird problem regarding the proximity sensor on all CM11 roms.
I was using lollipop roms for a long time now, and have been following latest builds, until I decided that I liked KitKat more. I already had a backup of temasek's last CM11 build, so I reverted to that one, after flasing the cm11 firmware. All was working perfect until I reverted a backup of my 5.1.1 rom, to try xposed. Again, before doing so, I flashed the latest cm12 firmware. After a couple of days experimenting with xposed, I eventually went back to my kitkat rom. After boot, I noticed that the proximity sensor wasn't working. I had already flashed the cm11 firmware before restoring, but I went and flashed it again. Problem was still there. I then tried cm11s 44s firmware, 05Q firmware and 05Q modem only. The proximity sensor problem was there in all cases. (Shows 0.0cm, like I always have my phone in my ear or pocket). I then tried flashing a complete cm11s rom (05Q) with no success.
This is not a hardware problem, as the sensor is working FINE on ALL lollipop roms. I used sensor box in all my tests. I even tried proximity fix from play store, but it did nothing. I also tried to install it as secondary on multirom, then flash the firmware, but again, no success.
I really really need some help on this one, I can't troubleshoot it on my own, I am out of ideas.
Thanks in advance.
(My device is OnePlus one - always using boeffla kernel on both lollipop and kitkat roms.)
EDIT: Solved. Look at my last post.
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
chazxt said:
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
Click to expand...
Click to collapse
Hello,
Which modem did you flash from that thread? I have only tried the 44s from there but it was a no go.
Thanks in advance.
XNPH44S for me it worked
Hello,
Finally found a fix for my problem.
It seems that I had to flash from fastboot the CM11 nightly modem from here: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
The process doesn't wipe anything in case anyone is wondering, it just flashes the modem ( NON-HLOS.bin)
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
reterosexual said:
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
Click to expand...
Click to collapse
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
berndblb said:
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
Click to expand...
Click to collapse
Thank you so much! I'd been formatting but maybe not properly.
I'll give it a go once it has some charge in it - it's been trying to boot for about 7 or so hours now. I'll report back with anything if it helps.
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
reterosexual said:
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
Click to expand...
Click to collapse
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
berndblb said:
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
Click to expand...
Click to collapse
Thanks for the link, but the official ASUS link in the post you've linked to is dead :/ I'll have a look after work tonight and see if I can find it anywhere else and whether I can get it working or not!
https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
I tried all of the above steps and re-flashed KatKiss to find that the WiFi still did not want to work, which resulted in not being able to get past the setup wizard. I'm not sure what to try next, but at least it was worth a shot. Thank you for your help!
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
berndblb said:
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
Click to expand...
Click to collapse
Just seen this! Yeah, the WiFi worked fine on stock, but any custom ROM I tried had the same issue, so I'm not 100% sure what caused it. I sold the tab on after flashing it back to stock, though.
Thank you for your help though!