yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Droidriven:
This forum does not deal with computer software development, this entire website is for android software and Windows mobile software ONLY, not PC software.

In other words, you are on the wrong website to be asking your question, find a computer software development site instead of wasting your time .
[General Questions and Answers] DiamondJohn:
If I am understanding him correctly, he may be on the correct site.

I understand him as wanting to build ANDROID, but for a non-arm device (ie x86). My belief is that this site is hardware agnostic. Our devices are computer systems, just mostly arm based.
[General Questions and Answers] Awate .Jr:
Thanks for understanding me SIR ?
[General Questions and Answers] Raresh T:
there s been already a few attempts on that, remix os, phoenix os, bliss os. remix os, is also abandoned, long time ago. perhaps there s the source somewhere on the internet. why not try to build from that? no point in trying to reinvent the wheel
[General Questions and Answers] Droidriven:
Ah, now it makes sense.
[General Questions and Answers] Awate .Jr:
Thanks

But my words idea is unique(please don't steal it) I am trying to integrate the wine compatibility layer in my is kernal so that I can make a os that. Can run android Linux(because of android) and windows apps.

Thanks in advance

I am 12 and looking for help from professionals like you
[General Questions and Answers] Raresh T:
https://www.androidpolice.com/2016/...dows-apps-android-chromebooks-even-photoshop/

your idea is gonna take time. go for it, who knows, maybe you are the next steve jobs
[General Questions and Answers] Awate .Jr:
Thank you so much sir for believe in me I will not let you down
[General Questions and Answers] DiamondJohn:
You probably receive a little push back on this thread, as its generally an entry area. For more specific dev, you may be better off within a different thread or by starting your own specific thread or a gtithub project.

Although not the perfect thread (as its building android, for mostly arm devices already running Android mostly AOSP or LOS based), you probably would be better off in a thread like:

https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

I really believe what you are talking about is a project big enough and specific for its own thread. ie its too specific for a general thread like this one.
[General Questions and Answers] Awate .Jr:
Thanks sir for guiding me can you please guide me on how to make an thread on XDA cause I am new here

Thanks in advance
[General Questions and Answers] DiamondJohn:
I think your post count may limit what you can do. Read the XDA rules etc Everyone was new here at some stage.

As for how, if you plan to build what you describe, operating a user friendly web site should not be a roadblock.
[General Questions and Answers] swaswaYT:
Recocer files from phone with broken screen (fully black)

Phone: Xiaomi mi 9 SE

ROM / Android version: MUI version 9 i believe (not sure)

Root (yes/no): no

Any physical damage prior to defect: broken screen + digitizer

Describe your issue:

Unable to retrieve data from phone, able to boot into fast boot and side load. ADB only recognized my phone in side load

When connecting to pc (windows 10) i recognized my phone as MTP device and detect the name but labels it as unspecified.

Tries using Fuzzymeep two his recovery tool but with no success.

Boot loader is locked and as far of my knowledge goes only able to unlock with full wipe.

Easiest solution is to repair the screen but it will cost me 180 euros including labor and 100 without labor.

For an student this means i have to sell a kidney and my left testicle so please no.

Thanks in advance!
[General Questions and Answers] Awate .Jr:
Thanks sir for guiding me .

Sir. But it is difficult to bring traffic to my website

Thanks in advance
[General Questions and Answers] Droidriven:
He was referring to this website. He was saying that XDA is user friendly and that you should not view navigating/using this website as a roadblock, it shouldn't be something to hold you back.

---------- Post added at 08:31 AM ---------- Previous post was at 08:24 AM ----------

This is a common problem, unfortunately, if you do not have USB debugging enabled in the device's settings and if the device is not properly recognized when you connect to PC, you won't be able to solve this. Whether you like it or not or can afford it or not, you need to replace the screen or send the device to a professional shop that has the proper tools and methods to disassemble your device and retrieve your data directly from the chip in your phone.

Be prepared to spend some money to achieve your goal or forget about it and throw the device away.
[General Questions and Answers] Awate .Jr:
Thank you so much sir for guiding me .

I will always understand respect , and adore you . ??

It means a lot when some one replies me or helps me out.

By the way my device is Lenovo k5 (a6020) and is fully compatible with android 10 (aex extended) in t has 2 GB ram which is enough for testing and proof of theory

Thank again.

Thanks in advance ?
[General Questions and Answers] Awate .Jr:
There are many ways to do it but a hard way is using Linux because there was s a chance that Linux will recognize your device . The hard way is is the f you have android running then you can use msf venom and insert a payload and do that's way . Just tell me in detail what has happened and how much your device is functioning.

Thanks
[General Questions and Answers] swaswaYT:
The only thing that is not functioning is the screen and digitizer (+ fingerprint sensor because this is part of the screen).

After the phone fell the screen stopt functioning. At first there were some green flashing lines but know it is completely death. The phone is able to turn on the flashlight by pressing the power button twice. Because of this function i know that the phone is turned on.

When connecting to my laptop. The laptop is able to reconize the device as Mi 9 SE with MTP enabled. File explorer is not able to open the phone.

I am able to boot it in recovery mode (stock) and fastboot.

Could you link me some tutorials to some of the ways i can retrieve my data?

Thanks.
[General Questions and Answers] Awate .Jr:
Why don't you use you Google assistant to operate the phone (if you have not locked your phone ) or

Step one install https://play.google.com/store/apps/details?id=com.koushikdutta.vysor (u can do this using you Google assistant).

Set it up [youtube]KHyFWxy_kiY[/youtube]

Wola then you can control your phone from PC

Op

You can also download the backed up data on Google cloud

I also have an great idea

Just tell the assistant to screen cast you phone to the smart TV . And then connect your phone with a USB mouse(using otg cabel)and then after you got access you can back it up

Op

Help link

[youtube]Ak2JruLESqw[/youtube]
[General Questions and Answers] Raresh T:
google assistant, by default, will not work. you have to install voice access and give it permissions to control your device it order for your idea to work.

second, [MENTION=10899921]swaswaYT[/MENTION], i have two questions

1. do you usually lock your device?

2. did you had any chance activating usb debugging on your device?. if yes, then is simple. you can get your files through adb. its a tedious process, but will work.
[General Questions and Answers] swaswaYT:
USB debugging is disabled.

As for locking the device. It is password protected and the bootloader is locked
[General Questions and Answers] Droidriven:
You are in a catch 22 scenario, you are pretty much screwed unless you find a way to unlock the screen without using the touch screen. ADB can be used to unlock the lockscreen but it requires USB debugging to be enabled in order to use ADB to unlock the screen so ADB is not an option for you. Google Assistant isn't going to work either because you can't access the device in order to install/setup Google Assistant.

I could be wrong, though not likely, my previous reply still stands, your only options are to replace the screen yourself, pay a professional to replace the screen, pay a professional to disassemble the device to possibly extract your data directly from the chip itself or put the device in the trash and forget about your data.
[General Questions and Answers] swaswaYT:
I can unlock the phone using an OTG cable and keyboard. But i cant really navigate using this method
[General Questions and Answers] Droidriven:
If you can unlock the screen, it should be able to connect to PC and access the internal storage on the device, but, you will only have access to the user partition, you will not have access to data partition or system partition, anything in those partitions will be unavailable to you unless you root the device, which requires flashing TWRP or Magisk but you can't do that because you don't have USB debugging enabled plus you have a locked bootloader.

Like I said, you are in a catch 22 scenario. In other words, you "could" do it "this" way "if" it weren't for "that" roadblock and you "could" do it "that" way "if" it weren't for "this" roadblock. You can get "close" but not "close enough".

Hypothetically, it may be possible to use the keyboard to access settings and enable USB debugging but it would require you knowing exactly which keys to use, when to use each key, how many times to strike each key and what sequence you need to strike them in, in order to access the correct setting and enable it.

You could try trial and error, to hopefully get the keys right and in the correct sequence, but you won't have anything to guide you to be able to tell if striking the keys in the order that you strike them is actually getting to the setting that you need. You will basically be shooting in the dark and hoping that you get lucky.

You are pretty much stuck "behind the 8-ball" with no viable options to choose from.

If you can unlock the screen, you should be able to access your storage to retrieve your photos, videos, downloaded files, stored files, etc.. You can only access files that you are stored in the user partition. The data partition(where the apps that you personally installed) and your system partition(your device's preinstalled software) can not be accessed by your PC file manager. Only rooting the device or installing TWRP can give you access to your data and system partitions, but your bootloader is locked which means Magisk or TWRP can not be used, therefore, you will ONLY be able to retrieve files from the user partition and nothing else.
[General Questions and Answers] mrrocketdog:
ok ,

galaxy s4 sgh-i337 (att) on android 5.0.1 rooted with kingroot then replaced with superSU.

noob mistake ; tried to flash twrp with Flashfire and then with Official twrp app before unlocking bootloader.

now get warning of "unofficial firmware found".

question ; if i factory reset will it restore original firmware? or am i stuck? (curious if anyone knows before i wipe my phone).

have also tried "samsung secret dialer codes" to find "golden backup" (found on some phones) or to reset phone without luck.

debugging is enabled and phone shows up with adb devices. but when i adb to bootloader i get message "waiting for any device". also , no option in settings to enable "oem unlock".

any help/insight appreciated. :)
[General Questions and Answers] Awate .Jr:
I have an Lenovo k5 vibe and it only has a root and the twrp is install using the app in playstore I was also able to install custom rom using it. I think it is the same in his phone . Surely you can and will unlock the phone using the otg because in the lock screen there is no other text in out rather than password so firs hit enter and there type your password and the hit enter again .
[General Questions and Answers] Droidriven:
The S4 should be able to just reflash the stock firmware to solve this or at least flash a copy of stock recovery via Odin, the S4 was before everything became so locked down but yet still right on the cusp.

You are getting the error because the recovery partition has been modified, not the system or "firmware". No, factory reset will not fix this, that only wipes the user partition and data partition, it does not do anything to system and it certainly won't restore your stock recovery, if it could do that, devices with TWRP would lose TWRP if they factory reset.
[General Questions and Answers] SubwayChamp:
https://youtu.be/FBfQLYEVldA
[General Questions and Answers] Droidriven:
Yes, that would unlock the phone and they have already done that using keyboard. But, that is just the beginning of the journey, it's the rest of the journey that presents their true challenge if they want to recover anything other than user data from the device. To go deeper requires things that they, more than likely can not do in the situation that they are in.
[General Questions and Answers] Awate .Jr:
That's motivation op

If he has unlocked his phone he can connect it to a smart TV if he does try and errors after that he has the control
[General Questions and Answers] Droidriven:
Yes, they can try, but that requires more connection to the device and control than they have. Your ideas are valid and have been suggested by many others in many threads here, but, unfortunately, typically, users in the situation that they are in can not take advantage of most of the things you are suggesting. It all comes down to being able to access the device settings in order to implent any of a number of options that any of us may suggest. As I said, just unlocking the lockscreen is easily achieved, it is everything else after unlocking that runs into a roadblock due to their limited ability to interface with/control the device, I doubt they connect to a TV easily or by default, it may require certain settings to be set in a certain manner to achieve connection with TV and control the device via the TV.

My point is, most of the time, it isn't exactly as simple as what your posts are implying. Quite often/most of the time, users that have a broken screen and do not have USB debugging enabled do not have much luck retrieving data due to the roadblocks I keep referring to. Connecting with the device and interfacing with/talking to the OS while the OS is running, other than MTP functions requires USB debugging to be enabled.
[General Questions and Answers] Awate .Jr:
That's motivation op

If he has unlocked his phone he can connect it to aOk sir I understand now I will suggest some ideas which can be done without touching the screen

Link one for turning on USB debugging without touching the screen [youtube]GPJcR_Iosm4[/youtube]

You can install vysor the same way and install it and then copy the data to cloud
[General Questions and Answers] Droidriven:
I wasn't saying anything about your suggestions requiring touch.

But, regardless, the video you posted is a viable option for enabling USB debugging, but if they haven't setup/used Google Assistant on their device before the screen was broken, they won't have much luck with what the video demonstrates.

Don't get me wrong, I am not saying that they absolutely can not access their device to retrieve their data. What I am saying is that in their particular scenario, they don't have a lot of options because many of the available options require certain things to be enabled or setup at some point before their screen gets broken in order to take advantage of any number of options after it gets broken. But, without some of those things enabled/setup prior to the issue, they will likely encounter some kind of roadblock with no way to set those things up to take advantage of "this" or "that" data recovery method.
[General Questions and Answers] swaswaYT:
Maybe a long shot but could someone Type out the exact keyboard button presses to enable usb debugging on the MI 9 se?

Maybe someone is able to use an emulator?

I cannot seem to get this working.

---------- Post added at 09:47 AM ---------- Previous post was at 09:02 AM ----------

I tried this but I get the notification that the app will install shortly on my device.

But it doesnt....
[General Questions and Answers] Droidriven:
For this, you would need to find someone else here at XDA that has a device like yours that also has a keyboard to use then have them use the keyboard to access their settings and navigate to the USB debugging setting then have them tell you the exact sequence of keys it takes to get to the setting.

You'll probably have to go to the about phone>software info>build number setting and tap the key 7 times on that setting to enable developer options then go back to settings menu to choose and open developer options then enable the USB debugging setting in developer options.

You may be able to use Google Assistant to open your settings menu, then use the keyboard to go to the bottom of the page(press the button enough times to ensure that you are at the bottom), the "About Phone/About Device" setting should be the last setting on the main settings menu, then tap the button to open the about phone setting. Then, if you can find a screenshot of the "about phone" setting from another device like yours, you can use that as a guide to count how many times you need to tap your keys to highlight the software info setting, then find a screenshot of your software info menu, then use it to count how many times you need to tap your keys to highlight your build number, then tap the key at least 7 times very quickly to enable dev options, then use the keys to go back to settings main menu then find a screenshot of settings with dev options enabled to find out how many times you need to tap the key to highlight dev options then open dev options, then find a screenshot of the dev options on your specific device and use that screenshot to count how many times you need to tap the key to highlight the USB debugging setting then tap the key to enable the setting.

It won't be easy, but it is possible.
[General Questions and Answers] SubwayChamp:
Miui uses Gboard by default (on non chinese firmwares), you would find many screenshots from in the net.

To enable USB debugging on Miui you have to go to >My device>Miui version (in Miui 10 and probably in 11 too) and tap on it 7 times, then back on the main menu and go to Additional settings, you will find the new item there.

Also if you find it easier you can enable Google Assistant (doesn't need extra settings) https://in.c.mi.com/thread-1716967-1-0.html
[General Questions and Answers] Droidriven:
They are using a physical keyboard due to the screen being broken.

Thanks for the clarification of how to enable USB debugging on Miui.
[General Questions and Answers] DragonFire1024:
So I'm just about at a loss. I'm trying to get the camera modules to function on the Google Nexus 10 AKA Samsung Nexus 10 on Android 7 whether it be lineage or built from AOSP. The problem is I believe, the hardware code is incompatible with present-day code. However it that shouldn't matter because at some point during this device is life a similar problem occurred where they were able to switch from using the hardware/platform camera (exynosX) 2 using a software version of the camera from Samsung AKA SecCamera. The thing is I can't seem to find any common files to fit the CPU of this device unless of course I am completely misunderstanding what I'm looking at. First off does anybody know what the common tree is for ExynosX (X being 1, 2, 3, etc.)? I have seen these modules for SecCamera in older source code for kit Kat, but I can't seem to figure out how they managed to get the common files to work with the platform files as I can't even get the device to boot or when I do, nothing exists for the camera except permission files. This is the only reference I can find where they managed to fix this and it's talked about within a email on a Linux forum. I will double check the configurations again but as far as I can recall I either had set them all or made sure they were all set. https://lists.ubuntu.com/archives/kernel-team/2013-May/027889.html basically any advice that someone might have in a similar situation on another device would be greatly appreciated.
[General Questions and Answers] Droidriven:
Camera is always a b**ch due to camera being proprietary/closed-source. A development thread closely related to what you are trying to do would be a better place to discuss your query.

Have you read this to see if it may give you some clues?

https://source.android.com/devices/camera/versioning

Have you tried discussing this with some nexus 10 lineageOS 13 devs to see what their trick was and to see if they have any ideas?

Have you tried discussing this on LineageOS github?

My guess(a long shot in the dark) is it's an API/libs/permissions issue between the stock camera apk and 7.0 kernel.

Have you tried decompiling the stock camera apk and the 7.0 kernel that the build process spits out to compare them to see what each might expect from the other software-wise?

Sometimes, swapping camera libs from other builds makes camera work. Or maybe porting the Marshmallow kernel(which seems to work with the stock camera, though a little unstable) to work in the Nougat build? Or a mixture of porting the kernel and porting the apk?

Considering the previous development issues with camera on Nexus 10 in the Marshmallow builds, I'd wager that even if you got camera working, it would be unstable and be a battery killer just like it was in the Marshmallow builds, with not much hope of resolving it.
[General Questions and Answers] DragonFire1024:
I did not actually think of looking in the APK but that's one thing I'll do. there aren't many around who actively developed for this device anymore so much so that I have found myself doing a considerable amount of the updating myself from what I can understand of it anyways. Some of it seems to be general compiler errors which aren't usually a problem with fixed except for there can be numerous amount at times. Anyways there are a few things I can look overto make a determination but I think you're probably right or at least some of it has to do with signatures or at least verifying signatures or checksums.

if I also had to guess I would say it's not so much as incompatible hardware as it is with the code just never being upgraded properly to a state where it would be working. Which I can understand that coming from a device that is no longer being manufactured. I'm pretty sure I'm beating a dead horse or at least poking what's left of the carcass with a stick, but you never know and I'm usually pretty good at solving these things though it may take some time to do so and if not there's always something else I can work on.I will update you when I have more and after I look over a few more things.

Edit I wanted to add that exchanging the libraries did not do any good in fact it actually put the device into a never-ending black screen. Even after replacing the original files it still wouldn't boot. That is not surprising though.
[General Questions and Answers] DragonFire1024:
Also one more thing.I have a ROM built from AOSP with cameras work but here is what the most advanced hardware detector I use can detect of them which is pretty much nothing in terms who makes them or what modules they actually are. I mean how does that even happen where the software name doesn't at least get passed through the build process in some registered form whether it be remnants of a file or something of that kind I have never seen this before proprietary or not there's always something there that gives you some kind of clue. These screenshots are almost screaming why even bother.
[General Questions and Answers] Droidriven:
Have you tried Aida64? It gives detailed codecs and system file names on my device.

It is my go-to for PC systems and android.
[General Questions and Answers] DragonFire1024:
I just did and it doesn't tell me any new information about the cameras even less so then the other one. Grrr.