Database Users

[FIXED] black screen on hboot/recovery and camera issue (FIXED)

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

Phone does not start after reboot on jamal2367 ROM, S4 GE Final-R4

Hi all,
I have this annoying issue with [AOSP] Official 4.4.2 - S4 Google Edition - Final-R4 from jamal2367; current baseband installed XXUFNA1.
Problem:
When the phone loses connection, it dies. Then there is no way I can turn it on.
if unplugged from the power: it starts to boot and it dies again, sometimes at the "samsung boot text", sometimes a bit ahead, but it does not go further than the animated logo with 4 coloured bouncing balls (it does not matter how many time I try to restart the phone)
If plugged: it survives the first part of the boot most of the time, but it loops into the animated logo with the 4 coloured bouncing balls and the phone does not start.
Solution:
Every time I have to re-install Android, by:
- deleting Dalvik, Data, System, Cache.
- Install the ROM
- Apply a factory reset
At this point, if connected to the plug, the phone starts, but I have to go through the manual installation process.
This is a bit annoying I have to admin, anyone with this kind of issue, or am I the only one?
A few more info:
Phone was working great with jamal2367 4.3 (don't remember the baseband)
After 4.4 was out I installed it, but it was booting every 5 minutes or so, I decided then to go back to 4.3.
When I went back to 4.3, baseband was changed, but I kept the hold one.
Phone started to have random reboots as well, but once every 3-4 days, so I was ok with it.
4.4 releases were progressing so, after a while I decided to put it back.
I had the problem described above with previous (recent) baseband (like ml6and mj6).
Now I have the latest, but I have got the problem anyway.
A wild guess:
The phone now charges very quickly, I am wondering if the percentage that I see is realistic. Maybe it runs out of battery, which it could explain why the phone dies on reboots, but it does not explain why it loops once plugged in and why it does not turn off normally instead of just dying with a blink of an eye.
mmm that should not be the reason
Another wild guess:
I couldn't target a specific application. Sometimes it dies using fb, sometimes maps, sometimes hangout, sometimes a after a long phone call. The first two have "location" active, but I don't think that the last two are using it.
mmm that should not be the reason either.
A consideration:
I have noticed that once Android is installed, the phone signal is quite good, but then it goes down to one or two lines only. Most of the time I have one line only (in my area) and when it disappear, 6 times out of 7 it dies.
Thanks in advance.
R
PS=I could not post this into "Galaxy S 4 i9505 Android Development"

too long
be sure to flash from zero, wipe everything then flash 4.3
if everything fils go to stock 4.3 or 4.4 TW, then flash 4.4 gpe after

racoonlab said:
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
Click to expand...
Click to collapse
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care

anu.cool said:
did you try battery calibration?
Click to expand...
Click to collapse
Nope I will give it a try
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Well, when I delete Dalvik, Data, System and Cache, I do it once I am inside _teamwin recovery_, I can also think about another ROM, but the one from jamal2367 is quite popular and I find it weird that no one else have the same issue.
Thanks for your reply though.
R

Same problem here...
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!

opticus44 said:
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
Click to expand...
Click to collapse
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R

Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655

Xv1nX said:
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Click to expand...
Click to collapse
mmm there must be some way. With the latest R1.1 I cannot even answer a phone call, with Ktoonsez's Kernel, with Alucard's Kernel no button works.
:-O

mmm also installing 4.3 back gives me random reboots. I am wondering if it could a wrong baseband.

it worked perfect for me for some hours. when i deactivated some bloatwares (g. earth, g. music, ...) it crashed and stucks in a loop reboot & crash at googke logo. swipe cache or wait some minutes don`t change anything.
i tried everything, now i have no idea what to do

I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R

anu.cool said:
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Hi,
What tool do you use for a battery calibration?

racoonlab said:
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
Click to expand...
Click to collapse
Same issue if I put back Jamal [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1,mmm, maybe the kernel....

The last thing I can say about it is that also all the sounds are gone. I cannot reproduce any sounds, notifications, alarm etc., it does not work on videos either.

I fix my problem! And I shared the solution here:
http://forum.xda-developers.com/showthread.php?p=49502855

racoonlab said:
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Click to expand...
Click to collapse
Sorry, long time since I last checked in. I downloaded official stock image from sammobile and flashed through odin.

same problem here
Hi guys same problem here,
GOOGLE EDITION 4.4.2 installed by Danvdh, Kryten2k35 & Ktoonsez on Galaxy S4 GT-9505 LTE with knox 0x1, and TWRP custom recovery when the battery reaches 0% turns off the phone I put the phone on charge and starts but hangs on colored dots.
How can I fix this?
Thx

Problem with touchscreen since 4.4.2 update

Hey there
A friend of mine has the following problem with his Note 3 (completely stock).
Since the latest 4.4.2 OTA update, sometimes suddenly the screen does not respond to touching it with your hand. It does react to the stylus.
Locking and unlocking the screen does the job, but only for a few minutes.
I wiped the phone via stock recovery, but the problem persists.
Anyone with the same problem, or maybe a clue?
Thanks!
GT-i9300, CM11, Boeffla

joriswagter said:
Hey there
A friend of mine has the following problem with his Note 3 (completely stock).
Since the latest 4.4.2 OTA update, sometimes suddenly the screen does not respond to touching it with your hand. It does react to the stylus.
Locking and unlocking the screen does the job, but only for a few minutes.
I wiped the phone via stock recovery, but the problem persists.
Anyone with the same problem, or maybe a clue?
Thanks!
GT-i9300, CM11, Boeffla
Click to expand...
Click to collapse
Hi
Same problem here,I tried several 4.4.2 official and custom roms but not fixed and I tried these too:
I tried mega wipe and last rom in samfirmware!
I removed my external sd card
And I googled and found there are others with same problem so it shouldn't be hardware problem
p.s.When screen freezes just half of it works! And just doesn't work by fingers and it works by s_pen!
There no way to come back to 4.3 too
What should I do?
Ty in advance

Finally Solved!
Hi
I had same problem
I did everything u said like:
mega wipe and changing rom
custom roms
taking out battery when it's on ( I Did this but I don't know It had any effects on my phone or not!)
taking out external card
But I still Had the Problem
Solution:
But I had a flip cover and I separated that from phone and thanks God,surprisingly It's Fixed and it works like a charm!!! after that I used my original cover and there is no problem till now.
Good Luck

Had the same issue posted it here bit no one responded.
Solution: The flip case I had..there's a problem with it where it locks the screen even when the case is not closed. But lately I had no issue it just seem to gotten fixed by itself.
Sent from my SM-N9005 using XDA Premium 4 mobile app

BLack screen after installing any rom

On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)

zxsq said:
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
Click to expand...
Click to collapse
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.

robertofelce said:
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
Click to expand...
Click to collapse
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
Remember that rr marshmallow releases don't work for SM N900. I guess that your phone is sm N9005. Right?
If it is, is awkward that you can't flash a rr marshmallow ROM

You should be in the T-Mobile note 3 forum?
Cm12.1 for the hltetmo: https://download.cyanogenmod.org/?device=hltetmo

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
got exactly the same problem....Tried to flash repair stock rom with pit, with success, but doesn't change anything
can flash 5.0 stock or 5.1 port rom but not CM or AOSP..
if you find what happen....

Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.

rikymatteo97 said:
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
Click to expand...
Click to collapse
My note 3 smnN900t is doing that same thing and it sucks because I know I did everything perfectly!! What Kernel were you able to flash for it and where did you download it from? By the way thanks in advance for any help and info you can give!!!

Wrong forum
forum links .
http://forum.xda-developers.com/showthread.php?t=2574886

Please help I am having the same issue. Did anyone find a solution for this ?

Custom ROMs result in black screen

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.