Related
ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?
The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App
if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.
Probably wrong modem for you, flash another one. You can find modems in the developement section.
ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me
Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App
yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment
The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App
cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.
ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?
Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
typci said:
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
Click to expand...
Click to collapse
Turn OFF wifi when you're not using the phone. problem solved
If not work try this :
Goto CPU menu -> smartass v2 and make low and high cpu speed settings to 1 ghz.
This will also increase Battery life and must fix random rebooting.
Other way is clear caches and install rom again.
Loureiro:
I'll try turning off the wifi. It sounds like a highly likely solution since: 1) I've only seen my phone at home 2) I always turn wifi on at home.
Is there a specific reason why wifi is causing reboots? Maybe something I can find a fix for?
technogod:
Don't have custom kernal installed, so I can't alter the CPU parameters. Wanted to make sure the phone was stable at stock before changing the kernal.
Speaking of which, what's the most stable kernal for overclocking the 2.3 stock rom?
I'll try clearing the caches as well.
Thanks.
The wifi bug is known fault with the .35 kernel found in the official upgrade. hopefully it will be fixed next week fingers and toes crossed. I am not sure if any of the kernel dev's have found a fix yet.
Without cpu parameters, only way i am found that : clear three caches with clockwork and reinstall your rom. It's working on stock roms or custom roms. I think, this is not rom problem. There is different something. Cache clearing solves problem. Resetting problem started on my phone when i start to try other roms.
I am using miui 2.2.3 now and i will setup 2.2.10 version today. While using stock rom, i have some resetting problem. But now, my phone working without self-reset.
Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues
Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog
Thank you, i'll try
wow, downloaded...
Many thanks, good job!
after installing cm11 and gapps, the phone always reboot to recovery
ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!
faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
do i need to have my phone rooted?
faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish
Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4
Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!
faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]
I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Tzheng456 said:
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Click to expand...
Click to collapse
I had the same issue with O2. I changed kernels and the problems persisted. A also word the device and started from scratch through fastboot and the issues persisted. I ended up on hydrogen and I've never looked back. There is a flashable zip in that thread for the newest full version .11. Follow the steps wipe everything besides internal storage, flash the full v11 zip and boot the phone. After this reboot to recovery (power and volume down). Flash the gapps and super su zip if you want root. After this you should be able to add your Google account and be good to go. One thing I did was remove all Chinese apps and the stock launcher. I use trebuchet launcher from cm 12.1. Phone runs incredibly smooth now. I recently started running AK kernel as well. The oxygen version works with hydrogen. I have been averaging between 5 and 7 hours of SOT for battery with up to 8 if I'm just watching videos. Hope this helps. The ROM is a little simpler and the notifications settings are different. But you can set apps to have priority notifications and they function similar to oxygens notifications at that point. Everything is in the thread if you have any questions I'll try to help you.
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.