yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ferlanero:
Finally I get rid of the phone brick following these steps:

1. Press vol+ + power for 25 seconds to enter Fastboot mode

2. In a console type:

fastboot flash boot image-new.img

to reflash the boot image again

3. In a console type:

fastboot reboot

Phone unbricked
[Android Q&A, Help & Troubleshooting] tidip:
I am brand new to rooting phones. I have an A5 Pro CC: can I first upgrade the phone through OTA updates before unlocking/rooting it or do I risk to loose the ability to unlock/root it once it's upgraded?
[Android Q&A, Help & Troubleshooting] zizicici:
I don't have A5 pro cc but you should read the instructions. Usually it would state a specific version if it only works with that version. Otherwise just update to the latest version. Read carefully. Many ppl did it wrong or didn't know what to do even it's already in the instructions.
[Android Q&A, Help & Troubleshooting] tidip:
Thanks. OK, I will check then and follow the instructions.
[Android Q&A, Help & Troubleshooting] lilila:
I have A7CC. Tried the unlock first.

Downloaded hisense_a7cc.zip from github.

Can't enter download mode with POWER + UP + DOWN combinations.

So I tried adb reboot autodloader instead.

Then I run the bat file included in hisense_a7cc.zip:

spd_dump exec_addr 0x3f88 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

TIMEOUT /T 10 /NOBREAK

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

TIMEOUT /T 10 /NOBREAK

spd_dump exec_addr 0x3f28 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

Now my AC77 is bricked? It's not responding to any button combinations. But I do get a notification sound every time I plug the phone with USB cable to PC.

Anyone has any idea?

Thanks
[Android Q&A, Help & Troubleshooting] chatgptfun:
Hi,

Please I am confused, can you help me?

I want to unlock and install google playstore in Hisense A7cc. What I could understand from the forum is

1. You need to unlock bootloadder first

Install SPD drivers and Hisense files (HisenseA7CC.zip) uploaded by member lichobg, I think whom you followed.

Then simply load the phone in fastboot mode (by using powerbutton _ volum+ and volum-) and run the bat file in the forum user lichobg folder he uploaded easyupload.io (HisenseA7CC.zip)

2. What are the steps to install magisk? and how to then install all google apps? Where to get them ?

Should I reset phone before all this?

Please help
[Android Q&A, Help & Troubleshooting] lilila:
Yeah, just changed address spd_dump exec_addr 0x3f88 to spd_dump exec_addr 0x3f28 .

And ran the bat file again. Looks like my AC77 is unlocked now.
[Android Q&A, Help & Troubleshooting] r1c47:
Awesome! (y)

When I did mine I noticed that when starting the phone from full shutdown it would now show a message in extremely small font saying something about the bootloader being unlocked.

1. Yes unlock the bootloader but the bat file I used is from TomKing062's github, which I just noticed he updated a few days ago. lichobg's file is the boot image with magisk already patched in. It expires in one day so I suggest you get it as fast as you can.

2. once you flash the patched boot image then just start up the phone and look for the magisk app which should already be installed. open it and use it to load the gapps module.

Resetting the phone shouldn't be necessary as it will al get wiped during the process of unlocking the bootloader and rooting. Just remember to backup any files in the phone you want to keep because they wont be there anymore when you finish this process.
[Android Q&A, Help & Troubleshooting] chatgptfun:
Thank you for you guidance. One last question, there is no difference between TomKing062's github file and lichobg's file. The only difference is lichobg one has magisk patched in it, it I install TomKing062's github, I have to do extra step

"TomKing062's github", it means you had to install magisk again from github magisk link. So, using lichobg's file is more direct.

Is there any changes I have to do like in any file or memory address etc?

If not then, it's as simple as using lichobg's bat file run after connecting phone in its fastboot mode and having SPD drivers installed.
[Android Q&A, Help & Troubleshooting] r1c47:
Which file from lichobg are you referring to? In my posts I'm referring to his file in post #231 which is only the patched boot.img for A5CC, A7, and A7CC. I used tomking's files to unlock the bootloader of my phone using the bat file and then used lichibg's patched boot.img because I forgot to backup mine and then once I got out of the softbrick wasn't able to get it to back up. So using lichobg's was convenient. well I guess you don't really need tomkings github files if you know the correct commands to use in cmd to unlock the bootloader,

I would still use it because just running the batch file was so much easier for me because it already had the correct command to use for my phone and I had a lot of trouble getting things to work because I was using commands for the wrong phone. Although it didn't create a backup of my boot.img so I had to use lichobg's anyways, but yeah..
[Android Q&A, Help & Troubleshooting] chatgptfun:
Oh, you are right!

Yes file is #231, i thought it would itself unlock bootloader and also install patched boot.img file. So there are two different files. Lichobg's post #197 is the one i think describing all but your instructions are very concise

So for myself, I should used the tomking github file you gave link, run it first then run licho's boot image file(as I don't want to manually type all the commands due to typo etc errors) and all done!

What tool did you use to flash the Lichobg's boot images?

There are multiple image files in his zip file, which one to to flash and in what order you did?
[Android Q&A, Help & Troubleshooting] r1c47:
Have you used adb or fastboot commands before? Also just to confirm, you are using windows, right?

Anyways this video will show you how to set up adb.

Once you have that set up then enable "USB debugging" on your phone and you should be able to get adb and fastboot to work.
[Android Q&A, Help & Troubleshooting] waka.vn:
Thanks you for your files. My phone is working perfectly now.

However, anyone have problems with TTS? I can't use google TTS even install google TTS from Google Play Store :(
[Android Q&A, Help & Troubleshooting] chatgptfun:
Yes and using windows.

Got it all now.

1. Use tomking's A7CC file to unlock bootloader (use bat file) but have SPD driver installed and use download mod(power+ volume - + volelume +)

2. Use A7CC image file from lichobg zip, use adb and commands to FLASH that image ..

3. Restart phone. Use magisk app in the phone to download all the gapps

Thank you sooooo much friend.

Did you use it to flash Hisense A7CC?

Hi Lilila,

Please can you guide me on this

1. Do I need to change 0x3f88 to 0x3f28 in Tomkings github bat file hisense_A7CC.zip? Otherwise it will brick?

2. I also cannot boot it into fastboot mode, how did you do it with using adb? After turning adb on and connecting USB to Mobile, what commands should I run? And after running then should I double click bat file in windows?

Please help me
[Android Q&A, Help & Troubleshooting] mello73:
Hi, while waiting that my new A5Pro CC ship from China, i am reading the instructions to unlock bootloader and root phone.I have one question:

@Limio in msg #195 say.

Comparing the commands to unlock bootloader the only difference is in the last command:

@Limio command

Vs

GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692

This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692 - TomKing062/CVE-2022-38694_unlock_bootloader

github.com

They are quite different, so i am asking you:

which one is right to use ?

Thanks,
[Android Q&A, Help & Troubleshooting] chatgptfun:
UPDATE. IT'S WORKING NOW. I installed adb and connected device

Used this command

adb reboot autodloader

The phone immediately became a brick

Then i clicked bat file in Tomking's guthub A7CC zip.

It ran , few times showed FAIL , I had to restart, and few times asked to type yes, (as told by Lichobd in #197 post)

Then the phone reloaded..

But didn't see any Chinese message if it is unlocked or not whenever I restart phone

Man! This is getting difficult.

How to check if it is unlocked? I don't think it's unlocked because there is no message

Will trying to flash boot image tell whether it's unlocked or not?

Please Can you these two text files. They show error log, one before restarting with POWER + UP and other phone is restarted and I again click bat script

Hi Lichobg,

UPDATE. IT'S WORKING NOW. I USED tomkings A7CC bat file without any changes and it the phone restarted fine. I don't know if the phone is unlocked or not. I don't know how to check it.

There is no chinese msg on phone restart so it is not unlocked

Please Can you these two text files. They show error log, one before restarting with POWER + UP and other phone is restarted,
[Android Q&A, Help & Troubleshooting] r1c47:
Go to developer options and there should be a setting in there that tells you if it's unlocked. The message at bootup that I was talking about when I unlocked my phone is not in chinese, it's just in very small white font on very small black bars to the top right of the boot screen.

EDIT:

Also, when I unlocked mine, the button combination I used to enter fastboot while softbricked was POWER + VOL+ + VOL-. I had to hold it for about 12 seconds until I heard the windows chime for a new connected device and then I checked it was recognized by typing "fastboot devices", only then I ran the bat file.
[Android Q&A, Help & Troubleshooting] lilila:
I was not able to enter download mode with POWER + UP + DOWN combinations.

So I enabled USB-debugging in setting, connected the phone to PC, then use

adb reboot autodloader

Then I changed 0x3f88 of the bat file into 0x3f28, and double clicked the bat file:

spd_dump exec_addr 0x3f88 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

TIMEOUT /T 10 /NOBREAK

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

TIMEOUT /T 10 /NOBREAK

spd_dump exec_addr 0x3f28 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
[Android Q&A, Help & Troubleshooting] chatgptfun:
Thank you so much for reply.

Could you be kind enough to see my log ( text files) in my post #287(it's above) and see anything wrong?

One thing I can see is that I didn't change the memory address like you did, old memory address was making your mobile bricked but for me, it is working fine just NOT unlocking bootloader that's it.

In the logs if you see, it doesn't write anything to the memory I think.

Any suggestions 😞

Thanks and sorry to be of botheration.

In the developer options I can still "deselect/select" Allow OEM unlocking button, which shows its not unlocked. It should be readonly (can you check yours? Is it read-only right?)

Also in logs I attached, you can see it didn't write anything....it should write long addresses like...00039983774 .. etx etc

May be I will give Zidag drivers a try because I just installed SPD drivers and connected phone and did it

Otherwise I will see if I can research more. May be like user "Lilila", I have to change memory address...

Too stressful these things are, may be I use phone as it is
[Android Q&A, Help & Troubleshooting] r1c47:
Don't worry too much. It took me more than a week to figure out what was happening with my phone.

Just to confirm some things, your phone is an A7CC right? The address you use depends on what phone you have and the method used to access fastboot from what I remember.

I dont think you will actually brick the phone all the way because I do remember playing with the address numbers trying to get tit to work and was able to recover. BTW, were you able to make a backup of your boot.img?

BTW Errot2.txt looks about right compared to what I remember I saw when doing mine. it's just missing another yes at the end.
[Android Q&A, Help & Troubleshooting] chatgptfun:
Hi,

Thank you a lot!

Yes i pressed yes after it again.

The device is Hisense A7CC and has Chinese and English language by default.

I think I should give changing memory address from 0x3f88 to 0x3f28 as user Lilia did in post #289.

I will play with it more and update.

Thanks a bundle!

It's A7CC model HNR320T

What I will do, thanks again, try changing memory from 0x3f88 to 0x3f28 like user Lilila did i ln post #289. Afterwards I will try with using Zidag drivers instead of SPDs

Will keep updated. Thanks a heaps!!!

BTW you cannot see if phone is bootloader unlocked or not because

fastboot devices command works but

fastboot oem device-info doesn't work, I think it's not supported by phone, this command tells if bootloader is unlocked.
[Android Q&A, Help & Troubleshooting] cklm:
Device is A5 Pro CC:

After device is bricked from adb reboot autodloader and driver is installed using zadig, I can't get spd_dump to find the device; I keep getting:

| Waiting for connection (30s)

| find port failed

Anyone having this issue or know what the issue could be?
[Android Q&A, Help & Troubleshooting] chatgptfun:
Hey

It's working now!!!

It's unlocked! I used Lilila's memory change trick. Thank you Lilia!!! And you!!!!

May good luck always have you in it's embrace.

We should either tell Tomking's or Lichobg may be so that the fix it

Here is the summary to unlock it

1. Install SPD drivers

2. Download model specific zip from Tomking's ❤️ repository

3. Turn on your mobile and Allow OEM unlock and USB Debugging in Developers option.

4. Install ADB

5. Change memory address in Hisense_A7cc folder file onekey_fsl1.bat from 0x3f88 to 0x3f28

6. Run this command in adb

adb reboot autodloader

7. Now double click onekey_fdl1.bat

Done!!!
[Android Q&A, Help & Troubleshooting] r1c47:
Does the phone show up when you run "fastboot devices" after holding the power and vol key/s for 12 or so seconds?
[Android Q&A, Help & Troubleshooting] cklm:
I can hear the device disconnect/connect after about 5 seconds, if I hold closer to 20 seconds another disconnect, and somewhere before the last and after I have tried: no devices output when running fastboot devices
[Android Q&A, Help & Troubleshooting] r1c47:
Have you already installed the SPD drivers?
[Android Q&A, Help & Troubleshooting] mello73:
Hi @luzki , your current firmare is the ML Multi Language custom one:

Spoiler content hidden.

as described you do not get OTA update.

I have just received mine from China and have the same problem.

I am downloading an old Stock Release firmware and will try to flash it.

If successful i will notify you.
[Android Q&A, Help & Troubleshooting] luzki:
That would be great... So your procedure is to downgrade first and then trying to update using OTA? Please share here if success and if you still have english language in phone (i have english + chineese now). Thank you!

Btw link to 'firmware choice' is not working, what is it about?
[Android Q&A, Help & Troubleshooting] mello73:
Was just the screenshot, seems that putting it in the spoiler section failed, i will add it here:
[Android Q&A, Help & Troubleshooting] cklm:
I installed libusbk using zadig; is there another driver I need?
[Android Q&A, Help & Troubleshooting] mello73:
seems to work, but will be painfully slow!!

First it updated to 1732.6.08.02.00 (was 1732.6.06.04.00)

not it's updating to 1732.6.11.03.00

i will notify ...
[Android Q&A, Help & Troubleshooting] mello73:
finished, updated to L1732.6.17.01.00!!

go to {Mod edit: Link to paid services website removed. Oswald Boelcke, Senior Moderator}

download firmware and extract to a Vfat formatted microSD (16GB).

(In the root of the SD must be present the dir HLTE203T_TF)

Then turn off phone insert mSD.

Press both Volume + and Volume - and at the same time press and keep pressed power button until something happen.

After flashed you will be able to upgrade OTA.

But be prepared that is a long long long process, as it do one update at time..
[Android Q&A, Help & Troubleshooting] luzki:
Well, when it came there was some

thanks a lot for your advice. I will try same procedure as you when i have time. So you have latest fw version using just ota updates and english language is there? Everything is fine and working ok?
[Android Q&A, Help & Troubleshooting] r1c47:
If you have problems flashing you'll probably nee the SPD drivers.
[Android Q&A, Help & Troubleshooting] cklm:
After installing those drivers, deleting the devices and reinstalling multiple different drivers, still can't seem to get device to show up in either ADB/Fastboot. The device was recognized at first, I was able to run the reboot autodloader, the device is just not recognized anymore. I've held the volume + -, power for long enough to enter fastboot too, I can hear the device disconnect but it immediately reconnects, so not sure where the issue is?
[Android Q&A, Help & Troubleshooting] mello73:
Yes you can choose between china and english in setup.

I have already unlocked bootloader and installed magisk + LSPosed (i use microG).

Now that i have root i will try to customize it some more ....
[Android Q&A, Help & Troubleshooting] r1c47:
That's the phone rebooting into fastboot.

Sounds like the same issue I had in #234 and #237

After getting it to fastboot mode look for the phone in device manager and update its driver to SPD driver.

then check if it shows up when you use the command "fastboot devices"
[Android Q&A, Help & Troubleshooting] luzki:
I updated my phone your way. Thanks, now it is on latest sw version. Could you summarize how you rooted the phone after it was updated to latest version? I am quite lost here and dont want to brick the phone.
[Android Q&A, Help & Troubleshooting] nakaata:
Hi, new to rooting but got a Hisense A5 Pro CC. It was network locked due to an unfair law but I legally purchased it. Thanks to this forum, I rooted my phone using Magisk and installed Gapps. Is there a way to change the IMEI so I can use it as my main device? Any Magisk mod recommendations? Any nuances to consider with Unisoc?
[Android Q&A, Help & Troubleshooting] r1c47:
I'm pretty sure that changing IMEI is illegal.
[Android Q&A, Help & Troubleshooting] cklm:
Within device manager I assigned SPD 4.20 driver to device, still no dice on showing up in fast boot. abd is not recognizing any devices/emulators, and nothing appears in fastboot. Device is now ghost mode :/
[Android Q&A, Help & Troubleshooting] mello73:
I just followed documentation on TomKing repo:

GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692

This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692 - TomKing062/CVE-2022-38694_unlock_bootloader

github.com

(but i use Linux not Windows, so had no need to download "ad hoc" usb drivers)
[Android Q&A, Help & Troubleshooting] vegeta123:
thanks for th eguide man. really helpful. but am stuck at the unpacking and repacking of the patched magisk img file. How do i run the command for that? can you give me the exact code? I've never rooted or used terminal before so its a bit confusing to me
[Android Q&A, Help & Troubleshooting] vegeta123:
i get this error after renaming the image-new file and running the command

(python2 avbtool add_hash_footer --image AIK/image-new.img --partition_name boot --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --salt 5F55215FD2302D021F850B55912ED48D176784678692DC012E054B1ECD0BE025)

in the avbtool folder- avbtool:

Error getting public key: unable to load Public Key 9716:error:0909006CEM routines:get_name:no start line:crypto\pem\pem_lib.c:745:Expecting: PUBLIC KEY
[Android Q&A, Help & Troubleshooting] vegeta123:
i finished insatalling gapps and was given option to reboot and i clicked on it. after that it wont power on again @r1c47 can u help?
[Android Q&A, Help & Troubleshooting] Pablitosaurus:
Hello, thank you all for the help !

I am stuck in the last part: adb doesn't find my phone so I can't push the final .img,

I can't find a way to download the USB google driver on windows, it always choose another one (or doesn't find it at all) even when I try: manually, with an advanced boot menu + allow unsigned drivers and I even tried on macOS... the same thing for "SPD Driver R4.20"

I can't find a way to make adb find my phone (everything worked fine bfr).

Thanks !
[Android Q&A, Help & Troubleshooting] chatgptfun:
Did you try to redo the steps? Put phone in fastboot mode and redo all steps?

Also try to connect it to pc using usb cable then open adb then type this command

adb devices

What do you see?

You can use lichobg already patched and signed files

Use SPD drivers?
[Android Q&A, Help & Troubleshooting] Pablitosaurus:
It was in this msg sorry
[Android Q&A, Help & Troubleshooting] vegeta123:
but it wont even power on. All i see is the hisense logo. when i hold the power on button all it does is on the frontlight. thats it
[Android Q&A, Help & Troubleshooting] chatgptfun:
Try this

Connect it to usb

Turn on the adb

Write this

adb devices

Do you see any numbers etc?
[Android Q&A, Help & Troubleshooting] vegeta123:
i tried adb devices- nothing. and when i do reboot - no devices or emulators found
[Android Q&A, Help & Troubleshooting] vegeta123:
no. i get this- "List of devices attached" and then a blank line after that
[Android Q&A, Help & Troubleshooting] chatgptfun:
It happened to my phone too before. I connected it to usb

Then power + volume up until it showed me battery icon in the screen big icon

Then i took it off the usb charging cable

Then press power button and wait

If not still on then again power button + up hold

It made my one fine

Also when your phone shows Hisense logo, does it show Chinese on top right corner of screen?

Hi r1c47

Any suggestions?
[Android Q&A, Help & Troubleshooting] vegeta123:
thanks ill try it. no chinese. but thing is my up button stopped working months ago so that might be a problem
[Android Q&A, Help & Troubleshooting] Pablitosaurus:
I succeeded to install the drivers but none of them worked... I was wondering if an EDL cable could help, as in:

https://www.reddit.com/r/eink/comments/16tpr96
[Android Q&A, Help & Troubleshooting] tidip:
I would like to unlock and root my A5ccpro from Ubuntu. I have followed the first instructions from the Git Repo:

sudo apt-get install build-essential libusb-1.0-0-dev git
git clone --recursive https://github.com/TomKing062/CVE-2022-38694_unlock_bootloader.git
cd CVE-2022-38694_unlock_bootloader
gcc chsize.c -o chsize
cd spreadtrum_flash
make

Then I copied the chsize and spd_dump to the soc/ums512 subdirectory. I guess this is it when they write "copy to the tools directory". But now I would like to know which script to run first:

manual_command_fdl1.txt or manual_command_spl.txt?

Also it's not clear to me if I need other files in that directory, right now I have this:

Is this enough?
[Android Q&A, Help & Troubleshooting] tidip:
If I read correctly #195, I should first make a backup of my boot loader right with this command?

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x3ee8 fdl uboot-mod.bin 0x9efffe00 exec read_part boot 0 35M boot.img reset