yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Renate:
A Firehose loader is a replacement XBL (extensible bootloader) that has the special sauce added to speak the Firehose protocol over USB.

You need one that is compatible with your Qualcomm processor (a single loader could work with multiple processors).

Normally with SecureBoot you also need one that is cryptologically signed by the company that made your device too.

Since manufacturers generally don't release these signed loaders their distributions is based on leaks?

Undoubtedly the company you mentioned has things locked down or else their business plan would fade away.
[Android Q&A, Help & Troubleshooting] velcrobomb:
It's pretty ridiculously locked down. Recovery has 0 options. Can't even install a zip. I downloaded the QPST application and tried to get a dump via edl but no dice yet.

Been doing some research, this page has a list of devices that have the snapdragon 622 and a most of them have custom recoveries and have been rooted.

The panasonic usb driver works for fastboot, but not much you can do on it other than look at what you have.

I was able to uninstall a few bloat apps via adb so it's better than it was out of the box. Got Chrome updated and installed einkbro browser.
[Android Q&A, Help & Troubleshooting] dferreira:
Hey folks 👋 I'm receiving this device in coming weeks. Have we tried these:

- fastboot flashing unlock

- fastboot oem unlock-go
[Android Q&A, Help & Troubleshooting] Ramkrsna:
Hello everyone,

I’m getting my A9 this week. I want to root it as well but I’m pretty new to this stuff. I previously rooted phones using guides but not on my own. Is it possible to root if we have .elf and boot.img files? I read the previous contributors messages and it gave me hope of rooting the A9. I know a person who has the complete firmware not the incremental updates. So that’s the reason why I’m buying this. It would be great if someone can outline the steps of the rooting process?

Thanks in advance. Hopefully we can root it.
[Android Q&A, Help & Troubleshooting] Ramkrsna:
Hey,

I think @RunnyYolk, tried both commands but didn’t work. I’m getting my A9 this week and will give it a try.

Any update on your order?
[Android Q&A, Help & Troubleshooting] dferreira:
Already cleared customs, should have it in a couple of days. Excited! 😁
[Android Q&A, Help & Troubleshooting] dferreira:
Can we get a copy of that complete firmware and share it here? I can poke around it while we wait for the device.
[Android Q&A, Help & Troubleshooting] dferreira:
Received the phone today and will tinker with this.
[Android Q&A, Help & Troubleshooting] dferreira:
Tried them, no dice. I'm gonna see if I can get GSF installed here via GApps .zip, extract .apks and adb commands with grant permissions. I don't really need root per se. A debloat + GSF should be doable. Will create an easy to run script.
[Android Q&A, Help & Troubleshooting] deny-bas-dns:
Some things that might help:

1) boot loader unlock option in developer settings

2) The Hisense A9 being generally unstable with seller installed software, especially the Google Play stuff. I factory reset mine to get rid of the bloat.

I have no experience rooting stuff, hopefully A9 gets root.
[Android Q&A, Help & Troubleshooting] doschxda:
I Just received my A9 and was able to install FDroid, MicroG and change the launcher. All without root.

So, I guess that that is all you need for an improved LightPhone experience... no?
[Android Q&A, Help & Troubleshooting] pkshr:
Under your Magisk / Installed there is no version listed. Below is mine:
[Android Q&A, Help & Troubleshooting] Segnaro:
You don't have root. You skipped the flashing magisk patched boot.img step, and probably other steps as well.
[Android Q&A, Help & Troubleshooting] Veganer:
I see the problem, i didnt reference the prepared boot.img. Now it is working without wiping the system. Thanks
[Android Q&A, Help & Troubleshooting] vuanh1408:
Hi. Could you pls help. I have a Hisense Touch running L1834.6.02.01.B3. I tried to dump the boot img and vbmeta using your code but not successful.

./adb.exe reboot edl

worked, the device reboot to edl

but

./edl.exe /lprog_firehose_ddr_001360E1.elf

outputs:

Found EDL 9008

Could not open device

Could you pls tell me what's wrong. Am I missing something here?
[Android Q&A, Help & Troubleshooting] Renate:
You still have the Qualcomm driver loaded which is monopolizing the device.

Install the WinUsb driver with Zadig as per the instructions.
[Android Q&A, Help & Troubleshooting] vuanh1408:
Thank you very much. After using Zadig to install the winusb, it worked like a charm. Already be able to dump the vbmeta and boot file
[Android Q&A, Help & Troubleshooting] Ololiuhqui:
It's good i don't have to degoogle this thing, as it doesn't have google play services by default lmao, i'm gonna try to install microg as soon as i get my hands on this device.

But did anyone manage to remove all the chinese trackers and stuff, for example removing the default location service (which is the weChat proprietary service) and substitute it with mozilla location services?

Is a tracker blocker enough to block them?
[Android Q&A, Help & Troubleshooting] HungYU0506:
I have a Hisense A9 mobile phone, but its software version is L2037.6.06.03.00. I flashed the boot.img of the L2037.6.08..01.00 version. As a result, I cannot root successfully, and the wifi cannot be used and cannot be repaired by resetting the system. Should I re-flash the boot.img of L2037.6.06.03.00? Or are there other ways to solve my problem? Thank you for your reading and assistance!

google translate
[Android Q&A, Help & Troubleshooting] Homerzinho:
I've successfully rooted the A9 pro version (8gb, 256gb) following the steps on the original post. Maybe the author could also provide links and instructions to install the usb drivers. I've only managed to do it after selecting "With disc..." in the windows driver update dialog.

I'm really loving the phone, and I really like the eInk OS. If I could remove all chinese apps, it would be perfect.
[Android Q&A, Help & Troubleshooting] Renate:
You've only partially updated to 6.08 and now your kernel is newer than the kernel module (whatever.ko) for WiFi and it won't work.

Either update fully to 6.08 or else roll back the kernel to 6.06
[Android Q&A, Help & Troubleshooting] vuanh1408:
Anybody knows any gapps that is good other than Lite Gapps Lite version that # 209 suggested here. Everything is fine except for google contacts does not sync. I checked, google contact is running. Anybody knows how to sync google contact or a better Gapps pls kindly let me know. Thanks alot

p/s: I tried installed other varriants of Lite Gapps (like Basic or Core) but the phone keeps stuck at logo. I had to format the data using recovery and installed the Lite one
[Android Q&A, Help & Troubleshooting] vuanh1408:
Hi. Could you help me with this. I tried rooting my Hisense Touch Lite also, but there are some problem:

./edl.exe /lprog_firehose_ddr_001360E1.elf

outputs:

Found EDL 9008

Serial: 37447cb7

HWID: 001360e100430000, QC: 001360e1, OEM: 0043, Model: 0000

Hash: 56d3f3c74a52172b-18ca2297db00f3fe-ebd23cdfc77decfb-34268abca09d9075-f89b18f87610ef3f-e67f948d4bdf4501 (x3)

Sending prog_firehose_ddr_001360E1.elf 100% Ok

Waiting for Firehose... Ok

After that

./edl.exe /u /r /pvbmeta_a vbmeta_a.img

Outputs:

Found EDL 9008

Configuring... Ok

Requesting info on LUN 0... No response

./edl.exe /u /r /pvbmeta_b vbmeta_b.img

Outputs:

Found EDL 9008

<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0" />

<log value="ERROR: Failed to open the device:3 slot:0 partition:0 error:0" />

<log value="ERROR: OPEN handle NULL and no error, weird 203918492" />

<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3" />

Configuring... Ok

Requesting info on LUN 0... No response

The same goes for boot.img code. Anything wrong here? Thank you a lot
[Android Q&A, Help & Troubleshooting] HungYU0506:
But I don’t have version 6.08 ROM, nor can I find it in the forum. Do you have version 6.08 ROM? Thank you for your help!

google translate
[Android Q&A, Help & Troubleshooting] Renate:
Hmm, that looks strange.

Could you download a fresh copy of edl.exe.

edl.exe /lprog_firehose_ddr_001360E1.elf
edl.exe /u /i /v

Edit: I think that you might be having USB connectivity problems? Try cables, ports.

Sorry, I don't have any software, or even this device!
[Android Q&A, Help & Troubleshooting] vuanh1408:
Hi, I've downloaded a fresh copy of edl.exe. Here are the outputs from your new code

edl.exe /lprog_firehose_ddr_001360E1.elf

Outputs:

Found EDL 9008

Serial: 37447cb7

HWID: 001360e100430000, QC: 001360e1, OEM: 0043, Model: 0000

Hash: 56d3f3c74a52172b-18ca2297db00f3fe-ebd23cdfc77decfb-34268abca09d9075-f89b18f87610ef3f-e67f948d4bdf4501 (x3)

Sending prog_firehose_ddr_001360E1.elf 100% ok, waiting for Firehose... ok

edl.exe /u /i /v

Outputs:

Found EDL 9008

USB maximum packet: in=512, out=512

Configuring...

<log value="INFO: Calling handler for configure" />

<log value="INFO: Storage type set to value UFS" />

<response value="ACK" MemoryName="UFS" MinVersionSupported="1" Version="1" MaxPayloadSizeToTargetInBytes="65536" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" DateTime="Jul 12 2022 - 22:36:03" />

Ok

Requesting info on LUN 0...

<log value="INFO: Calling handler for getstorageinfo" />

No ack/nak
[Android Q&A, Help & Troubleshooting] HungYU0506:
It's a pity that he can't update to version 6.08. If anyone sees me, can you share your version of 6.08? This will be a big help to me, thanks to everyone for your help!

Google translate
[Android Q&A, Help & Troubleshooting] Renate:
Hmm, strange. Could you try that edl /u /i /v a few times to see if it reacts the same?

Maybe a regression error has crept in. I'd like to resolve this.

Check cables and ports.

Is this running under real Windows or a VM under Linux?
[Android Q&A, Help & Troubleshooting] vuanh1408:
Hi. Sorry for my late reply. It seems that xda forums is migrating to a new address and I cant quote nor reply.

This is running on real Windows 11

I have tried changing the cables and ports but the results are the same.

Here are the outputs using the code edl /u /i /v that you gave me

1st output:

Found EDL 9008

USB maximum packet: in=512, out=512

Configuring...

<log value="INFO: Calling handler for configure" />

<log value="INFO: Storage type set to value UFS" />

<response value="ACK" MemoryName="UFS" MinVersionSupported="1" Version="1" MaxPayloadSizeToTargetInBytes="65536" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" DateTime="Jul 12 2022 - 22:36:03" />

Ok

Requesting info on LUN 0...

<log value="INFO: Calling handler for getstorageinfo" />

No ack/nak

2nd output:

Found EDL 9008

USB maximum packet: in=512, out=512

<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0" />

<log value="ERROR: Failed to open the device:3 slot:0 partition:0 error:0" />

<log value="ERROR: OPEN handle NULL and no error, weird 203918492" />

<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3" />

<response value="NAK" rawmode="false" />

Configuring...

<log value="INFO: Calling handler for configure" />

<log value="INFO: Storage type set to value UFS" />

<response value="ACK" MemoryName="UFS" MinVersionSupported="1" Version="1" MaxPayloadSizeToTargetInBytes="65536" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" DateTime="Jul 12 2022 - 22:36:03" />

Ok

Requesting info on LUN 0...

<log value="INFO: Calling handler for getstorageinfo" />

No ack/nak

3rd / 4th / 5th …output:

Found EDL 9008

USB maximum packet: in=512, out=512

Configuring... bad XML

If you have any ideas please let me know
[Android Q&A, Help & Troubleshooting] Renate:
Oops, maybe this is the problem. I thought that we were talking about the A9.

This has a Snapdragon 460 and probably has eMMC storage, not UFS.

So lose the /u

edl /lprog_firehose_ddr_001360E1.elf
edl /g
[Android Q&A, Help & Troubleshooting] vuanh1408:
Wow, it works. I have both Hisense Touch and Hisense Touch Lite. Touch I have succesfully dumped the boot and vbmeta img with the old code. The code for touch lite is

./edl.exe /g /r /pvbmeta_a vbmeta_a.img
./edl.exe /g /r /pvbmeta_b vbmeta_b.img

./edl.exe /g /r /pboot_a boot_a.img
./edl.exe /g /r /pboot_b boot_b.img
[Android Q&A, Help & Troubleshooting] Renate:
You don't need to do /g unless you actually want to see it.

I like to keep the noise level down.
[Android Q&A, Help & Troubleshooting] vuanh1408:
I attached the patched boot and vbmeta for Hisense Touch and Touch Lite in case anyone needs it:

- TouchLite_L2134.6.03.01.B4

- Touch_L1834.6.02.01.B3

- Touch_L1834.6.04.04.00

Touch_and_TouchLite

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[Android Q&A, Help & Troubleshooting] vuanh1408:
ok so just ./edl.exe /r /pvbmeta_a vbmeta_a.img ?
[Android Q&A, Help & Troubleshooting] GhostScr1pt:
Any chance of getting the patched boot and vbmeta of the Hisense Touch_L1834.6.04.04.00?

Edit: I managed to dump it from my device
[Android Q&A, Help & Troubleshooting] doschxda:
This all looks amazing and such, but also a little abracadabra for a starter..

Two questions:

1. Is there somewhere a tutorial I can follow to root my A9? (nevermind, I found it on page 11)

2. What are the prospects of LineageOS becoming available for this device?

Thnx!
[Android Q&A, Help & Troubleshooting] edoom1981:
First of all, I'd like to thank everyone involved in this development, the much awaited community support this wonderful device needed so much!

The thing is, it's been ages since I last rooted a phone, and I'm getting some difficulties here...

I have managed to get to FastBoot mode, but I'm at a loss about the folder structure and the files involved in the following steps.

EDIT:

I presume those .img are two different files. one of those, should be the one patched by magisk. but, I don't know which one is the other, neither wich one should be applied first... Or should I mount the same boot.img twice?

It may sound really noobish but, where can I obtain vbmeta.img?

I managed to install boot.img (the Magisk patched image) and had to finish the process without applying vbmeta.img (yeah, pretty stupid move on my part, but I was in a hurry and had to finish the procedure ASAP), and now the phone is stuck on recovery mode (or so I think, a 2-option screen in Chinese that prompts the phone to reboot again and again...)

I've tried to redo all the process from scratch, but now it seems impossible to get to fastboot mode again, and the following messages appears in the Win Terminal screen when typing the "./adb reboot fastboot" command:

"error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device."

I know I'm screwed thanks to my own carelessness and a bunch of mistakes on my part but, please, could anyone help me out to get my A9 up and running again? Thanks in advance!!!

EDIT:

Nevermind, I managed to get it up and running again, and I finally got to root the device successfully!! Thanks anyway!!
[Android Q&A, Help & Troubleshooting] Ololiuhqui:
Did anyone manage to install a custom recovery (like TWRP) too?
[Android Q&A, Help & Troubleshooting] korawasdead:
it's a bit confusing because it's mostly designed for A9 root even though it's the same process. mine is a Hisense Touch_L1834.6.04.04.00. can you provide a very clear instruction guide on how to do it? It would be very helpful.
[Android Q&A, Help & Troubleshooting] samgabbay:
Hello,

Has anyone succeeded in using any other LiteGapps package like Nano or Go? when i do it on my phone it boot loops.

Thanks
[Android Q&A, Help & Troubleshooting] buzuddha:
[cross-posted from reddit]

Hi all,

Just rooted my own A9 the other day. Everything went well, but I'm worried about security here, so haven't yet put in the SIM nor entered any passwords into anything.

I've set up Adaway as per this post about the A5 to modify /etc/hosts to redirect calls to known malicious domains to 0.0.0.0. The main issue I've run into is that many of the block-lists don't work with Adaway. The china-specific and A5-specific lists that I'm most concerned about, as this phone is made for the Chinese market are in Adblock format. I see there is an import/export tool Adaway has but I can't seem to make it work. Should I just try to convert with sed/awk or somethign? Many of these domains have || and other characters you don't usually see in URLs, so I'm not sure if that's part of the Adblock formatting or if these are actually the domains.

Another question is what packages to disable or delete with adb? Has anyone checked what is running on this device that may be malicious ?

Thanks for any help here!!
[Android Q&A, Help & Troubleshooting] deny-bas-dns:
Blocking bas.phone.hismarttv.com with nextdns via adb (guide linked below) and rebooting will block folder app recommendations.

With the default blocklist and manually adding qq.com and amap.com should block most china dns requests besides the ones from Hisense direct. Let me know if there are any more I should block! More details here:

https://www.reddit.com/r/eink/comments/178moyc
[Android Q&A, Help & Troubleshooting] zhelan:
Hello, I'm bootlooping after installing a magisk module. Is there a way to back up my user space?

I can't access adb and I don't see how to access fastboot, the chinese recovery is not even working.

I just order a edl cable.

By the way, if you want to keep pinned services (screenshot on locked screen or on switch off screen) while using another launcher than the stock vision launcher.

Put this code is a executable file chmod +x it in de /data/adb/service.d folder.

#!/system/bin/sh

# Define the package name of the app

app_package="com.hmct.vision"

# Function to check if the app is in the foreground

is_app_in_foreground() {

local foreground_activity=$(dumpsys activity activities | grep mResumedActivity)

echo "$foreground_activity" | grep -q "$app_package"

}

# Loop until the app is in the foreground

while ! is_app_in_foreground; do

# Launch the app's main activity

am start -n com.hmct.vision/.Launcher

sleep 5 # Adjust the delay as needed

done

# Loop until the service is started successfully

while ! am startservice com.hmct.vision/.einkpin.PinnedService; do

sleep 5 # Adjust the delay as needed

done

# Once the service is started successfully, set the home activity

am start -a android.intent.action.MAIN -c android.intent.category.HOME

It runs the launcher main activity, checks that it is on the foreground, when it is runs the einkpinned service and goes back to the regular chosen launcher, at every boot of the phone

Third question :

Should there be an update, to get the latest boot img,can I use B. Kerler's edl and

edl r boot_a,boot_b boot_a.img,boot_b.img --memory=ufs

Then patch it with magisk, and then flash it with fastboot. But would I loose my user data?
[Android Q&A, Help & Troubleshooting] vuanh1408:
You can find a very detail post on how to do it: #209. Just follow the guide, skip the "prepare the boot.img" part and use my patched boot.img instead
[Android Q&A, Help & Troubleshooting] korawasdead:
Thanks for the answer last night i successfully root my device Hisense Touch, with out any issues. The only problem i face up recently i got bootloop after install some magisk module. Fix that by go to recovery mode and factory reset the device. another method you an do flash with edl cable. I'll write my guide later.
[Android Q&A, Help & Troubleshooting] smartguy_noncoder:
I just bought a Hisense a9 hoping it could help me digitally detox, slow down and relax as I have pretty severe ADHD and get addicted to my smartphone too easy. I really want to make use of this because the operating system that comes with the A9 is half Chinese and a pain in the neck to use. I bought an EDL cable and am very, VERY eager to get Google Play on Android 11 going on this thing. Could someone please be a bit more explicit with the directions? For example, under "prepare boot.img" how to you go about transferring the files listed to the phone and where specifically do you transfer them to?

I'm afraid of bricking this wonderful device that I had to go to great lengths to get and shell out $400 for.

Sorry I'm just not at all experienced with flashing ROMs and stuff like this. I appreciate your time and hard work.

EDIT: if it would benefit the author of this hack, I promise to provide a review of my phone with Google Play on it on YouTube and reference you and your post.
[Android Q&A, Help & Troubleshooting] Renate:
Preparing boot images?

I usually rinse them in the sink, pat them down with paper towels, put them in a 350°F oven and baste with butter.

Or maybe I'm thinking of turkeys?

You need to install the Magisk apk. That's simple enough. I like to download on my desktop and then:

C:\>adb install Magisk.apk

Then you need to put the boot image that you just pulled off your A9 somewhere:

C:\>adb push boot.img /sdcard/

Then you run the Magisk application and point it at /sdcard/Magisk.img
[Android Q&A, Help & Troubleshooting] Ololiuhqui:
Essentially you need to patch the boot image with magisk, so that later you can flash (install) the boot image already rooted.

This might be helpful: https://yewtu.be/watch?v=iSwaFLWZjTE
[Android Q&A, Help & Troubleshooting] smartguy_noncoder:
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the

spelling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:1

+ adb install magisk.apk

+ ~~~

+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException
[Android Q&A, Help & Troubleshooting] Renate:
You have to install adb on your desktop. Google "minimal adb".

You'll find that adb is your friend that you'll use often.
[Android Q&A, Help & Troubleshooting] JessIsAFK:
You can also open a terminal in the folder that you downloaded adb to, and instead of typing in "adb <command>" you can use "./adb <command>" Another option is adding the folder to your systems PATH, through Advanced System Settings -> Environment Variables. However, this can be complex, and if done carelessly can cause issues.

A general way to do this on Windows 11 is, assuming that your adb is in a folder called "C:/Utilities/platform-tools"

1. Enter "view advanced system settings" into windows search and click the result of the same name.

2. Under the "Advanced" tab, click the button for "Environment Variables".

3. Under "User Variables for %username" click on PATH and hit Edit.

NOTE: the next part can cause pain, so please follow this guidance correctly. Incorrect modification can cause issue with your other paths. I *highly* recommend taking note of the variables already there, and either take a screenshot or write it down before continuing if you have any hesitation. (my config only has "%USERPROFILE%\AppData\Local\Microsoft\WindowsApps", but everyone's setup is different)

4. Click the "New" button, and it will open a new slot. do not overwrite any variables already there, again I *cannot* stress this enough. Add the folder path to your platform-tools directory. For me, that's "C:/Utilities/platform-tools"

5. After confirming your changes are correct, hit "ok", then "okay" and then "apply" (or "ok", if that's not there).

6. Log off or Reboot. once done, your adb should work everywhere without the need of an external installer.