yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Alondonboy:
I've no problem with either on phone, just head unit. That's why I'm trying to find out where the conflict is as unit Bluetooth pairs with either dongle but App doesn't see it???
[Android Head-Units] Alondonboy:
Well I guess you guys don't know either
[Android Head-Units] rigattoni:
Which app you are talking about???

You never stated that. If the unit connects to the OBD dongls there is nothing wrong.
[Android Head-Units] Alondonboy:
The main one is Torque but have downloaded 2 other similar apps and there is the same problem. Unit pairs with dongle, no option to select it in apps.
[Android Head-Units] rigattoni:
As I said... no issue at all with my CSM4 and others. I use Torque pro since years now, with a $6 cheapo ELM 327.

Write a mail to Klyde and ask for support, may be there is something wrong with your unit... but don´t expect an answer before Jan 28th. They are on Chinese New Year holiday.
[Android Head-Units] Alondonboy:
Seller has said that the dongle they sold is not compatible with the unit, said I need an ELM327. Told them I already had one and that didn't work with the unit either so this morning they messaged and said they had another model dongle and that they had tried it, that worked and they would send it. Thought they were all supposed to be generic? Trying to uplad video to show issue but keeps coming up with error. File probably to large so am reducing quality and will try again.
[Android Head-Units] Alondonboy:
Video
[Android Head-Units] kommando:
Your Galaxy is listed first, try remove it from the paired list so only the OBD unit is on the list, reboot and try again.
[Android Head-Units] Alondonboy:
I've done that. Unpaired it and even left it upstairs to make sure there was no conflict with stereo or in case OBD was trying to connect to phone.
[Android Head-Units] rigattoni:
Last thing I would try, because some guys had same issues long time ago with some MTCD units...

Remove the OBD dongle shut off the phone or just switch off the BT completely.

Unpair both, use a small pin and press the RST button at the front of the unit. (or just unconnect the battery for a second.)

Then stick in the BT dongle after the boot process is complete and pair it again. Try to setup the BT dongle in Torque.

If this then is possible it clearly is the reason that you had your phone connected first at the beginning.... if not, wait for the dongle from Klyde.

BTW: This needs also be done once you get the new one. If you have luck they send it tomorrow, but I would not bet on it... because tomorrow is there last working day until end of January.

Unfortunately not. I´ve seen some OBD with ELM327 which did not work... That´s the reason I told to buy a cheap one and give it a try.
[Android Head-Units] Alondonboy:
Well I'm not holding out much hope as the new one they are sending is the same as the one I had prior to buying the new unit (ELM237) so will be surprised if it works.

Erisin ES350 Mini OBD2 ELM327 V1.5 Car Bluetooth Scanner Tool Diagnostic Android Car Stereo DVD

OBD2 Car Diagnostic Scan Tool

www.erisin.co.uk
[Android Head-Units] EggstarZ:
I got the same problem as you, can you update if this OBD works?

Thank you.
[Android Head-Units] Alondonboy:
Received the new OBD II from seller this morning and just bee out to try it, surprising enough it works. What I did do was delete everything off Bluetooth and made sure Bluetooth was off on phone so the only device was the new dongle. Bluetooth on stereo found it ok and paired, same as other, but this time when you selected it from paired and clicked pair it went red like phone does when you select it. Bluetooth in app found dongle and allowed me to select it but it wasn't communicating so I closed app. At the same time I deselected it in stereo Bluetooth but left it paired, opened app again and it worked. Dials are working and run a quick scan so looks to be ok now.
[Android Head-Units] EggstarZ:
I got the OBD2 same as you got, tried to do the same process as you did with your headunit but no success on my side.

Do you know what kind of bluetooth mode you are using?

any one from the one iv'e attached picures from?

if you don't know you can got to factory settings and type "126", it should get you to the hidden menu.

what kind of MCU you got?
[Android Q&A, Help & Troubleshooting] missmilla:
Please be kind if this is a stupid question - I'm very new to this and learning fast.

Would it be possible to add a signature to aromafm or to a lock pattern removal script, using the leaked Samsung platform certificate (as recently reported), and if so would that allow it to be sideloaded to stock recovery in a Galaxy S9?

I recently had to add a pattern lock - which I somehow managed to immediately forget. Even though it was a simple pattern specifically chosen to fall naturally under the hand so that I wouldn't forget it... I've tried so many variations that it's now making me wait 24 hours between attempts. It also turns out that data that I thought was backing up externally was actually only going to internal storage, so I really don't want to do a factory reset without trying absolutely everything else first.

Galaxy S9

Not rooted

Bootloader is locked

USB debugging is enabled

ADB can see the phone but it's not authorised

ADB sideload does work - but of course any scripts need the Samsung signature.

The phone is not registered with Samsung, so I can't unlock it through my Samsung account.

I realise it's clutching at straws but would the leaked platform key be a way in?
[Android Q&A, Help & Troubleshooting] V0latyle:
While XDA prides itself on being hacker friendly, we shy away from anything that could result in legal liability, which is why we do not permit the sharing of any proprietary material, even if it's already in the public domain.

So in a nutshell....I imagine that if one did have a valid key, and signed an update package using that key, they could potentially use it to exploit their device, such as changing the props to allow bootloader unlocking, thereby permitting custom recoveries. Samsung as far as I know does not protect the system image with Verified Boot, so it is possible to modify /system without incurring a boot failure.

All that being said, the point is pretty moot, because as I pointed out we do not allow sharing anything that is licensed intellectual property, so any discussions on the topic would have to be rather...vague.
[Android Q&A, Help & Troubleshooting] missmilla:
Thank you, that's really helpful. I was thinking more whether simply adding a signature to a script would let that script be used directly with stock recovery, rather than unlocking the bootloader to flash a custom recovery (which I suspect would be beyond me), but it sounds as though in theory it might be worth a try. At this stage I probably have nothing left to lose as I'll have to to a full reset anyway if I can't find anonther way in.
[Android Q&A, Help & Troubleshooting] V0latyle:
I'm honestly no expert on this kind of thing, but if I'm correct in my assumption that Samsung does not protect the system image, then yes - you could, in theory, use the leaked key to sign an update package that could patch /system to gain root. This would require knowledge of exactly how Samsung signs their updates. However, if the system image is protected, this would cause a boot failure, as AVB would detect the modification.

But.

If the above were possible, then the best course of action would be to create a script that would set ro.oem_unlock_ability=1 and sys.get_unlock_ability=1, after which the user would immediately reboot to download mode and unlock the bootloader, because once you've unlocked the bootloader, you've removed a lot of restrictions - you can flash a custom recovery, flash a root patch, flash anything you damn well pleased.
[Android Q&A, Help & Troubleshooting] blackhawk:
I doubt it's that easy unless you have in depth detailed knowledge of the encryption system and precisely how it's implemented. It's designed to be hard to hack. As for the stolen Samsung data be careful what you download. You may end up with something extra like a partition worming rootkit(s). boom. That was too easy.

A data recovery specialist that works with Samsung's is your best shot if you really need the data. Around $800 seems to be a going rate, maybe less but expect to pay a couple hundred.

In the future redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC. Copy/paste only then verify the copy file size and that the backups are readable. Otherwise sooner or later you will lose data, money or both.
[Android Q&A, Help & Troubleshooting] missmilla:
Thank you, I will do some more digging around. Would unlocking the bootloader that way not wipe the data?
[Android Q&A, Help & Troubleshooting] missmilla:
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?

Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.

It's ludicrous that Samsung won't let you unlock a phone if you can prove it's your own.
[Android Q&A, Help & Troubleshooting] blackhawk:
If in the US try a Samsung Experience center at a Best buy.

I never set locks on my phones, bios's or use encryption on data backup drives because you are always the one most likely to be locked out, sometimes through no fault of your own😳

Digital data is fragile unless it's redundantly backed up.
[Android Q&A, Help & Troubleshooting] missmilla:
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?

Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.

It's ludicrous that Samsung won't let you unlock a phone if you can prove it's your own.

Thank you. I'm in the UK but we do have a couple of Samsung Experience Centres here so I'll try asking. Oh I will

definitely

be making multiple, unencrypted backups from now on! I will also be rooting the phone and installing a custom recovery just in case.
[Android Q&A, Help & Troubleshooting] blackhawk:
If you start playing with the firmware bricking the device is always a real possibility especially if you don't follow the protocols correctly. I never had to flash any of my Samsung's in 12 years, all are still working today. I don't do OTA updates either, ever, the potential to brick them like that is higher with you having zero control.

Samsung would really love to sell you a new expensive phone...

Some lessons you end up learning the hard way. I lost a 30yo database that is irreplaceable🤣

Learn from your mistakes and press on. It's a lot easier though to learn from other's mistakes.
[Android Q&A, Help & Troubleshooting] V0latyle:
Unlocking the bootloader will always require a data wipe.

The stock recovery will refuse any packages that are not signed, or are signed with an unrecognized key. There's other measures in place as well.
[Android Q&A, Help & Troubleshooting] missmilla:
Probably not something to be messing around with when I don't know what I'm doing then.

Ouch! No wonder you're so careful with backing up... as I will be too from now on. Lesson learned 🤦‍♀️
[Android Q&A, Help & Troubleshooting] missmilla:
It's sounding like I'd probably better count my losses and leave it alone. And be more careful in future. All this has got me itching to try stuff out though. Possibly not on my one and only phone, but maybe if I can get a cheap second hand one to play with, or the S9 once I eventually upgrade - it sounds so much fun!
[Android Q&A, Help & Troubleshooting] Skorpion96:
You can use the key to sideload an update, if I were you I'll try to flash a blank vbmeta and magisk boot so that you can bypass dm-verity and other measures, but the problem on this is where you can find the certificate? Nobody will tell you where you can find it because who has it remains silent and also communities do not allow this kind of sharing.
[Android Q&A, Help & Troubleshooting] missmilla:
Thank you. Yeah, I thought I had seen someone publish the certificate, but I misunderstood. So wouldn't be able to get hold of it what with not being familiar with the dark web!
[Android Q&A, Help & Troubleshooting] alecxs:
you can always flash blank vbmeta on low level (such as usbdl, edl or bootrom mode) but that's not how it works.
[Android Q&A, Help & Troubleshooting] Skorpion96:
Depends, if your device is made in USA you can't. I was only suggesting a way to bypass flashing restrictions hoping that bootloader lock don't block you. Normally bootloader lock blocks unsigned flashing but if you are able to bypass it during flash maybe you can boot unsigned firmware, I'm not sure though. To flash stuff you can use an exploit or escalate privileges with a signed app that updates a system one to become uid 1000 and after that you can do setenforce 0 or setenforce permissive to set kernel permissive
[Android Q&A, Help & Troubleshooting] alecxs:
No no, locked bootloader prevents booting unsigned boot, vbmeta, etc (not flashing in first place)

😜
[Android Q&A, Help & Troubleshooting] alecxs:
@missmilla just realized you wanna break into your device? this was always possible for S9 (encrypted with default_password) but it's not easy

https://www.forensicfocus.com/news/samsung-exynos-support-in-oxygen-forensic-detective
[Android Q&A, Help & Troubleshooting] blackhawk:
Apparently the Qualcomm variants aren't suspectable to this hack. Only Exynos models are listed.
[Android Q&A, Help & Troubleshooting] alecxs:
missed that. SM-G960F Exynos, SM-G960U Qualcomm? okay, but should be possible to flash combination ROM in order to enable adb, at least, so OP can adb pull -a /sdcard (and maybe adb backup of the desired app with database).

I remember it was even possible to get root. Extreme Syndicate Root was based on combination ROM.

edit: combination ROM should still work, although it requires to buy DID token for flashing. Read about how to flash without data loss (HOME_CSC + no re-partitioning)
[Android Q&A, Help & Troubleshooting] Skorpion96:
i just realised that, then i guess that maybe a temp root using the cert and setting kernel as permissive could be possible, but a root exploit (or a way to become root from system uid) would be needed
[Android Q&A, Help & Troubleshooting] alecxs:
backup all your computers ~/.android/adbkey.pub you have ever used adb, maybe there exist valid RSA certificates somewhere
[Android Q&A, Help & Troubleshooting] missmilla:
Oh wow, thank you! It looks like mine should have Exynos and I'm pretty sure I've never enabled Secure Startup, so may be possible. The article only mentions android 7-9, and mine's on 10, so I've sent the form to ask if it should work and request the demo license.
[Android Q&A, Help & Troubleshooting] alecxs:
SVE-2019-15230 is probably fixed on Android 10 but sure there exist other similar vulnerabilities. these companies keep its secrets. if you're interested in details read this

https://hexdetective.blogspot.com/2017/02/exploiting-android-s-boot-getting.html

https://xdaforums.com/showthread.php?t=1901376
[Android Q&A, Help & Troubleshooting] missmilla:
Unfortunately I've never used adb before, only installed it to try and get past the forgotten pattern, so the only certificate is the one from this attempt.
[Android Q&A, Help & Troubleshooting] alecxs:
there exist combination ROM for Android 10, double check your bootloader level from download mode screen RP SWREV:
[Android Q&A, Help & Troubleshooting] missmilla:
I may be missing something obvious... it doesn't give the RP SWREV. There's nothing on the download mode screen except "Downloading Do not turn off target." then the instruction how to reboot.
[Android Q&A, Help & Troubleshooting] alecxs:
okay kindly check recovery mode screen for buildno
[Android Q&A, Help & Troubleshooting] missmilla:
QP1A.190711.020/G960FXXUHFVG4

Thank you so much for helping.
[Android Q&A, Help & Troubleshooting] alecxs:
you need combination firmware with min. bootloader level = 17 (H) can't be downgraded

G960FXXUHFVG4
[Android Q&A, Help & Troubleshooting] missmilla:
Aha! Thank you, I will give it a go.
[Android Q&A, Help & Troubleshooting] missmilla:
Sorry for being dim but can you point me to any guide that shows how to use combination ROM to enable adb without having to authorize it on the phone, without wiping data?

I've been searching and searching but everything seems to be about OEM unlock or removing the FRP lock, with factory reset. Plus most of the info seems out of date and some looks really dodgy.

I'm pretty sure I've got the right combination ROM and have tried flashing the components as they are (BL, AP, CP and HOME_CSC), which all seems fine - I just can't work out which parts need to be extracted and put together in the combination file or what to do next to let me use adb before doing the reset.
[Android Q&A, Help & Troubleshooting] alecxs:
for Qualcomm you need DID token for flashing. your Exynos download screen does not show any DID, whatever that means.
[Android Q&A, Help & Troubleshooting] missmilla:
I've discovered that it has two versions of the download screen: booting to download from recovery shows no details, as in the photo, but if I switch on by holding volume down + Bixby + power then it goes straight to the download screen instead of recovery, and then it does have all the details including the DID code.
[Android Q&A, Help & Troubleshooting] alecxs:
not sure where to buy etoken, maybe other members (like @_guru_) can tell you how to flash combination ROM
[Android Q&A, Help & Troubleshooting] alecxs:
if you're still interested in sboot exploit... or paid service

https://xdaforums.com/t/flashing-co...er-without-using-etoken.4053059/post-83556083
[Android Q&A, Help & Troubleshooting] missmilla:
Thanks for thinking of me! In the end I had to do factory reset but am still interested in learning - the experience has piqued my interest so it's really good to find out more.
[General Questions and Answers] Nikolaosf:
Hello ppl.

After trying to instal TWRP on my Lenovo Tab 3 (TB3-850M) via adb i got bootlop Running OpenRecoveryScript .

I cant do anything :/ it bootloops all the time pressing buttons doesnt do anything

View attachment 5800767
[General Questions and Answers] ze7zez:
First, connect the usb cable to the PC and check if the adb devices command works. If so, you might be able to repair the partitions by entering TWRP via adb shell.
[General Questions and Answers] Nikolaosf:
because of the continous bootloop it cant connect with pc....connecting for some secs then disconnects
[General Questions and Answers] alecxs:
you can connect adb shell in TWRP recovery.

if you don't care about factory reset, adb push that zip file to /tmp and install from TWRP

https://xdaforums.com/t/deprecated-...encrypt-disk-quota-disabler-11-2-2020.3817389

if you wanna backup /data from TWRP, do not install that zip! adb pull /tmp/recovery.log so we can check how /data can be mounted (probably issue with disk quota)
[General Questions and Answers] Nikolaosf:
i manage to connect via adb in the right second. But i cant use twrp. only FASTBOOT mode.

I trying to "run" the disabler it via sd card but nothing.
[General Questions and Answers] alecxs:
what's that picture in post #1
[General Questions and Answers] Nikolaosf:
the picture is the picture i see during the bootloop.

only when i can see the picture i can use adb to go in fastboot mode
[General Questions and Answers] alecxs:
to me it looks like TWRP recovery. just type adb pull /tmp/recovery.log and upload file
[General Questions and Answers] Nikolaosf:
i did it... where can i find the file to upload it?
[General Questions and Answers] alecxs:
it's in the current directory (probably platform-tools)
[General Questions and Answers] Nikolaosf:
Starting TWRP 3.6.0_9-0-4ea0719f on Tue Jan 3 22:16:57 2023

Spoiler content hidden.

Done processing script file

Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
[General Questions and Answers] alecxs:
please edit post and upload file as attachment. if no attachment is possible, at least put it in [HIDE][PLAIN] these tags [ /PLAIN][/HIDE]

you installed TWRP recovery for TB3-850F is that same or compatible model? on what partition you flashed TWRP?

it seems there are some instructions left on /cache partition, try to format cache from fastboot

fastboot format:ext4 cache

if that won't help, try to stop that loop with following cmd (play with timing)

adb shell rm /cache/recovery/command

once the loop stopped you can use adb commands to mount /data ro, backup, disable dm-verity, restore boot etc. (refer to post #4)

https://twrp.me/faq/openrecoveryscript.html
[General Questions and Answers] Nikolaosf:
formating the cache do it possible to start twrp properly!

aIecxs​

i am Greatfull! thanks a lot
[Touch Diamond, MDA Compact IV General] D0MZE:
I have a dilemma now,

Rogers apparently has the diamond. Should I go and get it there or get it factory unlocked?

Any input?
[Touch Diamond, MDA Compact IV General] Shaady:
I guess it depends on if they fill it up with their own crud software or just give you the phone standard.
[Touch Diamond, MDA Compact IV General] raidendb:
rogers diamond

Just bought a locked Rogers branded HTC Diamond and sold my unlocked EU/Asia Diamond. Now I want my EU/Asia Diamond back since I find it more stable, faster and better gps function. Unless I can unlock and flash my Rogers phone.:o
[Xiaomi 12 Pro] karol_lol:
Hi Guys. I bought 12t pro this week and even if I am happy with the purchase I have noticed one issue with the phone. When I am on the calls and I turn on the speaker even if the volume is not very high the sound is kinda crackling. The issue is not very apparent when listening to YT or podcasts. Did anyone have a similar issue? Any possible ideas on how to fix it?
[Nothing Phone 1] AntoXik72:
Not an expert but I don't think you can make both slots work at the same time. One is for your rom, the other for OTA update. It doesn't matter on wich you are, when you flash, it flashes the other one on wich you are, if I was you, I would have flashed Rice (because of twrp recovery in case something is wrong) two times in a row to make sure your partitions are okay on both slots, then use your reindex link to flash 1.1.7 on one of them if you really want to go back on NOS
[General Questions and Answers] antoniu200:
Hello,

A couple of days ago, a member of my family wanted to unlock their Motorola Edge 30 Fusion's bootloader, to be able to decrypt the data. They brought it to me, since they knew I had some experience with doing so and because I got their bootloader unlocked Galaxy Note9 working with Netflix in full quality (WideVine L1).

This time around, after unlocking the bootloader, installing Magisk and decrypting the data partition, Netflix (and other DRM software) would fully refuse to work. So I took a LogCat read & a DRM info report and saw this:

SafetyNet BASIC is passed (MagiskHideProps & SafetyNet fix + Zygisk & MagiskHide)

WideVine reported level is L1

However! Logcat reports WVCdm being unable to locate & download a certificate for L1. So I checked /data/vendor/mediadrm and the reported error was correct.

However, there is a certificate for L3, but the phone refuses to fall back to L3 for some reason.

liboemcrypto disabler has been unsuccessful, since, from what I can tell, the phone does not use that library.

These same symptoms occur when the userdata partition is encrypted.

Does anybody have any suggestions? I used the exact same steps to get WideVine L1 on the Galaxy Note9.

My opinion is that it has to do with ThinkShield somehow. Can someone advise, please?

Thank you!