EDL Authorization working solution - Xiaomi Mi 9 SE Guides, News, & Discussion

First, I want to say that I have nothing to do with the program or the developer and this is not an advertisement.
I share the experience after a week of searching for the MI 9SE issue, but in the supported devices lists there are a lot of Xiaomi devices.
The phone is Chinese, as most with such a problem. To flash a phone with a locked bootloader requires EDL authorization, and as you know Xiaomi does not allow.
There are a lot of people and services that claim to have EDL account and will help you for some fee but most of them are scam.
Local Authorized Repairers do not have the authorization to flash these phones because they are from China.
A colleague at forum martview-forum.com recommended me a Chimera tool and after a test I can confirm that the program is really working and no authorization is required.
According to the LOG file or at least I think that they are using modified Qualcomm efl loaders.
Procedure:
1. You don't have to buy credits, what I bought is a 3 day test account for € 11.90.
2. Download the Chimera program from their site and install it.
https://chimeratool.com/en/download
3. To flash the device you need to disassemble it and enter EDL mode. The location of the test points on each type of phone will vary depending on the type of PCB. On Qualcomm phones generally provided test points to force the device into emergency download mode (9008).
4. The driver installing with Chimera tool is not working for me and I had to update it.
You can let Windows look for and install it for you, or install it yourself. In Device management, you should see Qualcomm's HS-USB Diagnostics 9008 as an open device.
Drivers: https://we.tl/t-WDrCGh8uda
5. Important: You cannot install Global ROM you need to install the Chinese version and then go through the process of unlocking the Bootloader and installing TWRP and Global ROM or another.
The procedure is easy and you just need to choose the fastboot rom and flash it.
https://www.imageupload.net/image/RCNAr
https://www.imageupload.net/image/RCHub

Mi 9 se global
Hi! Do you know if it works with the global version?

daniel.paredes2049 said:
Hi! Do you know if it works with the global version?
Click to expand...
Click to collapse
It should work.
Check what is your phone real version:
https://www.mi.com/global/verify#/en/tab/imei
Then flash the original ROM for it.
If it is Chinese, flash fastboot Chinese version.
If it is Global, flash fastboot Global version.
My phone was Chinese and with Global ROM I didn't succeed but with Chinese version it was OK and didn't ask for EDL account.
Now I am waiting 168 hours to unlock the bootloader and flash TWRP.

mi 9 se
This is my phone's version:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have another doubt. How can I flash my phone if in chimera there is no support to unlock the bootloader for MI 9 SE? (I saw in in the chimera page supported models)

daniel.paredes2049 said:
This is my phone's version:
I have another doubt. How can I flash my phone if in chimera there is no support to unlock the bootloader for MI 9 SE? (I saw in in the chimera page supported models)
Click to expand...
Click to collapse
The tool can flash the fastboot ROM under EDL model, not unlocking your bootloader!
You need to use Xiaomi official bootloader unlock procedure after you flash the ROM.

Can you help me ?
i've bought a license for 3 days like you, i can't install the chimera in my PC.
Error "its seems this installer is too old"

Can anyone confirm this is working? Also, where do you find this 3 day test account?

Would it be able to bypass a li cloud lock? My gf has no clue of her account login.

Redmi note 8
Wil ir work on redmi note 8 and where i get 3 day license if so

it does support redmi note 8 sadly it does not support my device and i bought a year subscription for 30 dollars i give up and hate xiaomi so stupid

[COM10]:edl authentication
[COM10]:GetUserInfo
[COM10]:AuthFlash
[COM10]:need edl authentication.
[COM10]:authentication edl.
[COM10]:send command:<?xml version="1.0" ?><data> <sig TargetName="req" verbose="1"/></data>
[COM10]:get response from target
[COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<sig TargetName="blob" value="AXXXXXXXX-hXyNj3Hyjq1SXXXXXXXXXX" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>
[COM10]rigin:AXXXXXXXX-hXyNj3Hyjq1SXXXXXXXXXX"
[COM10]:SignEdl
[COM10]:siged:FDSFSAFSDFSFS68F4SFDAS6F48ES4F46SDAF4SA6F8SA6DF46ASD5V4FAS684F68SEA4F6AS4F68ASF6AS4F6AS4F64S6VSAD464F6SFS4F65AS4F6S46F4FASF6SAF64AS5F46SAF465AS1F5AS61F6ASEF16SD46465651631665146A5S11SAD6V1SA6D5V1SDV6A1S51VASV61ASV1A6S1VSAVASD5VS16
[COM10]:send command:<?xml version="1.0" ?><data> <sig TargetName="sig" size_in_bytes="256" verbose="1"/></data>
[COM10]:get response from target
[COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="true" /></data>

jack3935 said:
[COM10]:edl authentication
[COM10]:GetUserInfo
[COM10]:AuthFlash
[COM10]:need edl authentication.
[COM10]:authentication edl.
[COM10]:send command:<?xml version="1.0" ?><data> <sig TargetName="req" verbose="1"/></data>
[COM10]:get response from target
[COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<sig TargetName="blob" value="AXXXXXXXX-hXyNj3Hyjq1SXXXXXXXXXX" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>
[COM10]rigin:AXXXXXXXX-hXyNj3Hyjq1SXXXXXXXXXX"
[COM10]:SignEdl
[COM10]:siged:FDSFSAFSDFSFS68F4SFDAS6F48ES4F46SDAF4SA6F8SA6DF46ASD5V4FAS684F68SEA4F6AS4F68ASF6AS4F6AS4F64S6VSAD464F6SFS4F65AS4F6S46F4FASF6SAF64AS5F46SAF465AS1F5AS61F6ASEF16SD46465651631665146A5S11SAD6V1SA6D5V1SDV6A1S51VASV61ASV1A6S1VSAVASD5VS16
[COM10]:send command:<?xml version="1.0" ?><data> <sig TargetName="sig" size_in_bytes="256" verbose="1"/></data>
[COM10]:get response from target
[COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="true" /></data>
Click to expand...
Click to collapse
Can u help me bypass with edl auth

Bagong15 said:
Can u help me bypass with edl auth
Click to expand...
Click to collapse
Can u tell me,how to bypass it

But to use Chimera needa a license, isn't?

Related

Mi A3: Diag mode and unknown device in QPST & QXDM

I am trying to enable CA on my Mi A3 device. I have unlocked the bootloader and even rooted the device. However, after enabling diag mode, QPST & QXDM is not getting full device information.
To enable Diag mode, I tried two methods and both are working.
Method 1#:
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Enter below in phone app.
*#*#13491#*#*
Method #2:
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Open "Minimal ADB & Fastboot" Command Prompt with administrative rights.
Type adb devices and press enter.
Type adb shell and press enter.
Type su and press enter.
Type setprop sys.usb.config diag,adb and press enter.
I have installed the latest Qualcomm drivers and device is listed under Ports(COM & LPT) as Qualcomm HS-USB Diagnostics 90DB (COM4).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, when I open QPST it is showing the devices as Unkown even though the port is being detected.
When I try to READ or WRITE any values in QxDM, I am getting an error "Diag Error Received: Invalid Command Error Response".
Anyone else had any success with enabling diagnostic mode on Mi A3?
starweb said:
I am trying to enable CA on my Mi A3 device. I have unlocked the bootloader and even rooted the device. However, after enabling diag mode, QPST & QXDM is not getting full device information.
To enable Diag mode, I tried two methods and both are working.
Method 1#:
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Enter below in phone app.
*#*#13491#*#*
Method #2:
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Open "Minimal ADB & Fastboot" Command Prompt with administrative rights.
Type adb devices and press enter.
Type adb shell and press enter.
Type su and press enter.
Type setprop sys.usb.config diag,adb and press enter.
I have installed the latest Qualcomm drivers and device is listed under Ports(COM & LPT) as Qualcomm HS-USB Diagnostics 90DB (COM4).
View attachment 5162031
However, when I open QPST it is showing the devices as Unkown even though the port is being detected.
View attachment 5162033
When I try to READ or WRITE any values in QxDM, I am getting an error "Diag Error Received: Invalid Command Error Response".
View attachment 5162035
Anyone else had any success with enabling diagnostic mode on Mi A3?
Click to expand...
Click to collapse
Never tried this, so I can't help you. But, it's an interesting matter. If you find any more things, please let us know.
Some success with the latest version of QSTP 2.7.496.1. The phone is now detected as NICOBAR which is the code name for Snapdragon 665.
However, I have only the old version QxDM v3 which won't work on the latest chipset as per below post.
How to enable carrier aggregation (LTE+) on Redmi note 5?
Hi! How to enable carrier aggregation (LTE+) on Redmi note 5 Global? Does it work on Linegae OS? Best!
forum.xda-developers.com
Until a cracked version of QxDM v4 become available, no chance of messing with LTE NV values on these new Snapdragon chipsets.
@starweb, any success dumping the QCN (XML or not) file though?
I just got an A3 and per my usual tinkering I wanted to dump it all before I start messing with it. When enabling the diagnostics I get the same 90DB port you do, and at some point I got the phone to be recognized by QFIL or QPST's Configuration, but neither of them were able to create a dump of that area.
Under QFIL the operation just timed out, QPST's Download back up function complained about not being able to write to disk. I've had no problems with older phones, although diag ports were usually 9091, not 90DB as in the A3.
I didn't try any dump.
Problem is you need QxDM v4 to mess with these new Snapdragon phones. Old version won't work.
May I ask where you got the latest drivers from? I only find drivers from 2016
der_hegel said:
May I ask where you got the latest drivers from? I only find drivers from 2016
Click to expand...
Click to collapse
adding onto this where can I find the QPST tool? I got a device stuck in EDL mode.

Question Help with hard bricked K40 Pro. How to flash recovery in EDL?

Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
froggydood said:
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
Click to expand...
Click to collapse
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
actually don’t know if this still works, but it was a major loophole found.
Kenora_I said:
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
Click to expand...
Click to collapse
I still get the write time out, maybe device was disconnected error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does that work with redmi k40 ???
+1
I am facing the same issue with the bricked device. Mi Flash won't let me install anything using EDL mode without authorization. Anyone can help?
Kenora_I said:
actually don’t know if this still works, but it was a major loophole found.
Click to expand...
Click to collapse
It doesn't work anymore.

Question EDL mode test points?

Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solved without using EDL test points. ​see The Solution below.​
BIG Thanks goes to @NOSS8 for his help.
ramiro2016 said:
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
Click to expand...
Click to collapse
this phone did not need edl or test point.
https://forum.xda-developers.com/t/...-after-flashing-gsi-rom.4448229/post-86995731
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
ramiro2016 said:
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
Click to expand...
Click to collapse
https://xiaomitools.com/sp-flash-tool-en/
there is also this tool (new not tested).
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
https://gearupwindows.com/how-to-disable-driver-signature-enforcement-on-windows-11-10/
check for program update
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
ramiro2016 said:
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
Click to expand...
Click to collapse
This is not the latest version(V52).
https://mega.nz/file/H0MW3BST#PfzzmSwbncT5aV7A1ZhWztQonLj4CgJLDHbXoRtCu54
Maybe useful
https://www.bypassfrpfiles.com/2021...h_Secure_Boot_Disable_Tool_V52_Latest_Version
BTW: I don't have and would never have a xiaomi Mediatek and therefore never use these tools for Mediatek, that's why I can help you for the links but not for the use of these tools.
If it still doesn't work post the latest log.
Unfortunately, even the latest version v52 doesn't work, but this tool helped me solve the problem.
https://github.com/bkerler/mtkclient (You need to follow the readme document).
I've used the mtk_gui, and after it got connected, I sent my original firmware boot.img that is currently installed on my mobile after renaming it to boot.bin to the device partitions boot_a and boot_b
Rebooting the device got me the original recovery mode and the fastboot mode.
Then I used the MiFlash tool to flash my phone using flash_all.bat
Every thing is working fine know.
BIIIIIIIIIIIG Thanks goes to @NOSS8 for helping me all the way to the solution .​

ANE-LX3 Bricked Stuck in Bootloader with screen off

If anyone can help me in any way to solve this I would greatly appreciate it.
fastboot oem get-build-number:
ANE-LGRP2-OVS 9.1.0.134
fastboot oem get-product-model:
ANE-LX3
fastboot getvar vendorcountry
vendorcountry: claro/la
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION:
ANE-LX3 8.0.0.152(C25CUSTC25D1)
fastboot mode recognizes it, even though the screen is off, and it still works since I flashed twrp and normal pass, but it only boots to fastboot with the screen off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ozhkavosh said:
If anyone can help me in any way to solve this I would greatly appreciate it.
fastboot oem get-build-number:
ANE-LGRP2-OVS 9.1.0.134
fastboot oem get-product-model:
ANE-LX3
fastboot getvar vendorcountry
vendorcountry: claro/la
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION:
ANE-LX3 8.0.0.152(C25CUSTC25D1)
fastboot mode recognizes it, even though the screen is off, and it still works since I flashed twrp and normal pass, but it only boots to fastboot with the screen off
View attachment 5795813
Click to expand...
Click to collapse
it looks like you installed the wrong (global) firmware. And of course, first of all, it was necessary to install TWRP, right? (I hope min. 3.5.9 version ).
Unfortunately, you have a specific regional variant (single SIM ? ). Try asking here:
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
Another option is a rebrand to C432 region dual SIM:
Guide 1
Guide 2
Also you can try DC-phoenix, test-point method & board software etc.
-Alf- said:
it looks like you installed the wrong (global) firmware. And of course, first of all, it was necessary to install TWRP, right? (I hope min. 3.5.9 version ).
Unfortunately, you have a specific regional variant (single SIM ? ). Try asking here:
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
Another option is a rebrand to C432 region dual SIM:
Guide 1
Guide 2
Also you can try DC-phoenix, test-point method & board software etc.
Click to expand...
Click to collapse
the problem is that it only wants to enter fastboot and the screen is still black, the testpoint also works but I don't have the filthy dongle to be able to use that mode, the device appears like this in device manager
Ozhkavosh said:
View attachment 5795917
Click to expand...
Click to collapse
You violated the partition layout. DC-phoenix is your friend, IMO.
Ozhkavosh said:
I don't have the filthy dongle
Click to expand...
Click to collapse
you don't need a dongle
-Alf- said:
You violated the partition layout. DC-phoenix is your friend, IMO.
you don't need a dongle
Click to expand...
Click to collapse
I revived it with testpoint and board software installing a development build that was the only one in that format and the mobile ended up with a rare model HB something. And then I followed guide 1 that you indicated (thank you) and it's already like LX1, but for some reason it asks me for NCK and I lost the imei 2 (maybe it's because a regional version is installed), I'll try to put a global one and incidentally update to 9.1 as it is now at 8.0
Ozhkavosh said:
I'll try to put a global one
Click to expand...
Click to collapse
C432 is a global. Flash service ROM again and do factory reset in stock Recovery (maybe it's because you was on EMUI 9.1, guide 1 is for E 8.0). Or try "Chapter 2", it works for both EMUI version.
Don't try to upgrade to EMUI 9.1 until you have a full working phone with EMUI 8.0, my advice.

Development Prototype ABL binaries from Nokia X10 and X100, for bootloader unlock purpose.

If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here for Nokia X10 (ScarletWitch)
Click here for Nokia X100 (Deadmau5)
3. Flash prototype ABL manually, then you can confirm bootloader unlock:
Code:
(Nokia X10) fastboot flash abl SCW-abl.elf
(Nokia X100) fastboot flash abl DM5-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
SCW-abl: 3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
QKS-abl: missing
DM5-abl: f16bafb998925b7a3f7651eb21edba8bb4283113f56628d9b0b685882015696b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Nokia X100: 05C8E21116890E3DAF3879ED4939F7F6267A3CA2085E3E943743E938C80C28C1
I'll have a go, thanks!
Alvy123 said:
I'll have a go, thanks!
Click to expand...
Click to collapse
it requires you to gain access of the tool from tri-color company, which is.... actually impossible.
The only way one can use it without any restrictions is if the same one is Nokia's customer support....
hikari_calyx said:
If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Click to expand...
Click to collapse
can I use 3rd-party tools (e.g: Fire Tool) to enable flashing perms, instead of HDK?
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Renate said:
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Click to expand...
Click to collapse
Oh wow, that's interesting. Mind telling me the full details about what you did?
AltFantasy said:
Mind telling me the full details about what you did?
Click to expand...
Click to collapse
Here's a whole thread on abl packing: https://forum.xda-developers.com/t/qualcomm-abl-android-bootloader-packing-signing.4473815/
Then there's the reverse engineering, probably using Ghidra or Ida.
Ghidra annoys me so I use my own custom stuff that simply annotates what objdump puts out.
I feel closer to the metal that way.
After unpacking/patching/packing abl you've got a modified abl that the signing is wrong.
If you're Nokia, you just take your super-secret private key and resign the abl.
If SecureBoot is not enabled on your device it does not need to be signed, but it needs to be hashed.
Hashing is not at all secret, it's just SHA256 or SHA384 on the program segments (one of which you altered).
My qcomview.exe can do that easily, it's in the sig.
I tested it for somebody; the unlock works by utilizing this abl. Thanks for the share
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Alvy123 said:
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Click to expand...
Click to collapse
that option is actually useless.

Categories

Resources