Related
Hello all-
I have a dual booting pocket-size (well, largish pocket- about the size of a 2.5" portable drive) media player called the HDX Bone.
Here's a link a to a place where I've begun to collect info on the device:
NOTE: I am adding spaces to the links below because I am too new to add live links to a post.
h t t p : / / minimodding.c o m/tiki-index.php?page=HDX%20Bone
(info here is one firmware release out of date- android 2.1 is now out for it)
&
Here's a link to the forum where I have mostly been figuring out how the bone works:
h t t p : / / minimodding.c o m/tiki-view_forum.php?forumId=44
(oh and for completeness here's hdx's own forum:
h t t p : / / w w w.hdx1080.c o m/forum/viewforum.php?f=36&sid=f3c932441675e25a26e25c14db6fe431 )
But here's the pertinent details:
It uses a Telechips Soc TCC8900
It is an arm1176jzf.
It has 128mb ddr2 ram x 2 (256mb total)
It has 256mb nand flash.
You can install 2.5" harddrive- and must have an internal harddrive if you want to boot android.
It has an ethernet port, a usb out port, hdmi, & composite.
It dual boots.
The default bootup "voir/v012" is a linux bootup with a media-playing gui overlay:
uname -a
Linux (none) 2.6.28 #827 Wed May 26 16:14:12 CST 2010 armv6l GNU/Linux
The android bootup was 1.6- but last week they released 2.1 for it.
uname -a
Linux localhost 2.6.29 #169 Fri Jul 16 20:36:50 CST 2010 armv6l GNU/Linux
Here's the latest 2.1 firmware install files, archived:
h t t p : / / w w w .hdx1080.c o m/bone/firmware/HDXV012_android_20100719-102014.rar
When you chose to install android 2.1, it:
activates the initial boot process to ask you if you'd like to boot into android
repartitions your internal harddrive:
/dev/sda2 281.0M 90.5M 176.1M 34% /media/sda2
/dev/sda3 265.8M 40.5M 211.6M 16% /media/sda3
dev/sda2 is the core android system.
dev/sda3 is the data partition for android 2.1. it gets mounted on /data.
the sdcard is just an unwritable directory by default.
The boot process, as near as I can fathom it, works like this:
tccboot.rom (telechips bootloader) loads-
if you do nothing, linux.rom is loaded and the voir/v012 is selected.
OR you can use the remote control to select android.
If so, linux_hdx_android.rom loads and eventually hands off to the install on the harddrive.
ANYWAY, I am starting this thread for one reason right now: the device won't let me install certain applications. And other applications it installs, but they won't open/forceclose.
I think this is tied to:
the system is mounted as read-only to begin with.
and the sdcard is not a writable partition.
I have tried:
making the system rw at start through the init.rc
mounting an extra ext3 harddrive partition in the /sdcard through the init.rc
(hasn't helped)
All the applications that fail/forceclose mention on screen when opened:
android.process.media
Apps that fail this way include:
Facebook
Music
Meridian Media Player
Two other applications open, but won't work:
streamfurious- initiates process to stream, but then quits.
slacker radio - login fails, though credentials supplied are correct.
The application installation procedure is to put apk's in /data/app- then at bootup, it adds those applications to the system.
I have also telnetted in, remounted the system as read-write and copied apk files to the /system/app/
Some applications appear right away in the application drawer this way- others do not. I don't know why this is.
Apps that won't show up include:
Superuser
Better Terminal Emulator
(BTW, UniversalAndroot does show up and shows the device to be "rooted")
Anyway, I have telnet access. Busybox is installed.
Help/insight/advice?
How applications get installed- and how they get rejected- is a mystery to me.
Why I am getting these media playback related failures is also troubling.
And if this is a really bad place to ask these questions, because this device is not a phone, or because this has already been answered 1000 million times, or whatever, please let me know.
Thanks in advance for your help.
-wigout
O lord,
mods on high, please move my thread to:
Android Software and Hacking General
sorry.
-wigout
logcat shows:
Caused by: java.lang.IllegalArgumentException: There is no external volume Id : -1
for all the failed programs....
Now if I only knew how one might fix such a thing...
-wigout
So when I unmount the sdcard (my ext3 partition), I get some functionality back.
I can open the Music program, though it won't play anything because it can't find anything.
I can open the Meridian Media Player and browse to the extra partition mounted elsewhere (I am fine with that as a solution, though it doesn't fit in with the purpose of the sdcard in the Android OS). I successfully played a movie back this way.
So, is the lack of a:
/data/data/com.android.providers.media/databases/external-####.db
that was causing the sdcard/partition media related errors?
How can I properly implement an after the fact sdcard? It seems at minimum I need a volume id number like a proper sdcard would have.... though how do I garner one from a partition?
Anyway, thanks for listening.
-wigout
So....
Can you generate an external-####-sd.db after boot up? on the commandline?
Or am I on the wrong track here?
Busybox and DNS
Hey wigout,
I'm interested in getting the sdcard mount writable too in android 2.1 on the hdx bone. I followed your instructions for telnet and latest busybox, but would like to get busybox's wget working so I can dl directly to the hdx. Busybox's ping/telnet/wget/you name it all complain of a bad address, while the native ping resolves domain names into ip addresses just fine (of course so does the browser in android...)
Any luck getting busybox to look up a dns server?
HEN
sdcard problems
I worked around my dns issue but not in an elegant way. Next step was the /sdcard dir... symlinked it to /data/sdcard (file flags writeable) but no luck. Google specs say that the directory can be a symlink to writeable storage, but:
"Device implementations MUST enforce as documented the android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage. Shared storage MUST otherwise be writable by any application that obtains that permission. "
Somewhere in android guts this permission needs to bet set. You may have figured that out.
btw got Connectbot working -- it's a great ssh client app.
HEN
vold.conf?
Looking at this now... Perhaps telling it that the sdcard device is a hard drive?
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/tcc-mmc0.0/mmc_host/mmc0
media_type mmc
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun0
#for_mtp ums_path /devices/platform/dwc_otg.0/gadget/gadget-lun0
Hello wigout/HEN201,
I just ordered an HDX-Bone and thinking of having my own busybox build + Qt and a mix of QML/OpenGL to redo the movie browsing interface.
Would you be interested in participating ?
latest bone android 101224 support wifi and 3G now!!
Any updates on this?
HELP !
I need "Total Binary" dump of the HDX Bone.
It can be dumped from FWDN V7 utility - menu "Binary" - "Generate Total Binary by Device" - then "Start"
Before this you should install drivers and enter device in recovery mode.
To enter to recovery mode short "JS1" pins on board and connect usb to PC
A step-by-step Android installation guide for Nokia N900 Users
Things you will Need:
1: Your nokia n900
2: Any Micro SD card (i used a 2GB)
---------------------
For this installation you need to Enable all repositories from App Manager (you need to input those information manually and be precise):
The configuration below is for N900 up to firmware PR 1.1.1:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle
Components: free non-free
----------------------
The configuration below is for N900 for firmware PR 1.2:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle-1.2
Components: free non-free
-----------------------
The configuration below is for N900 for firmware PR 1.3:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle-1.3
Components: free non-free
------------------------
Second step :Install rootsh from app manager or from this site : http://maemo.org/downloads/product/Maemo5/rootsh/
-------------------------
Third step we will use X-terminal (here get your fingers ready )
basic commands used : root( to give root access) ls (list files in a folder or directory) mkdir (create directory) rmdir (removes directory this command is specially used if you Used any NITDroid before and created AND directory in the root of the phone) Ok lets get started Type in X-terminal :
root
apt-get update (to download packages needed make sure you are connected to internet )
apt-get install nitdroid-installer
y
y (if its asks again)
-------------------------------------
After this you have to download two files on your PC:
1st file : http://downloads.nitdroid.com/e-yes/gingerbread.tar.bz2
2nd file: http://downloads.nitdroid.com/nitinstaller/Packages/nitdroid-kernel-2.6.28-06_final1_armel.deb
-------------------------------------
Once you downloaded those files make sure you copy them to the root phone memory ( once you connect it to the pc tap the mass storage mode and just copy them to the phone memory for example lets say its H: just open H: and copy it there)or for other users they can copy it anywhere as long as they put the path correctly
--------------------------------------
After you have successfully copied the files open the x-terminal and typeNOTE:be precise and take care for space)
root
cd /home/user/MyDocs (cd(space)/home/user/MyDocs)
bzip2 -d gingerbread.tar.bz2 (bzip2(space)-d(space)gingerbread.tar.bz2) WAIT
cd /home (cd(space)/home)
mkdir /and (mkdir(space)/and)
cd / (cd(space)/)
mount /home /and (mount(space)/home(space)/and)
cd /and (cd(space/and)
tar xvf /home/user/MyDocs/gingerbread.tar (tar(space)xvf(space)/home.......or the path you put the file in
dpkg -i /home/user/MyDocs/nitdroid-kernel-2.6.28-06_final1_armel.deb (write this one like this as it here with all spaces / _ . -
-----------------------------------------------------------
Now You have to install two more updates to Patch some Bugs in the OS.
First Is Codec Update:http://downloads.nitdroid.com/e-yes/gingerbread_update1.tar.bz2
second VOIP update :http://downloads.nitdroid.com/e-yes/gingerbread_update2.tar.bz2
copy both files in directory like the before 2 files
------------------------------------------------------------
After downloading both the files Again open X-terminal and type
root
mount /home /and
cd /home/user/MyDocs
bzip2 -d gingerbread_update1.tar.bz2
cd /and
tar xvf /home/user/MyDocs/gingerbread_update2.tar
Make sure you install the updates correctly.
-------------------------------------------------
After the updates are installed you are done Installing Android Gingerbread On your Nokia n900 . just slide open your keyboard and reboot your phone. you will get a Dual Boot Option screen Select Nitdroid And Unleash the Gingerbread Power.
For more visit Nitdroids official wiki
Wow, i've been waiting for a step by step post. And some of the posts i read said it needs a minimum 4GB SD card. Will all the features work, i mean calls and internet with 3G with other basic phone features ? This is for my wife and all she does is to go to FB, calls and text Is the Market working ?
Thanks again for the lovely tip
zeus09 Thanks for reply .....for me calls sometimes work sometimes not i need to fix it, camera also is not working, otherwise everything is working fine but you can try it and see it wont brick your device i will work on 2.3.3 to fix those minor bugs here....try it and tell me whats wrong so i can develop it more
Oh yeah, I'm gonna have the phone charged fully now. Gonna give it a shot tomorrow morning. Wish me good luck man . Hope I will not brick it ha ha
hey man go for it dont worry ! and if you need anything tell me here ill help you
Hi
I just want to know if someone could help me..
I found a problem on my n900 at ''apt-get update'' it said 99%(working) but then it said fail after a while it said some packages would be ignored, or the old ones would be used instead
apt-get install nitdroid-installer
It then said nitdroid couldnt be found
If someone could help it would be great..tnx
I found the problem tnx but the airplane mode is always on..
Just a? . Would this work for any nokia. Um say e7? Irs the same nokianess?
Sent from my Defy. Using XDA App.
I can't install the updates....
I can't install the updates. I receive the message: "Can't open input file gingerbread_update1.tar.bz2: No such file or directory."
I tried several times and always the same error. I put the 2 files in the root as i did with the first 2 files.
Please help!!!!
deviljf it worked for you ? just fine? is there any kind of deley ? but in both ways its nice to have android on n900 the concept is awesome even with some minor bugs ,,thanks for trying it man
metal_n ...you must specify the directory and the path well other wise it wont work ....but now if you reboot your phone and open the keyboard and choose nitroid you can boot it ... if you face the same problem... tell me ill try to help you but its matter of pathing only man and thanks for trying it
gplock ... no it wont work mate... sorry cuz nokia e7 is based on Symbian^3
^ damn nokia. Fingers crossed they go android n not windows. Good job man thanks for sharing
Sent from my Defy. Using XDA App.
First of all thanks a lot for the easy steps you have provided,
On the other hand we have two issues:
1. This version as many as other versions does not support the Mic, or the cam plus other features on the droid system
2. For the users that are trying to follow the steps you will face one issue, make sure to add the following:
root
mount /home /and
cd /home/user/MyDocs
bzip2 -d gingerbread_update1.tar.bz2
----------------->bzip2 -d gingerbread_update2.tar.bz2
cd /and
tar xvf /home/user/MyDocs/gingerbread_update2.tar
Hope to hear from u when you get the full version
Regards,
Hey, jut installed it on my n900 and it's pretty good... A few things don't work right, but it's pretty impressive - I think it's faster than my old g1 already!
Points of interest:
Wifi seems to work but very slowly...
No 3G but I can't seem to add an APN in the network settings...
I made a call but I don't think the speaker was working...
Marketplace is acting weird but probably because of slow connection
Anyway it's awesome that it's working at all - great job mate!
Rick
Rick glad you like it thanks mate for trying it
silver386.....ill try my best thanks for replay
i cant install the nitdroid-installer
error
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package multiboot
Click to expand...
Click to collapse
also when i type apt-get update its says.
failed to fetch repisitory devil
failed to fetch moff mozilla
some index files failed to download.. they have been ignore or use the old ones used insteal
Click to expand...
Click to collapse
i solve the previous problem
now the last one when i install the nitdroid-kernel-2.6.28-06_final1_armel.deb
error
files list file for package 'com.ea.app.sim; contains empty filename
Click to expand...
Click to collapse
how to solve?
I managed to get an APN added - it was me being dense but no 3G. Been doing a bit of reading and it appears that the 3G radio is not fully working with android at the moment...
Do you think that is going to be possible to have android able to make calls properly or is this just going to be a fun hacking experiment.
Either way is fine - it's the journey I enjoy with these things not necessarily the destination...
Thanks again for your efforts
Rick
I have done search after search, and I have found nothing.
Here is the problem, I bought a MID 097Q1 tablet, that runs ICS, and now when I shut it down, and reboot, it will basically reset to factory settings on it's own.
Has anyone any idea or even seen such behavior before?
Thanks All.
Is it an A13 tablet?
wcypierre said:
Is it an A13 tablet?
Click to expand...
Click to collapse
I am unsure on how to check for that. Under the settings -> About Tablet it just shows: Model = 097q1
If there was a way I could just flash and reset the thing, that might be good. But I have tried the hold volume and reboot trick, and it did not flash the thing back to factory. Basically my stuff was still there.
I found one set of posts that suggest that the install of busybox may be the reason to blame.
Also, the CPU is listed as BOXCHIP A10 - 1.5ghz (cortex A8).
Here are the specs from the site I got it from:
Specifications:
CPU
BOXCHIP A10 1.0-1.5GHz(cortex A8), GPU:Mali-400
Operation System
Google Android 4.03
Memory
1GB DDR3
NAND Flash
16GB
Display Screen
Capacitive touching screen (IPS), 1024*768 pixel
Touch Operation
Full-size touch operation, sliding menus, icons and drag
Network
WiFi 802.11 B/G
Bluetooth Support
Sensor G-sersor 360 degrees
Audio
Supports stereo speaker unit, built-in microphone
External Storage
Support to the 32 GB TF card
I/O Ports
Micro USB2.0
HDMI output
TF card slot
3.5mm stereo headphone jack
DC-in jack
Adobe Flash Flash11
Audio Player
MP3, WMA, APE, FLAC, OGG, WAV Frequency response: 20Hz to 20000H
Video Player
AVI,MKV(XVID/px/H.264),MOV,TS,M2TS,RM/RMVB,FLV,3GP,MPEG,DAT,MP4(support to 2160P:3480x2160)
Application soft ware
Google Search / Browser /Camcorder/camera/Email/Gmail
Video Player/Audio Player/Alarm Clock /Apk /Calculator
Calendar/ES file Explorer /ES Task Manager/Global Time
Google Maps /Google Talk/iReader/Market/NC Manager
PDF Reader/Photo Browser/Weather Forecast/QQ
PC camera
0.3M FF Front/2.0M AF Back
Accessories
Adapter, user manual, USB cable, OTG cable
Battery
Lithium-ion 8000mAh
Color
Silver
Net Weight 0.6kg
Product Size 240*185*9.8mm
ericm76903 said:
I am unsure on how to check for that. Under the settings -> About Tablet it just shows: Model = 097q1
If there was a way I could just flash and reset the thing, that might be good. But I have tried the hold volume and reboot trick, and it did not flash the thing back to factory. Basically my stuff was still there.
I found one set of posts that suggest that the install of busybox may be the reason to blame.
Also, the CPU is listed as BOXCHIP A10 - 1.5ghz (cortex A8).
Here are the specs from the site I got it from:
Specifications:
CPU
BOXCHIP A10 1.0-1.5GHz(cortex A8), GPU:Mali-400
Operation System
Google Android 4.03
Memory
1GB DDR3
NAND Flash
16GB
Display Screen
Capacitive touching screen (IPS), 1024*768 pixel
Touch Operation
Full-size touch operation, sliding menus, icons and drag
Network
WiFi 802.11 B/G
Bluetooth Support
Sensor G-sersor 360 degrees
Audio
Supports stereo speaker unit, built-in microphone
External Storage
Support to the 32 GB TF card
I/O Ports
Micro USB2.0
HDMI output
TF card slot
3.5mm stereo headphone jack
DC-in jack
Adobe Flash Flash11
Audio Player
MP3, WMA, APE, FLAC, OGG, WAV Frequency response: 20Hz to 20000H
Video Player
AVI,MKV(XVID/px/H.264),MOV,TS,M2TS,RM/RMVB,FLV,3GP,MPEG,DAT,MP4(support to 2160P:3480x2160)
Application soft ware
Google Search / Browser /Camcorder/camera/Email/Gmail
Video Player/Audio Player/Alarm Clock /Apk /Calculator
Calendar/ES file Explorer /ES Task Manager/Global Time
Google Maps /Google Talk/iReader/Market/NC Manager
PDF Reader/Photo Browser/Weather Forecast/QQ
PC camera
0.3M FF Front/2.0M AF Back
Accessories
Adapter, user manual, USB cable, OTG cable
Battery
Lithium-ion 8000mAh
Color
Silver
Net Weight 0.6kg
Product Size 240*185*9.8mm
Click to expand...
Click to collapse
Have you installed busybox before? If yes then you can follow the following steps:
Windows Only:
1. USB Driver: http://www.mediafire...q1oamnccjk82aq8 (Extracted from http://ployermomo9.w...cream-sandwich/)
2. Get yourself the fastboot files: http://wikisend.com/...id_fastboot.zip
3. Create a folder called fastboot at your root folder(C:/, D:/)
4. Open cmd(or also called command prompt)
4. Type "cd \fastboot" (without the quotes)
5. Type "adb shell" (without the quotes)
6. Type "su" (without the quotes)
7. Type "mount -o rw,remount /dev/block/mmcblk0p1 /system" (without the quotes)
8. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
9. If there is an error(sh cp: not found), follow step 10. If there is no error, then skip step 10
10. Type "ln -s /system/xbin/busybox /system/xbin/cp" (without the quotes)
11. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
12. Type "reboot" (without the quotes)
wcypierre said:
Have you installed busybox before? If yes then you can follow the following steps:
Windows Only:
5. Type "adb shell" (without the quotes)
6. Type "su" (without the quotes)
7. Type "mount -o rw,remount /dev/block/mmcblk0p1 /system" (without the quotes)
8. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
9. If there is an error(sh cp: not found), follow step 10. If there is no error, then skip step 10
10. Type "ln -s /system/xbin/busybox /system/xbin/cp" (without the quotes)
11. Type "cp /system/xbin/busybox /system/bin/busybox" (without the quotes)
12. Type "reboot" (without the quotes)
Click to expand...
Click to collapse
You are the Man!!
Since I use a MAC, I had to load adb there. But once that was done, I was able to do steps 7 and 8 with out error, and it now works. Thanks for the information on that.
Here is the info for MAC and adb install:
1. Download the latest Android SDK from Google: Android SDK
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and proceed with the tutorial: ADB
4.Create an environment variable (Optional)
5.Open Terminal
6.Type cd ~ this will take you to your home directory
7.Type touch .profile this will create a hidden file named profile
8.Type open -e .profile this will open the file you just created in TextEdit
9.In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
10.Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
NOTE: make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
source: Just google: how-to-set-up-adb-android-debug-bridge-in-mac-osx
ericm76903 said:
You are the Man!!
Since I use a MAC, I had to load adb there. But once that was done, I was able to do steps 7 and 8 with out error, and it now works. Thanks for the information on that.
Here is the info for MAC and adb install:
1. Download the latest Android SDK from Google: Android SDK
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and proceed with the tutorial: ADB
4.Create an environment variable (Optional)
5.Open Terminal
6.Type cd ~ this will take you to your home directory
7.Type touch .profile this will create a hidden file named profile
8.Type open -e .profile this will open the file you just created in TextEdit
9.In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
10.Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
NOTE: make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
source: Just google: how-to-set-up-adb-android-debug-bridge-in-mac-osx
Click to expand...
Click to collapse
good to know that it works :good: The adb config depends on your OS and you'll usually have it set anyway btw, does the battery at your rom has the graph indicated(the percentage of battery used for each apps, ex. screen - 60%, whatsapp - 4% and so forth)?
wcypierre said:
good to know that it works :good: The adb config depends on your OS and you'll usually have it set anyway btw, does the battery at your rom has the graph indicated(the percentage of battery used for each apps, ex. screen - 60%, whatsapp - 4% and so forth)?
Click to expand...
Click to collapse
Nope. It is showing "no data available"
ericm76903 said:
Nope. It is showing "no data available"
Click to expand...
Click to collapse
I had the same problem as well......... I wonder how can we solve this problem
original firmware
hello, can somebody provide link for original firmware of this MID 097Q1 or costum rom that really works? Mine get bricked and i flash rom from some other similiar tablet from china (M907), everything works except the touchscreen (it use LG IPS screen). Thanks in advance.
Hello all, im working on a app to transfer pictures from a camera to the phone and i would like some assistance. i got the camera connected after putting together some code reading around about it. but i can't or don't know how to transfer the files over. any assistance would be great. thanks!
inspector94 said:
Hello all, im working on a app to transfer pictures from a camera to the phone and i would like some assistance. i got the camera connected after putting together some code reading around about it. but i can't or don't know how to transfer the files over. any assistance would be great. thanks!
Click to expand...
Click to collapse
Use adb.exe
1) Set ADB to &PATH
2) Make a loop running "adb devices"
3) Parse out the devices when one is detected
4) Run adb -s "DEVICE-SERIAL" push /sdcard/ or pull /sdcard/ to send files across
Here is some Regex for java for parsing out adb devices if you have more than one device connected and want to add concurrency -
Code:
private static final String mRegex = "^([a-zA-Z0-9\\-]+)(\\s+)(device)";
Hope this helps,
Ryan
P.S - Some devices like the Kindles have non-standard file systems, you may want to make some logic around this if you plan to make it large scale; for example user input to the destination path using tree/ls mappings.
SkysRad said:
Use adb.exe
1) Set ADB to &PATH
2) Make a loop running "adb devices"
3) Parse out the devices when one is detected
4) Run adb -s "DEVICE-SERIAL" push /sdcard/ or pull /sdcard/ to send files across
Here is some Regex for java for parsing out adb devices if you have more than one device connected and want to add concurrency -
Code:
private static final String mRegex = "^([a-zA-Z0-9\\-]+)(\\s+)(device)";
Hope this helps,
Ryan
P.S - Some devices like the Kindles have non-standard file systems, you may want to make some logic around this if you plan to make it large scale; for example user input to the destination path using tree/ls mappings.
Click to expand...
Click to collapse
Thanks for the reply, i'll see if i can give this a try. Is there a way to do it with the mtp API? similar to how the android camera gallery works. cause else i have to redo the code. Thanks
Hello XDA Dev Community!! I`m with You since 2011 ! but never wrote.. So HELLO!
EDIT
I`m not sure why my Q was took out of the topic:
https://forum.xda-developers.com/t/...-a-decryptable-twrp-no-root-required.4086625/ - I won`t argue anyway my question is related to the guide - link above.
EDIT ENT
Just to check with community if all is ok
My phone is Pixel 2, stock Android 11, bootloader unlocked, rooted (Magisk).
Connected phone via usb, entered in CMD:
Code:
adb shell
su
dd if=/dev/block/sdf2 of=/storage/emulated/0/Download/modemst1.bin bs=2048
As I understand I changed location of the output file - if wrong - pls correct me.
In Solid Explorer those 2 files have like HH:MM in name in front of sdf2 and sdf3 and both weigh 0 B.
Output files landed in Download folder like this:
modemst1.bin 256.00 kB
modemst2.bin 1.50MB
Is that right?
Is there any way to open those bin files and check if they are correct?
adb shell info after dd comand looked ok for me:
Code:
128+0 records in
128+0 records out
Ok. iso asking I could check with internet.. so bin is like iso but older..
If I mount it or convert to iso and mount - is there a way to check if it`s backed up correctly? I know that 100% sure I will be after formatting EFS and trying to recover from created files BUT... maybe there is sth I can check before?