Database Develop

[Q] Can't get MTP to work

Hi,
I have been trying to connect my Nexus 6 to my work pc but I just can't get the MTP file copying mode to work properly. I have used the latest Google USB driver and actually it's not so bad. With USB Debugging turned ON, I see "Android Deivce > Android ADB Interface" properly installed in device manager. I even see my phone's serial no. when I type "adb devices" in command prompt. BUT the bloody MTP mode just refuses to work. It keeps showing up in Device Manager as "Other devices" > MTP, with a question mark next to it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I switch USB debug off, there's no Android ADB Interface, and the unknown MTP entry in "other devices" transforms to "Nexus 6", again with a question mark next to it.
I have tried to manually install the proper driver but for starters, if I just select the folder where the .inf files are located Windows don't seem to anything inside it and when I force it to use that file ("Show All Devices > Have Disk") it only shows ADB and Bootloader drivers:
So what am I suppose to choose there in order for MTP to work as it should?

Have you tried other pc or laptop??

Yes, the phone shows up correctly in all modes on my home pc.

Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ

DebianDog said:
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I did that to no success but in the end, I just tried a different USB2.0 port and it worked, all drivers installed correctly. Now the weird thing is I can read from the internal memory of the phone, I can delete stuff from it, but when I try to copy something to it it says: "Error copying. The device has either stopped responding or has been disconnected" so I can't yet copy to it. This is driving me crazy right now...

I have this issue this morning. Right click and Update Drivers > Browse For Drivers > Let me pick > Portable Devices > Standard MTP Device > MTP Device.

Need Method for Google Pixel 4 Android R QPST & QXDM Log Method

Hi ,
I Need to Know the Complete Method How to Connect Google Pixel 4XL Android R With QPST & How to Take QXDM Log for Google
Thanks ,
Nabil Anwar

Hi, I am trying to install QXDM5 ( QXDM5.5.1.280.7.Windows-x86) on win10. First i have installed QPST.2.7.485.7.exe and it is successful and then tried to QXDM5 but while installing seen the error saying that "QUTS.Core was not installed. Reason: CatalogError". Here i have attached error logs. It would great help if some one help me on this issue.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey!
I am working with the EDL mode, I am trying to use it as a way to unlock Pixel boot loader form it's carrier. Though I am still testing...
Let me see if I can help you guys:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.

Fast boot issue - Reported as '????????????' then switches to splash screen

Hey guys,
First time trying to flash a rom (using Windows 11). At first the Razer phone 2 showed up in my device manager as 'Android' with a yellow warning sign. I managed sort that by installing the latest android_winusb.inf drivers, and it shows up in the device manager As oculus Device>Andriod Composite ADB interface (not sure why it's under the Oculus tab, I didn't use the Oculus driver).
I've tried all three drivers (ADB Interface, Bootloader interface and Composite ADB interface) and the results are the same. When I send the 'fastboot devices' command, it will report
''???????????? fastboot'' and then it switches to the razer logo with 'Powered by Android' and 'Press any key to shutdown' text and is no longer in fastboot mode.
I assume the question marks are supposed to be a serial number.
Anyone have any ideas of what I might be doing wrong?
FYI, I've also tried 2 usb 2 ports, a usb 3, and two different Type A to C cables.

This happened to me. You need to run Powershell/Terminal in the path of the folder containing the Platform Tools. See example photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Also, make sure to follow this exactly. https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf

Thank you so much for your help, I will give this a try.

There is some sort of issue with Windows 11 and arter97-r12 and -r13. I was going to do a fresh install of SMR3 because of a few software issues and Google Play app updates. When booted into Recovery and making backups and moving files, I ended the session and rebooted "System" from TWRP boot menu. Upon execution, TWRP warned me there was no OS installed.. WORST NIGHTMARES. I've finally gotten it recovered, but what a MESS. Download platform-tools v33.0.1 from google and follow the directions from Razer to properly install ADB Fastboot drivers. See links below:
Platform-Tools: https://developer.android.com/studio/releases/platform-tools
Razer Driver installation: PDF attached
UPDATE: I found the issue was NOT necessarily my version of platform tools, It was my USB port. I am using a Surface Pro7 and tried multiple different cable and both the USB-C and -A ports to no avail. Would not communicate in fastboot mode, BUT, I then used a 4-port USB 3.0 hub, connected the phone, and all ADB/fastboot commands and communication functioned normally. once I figured this out, I was able to reinstall the proper drivers on Windows.

Same problem, u PC AMD?

[ROM][LINUX][ONCLITE] Droidian Bookworm

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones. This is accomplished by using well-known technologies such as libhybris and Halium.​Requirements​
Android 9 firmware for your device:
Redmi 7 onclite: LINK
Files​
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_onclite-api28-arm64-nightly_XXXXXXXX.zip
Installation​
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
Alternative installation
Alternatively the UBports installer can also be used to install Droidian
Notes​The default password is 1234.
List of working things can be found at https://github.com/droidian-onclite/device-page
APN​Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls​Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Out of storage​By default when flashing Droidian it allocates 8GB of storage to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
SSH access​connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications​You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
What Works
Notification LED, Torchlight, Vibration, Carrier info, Data connection, Calls, Pin unlock, SMS, Audio routing, Voice calls, Volume control, Battery percentage, Online charging, RTC time, SDcard, Shutdown, Reboot, Bluetooth, Flight mode, Hotspot, WIFI, Proximity, Rotation, Touch screen, Earphones, Loud speaker, Microphone, Waydroid, Brightness, Encryption
What partially works
Camera works fine in Waydroid but in system itself its slow and requires some technical work.
What doesn't work
GPS, Fingerprint, Offline charging, Dual SIM, Auto brightness
Waydroid​Waydroid is an Android container which lets Android apps run on Linux phones with GPU acceleration with full speed.
Waydroid works fine on onclite.
Final Notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @Barrys_crib.
Droidian telegram group: @DroidianLinux.
Thanks to the Droidian Team, bibarub, supirlelik96 and TheKit for helping out to make this happen.
All the sources are available at
https://github.com/droidian-onclite/
Attached images are from different devices but the interface looks and acts the same.

How long does first boot take, cause mine has been stuck on boot for the last hour or so. Is this normal or is my phone bootlooping?

SolomoEudor143 said:
How long does first boot take, cause mine has been stuck on boot for the last hour or so. Is this normal or is my phone bootlooping?
Click to expand...
Click to collapse
Have you downgraded to Android 9

FakeShell said:
Redmi 7 onclite: LINK
Click to expand...
Click to collapse
Link here should be onclite not lavender. (wrong in the other thread as well)

Eskander said:
Link here should be onclite not lavender. (wrong in the other thread as well)
Click to expand...
Click to collapse
ah my bad i forgot to change it
will update now

FakeShell said:
ah my bad i forgot to change it
will update now
Click to expand...
Click to collapse
Sry for late reply but I was eventually able to get it to work. Originally I had installed Android 9 via fastboot and booted into it. Then I went back into twrp, wiped system and data and installed the custom rom and adaptation package. This time it got stuck.
For my next go I wiped the phone entirely and installed the Android 9 rom via twrp this time. I wiped the system and data and directly flashed the droidian rom and adaptation package without booting into Android 9. This time it had worked.

[ROM][LINUX][ONCLITE][EXPERIMENTAL] Manjaro libhybris

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Manjaro is a GNU/Linux distribution utilizing technologies like libybris and Halium to run a Linux distribution on Android devices.​Before starting the installation I should add that Manjaro libhybris is very experimental and it might break at any time so its more of a toy. If you want a smooth and more stable experience that can be daily driven, take a look at Droidian. Droidian on onclite
Requirements​
Android 9 firmware for your device:
Redmi 7 onclite: LINK
Files​
Download the latest rootfs: Manjaro-ARM-phosh-google-sargo-XXXXXXXX.zip. (Yes my work is based on google sargo and i used that as a base mostly because i also own a sargo so i experimented with that first then based my work off of that)
Download the adaptation package: adaptation-manjaro-onclite.zip.
Download TWRP or any recovvery: TWRP.img
Installation:​
Boot into fastboot and run: fastboot flash recovery TWRP.img
Reboot into recovery: fastboot reboot recovery
in recovery wipe data and system.
Go into sideload mode and run: adb sideload Manjaro-ARM-phosh-google-sargo-XXXXXXXX.zip
After it's done go back into sideload mode and run: adb sideload adaptation-manjaro-onclite.zip
Now reboot.
The first boot will take a while.
Notes​Default password​The default password is 123456.
APN​Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls​Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Out of storage​By default when flashing Manjaro it allocates 8GB of storage to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
SSH access​connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications​You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
What Works
Notification LED, Vibration, Carrier info, Data connection, Pin unlock, SMS, Battery percentage, Online charging, RTC time, SDcard, Shutdown, Reboot, Bluetooth, Flight mode, Hotspot, WIFI, Proximity, Rotation, Touch screen, Waydroid, Brightness
What doesn't work
GPS, Fingerprint, Offline charging, Dual SIM, Auto brightness, Torchlight, Audio, Calls, Audio routing, Voice calls, Volume control, Earphones, Loud speaker, Microphone,
Notes
Settings app does not open from the app drawer. If it has been opened from the app drawer it must be killed from the terminal.
To open the settings app run: GSK_RENDERER=cairo gnome-control-center
The fingerprint sensor acts as Enter keyboard key.
Final Notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @Barrys_crib.
Thanks to the Manjaro team, Droidian Team, bibarub, supirlelik96 and TheKit for helping out to make this happen.
All the sources are available at
https://github.com/droidian-onclite/

Bry
But I want to know what is adaption package and how it works

Bry
But I want to know what is adaption package and how it works

Bro
But I want to know what is adaptation package and how it works

Sorry i sent it actually one time i dont know why it gone 3 times maybe the issue with network

the_arxyn said:
Bry
But I want to know what is adaption package and how it works
Click to expand...
Click to collapse
adaptation package is a sideloadable package containing all the binaires, scripts, configurations and other files needed to get the device to a working state. users flash the adaptation package once and that adaptation package installs a package as an example a deb package in debian which contains all the fixes and a repository for the user to update over the air via the package manager. so they do not have to flash anything else later they can just use the package manager and update and system will update just fine.