Database Info

[Q] Phicomm C230W -> white screen problem (android)

Hey guys,
i have 2 from in the title mentioned device(they're both dual core versions with 512 mb ram), and flashed on both a custom rom, because the stock rom available for it and the stock rom which was on it after shipping were working badly. (slow reaction on starting/stopping applications, crashing and low available memory(ram))
But the custom rom i found for them works great, without any problem until now. (only one of them, both has the same rom, but only one of them is faulty, and i don't think so it's caused by the rom flashing)
The problem occured yesterday evening after 2 days of using after flashing the custom rom. The problem itself is, that the screen became white, fully bright white.
I tried to reboot the phone maybe it just stucked or crashed or something like that, but after reboot, on startup/bootup, i got the same white screen, which became sometimes a bit dimmer, sometimes again bright, but i think that's just the screen backlight, the background remained full white.
I tried to boot into recovery mode, the same happened.
Then i tried to boot into bootloader/fastboot mode through my pc with usb cable plugged in and in adb, i tried to log into the shell. (adb shell). That's works, i can see all the folders and files in the internal storage. Anyways, i flashed back a stock rom(system and boot img, there was nothing else in it) through adb without problem, but the problem still remained.
I think the problem is related to the screen, or some cable contact failure or maybe the gpu?
Any suggestion what could be the problem, and what can i do against it?
Thanks for your answer and help in advance.
Matt
PS: i wanted to post the links to the roms too, but i don't have enough post yet.

[Completed] Kindle Fire HD7 stuck on TWRP boot logo after CM13

help needed !!
I have a KFHD7(tate) and had been running CM12.1 for a while with only an occasional update using the nightly builds, I only updated occasionally as the unit would not always turn on at the first attempt and would stick at the CM boot logo, after switching it off and back on the unit would run quite smoothly, however none of the updates seemed to cure the problem.
I noticed that there was a new release 'cm-13.0-20160218-UNOFFICIAL-tate' which I flashed via TWRP along with 'open_gapps-arm-6.0-stock-20160301', these were flashed at the same time.
after a reboot the KFHD7 worked fine with no apparent problems, I then downloaded one of the dark themes,(not sure exact one) and this seemed ok at first, I entered the settings screen and only a few words and graphics were visible!
I rebooted back into TWRP recovery and performed a factory reset from within TWRP ... big mistake, now the unit only boots to the blue TWRP boot screen and blinks off after a few seconds it is stuck in a loop and I dont know how to recover it, I have tried the usual combinations of holding the power and vol buttons but still comes on the same .. any suggestions would be appreciated (dumbed down solutions please as not that techy, but can muddle through if step by step instructions)

Hello,
Welcome to XDA.
Try posting your issue in the thread linked below that you got your ROM from.
http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-marshmallow-t3315075
The experts there may be able to help. Good luck.

Need help after failed rom install

I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.

Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.

Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.

Unable to enter TWRP, boot to OS, or enter recovery

Hello, i have seemed to have bricked my phone in a way I can't recover from. I can reach the Fastboot on my phone, but I can't do anything after that. Trying to boot to TWRP to the phone with fastboot will send it to a black screen with a solid white light. Attempting to enter the stock recovery on the phone also goes to the same black screen with a white light.
I have tried using the flashing tool in https://forum.xda-developers.com/t/rom-stock-fastboot-op6-stock-fastboot-roms-for-oneplus-6.3796665/, but I'm not sure if i got the right file set, as I only remembered that I had Oxygen 9 on my phone.
Lastly, I have tried to use the MSMdownloadtool to fix the issue. I have tried multiple versions from multiple sites, but the progress always gets stuck at 'param preprocessing' while the phone sits at a black screen with a green solid light
Any help on this will be nice. I am using a OnePlus 6 A6003. I would also like to add that while in the fastboot mode, the Bootloader version and the Baseband versions are blank

Just wanted to state I have got the issue fixed. I found the website https://onepluscommunityserver.com/ that had a version of MSM that worked for me.

Recovery boot loop and OS boot loop on HTC m8, lineageOS 18.0

I tried to install Lineage 18.0 ( lineage-18.0-20201109-UNOFFICIAL-m8.zip ) on my old HTC m8.
I had previously installed CyanogenMod on it 6(?) years ago, so it was rooted, unlocked, and already had an old TWRP.
I updated TWRP to twrp-3.5.2_9-0-m8.img and got an unofficial lineage 18.0 zip
TWRP installed this fine, I went through the Lineage setup - wifi, time zone etc. It seemed to be working fine. I wanted to sideload an APK from TWRP so restarted the whole phone.
Now there are two problems that prevent me using the phone, and fixing either one of them should be enough for me to fix things.
1) TWRP seems to have disappeared to be replaced with nothing interactive. If I hold power+vol down to get to the menu that le5ts me choose RECOVERY and select RECOVERY it will do one of two things, unpredictably - (1) stay on the white 'entering recovery' 6 seconds, then black 2 seconds then back to 'entering recovery' in a loop, OR (2) it will move onto the Lineage OS boot screen (black with a little animation), get to the home screen and crash back to the Lineage OS loading screen then loop through this continuously.
I see from the Lineage official site that the m8 is only up to 17.1, and they have their own Recovery (I didn't install Lineage's recovery). So this is perhaps mostly my own fault, but I'd like to get back control of the phone and try an official ROM.
Some questions:
1) How do I tell if I still have TWRP somewhere? Can I get back into it to load up a more stable older Lineage OS?
2) Is there any recovery at all? I assume there must be to get the Lineage OS loader started. There's nothing interactive or message about what recovery is running.
3) As I can't get to a functional normal working phone I can't do USB debugging. Can I use the adb commands against the phone if I have it connected by USB and sitting on the FASTBOOT screen from the boot loader? (not sure if I've got the right terminology there, this is the white screen with the two or three bootup items that you navigate with vol up / down and power).
4) Is there anything I can do with the Lineage OS startup so it doesn't just loop upon showing the home screen? Some sort of safe boot mode? I saw an older post saying to hold vol down once the OS boot animation screen starts, but that doesn't seem to do anything for me.
5) Complication - ADB didn't seem to work with this phone any more, even before I got it into this state, perhaps because of age, but it did work many years ago (different PC, USB cable). I think the only way I can get any new content onto the phone is through the external SD card, but even then I need to get to TWRP or something interactive to do anything with the card content.
Thanks for any advice you can offer.

My recommendation:
Take it to authorized service center and let them try to fix it.

jwoegerbauer said:
My recommendation:
Take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
Ebay has them from something like $30 - $60 used, so I don't think its going to be worth paying for a fix. Given that it's rooted and about 7 years old I strongly suspect that it is no longer covered by the warranty (is HTC still in business?). Still a very nice phone for its time - brushed metal body, solid, great stereo speakers, reasonable screen, in 'near new' condition even now. In a few ways better than my S8.
I suspect it will be going for recycling or an aggressive 'ifixit teardown' style post mortem if nothing comes up here.