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 just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
So i just got a new moto g4 plus XT1642 (UK amazon version) and so of course the first thing i had to do was install a custom rom, so i followed a guide here to unlock it and install TWRP which went fine until i flashed a new firmware, I dont know if i somehow installed the wrong one but now it wont go past the "checking connection" screen on setup without crashing (sometimes it doesnt even get past the welcome language screen) I have tried flashing the stock firmware but it just does the same thing no matter which one i try (XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip is the right one i think?)
If anyone could help me get back to marshmellow it started with then i promise i wont mess around with it again :3
Thanks for any help you can give.
Edit: Okay so I finally just went to do the thing i started out to do which was to install the Resurrection Remix rom (http://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275) so I just thought that maybe if i got it installed it might fix what problems i was having and yeah sure enough i followed what i was supposed to flash first which was (Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63_Stock_Img) btw and then flashed Resurrection Remix and it just started working again, everything seems fine but I'm worried I might have broken something with all my puttering around with its inside ya know?
But the main thing is phone calls work, texts work, it rooted itself magically, can install unsigned apks and such, wifi works and so does the fingerprint sensor which i heard people were having issues with. So should i just not look for problems and enjoy it maybe? I'm glad i got it sorted im some fashion at least
So I HAVE now noticed that some apps seem to hang/crash sometimes, epecially games, not sure if it has to do with my puttering around though Is there anything I can do to check that everything is working ok? any programs that scan for errors or something?
Happy its working don't get me wrong but no issues would be best ^^
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
gabriwinter said:
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
Click to expand...
Click to collapse
Hey, thanks for the input, I did use that when i was having issues but it still caused that crashing at the connection screen issue sso i dont know why it would work for you and not me, perhaps i needed to get it to a working state before i could downgrade again? I dont really want to try it out now and see, the crashing issue seems to be infrequent so its possible its a different issue (software conflicts or ram overusage maybe?). I'll keep using it and see what issues develop
Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...
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.