hi all, i know this is a developers' community but it's also a unique source of information on related matters so inevitably here i am (an end user)
system:
pc: windows 7 x64 pro os
phone: samsung gts-5300 (galaxy pocket), android os (gingerbread xxlj4), ('rooted' following these instructions)
question:
is there a way to be able to manipulate files in the phone through usb cable with a windows program (like a file manager)?
or at least can it be done using console commands?
note that by 'files' i mean android os files too
the issues:
'rooting' that phone does not actually grant root access to the system files but merely grants access to the su app and a glimpse of the system files
so yes we say it's 'rooted' but you can't actually pull any system file to a windows folder for example bcz you don't have the permissions required
i have installed numerous applications, on the pc and the phone, android sdk, android commander, qtadb, droid explorer, adb insecure, rom manager so i suppose that if someone gives me a set of steps i could hopefully quickly reply the problem that comes up on each step (obviously i don't think there is a quick solution to this, i know im an optimist...)
as far as i can understand, adb insecure should be the solution to this problem for similar devices where 'rooting' is not actually rooting, but im having the already mentioned and i suppose resolved issue of it causing the usb debugging mode to go off, and the problem is noone in the related thread actually mentions how that problem is overcome
thnx for your time
Hi there,
I finally decided to root my Note Pro (P900), which is just 10 Days old (refurbished tho, so no warranty issues).
My Backstory (only read if you are bored
The main Reason for me is privacy. Coming from a Xiaomi Android Device with its excellent Permission Manager I was shocked at the Permissions some Apps require, that cannot be changed.
I did my research and tried a relatively unknown option named "Appguard". (Google actually removed it from the PlayStore after a short period of time, still available from their Website). This app was developed by a IT Professor at a german university with the help of his students. It allows to manage app permissions on the fly for installed apps and doesn't require root. However, this requires to reinstall the apps you want to monitor (no big deal) and it also allows apps to get PlayStore upgrades (great!). However as it functions without requiring root, there is no way to monitor system apps (including all the Samsung bloatware!).
I did further research and am now opting for the xPrivacy Plugin for the Xposed Framework.
This of course requires root to function. So here I am.
My device is a stock, unrooted P900 Wifi (32 GB) currently running 4.4.2 (KOT49H.P900XXUANI1). And, I'm on a Mac!
Bummer!
I understand that the current setup to gain easy root is using Odin on a windows machine (wich i dont have!)
I did some more research and found Heimdall. Its a multi platform tool that allows flashing Samsung devices.
Did anyone already try Heimdall and can maybe give me a hand on setting it up?
Does it even work with the P900?
Any other Methods rooting the P900 on Mac OSX?
Thanks a lot in advance!
For times when I need to use Odin I use windows in a VMWare virtual machine on my macbook. The VM image takes up precious SSD space on my rig though so when not in use I'll copy over the image to removable storage to free up space and then copy it back to the macbook when I need it.
Thank you for your reply.
Ive done some tinkering in the Meantime and it seems like at the moment there is no possibility for the P900 using Mac OSX.
There are actually two options (or one technique used by two programs). Both of them are open source, available for Windows, Linux and Mac and can be found on github.
One is Heimdall, which seems to work fine for older Samsung devices and actually uses a special kext to replace the samsung drivers on Mac OSX. It comes with a command line tool as well as a straight forward user interface.
The other one is JOdin3, a Java/Casual based program that can be used directly in the browser or downloaded and run as a java program. It also uses the Heimdall drivers, but offers a user Interface that looks and functions exactly like Odin, plus it inludes a "noob friendly" step by step process in the UI.
The problem is that the heimdall drivers are still having issues with newer samsung devices (including the note pro) preventing it to fetch the PIT file from the device.
As of now, April 23rd 2015 there is currently no way to root your device using Mac OSX
I'm currently downloading a virtual windows machine in virtualbox and will try to root that way.
I have no Windows license, but thanks to the Internet Explorer Team from Microsoft you can download already complete virtual Windows Enviroment for both OSX and Linux directly from the windows servers. For free!
Will report back once I rooted my device.
I successfully rooted my P900!
For those Mac Users out there interested:
I tried Virtualbox first, but it didn't work. I installed the exact same windows image (Win7 Enterprise) with VmWare Fusion and was able to detect my device using Odin with the latest official Samsung drivers.
I used Odin (v. 3.10.6) to flash TWRP Recovery (v. 2.8.6.0). You have to boot directly into recovery after flashing, otherwise the OS will revoke the custom recovery at the first boot.
I then used TWRP recovery to flash SuperSU (v. 2.46) from a USB Drive and made a full backup to the ext. SD card.
Currently downloading the Hyperdrive custom rom. Really looking forward to it.
Did you end up tripping KNOX?
Keep us posted on your progress.
KNOX will be tripped when you install a custom recovery via Odin.
So yes, my KN0X has been tripped.
I'm currently running the Hyper drive Rom with different kernels. Performance seems good and customization Options excellent. l have a problem with random shutdowns (not reboots), no matter what kernel l use.
Pretty sure It's related to the Rom setting/ Setup rather than root method. Some users of the Hyper drive Rom reported similar issues,' however l have to figure this out before university starts again on monday and i absolutely need the tablet for lecture.
If I dont find a solution for the shutdowns until sunday i might have to consider flashing stock + .Xposed
Hi,
I'm still using CD Receiver XC-HM82. There is a dedicated, quite old, application Control App which Pioneer released some time ago. After installing the app, when a CD receiver is discovered the app unfortunately downloads some data needed for managing this particular model.
Recently I reinstalled android system and when I try downloading those data it says "download failed". The reason might be that there are some issues on Pioneer server side or they've simply stopped supporting this device.
I have still one phone where this application is fully installed and working fine. I think that the data (downloaded from Pioneer servers to manage XC-HM82) are being store at: /data/user/0. However, I haven't rooted this phone.
The question. How can I retrieve data from /data/user/0 and what's maybe even more important can I create APK which will include all data needed for managing XC-HM-82 so I could still use this application to manage my CD receiver?
Thanks for any tips
I'll answer to my own post for users who might use it.
1.Turn on Developers option in your phone
2. If you use Lineage OS allow Debugging as Root or Root via ADB
3. Check all aps you have installed
adb shell pm list packages -f -3
4. To backup base apk (in my case)
adb pull /data/app/jp.pioneer.avsoft.android.controlapp-PIpLM2ikeE7WRs7X2TlOFg==/base.apk pioneer.apk
5. To backup data of the application (including packet for controlling particular model)
adb backup -f pioneer.adb -apk jp.pioneer.avsoft.android.controlapp
Please note: you'll have to accept this action in Android
6. You should received two files: pioneer.apk and pioneer.adb
7. To restore base apk (in my case)
adb install pioneer.apk
8. To restore data of your app (in my case)
adb restore pioneer.adb
Please note: you'll have to accept this action in Android
Eventually, you should have a feel backup of you app with data folder.
This procedure has been created based on this source page:
https://gist.github.com/AnatomicJC/e773dd55ae60ab0b2d6dd2351eb977c1 \
Thanks to "@AnatomicJC"
gregory_cooky said:
I'll answer to my own post for users who might use it.
1.Turn on Developers option in your phone
2. If you use Lineage OS allow Debugging as Root or Root via ADB
3. Check all aps you have installed
adb shell pm list packages -f -3
4. To backup base apk (in my case)
/data/app/jp.pioneer.avsoft.android.controlapp-PIpLM2ikeE7WRs7X2TlOFg==/base.apk pioneer.apk
5. To backup data of the application (including packet for controlling particular model)
adb backup -f pioneer.adb -apk jp.pioneer.avsoft.android.controlapp
Please note: you'll have to accept this action in Android
6. You should received two files: pioneer.apk and pioneer.adb
7. To restore base apk (in my case)
adb install pioneer.apk
8. To restore data of your app (in my case)
adb restore pioneer.adb
Please note: you'll have to accept this action in Android
Eventually, you should have a feel backup of you app with data folder.
This procedure has been created based on this source page:
https://gist.github.com/AnatomicJC/e773dd55ae60ab0b2d6dd2351eb977c1 \
Thanks to "@AnatomicJC"
Click to expand...
Click to collapse
Gregory, thank you very much for your post!
First of all, I learned that I could stop checking my home network/router/settings etc.. to find the cause of the failing download.
I have the bluray player Pioneer MCS-FS232, with the controlapp working on my tablet.
I want to transfer the app to my phone.
I followed your steps:
Pulled the apk and backed up the data
I re-installed the app with adb install, and I restored the data with the commands above. Device report success after restoring data.
Unfortunately the app persists in asking for a download (also after restarting device). I tried also on another device, same result.
Could it be that the data restore command do need more specifications?
Thanks in advance for your reply...
Ptr
PS: the full command for step 4 would be (in my case)
adb pull /data/app/jp.pioneer.avsoft.android.controlapp-HjWUmVnui7FpTk0qKpQ3Ow==/base.apk pioneer.apk
you might want to add
adb pull
to your text in step 4
Thanks PtKt for your post and correction regarding "adb pull" missing.
There's no problem with base apk:
Pioneer ControlApp for Android - APK Download
Download Pioneer ControlApp apk 4.1.0 for Android. ControlApp is an application for corresponding Pioneer Products control.
apkpure.com
The thing is the data files (downloaded from Pioneer servers when it was still possible). What's the version of system: on a tablet and phone?
Recently, I realized that this method works on Android 9-11 but not on Android 7 cause there's a different folder structure. It recognized CD receiver but crashes when trying to connect to it.
Hello Gregory,
1. first tried it on my phone (where I had the app, but deleted it ( ). Android 11. This is the taarget-device. Not rooted. APK file installed with adb succesfully
2. when this did not work I tried on a tablet (rooted Asus transformer tf701t with timduru android 7). installed APK, date reports succes, but no working app.
3. device where the app works is Huawei tablet with android 10 (not rooted)
4. My computer is an old IMAC with Ununtu 20.4 lts
I tried to open the pioneer adb file, only partly accessible and only 5 lines.
I checked Androi/data/jp.pioneer.avsoft (etc), on my android 7 tablet, there is a map ' files' but without files.
tbc, Ptr
I'm not so advanced in this matter, but up to Android Version it's about folder /data/data/jp.pioneer... (and so on). You can't access it without root. Maybe you can do that via TWRP on Android 7 on later version it's an issue in easy way. Other solution is to use Magisk to manually copy needed files.
I'm not sure if referring to the system version different files were downloaded from Pioneer's serves. Unfortunately, I don't know.
gregory_cooky said:
I'm not so advanced in this matter, but up to Android Version it's about folder /data/data/jp.pioneer... (and so on). You can't access it without root. Maybe you can do that via TWRP on Android 7 on later version it's an issue in easy way. Other solution is to use Magisk to manually copy needed files.
I'm not sure if referring to the system version different files were downloaded from Pioneer's serves. Unfortunately, I don't know.
Click to expand...
Click to collapse
Aiai.... after a few days of efforts my conclusion was that you need root access to your source device.
And then I re-read your solution and I saw that I overlooked the last part of point 2 of your solution....
"2. If you use Lineage OS allow Debugging or Root via ADB." I did allow USB debugging but I missed 'as Root or Root via ADB'
OK, it is a pity, I'm not going to root my Android 10 tablet where the working app lives. Meanwhile I learned a lot and that's always fun....
Thank you very much for your work, if I come across another solution I will report here.
Ptr
Great. You're very welcome.
Hi guys. I have problem with this Control App from Pioneer too.
On my Android 11 phone is after starting the app visible only the loading screen or a black screen and nothing happend more.
On the old tablet with Android 5 run this app, but it want to download more files from the server, but that is not possible yet beacuse of severs shutdown? (it works well two months ago).
Can you please give me a advice how to run this app on Android 11 and share the downloaded files for my Android 5 tablet.
Because of this is using of my XC-HM72 very limited.
Thank your for every advice (My devices are not rootet).
Rdbc26 said:
Hi guys. I have problem with this Control App from Pioneer too.
On my Android 11 phone is after starting the app visible only the loading screen or a black screen and nothing happend more.
On the old tablet with Android 5 run this app, but it want to download more files from the server, but that is not possible yet beacuse of severs shutdown? (it works well two months ago).
Can you please give me a advice how to run this app on Android 11 and share the downloaded files for my Android 5 tablet.
Because of this is using of my XC-HM72 very limited.
Thank your for every advice (My devices are not rootet).
Click to expand...
Click to collapse
Hiya,
You won't download needed files (graphics or some scripts customized particularly for your XC- HM72) because there are no files on Pioneer's servers, anymore. If you don't have any device with fully working app you have to ask anyone who has it still working to export needed files (usually as "adb" file) for you then you just import it by a command:
adb restore exported_file_name.adb
Click to expand...
Click to collapse
and that's all.
Nevertheless, since Android 8 I think that the folder with user data files has a different location, so mentioned method should work for Android 8 - 11 (I haven't tested it on 12). That's all what I can suggest you.
gregory_cooky could you please share you date with adb file?Thank you
Rdbc26 said:
gregory_cooky could you please share you date with adb file?Thank you
Click to expand...
Click to collapse
There you go. Please unzip it and good luck!
Thank you for the file, but still without success. I tried adb restore pioneer.adb and on my android 5 tablet and still want to download files from innactive servers. The same I have done on my phone with android 12 and there is still the freeze or black screen :-( What now? Thanks
Rdbc26 said:
Thank you for the file, but still without success. I tried adb restore pioneer.adb and on my android 5 tablet and still want to download files from innactive servers. The same I have done on my phone with android 12 and there is still the freeze or black screen :-( What now? Thanks
Click to expand...
Click to collapse
I'm not much surprised about Android 5 cause it mightn't work. Unfortunately, I don't have any other news for you. I'm not even sure if my files were suitable for the model of yours. Further steps you should do by yourself. Maybe you'll find a solution and provide it for someone else who has the same CD Receiver as yours.
I've spend a lot of time trying to run the app for my old, but still well performing XC-HM71.
Luckily I've found old Titanium Backup (playstore) backups from 2015 and 2017. I successfully restored the app and settings on my forgotten redmi note 3 pro as root and old android were needed. If anyone is interested and want to try again, both backups are attached. Older app version is 3.5.0, never is 4.1.0. I'll recommend to start with older version, then restore just the newer app without data. It worked for me. Good luck.
But I've remembered the app a bit differently. Seems to be a bit useless, same can be done with remote itself.
Its just a bit faster to add internet radio stations, as browsing on unit itself is a bit pain in the backside.
XC-HM71 is a base version, no Bluetooth, Spotify or other currently standard addons, so really the Pioneer app do not have any real advantages.
Btw, I've had no luck with adb files from @gregory_cooky.
How to control my vsx 527 with control app? Can someone please help
Hi
I need files for Pioneer XC-HM81.
Can someone please help.
Good news!
I finally managed to transfer the needed Pioneer ControlApp data from my -non rooted- tablet (Huawei M5, android 10) to my -also non rooted- telephone (Samsung Galaxy A40, Android 11), based on gregory_cooky’s procedure in post 2 of this thread.
I tried it half a year ago (see above, my post 3) and gave up.
But a renewed attempt this week, learned me that I overlooked a crucial element: both devices need to have “USB debugging enabled” to operate the adb commands from my computer successfully.
Obviously, I misinterpreted step 2 in gregory_cooky’s procedure.
After enabling ‘developers option’ on both devices, you need to go to enable USB debuging . Without that, your devices are only partly accessible from your computer and adb commands will give error messages.
In detail: go to settings, scroll down towards about tablet or info telephone, look for software and then ‘buildnumber . Tap 7 times on buildnumber. this activates developers option. Go back to settings, you can now find developers option as the last point under settings. Tap developers option, enable it, look then for USB debugging and enable it. Do this on both devices.
Connect your source device (=device with a working ControlApp) to your computer. Open a terminal screen on your computer and type adb devices.
[email protected]:~$ adb devices
List of devices attached
P15YC3E10080000000007FC1881C0 device
Then proceed as described by gregory_cooky in post 2.
Be sure to have your source files (ControlApp apk and data) in the root of your home directory, otherwise adb cannot find it. Be aware this type of commands is capital sensitive, so if you ask for Pioneer.adb but the name of the file is pioneer.adb the computer comes with No such file or directory.
I use the ControlApp for my Pioneer MCS-FS232, which I can now easily operate from my arm chair. Volume, switch from CD to Aux or FM, etc.
Peter
It appears ControlApp has finally given up.
Looking if anyone has perhaps a copy of the source files.
ControlApp downloads the files from the following URL: http://www.pioneer.eu/files/support/Wr5Ch9makajA/smartphone_app/common/controlapp/sma/SmaHtml_14.zip
Note that this is a HTTP URL, so can easily be faked for the device, however need the ZIP. Used to have it, now it's gone
hello,
would anyone have a working adb for Pioneer X-HM72 please?
Hello,
We constantly have to prepare new tablets by connecting google accounts, installing apps etc. Maybe there's some tools for this? I can see that you can install apps with adb but what about google account? All devices are using same account.
Ideano said:
Hello,
We constantly have to prepare new tablets by connecting google accounts, installing apps etc. Maybe there's some tools for this? I can see that you can install apps with adb but what about google account? All devices are using same account.
Click to expand...
Click to collapse
No, that requires physically signing into each individual account on each individual device. This is required because you are signing in over the Google network(external to your device), not just signing into the device itself.
There is maybe one exception but it would only work if all of the devices were rooted or had a custom recovery installed. In the case that all of the tablets are the exact same specific model number, you could physically sign in to the Google account on one of the devices, then install TWRP on that device, then boot into TWRP and use the Backup option to create a nandroid backup, then install TWRP recovery on all of the other devices then place a copy of the backup on a external sdcard or a USB then, on each device, one at a time, insert the sdcard or USB then boot the device into TWRP then use the Restore option in TWRP to restore the back that is stored on the USB, this will flash an identical copy of everything that was on the device used to create the backup. Do this with each tablet and they will be exactly the same down to every single file that was on the first device.
In the case that all of the tablets are not the same, it would require rooting each of the devices then signing into the Google account on one of the tablets then locating where the files associated to the Google account are stored, copy those files and store them on your PC, then, using adb connect each of the devices to adb one at a time and use adb push commands to push the files associated to the Google account to the folders they belong in. You could even create an adb batch file to automate the adb push commands. You could even include the apps that were downloaded and installed by the user and use adb batch file to automate the installation of the apps but this may not work if the devices have extremely different chipset or SOC.
You may be able to simplify the process more than I described if you do a little research, use some thought and use some creativity.
All in all, virtually the same amount of work as just physically signing into each device and installing the apps and data from a Google backup during the sign-in process, though, this process could cause issues on devices that have different architectures if device settings are included in the Google backup and restored on incompatible devices.
Droidriven said:
No, that requires physically signing into each individual account on each individual device. This is required because you are signing in over the Google network(external to your device), not just signing into the device itself.
There is maybe one exception but it would only work if all of the devices were rooted or had a custom recovery installed. In the case that all of the tablets are the exact same specific model number, you could physically sign in to the Google account on one of the devices, then install TWRP on that device, then boot into TWRP and use the Backup option to create a nandroid backup, then install TWRP recovery on all of the other devices then place a copy of the backup on a external sdcard or a USB then, on each device, one at a time, insert the sdcard or USB then boot the device into TWRP then use the Restore option in TWRP to restore the back that is stored on the USB, this will flash an identical copy of everything that was on the device used to create the backup. Do this with each tablet and they will be exactly the same down to every single file that was on the first device.
In the case that all of the tablets are not the same, it would require rooting each of the devices then signing into the Google account on one of the tablets then locating where the files associated to the Google account are stored, copy those files and store them on your PC, then, using adb connect each of the devices to adb one at a time and use adb push commands to push the files associated to the Google account to the folders they belong in. You could even create an adb batch file to automate the adb push commands. You could even include the apps that were downloaded and installed by the user and use adb batch file to automate the installation of the apps but this may not work if the devices have extremely different chipset or SOC.
You may be able to simply the process more than I described if you do a little research, use some thought and use some creativity.
All in all, virtually the same amount of work as just physically signing into each device and installing the apps and data from a Google backup during the sign-in process, though, this process could cause issues on devices that have different architectures if device settings are included in the Google backup and restored on incompatible devices.
Click to expand...
Click to collapse
Wow thanks for detailed answer.
They usually are the same unless when we start to replace them with new models. I was thinking about backup/restore but yeah then I have to root every device and they also come with some software preinstalled with different user accounts so that won't work.
Tbh I was certain that such software should exists. I'm working at the trucking company and even though we are far from biggest even in my small country it does take significant time to configure every tablet manually so I imagine bigger companies must have separate person only for this.
Ok then I'll try to play with adb I found that you actually can install apk, open playstore and fake clicking install so I assume I could automate google account connection and etc. Although it won't be as smooth as just plugin it and clicking cofigure.