yashsingh1/xdaforums huggingface dataset:
[Android General] Renate:
To read everything you just need edl /r /u0 bigfile since accidentally reading 64 GB is not so bad.

To write a single partition you can edl /w /pboot mybootfile.

But if you forgot the /p then edl /w mybootfile would overwrite the MBR and partitioning with garbage (if we didn't prevent that).

To write everything you just need edl /w /u0 /s0 /c0 bigfile.

On UFS by "device" we mean a LUN which is a logical device.

No single read/write operation can span multiple LUNs.
[Android General] Renate:
Good

The Sahara protocol can easily get out of whack, you need to reset and restart the conversation.

You always need to load a loader first to switch to Firehose protocol.

The newer Sahara 3.1 does not give any secrets away. You need to say edl /l /qbc.

But you might as well say edl /lprog_firehose_ddr.elf /qbc

"Wiping" is reformatting the partition. Edl.exe does not do any formatting.

You could erase the userdata partition, but that would leave it without a file system which causes bootloops.

HWID identifies the Qualcomm processor, not the phone.

With the new Sahara 3.1 you can not directly query the HWID or PK hash of your device.

I left the default in Edl.exe to still try to get it even when it sees that it's 3.1 in case it works.

When it fails, you must use the "never mind" quirk code of /qbc to tell Edl.exe not to ask.

Since you have a working Firehose loader you don't really need to find the HWID.

Also, you could run qcomview.exe /p prog_firehose_ddr.elf and find the PK hash.

Whether QFIL itself would do it or a newly rebooted device would do it itself, I don't know.

QFIL goes through your device like a bulldozer, so unless you edit the XML it could probably reformat userdata.

QFIL is designed for factory use on blank devices (and pretty silly at that).

Edl.exe is designed to easily read/write a few partitions.

You could write a makefile or a batch file to write all the partitions

Doing anything might regenerate encryption keys for userdata, I'm no expert on any of that field.

Are you worried more about losing photos or application data or general setup?
[Android General] king of the lone woods:
Hi Renate,

Gracious & wish you a good day

I need some guidance to restore my user data,repair my phone stuck in bootloop

Here's the issue:

ADB usb authorization & bootloop issue,data recovery needs guidance

Good wishes to all, I have a vivo y71 model mobile (rigged by company),that it says 16gb internal,but even the fresh factory version shows

xdaforums.com

I used QFIL to backup my data,thanks to few articles found in Hovatek & some

But i just need clear assurance way to restore its good state (I read your reply where you said "better backup data while phone in use,decrypted")

Please help me in a more easy way without much "config" (i am new in this topic)

Extra rant:lost almost 2 months cause of this issue (whole year cause phone in first,hdd in laptop died) regret why "computer science" community became ungrateful,greedy,non-sharing of any era (all credits to arrogants at big tech,foundation influence the "trickle down" of *dark triads of psychology) and that whole "MIT" vs Unix of perfection vs simplicity..

Instead GNU not being Unix(while having name itself) steal the credible works of many to few arrogant work..

Goes to crush competitions,favor monopoly greed as big tech as Microsoft & few.. damn

Thanks in advance 😇

Wish all be well 😃🌟✨🙌

09.12.2023 04:29 pm ist
[Android General] Renate:
Three backup philosophies:

Backup your stuff as individual files with the system running normally and userdata decrypted.

Backup your entire flash as a single file (eMMC) or a half dozen files (UFS). You can restore your device to a restore point, then use #1.

Backup userdata as a single file. There's no guarantee that restoring this will work if the encryption keys have changed somehow.
[Android General] Renate:
There's really no use in copying slots around.

If the other slot is valid and you want to try it you can just set active slot in fastboot.

The less you flash, the less you have to fix.

The /v flag in edl.exe is really only useful when things go wrong.

I try to keep clutter to a minimum.

Spoiler content hidden.

Truncation is only helpful with boot images or ELF files in partitions.

Now that Android has starting putting stupid footers on images much of the utility is lost.

So instead of just copy/saving a 32 MB boot image we have 128 MB images that have 96 MB of zeroes in them, followed by a dozen bytes of stupidity.

This device has a "super" partitions which is where "system" and "vendor" for both slots is.

Using the markup of [code][/code] makes things prettier.
[Android General] Juglar:
I first tried "set-active-slot a" (or similar) in fastboot, but it was rejected by "locked bootloader", and I've been warned that unlocking the boot loader or re-locking it again wipes userdata, which is what I don't want to risk.

Please, do you (or any other kind member) know any way of doing it (unlocking- relocking bottloader) while keeping my userdata?

Ok, but I've seen that it adds some more info to the partitions "type" which I don't know if may be useful.

So do I try not to clutter, but I'm learning to use this forum. And I prefer to risk cluttering than hiding anything important.

Thanks,

Do you (or any other kind member) know how to insert those in the super partition, please?

Does the QFIL tool (or other flashing tool) handle this insertion from the stock rom to the super partition?

Since Nubia publishes their stock roms in update format (zip), is there any way to convert them to a format which QFIL or other flashing tools in EDL mode could use?

I'll try to learn to use it. Actually, I've just posted a question asking where I could find the guide or instructons to use this forum editing tools.

Thanks again !
[Android General] king of the lone woods:
Hello,

I think you didn't see my reply to your answer at my post,

Still i am making this to get to you,please read once you're free

I done backup my userdata & partitions,

Now i just need some positive assurance,guidance to restore them while fixing it from a bootloop

Thanks in advance 😇

Wish you well 😃🌟✨🙌

12.12.2023 11:15/6 pm ist

Rf sat 5:16p
[Android General] Renate:
Yeah, that's the problem.

If you have everything backed up include 6 big files of complete LUNs then you should be on safe ground.

You should be able to get back to where you are right now, that is, bootlooping.

If you have good boot images then fastboot boot boot.img is good because you can try stuff without flashing.

Then there is the question, what kind of boot loop do you have?

If you disabled your launcher, that is the most trivial boot loop.

If you mashed half a dozen partitions, that's something else.
[Android General] king of the lone woods:
Huh,well,

When i roamed over a month to search about this topic,i didn't get this cause of dump/write,since i tried "backup,restore" .. terms are getting cconfusing

Ok so,i got the userdata partition,

Then i got the other partitions later

Now let me explain the situation fully,

My phone is a dummy worse one made,it says 16gb,but internal shows <8gb when i last time had same issue (hope less with adb,February),Afyer fresh stock flashed from service center

This October,as usual,phone memory fills itself automatically (latest rom made me can't find,delete "." Hidden files as thumb caches),

Had some tabs in native browser present,

I just left home doorsteps,heat by sun light,then its bootloop (i had few times,but then those times,i just put them near fan,to let it cool,later it on itself)

This time as usual ram memory ran out.. i tried the method in outside which backfired & didn't helpful (my rush to outside 😫)

So yeah,i can get into fastboot,recovery modes with key combos,then it won't get into home page

Now feels like "freeze" it some time is the next way,if i didn't knew this thread works (i put another thread after learned about qfil,but i didn't update any)

Pardon for my long talk 😇

13.12.2023 01:32 am ist

17+mar,rf yda 11:59p
[Android General] Renate:
What does df show you?

Hardware problems can cause software corruption.
[Android General] Claws_77:
for people who want to know if their storage is emmc or UFS, try gsmarena.com with your phone model no.
[Android General] Claws_77:
my phone is redmi note 6 pro, india. i am trying this method, found firehose files in one of the tulip global rom

prog_emmc_firehose_Sdm660_lite.elf--- and this-- same error

prog_emmc_firehose_Sdm660_ddr.elf --used this

got this error, help!

device manager shows qualcomm HS-usb qdloader 9008 (com10)

qpst configuration shows-- in port section

port : com10

state :enabled

label: com10 (auto add)

phone: no phone

link: usb

serial no: *blank*

qc serial no: *blank*

in active phones section

phone: unknown

esn: no esn

phone no: *blank*

banner: unknown

port: com10 (com10 (auto add))

is there any way to flash twrp recovery, i am very familiar with this, and can backup my userfiles as well.
[Android General] Renate:
I don't know QFIL, I don't use QFIL, I don't like QFIL.

If you're using my software, I can be more helpful.

It may be that you need to long power reset your device and try again.

[sarcasm]

Or it may be that interplanetary time is standing still.

Why does it keep on saying "2024-02-20 01:31:20.203"?

Why doesn't it mention that it's Tuesday?

And where's the weather forecast?

[/sarcasm]
[Android General] Claws_77:
i live in a different time zone. UTC +5:30

downloaded elfview, qcomview, edl, ubi, zadig from your android page.

my phone is redmi note 6 pro india, phone details

here are the results

PS: In two days the phone condition has gotten worse, from being able to get into fastboot to no response on pressing power button.
[Android General] Renate:
You still have the Qualcomm virtual port drivers installed.

Install the WinUsb driver using Zadig.

If /lwhatever.elf doesn't work, don't bother with any Firehose commands (/i, (/g, /r, /w) since you're not in Firehose.

(And results wrapped in [code][/code] please.)
[Android General] Claws_77:
View attachment 6070932
[Android General] Renate:
Looks good so far.

Just always check in "Ports" to make sure that you have no wacky ports there, "Com 23 Qualcomm".

We can see it looks right, but opening under EDL is the test.
[Android General] Renate:
Oops, sorry. You got me confused by putting your response in my quote.

:(

Yes, your device needs authentication. I'm not sure if the Python bkerler EDL client can do that.

(The Python EDL client can use the Zadig WinUsb drivers you currently have installed.)

You probably need to go back to the Qualcomm virtual com port driver and software specifically for your device.

Sorry.
[Android General] Claws_77:
thank you for everything

if you know any guides for new software? HELP!

do you mean miflash tool - it is useless, becoz requires previously adding your account to MI unlock-- impossible now due to sudden brick

do you mean qpst/qfil?

do i have to uninstall zadig?

can i just flash recovery- twrp, so i can backup my data, and do a fresh install?
[Android General] Renate:
You'd need to reinstall the Qualcomm drivers.

If your TWRP can decrypt userdata, sure, that would work.

If you still have access to fastboot and you're unlocked, that will work.
[Android General] Claws_77:
C:\Users\sunan\Downloads\phoen\edl-master\edl-master>python edl.py --loader=C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf
Capstone library is missing (optional).
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Using loader C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
Version 0x2
------------------------
HWID: 0x000cc0e10000000 (MSM_ID:0x000cc0e1,OEM_ID:0x000,MODEL_ID:0x0000)
CPU detected: "SDM636"
PK_HASH: 0xa7b8b82545a98eca23d68d1b5828264903441bdef0cd57e3c370
Serial: 0xbae2fa

sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf ...
sahara - 64-Bit mode detected.
sahara - Firehose mode detected, uploading...
sahara - Loader successfully uploaded.

C:\Users\sunan\Downloads\phoen\edl-master\edl-master>python edl.py printgpt --memory=emmc
Capstone library is missing (optional).
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected :)
main - Mode detected: firehose
main - Trying to connect to firehose loader ...
firehose
firehose - [LIB]: !DEBUG! rsp.data: 'bytearray(b'<?xml version="1.0" encoding="UTF-8" ?>\n<data>\n<log value="Chip serial num: 467295 (0xffffffff)"/>\n</data><?xml version="1.0" encoding="UTF-8" ?>\n<data>\n<log value="Supported Functions: program configure nop sig firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase "/>\n</data>')'
firehose - TargetName=MSM8996
firehose - MemoryName=eMMC
firehose - Version=1
firehose - Trying to read first storage sector...
firehose - Running configure...
firehose
firehose - [LIB]: GetStorageInfo command isn't supported.
firehose_client - Supported functions:
-----------------
firehose
firehose - [LIB]: ERROR: SDCC Error 20 (2)
firehose
firehose - [LIB]: ERROR: Get Info Failed
firehose
firehose - [LIB]: ERROR: Failed to get info 1 slot 0, partition 0, error 2
firehose
firehose - [LIB]: storage_device_get_num_partition_sectors FAILED!
firehose
firehose - [LIB]: parseSectorValue could not handle start_sector value
firehose
firehose - [LIB]: ERROR: SDCC Error 20 (2)
firehose
firehose - [LIB]: ERROR: Get Info Failed
firehose
firehose - [LIB]: ERROR: Failed to get info 1 slot 0, partition 0, error 2
firehose
firehose - [LIB]: storage_device_get_num_partition_sectors FAILED!
firehose
firehose - [LIB]: parseSectorValue could not handle start_sector value

should i bother hiding chip serial no, and other info? @Renate
[Android General] Renate:
If it makes you feel better you can redact a serial number, (but never redact or fudge HWID or hash).

Apparently the Python EDL client doesn't do Xiaomi authentication either.

You need to be using something Xiaomi specific.
[Android General] Claws_77:
unfudged everthing

C:\Users\sunan\Downloads\phoen\edl-master\edl-master>python edl.py --loader=C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf
Capstone library is missing (optional).
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Using loader C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
Version 0x2
------------------------
HWID: 0x000cc0e100000000 (MSM_ID:0x000cc0e1,OEM_ID:0x0000,MODEL_ID:0x0000)
CPU detected: "SDM636"
PK_HASH: 0xa7b8b82545a98eca23d6e9105fb464568d1b5828264903441bdef0cd57e3c370
Serial: 0xbaec52fa

sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader C:\Users\sunan\Downloads\phoen\prog_emmc_firehose_Sdm660_ddr.elf ...
sahara - 64-Bit mode detected.
sahara - Firehose mode detected, uploading...
sahara - Loader successfully uploaded.

C:\Users\sunan\Downloads\phoen\edl-master\edl-master>python edl.py printgpt --memory=emmc
Capstone library is missing (optional).
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected :)
main - Mode detected: firehose
main - Trying to connect to firehose loader ...
firehose
firehose - [LIB]: !DEBUG! rsp.data: 'bytearray(b'<?xml version="1.0" encoding="UTF-8" ?>\n<data>\n<log value="Chip serial num: 4294967295 (0xffffffff)"/>\n</data><?xml version="1.0" encoding="UTF-8" ?>\n<data>\n<log value="Supported Functions: program configure nop sig firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase "/>\n</data>')'
firehose - TargetName=MSM8996
firehose - MemoryName=eMMC
firehose - Version=1
firehose - Trying to read first storage sector...
firehose - Running configure...
firehose
firehose - [LIB]: GetStorageInfo command isn't supported.
firehose_client - Supported functions:
-----------------
firehose
firehose - [LIB]: ERROR: SDCC Error 20 (2)
firehose
firehose - [LIB]: ERROR: Get Info Failed
firehose
firehose - [LIB]: ERROR: Failed to get info 1 slot 0, partition 0, error 2
firehose
firehose - [LIB]: storage_device_get_num_partition_sectors FAILED!
firehose
firehose - [LIB]: parseSectorValue could not handle start_sector value
firehose
firehose - [LIB]: ERROR: SDCC Error 20 (2)
firehose
firehose - [LIB]: ERROR: Get Info Failed
firehose
firehose - [LIB]: ERROR: Failed to get info 1 slot 0, partition 0, error 2
firehose
firehose - [LIB]: storage_device_get_num_partition_sectors FAILED!
firehose
firehose - [LIB]: parseSectorValue could not handle start_sector value

C:\Users\sunan\Downloads\phoen\edl-master\edl-master>python edl.py printgpt --memory=emmc

what does this mean? sahara - Protocol version: 2, Version supported: 1
[Android General] Renate:
It's not saying anything important. It actually means the version is 2.1

Unless you see 3.x, don't worry.

For my part, I'd like to know what all those useless lines with just "firehose" on them mean. :p

As I said, to continue you'll need to get some Xiaomi tool.
[Android General] SKAm69:
Is it possible to just extract the needed files from the /user-data or /sdcard? The problem is in data partition (stupid update of system app xiaomi System UI plugin), so restoring the whole partition is a problem. I just need my user files, thanks!
[Android General] Renate:
Your only hope is getting the normal system to run.

Because only the normal system can decrypt your data.

Do not under any circumstances "wipe" the data.

That will delete the decryption keys and your data is gone.
[Android General] SKAm69:
I'm not sure if it's even possible. I've updated a Xiaomi System UI plugin and the UI crashes and reboots one second after booting. And unlocking bootloader will case the data wipe anyway. I'm desperate

Edit: it's the infamous Xiaomi Feb 29th problem.
[Android General] espionage724:
I was wondering if the userdata partition could be pulled through EDL to a Linux desktop/host, and then opened up with a disk image mounter? As long as you know the password I figure it's just encrypted ext4 and Linux can handle decryption and mounting?
[Android General] Renate:
My knowledge on the details is poor.

I believe in older Android there was a single key to decrypt the entire partition.

I think now that different keys are used for each file.

The keys in either case are regenerated when needed through a convoluted chain of operations.

Since I sync my devices with my desktop on a regular basis with adbsync.exe (in the sig) I haven't had a reason to dig deeper.
[Android General] patrik996:
Anyone know where to find firehose/loader for this device?

HWID: 000ce0e1013a0ae8, JTAG: 000ce0e1, OEM: 013a, Model: 0ae8
Hash: 5ddeeac1a6d7b65d-0de1c91383478b3e-f133f23adf5af369-4f9283a69229d845-6b7b5aa0d7d54da0-aab8a2affb1113de (x3)
[Android General] Renate:
I don't see that hash anywhere.

Also, with OEM and model specified it doesn't look promising.

What is that thing anyway?
[Android General] patrik996:
All right, thanks anyway.

Pico 4 VR Headset

Qualcomm Snapdragon XR2

SXR2130P
[Android General] espionage724:
I'm very curious to hear all about whatever you're trying to do with that device!
[Android General] patrik996:
Just testing whats possible.

Just downgrading firmware would be a win but not looking good without a firehose file.
[Xiaomi Mi A2 / 6X Questions & Answers] amnher:
It seems not working i mean same 30and 60fps. Latest stock not unlockef
[Touch Diamond, MDA Compact IV Accessories] walshieau:
anyone know of a distributor with stock or stock arriving soon? Expansys reckon 01/08/08 and im not waiting that long...
[Touch Diamond, MDA Compact IV Accessories] someone1234:
thats the standard battery?

a quick google shows the earliest as 24th July. Don't you want to wait and see what this extended battery with replacement back is like?
[Touch Diamond, MDA Compact IV Accessories] walshieau:
hell no, the thinner the better....
[Touch Diamond, MDA Compact IV Accessories] someone1234:
yeah i agree.. but it depends on how much thicker the phone is and how bad the existing battery is. At least it won't look ugly with a big ass bulge like some of the other aftermarket batteries
[Touch Diamond, MDA Compact IV Accessories] richardirv:
Play.com have the standard battery for £14.99. Out on the 9th

I have 2 on order!! Hehe

Rich
[Touch Diamond, MDA Compact IV Accessories] zorba:
battery charging

How are you planning to charge your two extra batteries when you get them? I went through this on the Kaiser and it is kind of a pain to swap them out just to recharge them. Eventually I bought a third party charging stand with an external battery charger but, after two replacements that did not charge the battery, I gave up. Based on my three days with the standard battery, I would say it woud be a good idea to wait and get the dimensions of the extended battery. I have seen my battery getting drained in 3-4 hours (reminds me of the xda-flame).

Z
[Touch Diamond, MDA Compact IV Accessories] deCorvett:
Yes, but it's possible to make OEM-sized extended batteries... I'm carrying one on my Treo right now, just 25% more battery life.

Seidio does it., just wait.
[Touch Diamond, MDA Compact IV Accessories] chandrasekharm18:
iPower Pro PoGo

While on the road I'm using the iPower Pro PoGo to change my Diamond. I use an dual usb adapter that simultaneously allows charging and the use of the wired headset.

The PoGo is flat, 1/3" x 2" x 3 1/2", has a standard usb connector for the standard Diamond usb cable and it has at least 20 hours worth of extra charge. It fits nicely in my bag which I carry with me everywhere I go.
[Touch Diamond, MDA Compact IV Accessories] galinha:
www.expansys.pt

They have 80 .
[Touch Diamond, MDA Compact IV Accessories] kiowa79:
The vendor says:

Charging tips for iPod , Sony PSP , Blackberry (all models), Treo 600(s)/700(s), Moto RAZR (V3), Samsung , Nokia , Sony Ericsson phones and other devices that use a mini-USB charging port

So if it is only for mini-USB ports, how can you plug it into the HTC 11 pin connection? :confused:
[Touch Diamond, MDA Compact IV Accessories] MasK:
For charging/synching, the HTC 11-pin IS the miniUSB port.

The extra features that the HTC 11-pin connector (aka extUSB) is that it transports audio as well.
[Touch Diamond, MDA Compact IV Accessories] h4waii:
ExtUSB is one reason why I am HTC hardare fo' life.

But yes, anything that can be charged via USB and MiniUSB, can be charged via ExtUSB. Heck, I charge mine with an old Blackberry charger that is 5v @ .5mAh instead of 1mAh.
[Touch Diamond, MDA Compact IV Accessories] richardirv:
I hadn't thought about that but It really isn't going to be often that I will need more that one battery, I am only getting them for when I am out walking and I know its gonna be a long day, nice to have spares! and I will just charge them in the phone the night before!!

I will defiantly be getting an extended one if they ever come out too but for £14.99 each now you can't knock that!!

Rich
[Touch Diamond, MDA Compact IV Accessories] sandervanzijl:
got a message from seido.

they will have diamond stuff the end of july. so hopefully the will have an oem battery with more capacity.
[Touch Diamond, MDA Compact IV Accessories] kiowa79:
What I meant is that phisically you cannot connect a standard mini USB charger into the Diamond's 11 pin input. As the vendor says the do not provide an adaptor for HTC devices, so maybe he is using some extra stuff purchased somewhere.