hi everybody, first of all I want to apologize for my English, the translator of google helped me a little.
I have a a500 with the "bootloader sklilax_cz V8" and ROM "CyanogenMod 4.3.1 v8". I have proven other ROM's but always the same problem arises: two strips of pixels that do not respond to touch.
i68. tinypic.com/eb6f49.png
i67. tinypic.com/azgtao.png
When the tablet still had the boot loader and the factory system, everything worked fine. He never had a stroke or a fall, so I assume it is not a hardware problem.
But I still have not found a solution. Any suggestions?
Thanks in advance.
sounds like hardware problem
you could install stock rom again and see if problem is still there
Related
During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb
hi,
i installed cm 7.1.0. after a week or so, the touchscreen stops working properly. i wiped using the calkulkin erase all zip. tried flashing again and erasing then other stable version. touchscreen continues to play up. finally flashed with sun rom. home key and eome keyboard keys still dont work. any suggestions?
cheers paul
It's obviously a hardware issue if it persists across ROMs (Not that a ROM can ever cause a touchscreen to play up randomly)
which bit
thanks 3xeno,
any ideas on which bit - controller or screen itself? I can replace the screen and the receiver.
Cheers Paul
I have similar problems any progress with this?
Hi all. I flashed my stock 2.2 Milestone 2 to the MS2Ginger 3.0 about a month ago. Everything was working just fine. But after one to two weeks of use, some minor bugs started to trouble me. I am a Chinese user and I used Moto Smart HandWriting for Chinese input. Everytime i tap on a message box or anywhere else to input text, the screen goes blank. The machine is still responsive and I am still able to go back by pressing the back button. The only way i can input text now is to use other IMEs.
Another thing is that my physical keyboard started to get double bouncing which was initially alright after flashing the rom.
I figured that it is something related to the data/cache or something else because the phone was okay just after flashing the rom. So i booted into bootmenu and do the double wipe to clear all the setting on the phone. But when i rebooted into the system, everything was still there. Lock screen password, messages, account settings,etc. All of it was still there.
I then tried to flash the MS2Ginger again following walter's post in android development forum. Again, nothing was resetted.
I am very annoyed. Can anyone provide some advice? Thank you.
hi, i think this should fix your physical keyboard problem... worked for me
http://forum.xda-developers.com/showthread.php?t=1058544
Hey there everybody! First of all, Brazilian here so sorry for any weird typos and mistakes.
I was attempting to flash a custom ROM in my Moto X Play XT1563. What I got was a fully flashed phone but with a lost IMEI (which I am already pretty certain I won't get back as I didn't back it up, yep I messed up) and an unresponsive touchscreen. It KINDA works if I tap randomly many times on specific spots of the screen but the phone becomes completely useless with it.
Most threads I found about this subject have led me to think that I need a new digitizer for my phone. My question is: is there anyway to know if replacing the digitizer will get the touchscreen to work again? I have tried to flash a stock ROM but it's still unresponsive
Thanks in advance!
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.