Database Info

TWRP black screen since Oreo upgrade

I only just upgraded to Oreo a few weeks ago - mostly delayed by my CID / dual SIM model causing me to not receiving the OTA for ages. I just noticed today that TWRP no longer works. All that happens is the screen turns black, still backlit, and oddly enough, fastboot devices still lists it.
I use fastboot boot <twrp.img> so I can keep the stock recovery installed. I'm hesitant to try flashing TWRP as I don't have a backup of the current recovery, and can't see how to make one. I suppose to restore it, I could track down a link for the OTA I applied to extract it from, but I doubt flashing TWRP would help anyway.
I've tried all the versions available from the TWRP website:
Code:
twrp-3.1.1-1-ocn.img
twrp-3.2.1-0-ocn.img
twrp-3.2.1-1-ocn.img
twrp-3.2.1-2-ocn.img
Here's my output of
Code:
fastboot getvar all
:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_ocndugl
(bootloader) version: 1.0
(bootloader) max-download-size: 2399200000
(bootloader) serialno: FA78H1800284
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 356133083656859
(bootloader) version-main: 2.42.400.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1712011153
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC30000
(bootloader) cid: HTC__060
all:
finished. total time: 0.004s
Could it be to do with some partition structure change that could be part of my model's Oreo update that TWRP has yet to reflect? I don't know what else could cause this.
Does TWRP place a log file somewhere?
Is it even getting into the TWRP boot process at all? The fact it's still listed in fastboot devices is intriguing.
I've been rooting for several years, and as a developer and avid Arch Linux user, I tend to be able to sort out most issues myself, and so only have the need to post very rarely. I've tried hard to find information on this issue, but I'm completely stumped and would very much appreciate some help. Cheers!
Edit: I thought I should probably try flashing it just in case - lo and behold, it worked! Though I'm still quite curious as to why booting directly could have stopped working.

Twrp versions are now related to the android versions, at least for htc. I think I remember reading something to do with the encryption and how twrp interacts with the os..
Newest os = newest twrp. Once you have the device running don't change/upgrade twrp. It is meant to be safe but i dont trust it.

I do recall seeing something to do with encryption, actually. Surely they're aiming for backwards compatibility though. And I'd like to think it'd show a message if it's not working.

Messed up installing 5.1.11. now only fastboot boots and can't boot twrp image.

i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.

thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here

tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?

thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.

Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.

iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.

According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.

tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.

thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.

thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.

maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?

moto one vision hard bricked

i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Take it to a service center for flashing the firmware?

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183

muppetz said:
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
Click to expand...
Click to collapse
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.

D A R K 9 said:
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.
Click to expand...
Click to collapse
You're right . It doesn't explain their proposals if you just did a simple cmd to the phone as you said . Maybe they try to squeeze some extra bucks from you . I'm sorry , man .

hard bricked one vision
its showing as exynos9610 in device manager,any leads from here??

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
good news , it seems pc recognize phone , further steps to bring back phone , no clue, but I supose it's primordial to flash partitions . Google it .

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
Look in the OP for a rom to flash in fastboot.

gee2012 said:
Look in the OP for a rom to flash in fastboot.
Click to expand...
Click to collapse
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610

D A R K 9 said:
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610
Click to expand...
Click to collapse
Try the adb command ` fastboot devices` and see if you get a serial number.

I'm also in this same situation. Been looking all around for solutions but all i come across are fixes for qualcom devices. Even all the blankflashing posts are qualcom. My guess is that we need to find software that'll work with exynos chips that isn't samsung. Adb, fastboot and mfastboot commands don't work because in its current state the device is only recognized as "Exynos9610"

I have the same problema. Im trying to follow this thread:
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865/amp/
My problem is that my computer is Windows 10 and it can't load the Exynos drivers, I hope that you have good look with that. You should try to change the cfg archive to load bootloader.

Found something intresting on "lolinet" today. A "blankflash" for kane.
Could be worth a try for sure, if you're hardbricked.
I have not tried it so I've no idea if this is legit.
The procedure would probably be something like:
Unzip all files.
Install drivers (ImageWriterUSBDriver_1113_00.exe).
Open "Multidownloader_64bit_1.4.1.exe".
Connect device to usb and let multidownloader detect it.
In the "box", browse for the "usbbooting.cfg" that is present in the kane_blankflash and hit start.
My guess is that it's supposed to reboot to fastboot once it's done writing the files so that you can reflash full firmware from fastboot, like it is with blankflash for other moto devices.
Let us know how it goes if anyone tries it.

Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
target max-sparse-size: 256MB
sending 'fwbl1' (16 KB)...
OKAY [ 0.040s]
writing 'fwbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fwbl1
FAILED (remote failure)
finished. total time: 0.082s
Click to expand...
Click to collapse
My phone get vars
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190729
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: 0057049924
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 000003B54E4B96FA0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354154101426432
(bootloader) meid:
(bootloader) date: 05-09-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Aug 28 2:48:21 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .137-16-4/fc9db:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.4.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld115) (Android (4691093 based on
(bootloader) kernel.version[2]: r316199) clang version 6.0.2 (]
(bootloader) kernel.version[3]:
(bootloader) kernel.version[4]: 83abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (
(bootloader) kernel.version[6]: hain/llvm 34361f192e41ed6e4e8f9aca80a4ea
(bootloader) kernel.version[7]: 7e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Mon Jul 29 06:52:16 CDT 201
(bootloader) kernel.version[9]: 9
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190729
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Anyone can helpme?

Okay, I know the last message here was almost 2 years ago, but I'm just here to confirm, that I've tried this blankflash and indeed, it works.
So I've rewritten both bootloader A and B slots with /dev/zero and tried to reboot. Of course, nothing happened, but the device was detected and booted into fastboot. Everything was working there. Than just flashed bootloader_a and bootloader_b and it booted like nothing happened.

danmaya said:
Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
My phone get vars
Anyone can helpme?
Click to expand...
Click to collapse
So here you have probably broken UFS (device's internal storage). If the files you try to flash are signed, but you still can't load them, then it means, you have corrupted memory. With this, go to service, they could try to replace UFS chip with another one. From what I can see, your bootloader is locked, so try to unlock it and then flash the firmware, maybe this will work.

Fire HD 8 (9th Generation) Onyx Engineering Sample (with Root access, full fastboot)

I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Images:
{
"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"
}
https://imgur.com/a/XJMwNuG <-- More here
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
More pics and some dumped data (incl. dumped partitions) https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
Let me know if there's anything interesting to try on this thing that you're aware of.
If you wanna chat about this somewhere, I've got a discord server for general purposes: https://discord.gg/pPQtYnS

It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.

MontysEvilTwin said:
It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.
Click to expand...
Click to collapse
If the specs are the exact same, then I basically have an OEM image containing working fastboot and a rooted-stock version of Fire OS that just needs patching to allow me to install apps.
Amazon's impl of PackageManager (iirc) has some checks in it that prevent me from installing anything but whitelisted apps, but I have yet to find a way to either disable that check or intercept and manipulate the whitelist.

lokio27 said:
I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
Let me know if there's anything interesting to try on this thing that you're aware of.
Click to expand...
Click to collapse
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!

I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.

Rortiz2 said:
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!
Click to expand...
Click to collapse
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: [[REDACTED]]
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
MontysEvilTwin said:
I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.
Click to expand...
Click to collapse
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.

lokio27 said:
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno:
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.
Click to expand...
Click to collapse
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output

Rortiz2 said:
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output
Click to expand...
Click to collapse
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.

lokio27 said:
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.
Click to expand...
Click to collapse
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!

Rortiz2 said:
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
Regards!
Click to expand...
Click to collapse
Wandered into my possession via eBay. Didn't even spend half of what the 10th gen costed on it, funnily enough. I'd like to fix the app installation issue so I can install stuff on it (notably Discord and/or Google Chrome)
Also, yes I'll try that.

Rortiz2 said:
Hi again,
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!
Click to expand...
Click to collapse
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s

lokio27 said:
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s
Click to expand...
Click to collapse
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.

Rortiz2 said:
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.
Click to expand...
Click to collapse
Sure, I'll DM you my Telegram.

Thanks to help from @Rortiz2, we were able to get a stock system image from the Fire HD 8 (2020) running on this tablet. Sure enough, still have root permissions, and now I can actually install apps! Will be updating as more things are discovered.

You guys are amazing.

a guide maybe?
hi guy/gals, is there a guide for rooting the Onyx variant? thanks for your efforts!!!

I hope you guys find a way to crack this baby.

joining in this baby as well

Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?

Awesomeslayerg said:
Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?
Click to expand...
Click to collapse
no there isnt a bootrom exploit at this time on the hd8 (10). Mediatek seems to have fixed the exploit on their chip. If anyone can find a way to get into the bootrom there is hope for the old exploit. Maybe someone will get a root exploit that will force a bootrom boot. still early in the device....

Need advice on flashing - I keep getting errors

Good day all
i have been trying to flash a phone for a few weeks now with no success i have tried various flashing tools and some dont work at all and others have various errors appearing
currently i am using Qfil as thats been recommeneded a number of times but have had a number of errors with the software and this is the main error i get
11:37:47: INFO: File system.img is a sparse file, being split up into 7943 separate XML tags
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:37:50: {ERROR: StoreXMLFile:8890 2. Too many XML files in XMLStringTable, max is 8000
and i have tried various versions of the Qfil software from earliest to latest with no luck
until the other day i googled the error mentioned above and i came across a forum that linked to a flashing tool turned out to be Qfil again but on this occastion there was more activity it started the flashing process it appears to me it is flashing the images but seem to stop short of reaching 100% the amount transfered is different for each image it try sending and then errors out and moves onto the next image same thing raches a set percentage then error
i have attached some files a couple of screenshots plus the port trace txt file so hopefully someone can make sense of whats going on
im aware of some phones dont like being flashed with their battery still connected would it be worth cracking open the back cover and try disconnecting it
lastly to rule out any memory problems is there a tool that can read the emmc memory test it and detect any possible bad sectors if there is any issues how to get the flash tool to partition and flash around any bad sectors
many thanks

nighthawk658 said:
Good day all
i have been trying to flash a phone for a few weeks now with no success i have tried various flashing tools and some dont work at all and others have various errors appearing
currently i am using Qfil as thats been recommeneded a number of times but have had a number of errors with the software and this is the main error i get
11:37:47: INFO: File system.img is a sparse file, being split up into 7943 separate XML tags
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:37:50: {ERROR: StoreXMLFile:8890 2. Too many XML files in XMLStringTable, max is 8000
and i have tried various versions of the Qfil software from earliest to latest with no luck
until the other day i googled the error mentioned above and i came across a forum that linked to a flashing tool turned out to be Qfil again but on this occastion there was more activity it started the flashing process it appears to me it is flashing the images but seem to stop short of reaching 100% the amount transfered is different for each image it try sending and then errors out and moves onto the next image same thing raches a set percentage then error
i have attached some files a couple of screenshots plus the port trace txt file so hopefully someone can make sense of whats going on
im aware of some phones dont like being flashed with their battery still connected would it be worth cracking open the back cover and try disconnecting it
lastly to rule out any memory problems is there a tool that can read the emmc memory test it and detect any possible bad sectors if there is any issues how to get the flash tool to partition and flash around any bad sectors
many thanks
Click to expand...
Click to collapse
What is the device model number? What are you trying to flash? Are you trying to flash a stock software or are you trying to flash a custom software?

Droidriven said:
What is the device model number? What are you trying to flash? Are you trying to flash a stock software or are you trying to flash a custom software?
Click to expand...
Click to collapse
Thanks for your reply
Am trying to flash a stock firmware .. the mobile phone is an Asus ZenFone 5Q ZC600KL
I just noticed this minute that the error report from Qfil didn't upload I assume either this site doesn't allow txt documents or the size of the file it's to big
It's actually the error report in text file that would be more relevant

nighthawk658 said:
Thanks for your reply
Am trying to flash a stock firmware .. the mobile phone is an Asus ZenFone 5Q ZC600KL
I just noticed this minute that the error report from Qfil didn't upload I assume either this site doesn't allow txt documents or the size of the file it's to big
It's actually the error report in text file that would be more relevant
Click to expand...
Click to collapse
Try this, I tested the download link for the first firmware.zip on the list and it successfully downloaded.
Asus ZenFone 5 Lite Stock Firmware Collections [Back To Stock ROM]
Do you want to install Stock ROM on Asus ZenFone 5 Lite (ZC600KL)? then, you are at the right place. Here we will share all the latest Asus ZenFone 5 Lite
www.getdroidtips.com
Try downloading whichever firmware.zip of your choice from the list then try the two installation methods described in the guide.

Droidriven said:
Try this, I tested the download link for the first firmware.zip on the list and it successfully downloaded.
Asus ZenFone 5 Lite Stock Firmware Collections [Back To Stock ROM]
Do you want to install Stock ROM on Asus ZenFone 5 Lite (ZC600KL)? then, you are at the right place. Here we will share all the latest Asus ZenFone 5 Lite
www.getdroidtips.com
Try downloading whichever firmware.zip of your choice from the list then try the two installation methods described in the guide.
Click to expand...
Click to collapse
Thanks for that
I already have the firmware so am good with that
Reading the instructions I have not tired the first one yet by placing the firmware on memory card but will get a card and try that option ... ( BUT ) by trying to get into recovery mode or factory reset those options don't appear because that was the first thing I tried is getting into that menu for a factory reset but all I can get is CSC fastboot.. will recovery come up if the firmware is on a mem card
Second option I cannot do because the bootloader is locked and I cannot access the developer options or the OEM unlock because the phone is stuck on Logo
It I attempt to flash by fastboot it just says cannot flash in locked state
Will ask the missus for her mem card and try that recovery ootion but not sure if it will go but worth a shot..
But if flashing in EDL mode is my last resort I ideally need to get to the bottom of what's causing errors one error I seen comes up NAK and the rest are not completing the various images system stops at 84% other images at different percentages

nighthawk658 said:
Thanks for that
I already have the firmware so am good with that
Reading the instructions I have not tired the first one yet by placing the firmware on memory card but will get a card and try that option ... ( BUT ) by trying to get into recovery mode or factory reset those options don't appear because that was the first thing I tried is getting into that menu for a factory reset but all I can get is CSC fastboot.. will recovery come up if the firmware is on a mem card
Second option I cannot do because the bootloader is locked and I cannot access the developer options or the OEM unlock because the phone is stuck on Logo
It I attempt to flash by fastboot it just says cannot flash in locked state
Will ask the missus for her mem card and try that recovery ootion but not sure if it will go but worth a shot..
But if flashing in EDL mode is my last resort I ideally need to get to the bottom of what's causing errors one error I seen comes up NAK and the rest are not completing the various images system stops at 84% other images at different percentages
Click to expand...
Click to collapse
Have you tried doing a Google search for the specific error that you were getting?
Where did you download the firmware that you have been trying to flash? If you extract the file that you have, what is inside of it? Do you know if it is an update file that was designed to be flashed via stock recovery or is it an update file that was designed to be flashed via other flash tools? It makes a difference, if it was not designed to be flashed via stock recovery then it will not work. There is a difference between a firmware flash file and a stock recovery flashable update.
Try downloading the file listed in the guide because you can be 100% sure that it will work via the methods discussed in the guide provided that you follow the instructions to the letter. Just make sure to rename the file(the file I'm telling you to download) to "update.zip" or it will not flash.
As for why you are having issues with booting into stock recovery, what methods have you used to try getting into recovery? Does your device have a bootloader menu that gives you options to boot into bootloader mode, recovery mode, etc? Have you try using adb to issue the "adb reboot recovery" command? Can you connect to fastboot and reboot recovery?

Droidriven said:
Have you tried doing a Google search for the specific error that you were getting?
Where did you download the firmware that you have been trying to flash? If you extract the file that you have, what is inside of it? Do you know if it is an update file that was designed to be flashed via stock recovery or is it an update file that was designed to be flashed via other flash tools? It makes a difference, if it was not designed to be flashed via stock recovery then it will not work. There is a difference between a firmware flash file and a stock recovery flashable update.
Try downloading the file listed in the guide because you can be 100% sure that it will work via the methods discussed in the guide provided that you follow the instructions to the letter. Just make sure to rename the file(the file I'm telling you to download) to "update.zip" or it will not flash.
As for why you are having issues with booting into stock recovery, what methods have you used to try getting into recovery? Does your device have a bootloader menu that gives you options to boot into bootloader mode, recovery mode, etc? Have you try using adb to issue the "adb reboot recovery" command? Can you connect to fastboot and reboot recovery?
Click to expand...
Click to collapse
Yes did try to Google the errors but seem to be very little information about the errors and what does come up either relates to a different phone or states various things like changing drivers and versions of flash tool
The firmware I got is the exact firmware version I found on the phone I got the firmware version by pulling the version.bin file off of the phone and opening it in a hex program it was rather hard to find the version I can't remember the site I found it on but it all appears to be a complete set of files
In the firmware it has all the image files boot.img system.img and so on also the .elf files needed for Qfil the patch and so on
It also contains the batch files for using fastboot
In fastboot I can detect the phone using fastboot devices command it shows the serial number when executing the flashall command it will start sending data but will then just say cannot flash in locked state
I have tried ADB commands and from what I can remember it doesn't respond even ADB devices command shows nothing I assume because debugging is not enabled
To enter the recovery and or factory reset menu I tried all the combination the hold down of volume down plus power and volume up plus power only thing that appears is the CSC fastboot mode so where I would normally enter into factory reset on other phones using the standard procedure doesn't work on this phone
And I can enter EDL by holding both volume buttons and plugging in usb cable
I would like to post the last errors as I mentioned above that shows an error NAK and where it shows on each image it stops at a fixed percentage for example system.img stops at 84%
Due to the huge amount of data in the text file I can't copy it on here
Unfortunately I can't get a memory card yet stores nearby not got one in 4GB range in stock and due to restrictions can't get into city so am a bit stuck there

nighthawk658 said:
Yes did try to Google the errors but seem to be very little information about the errors and what does come up either relates to a different phone or states various things like changing drivers and versions of flash tool
The firmware I got is the exact firmware version I found on the phone I got the firmware version by pulling the version.bin file off of the phone and opening it in a hex program it was rather hard to find the version I can't remember the site I found it on but it all appears to be a complete set of files
In the firmware it has all the image files boot.img system.img and so on also the .elf files needed for Qfil the patch and so on
It also contains the batch files for using fastboot
In fastboot I can detect the phone using fastboot devices command it shows the serial number when executing the flashall command it will start sending data but will then just say cannot flash in locked state
I have tried ADB commands and from what I can remember it doesn't respond even ADB devices command shows nothing I assume because debugging is not enabled
To enter the recovery and or factory reset menu I tried all the combination the hold down of volume down plus power and volume up plus power only thing that appears is the CSC fastboot mode so where I would normally enter into factory reset on other phones using the standard procedure doesn't work on this phone
And I can enter EDL by holding both volume buttons and plugging in usb cable
I would like to post the last errors as I mentioned above that shows an error NAK and where it shows on each image it stops at a fixed percentage for example system.img stops at 84%
Due to the huge amount of data in the text file I can't copy it on here
Unfortunately I can't get a memory card yet stores nearby not got one in 4GB range in stock and due to restrictions can't get into city so am a bit stuck there
Click to expand...
Click to collapse
Trying different versions of flashtool has been known to solve flashing issues.
As for fastboot saying it can't flash while in locked state. Have you tried connecting to fastboot and then typing the command:
fastboot OEM unlock
Or
fastboot flashing unlock
If those don't work, do a Google search for:
"How to unlock bootloader (your specific model number"
Unlocking bootloader may allow fastboot to flash your file(s). Try flashing the whole file first, if it will not flash all at once, try flashing the .img files one at a time, but, make sure you use the correct command for each individual .img, using the wrong command could flash them in the wrong partition which would then cause a bigger problem to fix.
If your file has a series of .img files in it when you extract it, then the file you have is not the file that is designed to be flashed via stock recovery. That file is not going to work with the methods described in the guide. Stop being stubborn and listen to me, download the update from the guide, download it, download it, download it.
The memory card doesn't necessarily have to be 4GB, it can be any size greater than that, you only need the card as a medium to store the file so that stock recovery can find, access and flash the file.
Not all devices boot into recovery the same way, some have different button combinations and some have a bootloader menu with recovery as one of the options on the list. Unless you have corrupted your recovery partition, you should be able to boot into recovery.
You may have to use "fastboot erase" commands to wipe the cache partition and system partition then try flashing the firmware via fastboot. E.g. "fastboot erase cache" and "fastboot erase system". This may clear out any issues that were interfering with it successfully flashing. Have you tried extracting the file that you have and then flashing each individual file one at a time via fastboot? For exampleq:
fastboot flash system <name of your system.img>
fastboot flash boot <name of your boot.img>
If you attempt to flash your .img files via fastboot, remember to put your file in your fastboot folder on your PC, then extract the various .img files from inside it. Then, with the fastboot folder open in Windows file explorer, hold the shift key then right-click on your mouse, in the menu that pops up, select "open command here".
How did this issue start? What was your original reason for flashing the device? How many different ways have you tried to flash the device and what problems did you encounter with those methods? Depending on what you have tried up to now, you may have corrupted the device to the point that normal flashing methods won't work. You may have to use EDL mode to flash it. Have you found a guide that explains how to flash your specific device using EDL mode?
Please read this post carefully and answer every question I've asked. I'm trying to approach your issue from as many different angles as possible, maybe one of them will lead to a solution.

Hi
thanks for the new tips i will give that erase method a go and flashing the IMG files one by one as you suggested and will update on that either way i think that is the one method i have not tried yet because all the instructions i followed was based either on fastboot and using the flashall command or the Qfil under EDL mode and thinking about it if the old files are still on the phone might be why it wont flash the new ones
you asked how the issue started and reason for flashing well the phone got stuck on the Asus Logo when powering the phone on it would flash up saying powered by android then the asus logo will apear and its stuck there
the next process was to do what i would do with any phone is try to do a recovery / factory reset by using the volume down and power buttons but phone doesnt respond so tried the volume up and power and just brings me into CSC fastboot mode i tried holding volume button down press power and release power when phone vibtates but kept holding volume nothing happened ans then i tried holding both volume buttons plus power no response so either the phone was setup in a way that the recovery options was never there or some how the phone got corrupted i dont know because one minute it was working as normal and next its the Asus logo
tho i should say the phone at times had got a little warm usually because the phone is a bit of a work horse meaning its always being used for video recording and uploading and other work related tasks
all that i have tried has been the fastboot options such as being able to detect the phone via the fastboot devices command and that does bring up the serial number and have tried to use the flashall command per what the instructions said it would appear its doing something then suddenly it will give up the error cannot flashed in lock state oh yes and did run a command that bring up info about the bootloader and it states the bootloader unlocked is set to false
then i have tried the Qfil software and in most cases it had always given errors such as sahara errors and too many XML in string table max was supposed to be 8000 but it was something like 8900
the interesting thing to note is that i had downloaded several firmwares because i was not sure of the exact firmware on the phone so i was left guessing at the selection that was given so i tried working with a more up to date the interesting part about that is when trying in fastboot the error was different compared to the last 2 firmwares i tried the first 3 i tried i would get almost instantly a write protected error where as the last 2 firmwares will bring up the cannot falsh in locked state error so it seems to me the newer versions of the firmware the phone is rejecting where as the last 2 firmwares the phone seems to respond to them and fastboot might accept them if the bootloader is unlocked
back to Qfil i tried researching the various errors that displaed mainly the too many XML in string table and came across a post on XDA regarding Flashone 2.0 it has a Qfil flasher within its folders and i have tried that and that is the one that gave me the most action and that is what i discussed above when it copies over the IMG files it would stop and error at certian percentages such as system.bin 85% another image maybe 20% i will try and copy a snippet of the log on here so you can see for your self and this version of the Qfil was the first time i ever seen the blue progress bar move
in your reply you mentioned about using an update file i assume is where you mentioned the memory card i cant do the memory card option just yet because i cant get access to memor card have to rely on stores near home and dont have in stock size i need i dont want to go out and buy a huge size as i rarely ever use memor cards .. and i do believe one of the firmwares i download was actually an update rather than a folder full of files and because i cannot access any of the options under hardware key on start up im in doubt that accessing the memory card to recover would work anyway
now looking at the website you gave with the instructions i believe the memory card option as mentioned may not work because the volume up plus power puts the phone into CSC fastboot mode only
second option is install via ADB Sideload but the requirements is the phone needs to have its developer options enabled and thats disabled on this phone
as for the question about the bootloader yes have tried those commands you mentioned doesnt work and any research on unlocking bootloader for this model seems to always bring me back to the same options by using the APK file from Asus or the ADB commands
by the way here is the list of firmwares i have tried not sure if the info will help but its here anyway just in case Note the last 2 firmwares are the ones i mentioned above that seems to make the phone respond differently compared to the first ones
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
ASUS Factory WW ZC600KL(630)-14.0400.1807.056-20180816
[firmware27]NGI77B.WW_Phone-14.0400.1801.018-20180128(SW_T89199AA1_V018_M10_EF_ASUS_ZC600KL_USRD_ATO)
UL-ASUS_X017D_2-WW-14.0400.1811.061-user
[up_vnROM.net]_WW__ZC600KL(630)_14.0400.1801.031_20180313_Phone-user
WW__ZC600KL(630)_14.0400.1801.021_20180204_Phone-user
the last firmware on the list is the one i believe is the original version thats installed on the phone as i managed to pull the version.bin off of the device and open the bin file using Hex and this was what i found
4028938�1ASUS_X017D_2���asus/WW_Phone/ASUS_X017D_2:7.1.1/NGI77B/14.0400.1801.021-20180204:user/release-keys���������������������������������������������wt89199-user������������wt89199-user 7.1.1 NGI77B 14.0400.1801.021-20180204 release-keys��������������������WW__ASUS_X017DA_14.0400.1801.021����������������SW_T89199AA1_V021_M10_NF_ASUS_ZC600KL_USR_TEST��������������
here is a quick snippet from the text document of the error that i mentioned about when it stops copying after a certain percentage
this is one of the erorrs i mentioned 12:31:43: DEBUG: Response was 'NAK'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:31:43: {ERROR: handleProgram:7786 Please see log
12:31:43: INFO: In handleProgram('tz.mbn')
12:31:43: DEBUG:
second error
i will need to post the details a bit later cant find the full error its not showing in the log file but seems to only appear within Qfil so will attempt to get those details later
am downloading one of the firmwares from the link you gave

Droidriven said:
Trying different versions of flashtool has been known to solve flashing issues.
As for fastboot saying it can't flash while in locked state. Have you tried connecting to fastboot and then typing the command:
fastboot OEM unlock
Or
fastboot flashing unlock
If those don't work, do a Google search for:
"How to unlock bootloader (your specific model number"
Unlocking bootloader may allow fastboot to flash your file(s). Try flashing the whole file first, if it will not flash all at once, try flashing the .img files one at a time, but, make sure you use the correct command for each individual .img, using the wrong command could flash them in the wrong partition which would then cause a bigger problem to fix.
If your file has a series of .img files in it when you extract it, then the file you have is not the file that is designed to be flashed via stock recovery. That file is not going to work with the methods described in the guide. Stop being stubborn and listen to me, download the update from the guide, download it, download it, download it.
The memory card doesn't necessarily have to be 4GB, it can be any size greater than that, you only need the card as a medium to store the file so that stock recovery can find, access and flash the file.
Not all devices boot into recovery the same way, some have different button combinations and some have a bootloader menu with recovery as one of the options on the list. Unless you have corrupted your recovery partition, you should be able to boot into recovery.
You may have to use "fastboot erase" commands to wipe the cache partition and system partition then try flashing the firmware via fastboot. E.g. "fastboot erase cache" and "fastboot erase system". This may clear out any issues that were interfering with it successfully flashing. Have you tried extracting the file that you have and then flashing each individual file one at a time via fastboot? For exampleq:
fastboot flash system <name of your system.img>
fastboot flash boot <name of your boot.img>
If you attempt to flash your .img files via fastboot, remember to put your file in your fastboot folder on your PC, then extract the various .img files from inside it. Then, with the fastboot folder open in Windows file explorer, hold the shift key then right-click on your mouse, in the menu that pops up, select "open command here".
How did this issue start? What was your original reason for flashing the device? How many different ways have you tried to flash the device and what problems did you encounter with those methods? Depending on what you have tried up to now, you may have corrupted the device to the point that normal flashing methods won't work. You may have to use EDL mode to flash it. Have you found a guide that explains how to flash your specific device using EDL mode?
Please read this post carefully and answer every question I've asked. I'm trying to approach your issue from as many different angles as possible, maybe one of them will lead to a solution.
Click to expand...
Click to collapse
here is an update
have downloaded the firmware from the site you mentioned but i will need to wait till i get a memory card and cannot do the sideloading using ADB as i cannot enable developer options but i did try it anyway and will show the error messages
i also tried the erase command you mentioned i tried the erase on the cache it seemed to have done something rather quickly but did not show any error so then tried to flash the cache image from the firmware folder and did get an error
here is the errors for both adb and fastboot commands note there is 2 errors for the flash part because i did it fastboot flash cache.bin but per your message it said to fastboot flash cache cache.bin
Under ADB commands
C:\Users\Me\Desktop\firmware flashing>adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
fastboot commands
C:\Users\Me\Desktop\firmware flashing>fastboot devices
J2AXHM011670RNJ fastboot
C:\Users\Me\Desktop\firmware flashing>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.008s]
Finished. Total time: 0.023s
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache.bin
unknown partition 'cache.bin'
fastboot: error: cannot determine image filename for 'cache.bin'
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache cache.bin
fastboot: error: cannot load 'cache.bin': No such file or directory
as you asked earlier about the files within the firmware folder i have taken a screenshot so you can have a look at whats what it also should show the version details there also
i have also attached a text document (( i hope it shows up on site this time )) this is the log i saved directly from the information under the progress bar in Qfil it shows a lot of errors but i will also show what i was talking about when i mentioned it stops afrer a certain percentage
hope the information given could be helpful
again thanks for your time much appreciated

nighthawk658 said:
here is an update
have downloaded the firmware from the site you mentioned but i will need to wait till i get a memory card and cannot do the sideloading using ADB as i cannot enable developer options but i did try it anyway and will show the error messages
i also tried the erase command you mentioned i tried the erase on the cache it seemed to have done something rather quickly but did not show any error so then tried to flash the cache image from the firmware folder and did get an error
here is the errors for both adb and fastboot commands note there is 2 errors for the flash part because i did it fastboot flash cache.bin but per your message it said to fastboot flash cache cache.bin
Under ADB commands
C:\Users\Me\Desktop\firmware flashing>adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
fastboot commands
C:\Users\Me\Desktop\firmware flashing>fastboot devices
J2AXHM011670RNJ fastboot
C:\Users\Me\Desktop\firmware flashing>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.008s]
Finished. Total time: 0.023s
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache.bin
unknown partition 'cache.bin'
fastboot: error: cannot determine image filename for 'cache.bin'
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache cache.bin
fastboot: error: cannot load 'cache.bin': No such file or directory
as you asked earlier about the files within the firmware folder i have taken a screenshot so you can have a look at whats what it also should show the version details there also
i have also attached a text document (( i hope it shows up on site this time )) this is the log i saved directly from the information under the progress bar in Qfil it shows a lot of errors but i will also show what i was talking about when i mentioned it stops afrer a certain percentage
hope the information given could be helpful
again thanks for your time much appreciated
Click to expand...
Click to collapse
The command to flash your cache.bin is:
fastboot flash cache cache.bin
Fastboot commands to flash .img/.bin files to their proper partitions work like this:
fastboot flash <name of partition> <name of .img/.bin>
For example, to flash system.img:
fastboot flash system system.img
Do you see how it says "fastboot flash system" and then it says "system.img"? Do you see how it says "fastboot flash"(this tells fastboot that you want to flash a file), then it says "system"(this tells fastboot which physical partition you want to flash a file to), then it says "system.img"(this tells fastboot which file you want to flash to the specified partition)? You are telling fastboot that you want to flash "this" partition with "that" file.
To flash recovery:
fastboot flash recovery recovery.img
Again, the action that you want fastboot to perform(fastboot flash) followed by the name of the partition(recovery) followed by the name of the file that you want to flash to that partition(recovery.img)
A bit overdefined but I hope this helps you understand the structure or syntax required for fastboot flash commands.
To post your .txt file, upload it to hosting site of some kind and then post a link to it here then it can be viewed here.
Also, just to be sure, place your files inside your fastboot folder on your PC, then, when you open a command window, do it by going to the fastboot folder in Windows file explorer, then, with the mouse pointer somewhere in the empty field of that folder, hold the shift key and then right click, on that menu that pops up, select "open command here", then try the commands. This "might" fix the unknown file error because it bypasses the need for a file path in your commands and flashes files located in the fastboot folder by default without having a path name in the commands, you don't have to tell it to look for the file in fastboot folder, it does it automatically if the file is located in that folder.
Other than what I have told you so far, I think I might agree with you that you may not get anything to work with the bootloader being locked and USB debugging not being enabled. You may have to resort to EDL flashing methods, it is more of a "brute force" flashing method as it bypasses the bootloader.

Droidriven said:
The command to flash your cache.bin is:
fastboot flash cache cache.bin
Fastboot commands to flash .img/.bin files to their proper partitions work like this:
fastboot flash <name of partition> <name of .img/.bin>
For example, to flash system.img:
fastboot flash system system.img
Do you see how it says "fastboot flash system" and then it says "system.img"? Do you see how it says "fastboot flash"(this tells fastboot that you want to flash a file), then it says "system"(this tells fastboot which physical partition you want to flash a file to), then it says "system.img"(this tells fastboot which file you want to flash to the specified partition)? You are telling fastboot that you want to flash "this" partition with "that" file.
To flash recovery:
fastboot flash recovery recovery.img
Again, the action that you want fastboot to perform(fastboot flash) followed by the name of the partition(recovery) followed by the name of the file that you want to flash to that partition(recovery.img)
A bit overdefined but I hope this helps you understand the structure or syntax required for fastboot flash commands.
To post your .txt file, upload it to hosting site of some kind and then post a link to it here then it can be viewed here.
Also, just to be sure, place your files inside your fastboot folder on your PC, then, when you open a command window, do it by going to the fastboot folder in Windows file explorer, then, with the mouse pointer somewhere in the empty field of that folder, hold the shift key and then right click, on that menu that pops up, select "open command here", then try the commands. This "might" fix the unknown file error because it bypasses the need for a file path in your commands and flashes files located in the fastboot folder by default without having a path name in the commands, you don't have to tell it to look for the file in fastboot folder, it does it automatically if the file is located in that folder.
Other than what I have told you so far, I think I might agree with you that you may not get anything to work with the bootloader being locked and USB debugging not being enabled. You may have to resort to EDL flashing methods, it is more of a "brute force" flashing method as it bypasses the bootloader.
Click to expand...
Click to collapse
ok here is the latest
i tried the flashing of files again as i realised my mistake yesterday was using the extention .bin when it should of been .img i think the word bin got stuck in my brain because of the Qfil software as i access it from Bin folder haha
anyway i did the fastboot earse cache command and seemed ok
and then attempted to flash the cache.img file using fastboot flash cache cache.img and i got error
C:\Users\Me\Desktop\flashing folder>fastboot flash cache cache.img
Sending 'cache' (6400 KB) OKAY [ 0.265s]
Writing 'cache' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
i am suspecting thats because the bootloader is locked as per your question about researching how to unlock my bootloader sadly i been unable to find any working solution for this model other than the unlock app via the asus website but since the phone doesnt boot thats of no use
so i either need another method to unlock the bootloader and try flashing again or i need to be able to flash via EDL mode
by the way here is details from getvar all command just in case if any of the info is of any use
C:\Users\Me\Desktop\flashing folder>fastboot getvar all
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4068
(bootloader) version-baseband:
(bootloader) version-bootloader-CS2-8.0-user
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD20BF7E00
(bootloader) partition-type:version:raw
(bootloader) partition-size:version: 0x500000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xD000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:asusfw:raw
(bootloader) partition-size:asusfw: 0x4000000
(bootloader) partition-type:wt_ftm:raw
(bootloader) partition-size:wt_ftm: 0x500000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:factorybak:raw
(bootloader) partition-size:factorybak: 0xA00000
(bootloader) partition-type:factory:raw
(bootloader) partition-size:factory: 0xA00000
(bootloader) partition-type:asuskey6:raw
(bootloader) partition-size:asuskey6: 0x100000
(bootloader) partition-type:asuskey5:raw
(bootloader) partition-size:asuskey5: 0x100000
(bootloader) partition-type:asuskey4:raw
(bootloader) partition-size:asuskey4: 0x100000
(bootloader) partition-type:asuskey3:raw
(bootloader) partition-size:asuskey3: 0x100000
(bootloader) partition-type:asuskey2:raw
(bootloader) partition-size:asuskey2: 0x100000
(bootloader) partition-type:asuskey:raw
(bootloader) partition-size:asuskey: 0x100000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:bluetoothbak:raw
(bootloader) partition-size:bluetoothbak: 0x100000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x400
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x120000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x400000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) project-info:ZC600KL-SDM630
(bootloader) aft_support:yes
(bootloader) secure:yes
(bootloader) serial:c462427
(bootloader) product:sdm660
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 5.844s

nighthawk658 said:
ok here is the latest
i tried the flashing of files again as i realised my mistake yesterday was using the extention .bin when it should of been .img i think the word bin got stuck in my brain because of the Qfil software as i access it from Bin folder haha
anyway i did the fastboot earse cache command and seemed ok
and then attempted to flash the cache.img file using fastboot flash cache cache.img and i got error
C:\Users\Me\Desktop\flashing folder>fastboot flash cache cache.img
Sending 'cache' (6400 KB) OKAY [ 0.265s]
Writing 'cache' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
i am suspecting thats because the bootloader is locked as per your question about researching how to unlock my bootloader sadly i been unable to find any working solution for this model other than the unlock app via the asus website but since the phone doesnt boot thats of no use
so i either need another method to unlock the bootloader and try flashing again or i need to be able to flash via EDL mode
by the way here is details from getvar all command just in case if any of the info is of any use
C:\Users\Me\Desktop\flashing folder>fastboot getvar all
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4068
(bootloader) version-baseband:
(bootloader) version-bootloader-CS2-8.0-user
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD20BF7E00
(bootloader) partition-type:version:raw
(bootloader) partition-size:version: 0x500000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xD000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:asusfw:raw
(bootloader) partition-size:asusfw: 0x4000000
(bootloader) partition-type:wt_ftm:raw
(bootloader) partition-size:wt_ftm: 0x500000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:factorybak:raw
(bootloader) partition-size:factorybak: 0xA00000
(bootloader) partition-type:factory:raw
(bootloader) partition-size:factory: 0xA00000
(bootloader) partition-type:asuskey6:raw
(bootloader) partition-size:asuskey6: 0x100000
(bootloader) partition-type:asuskey5:raw
(bootloader) partition-size:asuskey5: 0x100000
(bootloader) partition-type:asuskey4:raw
(bootloader) partition-size:asuskey4: 0x100000
(bootloader) partition-type:asuskey3:raw
(bootloader) partition-size:asuskey3: 0x100000
(bootloader) partition-type:asuskey2:raw
(bootloader) partition-size:asuskey2: 0x100000
(bootloader) partition-type:asuskey:raw
(bootloader) partition-size:asuskey: 0x100000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:bluetoothbak:raw
(bootloader) partition-size:bluetoothbak: 0x100000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x400
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x120000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x400000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) project-info:ZC600KL-SDM630
(bootloader) aft_support:yes
(bootloader) secure:yes
(bootloader) serial:c462427
(bootloader) product:sdm660
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 5.844s
Click to expand...
Click to collapse
Yep, that data shows the bootloader is definitely locked, I don't have anything else to offer for advice in the scenario you are in as I'm not familiar enough with your model number or hardware architecture. I'd probably get you stuck in worse position from here on. As far as I can tell since I started helping, you haven't really done anything except erase the cache.img, that shouldn't be too complicated to straighten out if you can get the firmware to flash. I don't understand why the firmware won't flash, if it is the exact same version that was already on the device, it seems like it should flash without having to unlock the bootloader. It may be due to USB debugging not being enabled instead of it being an issue with the bootloader being locked.
EDL seems to be your only option from here going forward, I doubt anything else will, its virtually your last and only shot.

Droidriven said:
Yep, that data shows the bootloader is definitely locked, I don't have anything else to offer for advice in the scenario you are in as I'm not familiar enough with your model number or hardware architecture. I'd probably get you stuck in worse position from here on. As far as I can tell since I started helping, you haven't really done anything except erase the cache.img, that shouldn't be too complicated to straighten out if you can get the firmware to flash. I don't understand why the firmware won't flash, if it is the exact same version that was already on the device, it seems like it should flash without having to unlock the bootloader. It may be due to USB debugging not being enabled instead of it being an issue with the bootloader being locked.
EDL seems to be your only option from here going forward, I doubt anything else will, its virtually your last and only shot.
Click to expand...
Click to collapse
yes does seem the bootloader or something to do with debugging is a possible issue
i have tried to use Qfil as mentioned before but that always kept throwing up errors and also has been a mix bag of activity also most of the versions of Qfil i tried never did anything other than throwing up an error almost instantly
but i did download a package named flashone and as mentioned before gave the most activity by actually trasnfering images and progress bar moving i think the progrss bar stopped at 85% with images stopping at random percentages but all in all that was more activity than it ever did before using Qflash so something is amiss somewhere
and it took me a while to figure out the exact firmware that was on the phone luckily i used San mobile Qualcomm tool and i pulled files off of the phone and looked in the version image using a hex tool and found the exact firmware
have even tried using san mobile tool to flash over the images but get an error
there is a suggestion it may be a hardware issue the fact that i can pull data off of the phone suggests its not a read problem
but to rule out any hardware issues do you know of any tools i can run a memory test look for bad sectors on the phone memory if any a way to partition around them
but i do thank you for all your assisance on this it has been very much appreciated