I love the nexus 4 but the fact that my mac can't see it is really annoting. I could easily connect my GS2 like a pendrive and transfer files and also rearrange stuff. Now, I've searched around the web and found the 'Android File Transfer' app that allows me to copy files back and forth from my mac. I would be totally fine with this if only it allowed me to move files from on folder to another with my nexus. This is a ridiculously basic feature that is missing. i.e. say I copy a bunch of songs to the wrong folder on my phone, AFT doesn't allow me to just drag those files over to another folder on my phone. I now need to delete all those files and recopy them onto the correct folder. This is unacceptable so I'd like to know if theres a good alternative to AFT or am I missing something?
FYI: Im on 4.3 and not rooted
BUMP!
Some info I've found online suggests that running gvfs and Nautilus from MacPorts works well with MTP. I've had success with Nautilus in Linux but have not used Mac OS.
If your only issue is not being able to move the files to a different folder after they've been transferred, have you considered just using an Android file manager app to move the files once they're on your device?
I got access to WIndowsApp folder but unable to replace the live tile pictures. IS there any settings to unlock that.
https://onedrive.live.com/redir?res...authkey=!ALBf23_ZD8o--mE&v=3&ithint=photo,png
I also can't replace/overwrite any file on windowsapps folder even after gained permission as administrator/administrators/full control mode. I saw on youtube someone just able to do in windows 10 (before aniversarry update) but I wonder why I can't do it like what he did.. I just want to modding my games..
Hi, I recently bought a 2017 shield and Im now running the latest Android TV but to my dismay I haven't been able to figure out how to change the background from the, in my opinion, tacky wallpaper of the green blood cells? Is this possible at this time?
uratrtl said:
Hi, I recently bought a 2017 shield and Im now running the latest Android TV but to my dismay I haven't been able to figure out how to change the background from the, in my opinion, tacky wallpaper of the green blood cells? Is this possible at this time?
Click to expand...
Click to collapse
This is not my work but here you go:
Anyone interested in a tutorial on how to change the default wallpaper on your Nvidia Shield TV? (And possibly Android TV in general, have to figure that out first)
Root required..
Step 1: Edit your own wallpaper image so that it is named nv_wallpaper.png with dimensions of 1920x1080. Don't just rename a jpg to png, convert it.
Step 2: Back-up the NvCustomize.apk file in the /system/priv-app/NvCustomize/ folder to a secure location. Or use a backup tool.
(Note that when you copy the file back, the permissions have changed and you need to change them back to chmod 644 (for the apk) and chmod 755 (for the folders, which you don't need to backup per se)
Step 3: Copy a second version of the NvCustmize.apk to a location you can access on your PC or an easy to remember location you can access with a file explorer. Not all file explorers let you write to the apk when it's still in the system folder. So copy it anywhere else.
Step 4: Somehow merge the new PNG you made with the NvCustomize.apk, without decompiling or extracting the apk. You can use Winrar, but DON'T extract it. leave the file intact and just copy the nv_wallpaper.png to the location of the same png in the file and overwrite it. Done.
You can also do this on the device itself, with some effort. I use X-Plore for that (in the ATV Play store). To open the file as a zip and copy the png inside that apk.
the correct folder inside the APK is: NvCustomize.apk/res/drawable-xhdpi-v4/
put the file there (within winrar or the file explorer on the device) and overwrite.
Step 5: Copy the modified NvCustomize.apk back to the /system/priv-app/NvCustomize/ folder and overwrite it.
Step 6: Check the permissions of that file. In X-plore you can long press the apk, scroll down and select permissions. There you must see 644 in the bottom right. Or all Read checked and one write (owner) checked. Owner should be root.
Step 7: Reboot!
Done.
Hope that helps!
Thanks, that certainly does help, but heavens is that convoluted for such a seemingly simple request.
http://freaktab.com/forum/tv-player...3728-tool-windows-androidtv-wallpaper-changer
I'm an Android Developer and I need a tool support push pull data to mobile base on ADB commands. I search xda forum and found a tool at here: https://forum.xda-developers.com/showthread.php?t=1821601 .
But it have some problem and i developed a new tool with some advance features:
Attacted new adb version, high speed transfer for Android 7 or newer.
Support push, pull for multi files/folder.
Show more information of files/folders and sort data by name.
Don't freeze with large data.
Note: Current only support Windows.
Download: AndroidAdbFileExplorer.7z
XDA:DevDB Information
AndroidAdbFileExplorer, Tool/Utility for the Windows 8 General
Contributors
codinginthebigcity
Version Information
Status: Testing
Current Beta Version: 1.1.1
Created 2017-05-12
Last Updated 2017-05-12
Thank you for your app. Works very good.
Needs multi-file pull.
I tried to access /data so I clicked 'back' and everytime I choose a folder it trims 3 firsts symbols from selected folder.
Example:
I select folder named 'system' and in path I get /tem
I select folder named 'misc' and in path I get /c
I select folder named 'config' and in path I get /fig
I cannot edit filepath as it is not editable.
Please fix this
this is the only such application works!
broken and unusable. keeps thinking date and id is a path variable on every command,
This tool is lovely! Used it to move a ton of files from my Pixel on Pie to my PC so that I could do a full wipe and install of Android 10, then moved the files back. The speeds seem to be at least 10x faster using this than MTP over USB. Thank you so much!!!
works great for android tv.
Thanks broman
Thanks a TON !!!!!!!!!!
I used this software to backup various folders from the internal storage of my Moto G5 Plus and it worked flawlessly.
And the copy speed is too good to be true (but it is)
God bless you
This is the best method to transfer big amount of data from your phone. I had 35GB of photos and videos and this app transfer that quick and without any data corruption. MTP is not even close to that method. Thanks a lot!
FYI: I think this tool unfortunately doesn't really work under Android 11 any more, probably due to the new restricted storage access design by google.
Running an Pixel 2 with Beta RC3 and some files and folder won't be shown. For example the "camera" folder under "dcim" wont show at all.
Other files under downloads: some show, some don't.
Maybe you could look into it and fix it with an update? Was immensely usefull for copying pictures.
Thanks for your great work
Link/url is not working.
If can fix please.
Or if any other better File explorer after 3 years.
A new link would be great for me, too.
Anyone saved a copy of this? Also looking for a link
giant59 said:
Anyone saved a copy of this? Also looking for a link
Click to expand...
Click to collapse
Found it on an old computer for you.
I still prefer using this app instead of "Android Studio", especially if I'm only using Android Studio just for file transfer (overkill 800+ megabyte download) whereas "Android ADB File Explorer" is less than 1 megabyte. I also find it a lot easier to move directories with subdirectories with "Android ADB File Explorer".
Android ADB File Explorer MEGA download link (file is untouched from original download in 7z): https://mega.nz/file/vhpFiQwb#PngUnnspu6VA2enWCN9t06kGYcWkugsA1qWXswKjbTY
I've converted the original 7z file to ZIP for attachment to this post. No other changes were made.
Edit: I don't have any issues on Android 11 moving multiple files and directories with this. Much, much faster than MTP
Edit 2: I encountered the Android 11 issue with missing subdirectories. I just copied the parent folder and the subdirectories that weren't displaying in "ADB File Explorer" still copied over anyways.
ninjæon said:
Found it on an old computer for you.
I still prefer using this app instead of "Android Studio", especially if I'm only using Android Studio just for file transfer (overkill 800+ megabyte download) whereas "Android ADB File Explorer" is less than 1 megabyte. I also find it a lot easier to move directories with subdirectories with "Android ADB File Explorer".
Android ADB File Explorer MEGA download link (file is untouched from original download in 7z): https://mega.nz/file/vhpFiQwb#PngUnnspu6VA2enWCN9t06kGYcWkugsA1qWXswKjbTY
I've converted the original 7z file to ZIP for attachment to this post. No other changes were made.
Edit: I don't have any issues on Android 11 moving multiple files and directories with this. Much, much faster than MTP
Click to expand...
Click to collapse
MD5 Hash Matches
Hash: 22c12aaa9c47bee6e5ed0f3887969883
Is it still being maintained? I hope someone can add in the option to connect to ADB over WiFi (probably just another input field for IP address and change the adb connect command)
HRSE said:
Is it still being maintained? I hope someone can add in the option to connect to ADB over WiFi (probably just another input field for IP address and change the adb connect command)
Click to expand...
Click to collapse
The developer of this utility hasn't logged into XDA in over four years, so my guess is that this isn't being maintained. However, "codinginthebigcity" has updated their "Watch Navigator" app in the Google Play store as recently as February 2021. So they may still be active in Android development. Their email [email protected] is listed in that app description if you want to pose your feature request directly to them.
Well the link is dead, so much for this.
Toothless_NEO said:
Well the link is dead, so much for this.
Click to expand...
Click to collapse
Did you try the re-uploaded link or attachment four replies up?
*edit* deleted thread. Unfortunately this doesn't fix it. QFIL then flashing EUI ROM 14s and then upgrading to a newer EUI ROM or device firmware update then custom ROM is the only true fix.
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Iceee44 said:
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Click to expand...
Click to collapse
Heyyo, hmm darn that's unfortunate... Well, I have a test build of LineageOS 15.1 for the Le Max 2 with the calibration fixes in place and same with the upcoming official weekly build of LineageOS 14.1 for the X2 this Saturday. It's up to you which you would want to try. Hopefully one of them will work for you.
If not? I'm unsure what else could be causing the issue then hmm...
Hey thanks for reply!
I don't why, but something worked!
I got the splitscreen bug, then I flashed the recovery to the newest twrp (the blue one, don't know which version, but I will look it up). Then I wiped everything and install your fix. Result = bricked. Another try with one flash 2.0 and no error from flash. Fastboot recovery flash and everything was perfect.
I think it was luck, but my leeco le max 2 is repaired :victory:
Wow that's lucky! Congrats on fixing it!
May I please ask what happened to cause the brick? I've heard of device bricking but haven't seen an exact answer as to what unfortunately caused it.
It was totally my fault... I Format my data...and no image on storage... And one flash did the screen problem, maybe the program doesn't decompress a file finally... I decompressed the qfil data two times... The first time I got an error, after full decompressed everything...
Ah if you format data without any ROM on the device you can always use a PC and USB cable to do this...
adb push NameOfROM.zip /sdcard
Which will copy the zip file to the root of your data storage. Same can be repeated for Gapps or Magisk, etc.
I tried to push a 1,8GB file...
But after 2 hours it wasn't transferred, so I found the software and this is much easier.
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
ThE_MarD said:
Heyyo, this is a TWRP flashable zip file to replace the broken formatting on the qdcm calibration xml files for the display panels used in the LeEco Le Max 2
Click to expand...
Click to collapse
Which bug your fix is intended to fix? Do you mean this: https://youtu.be/3yXnrkfsJMI - I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
oneNight1 said:
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
Click to expand...
Click to collapse
For both of these questions the hopes is that the main issue with most people who unbrick their devices having screen issues is due to calibration settings being lost which this in theory should restore as it would have XML files with proper formatting unlike before where stock EUI ROM for the Le Max 2 had broken calibration XML files.
In theory if the black crush issue is also a calibration issue there's a chance this could also fix it... But still, I haven't really looked into that as I was mainly looking for a better solution for those unfortunate people suffering from unbrick device woes. If it fixes it? Cool... If not? Then I'm not too sure. Calibration files could potentially be modified to fix black crush if the issue is in there that LeEco never addressed.
giaur said:
Which bug your fix is intended to fix? Do you mean this:
- I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
Click to expand...
Click to collapse
How do i view the config files and transfer them to my computer to compare them to yours? I enabled usb debugging, thinking that would let me see everything but when i connect to my computer with MTP mode i can only see standard files, not all the linux config files etc.
(edit: I tried using adb shell and i could view the root directory but it wouldn't let me access the config folder - permission denied. Do i need root access? If so, how do i get it temporarily and then remove it once i have transferred the files? I can't just run adb as root because you need root on the phone apparently).
Also i did a search of the available EUI x829 source (http://opensource.le.com/ or http://opensource.le.com/ or https://forum.xda-developers.com/le-max-2/how-to/source-code-available-t3482334 )and i couldn't find those xml files. Are they generated by the OS or something?
To me it seems like the files are probably already formatted correctly on my particular phone as changing the colour mode does appear to function. However they obviously seem to be not calibrated properly (or intentionally calibrated very badly).
I wonder if it only reads these files on boot? Otherwise i guess an application could be made to interactively adjust them.
I wonder if KCAL uses these files.
However from looking at how large the data is and also the mention of LUTs (lookup tables), it would seem that this is actually more advanced than kcal? And could potentially give proper screen calibration if using a colourimeter etc?
Of course, more than one profile would be necessary for different brightness levels though.
But anything is better than nothing.
It is definitely to do with the eui colour mode settings because if you go to google translate and translate the names in for each profile, they match up with colour mode options.
These are part of EUI ROM as I did mention the XML formatting is broken on all the EUI ROM versions I looked at.
You can use an Android ROM extractor like this to open up EUI ROM and see the files yourself if you'd like.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
oneNight1 said:
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
The way the XML formatting is? Calib_Data is supposed to house the entire XML file to let QDCM know where the calibration data starts and ends... So on the broken EUI ROM XML files it only has an end and never loads the calibration data.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
Click to expand...
Click to collapse
Heyyo, it's definitely a formatting error. XML standard has open and close brackets.
For example, the OnePlus 5T
https://github.com/TheMuppets/propr...b_data_samsung_s6e3fc1_cmd_mode_dsi_panel.xml
Or the Xiaomi Mi5 (Gemini)
https://github.com/TheMuppets/propr...calib_data_sharp_fhd_cmd_incell_dsi_panel.xml
As for viewing the files on your phone? Yes you would need root and a root file explorer.
Magisk, SuperSU, KingRoot or such all work for root but some versions of EUI ROM have issues.
For root enabled file browser? Amaze works... Amazing. Just get it from the Play store and then in settings enable root explorer.
For uninstalling root please Google the uninstall method to whichever root method you use as they are all different.
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
oneNight1 said:
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
Click to expand...
Click to collapse
Write this in the terminal.
Code:
cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info | grep panel_name
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
oneNight1 said:
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
Click to expand...
Click to collapse
You should notice this does not work, garbage screen is there even with this fix applied. I have it all the time on latest Lineage 15.1.
Okay I checked in
Code:
system/etc
and I do have the files. They are formatted as
Code:
<Calib_Data />
too.
Why does your github page say that they should be in
Code:
config/qcdm
???
Anyway, I flashed your zip to see if it would make a difference but it didn't help with the black crush sadly.
Although maybe modifying the calibration data would - but of course we would need to understand the format.
I checked my TWRP backup image (you can just browse them with 7zip) and they have the same empty tag too.