> > > > > > > i like the idea of information being available if phone imaged > > > > > > > > > > > > > > maybe that's a separate concern from being able to reflash the > > > > > > > image > > > > > > > onto another phone for now :s > > > > > > > > > > > > obviously part of that is just disabling any normal basic encryption > > > > > > the phone has > > > > > > > > > > > > maybe then an image could be taken, and one could just look at the > > > > > > image to see if user files are plaintext! > > > > > > > > > > > > it's a little confusing cause android can have a custom logical > > > > > > partition format, maybe that could be added to a tool somewhere > > > > > > > > > > there maybe is a mainstream android mod called "disable force > > > > > encryption" that disables a normal android encryption of /data > > > > > so i could in theory possibly, tar a running /data, disable encrypted > > > > > /data, and untar my backup .... ? > > > > > > > > i'd likely need root > > > > > > this phone is mediatek :s > > > > > > maybe stepping back from project. happy i added links. > > > > > > i might try to make small steps on an appish thing to identify if > > > another phone is mediatek, from a given phone. some kind of standalone > > > script. > > > > i think mediatek phones can be identified by the serial device they > > expose briefly on boot .. i think there were two of them, one when it > > is using the ROM bootloader, and a different one when it is using a > > firmware bootloader > > or more robustly it can be communicated with. > > but i think there is a general way to identify these serial devices > because i think there is device code in the linux kernel that used to > be patched in order to engage them
might not be happening have a fruit
