Haven't managed to test if it fixes the bug because I had to sleep lol.
https://github.com/Demon000/libra/commit/b5067833797cd1eb207cd976bf2419c58ca8c7ed
If anyone can test if it works, I would be very thankful.
How I did it?
Get a hex file editor.
Compile kernel with old touchscreen firmware.
Open the synaptics_biel_sharp_update.fw or synaptic_biel_auo_update.fw that have been generated in firmware/ folder in the hex editor.
Get the MIUI kernel, split it, uncompress it.
In the .fw files, the first four hex groups are magic numbers(a hex group looks like "3F"), and after that there are some common hex groups in sharp and auo firmware.
Use the hex editor to search for the common groups in the MIUI kernel, and also find the magic number before the common groups.
Use the "csplitb" program to split the the kernel binary at the newly found magic number + common groups, and strip the result to 12661 lines.
Repeat this for every common group found.
Then use the objcopy program inside the toolchain to convert the binary files to .ihex, and replace the ihex files in the firmware folder.
Done.
It is complicated, but once you get the first steps it will be easy to understand.
Although I don't know if I did a good job at explaining.
Cozmy, you are magic. Lot of thanx, Man.
Many thanks. :good:
How does one flash this?
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
You cannot, devs that make custom roms can use it to build rom with fixed display firmware.
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Harrynowl said:
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Click to expand...
Click to collapse
I couldn't get it to update the firmware because I was not using Xiaomi touchscreen drivers in my kernel, but the firmware itself should be working fine.
I don't want to bloat my CAF touchscreen driver so it will take me longer until I find where it fails.
Please keep us updated.
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Cozzmy13 said:
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Click to expand...
Click to collapse
I hope this gets implemented on next releases of our roms
solis_f said:
I hope this gets implemented on next releases of our roms
Click to expand...
Click to collapse
Just give the ROM maintainers a link to this, they will surely add it to the ROM.
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Phlogistol said:
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Click to expand...
Click to collapse
It's my fault, I compiled the image with RR ramdisk. It definitely works on RR Nougat, that's for sure. I have since switched to Lineage OS and the fix sticked.
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
bankov said:
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
Click to expand...
Click to collapse
Is the touchscreen problem fixed? If it's not then this is not my fault. If it is fixed then it's XIAOMI's fault. I will test on my device and report back. Use on-screen buttons until I do some research.
The problem was not in your update. It was from the last AICP update 23.01.2017 i installed 19.01.2017 and buttons are fine now. The touchscreen seems to be fixed iven with full wipe, going back to miui and restoring 19.01.2017 AICP.
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Can you explain the problem a bit more?
Did it get fixed after restoring?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Mine is AUO. My touchscreen was like yours but it was from AICP update.
Basicly im not 100% shure it is fixed but i remember it couldnt register touch on the left bezel if somhere else is toched on the screen. And now is fine.
For anyone applying this from now on, the process is not reversible, because of the way the driver checks if firmware can be updated, it only wants to do upgrades, not downgrades.
Also, for anyone having problems that go away after a clean flash, they are probably not because of my fix.
If they don't go away, there is probably an updated firmware version somewhere that fixes it. I'll extract them again from the newest Nougat version.
Cozzmy13 said:
Can you explain the problem a bit more?
Did it get fixed after restoring?
Click to expand...
Click to collapse
Sure, I was a bit pressed for time yesterday
The touchscreen was inconsistent, for lack of a better word. Touches on a specific point on the screen didn't register on that location, but on some other one. It wasn't random because I could reliably reproduce this. There were also some points on the screen I couldn't reach at all. The capacitive buttons also didn't work. I'd have taken logs, but I couldn't get into developer options
I don't know exactly how this works, but the touchscreen got reversed to its original state when I managed to restore a backup of my earlier TS CM13.1 system from TWRP (I restored all available partitions). It took a few tries because of the weirdness though When I say original state, I mean it still suffers from the multitouch bug, so nothing got fixed.
Hope this is useful, but I'm stumped. Could we have different digitizers?
Related
Hi all,
Got my OnePlus One last week. It's a Chinese version that comes with ColorOS. I immediately tried to flash CM11 nightly onto it after I checked the phone is working.
For some reason I thought I could flash CM11 directly, and so the first thing I did was installing TWRP 2.8.0.1. Then, I copied CM11 zip in to /sdcard , booted to TWRP recovery, wiped all partitions (including System) and then flashed CM11. In hindsight, I believe it was the wrong way to get CM11. I could have wiped something really important (sensors drivers?) when wiping System.
Initially, CM11 nightly seemed to work OK. Then I noticed the Auto-Rotate is not working at all. I installed CPU-Z and *gasp*, there's not a single sensor listed in the CPU-Z Sensors tab!
I spent hours today trying various methods (flash CM11S, flash ColorOS, flash /persist, /reserve4 partitions). However, the sensors are still dead! Besides auto-rotate, I think auto-brightness, proximity sensors are all dead.
Is there any way to get the sensors working again? Your help is much appreciated!
Try http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and see if your sensors work after restoring to factory images.
Someone else said only twrp 2.7 is supported for opo, another guy had similar device breaking problems with 2.8.
I'm using TWRP 2.8.0.1 and have no problems. TWRP 2.8 had problems, but 2.8.0.1 resolved them.
Thanks a lot for the quick reply, zephiK! I've run flash-all.sh and I'm in CM11S now.
CPU-Z no longer shows an empty Sensors list! however, only the following 4 sensors have readings:
AK8963 Magnetometer
AK8963 Magnetometer Uncalibrated
TMG-3993 IR_Gesture & Proximity
TMG-3993 Ambient
No readings for the rest...
Does auto rotate work? I'm not really sure how your sensors disappeared in the first place, its very odd.
/system is wiped on every ROM flash anyway so that's not the reason. Glad it's working better at least. Any more issues with the sensors other then some not showing?
Nope, the auto-rotate is still not working.
I've just rebooted CM11S, and... the Sensors tab in CPU-Z became empty again! This is very strange indeed...
I think t is a kernel problem,
Maybe you van flash the original boot.img
Rebooted again. The list of sensors are showing in CPU-Z again, and the same 4 lines have readings (AK8963 Magnetometer, TMG-3993). Still no auto-rotate.
My gut feeling is that there is a low level corruption in one of the "special" partitions. By special I mean the ones that are there but not included in any of the ROMs or factory images. Unfortunately, I don't have a NANDROID backup to restore from (Huge mistake on my part).
Is there a way to download an NANDROID image containing those special partitions?
@gurby1, I thought about kernel problem too, but I've tried flashing many ROMs and kernels:
CM11S 33R
CM11 Nightly 20140296
Franco Kernel r20
ColorOS 2.0 beta
ColorOS 1.2
and the results were the same - broken auto-rotate.
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
DecemberNexus said:
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
Click to expand...
Click to collapse
Hello,
Did you find a solution ? I have exactly the same issue as you. It even worst, I don't see any sensor on my device. I have installed many ROMs without any success. I hope it is not a HW problem
Thanks.
Guys.. I also have this issue..
Glad if there any solution on this...
Same problem
Guys any solution yet? I'm getting annoyed by this so much.. Please post here if u have found any solutions. Thx.
I also have the sensor problem which is all sensor is "not supported" in antutu and empty in CPU-Z sensor tab. I fixed it by flashing the persist.img from this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Dzhedaj said:
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Click to expand...
Click to collapse
Have you try flash the persist.img?
TheDynamiteGuy said:
Have you try flash the persist.img?
Click to expand...
Click to collapse
Tried flashing everything, modems, persist.img, etc. Nothing helps, so seems something is toast in the hardware...
So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work but here you go. Roasted Marshmallow, hot off the build server
EDIT: Title is probably wrong, as pointed out by a mod. I based it on the Git ref being "6.0_r1", which I thought meant "6.0.1". This is really 6.0. Specifically, a build based on the exact instructions posted by Sony.
MOD EDIT by @gregbradley
I edited the title for you .
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
thatguy222 said:
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
Click to expand...
Click to collapse
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Gairtial said:
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Click to expand...
Click to collapse
Bummer. Thanks for nothing, Sony!
thatguy222 said:
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Bummer. Thanks for nothing, Sony!
Click to expand...
Click to collapse
Don't jump the gun. There are a lot of files in a standard Android build and I don't know if it comes from them or if it's a product of the build process. It could just be a misconfiguration on my part. The bug is for info, not because it's their fault.
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
aniket_ said:
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Click to expand...
Click to collapse
I tried that last night using one of the files from the various vendor repos but no luck. The kernel module threw errors about the data being invalid. I'll try extracting from official firmware when I get home. Also that thread doesn't yet have anyone confirming that it works :/
fratzika said:
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
Click to expand...
Click to collapse
I don't have my Z3C with me so I'm unlikely to be able to do anything helpful for ~9h, when I get home. You'll have to be a little patient
Okay, got a build up to date with Git and with a modem copied from one of the latest firmwares (ripped it from the SLIM stock ROM). Wouldn't get your hopes up but it might work
EDIT: No luck. It doesn't seem there's an available modem that's likely to work. Unless someone can suggest another device with close enough hardware and a working Marshmallow modem (seems doubtful), we're lost until someone can extract one from a legitimate Sony firmware or Sony releases it to us (seems unlikely).
Thanks for doing this Gairtail, let's hope you get it up and running soon (if Sony or someone else uploads the modem file..)
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
someone755 said:
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
Click to expand...
Click to collapse
Theliakos said:
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
Click to expand...
Click to collapse
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Gairtial said:
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Click to expand...
Click to collapse
I built on Novenber 5th, worked just fine. Just synced and started another build, but the November security update isn't here yet, bummer. (I reckon another 24 hours should do it.)
If you'd like, I can upload the build for you.
Apo14 said:
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Click to expand...
Click to collapse
I don't know for sure, but wouldn't flashing a stock FTF solve this?
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Also, not sure if you guys also get this, but I've been getting the dwc3-msm wakelock a lot. Happens because of kernel bug that keeps phone awake, thinking it's connected to a power source even after it's been disconnected. Drained my battery for 17 hours before I even noticed. I don't know if the official method with prebuilt kernels also has this, but I build the upstream sonyxperiadev/kernel repo myself. If you use a kernel source too, instead of using the prebuilt kernels, you could try picking this. Looks to be working for me, but it hasn't been merged yet, so take that as you will.
EDIT: Noticed this isn't upstream Marshmallow, but r1. Bummer.
You should really switch to 6.0.1, the 1.3.3 kernel is much better than 1.2.2 (and without the memalloc reboots caused by media/video). Though if you prefer not to switch, you could still add my uploads to the OP alongside yours if you want? That way we have 6.0 and 6.0.1 under one roof?
@someone755 so should i be able to extract those files without the need to flash?
Apo14 said:
@someone755 so should i be able to extract those files without the need to flash?
Click to expand...
Click to collapse
No reason to avoid flashing, really. Make a backup of system and boot, don't wipe userdata, and have a recovery image handy. Flash FTF, flash recovery, restore system and boot.
The only things that get updated are your modem and bootloader etc, your system and data stay untouched.
Though depending on when you last flashed an FTF, it may be a good idea to wipe your data in recovery before you flash (and back it up, of course). Some firmware can only be updated after Android has booted, like NFC for example.
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Apo14 said:
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Click to expand...
Click to collapse
I'm not saying it's best, but it could help you avoid potential issues. I don't know what all you've been doing with your device, so I can't make the call for you. Just telling you how it is.
This is a nice thread: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 You'll also need FlashTool if you go down this route, you can Google it to download.
EDIT: @Gairtial I have today's 6.0.1 source in a nice zip. https://www.androidfilehost.com/?w=files&flid=127723
There's also a folder with the kernels for 6.0.1/7.0/7.1 that I'll try to keep up to date, if there's any interest for that. (The kernel zip will flash to any of the three Android versions, so long as the ROM is AOSP-based. Other than that, it's version-independent.)
Another note would be that I didn't make any changes to the ROM build. GApps will have issues starting unless you do some adb wizardry, and you'll get your recovery overwritten with the useless AOSP one if you flash the ROM zip in recovery. (You could also just try flashing system and boot through fastboot, though I haven't tried.)
someone755 said:
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Click to expand...
Click to collapse
I'm tired of using stock Sony roms, and I'm starting to hate them. Still waiting for those latest camera blobs though for AOSP. I've tried your uploaded build, but it's causing a bootloop somehow. Didn't flash the separate kernel, but I don't see the need for that since there is one included in rom zip. Not sure what is the problem...
Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(
Maybe don't flash supersu? Cm comes prerooted?
audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.
Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs
Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!
I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model
I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.
since i dont own the device.... no logs= we cant help you
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?
I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(
Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?
Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?
Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.
Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...
Now with LineageOS 14.1 Nougat
builds
sources (github) PATCHES STRONGLY ENCOURAGED
local_manifests for building
current branch is cm-14.1 (LineageOS 14.1 with Linux 3.10.x)
Instructions:
Unlock bootloader
Flash TWRP from kugo/twrp/recovery.img or from https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
Do not use AndroPlus's, it does not handle /system writing very well (in my experience)
Do not use my recovery build for stock, it does not handle /data encryption
Flash zip in recovery
SELinux: Permissive (I haven't updated the sepolicy in a while, enforcing makes the camera panic which causes bootloop. I may fix this later.)
Lineage 14.1
WORKING:
WiFi
Data/Cellular (you may want to jot down APN settings from stock before flashing)
Fingerprint reader (a bit unreliable, will fail sometimes)
FMRadio
Camera
NOT WORKING:
AudioFX (the built in equalizer thing; just disable it from the apps menu)
SELinux (sepolicy needs update)
Bluetooth (system seems to crash when turning it off)
Whatever isn't working in AOSP/Omnirom (e.g. in-call volume control)
UNTESTED:
NFC (it turns on, but I have no NFC devices)
Keep in mind that I am not really a developer but will do what I can to help with issues
Special thanks to the Sony-Kitakami team for serving as a base to port changes from suzuran/kitakami to kugo/loire
Additional thanks to humberos for porting omnirom to kugo and serving as a base to port to kugo
...and thanks to Sony for allowing us to unlock our bootloaders and for porting AOSP to their phones (unlike some other manufacturers)
Recent Changes:
Rebased device trees off of omnirom trees, updated everything
I'll go first and say thank you for developing for this device.
Hope that this encourages other devs to build their ROMs too.
Great job! :good:
Nice
as soon as audio playback is fixed i will flash and try to post logcats !
A little love for the XC
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
ardylemon said:
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
Click to expand...
Click to collapse
Not to mention greater adoption of ROM flashing now that we have a way to get back to stock.
thanks for the update!
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Micka84 said:
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Click to expand...
Click to collapse
I would go with cm-13.0 honestly unless bluetooth is that important (which is next on the to-do list for cm-13).
CM-14.1 is pretty incomplete upstream, so it's missing some features (like theming).
It's also still running the marshmallow kernel, so things like vulkan probably won't work either, and
I don't plan on releasing a build with the nougat kernel until we at least get prebuilts for it.
howdid said:
as soon as audio playback is fixed i will flash and try to post logcats !
Click to expand...
Click to collapse
Audio playback should be "fixed" now, for both 13 and 14.1
How is camera quality and battery life?
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
ammarr said:
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
Click to expand...
Click to collapse
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
tlxxxsracer said:
How is camera quality and battery life?
Click to expand...
Click to collapse
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
EliWallace said:
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
Click to expand...
Click to collapse
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
ammarr said:
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
Click to expand...
Click to collapse
It was enough to get through a day, but I would end up with 30-50% instead of 60-75% (I have mail checking constantly, so that was a big drain)
Thats in comparison to a CM build with a newer kernel and audio offloading not disabled,
I haven't used stock at all so I don't know how the battery life is on it
Why not use an existing msm8956 tree for kenzo and hydrogen and make Sony additions to a car kernel source and boot cm. It will bring much lesser issues.
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
NL_henk said:
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
Click to expand...
Click to collapse
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
NL_henk said:
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
Click to expand...
Click to collapse
I also noticed that the mobile does not charge however at the laptop over USB load it
Ps. i use not Costum Kernel
StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.
Thanks you very much
I will test
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Just a question, does StatiXOS have slim recents included?
Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.
Is anyone else having issues with sending a text message with this rom?
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
Double Post
Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.
chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..
The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.
SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.