Only the Chrome notifications on my phone have black text and are too hard to read. I'm using Nova Launcher, but i've tried also with default launcher but nothing has changed.
I've tried different themes, but nothing to do..
There is some method or app to avoid this problem?
Try doing a factory reset, or try clearing the app's data, it might help.
DigiGoon said:
Try doing a factory reset, or try clearing the app's data, it might help.
Click to expand...
Click to collapse
Of course i've already done. Isn't a rom problem, because i've this problem from first rom (lollipop) now i'm on B370 and still have this problem.
Okay try this once, flash the whole firmware package by following these steps:
Download your phone's latest firmware.
After doing this put the UPDATE.APP in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
This might solve it.
walter4991 said:
Of course i've already done. Isn't a rom problem, because i've this problem from first rom (lollipop) now i'm on B370 and still have this problem.
Click to expand...
Click to collapse
This is a well known problem due to EMUI themes. I bet if you change the desktop background to one with more bright colors you will see the notifications.
Try to update to B371, backup, factory reset and play a little with the themes.
I think Colors or Vui themes solve this. Something that also could be solved in the EMUI theme engine or build.prop. I don't know for sure.
Related
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
wesley.neary said:
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
Click to expand...
Click to collapse
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
imadork8317 said:
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
Click to expand...
Click to collapse
I did try try that however it didnt replace the missing apps.
wesley.neary said:
I did try try that however it didnt replace the missing apps.
Click to expand...
Click to collapse
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
>> Download tf201-jb-twrp-recovery.blob and flash it via fastboot (fastboot -i 0x0b05 flash recovery tf201-jb-twrp-recovery.blob) and reboot.
Click to expand...
Click to collapse
Go back and follow the steps again
INSTRUCTIONS:
1. Download the ROM update zip (us-tf201-jro03c-10.4.2.15-stock-deodexed.zip)
2. Download the Superuser update zip (Superuser-3.2-arm-signed.zip)
3. Copy the files to your device and reboot into recovery
4. Wipe data/factory reset [VERY IMPORTANT STEP!! Just use the recovery wipe/factory reset, do not use any full wipe update zips or scripts]
5. Flash the ROM update zip and immediately after that, flash the Superuser update zip.
6. Reboot your device and wait for the new bootloader, kernel & recovery to flash (the blue progress bar) and then let the device boot up.
7. Enjoy JB on your device!!
Click to expand...
Click to collapse
imadork8317 said:
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
Go back and follow the steps again
Click to expand...
Click to collapse
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
flumpster said:
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
Click to expand...
Click to collapse
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
wesley.neary said:
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
Click to expand...
Click to collapse
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
flumpster said:
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
Click to expand...
Click to collapse
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
wesley.neary said:
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
Click to expand...
Click to collapse
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
flumpster said:
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
Click to expand...
Click to collapse
Ok how can i tell if i still have adb and if so whats the best file to try and push.
wesley.neary said:
Ok how can i tell if i still have adb and if so whats the best file to try and push.
Click to expand...
Click to collapse
You need to have the adb files on your computer. Open a command prompt where adb files are by holding down shift and right clicking on the folder adb is in and selecting open command prompt here. Then type adb devices into command window.
if you get waiting check in your device manager to see if you have any devices with explanation marks on it. If there are then install naked drivers from the top of developer section.
This only happens in landscape mode.
I've found a thread on it: http://forum.xda-developers.com/showthread.php?t=1594959
I've rebooted several times and tried both Nova Launcher and trebuchet. The problem remains. Any fix?
Thanks
redhonker said:
This only happens in landscape mode.
I've found a thread on it: http://forum.xda-developers.com/showthread.php?t=1594959
I've rebooted several times and tried both Nova Launcher and trebuchet. The problem remains. Any fix?
Thanks
Click to expand...
Click to collapse
try to reflash the rom, make sure you do the right things when flash the rom, don't miss any parts
Don't forget to hit THANKS button
nasheich said:
try to reflash the rom, make sure you do the right things when flash the rom, don't miss any parts
Don't forget to hit THANKS button
Click to expand...
Click to collapse
This is already tried. Flashed 3 times. One zip file.
Somebody suggested installing Xposed Framework manually, which put me in a bootloop. Uninstall seemed to work, but then after restarting to clear the cache, the phone now constantly goes into a loop again.
I have tried installing stock firmware in a dload folder on the SDCard, but that gives me a 'software install' failed error after around 10%
Obviously my next option was to flash the stock firmware in fastboot mode, but when I extract the update.app there's no proper filenames and the Huawei Finder application doesn't seem to work with the H7 firmware.
Pretty much completely out of ideas, so any suggestions would go a long way.
Fixed it now by formatting my SD card and downloading the L01 rom from the Huawei site.
Did you get xposed to work or is it a NO GO? I really wanna try Xposed, but my guts tells me that it's not gonna work because of the EMUI..
mamboboy said:
Fixed it now by formatting my SD card and downloading the L01 rom from the Huawei site.
Click to expand...
Click to collapse
do you have a link to the L01 european rom...Thanks
kjettern said:
Did you get xposed to work or is it a NO GO? I really wanna try Xposed, but my guts tells me that it's not gonna work because of the EMUI..
Click to expand...
Click to collapse
No go unfortunately. Flashing it in TWRP puts you in an endless bootloop, I fixed it by running the uninstaller, but the phone felt laggy after that. So I went back to TWRP and cleared the cache which was when the bootloop came back. Whether that's to do with the botched Xposed installation or a bug in TWRP, I don't know!
sheridan2000 said:
do you have a link to the L01 european rom...Thanks
Click to expand...
Click to collapse
It is here:
http://www.hihonor.com/es/pages/support#?view=downloads
The top one, 'PLK-L01C432B100 Upgrade Software UK'
I didn't download it initially and was trying ones from NEEDROM (which seemingly won't work on EU phones) because it says it's for the Honor 4X in the description, but turns out that's just a typo. Worked first time using the dload/UPDATE.app and volume up + down while plugging USB cable in method
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Flash fastboot rom and root again.
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
at4500 said:
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
Click to expand...
Click to collapse
Wipe data, cache, and dalvik, and reinstall your ROM. You will lose all your data, downloaded apps, and settings (I hope you made backups of them), but you will have your phone back.
at4500 said:
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Click to expand...
Click to collapse
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
MyNameIsRage said:
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
Click to expand...
Click to collapse
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
at4500 said:
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
Click to expand...
Click to collapse
Good news. You probably only needed to wipe the data partition - but you might as well start afresh.
BTW, I have been using supersu for a long time, without any problems. So I would very much doubt whether rooting via supersu was the cause of the problem. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". I have not done that in years, and I am not sure why anyone would want to do it now.
There is no harm trying magisk, but I prefer supersu myself.
DarthJabba9 said:
.. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". ..
Click to expand...
Click to collapse
Right, this is (silly of me) exactly what i did.