Imaging an Android Device

Forum rules
Discussion on the R-Drive Image software

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Imaging an Android Device

Re: Imaging an Android Device

by Alt » Sat Jul 12, 2014 8:41 am

Well, an Android device should be at least rooted. This is against the end-user license for most devices. I don't think we should encourage doing this.

Re: Imaging an Android Device

by iTee » Fri Jul 11, 2014 11:33 am

Hello,

This is an interesting topic.

Is there a progress update on this?

Re: Imaging an Android Device

by Alt » Sun Sep 01, 2013 4:59 am

An interesting experiment. I'll see how it works.
You see, Google does (and other mobile OS vendors do) everything possible to not let the user to touch the system.

Imaging an Android Device

by Randall H » Fri Aug 30, 2013 2:16 pm

Greetings..
Was wondering about the ability of R-Drive to image an Android Device? I have a Samsung Galaxy Media Player 5. It is rooted. Just to test, I went ahead and imaged the Internal Drive as well as the external SD card. It appears that the image process worked. As the disks are FAT 32, I would assume this is OK? I am not an Android system expert, but I believe that the system resides elsewhere on internal memory? Was wondering about whether in the future, R-Drive might be able to handle this as well? I am sure you can see how important a feature this could be?
Any thoughts?
Thanks
Randall

Top