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.
Related
As it says in the subject line, I'd never felt compelled to root my Shield Tablet buy now wishing I had. It is on the latest 5.1.1 update and I want to transfer my data in such a way as go clone it onto the new tablet I've received due to the recall.
Is there anyway of making a Nandroid backup and loading recovery without unlocking and losing the data I want to keep or another alternative method such as the built in adb backup solution.
Thanks for the assistance in advance.
I managed to use Helium (Carbon)
But remember having several issues:
First step was getting the desktop app to recognize the tablet in debug mode. In the end drivers need to be reinstalled with 'have disk'.
Think i used the ones from nvidia website
Also afterwards Helium had trouble detecting existing backups. Had to install all apps manually on the new tablet, 'fake' backup everything again, then replace all .ab files with the ones from your 'real' backups. Some details here.
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - user should be able to execute fastboot commands
Thanks
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
SaadatM said:
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
Click to expand...
Click to collapse
Not sure if I understand what you mean with "local terminal". .. Do you mean a shell spawned from regular app running on your phone?
The point of the app is to perform some privileged tasks that cannot be performed by regular apps on non-rooted phone.
You should be able to perform these tasks without the need to install ADB on your PC, or even without having a pc currently at your hands(e.g., if you're on-the-go).
Additionally, you should be able to perform a lot of these tasks with a couple of taps (instead of typing shell commands).
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
crunchybutternut said:
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
Click to expand...
Click to collapse
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
bugjaeger said:
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
Click to expand...
Click to collapse
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
Click to expand...
Click to collapse
If you made adbd listen on specific port before(adb tcpip 5555), then yes, you can issue adb commands from the app to the same device running the app.
bugjaeger said:
If you made adbd listen on specific port before(adb tcpip 5555), than yes, you can issue adb commands from the app to the same device running the app.
Click to expand...
Click to collapse
I believe you'd need root to do that though, right?
crunchybutternut said:
I believe you'd need root to do that though, right?
Click to expand...
Click to collapse
No, I don't think you need root. I used it a lot on my non-rooted Nexus 5x and once on an old Asus Zenfone during testing and it was working as expected.
That's great . I was just wondering if there was something like this already out there. Thanks for your efforts and I hope you are prosperous.
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I've added the possibility to copy apps/APKs between phones
Thanks
Click to expand...
Click to collapse
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
lodk said:
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
Click to expand...
Click to collapse
So you tried to connect your phone (with Bugjaeger installed) to you wife's phone via USB OTG cable? And the phone with Bugjaeger app doesn't detect any ADB device connection (or other dialogs pop up)? Did I understand this correctly?
You might need to temporarily disable the other protocols that Android offers via USB so that there are no other dialogs popping up (on your wife's phone). On my Nexus with Android 8, I can go to Connected devices -> USB and switch it to only "Charge this device" (so PTP or the other stuff is disabled).
In case there is some other app doing stuff with ADB USB devices, you might also need to change your defaults so that Bugjaeger can handle ADB USB devices.
Then you also need to make sure that Developer options are enabled on your wife's phone (and USB debugging of course).
Once you successfully connected and authorized the phone, you should do the following
- In Bugjaeger app switch to Packages tab and click on Add button top right (the button with the plus sign). Then you should pick the package disabler APK. This should install the package to your wife's phone
- Switch back to Commands tab (first tab) and either click on plus button in top right or shell into the device with the floating action button ("<>").
You can then activate the device owner with something like this
Code:
dpm set-device-owner disabler.package.name/.DisablerAdminReceiver
*Note that I don't prefix the command with "adb shell" here
When activating device owner you also need to make sure that there are no other accounts configured on your wifes phone (e.g. google account) because otherwise it probably won't work.
You can also check my blog post where I describe how to activate device owner with Bugjaeger in more detail (at the end of the blog post)
https://sisik.eu/blog/android/dev-admin/set-dev-owner
Hope that helps
going to give this a try thanks will post later with results,
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Crisal said:
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Click to expand...
Click to collapse
Hi,
Unfortunately, I don't think my app can help you in this case.
Hi, thanks for the reply. Do you know a way to help me?
please help me!!
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - for now the user can dump bootloader info
Thanks
Click to expand...
Click to collapse
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
I don't have any wear os watch at my hands right now and I can't test it at the moment. Is the APK compatible with the watch? If you're able to establish an adb connection between Bugjaeger and the watch, try to check the "Packages" tab in Bugjaeger app. There's a "+" button in the top toolbar, which allows you to select apk for installing on the target device.
The official docs are showing how to establish ADB connection with the watch - https://developer.android.com/training/wearables/apps/debugging
In Bugjaeger you then need to tap the connect button (plug with a plus sign in top toolbar), type in the IP address of the device, and tap on connect button. Both devices should be connected to the same WiFi network to make this work.
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
lindser112 said:
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
Click to expand...
Click to collapse
Perfect :laugh:
I. INTRO AND SUMMARY: I decided to experiment with rooting on this phone, which was lying unused. I was successful, using KingoRoot but from a PC (the Android .apk version did not work for me). Below are the details.
II. NOTE ON MODEL: The "BLu Life One" nomenclature does not identify a specific phone since there were several branded with this name, sometimes but not always including extensions to the name like "XL." This guide is for the phone that, under Settings > About Device gives the following information: Model BLU LIFE ONE; Processor Qualcomm Technologies, Inc MSM8916; Android Version 5.0.2 (I had done an OTA update from 4.4.4 at some earlier point); Kernel Version 3.10.49; Build Number LRX22G release-keys; Custom Build Version BLU_X010Q_V11_L_GENERIC 20-01-2016 16:15. This phone is described at gsmarena dot com / blu_life_one_(2015)-6930 dot php with pictures, if you need to make sure.
III. PROCEDURE I FOLLOWED:
PART A: On Android Phone
1. Do a factory reset of the phone (after saving anything you may want from the phone beforehand to a different device, of course). Settings > Backup & reset > Factory data reset.
2a. Normally, I would do one more OTA update to get the latest Android version (if there was one) before rooting via Settings > About Device > Wireless Update. However, this crashed consistently and silently. My guess is that BLU changed their update server and the older models can no longer communicate with them, and the OTA update attempt fails (not very gracefully).
2b. When doing the initial setup of the phone coming out of reset, do NOT setup your WiFi yet (otherwise it will automatically try an OTA update and be in an endless loop trying to do so, owing to the problem mentioned above, and your phone will never initialize). Just choose your language and skip all other steps like WiFi, Google account login or setup, etc.
3. Once you have successfully initialized your phone in a clean state, then turn on WiFi and connect to a reliable network.
4. Become a developer on your Android (Settings > About device > Touch "Build Number" 7 times). Turn on USB Debugging (Settings > Developer options > USB Debugging).
5. Go to Settings > Display > Sleep and change to "30 minutes" or "Never" (you can change it back later, but I found the root process would suspend if the phone entered sleep).
6. Open the Play Store, set up your Google Account and download the app Root Checker (Joey Krim version), recommended by KingoRoot to verify that the rooting was successful. You may want to create a separate Google account for this purpose, otherwise if you connect to your primary one, it will attempt to sync your email, calendar, and all sorts of other stuff to your phone from your Google account, which you may not want at this point. Or you can try to disable all sync and all automatic App update from your Google account and Play Store as early in the process as it will let you.
PART B: On PC
** NOTE: You may want to read the section below IV. PROTECTING YOUR PC before doing this part! **
7. Connect your Android to your PC via the USB cable. It may try to download various drivers, some of which may be successful and others not, but don't worry if some driver installations appear to fail--Kingoroot apparently has its own ADB drivers that it installs during the early part of the rooting process.
8. On your PC, go to kingoapp.com (avoid downloading from other sites), and click on the "Download for Windows" link to download kingoroot.exe on your PC (I earlier tried the "Download for Android" link to sideload the KingoRoot.apk file, but this version stalled at 90% and did not work--the Windows version is stated as being more reliable and this turned out to be true for me).
9. Run kingoapp.exe on your PC with your phone connected, and let it install. Uncheck the box "Install Recommended App" when it appears and allow it to run. (The mysterious "Recommended App" turns out to be a sponsored "SuperBattery" App that's pretty useless. If you accidentally allow it to install, you get the option to uninstall it later.)
10. Accept installation of the Kingo Link App over the USB. Google "Play Protect" will try at least twice to warn you about the danger of allowing this, but if you want to root, you need to accept it.
11. The program will prompt you to enable USB Debug mode if you didn't already do it, then will install an ADB driver (which Windows Plug and Play was unable to install successfully in my case). You will then get a prompt on the phone to accept USB connection from the computer with signature specified. Check the box "Always Allow from this Computer" and allow.
12. Finally, the screen "BLU LIFE ONE / Root your Android. Make it more interesting!" screen will appear on the computer with a ROOT button. This means that the drivers installed properly and the KingoRoot PC program is communicating properly with the phone. Press the ROOT button, after unchecking the box "Install recommended app."
13. At various points, Google will ask to "check device activity for security problems, and prevent or warn about potential harm. / Learn more in the Google Settings App," which I always declined.
14. At various points, the phone screen will turn white and then return to the home screen. Finally, the computer should show "ROOT SUCCEED / Would you make a donation to support us?" You can close the PC program at this point.
PART C: On Android Phone
15. Reboot the phone (NOT a Factory Reset, just a simple Reboot). I found the Google Play would not work without this additional reboot.
16. Run the previously downloaded Root Checker App. A prompt from KingoRoot's SuperUser app will appear, asking you if you want to allow Root access to the Root Checker app, to which, of course, you must say "Yes." It should confirm that you have root access.
17. Do NOT uninstall the KingoRoot SuperUser App, otherwise you will lose root access. (It is possible to replace it with others like SuperSU, but that must be done and run FIRST, before uninstalling KingoRoot's SuperUser. I did not bother with replacing KingoRoot's SuperUser with another.)
IV. PROTECTING YOUR PC
Since I'm wary of installing software on my PC from sources that are by definition hacking sources, I took the following steps to protect my PC and it's data. You may wish to do the same, even though I have not read reports of KingoRoot, if downloaded from it's official site, containing Malware or covertly installed Adware. It IS suspicious, however, that the ADB driver installed by KingoRoot advertises itself as "Name: Google, Inc., Publisher: Finger Power Technology Co., Ltd." Clearly naming the driver "Google, Inc." is a way to reassure people who see the name "Google, Inc." on the screen without realizing that it's not in the "Publisher" field--one wonders why they would bother with this deception if there weren't an ulterior motive behind it.
1. I used an old netbook PC for the rooting, with no important data on it. I did NOT use my primary PC with my important data.
2. I ran the program under a non-administrative username. Of course, I had to provide an administrator password at two points, but at least I knew each time that administrative access was being requested.
3. I uninstalled the KingoRoot program from the PC after I was done with it and deleted the downloaded executable installation file, and confirmed that the installation folder was deleted as well.
4. Lastly, I did a system Restore to a point earlier than my installation of the KingoRoot program (you may want to create a Restore Point for this purpose beforehand), so that any other system files accidentally or intentionally corrupted or installed by KingRoot would also be restored to their original state or removed. Note that while System Restore often uninstalls programs that were installed after the Restore Point you go back to, it did NOT do so for KingoRoot.
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
ravensfan8448 said:
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
Click to expand...
Click to collapse
So you're sending the phone back to Google....why? Because it came without the stock OS? It's hard to believe that the phone came with AOSP already installed...that's awesome if it did since AOSP is usually something that you have to load yourself.
So I'm sure you understand that your bootloader has to be unlocked in order to boot TWRP yes? Because typically when the bootloader is not unlocked the phone will reject the recover and shut down. So make sure your bootloader is unlocked in developer settings since you have a Google verison.
Sounds like your partitions are being weird when plugged in to the PC and its only seeing some of the partition. I would try to reinstall the driver and see where that gets you.
If you're concerned about your APKs, I would just use Titanium Backup and backup all the APKs to storage and then pull that from the phone using PC.
Hope this helps.
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?