Hi everyone
My first post here, hopefully someone can help me.
I have (had) a HTC Flyer P510e tablet. When I got it I went through the process of rooting, unlocking, etc, and if my memory serves was running Andoid 2.3.4.
A while ago I dropped it, broke the screen and rendered it useless. Digitizer not responsive, so I cant unlock the screen, or quite frankly do anything with it.
There is some important info on there I need to get off. I have already managed to pull off the contacts, calender, documents, apk's i needed, etc. The problemis as follows:
I have been using Garmin Mechanic to record all my fuel purchases, and PhoneTrack Explorer to record mileage use, site time, etc. I have backups of these apps and the data from January, but I am needing the Feb & March data from both these apps.
I was previously using TitaniumBackup for this, and from examining the backup files I can see the databases for these apps were stored as follows:
\HTC Backup\External\data\titaniumbackup\co.uk.journeylog.android.phonetrack-20130110-124837.tar.gz\co.uk.journeylog.android.phonetrack-20130110-124837.tar\data\data\co.uk.journeylog.android.phonetrack\.\databases\
\HTC Backup\External\data\titaniumbackup\com.garmin.android.apps.mech-20130110-124624.tar.gz\com.garmin.android.apps.mech-20130110-124624.tar\data\data\com.garmin.android.apps.mech\.\databases\
I have tried various commands, sequences and other suggestions using ADB, none which have worked. Tthe failures I get on ADB commands mainly are Permission Denied when trying to issue the su or root command, read only or read errors trying to mount, browse or copy, etc, etc. I have followed about 15 suggestions from different XDA pages, other sites, and more, with no luck so far.
I have tried Moborobo, MyPhoneExplorer and APK Batch Installer, with not much luck.
Things I do have which could be of use:
I have done a full clockworkmod backup and have the current image files.
I have already downloaded the Android SDK kit.
Is there any way I can get hold of these files so I can submit my expenses? Is there an easy way to pull them using ADB?
I was considering if there was a way to use the Android SDK to create a virtual Android device, add the clockworkmod recovery to the virtual device, then use the image backups I have to restore my broken device's load, then do a backup or export of the information I am needing?
Any help or suggestions would be greatly appreciated!
Thanks very much.
Did you try to re-install the HTC drivers? What is the response if you type:
adb devices
If no device is listed, it might just be a driver problem. Or just try another USB port, or another computer (if available).
redpoint73 said:
Did you try to re-install the HTC drivers? What is the response if you type:
adb devices
If no device is listed, it might just be a driver problem. Or just try another USB port, or another computer (if available).
Click to expand...
Click to collapse
It's not a communication problem. adb devices does list the device serial number. adb shell launches the shell and I can browse around and perform various commands, but I am always getting the permission denied errors when I try to access the system protected folders, and those hidden folders.
Related
Hi!
Could anyone help steer me towards a solution please?
Or tell me if its impossible (and why).
I am trying to put together a script of some kind which I can use to do a basic rebuild of my Archos 70 after I have done a Full Reinitialization. I like to mess around installing all sorts of stuff, but when done, it's nice to reset and go
back to a clean machine.
As it's not rooted (yet?) I generally rebuild manually which takes ages.
Although a relative newbie at Android/Linux, I have worked with scripting
on mainframes and in the Windoze arena for many years.
The scripting requirement is quite simple, namely to install packages one by one from the SD card. Also to copy back Bookmarks, launcher setting etc
I am happy to work in any language which will work, but to date have just been trying with .SL (Bash?) scripts which run quite happily from within the SL4A environment or according to my theory, should work also from Android natively.
I envisage the script residing on the SD card and when invoked installing my launcher, Dolphin Browser, various other apps and games, then copying back the settings which I have saved (also by script) before the Initialisation.
Trouble is, I can find no simple samples which help. When I try, I can 'cp' stuff about and echo messages etc, but when I try to install, I don't really know where to start. I have tried just the name of the app package
'/sdcard/sdcard/packagename.apk', it replies 'permission denied' and if I try 'sudo package.apk', it says 'not found'.
I am assuming that the 'permission denied' is a good sign because it understands what I'm trying to do at least. But if I am allowed to do it myself, then surely my script should be allowed to do it?
I am quite happy messing around myself. But if anyone has any pointers
(sample scripts, which language/environment to use, etc.) I would be most grateful.
Sorry if this is covered elsewhere. I have searched but was unable to find much which helped. I am continuing the search!
Thanks in anticipation!
1. All normal installed Apps are installed in /data/app as the apk
2. Local/private data comes into /data/data/name.of.the.package
Both directories are ony accessible with root.
Hell again,
Thanks for your reply fzelle, but I'm not sure as to whether I may have explained it properly.
I am running 'Quick System Info' which is great, and it has a function to backup all the installed apps to a directory you can get at without root access. From there I have copied them onto the SD card.
I am not just trying to copy them into the working directory.
If I click on an app, it lets me install it without any problem.
I am trying to automate that part of the process, and I need the name of the software which does the installation, and how to actually give it the parameters for it to do the install. Although a Linux newbie, I don't really understand why, if I am allowed to install apps myself,
a script that I run should not be allowed to install them also?
Anyone got any ideas please?
Oops! - Sorry for that unfortunate typo at the beginning of my last post. Please read as 'Hello'!
No, i didn't understand you wrong.
You want to automate the installation of your std programs, and that normaly doesn't only include the apk but also the private Data.
And if you manually want to install this, you need root to be able to write in /data/data
If you just want to Backup/Install the apps, use appSaver from the market.
That has allready everything you need, and doesn't need root.
fzelle said:
1. All normal installed Apps are installed in /data/app as the apk
2. Local/private data comes into /data/data/name.of.the.package
Both directories are ony accessible with root.
Click to expand...
Click to collapse
Not entirely true.
I have some SSH tunnels set up on my rooted phone that use keys and a shell script to launch them, all set up with Better Terminal Emulator. The key and script files are located under /data/data/com.magicandroidapps.bettertempro/home. I wanted to use the same keys and script on my A70, so I copied the files from my phone to the same directory on my A70 using the terminal command line. Although you can't browse to the app folders under /data/data/, there is some ability to copy stuff into them. I guess the trick is knowing what and to where.
I've not used appsaver, but Astro will also let you back up and reinstall your apps all at once.
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
Today, I finally have found where to post for newbies, so I post, thought 4 hours ago I posted on androidforums.
Here is very difficult to operate with this site, and to use this site for with android devices is quite impossible. Only in windows, and not every comfortable. Anyway, I see, that is the first university on the net
Click to expand...
Click to collapse
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
lovestudio said:
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
Click to expand...
Click to collapse
I am sorry, so no one knows, on 3 sites, no one knows. let me know, then I shall not check every hour this post. I t`s better to know, that nothing possible, that believe that smth. is possible. thanks.
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
godhand_sh said:
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
Click to expand...
Click to collapse
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Davey126 said:
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Click to expand...
Click to collapse
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
godhand_sh said:
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
Click to expand...
Click to collapse
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Davey126 said:
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Click to expand...
Click to collapse
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
godhand_sh said:
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
Click to expand...
Click to collapse
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Davey126 said:
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Click to expand...
Click to collapse
Yeah! I did it! Thanks for the powerful busybox, which can continue to split large files even when it is interrupted by device restarting. With this feature I could pull any file out of a keeping restart device given there is enough disk space for storing the split files. The following shares my process & scripts used in the backup. Hope that helps others might meet the similar case.
1. move busybox in the device
adb push busybox /data/local/tmp/
adb shell chmod 755 /data/local/tmp/busybox
2. split the large file
adb shell /data/local/tmp/busybox split -b 300m /sdcard/DCIM/Camera/%%i /sdcard/tmp/split /*used in a DOS bat file*/
3.pull the files out
for /f %%i in (%1) do if not exist .\kindle\tmp\%%i adb pull /sdcard/tmp/%%i .\kindle\tmp\ /*used in a DOS bat file*/
4.combine the split files into what it should be.
cat splita* > a.mp4
Hei there!
I just encountered some suspicious behavior on my phone, and I suspect some kind of malware / rootkit.
Background Information
After I accidentally deleted some pictures, I've installed EaseUS MobiSaver to try to recover those.
The scan for deleted files found some of my lost pictures, but also quite some more!
Turns out there are dozens of pictures, respectively screenshots of very random screens like, setting up my clock, browser pages, browsing files, watching YT or VLC, opened apps and so on.
I've attached some of those below.
At first I thought those images are just some kind of framebuffer leftovers or something like that. But then I found that "rootSU.png" image which is baffeling.
Kaspersky, Sophos and Malewarebytes do not find any hints of a infection.
As for my phone / environment
Pocophone F1
PixelExperience 10.0
NoGravityKernel 1.4
Magisk 20.4
So for now my phone is offline, and I would like to investigate what's going on there.
Is there any way to scan the system from external over adb or something?
.
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
jwoegerbauer said:
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
Click to expand...
Click to collapse
Thank you for answer.
No, did not use any XIAOMI Root-tool. Rooting was done via Magisk.
But termux could give me some insight. :good:
Well, despite those suspicious files, I was not able to identify any odd behaving processes.
I guess it's time to wipe and reinstall.