yashsingh1/xdaforums huggingface dataset:
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
~ # ls -d $(find /dev/block -name by-name)/*

/dev/block/platform/soc.0/7824900.sdhci/by-name/ADF

/dev/block/platform/soc.0/7824900.sdhci/by-name/APD

/dev/block/platform/soc.0/7824900.sdhci/by-name/DDR

/dev/block/platform/soc.0/7824900.sdhci/by-name/aboot

/dev/block/platform/soc.0/7824900.sdhci/by-name/abootbak

/dev/block/platform/soc.0/7824900.sdhci/by-name/abootdebug

/dev/block/platform/soc.0/7824900.sdhci/by-name/asdf

/dev/block/platform/soc.0/7824900.sdhci/by-name/asusfw

/dev/block/platform/soc.0/7824900.sdhci/by-name/asusgpt

/dev/block/platform/soc.0/7824900.sdhci/by-name/asusgpt1

/dev/block/platform/soc.0/7824900.sdhci/by-name/asusgpt2

/dev/block/platform/soc.0/7824900.sdhci/by-name/asuskey

/dev/block/platform/soc.0/7824900.sdhci/by-name/asuskey2

/dev/block/platform/soc.0/7824900.sdhci/by-name/asuskey3

/dev/block/platform/soc.0/7824900.sdhci/by-name/asuskey4

/dev/block/platform/soc.0/7824900.sdhci/by-name/boot

/dev/block/platform/soc.0/7824900.sdhci/by-name/cache

/dev/block/platform/soc.0/7824900.sdhci/by-name/config

/dev/block/platform/soc.0/7824900.sdhci/by-name/factory

/dev/block/platform/soc.0/7824900.sdhci/by-name/factorybak

/dev/block/platform/soc.0/7824900.sdhci/by-name/fsc

/dev/block/platform/soc.0/7824900.sdhci/by-name/fsg

/dev/block/platform/soc.0/7824900.sdhci/by-name/hyp

/dev/block/platform/soc.0/7824900.sdhci/by-name/hypbak

/dev/block/platform/soc.0/7824900.sdhci/by-name/keystore

/dev/block/platform/soc.0/7824900.sdhci/by-name/misc

/dev/block/platform/soc.0/7824900.sdhci/by-name/modem

/dev/block/platform/soc.0/7824900.sdhci/by-name/modemst1

/dev/block/platform/soc.0/7824900.sdhci/by-name/modemst2

/dev/block/platform/soc.0/7824900.sdhci/by-name/oem

/dev/block/platform/soc.0/7824900.sdhci/by-name/persist

/dev/block/platform/soc.0/7824900.sdhci/by-name/persistent

/dev/block/platform/soc.0/7824900.sdhci/by-name/recovery

/dev/block/platform/soc.0/7824900.sdhci/by-name/rpm

/dev/block/platform/soc.0/7824900.sdhci/by-name/rpmbak

/dev/block/platform/soc.0/7824900.sdhci/by-name/sbl1

/dev/block/platform/soc.0/7824900.sdhci/by-name/sbl1bak

/dev/block/platform/soc.0/7824900.sdhci/by-name/sec

/dev/block/platform/soc.0/7824900.sdhci/by-name/ssd

/dev/block/platform/soc.0/7824900.sdhci/by-name/system

/dev/block/platform/soc.0/7824900.sdhci/by-name/tz

/dev/block/platform/soc.0/7824900.sdhci/by-name/tzbak

/dev/block/platform/soc.0/7824900.sdhci/by-name/userdata
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
my ze500kl already on android 10 hovatecOS , whar file is safety to flash for test before i should flash all 1 to 42?,

aboot is safety to flash for test ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
i am not sure what do you want. aboot is the bootloader, which obviously works. therefore no need to flash. it is risky to flash aboot, if aboot doesn't work you cannot enter fastboot or recovery.

I thought your goal was to unbrick this device, therefore flashing complete stock ROM. maybe easier method, flash this zip from OrangeFox

https://www.asus.com/supportonly/asus zenfone 2 laser (ze500kl)/helpdesk_bios

BUT if you're already on Android 10, why flash older android?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
how to flash that file with orangeFOX ?

,

im not posibble download those 1,5 gb zip right now ,

why i must flash that firmware?

my ze500kl have display all is grey or like this forum background color , not black , i think it is grey.

i already flash lollipop asus firmware but not change the display still all is grey , i flash asus firmware marsmallow 13.10.6.16 the display still all is grey.

i wish flashing csc image will fix my ze500kl display all is grey became normal again.

th
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
I don't know how to fix display. However, flashing partitions can be done from OrangeFox adb shell or from fastboot.

OrangeFox adb shell

adb push boot.img /dev/block/platform/soc.0/7824900.sdhci/by-name/boot
adb push sbl1.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/sbl1
adb push sbl1.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/sbl1bak
adb push emmc_appsboot.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/aboot
adb push emmc_appsboot.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/abootbak
adb push hyp.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/hyp
adb push hyp.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/hypbak
adb push tz.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/tz
adb push tz.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/tzbak
adb push rpm.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/rpm
adb push rpm.mbn /dev/block/platform/soc.0/7824900.sdhci/by-name/rpmbak
adb push NON-HLOS.bin /dev/block/platform/soc.0/7824900.sdhci/by-name/modem
adb push asusfw.img /dev/block/platform/soc.0/7824900.sdhci/by-name/asusfw
adb push system2.img /dev/block/platform/soc.0/7824900.sdhci/by-name/system

fastboot

fastboot flash boot boot.img
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash asusfw asusfw.img
fastboot flash system system.img

Note: system.new.dat or sparsed system.img needs conversion, either

https://github.com/xpirt/sdat2img

python3 sdat2img.py system.transfer.list system.new.dat system.img

or

https://github.com/anestisb/android-simg2img

simg2img system.img system2.img

to circumvent the above, you can copy zip to phone and just install from recovery - menu - install

adb push UL-ASUS_Z00E-WW-13.1010.1612.53-user.zip /sdcard
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
I don't know. the files extracted from 7-Zip can't be trusted. I think the proper way to flash RAW is from flashall_AFT.cmd only. sorry for misleading.

will brick device. files are not properly extracted from raw file.

for flashing CSC_Image_ZE500KL_v12_9_1_64_M1.3.22_OPEN_Phone-userdebug.raw

fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1bak.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpmbak.img
fastboot flash tz tz.img
fastboot flash tzbak tzbak.img
fastboot flash hyp hyp.img
fastboot flash hypbak hypbak.img
fastboot flash DDR DDR.img
fastboot flash ssd ssd.img
fastboot flash sec sec.img
fastboot flash aboot aboot.img
fastboot flash abootbak abootbak.img
fastboot flash fsg fsg.img
fastboot flash fsc fsc.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash factory factory.img
fastboot flash factorybak factorybak.img
fastboot flash asuskey asuskey.img
fastboot flash asuskey2 asuskey2.img
fastboot flash asuskey3 asuskey3.img
fastboot flash asuskey4 asuskey4.img
fastboot flash persistent persistent.img
fastboot flash asusgpt asusgpt.img
fastboot flash asusgpt1 asusgpt1.img
fastboot flash asusgpt2 asusgpt2.img
fastboot flash misc misc.img
fastboot flash keystore keystore.img
fastboot flash config config.img
fastboot flash asdf asdf.img
fastboot flash abootdebug abootdebug.img
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash persist persist.img
fastboot flash asusfw asusfw.img
fastboot flash modem modem.img
fastboot flash ADF ADF.img
fastboot flash APD APD.img
fastboot flash system system.img
fastboot format cache
fastboot format userdata

edit: after reading what this file does, this should work (still I don't know if these RAW files can be trusted, I prefer official sources #27)

fastboot flash all CSC_Image_ZE500KL_v12_9_1_64_M1.3.22_OPEN_Phone-userdebug.raw
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
feel unknown , after 5 minutes edl command python edl printgpt still on line this look

sahara - 32-Bit mode detected.

sahara - Firehose mode detected, uploading...
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
on miracle thunder 2.82 is stuck then failed connect to phone after success show phone model etc tehn give notice bootloader (i forgot, but like error maybe) ID 0003

,

so i still not try push .img files via fastboot or adb , but what is about system conversion ?

or maybe i must stop try to fix my ze500kl display all is grey , before something fatal error makes it cant do anything ?

i just want fix and not to get fatal error .
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
upsetly feel unknown

sahara - Firehose mode detected, uploading..

indication process like adb sideload not in there to get know how long it will be done to error or success.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
then leave it as is, no clue how to fix. maybe it's a hardware issue.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
yea everything is work , only display still all is grey .

so about flash csc image , i want try 1 files (recovery.imh) to flash via adb and fastboot , i will info it soon.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
all files extension is .img , no .mbn in .raw csc image ?,

do you have csc image for ze500kl ?, or where i can download ?

root@TworldBill:~/android# fastboot flash boot 33.boot.img

Sending 'boot' (32768 KB) OKAY [ 1.617s]

Writing 'boot' FAILED (remote: 'image is not a boot image')

fastboot: error: Command failed

----------

root@TworldBill:~/android# adb push 33.boot.img /dev/block/platform/soc.0/7824900.sdhci/by-name/boot

33.boot.img: 1 file pushed. 11.0 MB/s (33554432 bytes in 2.915s)

root@TworldBill:~/android#

via adb push look success , but if im boot it will bootloop , so if i do all 1 to 42 push via adb ,,, it will ok ? , no problem , no error , no fatal error ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
yeah I have noticed one can't extract CSC*.RAW file with 7-Zip, just forget about it. whatever extracted doesn't look like healthy files, that's why I said you will brick. Don't try this. fastboot has warned you for reason.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
arghhhh so extracted files from .raw wotj 7zip is unperfect file ?, so why u not give me how to completely extract .raw with perfect files? , what tools can extract .raw files ?

and about ze500kl csc image , where to get it ?, do u have it ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
I don't know how to extract. I believe (I don't know) these files may intended to flash with unofficial Asus Flash Tool. I have linked some CSC in post #28.

I don't own Zenfone device. I recommend not to try unless you got the edl tool working for emergency unbrick. for this, you need to pass the prog_emmc_firehose_8916_asus.mbn from cmd line, see post #14. not sure it will even run on 32-bit PC though.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
so its like program running on OS , GPT use 64 or 32 like apk can install 32 or 64 on ze500kl

,ok thanks alot for any respon from yoou alexcs in this post so appreciated.

and i believe to flashing csc image or emmc dump files not stop just because the computer media is 32bit, the natural logical catch from list all partitions in ze500kl can show it , and its posibble to backup and restore , the problem is how to get csc image universal flashable.

i stop this post .
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
as suggested in post #6 once you have created a full dump off your current phone partitions, you have good base to unbrick. EDL mode is always working and can't be broken. it all depends on the firehose programmer.

without this failsafe backup, I would not go any further.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
dear alexcs,

so this filr prog_emmc_firehose_8916_asus.mbn ( https://androidfilehost.com/?fid=11410963190603859555 ) is loader to makes edl program is work to read amd do backup all [artitions ze500kl ?,

via this command python3 edl wl rom --loader="path/to/prog_emmc_firehose_8916_asus.mbn" <- where file backup in hardisk ?, and what name it will saved ?

by the way there have apk have name backup and restore can backup and restore smartphone partitions , i dont know those apk will success backup and restore or no.

may you check and analysis this apk https://www.apkmirror.com/apk/wanam/partitions-backup/ .

i will try do backup via edl using that .mbn loader after get more your replay.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
still feel unknown, i dont like waiting feel unknown , command edl rl or wl makes me wont wait so i do ctrl z.

how do backup all partitions from adb pull method ?, should i add .img ?

adb pull /x/x/x/boot /x/x/x/boot.img or how to do right method?

i feel weird about edl mode , edl mode is for if recovery or fastboot not work ?, but when recovery and fastboot is fine , why edl mode so weird it is can use or no ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
zenfone or maybe same like another phones... EDL Mode only fully work if the pineout hardware get unplug , because this reason why edl mode with miracle box or edl program linux is connect to edl mode port 9008 qualcom (qualcom driver phone) is stuck .

youtube-dl -f 22

so no way out to use edl mode without pineout hardware (edl) first .

dear john still be johndoe.

the posible backup and restore phones partition if cant touch the hardware is only by software method (adb recovery/shell or fastboot)

so how ? to flashable any files from edl mode to restore without edl mode ?

or how backup and restore emmc with adb or fastboot ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
it's not about the backup, it's about unbrick later. cd into target directory on harddisk, then start the backup process. a new directory rom will be created. inside there will be multiple files created, one file for each partition. there is no waiting time, everything must work immediately as soon as phone is connected in EDL mode. the backup process will show you progress bar.

if the loader doesn't work for backup, it won't work for unbricking, too.

any other backup method is pointless, as I stated without working EDL there is no way to restore backup in case of brick.

EDL mode can be achieved with different methods. the test point method is explained in post #2. if you can see main - Device detected :) the phone is connected in EDL mode already, no need for test point method.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
?

how many i give results any edl try in this thread ?, after any command python3 edl printgpt , python3 edl --serial , python3 edl rl bla bla , python3 edl wl bla bla , all this command show device connected but in bottom there is no any moving progress, and my cpu led working progress indication too not show beep light , not like when in adb shell do command to show all phone partitions, the command showing all partitions, but in edl mode to do command show all partitions , i cant see whre all partitions showing in edl mode ?

if the loader is not right , cmon give me anything what i need to do backup ze500kl via edl mode, i will show you any effects results by screenshoot to you .
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
I don't know what is the issue. maybe bad drivers, maybe usb-port on PC, maybe usb jack on phone, maybe wrong cable, maybe wrong firehose file, or maybe the tool is broken or unsupported on 32 bit PC.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
brb for final conclusions
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
final conclusion is EDL program is not stable developer to use for all smartphones , even in edl program can found many loaders and can detected phone model , but the true edl program nuss something on reality mode implementation for smartphones model , this edl program is same with another program made by teorical how to work by front case .

go to deep edl program like another program just same is just can use front how it can use for work , like adb , fastboot , one click method , the program cant fight with smartphone company who makes the smartphone model with specification method not same with other in deep implementation how it can work ,

https://github.com/bkerler/edl/issues/59 .

so it is still not imposible to do any deep method implementations to any smartphones model .

just need realita experience and make it true to program how it can use and works .

if just theorical it maybe success and still unsuccessfull ., like how to decrypt code in war .

smartphone made for money , it is normal they protect it to not easy broke their black marketing code if the phone like magic in one day became fake broken .

sadly to many people think they phone is can not use again because go to any read tutorial still can make the phone can work again .

but people can make their phone always good until new update about hardware update to works normally.

if there no any hardware update , the phones still can safe from fake broken by do care with adb and fastboot to dodge any hit like virus can made the phone under fake broken .

my ze500kl is not hardware issue what makes my ze500kl display all is grey.

there have softwarre got wrong setting so my phone display all is grey , i dont understand what software handling display , my lcd touchscreen full working , just the display still all is grey .

the easier logic if my ze500kl have hardware issue on display , offcourse it will domino to another function on lcd use for .

like hw or sw mode in build.prop can make efect in video results, or imei is gone etc .

arghhh i am so feel dispointed , million result by search engine showing labyrin bad how .

if people have much money problem fake broken will make them buying new phones .

but me cant buy new phone .

all is done here .
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
you need to find working firehose programmer especially for your phone. these loaders are signed.

there is a collection here (1, 2)

https://xdaforums.com/t/4383255/post-86321813
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
i will try it all files available to download , 2 from all links i already use as edl program loader before u mae the post (hang) , forgotedly i am forgot to download edl program live dvd , so i can use version method deteced 32/64bit via bios sata mode.

argh soon to update part final conclusion.

i have question u not answer about do you already tested edl program for edl mode to asus zenfone (model?) ?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] alecxs:
I don't own any Asus device.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
by the way there have female member in ur team?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] letm2d:
all downloaded loaders is same status stuck/hang

one sample results (as all downloaded loaders u give)

(my_env) root@an:~/Documents/edl# edl rl dumps --loader="tmp-l/Qualcomm_Factory_Loader_MSM8916_Asus.mbn" --skip=userdata --genxml

Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.

main - Using loader tmp-l/Qualcomm_Factory_Loader_MSM8916_Asus.mbn ...

main - Waiting for the device

main - Device detected :)

sahara - Protocol version: 2, Version supported: 1

main - Mode detected: sahara

sahara -

------------------------

HWID: 0x007050e100290014 (MSM_ID:0x007050e1,OEM_ID:0x0029,MODEL_ID:0x0014)

CPU detected: "MSM8916"

PK_HASH: 0xcc3153a80293939b90d02d3bf8b23e0292e452fef662c74998421adad42a380f

Serial: 0x08bdc903

sahara - Protocol version: 2, Version supported: 1

sahara - Uploading loader tmp-l/Qualcomm_Factory_Loader_MSM8916_Asus.mbn ...

sahara - 32-Bit mode detected.

sahara - Firehose mode detected, uploading...

someday i will try live dvd (event i should do hardware pineout , i cant do this till can have new one)

.
[Galaxy Ace S5830 General] RDS5:
This phone is quite old and has nearly no software support in 2023, thats because its armv6.

However, I still think its unfair that people who want to mess with their galaxy ace have to go through archives and archives just to find the files.

I have decided to make an all in one guide, complete with the links, to install android 4.4 kitkat (latest version this phone supports) from scratch, with the most up to date rom it supports. (CM11 Linaro)​

First, a warning: You shouldn't trust any of this software on your main devices. Android 4.4 is outdated to an unimaginable level, and is riddled with security hole after security hole. Please, if you value your security, do not rely on any of this as daily driver. Also, for any of the windows executables, as they come from sources of "dubious quality" (aka. random forum post from 10 years ago, leaked software from samsung) and require UAC administrator rights, you should not be running this on your main computer.

I haven't tested with virtual machines, but those might work too.

Here are some requirements:

Windows 7 (8.1+ doesn't recognize msm7227 download mode, even with samsung usb drivers)

Spare computer to run W7 on (don't run outdated software on your main computer!!)

A microSD card for the galaxy ace

A way to interface with that sdcard from your computer (on mine there's a slot for them, you can also get a cheap SD to USB adapter)

This archive of all the software: https://www.mediafire.com/folder/5v6kqf7dsqqyl/acearchive

Now that you have all that, we're going to reinstall touchwiz. (optional but recommended)

0. Get into download mode (VOLDOWN+HOME+POWER)

1. Open odin 4.38

2. Click on "OPS" and select the cooper_v1.0.ops file

3. Check the "One Package" box and select the stock rom you downloaded OR the one that comes with this archive (make sure your baseband matches! i didn't check but it ended up working for me)

4. Click start, wait for the phone to finish and then complete setup

Next, we're going to install cwm recovery through odin.

1. Get back into download mode

3. Select "cwm-recovery-ace.tar.md5" in the one package slot

4. Click start, wait for the phone to finish and boot into recovery mode (HOME+POWER)

Now, place the items within the sdcard folder in the archive into your sdcard (CWM-6.0.5.3 and the CM11 images)

Boot your phone into recovery mode and install the CWM-6.0.5.3 image (might be possible from stock recovery, but by using odin we avoid bricking things if anything were to go south) (DO NOT INSTALL CM11 FROM CWM 5, IT IS NOT COMPATIBLE!!)

Now, reboot back into recovery, it should now be CWM-6.0.5.3, and you should be able to flash CM11 from there.

There isn't a bootanimation on this version of CM11, and it doesn't come with Gapps, so just be aware of that. (you can look for other ones, but its kinda hard to find.)

Hope this guide helps anyone who doesnt want to spend hours looking through archives and trying different combinations of software to get this 10+ year old phone booting!
[Galaxy Ace S5830 General] Oreeeee:
Thanks for the tutorial. I flashed cm-11-20151026-UNOFFICIAL-cooper.zip and the phone works great, without any non-working Google Services. The only issues I've seen is that the browser crashes, but that would probably get fixed by sideloading another browser, and home button not working. But the hardware is underpowered a bit and battery runs out quickly, due to combination of the battery being old and the ROM being Android 4.x (something based on 2.3.x would be more battery efficient). Now I'm gonna experiment with compiling some Linux stuff to armv6, maybe even trying to chroot.
[Galaxy Ace S5830 General] ie8yq:
It's heartwarming to see that someone still cares about that phone. I remember installing custom roms on it back in 2010s, it was so simple compared to modern smartphones. The hardware was underpowered though
[XPERIA X1 General] Evostance:
This is how I SE WinMo customisation.

Its windows mobile with panels. But you can choose panels.

However all these panels are, are essentially interative desktops...

To make the panels seem more unique, is there anyway to remove the start menu?

I.e. Say someone wanted to make a iPhone panel. You could have your phone run like the iPhone without the start menu

If someone wanted to make a vista panel it could look like vista without the start menu at the top

Any ideas?