Related
Does anyone know how to make a complete memory dump (RAM) of the XDA, apart from the m? commands. These commands give a memory, hex, text breakdown. What i'm looking for is a command that get's 32MB of data and stores is as 32MB of DATA (the the invoking and storing the dump is obvious, so no tips on those please, i only want the commands get this raw memory dump).
Regards,
René
I just read up on some of the other stuff in here.
Somebody mentioned the XDA has 32MB of RAM "AND!!!" 32MB of flash ROM.
So, is this true? And if so. Does this mean that the organizer data is held in flash ROM allways? (this would in my opinion not be correct with some of the functions of the XDA, but OK). And if so..... How do i make a raw dump of this memory?
Cheears,
René
dumping ram
Hi,
I'm not aware of a means to dump RAM using the bootloader functions. However I'm considering developing something for it. It shouldn't be too hard with a bootloader patch like we developed to get around 5.17 limitations.
What I'm looking for is info on how data is organized in RAM such as the filesystem. The 32 RAM contains semi persistent data while the ROM contains what is needed to reinitialize the device and system binaries. However, as far as I understand, applications you install additionally and any application data is only stored in RAM. Anyone knows how the filesystem works on the lower level? I'm looking to implement a tool that can read such a RAM dump and make sense outof it.
Ok, so i came up with the idea of using the m? functions for dumping the data (what is the difference between those anyway?), into a huge file (you get 80bytes for each 16 bytes of data, so 160MB for a 32MB model and a hellufa lot of time, say 4 hours at 105200), and than parse these back to the original 32MB, based on the hex dump supplied.
As to your question, for which i'd like the answer myself, about the file system: as it's windows, i hope it will be some form of FAT or NTFS, but what i've seen so far, i'm afraid it's the system MS developed for storing their office documents....
Does anyone know if parts of the data are stored encoded/crunched/ encrypted?
Anonymous said:
As to your question, for which i'd like the answer myself, about the file system: as it's windows, i hope it will be some form of FAT or NTFS, but what i've seen so far, i'm afraid it's the system MS developed for storing their office documents....
Does anyone know if parts of the data are stored encoded/crunched/ encrypted?
Click to expand...
Click to collapse
I doubt if its FAT or NTFS, as it needs to handle having its size limitations changed dynamically as the device manages objectstore<->memory changes.
And its all stored compressed.
..Chuck..
Well, I recently managed to work out what RAM belongs to the file system, and dump that ram only. And within that RAM I've found some files, and their compressed data, and used the BinaryDecompress calls to decompress it and verify the contents.
However I still can't work out the overall structure that provides the pointers/identifiers to the location of the files, I just happened to find certain files by searching on the filename (which is stored uncompressed BTW).
Has anyone else been trying this?
..Chuck..
I have probably a stupid question, but I ask it.
I would like to know if it is possible to upgrade a pda without flashing ? why it is not enough to install a big cab and load registry ?
I know most of the pda have just 64 Mb memory. and often the rom is 64 Mb, so if we do like that at the end we will have no memory.
But O2 XDA Flame has 2 Gb of memory. so 64 Mb is nothing and I can spend it, if that allows me to upgrade it without the need to cook a rom with complex tools, to find how to be in bootloader, and without the ask to brick it.
Stupid question ?
I can't imagine that no one knows concerning my question in xda- devs.
Not so stupid question. But the answer is simple - because the bootloader was designed in such a way it can only load the OS from its special partition in a special manner.
There are some ways to boot from specially formatted SD, but thats all.
and a cab file is a pocketpc install file
a pocketpc install file cant change the os
because it would mean that the installed things
had to update the system which was running it
think sawing over the branch you are sitting on in the tree
Theoretically, you could overwrite all the non-system files (or at least the ones not needed for initiating the boot) with all the new files and overwrite the hv registry files... but I wonder how well this would work... And how fast it would be if you're not using modules but instead just files... and you couldn't really update it to WM6...
Thanks to all of you.
When I have asked the question, we where not able to flash the Flame. Now we are.
So know I am in the process to port wm6 on the Flame.
I have extracted the xip of the Flame using xipport.
And I have also extracted the xip of the WM6 port to Universal of ranju.
Now I am in the process of merging the 2 xip.
If somebody can give me some advices, I will be glad.
Ranju has started. But I need more info in the process of mixing.
I have a htc rhodium 210(t-mobile branded) and i am running the latest xdandroid froyo (as of a few days ago) And iv been gettn a low phone storage space alert in my status bar asking me to uninstall apps wenever i install a new one. Also if i receive messages while this alert is there they are delete due to 'lack of storage' But when i open appmonster to uninstall some apps im told i have used only memory:24mb/247mb SD:1.991/7.560mb and im using an 8gb micro sd which is less than half full so storage shouldnt be a problem?
Any ideas and why im gettn this warning and is there any way to stop it? because i dont have a huge amount of apps and i shouldnt have to keep uninstalling decent apps when i should have enough storage.
tanks in advance
This has been answered several times before...
The data.img file is only 256mb. If you want a bigger one, you have to either expand the file yourself or modify the rootfs so it builds a larger data.img.
For most, 256mb is plenty. Lots of people don't even come close to using that much, plus if the users card was only 512mb, creating a 512mb data.img on boot would be a problem.
Ok tanx, sry if this sounds like a noobish question but how can i expand my data.img file? without creating a new one.
but wait i dont even need a bigger data.img file because it shouldnt be full. It says im only using 24mb outta the 256. And yet it still says low storage and rejects my messages?
Huh... I don't know. I've never had it reject my messages before, or give me that error message.
May want to try the typical troubleshooting crap. Delete (move, rename) data.img, delete everything & start with a fresh build, format SD & start completely over - in that order.
yeah iv tried that, id say my best bet would be to expand the data.img file do you kno any way to do this?
Jandyman said:
yeah iv tried that, id say my best bet would be to expand the data.img file do you kno any way to do this?
Click to expand...
Click to collapse
Either you can expand it manually or modify the rootfs to create a larger one for you.
how can i edit the img files? i have vista and no way of opinging these files. Iv heard you need linux.
Jandyman said:
how can i edit the img files? i have vista and no way of opinging these files. Iv heard you need linux.
Click to expand...
Click to collapse
Yes. Virtual machine to the rescue!
Try cachemate picced up 8mb
Sent from my MSM using XDA App
tanx for the help, iv searced and found no program capable of simply editing the file and saving it bigger so il try my hand at using virtual machine, or a friends netbook running ubuntu to do so. But having little or no knowledge of the layout or coding an whatnot in the files it will probly take some more time and searching to figure out.
also i am now using cachemate also, it doesnt solve my problems but its handy app nonetheless for quick freeing up wen im browsing and get the low storage message.
.. is there a way to make the data.img bigger directly on the PDA? may be with the total commander?
THX
_cv
_cv said:
.. is there a way to make the data.img bigger directly on the PDA? may be with the total commander?
Click to expand...
Click to collapse
Did you think I was joking when I outlined the two methods required to expand the file...?
arrrghhh said:
Did you think I was joking when I outlined the two methods required to expand the file...?
Click to expand...
Click to collapse
sorry, but i thought that there are more solutions and you are talking about two of them.
OK, i understand there is no way on my PDA to make the data.img bigger.
grz
_cv
If you want to make the data.img file bigger than 256mb, I suggest you to use Neopeek's build. It is totally a different setup since neopeek's doesn't use the data.img file. If you want to have more storage, you are gonna have to make the ext2 partition a little bit more bigger using GParted Live, max is 512mb. Right now I have my ext2 partition to 495mb and I have more than 30 app's installed and I haven't gotten one of those messages you get.
Found a post where a guy setup a 4gb data.img...
Here
1 GB rootfs
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
devilcuban said:
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
Click to expand...
Click to collapse
Awesome dude I was hoping someone would post a 1gb one All I could find was that 4gb one haha! Now peoples have choices!
arrrghhh said:
Awesome dude I was hoping someone would post a 1gb one All I could find was that 4gb one haha! Now peoples have choices!
Click to expand...
Click to collapse
haha yea no problem 4GB its alot specially if u only have a few GBs on the SDcard lol, i did a 512mb but my girl downloads 2 many apps lol wasn't enough lol,
devilcuban said:
Here is my modded rootfs.img i use to create a 1GB data.img. Use it will create a 1GB data.img. its only a few days old, but after the data.img is created you can raplace it with the new up-to-date rootfs.img. Hope this works for ya
Note: you must create a fresh Data.img for it to work.
Click to expand...
Click to collapse
So. I just have to delete my data.img. and my rootfs.img. and replace it with yours (rootfs.img)?
sprint htc touch pro 2 (rhod400)
I have done wonderful things to my device thanks in large part to this community. Thank you.
I see that the system partition has about 1 GB of free space yet there are only 427 MB of files in there. Do I need that much free space? If not, how can I safely resize it?
Using parted. I've tried doing it though, shrinking my data partition to give more to system but it won't stick for some reason. Either I'm doing it wrong, or it doesn't work
The parted binary for android can be found on Cyanogenmod's github in the android_bootable_recovery repo
@CNexus, thanks. I appreciate that. I'll take a peek at that. Strangely enough I'm looking to shrink my system partition. I've seen others are wanting the opposite.
I've partitioned PC drives before but this appears to be much more involved.
Does anyone know of an optimum allotment for system and cache that I should follow?
You should be fine whatever you do.
Worst case if something goes wrong, just flash the PIT file for your internal storage size in Odin and all should be good
But yes, this will be more involved since it will need to be all command-line
SO basically im trying something out and i need to add a partition to my android device thats about 100mb big. Is this possible? the Sdcard wont work as a partition
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
CNexus said:
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
Click to expand...
Click to collapse
will modifying that file be able create an extra 100mb partition so when i hook it into my comp two partitions show up?
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
CNexus said:
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
Click to expand...
Click to collapse
Alright thanks im looking into it know do you know how to dump one from a phone? as google is not bringing up anything besides info on what it is
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
CNexus said:
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
Click to expand...
Click to collapse
its a 16gb lph 710 ill look into heimdall thanks
What's your current bootloader version? If not known, run
Code:
getprop ro.bootloader
In a shell on your device/terminal emulator app
And then post the last three alphanumeric characters
Sorry I realized the bios of a comp doesn't recognize the android phone as a peripheral or a mountable boot device which ruins my plans as of now I'm going to try to find a way to at least get the bios to pickup the SDcard if I can I'm doubtful though