Develop Bugs

[Q] user interface? File management wp7?

I am at a complete loss here. Just succesfully installed WP7 om my HTC HD2 now trying to set up the android dual boot. Necessary files are copied to the proper partition on teh SD card.....but NOW HOW TO GET TO THEM?????
Can't even run the exe files no explorer, no config, Am I dealing with a different Microsoft company? Filesync with PC...?
All very basic, but i can't even find a manual of some kind.
Help would color my weekend!

[Q] Dump Memory from Mango Phone / Extract Data From Backup?

I haven't found anything on the forums about this (I have searched) so forgive me if it's a basic question. Is it possible to either:
1) Dump all data on a mango phone (in my case, a Samsung Focus, no interop-unlock) to a file on my computer, or alternatively
2) Access the data stored in the umpteen files created during a WP7 backup.
If anyone knows how to do either of these things (without interop unlocking -- I have data I need to pull off, but my firmware is too old to get interop unlocked, and I get error messages when I try to manually update the firmware), it would be greatly appreciated.
Thanks,
Beakin
Note: edited to clarify

I doubt it's even possible *with* interop-unlock.
1) A native app could map a large region of memory, but the WinCE kernel uses process isolation (same as every other modern OS) so there's no way for one app to access the full physical memory.
2) They're encrypted with a key that appears to be stored in the device itself. Nobody has yet figured out how to reverse this encryption.

GoodDayToDie said:
I doubt it's even possible *with* interop-unlock.
1) A native app could map a large region of memory, but the WinCE kernel uses process isolation (same as every other modern OS) so there's no way for one app to access the full physical memory.
2) They're encrypted with a key that appears to be stored in the device itself. Nobody has yet figured out how to reverse this encryption.
Click to expand...
Click to collapse
On #1, I should have been more specific -- I meant dump the phone's storage; what's in non-volatile memory, not RAM.

Still no without interop-unlock, then - standard apps don't have the privileges to access the filesystem (aside from a few very specific locations, like their isolated storage folder). That probalby means no access to the storage device itself either, although I admit to not knowing how that works on CE (NT or Linux, but that's it). If the app was initially sideloaded you can use the Isolated Storage Explorer to pull files from that app specifically, but if it's a marketplace app or something built-in like the SMS store, no such luck.
Of course, you can get more permissions if you can call into a driver - which is what ID_CAP_INTEROPSERVICES allows you to do, and ID_CAP_INTEROPSERVICES is why you need interop-unlock. I'd suggest you focus on figuring out why you can't interop-unlock and fixing that. Unfortunately I can't really help you there; I don't have a Samsung phone and the steps to IU an HTC phone are very different.

GoodDayToDie said:
Still no without interop-unlock, then - standard apps don't have the privileges to access the filesystem (aside from a few very specific locations, like their isolated storage folder). That probalby means no access to the storage device itself either, although I admit to not knowing how that works on CE (NT or Linux, but that's it). If the app was initially sideloaded you can use the Isolated Storage Explorer to pull files from that app specifically, but if it's a marketplace app or something built-in like the SMS store, no such luck.
Of course, you can get more permissions if you can call into a driver - which is what ID_CAP_INTEROPSERVICES allows you to do, and ID_CAP_INTEROPSERVICES is why you need interop-unlock. I'd suggest you focus on figuring out why you can't interop-unlock and fixing that. Unfortunately I can't really help you there; I don't have a Samsung phone and the steps to IU an HTC phone are very different.
Click to expand...
Click to collapse
Thanks for the clarification. I've spent the last month trying to figure out how to get the interop unlock working on my phone to no avail, which is why I was changing tact by asking this. Oh well, back to the old drawing board.
BTW if you or anyone know how to take a windows phone firmware CAB file and alter it (removing items) I'd appreciate it. My problem with updating the firmware is that I get a "file name conflict" error pointing to specific items in the CAB. At the risk of bricking my phone, at this point I'd try removing those items and installing it anyway.

Editing a CAB is easy; Win7 Explorer can open them natively and many third-party tools also exist. Editing a CAB so that it can still be isntalled may take a little bit more effort, but the important point is that as soon as you edit it, you'll invalidate the signature on the CAB. That means it will no longer install through the default update-OS at all. On HTC phones, you can use RSPL (or HSPL) to install custom updates, but on a phone with a retail bootloader (such as a Samsung), you can only install official updates.

[Q] Understanding System Structure, SGH-I257M

I am wanting to get a clear understanding of the structure of the Android phone - hardware, firmware and software - in particular, relating to the Samsung Galaxy S4 mini, Canadian edition SGH-I257M.
I have been a computer bum since the mid-60s. I have extensive experience with machine and assembly languages, microcomputers and microcontrollers, programming "to the metal" [as we used to say], as well as C and high level languages, and a little UNIX knowledge via QNX from the century gone by. But i have been retired from all that for 15+ years and am entirely new to smartphones and Android.
So i have some questions.
But first, i have read and read and read. Too much hi-tech info the "get it" all at once. In particular i have found these threads specific to the SGH-I257M ...
Galaxy S4 Mini Archive
http://www.s4miniarchive.com/2013/12/How-to-unroot-and-unbrick-Samsung-Galaxy-S4-Mini-SGH-I257M.html
Root new S4 mini model SGH-I257M
http://forum.xda-developers.com/showthread.php?t=2470173
STOCK and ROOTED SGH-I257M
http://forum.xda-developers.com/showthread.php?t=2520299
and several others on rooting various specific-only versions of the S4 mini, CyanogenMod, flashing firmwares, etc. But no complete, tested process for rooting this specific model, or for installing CyanogenMod on it, etc.
And a little history ...
Back in the mid 60s a visiting professor at the University gave a talk entitled "Hardware, Software and Underwear". The title was of course, intentionally provocative. It was a bit mysterious to us at the time, but the idea was to encode low level software in hardware to make it run faster, among other reasons. The term underwear did not stick. Instead we have firmware, and in particular on microcomputers, the BIOS - Basic Input Output System.
Question #1: with regard to Android, my guess is the the BIOS is the interface between the physical hardware and the Linux Kernel. Is this concept of the system structure correct? ...
hardware <-> BIOS <-> Linux Kernel <-> Android System
Question #2: I am not clear on the various categories of memory. The S4 mini has a SIM card, either 8 or 16 gb memory [mine has 16], and may optionally have up to an additional 64 gb memory via a microSD card installed by the owner. Is the BIOS on a separate chip like in microcomputers? Any other memory types? [I have a feeling that i am missing something].
Question #3: Which physical memory contains each of the BIOS, the Linux Kernel and the Android system?
Question #4: I am thinking that CyanogenMod is a replacement for what i have labelled Android System in my simple structure diagram in question #1 above. Is this correct?
Question #5: The idea of rooting the phone is clear to me. I know what is the root directory on a computer hard drive and that the rooting process gives the user access to both that directory and permissions to do anything [delete, rename, replace, install, uninstall, whatever]. And that doing this voids the warranty.
When spring/summer comes along [and they will, even in this cold and frozen Canada!] i expect to be off on my motorcycle [vintage IronHead] for extended periods. I will want to do whatever to extend the battery life of my phone. So i am anticipating rooting the phone by then and perhaps installing CyanogenMod. I have not yet seen a clear process for rooting for the Canadian S4 mini SGH-I257M including making appropriate backups of the system software, or for installing CyanogenMod, but i am looking. Any pointers to this i would appreciate.
Question #5: Any books on this topic of Android system structure, especially wrt Samsung smart phones? I know, books are so last century; so maybe a website, forum thread, or whatever.
TIA! More ?s later.
Mick

OK, i got some answers on another forum, and these answers have been very helpful. So as i understand things now, ...
The BootLoader is in a rewriteable ROM, an actual physical chip
The 1.5 gb RAM is what i have been missing. This is where currently running programs are stored, temporarily, until both they are no longer running and the system needs the RAM to run another process
The 16 gb storage is equivalent to the hard drive on a PC. All software - Android system and apps - are stored here, and are loaded into the RAM when they need to run. The storage is divided into partitions.
I can see what programs are currently in RAM by Settings | more | app manager | running
I can see what programs are in storage by Settings | more | storage
As mentioned, the common use of the word ROM does not refer to an actual physical ROM chip or to software that might be loaded into one. Rather is is a generally accepted but misused term for replacing the whole [or perhaps part of the] operating system.
So now i have two more questions/thoughts ...
What about these partitions? Are these really partitions like on a PC hard drive? or are these really sub-directories of the root? There would be certain partitions, standard with the Android setup, each with a specific purpose. It would be helpful to know at least a few of these.
In my running apps list i see S Voice. Hhmmmm, i thought i deleted this app. I know i did. I do not need it to be in there, taking up space and CPU cycles. I expect that it is OK to Stop it, and that it will re-start itself next time i power off/up. I'll have to go down that list and see what else i can "put a stop to".
TIA. More ?s later.
Mick

Got some more info from the other forum, including this excellent link to an explanation of the partitions, so things are moving along ....
http://www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc/
Looks like the "partitions" are "directories", using the old MS-DOS and UNIX terminology. So once rooted, ...
cd / goes the the root directory, or
cd /recovery goes to the recovery directory
and ...
ls
would list the contents of whatever is the current directory.
Mick

To Root or Not to Root?

My current Nexus 10 is on it last legs and I decided to pick up a Galaxy Tab T800 10.5 inch wifi only in good/Used condition on ebay and should receive it next week.
While I await it, I'm starting to look at its rooting process and if I should root it not. I assume it is coming unrooted, but won't know for sure till I get it and what version of Android it currently has. I'm not completely new to rooting as I have done it before on my Nexus 10 and Note 2 phone (yeah, time to upgrade). Its just been a while since I need to root something.
But do you think rooting it and going with a custom Rom is that much better than the Stock Rom?
Also, I did only buy a 16GB version, as the majority of all of my video's are on a home server and I use either XBMC/Kodi and BSPlayer to connect and watch things. But I remember with my Nexus 10 it was also possible to Map a Folder to a local server. Does anyone know if that is possible with Galaxy Tab? The ability to map a folder/drive is great to navigate and view pdf's, pictures etc.
Thanks
PT

ptmuldoon said:
My current Nexus 10 is on it last legs and I decided to pick up a Galaxy Tab T800 10.5 inch wifi only in good/Used condition on ebay and should receive it next week.
While I await it, I'm starting to look at its rooting process and if I should root it not. I assume it is coming unrooted, but won't know for sure till I get it and what version of Android it currently has. I'm not completely new to rooting as I have done it before on my Nexus 10 and Note 2 phone (yeah, time to upgrade). Its just been a while since I need to root something.
But do you think rooting it and going with a custom Rom is that much better than the Stock Rom?
Also, I did only buy a 16GB version, as the majority of all of my video's are on a home server and I use either XBMC/Kodi and BSPlayer to connect and watch things. But I remember with my Nexus 10 it was also possible to Map a Folder to a local server. Does anyone know if that is possible with Galaxy Tab? The ability to map a folder/drive is great to navigate and view pdf's, pictures etc.
Thanks
PT
Click to expand...
Click to collapse
Previous to my S1 10.5" I had a rooted Nexus 10. I rooted without tripping Knox to retain my warranty. Although I had my S1 for several months without rooting (5.0.2) there will a few things I missed:
- Viper4Android (superior audio replacement)
- GMD Gesture Control (including immersion mode)
- Enhanced Power menu
- Titanium backups
- Full RW access to the internal microSD card
- The ability to theme the TouchWiz UI
There are more reasons to root but those are the first few that I desperately missed from the N10.
The free ES File Explorer can map CIFS/SAMBA network drives and with root can access the entire internal storage with RW permissions. I use Plex/MXPlayer to access my NAS video collection without transcoding but the setup you mentioned would also work well even if you didn't root.
I found that after having full RW access to my MicroSD card (64GB) that you could do what ever you wanted as far as mapping is concerned. I get Titanium Backup to write straight to the mSD card and have never seen my 16GB device as too small, it just does not happen. With that said I am not a gamer so take the comment with a grain of salt. My mSD card is mainly filled with backups and music files.
As you are likely to no longer be under warranty I would advise rooting using the CF method which includes TWRP then you can try which ever custom ROM catches your fancy and switch safely as long as to take nandroid backups with the enhanced recovery.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
Previous to my S1 10.5" I had a rooted Nexus 10. I rooted without tripping Knox to retain my warranty. Although I had my S1 for several months without rooting (5.0.2) there will a few things I missed:
- Viper4Android (superior audio replacement)
- GMD Gesture Control (including immersion mode)
- Enhanced Power menu
- Titanium backups
- Full RW access to the internal microSD card
- The ability to theme the TouchWiz UI
There are more reasons to root but those are the first few that I desperately missed from the N10.
The free ES File Explorer can map CIFS/SAMBA network drives and with root can access the entire internal storage with RW permissions. I use Plex/MXPlayer to access my NAS video collection without transcoding but the setup you mentioned would also work well even if you didn't root.
I found that after having full RW access to my MicroSD card (64GB) that you could do what ever you wanted as far as mapping is concerned. I get Titanium Backup to write straight to the mSD card and have never seen my 16GB device as too small, it just does not happen. With that said I am not a gamer so take the comment with a grain of salt. My mSD card is mainly filled with backups and music files.
As you are likely to no longer be under warranty I would advise rooting using the CF method which includes TWRP then you can try which ever custom ROM catches your fancy and switch safely as long as to take nandroid backups with the enhanced recovery.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
Thank's for the great info and feedback. I'll plan to root it when it arrives (hopefully this weekend). But have 2 more general questions as you seem pretty familiar wit the tablet.
I know its personal preference. But have you found a preferred custom Rom you like? And are you sure you ESFile Explorer can actually Map a network CIFS/Samba share location? I can use ESFileExplorer to access my server and navigate the network shares. But I have not figured out how to actually map the shares to a local folder on the tablets. I'll have to revisit that ability separately though as its not big deal as XBMC/Kodi and others can still access the shares.
But when the shares are actually mapped to local folder, you can navigate them from pretty much any native app.

ptmuldoon said:
... But have you found a preferred custom Rom you like? And are you sure you ESFile Explorer can actually Map a network CIFS/Samba share location? I can use ESFileExplorer to access my server and navigate the network shares. But I have not figured out how to actually map the shares to a local folder on the tablets. I'll have to revisit that ability separately though as its not big deal as XBMC/Kodi and others can still access the shares.
But when the shares are actually mapped to local folder, you can navigate them from pretty much any native app.
Click to expand...
Click to collapse
As I rooted but preserved my warranty by not tripping the Knox counter (I can return to pure uprooted stock), I must keep the Samsung locked bootloader. The means I have limited choices in custom ROMs and no choice in custom kernels. The only ROM I could flash is Ironman. With all that said I decided to stay with stock 5.0.2 and just augment it with root apps that I listed in my previous post. That gave me all the custom ROM features I regularly use.
I think now I understand better what you wanted from mapping. So ES File Manager would not give you what you wanted as its cifs/samba maps are usable by other apps only when you use the ES file manager UI. For example click on a CIFS mapped video file in the ES file Manager UI and an associated video player plays the video. In the past I used XBMC on Android and that version included CIFS/Samba drivers that allowed me to access my network attached video collection. I suspect that feature still exists.
Now if you had video files on either the internal storage or external microSD card and wanted those directories available to XBMC the internal storage would be no issue but I think you need to use an app like Stick mount for the microSD. Stick mount creates a symbolic link on the internal storage (\sdcard) to directories on the microSD card allowing any app to access those files as if they were located on internal storage. That may accomplish what you want.
I still maybe misinterpreting what your trying to accomplish with mapping but I'm fairly sure one way or another you can get what your looking for especially as you'll be rooted.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
I think now I understand better what you wanted from mapping. So ES File Manager would not give you what you wanted as its cifs/samba maps are usable by other apps only when you use the ES file manager UI. For example click on a CIFS mapped video file in the ES file Manager UI and an associated video player plays the video. In the past I used XBMC on Android and that version included CIFS/Samba drivers that allowed me to access my network attached video collection. I suspect that feature still exists.
I still maybe misinterpreting what your trying to accomplish with mapping but I'm fairly sure one way or another you can get what your looking for especially as you'll be rooted.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah. It was tricky on the Nexus 10 to mount a CIFS/Samba share and needed specific cifs.ko and other modules. It was sorta of hit and miss and I remember most said it worked best when you mounted them to the /mnt/obb system file folder location. If you google it, you'll find bunch of topics leading back to posts on xda about it.
Its the same concept of mapping a share with a PC, etc. Once done, any program/app should see that information as a local system folder. So you could launch any app and if needed, navigate to your network share files to open a document., text file, pdf viewer, and so depending on what the app was looking for. Even ESFile Explorer would then see your network shares as a local system directory. And you could actually save your titanium backups directly to your NAS or network server, if you wanted to.

What's with the file system support on Android

Hi guys,
I bought an USB-C flash drive recently which I wanted to use with my phone. I wanted to store big movies on it so I did a quick Google search about exFAT support. According to what I found Android supports it since KitKat. Nontheless, it doesn't work on my Nexus 5X.
I did some more digging and I found out that OEMs can simply decide not to enable this feature (possibly because it costs a license fee). Is it possible that Google wanted to save a few bucks and simply removed the support from this device?
I tried to use ext3/4 as my file system but that did fail too. I find it painfully ridiculous, that Android, which builds on Linux doesn't let me use filesystems that are supposed to be supported natively by the kernel. It's like they are trying to make things difficult on purpose.
What can I do to use my flash drive with a file system that works with my phone and doesn't have the 4GB file limit? Is there any other FS that may work without serious tinkering? Currently I'm not rooted and I intend to keep it that way because my banking app wouldn't work otherwise. I know about apps that adds support to specific filesystems but aren't they more limited than the native support?
I don't remember if I tested file system support with Android 7 or 8. Is it possible that things changed since the new Android version?

manfreed said:
Hi guys,
I bought an USB-C flash drive recently which I wanted to use with my phone. I wanted to store big movies on it so I did a quick Google search about exFAT support. According to what I found Android supports it since KitKat. Nontheless, it doesn't work on my Nexus 5X.
I did some more digging and I found out that OEMs can simply decide not to enable this feature (possibly because it costs a license fee). Is it possible that Google wanted to save a few bucks and simply removed the support from this device?
I tried to use ext3/4 as my file system but that did fail too. I find it painfully ridiculous, that Android, which builds on Linux doesn't let me use filesystems that are supposed to be supported natively by the kernel. It's like they are trying to make things difficult on purpose.
What can I do to use my flash drive with a file system that works with my phone and doesn't have the 4GB file limit? Is there any other FS that may work without serious tinkering? Currently I'm not rooted and I intend to keep it that way because my banking app wouldn't work otherwise. I know about apps that adds support to specific filesystems but aren't they more limited than the native support?
I don't remember if I tested file system support with Android 7 or 8. Is it possible that things changed since the new Android version?
Click to expand...
Click to collapse
It's not about what file systems are supported by the kernel and tools, of course ext2/3/4 is supported (the internal storage is ext4). It's about what OTG supports and that would be FAT32 and *probably* NTFS.
The tools included on the phone do not support NTFS so you cannot format it to NTFS using your phone but you can do that with the computer and then use it on the phone, if it does indeed support NTFS.