Related
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Sent from my MT11i using XDA
mpiekp said:
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Click to expand...
Click to collapse
Any noticeably difference? Run any benchmarks? I never understood why SE used yaffs2 for phones, same as why ext4 isn't supported by default, but that's other story
Anw, I guess now you can only install rom via .zip from CWM? Or maybe even flashtool wouldn't complain, but I guess PCC would complain for sure
p.s. respect for trying that
report pros and cons
Lol to revert just flash s zip that formats as yaffs, will try flashtool, although don't expect an issue as it basically raw writes the sin, which are complete img files including filesystem.
Benchmarks would be pointless, due to running experimental build anyway so nothing to compare to, but things like file manger appear more responsive.
All I can say is try it, make sure the updater-binary you use can accept 4 arguments for format and mount (hint the one in codename can), place that into any Rom zip and edit the updater-script.
So the format line is like this
format("ext4", "MTD", "system", "0");
Sent from my MT11i using XDA
Wonderful and brave find!! ext4 are supposed to be safer (journalism), but can have some overhead.
I have seen a script that even converts live yaffs2 to ext4 in some other forum, so that formatting is not required.
Otherwise, after format, you can restore the backups!
I am really interested to know if the partitions can be resized, so that we can have more space for /data (instead of 100 mb /cache and such a large /system)
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
mpiekp said:
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Maybe those links help you understand :
http://forum.xda-developers.com/showthread.php?t=1566846
http://forum.xda-developers.com/showthread.php?t=1449917
how can we check the type of our partitions?
I'm researching a bit, and people say that yaffs2 is better than ext4 for NAND memory.
I need to research a bit more on this matter.
I am here to learn.Thanks for sharing.
termagazis said:
how can we check the type of our partitions?
Click to expand...
Click to collapse
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
su
Click to expand...
Click to collapse
df
Click to expand...
Click to collapse
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
400 for system is excessive, should be safe to bring down to 300, forget vendor 6m is not worth worrying.
With /cache that could be another 200mb for data.
Also boot is a worry, formatting the blocks of mtd doesn't appear to work, could rewrite the array, but may kill boot, which would be a hard brick.....
Sent from my MT11i using XDA
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
leajian said:
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
Click to expand...
Click to collapse
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
termagazis said:
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
Click to expand...
Click to collapse
In that case, just time
mount
Click to expand...
Click to collapse
in Terminal Emulator and see that every partition is reported on what filesystem it is.
More info @ http://www.cyberciti.biz/faq/linux-how-to-determine-find-out-file-system-type/
Or run it as root
Sent from my MT11i using XDA
yacloo said:
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Before you will notice any degradation of NAND, you will sell this phone and forget about it, so...
I made a mess
do I change file system? dont i change it? good or bad?
Actually, it is that easy.
However, all the kernels are set to mount as yaffs, so you also need to unpack and edit the config files in the kernel too.
Sent from my MT11i using XDA
Hello all.
I started to develop my edition of JB, but i had a problem. The system partition is about 600MB, and the deodexed version of stock samsung's JB rom is about 700+MB. (Odexed should be about 800MB)
Firstly i did extract system.img to deodex it but a problem occured. Many apk files (about the half!) were missing (.odex files were still there). I was stuck. So i did an "adb pull" from my phone and i had all the system files, strange huh? I deodexed them (=> smaller size), removed bloatware and the system folder was about 675MB. I zipped it and flashed it from recovery. Phone was booting and booting and booting for 15 minutes... I re-checked the files and i saw that the system files were bigger than the system partition.
Then i checked for a hidden partition to find the "extra" space required for system. In "CSC" tar file of JB there is a hidden.img. In GB there was a small video by samsung so i thought that it would be again the same video or similar. I was wrong. Inside this file there are many apk system files (about 200MB!). I checked the firmware in my phone with root explorer and i saw that there are many symlinks from /preload/simlink/system/app/ to /system/app/ . That explains the Samsung's logic. Anyway i think that this is a bit fail. Why samsung didn't resize the system partition so it can handle all system files? Anyway, i will make a flashable test rom with some files in /preload/ and then i will symlink them (in updater-script) to /system/app/.
So for conclusion there is:
-a /system partition about 600MB and
-a (fake system) /preload partition about 250MB to handle most of the /system/app/ folder.
Also, temporary CWM6 for JB is working fine to install zips or anything or for backup and restore.
I thought it will be useful info for any dev here.
I solved this major problem and i will focus in Kyrillosv6b JB rom this week. I have already done many mods for JB but i couldn't test them because of that.
Have a nice day.
Maybe they just used this solution for the xxmb2 test version and for the final version they will resize the partition table.
It's a "strange" solution but I think not that bad.
We still don't know where is the imei/simlock data it's possible they don't want to modify the partition layout if not really necessary, to keep important data safe.
Repartitioning the device is always risky...
Sent from my GT-I8160 using xda app-developers app
Szaby59 said:
Maybe they just used this solution for the xxmb2 test version and for the final version they will resize the partition table.
It's a "strange" solution but I think not that bad.
We still don't know where is the imei/simlock data it's possible they don't want to modify the partition layout if not really necessary, to keep important data safe.
Repartitioning the device is always risky...
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Hmm simlock and imei data are on /efs partition... But we did repartition the device for JB. There wasn't a "preload" partition on GB i think.
It's not on efs I erased my efs partition to try (ofc. I made backup first) and the imei was ok
I tried to restore efs from a different phone and nothing changed.
I remember there was something else not preload will check tomorow but I'm sure that unpartitioned space was only 10 MB and it's still 10 after Jb.
Probably preload in gb was named hidden just like the file and the video file was moved to internal sd or symlinked.
I know we had to rp but I can't see much difference, even the counter data is stored on the same offset.
Sent from my GT-I8160 using xda app-developers app
Yeah. 30 APKs were not deodexing on mine. permissions were rwxrwxrwx when I looked. some didn't have sizes, others had -1 bytes.
Is there any way we can deodex JB ROM? I don't know how to mod and odexed ROM.
Dr01nE said:
Yeah. 30 APKs were not deodexing on mine. permissions were rwxrwxrwx when I looked. some didn't have sizes, others had -1 bytes.
Is there any way we can deodex JB ROM? I don't know how to mod and odexed ROM.
Click to expand...
Click to collapse
I will upload the deodexed MB2 tomorrow. but as i said at the first post, it doesn't fit on /system partition.
kyrillos13 said:
I will upload the deodexed MB2 tomorrow. but as i said at the first post, it doesn't fit on /system partition.
Click to expand...
Click to collapse
I have completely deodexed it the problem is flashing. I also get stuck in bootanimation and it keeps vibrating.
Let me know when find a way to flash it. For the mean time, I'm back to GB for theming.
Dr01nE said:
I have completely deodexed it the problem is flashing. I also get stuck in bootanimation and it keeps vibrating.
Let me know when find a way to flash it. For the mean time, I'm back to GB for theming.
Click to expand...
Click to collapse
You should copy most of /system/app folder to /preload. Because system partition is small to handle all files.
kyrillos13 said:
You should copy most of /system/app folder to /preload. Because system partition is small to handle all files.
Click to expand...
Click to collapse
I'll try this one later, I need to finish my theme.
Will it have all Kyrillos V5 features?
Sent from my GT-I8160 using xda app-developers app
Here is a comparision between GB and JB (partition table).
There is no difference in size, I have no idea why was repartition required for XXMB2.
I think preload wasn't mounted in GB but I'm sure it's the "Hidden" partition.
malamharian said:
Will it have all Kyrillos V5 features?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Yeap.
Szaby59 said:
Here is a comparison between GB and JB (partition table).
There is no difference in size, I have no idea why was repartition required for XXMB2.
I think preload wasn't mounted in GB but I'm sure it's the "Hidden" partition.
Click to expand...
Click to collapse
Hm interesting.
I'm testing that too.
The deodexed ROM boots but having too problems:
- The baseband is unknow and i can't recover it flashing modem or EFS partitions.
- I have a android core stop and can' t pass the first screen.
My deodexed ROM has 430 Mb but maybe is not complet and because that i have the android core problem.
http://forum.xda-developers.com/showthread.php?t=2030594
Messi10 said:
http://forum.xda-developers.com/showthread.php?t=2030594
Click to expand...
Click to collapse
So we need to create an APK which contains
Code:
Link: /preload/symlink/system/app/nameofapp.apk
Manually doing this will definitely take a lot of time.
But is there an easier way or hassle-free way of doing this?
Dr01nE said:
So we need to create an APK which contains
Code:
Link: /preload/symlink/system/app/nameofapp.apk
Manually doing this will definitely take a lot of time.
But is there an easier way or hassle-free way of doing this?
Click to expand...
Click to collapse
You have those symlibs apps in your System/app from system.img or backup. if you open the fake apk with some editor you can see it.
Because that you can't deodex it with the kitchen , you need the real apk from preload.
cbolumar said:
You have those symlibs apps in your System/app from system.img or backup. if you open the fake apk with some editor you can see it.
Because that you can't deodex it with the kitchen , you need the real apk from preload.
Click to expand...
Click to collapse
You cannot deodex the 30 APKs that are symlinked on preload using the system.img from leak fw. but copying them from /system/app/ to /sdcard/ gets you the real APK. What i want to know is how do I include preload links in flashing with script or is it better to do it manually. Because pushing a symlinked file directly causes and infinite bootloop and vibration. (-___-)
Dr01nE said:
You cannot deodex the 30 APKs that are symlinked on preload using the system.img from leak fw. but copying them from /system/app/ to /sdcard/ gets you the real APK. What i want to know is how do I include preload links in flashing with script or is it better to do it manually. Because pushing a symlinked file directly causes and infinite bootloop and vibration. (-___-)
Click to expand...
Click to collapse
Did you try the frapeti method?
We can also edit the pit file and resize system partition or remove some system apps,ringtones,boot animation... Till apps fit in
Sent from my GT-I8160 using xda app-developers app
Messi10 said:
We can also edit the pit file and resize system partition or remove some system apps,ringtones,boot animation... Till apps fit in
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
yes , i'm doing that but i have some problem with some specific apk because i have a rom booting and another smaller not boot.
I have been doing a lot of restoring, it would be nice to just be able to push the flash rather than geting an os installed, installing a recovery and then recovering.
I saw something for another samsung device and it involved dd'ing files and then putting them into a tar. but i suspect the /dev/xxxxxx files would be a different name on the GT10.1?
Thanks
Rob
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Right, but they are dumps of the /dev/system|recovery|... file systems from using dd to get a binary image, they are not the files like in a zip. which is why, if my reading is correct, zips actually get processed (extracted and moved) and the files in the odin.tar are binary dumps and they just get splatted back out into the file system like a Norton Gost restore. The trick is knowing which /dev/xxxx/ systems to pickup. I found a link right before leaving for work that seems to suggest if I get rooted and busybody on, I should be able to run an fdsik -l and get a list of the partitions.
I just got the stupid tablet back to stock ICS 4.04 this morning after running updates last night, so I hope to have some time play today.
i am using CM10.1 with the A1 kernel and a little bit ago, i could just simply go to the /sdcard directory to get to it but now, i have to go to /data/media/0/ and that's the sdcard and everytime i flash a rom it adds a 0 so it'll be /data/media/0/0 which i don't understand why it's doing that. can anybody help me with this issue? thanks!
You can move your files out of the second 0 to the first 0 then delete the second 0.
Its because of JB 4.2. Google implemented the multi-user function. In order to do that, they added the 0.
Sent from my GT-P7500 using XDA Premium HD app
Oh okay, thanks for the help! I didn't know what was going on, lol
Sent from my GT-P7510 using Tapatalk HD
What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X