Booting ROM from SD-Card (No flash/internal memory) - Android Builders Collective

Hi All,
As the title states, I'm looking for someone who can help advise around the feasibility on the following.
The goal is :
1. Remove Android internal storage/disconnect flash memory chip (No data can be written)
2. Create bootable SD-card with custom applications for chatting.
3. If our users are in danger, they can simply turn off the phones OR remove the SD card, and no data can be written to disk for later retrieval (I'm fully aware of memory aquisition but I'm talking about post power-down in terms of minutes to hours when the memory has dispersed).
I've read a number of posts talking about live booting off an SD-Card similarly to how you would do it with x86 devices and live-boot USB's.
Can anyone help out?

Related

Application for bridging SDHC as device memory

Guys,
Is there somewhere else who create an application that can make SDHC card as device memory?
Thanx.
irmanpribadi said:
Guys,
Is there somewhere else who create an application that can make SDHC card as device memory?
Thanx.
Click to expand...
Click to collapse
The storage card can only be used as a storage card, not for device memory. nice idea though, it would be nice to have 16gb of ram
Regards
Jay
maybe this is not about ram but about having the sd card as primary partition, which might be possible although it has never been done before. in wm2003 the ramdrive was the primary partition and the "storage" was listed as a storage card. these days the storage is the first (and on most devices and roms only) partition. but when a ramdisk is added, it is listed as a storage card. that means the order of the drives is variable and a storage card could also be the first partition.
but what would you want with a theretical answer like that? an expert rom chef, who started with cooking wm2003 might know the answer or could do that for you.
but for all realistic means, you should simply try and save all documents, pictures, videos and music, install bigger programs, derive the cache for your browser, store email attachments all on the sd card. the only problems with completely leaving out on the internal storage, especially for program installation, is that it is slow.
It should be possible but you will probably need to cook a new ROM to get it working. It's mostly just a matter of telling CE which mounted volume you want to mount as root for the emulated objectstore.
This document on MSDN should give you an idea of what to do:
http://msdn.microsoft.com/en-us/library/ms885839.aspx
The MPx200's WM5/WM6 ROMs do this already. If you do this, keep in mind you likely won't ever be able to eject the card while the device is booted as the registry will be stored there. Now, maybe you could write some sort of app that would dismount/remount and reinitialize the registry at the press of a button but that doesn't seem too practical unless you have no choice as on the MPx200. Another workaround might be to store the registry hives on an internal flash partition and store the rest of the system folders on the SD card.
As for implementing the RAM/ROM based filesystem like in WM2003, I'm not sure. The Windows CE 5.x kernel used for Windows Mobile 5/6/6.1/6.5 certainly won't prevent you from doing it but I'm unsure the Universal's hardware can persist the ram contents between "soft" resets. If it can, then I imagine it's only a matter of using an NK.exe that doesn't force a clean reboot and using a different filesys.exe than the included ROM only/hive registry configuration it ships with. Heh, if you ever looked at the MS news groups you will see a whole bunch of posts by OEMS getting yelled at for using the ram based configuration in their beta WM5 roms. "Not supported" doesn't mean it can't be done and work, it just means MS doesnt' want you to do it for either marketing or other reasons.
Chef_Tony said:
maybe this is not about ram but about having the sd card as primary partition, which might be possible although it has never been done before. in wm2003 the ramdrive was the primary partition and the "storage" was listed as a storage card. these days the storage is the first (and on most devices and roms only) partition. but when a ramdisk is added, it is listed as a storage card. that means the order of the drives is variable and a storage card could also be the first partition.
but what would you want with a theretical answer like that? an expert rom chef, who started with cooking wm2003 might know the answer or could do that for you.
...
Click to expand...
Click to collapse
The ramdisk you are talking about is very different from the Windows CE object store used in WM2003 and many current non-PPC WinCE devices.
They don't even use the same filesystem! The ramdisk driver commonly circulated on these forums basically just formats/mounts a chunk of RAM as a FAT partition. It can't be resized and appears to the OS as any other flash card. You can even format it with StorageTools or whatever. The dynamic ramdisk or objectstore is built into the WinCE OS. It uses a proprietary filesystem optimized for RAM usage that is closely integrated into the kernel. As I understand it, It's more like a database than a filesystem like FAT. The registry, files and DBs are all stored in the same internal format and then abstracted by the OS and it's APIs. It couldn't even be disabled until more recent WinCE versions. More info: http://msdn.microsoft.com/en-us/library/aa910544.aspx

Which memory is best Internal or External?

I had a quick search through the posts and found some folk with questions about their SD card and extra space, however...
The question I have is, what is the best practice for installing applications on Winmo devices?
I understand that some applications that boot at start-up need to be on the device because the SD card may be started late on in the boot up process.
In general though, is it better to install applications to the device and fill the device memory with applications while keeping files on the SD card, or am I just as well installing them on the SD card?
I ask only because today I have been made aware of a potential issue with my Blackstone / SD card and recent updates from HTC.
Thanks for any comments, if there is a better place for my question please let me know what to do to move / remove my thread.
internal is faster
internal is lost at hardresets and of cause flashing
external is disabled when the device is suspented so
today screen running programs are best left in the internal

[Q] Why does no Mod Rom or Custom ROM allow official ext4 external?

Dear All,
I have a simple question to open a discussion here. We all know that modern android phones are having the ability to understand ext4 (and if my research is right - the internal storage in most Android 4.x phones is formatted in ext4). Why is dev or mod build like Cyanogenmod or even a OEM like Xiaomi which develops MIUI not removing emulated sdcard functionality (optionally) and instead allow users choose to reformat their actual sd to ext4 when inserted (and mark that as internal SD - to allow standard App2sd)? Thereby enabling secure app + media storage a reality? And in the same way as Internal Storage, I think we can use MTP to read the external storage (ext4) when connected to PCs.
Furthermore, we can have a setting to warn the users about this compatibility change (that once they take up/choose this method)- they will not be able to read cards in normal way when connected directly via card reader to Windows PCs because of no direct ext4 support in Windows.
Additionally, can't we at least have this as an advanced or developer only setting, if we want novice users to not mess with the functionality?
Do you all agree? Or am I having a over-simplified understanding of making such a change?
Lastly, given an option, I would definitely choose such a change at the cost of compatibility rather than paying tons of extra money for higher internal flash storage
Nobody wants to answer this? We have so many experts here - I am really surprised to see no replies

[Completed] [Mod] Maximizing relocating internal data to external SD, LG Optimus Fuel L34C KitKat

Can you please help a noob figure out where this post belongs?
I make no pretense to being a developer, and I was very hesitant to join XDA, but these are questions concerning modding which I have not found answers to, despite posting to a number of other Android forums, so I was forced to "raise my sights."
I have an LG Optimus Fuel L34C (KitKat). I am an Android noob but I have a history with Linux, so I know just enough about what goes on behind the KitKat curtain to make me dangerous. So yes, I also care about the journey. And I'm already heavily invested in this quest, so despite my lack of expertise, I'm willing to do the leg work to make it happen.
My one saving grace is I have a backup fetish. And I want to continue to make Nandroid backups even when the L34C's puny internal storage (1790 MB usable) is maxed out (or nearly so). But I don't want to resort to backups to the cloud because 1) it offends my inner geek that I have to rely on someone else for backup support, and 2) as a delusional paranoid, the concept of "the cloud" gives me the willies.
I'm using TWRP Manager (Root) for Nandroid backups now, but TWRP only can write to the internal SD. Which means that once internal storage is about half full, there's no longer enough space remaining for any more Nandroids. And a bare bones installation with just enough additional apps installed to perform the Nandroid already takes up about 700 MB. So there's no chance of any further Nandroid backups after downloading or installing just two or three hundred more MB.
So my primary goal is to be able to write Nandroid backups to the external SD card (or, pipe dream, to write them to USB). If this also allows me to install apps or store other (internal) data on the external card, so much the better.
I just bought a second L34C because the WiFi on the original L34C pooped the bed. So now I have a new and unmodded L34C to experiment on. I had (towel) rooted the old phone, write-enabled the external SD card and installed the TeamWin open recovery image v2.8. And I replaced the OE 4GB external SD card with a 16GB class 4 card, partitioned half in Fat32 and half in Ext3.
The primary obstacle was that I could never get the second partition on the 16GB card to mount, which prevented me even from experimenting with symlinks. I also installed the latest version of Link2SD, but when I tried to use it to move an app that Link2SD labeled as movable, I got this:
!Failure
App2SD is not supported by your device. Because your device has a primary external storage which is emulated from the internal storage. You can link the app in order to move its files to the SD card.
Click to expand...
Click to collapse
Dunno why it's blaming Apps2SD unless Link2 is built around Apps2.
Curiously, I installed Aparted, too, and it was able to access (and process) the 2nd partition, even though it wasn't mounted. I've not heard this definitively but I'm led to believe this is down to the L34C's lack of support for init.d. So I downloaded a copy of daishi4u's custom boot image, which includes support for init.d, but the old phone crapped out before I could try it.
So with background in place, and a spanking new L34C in hand, on to the questions.
#1. With the current state of L34C/KitKat development, is what I'm asking even possible? Once the internal SD card has got too crowded for a Nandroid, is there a solution that will allow me to continue making local Nandroid backups? In particular, I'm thinking there might be another Nandroid backup app that I am unaware of that can write its backups to some location other than the internal SD card.
If this already has been accomplished (and is documented online), please just point me to the details and I'll get out of your hair.
2. I picked daishi4u's custom boot image because the reputation of daishi4u's work is known to me, and because it offered init.d support. If you think another boot image is preferable, please enlighten me.
3. Is Link2SD's problem with the L34C truly the emulated storage? I ask because I know developers typically code apps to make a best guess as to the cause of an error, but despite their best efforts, an app still is liable to be exposed to unanticipated conditions, resulting in a problem that might be beyond the scope of their programming to understand and enunciate.
4. Is the lack of init.d support in fact what prevents an L34C mounting additional partitions on the external SD card? Or am I barking up the wrong tree?
5.a. I found a post in another forum that was near three years old stating that the extra partition on an Android external SD card must be no more than 2GB, and preferably just 1GB. If this ever was true, is it still the case for KitKat? And what is the source of the limitation?
5.b. If there is a 2GB partition limit, is there a limit to how many 2GB partitions can be externally mounted? A Nandroid backup of a heavily configured L34C could take up most of 2GB, so it would be especially useful work-around if there were one (additional) partition for the Nandroid and a second (or third, or fourth, ...) for moving apps and random data off the internal SD.
6. Which app(s) would you suggest I try for moving apps/data/folders to the external SD? There are so many available, and I have not been able to find any comparisons/contrasts of their relative merits, so I would appreciate your recommendations to avoid having to resort to the 'shotgun' approach. This is presuming I'm able to get more than one partition on the external SD card to mount.
I've not lost sight of the fact that some of these apps do not require a second partition on the SD card (creating something functionally akin to an iSCSI partition on it?), but I'm not counting on finding a solution in one of them.
Thank you for taking the time to read my long-winded post.
Well personally I don't keep more than one nandroid on my phone but what you may wish to do is transfer them to your pc for safe keeping and not have to worry about it. You could also try inserting your sd card into your pc and manually transferring the nandroids from your pc to your sd card afterwards. It may work.
Now with regards to the sd card write protection issue, I could not locate anything for your device in particular but if you register you can ask your question here and someone may be able to help you.

[Completed] Request for help with Android tablet storage partitioning.

Hello,
I am a new Android use, but I have some knowledge and experience with computers (wintel platform mainly).
The Android tablet that I own was given to me as a present, at the beginning of this year (I did not choose it). It's technical characteristics can be seen in the pictures contained in the attached zip file.
My problem is the following: the partitioning of its built-in storage (which I think is 16GB), for reasons unknown to me, is such that the "internal storage" of 1GB (almost) very quickly becomes full from the installed apps that soon these apps cannot even be updated. Most of them cannot be moved to what is referred to as "USB storage" or to the external SD storage.
I would be grateful if somebody would tell me how to re-install the system with e;ither one partition (whatever remains of the 16GB after the OS and other system s/w is installed) or, if the presence of an "internal storage" partition and a "USB storage" partition is "obligatory", then I would like the "USB storage" to be the smaller one (the minimum "required"). Any "data" (music, videos, photos) I will put in the external SD storage.
If the solution that will be proposed requires the installation of a ROM different from the one supplied by the OEM of the tablet, which in turn will mean that I loose whatevet warranty I have, that's OK with me.
Thank you to anybody who will take the time to read this and offer a suggestion for the solution of my problem.
George (geokats56)
Hi, thank you for using XDA Assist. Android uses many different partitions to operate properly. You really don't want to be messing with them. Unless you really,really,really know what you're doing you will brick your device and make it inoperable. You also won't gain much in usable space. So, while 16 gigs isn't that big, I'd learn to live with it.
Reply to jd1639
Hi jd1639,
Thank you for taking the time to read my post and respond.
Actually, I am not complaining for the 16GB, which is probably adequate for the purposes that I intend to use the tablet for. I am complaining about the fact that the manufacturer saw fit to allow only 1GB (of the 16, minus the approx. 3 that the "system" consumes) for the partition where everything seems to want to work in, mainly the applications that are downloaded from Google Play store. After a very little while, this partition becomes full, to the point where the already installed apps can't update themselves, when the OS finds out there is an update available and "prompts" the user to proceed with the update.
I most ecrtainly don't want to brick the tablet, and because I am not an experienced Android user (as I already mentioned in my original post) I am asking for guidance.
Best regards,
George (geokats56)
I really don't recommend you mess with the partitions. But see this, http://forum.xda-developers.com/showthread.php?t=2234515. Read it very carefully and make sure you understand what you're doing first. If you have any doubts ask in that thread. The guide is for a specific device. Your partitions will be different. See this also, http://forum.xda-developers.com/showthread.php?t=2450045 also this, http://www.xda-developers.com/uapm-partition-management/
Thanks!
Thanks again jd1639, for taking the time to send me the info.
Best regards,
George (geokats56)

Categories

Resources