yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] lsss:
Hi all,

Thanks a lot for all the work that's gone into this. Amazing to see how quickly this has happened.

Looking for some help. A friend bought a Hisense A9 second hand that came with Lineage 20 and an unlocked bootloader. He wanted to put the stock OS on it, so we got it into EDL mode via `adb reboot edl` and then using the `qdl` tool on Linux, started flashing the original ROM, which I downloaded from here: https://drive.google.com/drive/folders/1_5PvcvgA9TltEU_XwmiL-t2Eh0VM6C40

However, I unplugged the phone too early, thinking something was hanging, or that it was complete. Phone was stuck in a boot loop with the hisense logo on the screen and the backlight turning on and off intermittently. I could get into fastboot (pwr+vol-up) and recovery (pwr+vol-down) however.

Then have been trying to flash various custom ROMs, using this guide

https://www.reddit.com/r/hisenseA9/comments/1diqvv6
. But with no luck

It is now stuck in Fastboot mode (with the small text in the upper right). I can get it into `fastbootd` using `fastboot reboot fastboot` command. But flashing any new ROMs doesn't seem to get it out of this boot loop.

I have built and EDL cable, but haven't had any luck getting the phone into EDL mode with it. Has anyone been successful getting the phone into EDL mode via fastboot? Been reading about some patched fastboot versions that have the edl command patched in, although haven't had any luck with that.

Read on a Hisense A5 link that you can bridge two jtag pins in the back, close to the camera, to get it into edl mode. Has anyone explored this on the A9?

Sorry if I've missed the solution somewhere in this thread, there's a lot to go through.

Thanks for your help, will happily donate to anyone who can get us out of this boot loop :)
[Android Q&A, Help & Troubleshooting] damianmqr:
I tried but I don't think you can get to EDL from fastboot. You should really try with the EDL cable, it should work within a few tries.

I used a windows machine with qfil to run it but it should be similar on linux qdl. What you need to do is press all buttons on the device first (vol+ vol- eink and power) then quickly connect the two wires on a cable and plug it into the PC, later disconnecting the wires. If your device is on, you should hold volume down + power button and as soon as the screen gets dim do the procedure above, it can be a bit tricky but I usually get it within 3 tries.

If the phone vibrates it means you didn't get it and need to try again.
[Android Q&A, Help & Troubleshooting] OwlTec:
I have essentially the same problem as well except I am unable to get into fastboot mode. Super strange!
[Android Q&A, Help & Troubleshooting] lsss:
Okay cool, I'll try with the EDL cable then. Hopefully it works.

For clarity, I'm into Recovery Mode now. I'm going to:

1. Get qdl ready to flash and listening for devices. With the edl cable unplugged from my laptop.

2. Hold power + vol down until screen gets dim

3. Then also hold down Eink Button + vol up as well

4. Then press the edl button, and quickly plug in the phone

5. Hope that the phone doesn't vibrate. (I don't think it is vibrating when I plug it in anyway at the moment.

I had a time where it took like an hour to get into fastboot. Just kept holding vol-up + power and trying releasing some of the buttons every now and then. I think it'll work eventually. 🙏🏽
[Android Q&A, Help & Troubleshooting] dferreira:
😔 Probably Google screwed up AOSP contacts. If you connect your device with ADB, can you share what the crash is with logcat?
[Android Q&A, Help & Troubleshooting] OwlTec:
Can you go anywhere from fastboot including flashing a new room?
[Android Q&A, Help & Troubleshooting] lsss:
yeah, can flash a new ROM, and also boot img, but still just end up back in the boot loop.

I think unplugging whilst flashing via EDL has messed up something underneath fastboot maybe? Dunno if it's a partition table thing? It doesn't seem to be set when I list the vars via `fastboot getvar all`

Will update if I find a solution!
[Android Q&A, Help & Troubleshooting] lsss:
Ohhhh, I got it into EDL Mode!

Only thing is, QDL is failing with this error
[Android Q&A, Help & Troubleshooting] OwlTec:
Interesting - I wonder if if that would cause the same issue that I currently have. Let me try getting into that mode and see if I can throw the factory rom.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
Quick question about the screen back light. If i lower android brightness slider to the min, does it turn off the back light?

Trying to see how i can turn off the back light during the day to save even more battery :P
[Android Q&A, Help & Troubleshooting] dferreira:
Ok you are missing the contacts provider... So Google is stripping AOSP from a functional contacts app...

Search for Google Contacts apk and install it. Should work without an account!
[Android Q&A, Help & Troubleshooting] dferreira:
It does. Enable the allow minimum backlight on Treble options!
[Android Q&A, Help & Troubleshooting] meh.:
That doesn't seem to work either :(
[Android Q&A, Help & Troubleshooting] dferreira:
Try using EDL by https://github.com/bkerler/edl. I was only successful with that tool to restore my phone when I was poking around 😁
[Android Q&A, Help & Troubleshooting] dferreira:
Damn... Did it install? Long press the app, give all permissions and reboot.
[Android Q&A, Help & Troubleshooting] dferreira:
In the apps manager, show system apps, clear data from Contacts Provider to force it to recreate the database.
[Android Q&A, Help & Troubleshooting] meh.:
That did it! Thanks :)
[Android Q&A, Help & Troubleshooting] OwlTec:
Alright, got my EDL cable - EDIT - I figured it out!

Of course one step forward and another backwards. Now I am getting errors on QDLoader (see below, you can make fun me for taking a photo but I am using a friends laptop for this). Another drive error on my end?

Also this is the cable I bought, is it the wrong one?
[Android Q&A, Help & Troubleshooting] dferreira:
I think you need to install Qualcomm QDL driver?
[Android Q&A, Help & Troubleshooting] Frost015:
I haven't been able to send SMS messages via Google Messages since yesterday's afternoon. I get an error 28 pop-up. SMSC is greyed out so I cant's change it either. I don't know if anyone else experienced this on Ponce's Android 14 build. I can still receive messages, call (receive calls too).
[Android Q&A, Help & Troubleshooting] OwlTec:
I thought I did but I have been having nothing but driver problems with that Windows 10 laptop. I am going to rebuild it but this time with Ubuntu. Wish me luck!
[Android Q&A, Help & Troubleshooting] dferreira:
Haven't had issues 🤔 have you rebooted?
[Android Q&A, Help & Troubleshooting] BenjaminLSR:
Keep Volume Down (or was it up) and power pressed until your phone restart and screen displays weird artifacts, as soon as it does, press the other volume button and keep pressing. The phone will be in fastboot and from here you can reflash or wipe user partition.
[Android Q&A, Help & Troubleshooting] Frost015:
Yeah, I've switched SIMs, rebooted, tried the SMSC fix, nothing worked so far. It's weird because it's been working perfectly until yesterday. It doesn't make any sense apparently.
[Android Q&A, Help & Troubleshooting] OwlTec:
Okay one step forward, and another step backwards! I got my Ubuntu machine all configured and it is good to go BUT now the battery on the phone is dead and the device itself does not want to charge. Using my EDL cable I was able to get to this screen at least.

Extremely stupid question but is there anything I am doing wrong besides plugging the phone in to charge?

Anyway this phone is doing a good job of humbling me :ROFLMAO:
[Android Q&A, Help & Troubleshooting] dferreira:
Just leave it plugged in so it gets enough charge 😁
[Android Q&A, Help & Troubleshooting] dferreira:
Did you install updates or something? You could try removing IMS and reinstalling it. Or clear storage on IMS package?
[Android Q&A, Help & Troubleshooting] OwlTec:
Well it has been an hour-ish since my post but for whatever reason my phone is not properly charging. Am I just being impatient therefore I should come back in a day? Even before I rooted my phone it deem seem like it took forever to charge it.
[Android Q&A, Help & Troubleshooting] dferreira:
It should be quick. Do you have a 10W-20W USB-C charger? Mine takes 30 minutes to go from 30-90!
[Android Q&A, Help & Troubleshooting] OwlTec:
I'll give it a try with my 160W uGreen charger + the factory cable. Fingers crossed.

Edit: No joy - I think the device came to me like this so I will contact the seller and figure something out.
[Android Q&A, Help & Troubleshooting] Frost015:
Not that I know of. I tried removing IMS, reinstalling and clearing storage. Nothing. Still error 28 when sending SMS and no SMSC :S Really weird stuff. I placed the SIM in another phone and it's working fine when sending SMS.
[Android Q&A, Help & Troubleshooting] dferreira:
Maybe this will help: https://community.o2.co.uk/t5/Discu...rror 28 is a SMSC,in the messaging app itself.

Seems a misconfiguration!
[Android Q&A, Help & Troubleshooting] Frost015:
Yeah, tried that already. Idk why this is happening.
[Android Q&A, Help & Troubleshooting] Frost015:
I think I'm going to reflash. I can't think of any other fix atm, but it's kind of weird that it happened when no updates, or settings changes were involved. Maybe some google app (messages, contacts....) updated and did something?

Edit: Ok, problem persists after reflash, so my theory from above is debunked.

I'm scratching my head now because when I first flashed the ROM I was able to send SMS for a few days with no problems. Mind boggling
[Android Q&A, Help & Troubleshooting] ferlanero:
@dferreira

@dferreira LOS20 is what I'm using and sms works as xpected
[Android Q&A, Help & Troubleshooting] Frost015:
I haven't been able to make SMS work :S I forgot to report that headphones won't work either. I don't know if I should tweak something on treble settings but with default settings headsets are not recognized in this build.
[Android Q&A, Help & Troubleshooting] dferreira:
Enable alternative audio route on Treble settings. About the SMS, this is indeed very strange. Only thing I can think off is something happened on the operator side. Call them, maybe they screwed up on their side. They usually have logs based of device IMEI and SIM. Perhaps you were SIM swapped?
[Android Q&A, Help & Troubleshooting] treff89:
Might relate to your APN settings, especially if you're using LTE/4G.

Try resetting them to default. Then correlate the one that's selected with your carrier's published settings. Then try selecting a different APN checkbox than the one selected by default.
[Android Q&A, Help & Troubleshooting] DrogenDiego:
Got a quick question. please don't hang me I'm sure it was responded somewhere in this 100 page thread but I couldn't find it so far.

Just wondering if there is a quick tutorial or guide how to root the device. Just root it without flashing a custom ROM. Want to stay on the stock ROM but install a better ad blocker which needs root.

Thanks for the response
[Android Q&A, Help & Troubleshooting] Frost015:
I came here just to say that it was the operator's fault! Apparently they changed my phone plan without warning me and my new SMS quota had been surpassed. I actually reached my money limit so I got pissed and asked them for a refund of the surplus.

The headphone solution did not work though, so now I'm playing around the audio settings to see what's wrong.
[Android Q&A, Help & Troubleshooting] dferreira:
Under Misc settings
[Android Q&A, Help & Troubleshooting] dferreira:
Install Magisk app and use it to root - it will create a custom boot.img and you need to flash that using fastboot:

$ adb reboot fastboot

$ fastboot flash boot_a magiskGeneratedboot.img

$ fastboot flash boot_b magiskGeneratedboot.img

If you are on the latest stock ROM, you can flash the already generated root boot.img

Most of this means you need to be comfortable with the command line and read the guides that were shared on GitHub: https://github.com/aimindseye/hisense-a9
[Android Q&A, Help & Troubleshooting] DrogenDiego:
Thanks for the link. That's what I was looking for. Just found the guide that's almost a year old but figured we probably have a more comprehensive version by now ;)

I am confident with adv etc etc so I guess its gonna be fine. My phone arrives in 10 days and I will check what stock ROM it's on. I bought it from chosen store in China. It has gapps installed already but I prefer to do it myself ;)
[Android Q&A, Help & Troubleshooting] dferreira:
Ok, that will mean the OS that you get has the latest stock ROM so to root all you need to do is flash magisk patched 6.08 boot.img on your device. Then it will show Magisk icon on your launcher. Open it so that it finishes setting itself up - just follow the prompts.

Patched 6.08 boot.img https://drive.google.com/file/d/1S7USjt1k5SkMYILtU135Z8MUQAyMCkST/view?usp=drivesdk
[Android Q&A, Help & Troubleshooting] Frost015:
That did it sir!
[Android Q&A, Help & Troubleshooting] dferreira:
Set System UI to this and when you lock, and if you don't have AOD enabled, it will keep what was on the screen visible when you lock. It will clear and show locked screen if you receive a notification.
[Android Q&A, Help & Troubleshooting] Frost015:
It didn't work for me. Still getting a black screen as the lock screen. I have AOD disabled in treble settings.
[Android Q&A, Help & Troubleshooting] dferreira:
Yeah it's finicky. Sometimes it works, sometimes not 🥴
[Android Q&A, Help & Troubleshooting] Frost015:
Yeah haha. Love the puzzle solving with custom os builds. It's always an adventure
[Android Q&A, Help & Troubleshooting] StridAst:
So, running Dferreira's build, and I'm noticing when I lock the screen the backlight often stays on, just at a very low level. Anything I missing in the settings to stop this? The problem seems to be somewhat inconsistent, and the light output is low enough to not be visible except at night.
[Android Q&A, Help & Troubleshooting] dferreira:
Enable the allow max minimum brightness on Treble settings. You should be able to turn off the light completely.
[Android Q&A, Help & Troubleshooting] ext23:
With all this talk about SMS I tried sending one from my A9 using @damianmqr's ROM..it didn't work. I also can't receive SMS. I can receive calls, but I can't make calls. I tried replacing the Lineage dialer/messenger with Google dialer/messenger, same problem.

I only use my A9 for mobile data so I never noticed this until now (mobile data is fine). Anybody else?
[Android Q&A, Help & Troubleshooting] idonotbelonghere:
I had that issue with DF LOS20 and it seemed to be due to my phone trying to use 3G despite all the settings being set to 4G/LTE (3G network has been deactivated where I am). I wasn't able to solve it.

I'm now on DF Ponce Android 14 and calls and text worked consistently over the weekend so now I'm seeing if I get any issues daily driving it!
[Android Q&A, Help & Troubleshooting] R0W3Y:
I don't use them often, but they test ok for me on the LOS21 builds (on EE in the UK).
[Android Q&A, Help & Troubleshooting] damianmqr:
@ext23 The issue with SMS might be regional since it works for me and few others, but have you installed the IMS app? If not you could find it in treble settings and reboot your device afterwards to see if that helps.
[Android Q&A, Help & Troubleshooting] Kandwo:
So I got dferreiras AOSP vanilla working. My next steps would be to install microG and Tasker (for the screen refresh in reading apps). Is root needed for MicroG (it says it requires signature spoofing)?

Has anybody installed microG on this ROM? Which steps should I go through?

EDIT: MicroG settings says that "System spoofs signature" (checkbox is marked), but at the same time claims that the system doesn't natively have system signature spoofing.

I don't know if it's connected, but when trying to open the Couchsurfing app it shows a popup asking to be installed from Google Play Store instead (I installed it from Aurora store). It also doesn't seem to be able to get my location, although I have granted MicroG all permissions and rebooted the phone twice.

EDIT2: It seems like the location issue was solved after installing the back-end services from here: https://old.reddit.com/r/microg/wiki/location. I just assumed that they were already a part of the package.

The only thing remaining for MicroG is to find out how to make Couchsurfing (and potentially other apps) not complain that they are not installed from actual Google Play Store. Or maybe that's an issue elsewhere?
[Android Q&A, Help & Troubleshooting] dferreira:
I think you need to install a spoofed Play Store?
[Android Q&A, Help & Troubleshooting] iCloud:
Try to use adb to install the package and spoof the installer as if it's from the Play Store: adb install -i com.android.vending (apk).
[Android Q&A, Help & Troubleshooting] Kandwo:
I'll try that a bit later. The app works for now by long pressing it and choosing something from the menu e.g. "Hangouts", and from there the rest of the app is available without a problem.

But I noticed that Tasker is grayed out in the accessibility menu "for my protection". I assumed it requires root. Is the process on AOSP the same using Magisk? Is there a particular version of Magisk that needs to be used (I recall some users experiencing a bootloop earlier in the thread) or just the latest?

What would the rooting procedure look like on Ponce's AOSP?
[Android Q&A, Help & Troubleshooting] lichobg:
Fix DAC and 3,5 Audio output problem Hisense A9 AOSP.

Probably work for Lineage 20-21 not testet.

Install

DAC Fix​

from Google Play. Switch all on. Reboot.​
[Android Q&A, Help & Troubleshooting] dferreira:
How is this different from enabling Treble settings?
[Android Q&A, Help & Troubleshooting] dferreira:
Android 14 is more picky with accessibility services if they are not built in. You need to force stop Tasker, long press it, app settings then special access and enable it there.
[Android Q&A, Help & Troubleshooting] dferreira:
Gcam on our device 😉
[Android Q&A, Help & Troubleshooting] vbhai:
Any luck with the vibration? @dferreira @damianmqr
[Android Q&A, Help & Troubleshooting] lichobg:
Treble dont worked with my Hisense. Audio was distorted only with Treble fix and without output from 3.5 - headphones not detected.
[Android Q&A, Help & Troubleshooting] dferreira:
Currently on a summer trip, have made progress but can't share without my laptop 😅
[Android Q&A, Help & Troubleshooting] dferreira:
Those enabled and reboot. No distortion, headphone jack working.
[Android Q&A, Help & Troubleshooting] lichobg:
@dferreira

"Those enabled and reboot. No distortion, headphone jack working."

Yes i know and tried all from these . But with mine with Qualcomm options enabled i have audio distortion on Telegram - high pitch /distortion. Worked only media play or only calls/voice. DAC output /Headphones dont work. With alternate route or not no difference. Im not sure if all Hisenses have ES9318 or possible older or new version from audio Soc. DAC fix ist compatible with 9218P and above from LGs Phones and worked.
[Android Q&A, Help & Troubleshooting] biodbl:
It could be Nice tô post with original câmera and with GCAM. The same photo.
[Android Q&A, Help & Troubleshooting] Kandwo:
Which setting would that be? I have allowed most of the settings in special access, but I don't see any accessibility setting specifically.
[Android Q&A, Help & Troubleshooting] dferreira:
Where it shows this menu?
[Android Q&A, Help & Troubleshooting] dferreira:
Side by side
[Android Q&A, Help & Troubleshooting] Kandwo:
No, I'm with you. That's where I've allowed most permissions. And in the "special access" submenu in the App settings. But I don't see anything connected to accessibility in either place.

Hm, trying just now it wouldn't allow me to activate the alarm permission for Tasker. If I flick the switch and go back in the menu it's back to "denied". But I don't know if that makes a difference.

I guess Tasker is still the easiest way to incorporate a full screen refresh when turning pages in reading apps? The way I had it set up before was that it called the full screen refresh function whenever using the volume keys in the apps of my choosing (e.g. Koreader). That way volume down would trigger a page turn within the app and would call the full screen refresh function. Somebody in this thread kindly provided the process of how to achieve this.

That's all I use Tasker for, and it seems it requires accessibility access.

I guess that would be too complicated for the e-ink center? Or a separate app?

I linked a thread here before: https://xdaforums.com/t/hisense-a5-auto-refresh-app-no-root-test-required.4483213/

But the developers seem to have abandoned the project.
[Android Q&A, Help & Troubleshooting] dferreira:
See this: https://www.reddit.com/r/androidapps/s/OOkymKGJvL

Android 14 if you install an accessibility service not from Play Store, it disables them unless you explicitly allow it.
[Android Q&A, Help & Troubleshooting] Hadi99:
Can someone name a quickstep launcher that supports grid recents? The scrolling carousel appswitcher on AOSP isn't ideal on e-ink
[Android Q&A, Help & Troubleshooting] bumblar:
I miss face unlock of the stock firmware, spite I know it is unsecure. I don't keep anything worth protecting on my A9.

Is there a chance to get face unlock back, maybe through extracting the implementation from the stock ROM. Are we so lucky that it is just a stand-alone app that just has permissions set to unlock the phone?

I don't have an EDL cable so I can't go back to the stock rom to poke around.
[Android Q&A, Help & Troubleshooting] joke19:
You rooted your phone?
[Android Q&A, Help & Troubleshooting] bumblar:
I don't mind doing so. :-)
[Android Q&A, Help & Troubleshooting] joke19:
Here, its looks like away to root. But and check it works or other you must look for it. I hope you have knowledge for it. Lsxposed and there is a module for face unlock or magisk. I don't remember where, but good luck

https://www.reddit.com/r/eink/comments/16tpr96
[Android Q&A, Help & Troubleshooting] Kandwo:
I'm trying to run the Tasker code from page 19 in this thread to have a full screen refresh whenever I use the volume buttons in Koreader (out any reading app), but I get an error message:

16.27.40/LicenseCheckerTasker Checking cached only
16.27.40/LicenseCheckerTasker cache validity left -8449567
16.27.40/LicenseCheckerTasker Cached status: Licensed
16.27.40/LicenseCheckerTasker Cached only: Licensed
16.27.40/E Run Shell: ->
16.27.40/E Run Shell: ->
16.27.40/E Run Shell: ->
16.27.40/Shell runBackground service call epd 21 root: false timeout: -1
16.27.40/Shell start process-thread ID 479
16.27.40/Ew add wait type Shell1 time 2147483647
16.27.40/Ew add wait type Shell1 done
16.27.40/E add wait task
16.27.40/E Error: null

Is this connected to root access or something else?
[Android Q&A, Help & Troubleshooting] Kandwo:
This was building on using a shell command that doesn't exist in this ROM, I guess. Trying to call the function in adb results in:

"adb shell service call epd 21

service: Service epd does not exist"

What should I change this to? What's the code for a full screen refresh in AOSP 14? :)

The other method of simulating a press on the eink button using button code 440 also results in nothing. Is the button code different in AOSP 14? Is there any way to find out what code it uses?
[Android Q&A, Help & Troubleshooting] dferreira:
My Ponce's Android 14 build does have face unlock, powered by Google!
[Android Q&A, Help & Troubleshooting] dferreira:
If you install Eink Center, I have added a Broadcast you can use in Tasker to trigger a full refresh:

com.hisense.einkservices.broadcasts.EinkClearReceiver"
[Android Q&A, Help & Troubleshooting] dferreira:
I'm not using the stock service, but my own. Stock service had too many dependencies from Android 11 and other telemetry that I did not want running on my phone. As I said before, I did expose a broadcast you can issue via adb and it will clear the screen.