yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ferlanero:
Thanks guys for your help, but I only get CHECK_BAUD FAIL advice whatever I do :(
[Android Q&A, Help & Troubleshooting] ferlanero:
GUYS! I get it!!! Simply by entering in downloader mode, vol+ power for 25seconds and changing fist command by:

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec read_part teecfg 0 1M teecfg.bin read_part trustos 0 6M tos.bin read_part sml 0 1M sml.bin erase_part splloader reset

Nex5, remain exact :)
[Android Q&A, Help & Troubleshooting] zizicici:
What a great news! Hope Hisense Q5 will be supported soon, it uses the same CPU as Hisens A5 Pro (Unisoc T610).
[Android Q&A, Help & Troubleshooting] ferlanero:
Having this news are indeed really good news for our phones :D
[Android Q&A, Help & Troubleshooting] kyle564448:
Thanks a ton! Worked for me! All google apps are working properly now! What a pity that the phone doesn't support US carriers
[Android Q&A, Help & Troubleshooting] r1c47:
Shame that The A5 Pro that I have is the non-CC version. ):
[Android Q&A, Help & Troubleshooting] museng:
sA5pro may also
[Android Q&A, Help & Troubleshooting] lennonyr:
help!!

My phone is A7, I downloaded related drivers and files of A7.

firist I enable USB debug in Develop mode, then run "adb reboot autodloader" from PC, the phone screen stuck, after install success of Zadig (Zadig recognized the phone as “iWhall" sth.) , the phone screen still stuck, whatever key combo I have tried, screen and phone had not any reaction！

any buddy have advise of this, the phone is really a brick now.
[Android Q&A, Help & Troubleshooting] r1c47:
Have you tried this?:

https://xdaforums.com/t/hisense-a5-...ode-even-with-edl-cable.4408635/post-86840081
[Android Q&A, Help & Troubleshooting] SkingTom:
hisense q5 supported now

and if you appreciate my work, i registered yx42_44@126.com as my Paypal
[Android Q&A, Help & Troubleshooting] ferlanero:
Donated. Great achievement unlocking bootloader and gaining root access in Hisense A5 Pro CC. Thank you very much.
[Android Q&A, Help & Troubleshooting] elermo:
does this also work for the a5 pro NON CC?
[Android Q&A, Help & Troubleshooting] ferlanero:
Sure. Just follow these instructions: https://github.com/TomKing062/CVE-2022-38694_unlock_bootloader
[Android Q&A, Help & Troubleshooting] elermo:
im still thinking about if i should get the hisense a5 or a9 ~ but as far as i know the a9 has not been rooted yet. does anybody know, if this could be possible in the near future? is somebody on it?
[Android Q&A, Help & Troubleshooting] lichobg:
There is no news for A9 . But:

If OEM unlock work then with modified developer image is possible to try and root the A9.

So i have working OEM unlock. But no time :)
[Android Q&A, Help & Troubleshooting] elermo:
if you need an incentive, a reward is offered here in this post:

[Hisense a9] Root - Reward Offered (Snapdragon 662)

The Hisense a9 is an e-ink 4g smartphone that I want to use as my own Frankenstein light phone. I would like to root mine and use this custom launcher to create a minimalist phone that isn't quite as useless as the Light Phone concept (i.e...

xdaforums.com

:))
[Android Q&A, Help & Troubleshooting] lichobg:
Just kidding.

No OEM unlock for A9

;)

fastboot devices

48960cf6 fastboot

fastboot oem device-info

(bootloader) Verity mode: true

(bootloader) Device unlocked: false

(bootloader) Device critical unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.001s]

Finished. Total time: 0.001s

fastboot flashing unlock

FAILED (remote: 'Unlock is not allowed!')

fastboot: error: Command failed
[Android Q&A, Help & Troubleshooting] kamil404:
A5 PRO CC

I have a problem with step of creating a copy of boot.img:

PS C:\Users\krzys\Desktop\a5 pro cc - rooting\hisense_a5procc_fdl1> ./spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x3ee8 fdl uboot-mod.bin 0x9efffe00 exec read_part boot 0 35M boot.img reset
libusb_control_transfer ok
CHECK_BAUD bootrom
BSL_REP_VER: "SPRD3\0"
CMD_CONNECT bootrom
current exec_addr is 0x3ee8
timeout reached
PS C:\Users\krzys\Desktop\a5 pro cc - rooting\hisense_a5procc_fdl1>

Occasionally it goes that way:

PS C:\Users\krzys\Desktop\a5 pro cc - rooting\hisense_a5procc_fdl1> ./spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x3ee8 fdl uboot-mod.bin 0x9efffe00 exec read_part boot 0 35M boot.img reset
libusb_control_transfer ok
CHECK_BAUD FAIL
CHECK_BAUD FAIL
CHECK_BAUD FAIL
usb_send failed : LIBUSB_ERROR_TIMEOUT

Each time the same result and I unplug and plug again my phone, then entering download mode by POWER + UP + DOWN for 10 seconds (only then device is visible in Windows) and again the same result.

What is wrong?
[Android Q&A, Help & Troubleshooting] zizicici:
Try to change the address 0x3ee8 to 0x3f48. See Lichobg's post on #197.
[Android Q&A, Help & Troubleshooting] Imlosrila_36:
Hi, can I please get new links for a7cc boot image? i cant seem to get the boot image working.
[Android Q&A, Help & Troubleshooting] r1c47:
I have a question about the phone because I thought I had a HisenseA7CC but now Im not quite sure and I dont want to brick the device.

Ok so I factory reset the device before starting to try to root/unlock the bootloader. It's supposed to be an A7CC which means that the model# should be "ud710_2h10", right? According to the list tomking062's github device support list page.

But when I go to "About phone" in Settings, the model that it shows is HNR320T, and on the processor info it says "Tiger T7510".

Do I have a fake A7CC?

Also the A5Pro that I have says it's a "HLTE203T" instead of "ums512_1h10", with a Tiger T610, so I guess that's wrong too, fug.
[Android Q&A, Help & Troubleshooting] NomadicOldMan:
Is there any chance that the Hisense Hi Reader will be supported?
[Android Q&A, Help & Troubleshooting] r1c47:
Ignore my previous post I guess it maybe was the right model although I still dont know for sure because of the different numbers, but anyways I was semi successfully able to follow the github wiki and then somewhere midway post #195 and got to the part where you brick your phone(HOORAY! X'D), although I wasn't quite able to backup the phone because I was quite lost on the wiki until I read post198, sooo... yeah that's where I am right now.

Well I actually got to that part yesternight but got tired of trying to connect to the bricked phone and fell asleep. I might try to continue later tonight but ... yeah... that's where I currently am. The part that I think I'm currently stuck at is that I'm not quite sure I'm using the correct "exec_addr" and I'm not sure which is the right one for my A7ProCC because I dont know which SOC this has. If anyone can offer any advice, It'd be greatly appreciated.

Also the device doesnt show up anymore on "adb devices" and I cant enable USB debugging anymore because brick. So yeah.
[Android Q&A, Help & Troubleshooting] zizicici:
You have to know your phone model in order to download the correct files to root it.

You could try holding "power" + "volumn up" keys for perhaps 20 seconds to enter the bootloader mode while the phone is connected to the computer.
[Android Q&A, Help & Troubleshooting] zizicici:
- You are funny, if it's so easy and finacially feasible to fake an eink phone, then the eink phone market wouldn't be so niche.

- Yes. "ud710_2h10" I believe it's the SOC model (Tiger T7510).

- HNR320T is the phone model.

You are condused with the SOC model and the phone model. You can do an easy search using Google.com or bing.com or any other seach engine to clear things up.

I am a noob myself, I had tried and failed many time when I was trying to root my Hisense A5 and Q5. But I did do a lot of google searches. I have learned a lot from the searches. That's the least thing I can do if I was a noob and didn't know nothing.
[Android Q&A, Help & Troubleshooting] Cinnob:
Can you please repost download link for A5 ProCC magisck patched signed boot image. The link seems to be dead.
[Android Q&A, Help & Troubleshooting] SkingTom:
wow, another hisense t610 device 👀 will check weekend
[Android Q&A, Help & Troubleshooting] r1c47:
Boot image download link is dead please reupload. I'm trying to get the A7CC but none of the others are available either.
[Android Q&A, Help & Troubleshooting] NomadicOldMan:
Much appreciated, thank you. My fingers are crossed.
[Android Q&A, Help & Troubleshooting] SkingTom:
hisense didn't provide rom of hi reader publicly 😕
[Android Q&A, Help & Troubleshooting] lichobg:
Easyupload.io - Upload Files and Share Them Easily

Uplaod files easily and share them with your friends and colleagues. File upload solution for everyone. Upload big files and get a link to share effortlesly.

easyupload.io

Reupload

30 Days only - A5procc, A7, A7CC - signed patched bood image.
[Android Q&A, Help & Troubleshooting] android_495:
Hello,

thank you for finding how to unlock bootloader.

I have a question, is there a command to get out of autodloader without erasing again?

Thank you, my Hisense Q5 is now rooted
[Android Q&A, Help & Troubleshooting] r1c47:
Ok, PROGRESS!

I got the phone out of the softbrick(or at least I think I did, the phone is charging now) by connecting the phone to the computer and then holding the pwr,vol+,vol- keys to go into some mode the zadig can recognize and then using the onekey_*.bat for my phone in tomking's github releases pages in the assets for "Tool". When I got the batch file running in the cmd, then I just had to write yes a few times to allow the batch to erase, do something, and the write something else into the phone. sfter that was done then the phone rebooted into the charging image and that's where it has been for the last 20 or so minutes.

Now I'm just reading into how to get magisk onto the boot image, although I think that maybe lichobg's bot image already have it so I might not even have to do that. So I'm just trying to figure out what my next step should be and how to flash it.

Thank you very very much.
[Android Q&A, Help & Troubleshooting] r1c47:
Ok, I dont know what's happening. the phone booted ok and everything is fine but I'm not able to get the boot.img to flash into the phone.

I set android debugging in the phone and then "adb reboot fastboot" then the phone reboots into fastboot but when I enter the "fastboot flash boot A7CC_image-new.img" all I get is a "< waiting for any device >" from cmd, and nothing happens. I did try checking zadig and the phone shows up as "Unisoc Phone" but "(NONE)" in driver with USB ID: 1782 4EE0. I dont know if I should install the libusbk to it since I've not seen any mention of installing the driver at this stage. Anyone have any ideas on what my next step should be. I'm pretty sure now that all I need is to flash this boot, then install magisk to then install gapps and this will all be done but I keep running into problems on every step. ¯\_(ツ)_/¯

BTW the fastboot page shows this:

Product name - HNR320T

Bootloader version - unknown

Baseband ver -

Serial number - ##############

Secure boot - yes

HW version - 0

EDIT: Do not go into recovery, it's all in chinese and you might end up clearing user data, hard reseting it midway because you have no idea what's happening, and having to use google translate to figure out wtf is happening because it just keeps going to the same page and not allowing you to continue until user data clearing goes through all the way...

Thank you google translate!
[Android Q&A, Help & Troubleshooting] android_495:
For fastboot you do not need zadig (it's require only for autodloader)

You need to use driver from google : https://developer.android.com/studio/run/win-usb

On unisoc phone you click update driver, from folder, choose folder you downloaded, and it's call android bootloader or something, install it.

Then when you do "fastboot devices" you need to see your device, if there is nothing it do not see the device so you can't flash boot.
[Android Q&A, Help & Troubleshooting] tidip:
I am not sure reading all the instructions, is it possible to unlock and to root the A5 Pro CC only from Linux? I see that there are some instructions for Linux but it's not so clear to me...
[Android Q&A, Help & Troubleshooting] r1c47:
Thank you. I wasn't successful in getting that google usb driver to install because it wouldn't recognize the drivers in the folder when I pointed at the driver folder and its contents but I was able to get the "SPD Driver R4.20" that tomking mentions in one of his github's issues pages to successfully install. I hadn't tried installing it before because one of the comments in that issue page mentioned that it hadn't worked but, it worked for me. I just had to put the phone into fastboot, connect it to pc, and then update the driver software of the "unisoc phone" in device manager. Once the driver updated, "fastboot devices" recognized the phone and I was able to "fastboot flash boot A7CC_image-new.img" into the phone. After that everything else was easy.

Just loading the [MAGISK]LiteGapps into magisk module and setting google play.

Finally Success COMPLETE! *cue Metal Slug boss fight end music"
[Android Q&A, Help & Troubleshooting] lichobg:
To all trying to unlock/root. You need to keep in mind.

This is 2 step process.

1. Unlock boot-loader save boot image.

NOTE :

if you reboot in download mode with key combination (Power +UP+Down) first command there will be exec_dump_addr 0x3f48

and after that memory address will be 0x3ee8

by example:

spd_dump exec_addr 0x3f48 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec read_part teecfg 0 1M teecfg.bin read_part trustos 0 6M tos.bin read_part sml 0 1M sml.bin erase_part splloader reset

chsize teecfg.bin

chsize tos.bin

chsize sml.bin

spd_dump exec_addr 0x3ee8 fdl fdl1-boot.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 fdl teecfg.bin 0x9401fe00 fdl tos.bin 0x9403fe00 fdl sml.bin 0x93fffe00 exec

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec erase_part uboot_log write_part splloader spl.bin timeout 100000 write_part userdata userdata.bin reset

if you reboot to download mode with command

"adb reboot autodloader"

in all commands memory address will be 0x3ee8,

By example:

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec read_part teecfg 0 1M teecfg.bin read_part trustos 0 6M tos.bin read_part sml 0 1M sml.bin erase_part splloader reset

chsize teecfg.bin

chsize tos.bin

chsize sml.bin

spd_dump exec_addr 0x3ee8 fdl fdl1-boot.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 fdl teecfg.bin 0x9401fe00 fdl tos.bin 0x9403fe00 fdl sml.bin 0x93fffe00 exec

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec erase_part uboot_log write_part splloader spl.bin timeout 100000 write_part userdata userdata.bin reset

NOTE:

If you see error:

CHECK_BAUD FAIL

CHECK_BAUD FAIL

CHECK_BAUD FAIL

...

after command 2 or 3

reboot the phone with

Power + Volume UP

or reinsert usb connector.

If you see error

CHECK_BAUD FAIL

CHECK_BAUD FAIL

CHECK_BAUD FAIL

...

after first command check memory address 0x3ee8 or 0x3f48 see above.

Step 2 ist to patch and sign copied boot image with Magisck and unpack&repack.

If you have my patched and signed boot image there is no need for step 2 .

After Phone unlock and normal boot check if developer mode need to be reenabled and after that with command:

"adb reboot fastboot" - go to fastmode

Then with "fastboot flash boot image-new.img" - (change image-new.img with name from patched and signed boot image archive.

just load boot image to phone.

After that reboot with "adb reboot"

Install Magisk, Google etc. see above.

Happy rooting:)
[Android Q&A, Help & Troubleshooting] r1c47:
Absolutely, that is the way. I just found that while trying to perform those 2 steps there were a few driver troubleshooting problems, although it seems that if I had just used SPD_Driver instead of zadig it would have gone more smoothly. Also, if I were to try this again, I would just use the bat files in the phone's tool folder instead of typing the commands one by one to unlock the bootloader. The only problem that I had that I was never able to perform was getting a backup of my phone's boot which led me to sofbrick my phone quite a few times. So thank you once again lichobg.
[Android Q&A, Help & Troubleshooting] luzki:
Hi guys, i have a5 pro cc and i want to root it. Probably stupid question - does version of phone firmware matter or not? Should i first try to update phone to latest official version (if there is any update - wifi update says there is none) or it is irrelevant and just type of phone matters (a5 pro cc) regarding rooting procedure?

Btw does anyone have a plan to create some custom english/multilangue rom without chineese aps and with google framework already implemented?
[Android Q&A, Help & Troubleshooting] luzki:
Btw would some of our fellow chineese guys be able to download and share following latest official firmware for A5 Pro CC from this link? https://fans.hisense.com/thread-199093-1-1.html, e.g. uploading it to google disk/onedrive etc?

I am unable to register to hisense account since i dont have chineese mobile number and i would like to update my A5 Pro CC to its latest version. Thanks very much in advance!
[Android Q&A, Help & Troubleshooting] zizicici:
You can always update your phone OTA. I can update my A5 that way even my A5 is older than A5 pro cc.
[Android Q&A, Help & Troubleshooting] luzki:
Unfortunatelly no update is showing OTA but there is newer firmware on this link 😒
[Android Q&A, Help & Troubleshooting] zizicici:
Maybe you are on the latest firmware already. You sure the one in the link is newer?
[Android Q&A, Help & Troubleshooting] luzki:
I am not. The link refers to ROM L1732.6.12.02.00 but my phone has only L1732.6.09.02.00
[Android Q&A, Help & Troubleshooting] r1c47:
Do you mean before or after root/unlocking bootloader? Because I already did all the process to get google play services on my A7CC and I'm getting a notification to update, but I haven't for fear of losing it all.

Would I really want to tho?
[Android Q&A, Help & Troubleshooting] zizicici:
If you rooted, don't update unless you know it's safe, otherwise you would brick it. You will lose lose root access for sure.

For my A5, I need to downgrade it to a specific version (which is safe and will lose root access) and then upgrade one version by one version to the latest and root the latest one.
[Android Q&A, Help & Troubleshooting] funkypitt:
I'm trying the same process on my Q5 and I'm getting the same error. It looks like you succeeded but you don't say how you did it! Can you explain me what was the issue for you? I have the feeling that it might be simply a disguised "file not found" error, but nothing that I tried so far worked.

EDIT: solved it by using Linux instead of Windows.

If you have trouble using avbtool, just use it on Linux! It worked for me.
[Android Q&A, Help & Troubleshooting] luzki:
So this is latest version? Even higher than in official hisense forum? Can you share link to download this latest ROM please?
[Android Q&A, Help & Troubleshooting] ferlanero:
Sorry, I can't provide a link. I only update via OTA
[Android Q&A, Help & Troubleshooting] luzki:
I wish i could do as well, but no luck in my case. Seems like i will be stuck with L1732.6.09.02.ML which was on the phone when i recieved it last week. Maybe someone else would be so nice to provide a link to download newer rom which i can use to update my phone...
[Android Q&A, Help & Troubleshooting] zizicici:
Maybe you did something that blocked the OTA update? Otherwise it's hard to believe that you can't do OTA while other people can.
[Android Q&A, Help & Troubleshooting] luzki:
The phone was behaving unstable when i received it, there were preinstalled some apps like 2accounts, not working google play etc probably by the seller. So i did factory reset, now the system is working fine and should be in original state. But when i try to search for ota update, nothing is found and my version of system is L1732.6.09.02.ML. I am used to the fact that chineese phones/e-readers dont receive ota updates but they are available for manual update from sd card. So i am not surprised that it does not find anything in my case, but i am surprised that you did receive ota updates :-) I would like to have latest version as well but dont know how 😒
[Android Q&A, Help & Troubleshooting] sulunlun:
Thank you for sharing. Packed BOOT.

Also, my hand is A5PRO ( NO CC).

The system version is L1732.6.15.01.B10, can I use the packaged BOOT.IMG of A5PROCC to get ROOT directly?

TomKing062/CVE-2022-38694_unlock_bootloader said

If you want to Magisk ROOT , the corrected BOOT.img needs to be signed by avbtool to be flashed into A5.

Can you tell me how to do it?
[Android Q&A, Help & Troubleshooting] zizicici:
Read #195 and #197, they tell you how to do that.
[Android Q&A, Help & Troubleshooting] sulunlun:
I have unlocked the bootloader.

and now I'm downloading boot.img

I keep getting the following message , how do I troubleshoot it?

D:\hisense\A5Root>spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x3ee8 fdl uboot-mod.bin 0x9efffe00 exec read_part boot 0 35M boot.img reset

libusb_control_transfer ok

CHECK_BAUD FAIL

CHECK_BAUD FAIL

CHECK_BAUD FAIL

usb_send failed : LIBUSB_ERROR_TIMEOUT
[Android Q&A, Help & Troubleshooting] zizicici:
Check your Device Manager and see if there is some question marks. I guess the android usb driver is missing.
[Android Q&A, Help & Troubleshooting] sulunlun:
Thanks for the clarification.

According to #195 and #197, I have done the ROOT and GOOGLE on my A5PRO (NO CC), like GMAIL, PHOTOS, MAPS are all working.

Also, I downloaded my calendar and contacts from the PLAY store, and the calendar can be synchronized, but the contacts can't be synchronized even though I've tried for a long time. What else should I pay attention to?

Take a note

A5PRO NO CC

L1732.6.5.01.B10

I flashed LiteGapps_arm64_10.0_v2.9_official.zip with MAGISK , if I remove it , I may get stuck in the logo screen when I reboot.
[Android Q&A, Help & Troubleshooting] zizicici:
Sorry can't help. I don't have A5 pro and I use different package of Gapps. Maybe try to flash a different package of Gapps on your own risk.
[Android Q&A, Help & Troubleshooting] sulunlun:
Thank you for your reply.

I tried a different google package yesterday and he rebooted and got stuck on the logo screen.

I was thinking it might be a permission issue, I'll look for another way,. I think it's working well enough for now.

BTW, I've ordered an A7CC, I'll try it again when I get it.
[Android Q&A, Help & Troubleshooting] ibrahim7443:
Hi, after using "adb reboot autodloader" my phone became dead (permanently off with a frozen screen), I tried to hold the power button, but it didn't work, also tried disconnecting and reconnecting the battery but no luck. I think it's a software issue, please help if anyone knows it can be fixed. Thank you!
[Android Q&A, Help & Troubleshooting] zizicici:
If you read #195, you will see

"if everything worked, your phone froze now and it doesn't react to any touch or anything. It's basically a brick at this point.

it's here that you have to use Zadig to get the drivers going for your computer. When the phone is connected to your computer go to zadig, click on "List all devices". it should be listed on there and then you install the libusbk driver for it (if you don't know which device should be selected, the device id in zadig is: 1782 4d00)".
[Android Q&A, Help & Troubleshooting] ibrahim7443:
Many thanks
[Android Q&A, Help & Troubleshooting] sulunlun:
Thank you.

May I ask which google file you are using, can you share it?

I tried joy_gapps_installer-R07-core earlier , it doesn't work, it's stuck on the boot screen!
[Android Q&A, Help & Troubleshooting] zizicici:
That's the one I used, it worked every time I installed it on my A5.
[Android Q&A, Help & Troubleshooting] sulunlun:
Okay, thanks for the reply.

I've used this file on my A5 before, but it doesn't work on A5PRO.

I'll try again, thanks.
[Android Q&A, Help & Troubleshooting] ferlanero:
Upgrading to Magisk 26.3 bricks phone. So take care with it. Do you know if there is any solution than hard resetting the phone and not loosing all the data?