yashsingh1/xdaforums huggingface dataset:
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] The Dumb Dino:
How do I install EMUI 8 on my phone (I have a BLN-L21) I saw that I need hwota but cant find it anywhere and the video doesnt help much because that guy is noot speaking english.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] mingchen07:
666啊
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] mingchen07:
6666
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] sash_2k:
I have problem with external storage. I cant write files. At first time the app request access to storage. I can access the sdcard, but wenn i create a file, it creates a 0Byte file with the Name, after that i can modify the file. From widnows i can copy over USB to sdcard. This happens also with the aosp Filemanager too when i create a folder with message "can not create", but folder was created.

logcat show

* "Unkown volume at /mnt/media/"DeviceName"

* Faild to determine if ... is child of... Missing file vor ... at /mnt/media_rw/B5A1-1B09...

wont work under:

/mnt/media_rw/B5A1-1B09 on /storage/B5A1-1B09 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)

works under:

/mnt/media_rw/B5A1-1B09 on /mnt/runtime/default/B5A1-1B09 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)

/mnt/media_rw/B5A1-1B09 on /mnt/runtime/read/B5A1-1B09 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)

/mnt/media_rw/B5A1-1B09 on /mnt/runtime/write/B5A1-1B09 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)

/mnt/media_rw/B5A1-1B09 on /mnt/runtime/full/B5A1-1B09 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=7)

no workaround found that works.

* format sdcard

* test other sdcard

* modify plattform.xml

* third-party Tools

any ideas?
[Xiaomi Poco F1 Questions & Answers] DaRthVaDer 69420:
I dropped my poco f1 in water for few seconds (back in march). Initially it wasn't turning on but after keeping in rice for 2 days it started working except the network part. Can't turn on bluetooth, wifi and sim isn't showing any signal either. Been waiting for many weeks for shops to open but nothing here coz of covid. Any suggestions?
[Xiaomi Poco F1 Questions & Answers] Sathyamasu:
Same
[General Questions and Answers] sa1:
I am ultra noob, so can anyone take a look at the following link for me.

And post a detailed guide.

https://www.pentestpartners.com/security-blog/cracking-android-passwords-a-how-to/

Thanks

P.S. I need this for my own phone and not for illegal stuff.
[General Questions and Answers] :
If your phone's Android is rooted

&

If your phone can get accessed by means of ADB

then

you can open Android's SQLite database named /data/system/locksettings.db via ADB

adb devices
adb shell
mount -t auto -o rw,remount /data/system
sqlite3 /data/system/locksettings.db

and do the database query as mentioned in the article linked to.
[General Questions and Answers] sa1:
@jwoegerbauer this is what it showsView attachment 5306899​

Some things to mention.

1.My phone is locked.

2.By default it goes to USB tethering mode upon connecting to my PC(I changed the setting in DEV mode)

3. It is rooted

4. It has orange fox recovery installed

5. Again I am a noob right now (won't remain that way for too long) and need a tutorial of some kind to do this successfully.

6. I do not know SQL and so how to use it either, and for that matter Hashcat too.

The blog still remains difficult for me.

Thanks again
[General Questions and Answers] :
Line

mount -t auto -o rw,remount /data/system

should read as

mount -t auto -o rw,remount /data
[General Questions and Answers] sa1:
Nothing View attachment 5306943
[General Questions and Answers] :
I see today is not my best day. :(

This should work

adb devices
adb shell
su -c 'mount -t auto -o rw,remount /data'
sqlite3 /data/system/locksettings.db
[General Questions and Answers] sa1:
View attachment 5307221

Still not working @jwoegerbauer
[General Questions and Answers] sa1:
Is there any other way such as doing all this in recovery mode or using terminal in orange fox

or adb sidelode or something.
[General Questions and Answers] :
My guess is that your phone 's Android isn't properly rooted.
[General Questions and Answers] sa1:
@jwoegerbauer what does properly rooted mean. All apps that require root works properly.

SubwayChamp said : If you are in Android 10 system can't be mounted the suggested way, you also said that device is locked but is rooted (?). Orange Fox recovery has inbuilt an add-on feature that can do that.

Here : https://xdaforums.com/t/help-thread-ask-any-question-noob-friendly.2257421/post-85003273
[General Questions and Answers] :
It's not interesting here whether apps that require root work or not. In your case it is only important whether SU-binary can be found by the system.

Anyway:

Some newer Android builds require the following additional ADB commands to be run first to disable Android's AVB-lock

adb root
adb disable-verity
adb reboot
adb wait-for-device

Try this. Then run commands as listed above.

FYI: I no longer participate this thread. Have a nice day.
[General Questions and Answers] sa1:
View attachment 5307781

This is what it shows
[OPPO Find X3 Pro] stuclark:
I've found that my phone has *the most annoying bug* with Android Auto - AA will work absolutely fine when you connect the phone, but then freezes / stops responding as soon as the phone's screen timeout expires and the phone auto-locks.

AA doesn't freeze, when using the same cable and same car, if I swap the phone to being my OnePlus 8 Pro - which suggests this is definitely a Find X3 Pro issue :(

(I'm on the 15 firmware, and at the moment can't get it to update, no matter what I do)
[OPPO Find X3 Pro] mgbosshogg:
@stuclark

I'm on a UK unlocked device and mine won't update either . Still on A15.

That said I tested AA for 2 X 30min trips ( WFH still ) and did NOT have this bug .

I have seen it mentioned in Oppo advert threads on Facebook , they responded each time saying they were aware and working on it . So far I do not put much faith in their updates though.
[OPPO Find X3 Pro] stuclark:
Thanks for the reply - I guess we'll wait to see what the firmware update brings (I've tried uninstalling and re-installing AA, but that doesn't downgrade me to an older version I can use). I'll have a go on facebook and the ColorOS forums
[OPPO Find X3 Pro] mgbosshogg:
@stuclark . Probably worth opening ticket on chat / Twitter DM with them so they are aware. The more the better.
[OPPO Find X3 Pro] stuclark:
Not surprisingly, the answer from Oppo is:

It's an Android Auto bug. It will be fixed when they release a new version. Until then, set the screen to stay on whilst the phone is charging (in developer options)
[OPPO Find X3 Pro] mgbosshogg:
Yup. Welcome to Oppo.

Seems the bug has been present for the year the X2 has been out. So dont hold your breath on a fix.
[OPPO Find X3 Pro] perfecteric:
For me it worked to shut down the always on display function
[OPPO Find X3 Pro] perfecteric:
Try turning off always on display, worked for me.
[OPPO Find X3 Pro] uzumakinaruto69:
Good evening I live in France and I test Android auto because some of you have problems with the application and I wanted to know if it was the same with my X3 pro. I use the app for over an hour and don't notice any worries. Good luck to all

P.S: I'm under the latest oppo update with the A17
[OPPO Find X3 Pro] stuclark:
Thanks for your answer - Android Auto does indeed seem better under A17 than the previous (UK certainly) A15 release.

It also helps to turn off third party navigation apps, such as Sygic or Waze - these seem to exacerbate the Android Auto issues with this phone (but work perfectly on other devices)
[OPPO Find X3 Pro] stakyr:
Images on the lock screen, crash the Android Auto. It is an OS problem. Here is what to do, till the problem is solved :

-Go to Settings, Security, Smart Lock and and your car a trusted device. That way you have your phone unlocked while driving and fingerprint disappears.

(You can also remove fingerprint from lock screen by going to Settings, Passwords & Biometrics, Fingerprint, Screen-off unlock and select off, but then you have to wake up your phone before being able to use fingerprint)

-Go to Settings, ..Always-On Display, Always-On Display and disable it. (You can also select Always-On Display with battery saver, which turns off image after some seconds, but on those seconds, the Andriod Auto is crashed)
[Xiaomi Mi A3 Questions & Answers] ollie2012:
April Update of Android 11 is fast & 720P NOT EYE SORE BUT​

Anyone found any other issues??? Battery life???

Factory reset to Android 10, downloaded Android 11, factory reset and dump on Nova Launcher and lo and behold, 720p looks better

ANTIALIAS???
[Xiaomi Mi A3 Questions & Answers] wetito:
I don't understood your question...,
[Xiaomi Mi A3 Questions & Answers] ollie2012:
Follow the Question Marks?? :P
[Xiaomi Mi 11 Lite 4G] Mahmoud Rasslan:
hello everyone

i'm just wondering if there any working gcam available for the mi 11 lite? and also how's the custom rom development now, is there any custom rom available for the device?
[Xiaomi Mi 11 Lite 4G] the_lzxman:
Yes... U can install Gcam...

For now Only ROM Xiaomi.eu And Miuimix...

Flash via fastboot
[Xiaomi Mi 11 Lite 4G] Mahmoud Rasslan:
could you give me the link please.. also if there's a telegram group or channel can you send it in a dm?!
[Xiaomi Mi 11 Lite 4G] the_lzxman:
Check other post if You search Gcam...
[OnePlus 9 Pro] Frosted_:
My OP9Pro's stock camera app is not opening. Tried all the methods suggested by the customer support team. There is no problem with the hardware as other applications are able to use the camera. The problem is with the camera app.

I was suggested to go with remote flashing by the Team, but they are not responding to any queries and they keep on postponing. So, if there is any detailed guide on how to flash this device (for a beginner) please let me know?

I'm tired of waiting for assistance from the OnePlus Team and it's so difficult to use a phone where I cannot click pictures and record videos.

Or if there is any other alternative for this issue apart from flashing, please let me know.

Thanks in advance!
[OnePlus 9 Pro] nofam:
Have you tried clearing app cache and storage, and defaulting permissions back to default too? You could also try side-loading the .apk from apkmirror?
[OnePlus 9 Pro] Frosted_:
Yeah tried clearing cache and even did a factory reset. No resolution. Sideloading is not working either.
[OnePlus 9] reaper000:
++This post is ONLY for those unfortunate souls who see <awaiting any device> in Fastboot mode for minutes while following the Instructions in Post #1++

- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes

- hit CTRL C to stop the flashing process

- go to Device Manager in Windows and look for the yellow-triangled ! device. LE2115 -- that's your unrecognized Fastboot device

- right click it and select update driver

- select "Browse my computer for drivers" and then "Let me pick from a list..."

- select ADB interface (and you might further need to pick the Universal or Samsung Android device) and install it

- once that driver window closes, go back to the PowerShell window

- type fastboot devices

=if you see a small string of characters, you're good. Go to the last step!

=if you only get another prompt, you need to unplug the OP9 and then reconnect it. Since you just updated the driver, Windows should now recognize and engage the driver for the Fastboot mode OP9. Confirm this by looking for a small string once you again type fastboot devices

=if you still don't get a small string confirming device recognition, try updating the driver again. And again. Because, you know, Windows. If you never succeed in getting Windows to recognize the OP9 in Fastboot mode, you might need to try downloading another ADB driver. But you really can't go further in this flashing process till the OP9 is recognized in Fastboot mode. Only then can you go on...

- the last step! Type rescuefastbootd.bat to complete the flashing process in Fastboot mode. With any luck, your OP9 will now flash the 2nd set of images and then reboot normally, on OOS 11.2.2 in slot B, and you will see the orbiting dots of a normal OOS boot. When you do, you can unplug your phone from the PC. Success!!
[OnePlus 9] reaper000:
OPTIONAL: if you're reading this before catastrophe, I would suggest that you ensure you have working drivers for both Bootloader and Fastboot modes. (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) After driver installation on your PC, steps to do this look like:

- Settings>About Phone> tap Build number 7 times, then

- Settings>System>Developer Options>toggle Advanced Reboot.

- Hold the power button, select the 3-dot menu icon, tap Bootloader

- connect OP9 to your PC, and Windows 10 should install the right driver.

- On your PC, navigate to the Fastboot ROM downloaded unzipped folder.

- double-click cmd.bat and a PowerShell window opens.

- in the PowerShell window, type: fastboot devices

=if you get a small string of identifying characters, you're good.

=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager

- type: fastboot reboot fastboot

and your OP9 will reboot into Fastbootd mode; when you see a splash screen with a choice of languages...

- type: fastboot devices

=if you get a small string of identifying characters, you're good.

=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager (read over Post #2). Once that's done successfully (typing: fastboot devices and getting an identifying string), you want to reboot normally. Success!!
[OnePlus 9] reaper000:
Yeah. Just in case.
[OnePlus 9] _MartyMan_:
Thank you
[OnePlus 9] XNine:
Nice write up, friend! Thank you for taking the time to do so.
[OnePlus 9] Fireblast3:
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).
[OnePlus 9] reaper000:
Glad to help.

Here's your next steps:

I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)

Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.

After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.

Good luck!
[OnePlus 9] Fireblast3:
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"
[OnePlus 9] reaper000:
Try the direct link...?

https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip
[OnePlus 9] Fireblast3:
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
[OnePlus 9] infamousvincci:
Will this convert tmobile variant to global?
[OnePlus 9] reaper000:
Let me quote the OP:

THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.

It wasn't intended to convert Tmo to Global.

If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.
[OnePlus 9] infamousvincci:
ooofff. gotcha. Thank you so much!
[OnePlus 9] reaper000:
I've provided an AFH mirror for OOS' full OTA 11.2.4.4AA for convenient download.

Also, the recommendation I gave you is also now added to the OP.
[OnePlus 9] deadzombieseverywhere:
I appreciate this. It would have definitely helped me back when I had these issues. Now it's here. I'm honestly scared to flash anything on this device.
[OnePlus 9] reaper000:
I've redone the original post to reflect OnePlus' publication of 11.2.7.7AA as a downloadable full OTA and provided a mirror on AFH
[OnePlus 9] flameteam:
My device bricked :(
[OnePlus 9] reaper000:
I'm sorry to hear that. I'm not sure how much I can help, but perhaps you can please provide details? (device model, what circumstances led you here, what version of oos, what you've already tried, etc)
[OnePlus 9] _MartyMan_:
Please upload to MEGA or Google Drive or actually anywhere else as AFH is so slow it gives me 3 days for estimated download time. Thank you. Somebody sending a mirror would be much appreciated.
[OnePlus 9] baboulint05:
hello,

after tired to flashed my OP9 LE2110 , my op9 stuck in EDL mode and erreor sahara with indian eu and global version

any idea for unbrick my phone ?
[OnePlus 9] wtfmars:
I'm getting an error when installing the drivers.

:
[OnePlus 9] gorilla p:
I attempted to use this after a bootloop coming from Arter97 Alpha kernel. This hard bricked it. Failed during install due to apparent driver issue and there was no coming back.

MSM failing with Sahara error
[OnePlus 9] reaper000:
Yikes, at what point did the process fail?

Did you get a response on your pc to fastboot devices when initially connected in bootloader mode?
[OnePlus 9] gorilla p:
It failed after what appeared to be a disconnect and reconnect, but I didnt have the driver installed for the device.

I was eventually able to recover, but the only thing that would work was the OnePlus 9 Pro India MSM tool. I have a OnePlus 9 Global (not pro, not India). So now Im trying to figure out how to get back to the proper image.

Update: After getting booted into the OP9 Pro India image, I was then able to get booted into TWRP and flash the correct full OTA zip for my device. I think Im on the right track now.
[OnePlus 9] reaper000:
I'm glad you got it going... But I'm even more excited of the news that TWRP is now functioning well enough to flash a ROM, even if it is just stock OOS. Can you root it (Magisk) as well with TWRP?

And just to clarify so I can understand what went wrong with the process I outlined -- you said you got a connect/disconnect with no driver. I'm kinda wondering If you didn't have a driver to properly interface Windows to your device, then how could you even get a chance to type any fastboot commands, or confirm that fastboot could recognize your device in bootloader mode?

Thanks for posting and helping out!
[OnePlus 9] gorilla p:
So, the issue occured after

- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes

- hit CTRL C to stop the flashing process

After doing that, and installing the correct driver, I wanted to try again but phone was blank. I just wish I already had that driver installed. Might have avoided the extreme soft brick.
[OnePlus 9] DeathCite:
Stuck in EDL mode after trying this not even MSM can save it and in the windows device manager it just shows up as "QUSB_BULK_CID...."
[OnePlus 9] rulerofmydomain:
Is this a good method if I have a working Oneplus on LIneageOS and just want to return to stock?
[OnePlus 9] reaper000:
It can be.

Just make sure that BEFORE you try this, you:

- make a backup of your data, because it will wipe your device completely

- have PC drivers that recognize your device in both bootloader and fastbootd modes. Seems that's where some failures start.

- understand that you will lose root and have a completely stock device again.

- download the appropriate MSM tool, just in case of catastrophic failure
[OnePlus 9] rulerofmydomain:
First, Greatly appreciated.

To confirm

-backup, I assume you mean user data? It was a test so no user data to speak of

- if I run fastboot devices and see it in in both modes, my drivers should be good

- didn't root, stock is the goal

- hopefully don't have to look what the MS tool is :)

Now it's just time to read over the directions a few times and let'er rip
[OnePlus 9] rulerofmydomain:
So it looks like I got stuck. I was pretty sure that the device was showing in both modes but sure enough when it rebooted it wasn't recognized. I have tried every driver I could fine, nothing seems to work. Any suggestions on a driver?

Can I assume I am stuck here, as in I need to keep the phone in the current state until I find a driver? Or can reboot and maybe flash back the custom ROM i had.

Thank you for any suggestions
[OnePlus 9] reaper000:
Read my 1st 2 posts on this thread... where I give you a link to the driver I used with success personally, and in the 2nd post also walk you through how to install it on your PC. It took a few attempts to update the driver, using the same driver file, unplugs and plugs for the PC to finally recognize the device in Fastbootd.

You cannot abort the process once you start without significant risk of a soft brick that can only be rectified by an MSM tool.
[OnePlus 9] rulerofmydomain:
I had tried what was in the post before searching for other drivers. I will give the multiple try's again and cross my fingers. Currently the device shows up as QUSB_BULK_CID:041D_SN661D980 in device manager.
[OnePlus 9] reaper000:
Sorry for your troubles, but I'm if you tried "disabling driver signing" in Windows 10..?

Look here:

https://xdaforums.com/t/guide-fix-device-not-showing-up-in-fastboot-mode-windows-10.4194491/
[OnePlus 9] rulerofmydomain:
I think I made some progress. Now it shows up as OnePlus Android Bootloader Interface or ADB interface based on what I chose. But fastboot devices still doesn't see it. What is the best way to put it in the correct mode with the keys in light that nothing on the screen comes on?

Thank you
[OnePlus 9] reaper000:
You mentioned that your phone rebooted and that upon reboot, it wasn't recognized by the PC <awaiting device>... Which leads me to conclude when the screen was on, you saw that it was in Fastbootd.

Where it should still be unless you held the power on button down long enough to reboot.

One more thing: you might need a more recent version of SDK platform tools (the programs behind the Windows PowerShell fastboot command etc). Update your PC to the latest version of Android Studio and see if the latest version of the "fastboot devices" command recognizes the device...
[OnePlus 9] reaper000:
I think I might have figured out why people are crashing out at the fastbootd reboot of this process. It's because their version of SDK platform tools has not been updated -- hanging at fastbootd has been happening to people flashing factory stock ROMs on the latest Pixel, and apparently it's because they need new platform tools!

The OP has been amended to include updating SDK platform tools on your PC to the latest version as a step in the instructions.
[OnePlus 9] Moe2003:
how

how did u get it to turn on after the hard brick?
[OnePlus 9] gorilla p:
It wasn't easy. I remember looking through the forums and found someone mention a key combo that got it powered on.
[OnePlus 9] lockmunk:
Press both volume up & down while connecting usb cable. It should detected qhs usb bulk in your pc. If not, I afraid it was really hard brick.
[OnePlus 9] papad13:
hi can you share the key combo please ?????????
[OnePlus 9] Moe2003:
I got it working after praying for about 30 min lol, changed it back to stock then returned it to the seller. NO MORE. ill get a Samsung and have some peace of mind.
[OnePlus 9] dlembazo:
Thanks for your HELP!!!

I just want to be sure of putting right everything, before starting!

How to use "SDK platform tools" to avoid to be stuck " at "a later step (specifically, when rebooting to Fastbootd)"

Thanks very much :)