yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] alecxs:
your bootloader is locked, therefore any harmful cmd (such as flash, erase, format) is forbidden and has no effect. (btw phone gave you warning you mixed up cmds format with erase)

fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache'
FAILED (remote: 'device is locked. Cannot erase')

I said on formatting, no data remains (nothing survives) because it is overwritten by new file system.

(Maybe on quick format some data may survive, but not provided by file system and therefore invisible/non existent, like free disk space.)
[Android Q&A, Help & Troubleshooting] wenyendev:
I was talking about fastboot erase cache that worked on another bootloader-free device.
[Android Q&A, Help & Troubleshooting] alecxs:
then you are lucky your phone...
[Android Q&A, Help & Troubleshooting] wenyendev:
fastboot flashing unlock produced the following error.

View attachment 5797151
[Android Q&A, Help & Troubleshooting] alecxs:
What brand/device model/android version you are trying to unlock?

adb shell
$ getprop ro.build.fingerprint
$ getprop sys.get_unlock_ability
$ getprop ro.oem_unlock_supported
$ getprop ro.oem_unlock_allowed
[Android Q&A, Help & Troubleshooting] wenyendev:
It returned

OnePlus/OnePlus2/OnePlus2:6.0.1
[Android Q&A, Help & Troubleshooting] alecxs:
as getprop returned nothing, you can try generic unlocking method to force oem_unlock_allowed offline (fastboot oem unlock required)

https://github.com/bkerler/edl#for-generic-unlocking

or unlock bootloader by hexpatching devinfo partition directly (you can use bkerler/edl for this)

https://xdaforums.com/t/bootloader-...evices-devinfo-partition-modification.4100897

Beware: Unlocking bootloader forces factory reset. even in case you unlock bootloader without wiping data, encryption might break anyway, what makes data effectively unreadable.
[Android Q&A, Help & Troubleshooting] wenyendev:
It is weird in the sense that if bootloader has been locked, then how the recovery (TWRP) could be installed by fastboot flash recovery recovery.img ?
[Android Q&A, Help & Troubleshooting] alecxs:
on locked bootloader fastboot flash is forbidden. either TWRP was flashed from fastboot in unlocked state or flashed on locked bootloader with different method (either via dirty c0w exploit or via EDL mode with flash tool)

I have done similar on Cubot King Kong on Android 7. This is possible because dm-verity isn't properly enforcing signature of recovery partition due to a bug.

on such ancient device running Lollipop there exist simply no dm-verity at all.

A Look at Marshmallow Root & Verity Complications

Learn about the newer complications that verity and Marshmallow bring to rooting locked-down devices.

www.xda-developers.com

you own rooted OnePlus2 with TWRP recovery, what you can do is pull devinfo partition and flash it to locked OnePlus2 (that's where the bootloader lock state is saved).
[Android Q&A, Help & Troubleshooting] wenyendev:
Thanks for your advice.

But after adb pull device-info partition,

adb pull /dev/block/mmcblk0p9 device-info.img
/dev/block/mmcblk0p9: 1 file pulled, 0...ipped. 0.2 MB/s (1024 bytes in 0.006s)

flashing it in fastboot mode failed. Here below was the detail.

fastboot flash devinfo device-info.img

Sending 'devinfo' (1 KB) OKAY [ 0.048s]
Writing 'devinfo' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed

Apparently, a locked bootloader did not permit flashing device-info.
[Android Q&A, Help & Troubleshooting] alecxs:
locked bootloader does not permit fastboot flash cmd at all. kindly read the instructions

https://github.com/bkerler/edl#for-emmc-flash

edit: can you flash it from fastboot on its origin device? it's unclear that devinfo is locked/unlocked (you could upload zip so we can double check with HxD editor)
[Android Q&A, Help & Troubleshooting] wenyendev:
But you just wrote

"you own rooted OnePlus2 with TWRP recovery, what you can do is pull devinfo partition and

flash it to locked OnePlus2

(that's where the bootloader lock state is saved)."
[Android Q&A, Help & Troubleshooting] alecxs:
Yes. I have linked two different flash tools in post #21. both requires device booted into EDL mode.
[Android Q&A, Help & Troubleshooting] wenyendev:
Do you mean flashing devinfo partition in EDL mode?
[Android Q&A, Help & Troubleshooting] alecxs:
yes but you need modified fastboot for this (command not supported on all devices)

Fastboot_edl-v2.zip

sometimes it's sufficient to press both Volume Buttons + while connecting usb-cable (device powered off)

another method is deep flash cable (search for how to DIY)

if no methods work you need to short-circuit test point to GND

dirtyc0w exploit should also work (no EDL)

https://xdaforums.com/t/root-tool-dirtycow-apk-adb.3525120
[Android Q&A, Help & Troubleshooting] alecxs:
on some devices adb is supported

https://xdaforums.com/t/how-to-boot-into-edl-mode.4398479

adb reboot edl
[Android Q&A, Help & Troubleshooting] ze7zez:
"This" meaning what model?
[Android Q&A, Help & Troubleshooting] alecxs:
are you sure you meant TWRP?

Question already answered here

https://xdaforums.com/t/question-fastboot-oem-unlock-boot-into-recovery.4531349/page-2

please continue your thread to same issue as already pointed out several times. it makes no sense to conceal information that has already been given to solve your issue.
[Android Q&A, Help & Troubleshooting] wenyendev:
Thanks for your reply to @ze7zez.

Yes, it booted into Twrp recovery.

Nope, issue unresolved, bootloader remained locked.
[Android Q&A, Help & Troubleshooting] wenyendev:
Hi there,

I installed edl: https://github.com/bkerler/edl#for-generic-unlocking

in order to unlock the bootloader of a Qualcomm device.

All requirements were satisfied.

I booted the device into edl mode by adb reboot edl.

When I ran

edl modules oemunlock enable

It returned

Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
------------------------
HWID: 0x009400e100000000 (MSM_ID:0x009400e1,OEM_ID:0x0000,MODEL_ID:0x0000)
CPU detected: "MSM8994"
PK_HASH: 0xcc3153a80293939b90d02d3bf8b23e0292e452fef662c74998421adad42a380f
Serial: 0x0209e3d5
sahara - Possibly unfused device detected, so any loader should be fine...
sahara - Possible loader available: /Users/wenyuan/Desktop/Android/adb/edlclient/../Loaders/qualcomm/factory/msm8994/009400e100000000_dbbd98bdc71d24ce_fhprg_peek.bin
sahara - Possible loader available: /Users/wenyuan/Desktop/Android/adb/edlclient/../Loaders/xiaomi/009400e100000000_57158eaf1814d78f_fhprg_peek.bin
sahara - Possible loader available: /Users/wenyuan/Desktop/Android/adb/edlclient/../Loaders/cyanogen/009400e100000000_b0d6c9fc8d2cf585_fhprg_peek.bin
sahara - Trying loader: /Users/wenyuan/Desktop/Android/adb/edlclient/../Loaders/qualcomm/factory/msm8994/009400e100000000_dbbd98bdc71d24ce_fhprg_peek.bin
sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader /Users/wenyuan/Desktop/Android/adb/edlclient/../Loaders/qualcomm/factory/msm8994/009400e100000000_dbbd98bdc71d24ce_fhprg_peek.bin ...
sahara - 32-Bit mode detected.
sahara - Firehose mode detected, uploading...
Traceback (most recent call last):
File "/Users/wenyuan/Desktop/Android/adb/./edl", line 391, in <module>

base.run()

File "/Users/wenyuan/Desktop/Android/adb/./edl", line 370, in run

if "load_" in mode:

^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable

What could I do to solve this issue and properly unlock the bootloader?

A side question: what is the function of "fhloaderparse" in fhloaderparse examples Loaders?

Thanks in advance.

May you need any further information, please do not hesitate to ask me.

Regards,

Wy
[Android Q&A, Help & Troubleshooting] Renate:
Keep it simple.

Specify the Qualcomm factory loader.

Try to print the GPT.

Then you know that you have a good Firehose connection.

Then try doing all these things that get you a Python stack trace. :p
[Android Q&A, Help & Troubleshooting] wenyendev:
It's a Oneplus2.
[Android Q&A, Help & Troubleshooting] alecxs:
thread moved.
[Android Q&A, Help & Troubleshooting] wenyendev:
Nope, it's a wholly different topic... It's made to solve issue in edl.
[Android Q&A, Help & Troubleshooting] kskksks:
Mine says: UsbDkController' is not recognized as an internal or external command,

operable program or batch file.
[Android Q&A, Help & Troubleshooting] wenyendev:
I worked the whole afternoon and evening on edl, and feel fully justified to post this thread.
[Android Q&A, Help & Troubleshooting] wenyendev:
To judge how to treat a thread (to move it, merge it, delete it, etc.), I believe, is moderators' job, not yours.
[Android Q&A, Help & Troubleshooting] Renate:
Oh, you didn't mention that.

It's probably blowing up on OP security.

Try the advice in post #2.
[Android Q&A, Help & Troubleshooting] alecxs:
well, you could just have asked in your other thread and saved half a day... :coffee:

I will answer tomorrow after threads are merged.
[Android Q&A, Help & Troubleshooting] wenyendev:
I believe that these are two different topics

- this thread aims at solving issue so

I could use edl

;

- the one you mentioned was a question to answer "Why did adb pull /dev/block/mmcblk0p43 43.img fail to pull userdata partition?".

Even if you answered this question, I could still not use edl.

It is as simple as that.

Furthermore, your answer ("adb pull /dev/block/... requires 'adb root") did not solve the issue -- "adb pull" was inapplicable as previously.
[Android Q&A, Help & Troubleshooting] Bill720:
Folks, after much deliberation, I've merged all of the duplicate posts from the unnecessary second thread that was created back into this one. The reason for this is that, as best as I can tell, the end goal is still the same, so it makes more sense to have it all in one place.

Secondly, it is not made clear what device this is actually for. There are two mentions of the OnePlus 2, so, is that it? If so, is there any reason why this thread was posted where it was instead of the OnePlus 2 section?
[Android Q&A, Help & Troubleshooting] wenyendev:
I am amazed how personal arbitration weighed over the rules of the forum.

https://xdaforums.com/t/how-to-tell-if-data-partition-is-encrypted-by-adb-command.4528429/
[Android Q&A, Help & Troubleshooting] alecxs:
off-topic

already explained. it works only like this (and you did something of this before):

yes, the topic may different. but the reason for linking that post (with the words "as already pointed out several times") was not the topic itself. let me point you to reason one more time. it applies to all members and threads, regardless of the topic (from the link):

finding and parsing the proper firehose programmer (matching your device) is just single minor issue on your way to unlock bootloader from EDL mode, and belongs to this thread.

What will be your next question after python edl modules oemunlock enable?

Why Fastboot oem unlock failed to unlock bootloader?

How to patch devinfo partition?

I have already asked you to share devinfo as zip file on Jan 2, 2023 (so I can double check)

The script searched for loaders in its own Loaders directory and found possible matching firehose programmers. it tries to iterate about all (4x) four results. However, the script has probably a bug, so it doesn't work.

with this function one can add own firehose programmer files into the Loaders directory. But as the script seems broken this would be probably pointless.

as workaround you can either pass your own firehose programmer from cmd line directly (as suggested by @Renate #36)

python edl --loader="path/to/prog_emmc_firehose_8994_lite.mbn" modules oemunlock enable

or you start from scratch, delete everything and use latest official release instead of the master build.

git clone -b 3.52.1 https://github.com/bkerler/edl.git
git submodule update --init --recursive
python3 setup.py build
sudo python3 setup.py install

(please note usage is slightly different, the old python script has suffix .py)

python3 edl.py --loader="path/to/prog_emmc_firehose_8994_lite.mbn" modules oemunlock enable
[Android Q&A, Help & Troubleshooting] wenyendev:
I encountered errors while executing the codes here.

fhloaderparse newstuff Loaders

fhloaderparse examples Loaders

1. Convert own EDL loaders for automatic usage​

After

- making a subdirectory "newstuff" under "adb" (I cded to "adb" and dropped "edl" files in "adb");

- copying "Loaders" and also "oneplus" under "newstuff";

I typed fhloaderparse newstuff Loaders.

It returned

-bash: ./fhloaderparse: No such file or directory

2. Install EDL loaders​

I created "examples" folder and dropped all the loaders in "examples".

After executing fhloaderparse examples Loaders,

the same error occurred

-bash: ./fhloaderparse: No such file or directory

What could I do to solve these two problems?

Thanks in advance.
[Android Q&A, Help & Troubleshooting] alecxs:
the script has moved with commit d9532b5 and now it's in Tools. you don't need this. it doesn't work for me either.

(btw the usage examples are the exact same command)

$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders
[8525, TyTN, MDA Vario II, JasJam ROM Development] sapphire_pro:
Hello,

where can I download the latest Version of HTC Album? (CAB)

Edit/Delete Message
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
Here you go man:

http://xdaforums.com/showthread.php?t=425694

fresh from the opal builds
[8525, TyTN, MDA Vario II, JasJam ROM Development] sapphire_pro:
Thank you but on 4shared there is a Opal Album 2.5 (But just in rar and not in cab).

http://www.4shared.com/file/68753396/59cd7596/HTC_Opal_Album__2518191330.html?s=1

So the version in the link you posted is the latest one, isnt it?
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
not sure, after the opal build there was a blackstone build that would be later. if we can find a album from blackstone rom that would be the latest. ;) I'll look some more
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
ok here's the latest cabs from the latest official blackstone (Touch HD) rom.

http://xdaforums.com/showpost.php?p=2859650&postcount=2

i don't know if they will work with Hermes so you will need to test them :)

lemme know and maybe i'll start ripping and cooking them in. ;)
[Redmi 9 / Poco M2 Questions & Answers] XalyLodak:
Hi,

I have a problem, my phone Redmi 9 (lancelot) doesn't boot (bootloop) and he can't enter into fastboot mode and recovery mode after flash recovery.img and vbmeta.img for install the uTWRP, unofficial TWRP because Team Wn doesn't have made a version for this devices, i've try to install him on my phone (no root) for root this same, but after flashing recov and vbmeta he does not boot in system, fastboot mode or recovery

full specs :

Android 12 MIUI 13.0.1

Xiaomi Redmi 9 MTK G80 AUG/SEP 2020

4/64GB OEM UNLOCKED

all are original parts except the screen

if you can help me, please do it

Thank you in advance
[Redmi 9 / Poco M2 Questions & Answers] Harlock1978:
MAybe you can try to upload a whole new ROM with Spflash
[Redmi 9 / Poco M2 Questions & Answers] XalyLodak:
J'ai fait ça, ça a fonctionné, mais maintenant c'est NVDATA qui est corrompu et je n'ai plus d'IMEIs (Dual SIM) et les outils de MediaTek ne fonctionnent pas, SNWriter Tool, IMEI Writer Tool, Maui et Meta Modem MTK, aucun n'arrive à écrire les IMEI
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] MaxisMan:
I noticed that Android 12/13 ROMs do not have a working encryption. What's the latest Android version/custom ROM with encryption working?
[T-Mobile REVVL V+ 5G] fboofs:
is this where i would find anything on the tmobile revvl v 4 g phone?>?
[Xperia Z5 Original Android Development] tarkzim:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

Introduction

LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Bugs

What's working:

Boot

Double Tap to Wake

Fingerprint Sensor

RIL (LTE/Call/SMS)

GPS

WiFi

WiFi Hotspot (2.4/5Ghz)

USB (ADB/MTP/PTP)

Audio Playback

Video Playback

Torch

NFC

LED lights

Sensors

ExFAT SDCard

USB OTG (From Quick tiles -> Add USB OTG tile -> Press it)

What's not working:

Bluetooth

Bluetooth Headphone (Media / In-Call)

Camera / Camcorder

FM Radio

Hardware Encryption

SELinux is permissive

You tell me.

Installation instructions

Download the zip(s).

Install a compatible Recovery

Perform a NANDroid backup of your current ROM (Optional)

Wipe system / data / cache partitions

Flash ROM.

Optional: Install the Google Apps addon package.

Optional: Install Magisk for Root.

Supported models:

E6603, E6633, E6653, E6683

Downloads

Recovery : My Unofficial TWRP (Doesn't support decryption)

Gapps : NikGApps 13.0

Rom : Download

Sources

Device/Kernel/Vendor Tree: Sources

Donate

DONATE To Me

Big Thanks

LineageOS Team.

@ Myself5

@ Olivier97

all sony-msm8994 contributors.
[Xperia Z5 Original Android Development] tarkzim:
Changelogs

2022/12/18

Initial release of LineageOS 20.0 for Z5.
[Xperia Z5 Original Android Development] Dandroboti:
Hey, this rom looks more fast than LOS 19.1 12L, but sometimes the rom has lag, stops and continues the action that I order. But the rest of the things looks good, keep working in this alpha.
[Xperia Z5 Original Android Development] _harley:
damn Android 13 already
[Xperia Z5 Original Android Development] Azael85:
Did Cam and Bluetooth work or not?
[Xperia Z5 Original Android Development] pjzmj2012:
camara still not working.
[Xperia Z5 Original Android Development] zbieracz2000:
Will camera and bluetooth be fixed in future?
[Xperia Z5 Original Android Development] koron393:
@tarkzim

In my case (Z4 Tablet), camera gets preview after applying this dirty patch to frameworks/native.

diff --git a/libs/binder/Parcel.cpp b/libs/binder/Parcel.cpp
index 58b0b35323..c9d13700a8 100644
--- a/libs/binder/Parcel.cpp
+++ b/libs/binder/Parcel.cpp
@@ -783,6 +783,7 @@ bool Parcel::enforceInterface(const char16_t* interface,
}

binder::Status Parcel::enforceNoDataAvail() const {
+ /*
const auto n = dataAvail();
if (n == 0) {
return binder::Status::ok();
@@ -791,6 +792,8 @@ binder::Status Parcel::enforceNoDataAvail() const {
fromExceptionCode(binder::Status::Exception::EX_BAD_PARCELABLE,
String8::format("Parcel data not fully consumed, unread size: %zu",
n));
+ */
+ return binder::Status::ok();
}

size_t Parcel::objectsCount() const
[Xperia Z5 Original Android Development] Berni-0815:
That does not work at my z5c. In fact, it does nothing.
[Xperia Z5 Original Android Development] Berni-0815:
As @tarkzim has written some time ago:

That's my point of view too; unfortunately...
[Xperia Z5 Original Android Development] zbieracz2000:
Isn't the Z5 camera the same as in X Performance? Sony claims that both are 23MP, 1/2.3'' Sony Exmor RS Mobile. And as we can see on the threads for X Performance, there's no problem with the camera. Maybe it would be possible to port the HAL from X Performance ROMs?
[Xperia Z5 Original Android Development] Berni-0815:
Maybe that the camera is the same one, but the loire platform uses another chipset (msm8956) than our kitakami platform (msm8994).

I don't think that you can use HAL's from this different platform.

But feel free to test it. I won't...
[Xperia Z5 Original Android Development] Jogsn:
I flashed this alpha and now the phone is stuck on the lineage OS boot animation. I tried booting into recovery without success. The phone also has trouble charging and is in a miserable state physically, so it might be caused by a hardware issue.

Do you have any ideas what I could do to fix it? It is not my main device and as such having it bricked is no big issue. However I would like to restore it as a side project.
[Xperia Z5 Original Android Development] H3ADROOM:
Any progress?
[Xperia Z5 Original Android Development] tarkzim:
Not having any major progress or bug fixes, so it won't be updated in anytime soon.
[Xperia Z5 Original Android Development] Seth Cristo:
Alguma atualização? Tenho a rom do Android 11, desde então o giroscópio parou de funcionar (a tela não gira automaticamente), mesmo piscando a Stock Rom, e os sensores estão funcionando normalmente... Talvez com essa rom eu consiga resolver esse problema. .Não tem planos para corrigir os bugs?
[XPERIA X1 Q&A, Help & Troubleshooting] owenchong:
Any success case using Redfly with X1?

I tried 2 versions, both failed.

Redfly client comes with CD, installed correctly but generate error durinng initialization when connecting to Redfly.

Latest Redfly beta client, installation ok, but timeout when connecting with Redfly.
[XPERIA X1 Q&A, Help & Troubleshooting] KaiDream:
I have the redfly and using a custom rom for the Athena 7501. Are you having issues with both usb and bluetooth? (I've had issues with bluetooth before) The X1 is an upgrade option of mine so I am curious.
[XPERIA X1 Q&A, Help & Troubleshooting] jah:
See here for latest beta drivers for the Redfly for the X1: http://www.celiocorp.com/install/beta/

EDIT: remember these drivers are BETA can could be unstable. In my case I had a hard reset and loss of data.
[Google Pixel 7] justDave:
When I first got my Pixel 7 I tried activating 2 eSIMs and was glad to see they worked, as early reports suggested they would.

I just tried it again now and I'm getting a message that says "Only one downloaded SIM can be active at a time."

I was trying Fi and Dent, if that matters.

Can someone still on the October firmware

check if dual eSIM still works there?

Edit: It came back with the March release.
[Google Pixel 7] EtherealRemnant:
I was the one who first reported it working in the 7 Pro forum and unfortunately it has stopped working for me as well. Was nice while it lasted. Supposedly it's being added in the March update but I can confirm that as of the first beta of the March update, it's not working.
[Google Pixel 7] justDave:
I hope it's not a repeat of the dual SIM debacle on the Pixel 3. They released a beta with dual active SIM support and then pulled the feature before the release. We never got it back.
[Google Pixel 7] EtherealRemnant:
Yeah but they wouldn't have added MEP if they weren't planning to enable it.

Two exciting Pixel 7 features were just confirmed by the Google Play Console

According to information gleaned from the Google Play Console, the Google Pixel 7 series will have Face Unlock and eSIM MEP support.

www.androidauthority.com