Hello to all ZenFone4 (ZE554KL) owners.
(I am not good at English so I use DeepL translation.)
I would like to backup the data of an app, please lend me your wisdom.
Here is the app that has the problem.
小説を読もう！オフラインリーダー - Apps on Google Play
More convenient, comfortable! "Restaurant novel!" And "Shousetsukaninarou"
play.google.com
This app is an offline reader for a famous Japanese novel submission site.
I have been using this app since 2014 until now.
But recently I had a problem with data backup.
This app is originally equipped with a backup function.
However, if the file size of the database (SQLite3) used internally exceeds 2GB, the backed up data is interrupted there.
Also, until now, it was possible to backup using the Android adb backup function and retrieve the data from backup.ab to get the same data even if the file size exceeded 2GB.
But now this method also stops in the middle of the backup and fails.
This app has not provided any updates since 2018.
Also, I have not been able to contact the developer by sending an email to their email address.
I thought about rooting the device and backing it up, but I have not been able to do so because I have heard (with Android in general) that unlocking the bootloader will initialize all user data.
Is there any good way to do this?
Thank you for reading this far.
Japanese(Original)
ZenFone4(ZE554KL)をお持ちの皆さんこんにちは。
(英語が不得意なのでDeepL翻訳を使用しています。)
あるアプリのデータのバックアップを行いたいのですが知恵を貸してください。
問題があるアプリはこれです。
小説を読もう！オフラインリーダー - Apps on Google Play
More convenient, comfortable! "Restaurant novel!" And "Shousetsukaninarou"
play.google.com
このアプリは日本の有名な小説投稿サイトのオフラインリーダーです。
私は2014年から今までずっとこのアプリを使用し続けてきました。
ですが最近になってデータのバックアップに問題が発生しました。
このアプリは本来バックアップ機能が搭載されています。
しかし、内部で使用されているデータベース(SQLite3)のファイルサイズが2GBを超えるとバックアップしたデータがそこで途切れてしまう問題が発生します。
また、今までは2GBを超えてもAndroidのadb backup機能を使用してバックアップを行いbackup.abからデータを取り出すことで同じデータを得ることもできました。
ですが、現在ではこの方法もバックアップの途中で止まってしまい失敗します。
このアプリは2018年からアップデートが提供されていません。
また、デベロッパーのメールアドレスにメールを送っても連絡が付きません。
端末をrootしてバックアップすることも考えましたが、(Android全般で)ブートローダーをアンロックするとユーザーデータが全て初期化されてしまうという話を聞いたので行えていません。
何か良い方法はないでしょうか？
ここまでお読みいただきありがとうございます。
provide info more about phone. Snapdragon 630 or Snapdragon 660?
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
aIecxs said:
provide info more about phone. Snapdragon 630 or Snapdragon 660?
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
Click to expand...
Click to collapse
Model ASUS_Z01KDA(WW_Z01KD)
SOC Snapdragon 660
RAM 6GB
ROM 64GB
Android Ver 8.0.0
Build ID
OPR6.170623.013.WW_Phone-15.0405.1806.116-0
please read boot.img off device and share file (we will check if we can cheat bootloader)
on PC
install python, install this https://github.com/bkerler/edl
Code:
adb reboot edl
python3 edl --loader=/path/to/prog_emmc_ufs_firehose_Sdm660_ddr.elf r boot boot.img
if you can't enter EDL mode from adb, try this:
- disconnect usb cable
- power off phone entirely
- press and keep holding both volume buttons
- connect usb cable
I live in Japan where it is just before 6 am and I am so sleepy I am going to miss the work, so I will try again later.
Thank you very much.
Japanese(Original)
私が住んでいる日本は、今午前6時直前で私が眠くて作業をミスしそうなので、また後で試させていただきます。
ありがとうございます。
aIecxs said:
please read boot.img off device and share file (we will check if we can cheat bootloader)
on PC
install python, install this https://github.com/bkerler/edl
Code:
adb reboot edl
python3 edl --loader=/path/to/prog_emmc_ufs_firehose_Sdm660_ddr.elf r boot boot.img
if you can't enter EDL mode from adb, try this:
- disconnect usb cable
- power off phone entirely
- press and keep holding both volume buttons
- connect usb cable
Click to expand...
Click to collapse
I tried it, but I can't seem to get into edl mode with the adb reboot edl command or with the USB cable connected while holding down the volume button.
I was able to enter CSC fastboot mode by booting while holding down the Volume plus button. ......
In addition, a mysterious barcode appears on the right side of the screen when I enter fastboot mode using the adb reboot bootloader command.
Japanese(Original)
試してみましたが、adb reboot edlコマンドでもVolumeボタン押しながらUSBケーブル接続でもedlモードに入れないようです。
Volumeプラスボタンを押しながら起動するとCSC fastboot modeには入りましたが……
なお、adb reboot bootloaderコマンドを使用してfastbootモードに入ると画面右側に謎のバーコードが表示されます。
1) maybe translation was wrong.
press two Volume Buttons at same time. Volume Up & Volume Down. then connect usb cable.
2) another method from modified fastboot
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
3) another method with deep flash cable
{
"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"
}
4) another method via test point
aIecxs said:
1) maybe translation was wrong.
press two Volume Buttons at same time. Volume Up & Volume Down. then connect usb cable.
2) another method from modified fastboot
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
3) another method with deep flash cable
4) another method via test point
Click to expand...
Click to collapse
It's ok, I was pressing Volume + and - at the same time.
Unfortunately, it didn't go into EDL mode, though.
I'm sure it's a security delight, but it's a shame that it seems to be really difficult to freely play with one's own devices in recent years.
I really respect aIecxs for his erudition.
Even the modified fastboot command reboot-edl didn't work.
I don't have a deep flash cable, but I have an adapter that can pull each signal line from USB Type-C, so I will try that tomorrow.
I've changed the battery several times, so I have disassembled it, but I don't really want to use the test-point if possible because I might accidentally destroy the device.
Japanese(Original)
大丈夫です。Volume +と-を同時に押していました。
残念ながらEDLモードには入りませんでしたけどね。
セキュリティ的には喜ばしい事なのでしょうが、近年は自分のデバイスを自由弄るのが本当に難しいようで残念ですね。
aIecxsさんは博識で本当に尊敬します。
改造したfastbootコマンドのreboot-edlでもダメでした。
deep flashケーブルは有りませんが、USB Type-Cの各信号線を引き出せるアダプタを持っているので明日それを使って試してみます。
何回かバッテリー交換はしているので分解はしていますが、デバイスを誤って壊してしまいそうなのでtest-pointはできればあまり使いたくないですね。
Unfortunately, the test point picture is for Snapdragon 630. But you can upload picture of PCB board Snapdragon 660.
aIecxs said:
Unfortunately, the test point picture is for Snapdragon 630. But you can upload picture of PCB board Snapdragon 660.
Click to expand...
Click to collapse
This is an image from a previous battery replacement.
The PCB is not visible, but looking at the shape of the plate and the placement of the components, I suspect that the test point is in the same position.
Twitter:
https://twitter.com/i/web/status/1202833859068321793
Japanese(Original)
以前バッテリーを交換した時の画像です。
PCBは見えませんがプレートの形状や部品配置を見るとtest point同じ位置にあるのではないでしょうか？
Twitter:
https://twitter.com/i/web/status/1202833859068321793
aIecxs said:
1) maybe translation was wrong.
press two Volume Buttons at same time. Volume Up & Volume Down. then connect usb cable.
2) another method from modified fastboot
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
3) another method with deep flash cable
4) another method via test point
Click to expand...
Click to collapse
I substituted the EDL cable with an adapter like the one in the image, but it did not enter EDL mode.
(I used a digital multimeter to verify that the wiring was correct.)
I will try again at a later date as it requires preparation and courage to disassemble and short-circuit the test points.
Thank you very much.
Japanese(Original)
画像の様なアダプタを使用してEDL ケーブルを代用しましたがEDLモードには入りませんでした。
(デジタルマルチメーターを使用して結線が正しいか確認しました。)
分解してテストポイントを短絡させるには心の準備や勇気が必要なのでまた後日試してみようと思います。
ありがとうございます。
We have succeeded in avoiding BackupManager crashes by specifying the -nocompress option in adb backup,
and avoiding adb backup timeouts (5 minutes) by connecting a USB-LAN adapter via OTG and using a wired LAN
connection for backups.
Japanese(Original)
adb backup にて -nocompress オプションを指定することによりBackupManagerのクラッシュを回避し、
USB-LANアダプタをOTGにて接続し有線LAN接続でバックアップすることによってadb backupの
タイムアウト(5分)を回避することに成功しました。
Related
If you connect your phone to the pc and see something like this
{
"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"
}
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Thanks for the tip ramm...
Dr. Ramm said:
If you connect your phone to the pc and see something like this
View attachment 3590142View attachment 3590143
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
View attachment 3590159
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Click to expand...
Click to collapse
Thanks man u are truly
Savior of mine MI4
Thanks a lot
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Nice share bro. Thanks
mad-extrem said:
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Click to expand...
Click to collapse
There is no difference between stock or extended partition, in flashing fastboot rom using MiFlash! It will recreate whole partition table!
Just follow steps in OP
Inviato dal mio D6633 utilizzando Tapatalk
mad-extrem said:
Tell me how to flash fastboot rom on extended partition.
Click to expand...
Click to collapse
U mean MM merged partition? IDK, which error show MiFlash?
If error: 0x80004005: FAILED (remote partition table doesn't exist).
then use this tutorial
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
It worked, thanks allot
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
vaski123 said:
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
Click to expand...
Click to collapse
What do you not understand?
You have to flash a fastboot rom, with MiFlash, that will re-build partition table
Inviato dal mio D6633 utilizzando Tapatalk
That will erase internal stoarge (sd card too). I lost everything on stored on it.. ?
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
marlo125 said:
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
Click to expand...
Click to collapse
Check post #7, if you read all (just less than 2 pages) you could find the solution by yourself.
Inviato dal mio D6633 utilizzando Tapatalk
Thank you for you sharing your knowledge I am very grateful I ran into this post and was able to repair my mi3. :good:
thanks sir, you saved ma life,thanks once again
You are my saviour
thanks for tutorial
a.broken.star said:
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
Click to expand...
Click to collapse
hey could you or anyone else help me with this...i bricked my phone and not able to boot into recovery and fastboot mode..its just completly dead...i am downloading miflash and fastboot room for my device[mi3]...plz help
Sir I Have followed your instructions because my problem is having having a Partition does not exist error in mi flash. i was already in the MiFlash step when suddenly the there was an error Access Denied and i keep receiving an error saying USB not recognized. Please help me any workaround Sir my mi3 no longer turns on and it no longer detected to a computer
Device: LG-D325
I tried rooting, unlocking bootloader, and installing custom rom (this link).
I successfully gained root & unlocked bootloader. Than it all went down.
I flashed recovery and booted into it, using "fastboot boot recovery.img" command.
I flashed cm12.1 and after that I got the "purple screen" error.
When phone is off and I try to normally turn it on:
1st screen:
Code:
Secure booting error!
Cause: boot certification verify
2nd screen:
Code:
DemiGod Crash Handler : DBI Err Fatal!
Board Rev.: 1.0
Ram dump mode.
Option : SD card ram dump mode.
Push below files to sd card before test.
rdcookie.txt, rtcookie.txt
Please do following action.
1) Ram dump Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
3) If sdcard ram dump enabled just wait for reboot.
4) Collect ramdump files from your pc or sdcard.
5) Send e-mail to [email protected]
The same happens when I plug in the USB cable when phone shut off.
Also, I cannot enter the fastboot menu (previously I could - before flashing CM12.1 via recovery) using volume UP + power buttons. Therefore, I cannot enter recovery.
Any info on this situation?
You need to short the test point of your phone and force the phone to qhsusb dload mode after that boot repair
it will repair your phone's download mode
And flash the phone
Br
Shahzaib Jahangir
Is there any way to fix this problem bro with out jtak
Thanks.
The test point method is not the JTAG method
razeen said:
Is there any way to fix this problem bro with out jtak
Thanks.
Click to expand...
Click to collapse
Use the test point method. It works very well and it's quite easy. But first I recommend you try "LG Flash Tool 2014" . If that works, no need to open up the phone for test point method. If you are already seeing pink screen demigod error DBI fatal error, no need to go for JTAG I think.
Feel free to ask if you need assistance for testpoint method. I have already published the method for few other people here on XDA. A little search will bring you there
my Lg325 also violet and dump mode cant flash i go to celpon repair but they cant fix my pon pls help me tnx
gilliane.08 said:
my Lg325 also violet and dump mode cant flash i go to celpon repair but they cant fix my pon pls help me tnx
Click to expand...
Click to collapse
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
honeybun.1986 said:
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
Click to expand...
Click to collapse
same problem here
can you help, please?
LG D325f L70
UPDATE
Now i have QDLoader 9008 (i've installed driver manually without signature). I don't know why my computer did not recognise automatically installed drivers
Else i trieb Board diag
I,ve tried QFIL QPST and recieved
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
Before that
BoardDiag 3.99c I have an error
AP CHECK START
FAILED during loading flash programmer
There were already messages about this trouble,but there are no solution, so i am asking for it.
LGE AndroidNet USB
qhsusb_bulk
Previously i had Pink screen and Lg Pc Suite could recognize my phone
I,ve tried Format to Fat32 my inner phone emmc(i did not insert in my phone microSD card) DiskImageRev2.zip and LoaderD325.img. After format to fat32 it was 4gb.When i,ve installed loader.img it became 64mb with 2 folders in it. Device monitor showed the phone as qhsusb_bulk (i already had istalled Qualcomm drivers) After installation of LGMobileDriver_WHQL_Ver_4.0.4.exe ( 12,39 МБ )
It was recognised as LGE AndroidNet USB. (com port 3) After that i tried LgFlash tool (tot and kdz firmware,it showed error on 50%) 2014 and BoardDiag also showed error .
I can not convert it to Qualcomm HS-USB QDLoader 9008 (I saw many articles where people with qhsusb_bulk converted it to Qualcomm 9006 after installation of qualcomm drivers,but it did not works for me. Please help
Any ideas? I heared about SRK tool 2.1 Does it works for my Lg L70 D325? Or maybe QPST, or ADP
honeybun.1986 said:
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
Click to expand...
Click to collapse
Please help me
My lG D325 cant on recovery and download mode. Fatal error. Who can help me
Gayan360 said:
My lG D325 cant on recovery and download mode. Fatal error. Who can help me
Click to expand...
Click to collapse
I think you are referring to the famous "purple screen" mode. Relax, that is not hard to get pass.
Follow the steps below.
But, be warned, I am not responsible for any damage caused by following these methods.
Your phone's battery has to be charged at least 50%.
You'll need a USB "data" cable.The one came with your phone is the best. Some third party cables have only power lines connected in and they will not work. So, make sure you have the "data" cable.
1. First, we have to install the necessary drivers(I am assuming that you're using a Windows PC) .
Here are the drivers. Download, install and give your PC a restart.
2. Download LG flash tool 2014 from here and extract it to your root directory(For example, drive "C " in your PC )
3. Download the firmware file for your specific phone model. In your case, as you have mentioned, it is LG D325. This is a link to a matching firmware for LG L70 D325. This file is big and its around 920MB. After download, extract the zip file to the folder where you copied the LG Flash tool 2014.
4. I hope the above mentioned steps were followed correctly and you're ready now. Remove your battery, press the power button for 5-10 seconds and then re insert the battery. press the volume up button and plug the USB cable(The other end has to be plugged in first to PC. Refer to this video if you are unclear.
5. Now launch "LG Flash tool 2014.3.exe" (right click on it and select "run as administrator" for best results).
6. Once the program is open, and click on 1 and select your kdz file which you got from the step 3. Then click either "Normal Flash(2)" of "CSE Flash".
{
"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"
}
7. Now another window will appear and click "Start" as in this picture.
wait until the program finishes and once done, you'll get the initial setup screen on your phone with a greeting message.
If you're still unclear, please pass a comment. Happy communicating..
A couple days back I bricked my G3 so I tried many things but nothing seemed to work, then I found R-T-B’s guide, and it worked, it can unbrick any G3 Vs985.
I highly suggest you to read the complete guide before proceeding and you must ignore the instructions.txt file included in the Unbrick Kit folder.
I am just writing this, the tools are from @R-T-B
Say thanks to that guy and if you like please donate.
Disclaimer: I’m not responsible for anything, use it on your responsibility
What is Hard Brick?
When your has no power, no sign of life, no indication whether plugged or not, sometimes vibrates when plugged in usually stays at black screen aka dead, LED changes color.
To Put Your Phone in Qualcomm USB mode:
If connected to PC Device Manager recognizes as LGE Android Mobile Usb which isn’t a good sign means you going to have to Short Pin via test point.
Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2. You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture with a small thin, stiff metal wire. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
Shorting means just attaching those two points with a small thin, stiff metal wire for 5secs or so.
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. When your phone has detected as Qualcomm usb then release the shorting points.
{
"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"
}
Now you’re ready for resurrection of your beloved LG G3
Pre-requisites:
All you need is in this Unbrick Kit, it’s a pretty big file, download, be patient.
Download it here:
md5:
c2a9cff174ed0d4a1c218023087d10cc
Qualcomm QDLoader_HS-USB_Driver 32 and 64bit
LG_Verizon_Drivers
LGUnitedMobileDriver
Note: Only install 32bit or 64bit drivers of Qualcomm, don’t install both
Procedure:
Make sure your phone is in Qualcomm 9008 mode note the com port # in Device Manager
If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command prompt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Or you can simply disable driver signing by pressing F8 before Windows logo appear when it’s booting.
Step 4. Reboot and you’re done.
Connect your phone w/o battery and run BoardDiag from folder “v2.99” inc. in Unbrick kit
And be sure the AP check and EMMC are checked, select AP chipset as B2 (MSM8974AC), check Qualcomm’s port # from Device Manager and put it in BoardDiag’s ComPort box, see image below:
Now click start and wait for test to complete, if that does not work, try unchecking the EMMC test. If that still does not work, use the BoardDiag in v3.99c folder and also try it without EMMC test.
If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
Now check RESTORE BOOT IMG and choose “aboot” from drop down menu and again click start
Do the same for following partitions FOLLOW THE ORDER!!
BackupGPT
boot
dbi
laf
PrimaryGPT
recovery
rpm
tz
Now flash “sbl1”. Always flash “sbl1” at the end to prevent super brick.
Phone should now get disconnected.
Remember your phone is connected w/o battery till this point.
Now disconnect from PC and put in the battery
Hold Volume Up button and connect to PC while holding Volume Up button, Congrats you’re in download mode. Now use LG Flash Tool 2014 included in Unbrick Kit.
Run it As Administrator, see image below.
You’ll see this window after clicking CSE Flash, hit enter.
Now it will Stop Responding at 99 percent, happened to me, so I assume it’s just a bug in the program. Don’t worry it’s still going to install the software in your LG G3
Do not remove usb/unplug phone till your phone restarts.
NOTES: If you get an error about a dll missing you need to download and install the following: Download
Now your running 47A Android MM
Hope that this helps, also if you find any problems or need help please post so I can update this post.
Feel free to comment and help me to improve this guide.
The guide is attached as 7z for convenience ...
Thanks..
I seem to have bricked my wife's vs985 trying to flash jasmine ROM. Can get it to qualcomm mode but it keeps failing the eemc test at sbl1. I'll run through the guide a few more times tomorrow but its really being a pain. First the WiFi disappeared and it started acting crazy. Could be its time to go even with the new battery I purchased.
Update:
I managed to flash every file that was mention with the exception of System and User Data. Tried to power on and nothing.
I did that for some odd reason jumping the pins isn't necessary and the device populates automatically when connected to USB. I tried running KDZ but nothing. I can try and run the TOT but, I'm a bit skeptical. As of this moment I have successfully erased the eMMC but when testing it always finds some reason to fail the test.
I'm able to write with APC and Restore Boot IMG selected and as of this moment managed to get the system image re-flashed. I'm in the process of loading the User data which is about 11Gb so it'll take awhile. I still have sbl1 at the end to flash. I will note that when I did jump the pin to ground it would always fail sbl1 or load a partition.txt doesn't exist error. I extracted the TOT as directed but it just kept throwing the same error.
I did also notice when the battery is in and the usb connected it is not recognized by my PC.
very good tutorial
"partition.txt doesn't exist"
Is nowhere to be found. What can I do?
Thanks Almighty God and you alich3451, so much for this guide. My VS985 was bricks. No download, no recovery mode, black screen and the led blinks red and blue continuously when plunged. I toiled for for many researches and guides but all never worked, except this one.
Yes, I really followed the steps critically got the phone back from dead to life.
Through my experience i want to recommend the battery in before the flashing of the TOT file begins . Secondly, do not check the devices manager for the port number but ratter check and watch closely the right conner of the taskbar for the pop up messages with the port number written at the end of the message during the installing of your driver by your windows 7 PC when you plug in the phone with the battery inside. That is the port number you have to take note and use it in Com Port area of BoardDiag v2.99a during the flash of the TOT partitions.
With this added to the main guide above you should get everything working normal.
Thanks alich3451 !!
Do I need to short the pins & stuff if I get into Download Mode already? My Phone is getting shown as LGE AndroidNet USB Serial Port (COM4) is that alright?
Need help please!!!
while i managed to reach up flash tool step where it stack so i had to start all over again but this time i cant even pass the first step.
I successfully sort the pins every time and after i do a successful test with BoardDiag (without emmc) and i get pass message after a few seconds its disconnects and i cant move to the rest steps.
what iam doing wrong ?
Lg Mobile Flash tool
Hello,
after I hit start on the flash tool, it opens up another lg tool that tries to download stuff from the internet. Then my stuff fails
I have G3 D858HK, when i use my current .tot file. It won't boot into download mode. When i use your model file, it successfully boot :3
Is my file corrupt?
there are too many people have bricked their device. so here is the guide on how to debrick your device.
1. download the factory firmware ,uncompresss to your local disk. links : http://pan.baidu.com/s/1bC1tJw ; direct link from my server: https://tenfar.com/usr/uploads/nexus6p_fix_bricked.zip .use baidu disk .if you can. bandwidth limited.
2. download the EDL mode drivers ,and install to your pc. links: https://pan.baidu.com/s/1bpHPXE3
3. download miflash http://api.bbs.miui.com/url/MiFlash and install in your pc
4. run the miflash program and select the firmware ,plug in your phone to usb cable. in pc's device manager it will show the 9008 com port.
5.in miflash will show the com port,click flash,wait for it to finished
{
"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"
}
Edited:
How to enter EDL mode:
1 your device is bricked ,stuck in edl mode.try reset your device before flashing with miflash
2 flash a customize boot from cyanogemod or lineage.
Code:
adb reboot edl
3 unlocked phone with fastboot commands ,try this https://forum.xda-developers.com/ne...l-bootloader-extra-commands-nexus-6p-t3564086
4 unlocked phone using fastboot commands to erase sbl1
Code:
fastboot erase sbl1
not recommended
5 erase your sbl1 with dd commoand not recommended
Code:
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/sbl1 bs=16384
can you upload to androidfilehost links, not able to download from there.
also is that a normal firmware or special one?
Same here, first link is not working. Is it the standarg Google Factory Image or is it something different?
The Bootloader must be unloked?
I see the following under Device Manager when I connect my Nexus 6P to a Windows 10 Desktop via USB C:
Qualcomm HS-USB QDLoader 9008 (COM3)
I have installed the Mi Flash Tool as above along with USB drivers and Qualcomm drivers. I am not able to flash any factory firmware, however. I receive an error stating that the "hello packet" could not be received followed my an object reference error. I have tried many versions of the Mi Flash Tool to no avail.
Any other suggestions are much appreciated.
Thanks.
catalase said:
I see the following under Device Manager when I connect my Nexus 6P to a Windows 10 Desktop via USB C:
Qualcomm HS-USB QDLoader 9008 (COM3)
I have installed the Mi Flash Tool as above along with USB drivers and Qualcomm drivers. I am not able to flash any factory firmware, however. I receive an error stating that the "hello packet" could not be received followed my an object reference error. I have tried many versions of the Mi Flash Tool to no avail.
Any other suggestions are much appreciated.
Thanks.
Click to expand...
Click to collapse
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
@tenfar Can u update to the another host so we can easily download? That's will be great.
@tjchuot287 you can download "nexus6p_fix_bricked" firmware using "Advanced Download Manager" ADM on PlayStore using its built-in browser with "desktop mode" enabled...
Worked for me...
Hope that helps...
@5.1 I mean that i cannot download "USBdriver_8916.zip", but i think i will find it on google and download it instead. Hope it works.
@tjchuot287
I used advanced download manager and both downloaded fine... Since then far already shared the firmware from his server, It's likely he'll provide an alternative link for the driver as well... :good:
@5.1 does it unbricked your phone? Im kind of desperate
Well, I didn't use it... Since my phone is working. :angel:
I guess tenfar wouldn't have posted it if it didn't work. :good:
anyway, how to enter to EDL mode?
tenfar said:
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
Click to expand...
Click to collapse
I press the power key for 30 seconds with the USB C cable attached to the computer and the computer does emit a tone as if the phone has been disconnected and the device manager continues to show the Qualcomm HS-USB QDLoader 9008 (COM3). However, I still receive read packet error.
Do you have any other suggestions on how to get it into the correct EDL mode or the correct firehose state?
UPDATE:
[0.00 COM3]:[COM3]:start flash.
[0.00 COM3]:received hello packet
[0.00 COM3]:can not found programmer file.
Hello packet is recevied. However "can not found programmer file" is returned. Programmer file prog_emmc_firehose.mbn is in the extracted contents nexus6p_fix_bricked.zip, however the Mi Flash Tool does not recognize.
tjchuot287 said:
anyway, how to enter to EDL mode?
Click to expand...
Click to collapse
A few posts above yours...:
tenfar said:
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
Click to expand...
Click to collapse
@5.1 thank you, I really appreciate your helps, but i think my phone is dead now. I didnt unlock bootloader before so now i cant do anything. Poor me
I'm having the same "cannot receive hello packet" error. I tried to old down the power until the device is re detected in device manager, but it still does the same.
catalase said:
I press the power key for 30 seconds with the USB C cable attached to the computer and the computer does emit a tone as if the phone has been disconnected and the device manager continues to show the Qualcomm HS-USB QDLoader 9008 (COM3). However, I still receive read packet error.
Do you have any other suggestions on how to get it into the correct EDL mode or the correct firehose state?
UPDATE:
[0.00 COM3]:[COM3]:start flash.
[0.00 COM3]:received hello packet
[0.00 COM3]:can not found programmer file.
Hello packet is recevied. However "can not found programmer file" is returned. Programmer file prog_emmc_firehose.mbn is in the extracted contents nexus6p_fix_bricked.zip, however the Mi Flash Tool does not recognize.
Click to expand...
Click to collapse
select the file in advance settings in miflash
从我的 iPhone 发送，使用 Tapatalk
tjchuot287 said:
@5.1 thank you, I really appreciate your helps, but i think my phone is dead now. I didnt unlock bootloader before so now i cant do anything. Poor me
Click to expand...
Click to collapse
I'm not sure this procedure require an unlocked bootloader. However @tenfar may certainly shed some light on this matter...
Hoping you get it sorted though...
Still getting "cannot receive hello packet" error. @tenfar a couple of questions:
- If the phone is detected in Device Manager as "Qualcomm HS-USB QDLoader 9008 (COMx)" do I still need to install the drivers from step 2?
- Do I need a particular combination of power, vol +/- in order to put the phone in the right EDL mode?
When I hold the power button for few seconds, the PC it is connected to makes the standard tone when a USB device is plugged/unplugged, but device manager still show the same device and Miflash still gives me the error when I flash.
Thanks for all the help BTW
WARNING!
THIS GUIDE REQUIRES DISASSEMBLY, SO YOU WILL DEFINITELY LOSE THE WARRANTY!
DO IT AT YOUR OWN RISK!
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
UPDATE: I've updated the new tool for unlocking the phone without understanding how to utilize such long commands.
You can watch the demonstration here: https://youtu.be/whrFsn8h7A4
Click to expand...
Click to collapse
So after I got a Nokia 4.2 prototype by opportunity, I just found the theory of bootloader unlocking.
Tricking development options for allowing "OEM unlocking" no longer works on latest security update.
What you need to have:
- a Nokia 4.2 unit that you finished back cover and upper plastic shell removal
- tweezers, and probably a standard philips screwdriver
- QPST (use at least 2.7.474) or any other app that could access the EDL, and Qualcomm USB port drivers are installed
- Latest Google Platform Tools
- Full backup of your userdata
Step 1: Trigger the phone to EDL mode, then change the driver to "Qualcomm HS-USB QDLoader 9008"
Please take a look at the attachment below, about the location you need to use tweezers.
For Windows users:
If the driver is already indicated as "Qualcomm HS-USB QDLoader 9008", get to Step 2.
If the driver is indicated as either "QHSUSB__BULK" (For users who have installed Windows Device Recovery Tool before) or "Qualcomm HS-USB Diagnostics 9008", you must change the driver to "Qualcomm HS-USB QDLoader 9008".
After driver changed, you need to disconnect the phone, disconnect and reconnect the battery ribbon cable, then trigger the phone to EDL again.
I assume the COM port number is 8 (COM8).
Click to expand...
Click to collapse
Step 2: Write config partition
As we already know, config partition is also the frp partition.
You need to create a config partition image that has "OEM Unlocking" function enabled, which need to alter the last byte, then change the overall checksum to make the config file valid.
For your convenience, I've created one.
Now download and extract the attachment below.
Use QFIL included in QPST to load the firehose file. Choose "Flat Build" and choose the "prog_emmc_firehose_8937_ddr.mbn" you extracted from the attachment.
Choose "Tools" - "Partition Manager", then wait for the partition list appear.
As "Load Image" seems not reliable, we have to use command to write it manually.
For 64-bit Windows users, the command is:
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\where\you\extracted\N32_N42_unlock --sendimage=config.img --start_sector=16583680 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
If you use 32-bit Windows, you need to remove the " (x86)" (within space, without quotes) in the command above.
Step 3: Trigger the phone back to fastboot mode
Now hold the Volume down key, keep the phone connected, close the partition manager, then your phone will exit EDL mode and enter Fastboot mode directly.
Now check the unlock ability:
Code:
fastboot flashing get_unlock_ability
Expected output:
Code:
get_unlock_ability: 1
Step 4: Unlock the bootloader!
And you can unlock the bootloader with familiar commands.
Code:
fastboot flashing unlock_critical
Confirm unlock on the phone, then keep the volume down key pressed while the phone is erasing userdata.
{
"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"
}
Your phone will boot to fastboot mode again, and then:
Code:
fastboot flashing unlock
Confirm unlock on the phone again.
All done, that's how the bootloader is unlocked. You can reassemble the phone.
But strange enough, you can't see any unlock warning.
I will release boot image dumping guide and root guide very soon.
Special thanks:
Wingtech for leaking prototype units
why must Nokia insist on locking their devices down so hard ??
great discovery, will definitely be useful once TWRP is released. just curious, but SafetyNet is tripped with this, right?
Great!
Damn Nokia
I don't even own this phone but I kinda want to weigh in, are we seriously at this point? No honestly, Android as a whole was basically were dev focused iOS is locked down to hell and back here's freedom. Google has the Nexus line made for developers companies embraced it I remember there being multiple Google play editions of phones that ran stock Android. I'm happy we as a community can keep this alive but damn are companies trying to make it difficult to do something I want to do to a device I paid for and own. Samsung you can't root (save for sampwn and samfail) LG locked down bootloaders and gimped fastboot on some models (fastboot seriously?) Nokia now requiring you to take apart the freaking phone to achieve this, I'm half asleep and can't think of any other major brands at the moment. It's a joke. (Above root methods were mainly for US variants and TMobile variants of LG) something has to change I know it won't and I understand the reasoning behind it security and such but still. Sorry for the rant congrats OP on what you did I consider it magic but it's more you accomplished something I could only wish I could do.
Will it be possible to do without disassembly? Just in theory, not now
kir23rus said:
Will it be possible to do without disassembly? Just in theory, not now
Click to expand...
Click to collapse
Unwise to say no with absolute certainly, but doubtful
kir23rus said:
Will it be possible to do without disassembly? Just in theory, not now
Click to expand...
Click to collapse
I think it will be possible.
There's a hidden command in aboot "fastboot reboot-emergency" but unusable, unless some sort of authentication is done or bootloader unlocked.
I still don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
That's why disassembly is required for now.
Very interesting breakthrough. Great work
I'm facing the same bootloader unlock in my infinix hot s 3. I believe I can use your procedure to unlock my device. And if necessary how to make changes to the config file? I will be expecting your reply soon. Thanks
Is it possible to explain how the config.img file is altered ? It might not be difficult to alter the last byte , but what does it mean to Change the overall checksum ? I have been trying to do something similar for a while , it would be great if you answered here or via PM , thank you
awab228 said:
Is it possible to explain how the config.img file is altered ? It might not be difficult to alter the last byte , but what does it mean to Change the overall checksum ? I have been trying to do something similar for a while , it would be great if you answered here or via PM , thank you
Click to expand...
Click to collapse
Fill first 32 bytes with 0x00, then calculate SHA256 checksum and paste the new checksum as hex value at the first 32 bytes.
hikari_calyx said:
Fill first 32 bytes with 0x00, then calculate SHA256 checksum and paste the new checksum as hex value at the first 32 bytes.
Click to expand...
Click to collapse
Thank you for taking the time to explain, great help and great effort, the last byte should be altered to 1 ? Or 0 ?
awab228 said:
Thank you for taking the time to explain, great help and great effort, the last byte should be altered to 1 ? Or 0 ?
Click to expand...
Click to collapse
1 for allow, 0 for disallow
do you have any fastboot rom or rawxml rom for this device ??
mine always reboot in bootloader mode.
malkabhai said:
do you have any fastboot rom or rawxml rom for this device ??
mine always reboot in bootloader mode.
Click to expand...
Click to collapse
We have full OTA zip of it.
You can use payload dumper + img2simg to convert it to fastboot images. If recovery mode working (including unofficial TWRP), you can also reboot your phone to recovery mode to sideload it.
PAN-141B-0-00WW-B03-update.zip
I was able to use "OEM Unlocking" from developer options and after starting at step 3, to obtain a full unlock. After I was also able to fully root my phone using the normal guide. I am running the latest security update (October 5 2019). No idea why this worked for me...
Hello,
I've got the Nokia 3.2 16gb variant. I can get it into edl mode but it seems to be in Sahara mode. How can I put it into firehose mode? Because I can't load anything using qfil.
Any help?
Missing pads
Any idea where these pads could be now? That does not seem to be there anymore?
Missing testpoint pads
piteer1 said:
Any idea where these pads could be now? That does not seem to be there anymore?
Click to expand...
Click to collapse
I has the same problem. Thanks in advance.
I don't see those test point in my mobile
Hi, does this work for Nokia 6.1 plus TA-1083? or do you have any trick for this too?
I am able to load phone in EDL Mode by making EDL Points short.
Just in case you read my comment, I have a emmc problem post, if you can help -
https://forum.xda-developers.com/nokia-6-1-plus/help/nokia-6-1-plus-edl-mode-emmc-failure-t4114507