[GUIDE] How to Unbrick Nokia 8.3 affected by May 2023 Security Patch

Search This thread

hikari_calyx

Senior Member
Hi all, this package will be updated to prevent these issues:

- Fix the issue where "fastboot: error: Could not check if partition XXX has slot all" would appear when something wrong happened.
- Fix the issue where 0_OpenMeToInstall won't run as expect when run as Administrator privileges.
- Now simply double click 0_OpenMeToInstall inside of archiver will not proceed at all.

However, if you encounter "This is not Nokia 8.3" error and you're absolutely sure you're processing a Nokia 8.3, please double check if you have installed driver and RegistryFix.reg. You SHOULDN'T IGNORE, REVERSE, SKIP any of the step.
 
  • Like
Reactions: iSvein

Jayzteroid

Member
Jun 6, 2023
9
0
First of all - thanks for this thread and helping with the phone problem.

I did the step by step procedure, it went throug, but I ended up in boot loop.
The phone is also no longer recognized by Windows 10, tested with two different machines.
I can enter Fastboot mode on phone, but Command prompt says < waiting for any device >

I've tried registry fix, removed and reinstalled drivers...
Any ideas what to try next?

I can't make Windows 10 to recognize the 8.3 anymore.
When 8.3 in fastboot mode, Windows Device manager says Android Bootloader&ADB Interface :"The USB device returned an invalid serial number string descriptor."
Next I'll look into option to fix from SD card.
 

hikari_calyx

Senior Member
I can't make Windows 10 to recognize the 8.3 anymore.
When 8.3 in fastboot mode, Windows Device manager says Android Bootloader&ADB Interface :"The USB device returned an invalid serial number string descriptor."
Next I'll look into option to fix from SD card.

Open Administrator privilege command prompt, powershell of terminal, execute this command:
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d00d" /t REG_DWORD /d 1 /f

After that, use volume key to select "reboot to bootloader" on your phone and try again.
 

MaxWho17

New member
Jun 7, 2023
2
0
Hi,
After using first version of the script, a few days ago,, my phone has reboot at and of script and now i'm stuck in bootloop with recovery mode don't work anymore.
I try with menu or fastboot utility, same result :
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I thing the recovery partition is killed.
I can enter EDL mode with volume up + power but then the phone is recognize as 900E on pc (not 9008), and QFIL don't work (Sahara failed)

Is there only EDL mode to save me ? Should I have a deep flash cable to use QFIL ?

Thanks
 

hikari_calyx

Senior Member
Hi,
After using first version of the script, a few days ago,, my phone has reboot at and of script and now i'm stuck in bootloop with recovery mode don't work anymore.
I try with menu or fastboot utility, same result :
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I thing the recovery partition is killed.
I can enter EDL mode with volume up + power but then the phone is recognize as 900E on pc (not 9008), and QFIL don't work (Sahara failed)

Is there only EDL mode to save me ? Should I have a deep flash cable to use QFIL ?

Thanks
If that happens, I'm afraid only EDL mode will help.
I don't know if hydra edl cable will work, but disassemble and using EDL test point on the motherboard will definitely work.

Write both ABL partitions with EDL, then use latest unbrick fix package.
 

Jayzteroid

Member
Jun 6, 2023
9
0
Open Administrator privilege command prompt, powershell of terminal, execute this command:
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d00d" /t REG_DWORD /d 1 /f

After that, use volume key to select "reboot to bootloader" on your phone and try again.
Thanks and sorry to keep bothering with this.

This reg key makes Windows to recognize the device in Bootloader menu. (LeMobile Android Device - Android Bootloader Interface).
When I use fastboot reboot-fastboot in Command promt, the device boots to fastboot mode and after that is not recognized any more and in Device Manager it changes to Andoid Phone - Android Bootloader&ADB Interface with exclamation mark and status says about ...invalid serial number string...
 

hikari_calyx

Senior Member
Thanks and sorry to keep bothering with this.

This reg key makes Windows to recognize the device in Bootloader menu. (LeMobile Android Device - Android Bootloader Interface).
When I use fastboot reboot-fastboot in Command promt, the device boots to fastboot mode and after that is not recognized any more and in Device Manager it changes to Andoid Phone - Android Bootloader&ADB Interface with exclamation mark and status says about ...invalid serial number string...
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d14ee0" /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d001" /t REG_DWORD /d 1 /f

Note, it's 18d14ee0 instead of 18d1d00d.
 

MaxWho17

New member
Jun 7, 2023
2
0
If that happens, I'm afraid only EDL mode will help.
I don't know if hydra edl cable will work, but disassemble and using EDL test point on the motherboard will definitely work.

Write both ABL partitions with EDL, then use latest unbrick fix package.
Thank you, i will try this.
I have to flash abl_proto.elf into both abl_a and abl_b, right ?
 

Jayzteroid

Member
Jun 6, 2023
9
0
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d14ee0" /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d001" /t REG_DWORD /d 1 /f

Note, it's 18d14ee0 instead of 18d1d00d.
Thanks. Everything else is working now, no exclamation marks in Windows, but device is still in boot loop and I can't do sideload.
adb: sideload connection failed: no devices/emulators found
 
Jun 4, 2023
6
0
So, I figured out I had to manually select the adb bootloader under device manager to get it to read in that mode. I feel like I'm missing something though as I don't see RegistryFix.reg anywhere. I do want to point out that prior to this update I never enabled developer options and I don't know if that would have an effect.
 

hikari_calyx

Senior Member
So, I figured out I had to manually select the adb bootloader under device manager to get it to read in that mode. I feel like I'm missing something though as I don't see RegistryFix.reg anywhere. I do want to point out that prior to this update I never enabled developer options and I don't know if that would have an effect.
You didn't open DPInst32.exe or DPInst64.exe inside of FastbootDriver directory.
 

hikari_calyx

Senior Member
I didn't get that from any of the download links. I also don't know where the fastboot driver directory is. But it could be I don't have it installed. I've been using this guide mostly but for trouble shooting I look up other guides.

The first package has it included. Make sure the filename contains UnbrickV4.
If not then redownload it.
 
Jun 4, 2023
6
0
Install 7-Zip, right click on the file and choose 7-Zip SHA -> SHA256, then compare it.
I really appreciate your help so far. I'm really sorry and feel bad that I need so much help. Unfortunately, I guess I'm getting stuck on 4 because I dont have a SHA zip file downloaded from all the packages or is it just right click on the update?
 

Jayzteroid

Member
Jun 6, 2023
9
0
Thanks. Everything else is working now, no exclamation marks in Windows, but device is still in boot loop and I can't do sideload.
adb: sideload connection failed: no devices/emulators found
I downloadede V4 package, installed the drivers and reg fix, reloaded OTA package, but the adb sideload part (6.) refuses to work. I've tried two different computes, laptop and desktop, and in desktop both front and back USB connections.
When I select Apply update from ADB, Device manager indicates that LeMobile Android Device - Android ADB Recovery Interface starts normally and without error (event log).
I can't figure out why does the adb connection fail.

Is it normal when entering Apply update from ADB the phone tries to update via SD card first and gives:
ro.boot.bootdevice is: id8400.ufshc
Update via sdcard on UFS dev.Mounting card
Failed to mount sdcard: No such file or directory
E:
Failed to mount sdcard

Do I need to unmount SD card which is not present on the phone?

I tried with thrid Windows machine, this time with W11 and with fresh install with no previous istallations related to this issue.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I am in the same situation you were in before, stuck in fastboot and cannot get into recovery mode anymore. How did you manage to unlock the bootloader? When I run
    Code:
    fastboot flash BGT-abl.elf
    I get the following error: "Writing 'abl_b' FAILED (remote: 'Flashing is not allowed in Lock State')"

    Any tips on how to proceed is appreciated.
    Sadly, I had to follow the links scattered around in this thread and on this forum to learn how to get into EDL mode, and then flash some stuff (the a l proto files into two separate partitions) that way. After that I could follow the guide to unlock bootloader etc. Sorry if this doesn't help much, I have already forgotten much of it. Read through this whole thread a few times though, I found many clues in here.
  • 3
    As I mentioned before, unlocking the bootloader will fix this issue.
    But if you don't want to unlock the bootloader, then this guide is for you.

    DO NOT USE THIS METHOD IF JUNE 2023 OR NEWER UPDATE RELEASES IN FUTURE!
    YOU SHOULD NOT IGNORE, REVERSE, SKIP ANY OF THE STEPS!


    We assume you know how to use ADB/Fastboot commands.
    Before you proceed, make sure you have your phone's battery charged as much as possible, or the bootloader will not allow you write any partitions.

    1. Download this package and extract:
    Non-Chinese users: https://www.androidfilehost.com/?fid=10620683726822058340
    Chinese users can download from here:
    Code:
    SHA256: 72425ebdf249f523c81646786eb92d57229e9164ad25be2ef2d920eb7176fcd3

    You should keep at least 10,030MB (10GB approx) empty space.

    2. Open FastbootDriver folder and open DPInst64.exe (or DPInst32.exe if you're using 32-bit Windows) to install correct Fastboot driver. Once Fastboot driver installed, open RegistryFix.reg to prevent fastboot mode become unstable.

    3. Sideload Android 10 Full OTA Package Under Recovery mode. Enter Recovery Mode by using either of these 2 methods.
    - Execute these 2 commands:
    Code:
    fastboot reboot-fastboot
    fastboot reboot-recovery
    Then this phone will boot right into Recovery menu.

    - At Fastboot screen, use Volume key to select Recovery mode, then power key to confirm.
    When you see Android robot lying, press Volume Up key while holding power key to get Recovery menu.
    We recommend users to use method 1 as many people don't know how to press such combination key.

    4. Download this Android 10 Full OTA package:
    or from here: Chinese users who don't have access to Google server can download from here:
    Code:
    SHA256: ba940f216f8d69de988005a6c61ba03073a5b0aacb0789005db5f2f2befe1a02

    Please re-download this package if SHA256 is incorrect.

    5. Use volume key to select "Apply update from ADB", then power key to confirm.

    6. Execute this command to sideload Android 10 Full OTA to your phone:
    Code:
    adb sideload /path/to/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
    You may see downgrade not allowed message on screen, but it will be installed anyway. Wait for the procedure completes.
    If the procedure halted at 94% and it says "adb: failed to read command: No error", it's expected.

    7. Use volume key to select "Reboot to bootloader", power key to confirm.



    8A. To Windows users, double click "0_OpenMeToInstall.cmd", and wait for the procedure completes. We only guarantee it will work on Windows 10 and 11.

    DO NOT RUN IT WITH ADMINISTRATOR PRIVILEGES!
    -

    8B. To non-Windows users or you prefer to flash the package manually, execute these commands. It's absolutely discouraged to use outdated Fastboot binary (e.g. Minimal ADB and Fastboot).
    Code:
    cd /path/to/where/you/extracted/package/
    fastboot flash abl_a abl_proto.elf
    fastboot flash abl_b abl_proto.elf
    fastboot reboot-bootloader
    fastboot flash aop_a aop.img
    fastboot flash aop_b aop.img
    fastboot flash bluetooth_a bluetooth.img
    fastboot flash bluetooth_b bluetooth.img
    fastboot flash boot_a boot.img
    fastboot flash boot_b boot.img
    fastboot flash core_nhlos_a core_nhlos.img
    fastboot flash core_nhlos_b core_nhlos.img
    fastboot flash devcfg_a devcfg.img
    fastboot flash devcfg_b devcfg.img
    fastboot flash dsp_a dsp.img
    fastboot flash dsp_b dsp.img
    fastboot flash dtbo_a dtbo.img
    fastboot flash dtbo_b dtbo.img
    fastboot flash featenabler_a featenabler.img
    fastboot flash featenabler_b featenabler.img
    fastboot flash hyp_a hyp.img
    fastboot flash hyp_b hyp.img
    fastboot flash imagefv_a imagefv.img
    fastboot flash imagefv_b imagefv.img
    fastboot flash keymaster_a keymaster.img
    fastboot flash keymaster_b keymaster.img
    fastboot flash mdtp_a mdtp.img
    fastboot flash mdtp_b mdtp.img
    fastboot flash mdtpsecapp_a mdtpsecapp.img
    fastboot flash mdtpsecapp_b mdtpsecapp.img
    fastboot flash modem_a modem.img
    fastboot flash modem_b modem.img
    fastboot flash qupfw_a qupfw.img
    fastboot flash qupfw_b qupfw.img
    fastboot flash recovery_a recovery.img
    fastboot flash recovery_b recovery.img
    fastboot flash tz_a tz.img
    fastboot flash tz_b tz.img
    fastboot flash uefisecapp_a uefisecapp.img
    fastboot flash uefisecapp_b uefisecapp.img
    fastboot flash vbmeta_a vbmeta.img
    fastboot flash vbmeta_b vbmeta.img
    fastboot flash vbmeta_system_a vbmeta_system.img
    fastboot flash vbmeta_system_b vbmeta_system.img
    fastboot flash xbl_a xbl.img
    fastboot flash xbl_b xbl.img
    fastboot flash xbl_config_a xbl_config.img
    fastboot flash xbl_config_b xbl_config.img
    fastboot flash super super.img
    fastboot flash abl_a abl.img
    fastboot flash abl_b abl.img
    fastboot reboot

    8. Enjoy your fully revived Nokia 8.3 - and all your data should be safe.

    Individual SHA256 hashes of partition image files inside:
    Code:
    (Under PowerShell: Get-FileHash *.img)
    (Under non-Windows: sha256sum *.img)
    Algorithm       Hash                                                                   Path
    ---------       ----                                                                   ----
    SHA256          140D09DD173058C4C79F1C2D34F8B46DE7BB82E7FBE19FD05A948EB52872480B       abl.img
    SHA256          B7D035134F97B9489695E3DA61ADEAFE070DD6FCEFA468904A37D70625F072CA       aop.img
    SHA256          2396EA3DF4DEEB12CE0D2B7AF330FF30BE33378D6AE5735A67B3956E716F0B8C       bluetooth.img
    SHA256          4791877752DF73DDCA782AF9F26606FE10E1F28F1CF1AD075028F5D89FD190C3       boot.img
    SHA256          5EB11607A4419B2925EFB01EEA0DAA274D557BFAC5BDDD61569B7B41125503D4       core_nhlos.img
    SHA256          96470A8026D0A41A681D5FFF12D4176E4EA71DE7231C7A74CDFE1B9B5C2F99BF       devcfg.img
    SHA256          05A2A67646656DBC338FC5998D50A104A8698716522EBC119F6FC16E0396C3EA       dsp.img
    SHA256          BA725112139B4E5DE81B93801BCA7AD7D40753037B12EA828D9B1216970A1FFB       dtbo.img
    SHA256          002E04E2048AF1DA5A225E0BE0B8B1982316DD7CE432B621562933C88D1C1850       featenabler.img
    SHA256          6163C0E57B63960E64ACD4B77FE533DEFC4CC7748EAA400BE019EBC4058016FF       hyp.img
    SHA256          D3C7252B6B0134DCCEED17A08CA43D8DD759EDD4D78F1CBD52F8AE802B1A55D6       imagefv.img
    SHA256          C76A37B08B9DFD5596EC49FEFEC3A1329AB0F89AF1CB62E96C38EF271EE220BA       keymaster.img
    SHA256          83EE47245398ADEE79BD9C0A8BC57B821E92ABA10F5F9ADE8A5D1FAE4D8C4302       mdtp.img
    SHA256          BB9F8DF61474D25E71FA00722318CD387396CA1736605E1248821CC0DE3D3AF8       mdtpsecapp.img
    SHA256          87376F8E1B7B7BEF97DB54B0C0D14D70D479AB10C6FB03AE0014BA44889C02EF       modem.img
    SHA256          BB49FAE2D929947FC1D79C72660C452FABF530ED160ED0EB050C6245940C46F0       qupfw.img
    SHA256          C3E84263C579F65F9B0A5E7DADB158F1BD886B7E45230ABED2685E1B24AA883E       recovery.img
    SHA256          6847A192D8F9B305265D0FF9C0A3CA46075CA581CF362FFA8AFFFAD4AB14EADB       super.img
    SHA256          4173001FB44F687005A1E0A1C719FF9DEB1492FE5D014203392A2D42F8D4C3AB       tz.img
    SHA256          36B6761983FC0E9CBC3A86C404BB924EC83DFCF8788DC0FA4E6454CFA9FC9BB1       uefisecapp.img
    SHA256          902C2CC63EA88DB470137D52779EFD88DFBB0F576B83BF6AC2C0B8AA05A3BA4B       vbmeta.img
    SHA256          6400FA9176E7D1A156AFA5B8726E471E51247B23E130A8164B163E7D2BEF8F7F       vbmeta_system.img
    SHA256          093479DAA6C67B06AB0A20A53A39CDEAB23A6974BEEB2D4CB9E40B37BC415386       xbl.img
    SHA256          0E374E7DACA01705B136FE4C2B0122E0BDA119EF77291A0A791C80A6EE6977A7       xbl_config.img


    Older April 2023 package can be downloaded for archiving purposes. Do not download if you don't know what you're doing.
    1
    FAQ and Troubleshooting

    Q1. ADB prompts cannot read '/path/to/zipfile.zip' when sideloading!
    A1. You're probably using outdated ADB binary (e.g. Minimal ADB and Fastboot). Always use latest Platform Tools from here: https://developer.android.com/studio/releases/platform-tools

    Your outdated ADB binary might be installed at following directories. We strongly recommend you delete it before you proceed.
    Code:
    C:\adb
    C:\Windows
    C:\Windows\system32
    
    Delete these files:
    adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe

    Q2. Can I safely update to newer security updates?
    A2. Yes you can. In case it bricked the phone again, rollback with this method.

    Q3. The phone gets into bootloop while reinstalling firmware!
    A3. To re-enter Fastboot mode, hold volume down key and power key while connected to PC. When the phone displays android one again, release power key immediately but don't release volume down key. Your phone should boot right into fastboot mode without vibration. You may need to try it multiples of times.

    Then, re-open 0_OpenMeToInstall.cmd .

    Q4: Why we don't recommend you to use "fastboot continue" method to "fix" the phone?
    A4: 00WW_3_49E build has following known issues:
    * You cannot install APK directly on device. PackageInstaller will crash immediately when you attempt to install APK.
    * You cannot install newer OS update.

    Those who're staying at 00WW_3_49E can reboot the phone into bootloader mode and follow this method to reinstall 00WW_3_49F update.

    Q5: Can I do this under Windows 7?
    A5: We can only guarantee it will run under Windows 10 or 11. Take your own risk if you're using Windows 7.

    Q6: How to acknowledge if SHA256 is correct?
    A6: For Windows users, you can install 7-Zip or it's fork (e.g. NanaZip), and you can find SHA256 checksum feature by right click on the file.
    For macOS or Linux users, execute this command:
    Code:
    sha256sum /path/to/package/you/d/like/to/checksum.zip

    Q7: What if the PC is infected by Synaptics virus - where executables become into "._cache.fastboot.exe"?
    A7: Please look for an antivirus app you trust, do a full scan then restart. It's most likely caused by using USB Redirector Customer Module before from unknown sources.

    Q8: I got "This is not Nokia 8.3" error, but I'm pretty sure it's Nokia 8.3!
    A8: I'm afraid that you have ignored some procedure. You must install have driver installed properly before you proceed.

    Q9: The PC does not detect the device. I got "The USB device returned an invalid serial number string descriptor." in Device Manager.
    A9: Open Administrator privilege command prompt, powershell of terminal, execute these commands:
    Code:
    reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d00d" /t REG_DWORD /d 1 /f
    reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d14ee0" /t REG_DWORD /d 1 /f
    reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d001" /t REG_DWORD /d 1 /f

    After that, use volume key to select "reboot to bootloader" on your phone and try again.

    Q10: The phone is listed under Universal Serial Bus Controller as "Unknown Device (Device Descriptor Request Failed)" in Device Manager.
    A10: This is caused by following reasons and none of them are related to USB driver:
    * USB port on your PC or phone is too loose.
    * You're using USB cable with low quality.
    * If full-size desktop PC, you're not using the USB port on the rear side. Using rear side USB port is always preferred.

    Q11: Something wrong happened when using early version of UnbrickFix package, now I cannot enter Recovery mode and cannot flash anything under Fastboot mode. How can I revive my phone?
    A11: You'll have to utilize EDL method at this point. Install prototype ABL by following the topic below. Once prototype ABL images are installed, reboot the phone back to fastboot mode and reopen latest version of UnbrickFix package. Note you don't need to unlock the bootloader, just install prototype ABL.
    Alternately, you can request someone who has access of using HDK to reinstall given firmware for you. We don't have or promote such access, please search online.
    1
    I tried that, but still:
    loading: 'C:\Korjaus\sideloader.zip'
    * cannot read 'C:\Korjaus\sideloader.zip' *

    Any other possible tricks?
    Alternately, if you have external SD card, try to put the package into SD card, then use "apply update from SD card" to install it.
    BTW, are you using adb.exe inside of unbrick fix package, or you downloaded it separately (e.g. Minimal ADB and Fastboot)?

    If you're using Minimal ADB and Fastboot, please don't use it. Use this instead:
    1
    Hey, i found out other method to fix your bricked 8.3.
    I typed just "fastboot continue"
    My phone booted itself staying while on Android whitesceen, after like minute or so it continued to "Nokia" logo and started itself perfectly fine!

    Dont ask me how i did it or did i do something else by mistake, i dont know anything about these things.
    But my phone works finally!
    1
    To readers here:
    I'll reupload a newer package based on recently pushed 00WW_3_49F update (00WW_3_490_SP06).
    Once uploaded please let me know if it works well.