Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/12/2023 in all areas

  1. Thanks for all the extra info. As you now know the count, l would love to know roughly how large a fraction of the waiting that will be served with the recovered devices
    1 point
  2. Good point, better to have backed up and not need the backups than the other way around! Some more info: I did not time it, but I think I let it sit at the boot logo for 2-3 minutes before rebooting and flashing LineageOS again. I assume that the firmware flashing actually happens pretty early in the boot process, so I wouldn't be surprised if letting it boot for a much shorter time works as well. Haven't seen any anomalies since I did this. Used my phone with my banking app, Whatsapp, Android Auto, etc. The only difference is that I am regularly surprised that UI elements at
    1 point
  3. Now that is just an awesome workaround! Thanks. Though people should make sure to backup as much as possible first. as the workaround relies on the stock android failing to use the current userdata without destroying anything, and that might not always go so smooth.
    1 point
  4. I found an easy way to fix this from any ROM, without having to wipe userdata. tl;dr: Edit: Make backups. It shouldn't be necessary, but you never know! Flash the 2020-08-25 stock ROM, but skip flashing/wiping userdata. More info here. Let it attempt to boot (for a couple of minutes). It (very probably) won't ever get through it, because the userdata partition wasn't wiped. This doesn't matter, though. It does flash the touchscreen firmware, which fixes the unresponsive screen edges. Edit: I did not time it, but I think I let it sit at the boot logo for 2-3
    1 point
  5. Thanks for the work, people. Life got in the way here a bit. I did a bit of digging based on the rar shared in this thread by Kaali: The APK does seem to contain code to write config data to the chip (com.goodix.tools.ICParametersConfig.class). I attached a version of the *.cfg converted to decimal, separated by newlines. There are 239 bytes in total, which do not seem to map cleanly to the config information in the datasheet. I also attached a version of the flashing instructions with Google translations in them. I used the APK with my Pro1 in USB debugging mode, and after havi
    1 point
×
×
  • Create New...

Important Information

Terms