Just a question, everything I see being LZX compressed says you must flash it via sd card. I understand the factor of it being less than 50 MB and the RUU won't take it. But what if a rom is over 50 MB and is lzx compressed, what are the rammifications of using the ruu to flash?
I think that LZX compression has to be flashed through an SD card not only because the RUU wo't take it, but because the RUU doesnt know how to deal with a compressed image file. Correct me if im wrong but I do know that this is so with things like game system emulators.
Hehe look what I can do
I got to playing around with the kitchen and decided to experiment a little... I cooked up something through super just and made it around 50mb. Got the standard invalid image size through the RUU. I then threw a couple things more on there to make it 53 MB and it flashed WITH LZX compression. Made it to 100 percent and hasn't bricked on me yet. I'll see how this thing runs through out the next day or two to see if it bugs out really bad.
UPDATE: It seems to work fine but it's slower...
Related
I am a bit disappointed on the available flashrom space on the Kaiser. On a machine that is marketed with a whopping 256MB Flashrom, in reality, only ~130MB is available.
Now I understand that the OS and the pre-installed softwares may take up some rom space. However, I can't remember any other device taking up more than 70-80MB max on the rom! Besides, there aren't many software that are built-in to the device!
So where did our space go?!?!?!
Anyone know?
Τhe windows folder after hard reset is 113 mb !!!! I think we need new ROM...
panosha said:
Τhe windows folder after hard reset is 113 mb !!!! I think we need new ROM...
Click to expand...
Click to collapse
This is nuts! I can't seem to locate what is using so much space in the windows directory!!!!
There is a mxip_initdb file that takes 16MB!!!
Hallo everyone,I am stuck in a problem for a long time,As you know,X1'ROM is 512 MB,but my device storage space is always about 200 MB though my rom file is usually smaller than 100MB,I thought it should be about 512-100≈400 MB or some Left,I wonder Where does the missing 400-200=200MB space go?and need a way can solve this,THX
Finally I get the reason,Because i use OSBuilder to create Imgfs.bin,and now I use ImgfsFromDump,It is OK now,thanks all the same!
Hmm, I think device memory is slip into 2 sections... 1 is Storage, 1 is Program... Maybe i wrong, but if u should check that in ur X1, Settings---> SD card and Phone Storage.
U will see that there are 2 section for all, Device and SD card, and Device has 2 sections that are Total storage and Total Program.
Hope u understand my English, I'm learning Eng now, so i still practice it
It depends on rom what you are using. The rom file (nbh) is compress so the decompressed size is about 2 times larger. And people usually use the cutomization what starts after rom update. It also uses some space. Just do a hard reset and see how much space is used.
So yes the 200MB is believable.
Shady313 said:
It depends on rom what you are using. The rom file (nbh) is compress so the decompressed size is about 2 times larger. And people usually use the cutomization what starts after rom update. It also uses some space. Just do a hard reset and see how much space is used.
So yes the 200MB is believable.
Click to expand...
Click to collapse
thanks for your relpy , And Maybe I did'nt describe it well , I mean when I cooked a rom that is 100 MB then they storage space is 200MB , When rom is 80 MB ,the storage is still 200MB , even 60 MB, no space increase or decrease when rom is smaller or bigger,that's the problem
Has anyone tried Clemsyn's updated kernels from the Kaiser section on the Vogue? I'd like to try them since people say they are more stable, but ATools doesn't work for me and can't properly get the kernel to install on nand... Keeps making system and data .imgs regardless of settings.
Anybody have a working kernel they could post?
Have had the same issue. Would love to try clemsyn's rom on Vogue but can't get it to work through Atools.
I've gone back to Incubus's v12 froyo just for the battery life. I think v10.5 had the best battery life, but was a bit buggy. Using the latest rom from liq1d (Nov 30? i think) Relatively stable with v12 and decent battery life again compared to thoughtlesskyle's v17.
Try this out...
Download the latest Atools 1.1.4 here:
http://sourceforge.net/projects/androidhtc/files/AtoolsRelease/
Open Clemsyn's Kernel - located here:
http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
With the Atools 1.1.4.py - choose Vogue, screen res, Froyo, then save it somewhere.
Now - use the attached Atools to open that new saved NBH and edit it how you want for your Vogue.
Save this atools-old.zip - this is the one I always use to modify kernel NBH for my vogue.
Forgot - also for the newer NBH files, l1q1d had an update file that needed to be applied
to Froyo builds so that it would allow it to boot - attaching that as well as it can be hard to find.
@Does_It_Matter: Does work the USB mass storage with this kernel?
Josue_181 said:
@Does_It_Matter: Does work the USB mass storage with this kernel?
Click to expand...
Click to collapse
Nope - can't get it to work for me.
Last working kernel for the Vogue - WITH USB support working, was the
10-31-10 2.6.25 NBH kernel - I tested all of them - lots of flashing!
I can say that it does not work, but the smart thing to do for stability right now is to use data on SD anyways for space reasons also stability if on .32 kernel. With that you could just pull the card out and put it in a reader. That is what I do with my card.
Does_It_Matter said:
Nope - can't get it to work for me.
Last working kernel for the Vogue - WITH USB support working, was the
10-31-10 2.6.25 NBH kernel - I tested all of them - lots of flashing!
Click to expand...
Click to collapse
Ok, thank you very much for the information I will continue with that kernel because the solution that I mentioned aceoyame not seems best.
aceoyame said:
I can say that it does not work, but the smart thing to do for stability right now is to use data on SD anyways for space reasons also stability if on .32 kernel. With that you could just pull the card out and put it in a reader. That is what I do with my card.
Click to expand...
Click to collapse
Improved stability with data on SD? This is the first I've heard of this, but I'm definitely interested. Are you talking ext2 or data.img? Is this related to the yaffs thing, or just personal experience? I would love to see my phone freeze less.
It is related to YAFFS. On SD it uses EXT2 or an image file. The image file is the best as it has file checking on it every boot/mount. YAFFS is the file system on the NAND and we don't have it working 100% stable just yet. If you do go the SD route just have a fast SD card. Don't spend extra on a class 10 card as it will be a moot point. The card can't push 10 MB/s in our devices. Even 6 is almost pointless, I wanna say it pushes around 5 MB/s
Thanks for the nice explanation. I guess I had discounted the .img method because it was the "old way", but I guess that means it's just extra well tested. Would ext2 have performance benefits over the .img? I'm not entirely sure what's in the .img file--is that just a virtual partition of ext2? Or is it a different file system altogether? Is it using any compression, or is it just a direct read/write file?
Now that I think about it, my phone was at its peak stability back in the days of Fresh Froyo using ext2 sys/data through Haret (before I had the courage to flash to nand). Nand brought speed and ease of rebooting once crashed/dead battery, but in the stability department it never held a candle to the SD card.
I like the idea of mixing system on nand and data on SD. I think I will try that tonight. No sense messing around with yaffs corrupting my files every day.
wondercow said:
Thanks for the nice explanation. I guess I had discounted the .img method because it was the "old way", but I guess that means it's just extra well tested. Would ext2 have performance benefits over the .img? I'm not entirely sure what's in the .img file--is that just a virtual partition of ext2? Or is it a different file system altogether? Is it using any compression, or is it just a direct read/write file?
Now that I think about it, my phone was at its peak stability back in the days of Fresh Froyo using ext2 sys/data through Haret (before I had the courage to flash to nand). Nand brought speed and ease of rebooting once crashed/dead battery, but in the stability department it never held a candle to the SD card.
I like the idea of mixing system on nand and data on SD. I think I will try that tonight. No sense messing around with yaffs corrupting my files every day.
Click to expand...
Click to collapse
Yep thats the logic I used. Any Odex'd build with Clemsyns kernel with Sys on Nand and data on an img file will last a long time. I haven't had corruption in over a month I wanna say with light usage on my kaiser. The odex'ing helps just because it makes for less writes to NAND.
I have a 8gb sd card and tying to figure out how big to make the two extensions?
Depends on the rom. Sense needs more because of the size of the rom, but if you just use a2sd you can get away with 500 - 750 mb.
evilkorn said:
Depends on the rom. Sense needs more because of the size of the rom, but if you just use a2sd you can get away with 500 - 750 mb.
Click to expand...
Click to collapse
That is what I thought but haven't seen much on it. Thanks
Hello Everyone
I rooted and already have my phone the way I want it but I've noticed that when you do the full wipe
theres like 7 gigs of space missing. I was wondering if anyone was able to at least get most of their space back when they wipe the phone
if so how can i do it?
I currently running the Rage Rom thinking of going back to Ecliptic ONE
and i have TWRP recovery
any ideas will be appretiated thanks
Have you made any backups?
g00s3y said:
Have you made any backups?
Click to expand...
Click to collapse
I made a back up but i deleted it unless theres another back up am missing somewhere?
how much space you supposed to have after the full wipe?
I recently did a full wipe and it was like 6.x gigs right off the bat. It boggles the mind, considering there are phones out there that have only that much total capacity.
Wtf htc.
Does anyone know how much space AOSP roms take? I'm switching once the installer comes out.
sauprankul said:
I recently did a full wipe and it was like 6.x gigs right off the bat. It boggles the mind, considering there are phones out there that have only that much total capacity.
Wtf htc.
Does anyone know how much space AOSP roms take? I'm switching once the installer comes out.
Click to expand...
Click to collapse
AOSP ROMs are typically around 120-150 Megs zipped, sense ROM go.from 700 to a little over 900 MB's zipped.
https://vzwsupport.jive-mobile.com/#jive-discussion?content=/api/core/v2/discussions/804286
It's only 25 GB available left. :-[
Sent from my m7spr using tapatalk4
phatmanxxl said:
AOSP ROMs are typically around 120-150 Megs zipped, sense ROM go.from 700 to a little over 900 MB's zipped.
Click to expand...
Click to collapse
Right, but I'm asking for how much CM takes after installation and clean wipe. I'm not sure how compression works, so this may be wrong, but if I set up a proportion (I'm almost sure you can't do that), CM comes to 1.5 gigs installed (205meg for 10.2 zipped), which seems more reasonable.
It really sucks that I have to keep clearing out stuff because I start with only like 25 gigs of space rather than 31.5.
Can somebody who has 10.2 installed comment?
if its off a fresh boot, it's because of all the apps that prolly installed to the internal sd got erased, thats why you had more space, and still have your files and stuff
ticklemepinks said:
if its off a fresh boot, it's because of all the apps that prolly installed to the internal sd got erased, thats why you had more space, and still have your files and stuff
Click to expand...
Click to collapse
I (tried to) delete ALL data from my phone and it was still 7 gigs.
Got this explanation from another site.
The 32GB are in 1000Byte = 1KB Logic, and the 25GB should be in Binary Logic, so 1024Byte = 1KB. which gives at first a "loss" of about 2GB: 32GB = 29,8023GiB
the rest of the space is mostly the android system, reserved space for cache etc... one small part will be the journal of the ext file sytstem which is used instead of yaffs. So arround 200-400MB i think will be covered by the ext journal.
you have the same problem with harddisks too. The firms write it in decimal logic but the operating system does it in binary. Some Operating Systems nowadays also write the correct GiB or MiB or KiB but not all...[\quote]
Click to expand...
Click to collapse
use a file explorer and go back as far as you can. Check /data/media. if you've ever flashed a 4.2 rom it moves all your files around and it gets confusing.
If that doesn't find it, download Diskusage. it could help you out.