[Hisense A5 Pro CC] How to root/unlock bootloader?

[waka.vn]

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.

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

 

[chatgptfun]

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.

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.

 

[chatgptfun]

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

Did you use it to flash Hisense A7CC?

 

[chatgptfun]

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.

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

 

[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.

DON'T USE THE COMMANDS OF THE README FILE IN THE FOLDERS OR YOUR PHONE WILL BE STUCK

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

@Limio command

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec write_part uboot uboot.bin write_part splloader spl.bin reset

Vs

GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: User can execute unsigned binaries with BootROM privileges, which can be used to unlock bootloader

User can execute unsigned binaries with BootROM privileges, which can be used to unlock bootloader - GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: User can execute unsigned binaries with Bo...

github.com

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

They are quite different, so i am asking you:
which one is right to use ?


Thanks,

 

[chatgptfun]

Awesome!
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.

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

 

[chatgptfun]

So Google Apps is simple. I have rooted A7, A5proCC, A7CC.
Process can be simplified if you have magisck patched signed boot. image. I will provide patched and signed boot images but first lets see unlock process. After you unlocked boot loader you can flash signed and patched boot.img and after that install Magick and Google App.

Phone need first to be unlocked with unlock Process and provided Github tools. If your Phone is already unlocked start with Part 2 below. If not first unlock your Phone. and then follow Part 2 below.

Unlock Process is free to read and follow in GitHub repository

GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: User can execute unsigned binaries with BootROM privileges, which can be used to unlock bootloader

User can execute unsigned binaries with BootROM privileges, which can be used to unlock bootloader - GitHub - TomKing062/CVE-2022-38694_unlock_bootloader: User can execute unsigned binaries with Bo...

github.com

Many Thanks to TomKing062

Here is my comment to unlock process only with Windows PC but i have done unlock process with Linux
1. Part 1 Unlock Process

From Windows:
1. Phone unlock
A5 procc

Download Tolls:
DriverStoreExplorer

Zadig

Download Releases:

hisense_a5procc_fdl1.zip

hisense_a5pro_spl.zip

After Driver&Zadig installation,
you need to put phone to download mode:

adb reboot autodloader

After that start extract archive spl and fdl and start with provided readme file and commands copy paste.
I will be start with fdl if have problems will try with spl.
Problem is baud loop, after command 2 or 3. just reboot Phone with Power+Volume up. If baud loop is direct after command 1 change adress 0x with adress from command 2. If this not work for you try with spl and read github issues. After Phone started again with unlocked boot loader:

If you have signed magisck patched image rooting process is done and you need to jump to Part2 install patched image and Google play if not read to end.

After Phone started again with unlocked boot loader enable Developer options and usb debug and sent it again to download mode with:

adb reboot autodloader:

save unlocked boot image with:
spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec read_part boot 0 35M boot.img reset.

After that you will have boot.img and phone start again.
if Phone not reset and start normaly then again
with command 3 write to splloader and reset:

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

After phone startet:
If need enable developer, usb debug. Install Magick with:

adb install Magisk-v26.1.apk.

Copy boot.img to phone with:

adb push boot.img /sdcard/Download

Start Magisck from phone and patch boot.img.

How?
Press install buton
dont check option patch vbmeta.
Choose select and patch file and go patch boot.img.
Magick will patch boot.img and save it with magisck_patched_blabla.img.

copy magisck patched image to PC with:

adb pull /sdcar/downlaod/magisck.patched_blabla.img

And now this image need to be signed etc. and flashed to phone.

see:

Magisk

User can execute unsigned binaries with BootROM privileges, which can be used to unlock bootloader - TomKing062/CVE-2022-38694_unlock_bootloader

github.com

Start from android 10 +

2.

Part2 - Phone boot image flash and Google Apps install
I provide A5 ProCC magisck patched signed boot image (user Limio unsigned boot)
I provide A7 magisck patched signed boot image
I provide A7CC magisck patched signed boot image
They are tested to work. If you unlocked your phone no need to save boot image and patch it&sign it. My boot images are already patched&signed. You need to flash image install Magisck and Google Play.
Process is for A7, A7CC, A5Procc only.

Download from:

Filebin | rm6kls9c9jou4eow

Convenient file sharing. Think of it as Pastebin for files. Registration is not required. Large files are supported.

filebin.net

After Phone is unlocked and started normal again put it in fastboot mode with adb:

adb reboot fastboot

Flash image to Phone with:

fastboot flash boot image-new.img - (change image-new.img name with
provided image name)

restart again with:

fastboot reboot

Install Magisck to Phone from https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwj14c2Sv5CAAxXylP0HHUODAEUQFnoECA0QAQ&url=https://github.com/topjohnwu/Magisk/releases/download/v26.1/Magisk-v26.1.apk&usg=AOvVaw1JulPdgCcSLR67i-FQGkPn&opi=89978449

with:

adb install Magisk-v26.1.apk.

Start Magick from Phone if it need Update.

Look for

[MAGISK]LiteGapps_arm64_10.0_v2.9_official.zip

Download it from:

https://sourceforge.net/projects/litegapps/files/litegapps/arm64/29/lite/v2.9/%5BMAGISK%5DLiteGapps_arm64_10.0_v2.9_official.zip/download

Download to Phone and install as modul with Magisck and reboot.
After that you see Google Play. Open it wait to update and install what you need.

If you have already unlocked your Phone but no luck with Google install - then reflash with provided boot images and install Magisck&Google play again.

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,

 

[r1c47]

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,

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.

 

[lilila]

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

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

 

[chatgptfun]

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

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

 

[chatgptfun]

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.

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

 

[r1c47]

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

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.

 

[chatgptfun]

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?

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.

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.

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.

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.

 

[cklm]

here is my tutorial for unlocking the bootloader on the Hisense A5 Pro CC: (don't kill me if you brick your device)

(1) PREPARATION:

go to:

Release v1.0 · TomKing062/CVE-2022-38694_unlock_bootloader

v1.0

github.com

download
hisense_a5procc_fdl1.zip

and

hisense_a5procc_spl_this_may_fail.zip

now you extract both in seperate folders.

also (if you didn't already do so, please download adb tools.: https://dl.google.com/android/repository/platform-tools-latest-windows.zip )

Put the platform-tools also in a seperate folder.

we've got three different folders now.

There is also one program you need to download (zadig): https://zadig.akeo.ie/

Now it would be time to connect the phone to your computer.

(2) EXECUTION:

READ THIS!!!!! ALL YOUR DATA WILL BE WIPED, EVERYTHING WILL BE GONE SO PLEASE SAVE YOUR DATA BEFORE DOING THIS (not like me, lol)
Ok so first off on your computer you do Shift+right click on the platform-tools and open the command window. (powershell or cmd or whatever it is called on your windows computer)
now you type in:

adb reboot autodloader

(in powershell all commands have to begin with .\ so it would be .\adb reboot autodloader I guess)

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)

now you do Shift+right click on the hisense_a5procc_fdl1 folder and open another command prompt (because now you will use other commands).

(note: a command is finished when you can write in the command prompt again. don't close command prompts before a command is finished)

(2.2) BACKUP

So from this point on I highlyyyyyyyyyyyyyyyyy advice to do a backup of your boot.img first. Just in case your Phone for whatever reason is different from mine, you will be able to bring it back to life (especially later on, when you want to root your phone):

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

now wait a little bit. In hisense_a5procc_fdl1 the backup boot.img will be stored.

(2.3) UNLOCK THE BOOTLOADER

Now it's time to actually unlock the bootloader:

In the command promp of hisense_a5procc_fdl1, type in the following 6 commands after one another: I would suggest to do it one by one! AND DON'T USE THE COMMANDS OF THE README FILE IN THE FOLDERS OR YOUR PHONE WILL BE STUCK. (in case of error messages, no worries. to resolve error messages scroll down to 2.4 RESOLVE ISSUES)

1.

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

2.

chsize teecfg.bin

3.

chsize tos.bin

4.

chsize sml.bin

5.

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

6.

spd_dump exec_addr 0x3ee8 fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec write_part uboot uboot.bin write_part splloader spl.bin reset


(2.4) RESOLVE ISSUES

if everything worked out, congratulations, your phone rebooted automatically after the last command and your bootloader is unlocked now. For me, things didn't go so smooth however.

Here is how to resolve the issues I encountered:

(2.4.A) repeatedly CHECK_BAUD_FAIL, CHECK_BAUD_FAIL, CHECK_BAUD_FAIL
(individual CHECK_BAUD_FAIL errors are no problem, but sometimes the command window will get stuck and doesn't do the command it is supposed to execute)

Just reconnect your device and connect it again (and again and eventuelly again) until the last command you wanted to execute works. Sometimes I had to do like 10 reconnects before the command actually works so just chill and be patient.

(2.4.B) The last command (nr 6) gives you a fdlload error and the phone is stuck and doesn't reboot.

In this case you do Shift+Right click on the hisense_a5procc_spl_this_may_fail folder and open another command prompt. Within this command prompt you try only the last command once again (command nr 6, not the other one's, only the last one which didn't work before)




- There you go

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?

 

[chatgptfun]

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

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.

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!!!

 

[r1c47]

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?

Does the phone show up when you run "fastboot devices" after holding the power and vol key/s for 12 or so seconds?

 

[cklm]

Does the phone show up when you run "fastboot devices" after holding the power and vol key/s for 12 or so seconds?

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

 

[r1c47]

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

Have you already installed the SPD drivers?

 

[mello73]

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...

Hi @luzki , your current firmare is the ML Multi Language custom one:

Spoiler: Firmware choice

View attachment 6005923

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.

 

[luzki]

Hi @luzki , your current firmare is the ML Multi Language custom one:

Spoiler: Firmware choice

View attachment 6005923

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.

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?