Database Users

[i9001]Discussions about development of CM7 and CM9

Hi to all!
I've created this topic that we can discuss about the CM7 and CM9 ROMs that are in development, and not flood the development topic with Q&As. Feel free to post!

How to avoid bricking the SGS+
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!

You can get the most important partitions from the wiki: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9001#Partitions
I once dumped all partitions and can verify that the most important stuff is below the kernel partition, so don't mess with them. mmcblk0p14 is a parameter partition (thx skywalker01) for the bootloader, that is what causes some devices (including mine) not to work 100% correct with CWM. You can only get out of recovery boot loop by dd'ing zeros to that partition.

despotovski01 said:
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!
Click to expand...
Click to collapse
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .

rayiskon said:
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .
Click to expand...
Click to collapse
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.

Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.

despotovski01 said:
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.
Click to expand...
Click to collapse
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker

rayiskon said:
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker
Click to expand...
Click to collapse
Thanks, I've sent him a PM.

GIBbeerSKY said:
Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.
Click to expand...
Click to collapse
Are you talking about SGS i9000 or SGS+ i9001?

I'm sorry, I've missed the "1" at end of model.

well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??

YMYA said:
well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??
Click to expand...
Click to collapse
i think u already made ur choice. here and here

rayiskon said:
i think u already made ur choice. here and here
Click to expand...
Click to collapse
tht wasn't mine..
so what do you suggest?

YMYA said:
tht wasn't mine..
so what do you suggest?
Click to expand...
Click to collapse
neither. S2 or galaxy nexus

rayiskon said:
neither. S2 or galaxy nexus
Click to expand...
Click to collapse
what if i have to choose one of them..which one is better?

YMYA said:
what if i have to choose one of them..which one is better?
Click to expand...
Click to collapse
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.

rayiskon said:
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.
Click to expand...
Click to collapse
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?

YMYA said:
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?
Click to expand...
Click to collapse
although the lack of community support is a very big minus, but i'd still get the S+ , coz it's better. the only thing i miss is to try an ICS build, but i'm sure it will be here sooner or later.

DroidXDA
SGS+ News :: We almost to booting stage with now fixing the kernel (we hope it will work out) :: do support us by clicking our advert at our blog thanks Have A nice Days
Click to expand...
Click to collapse
Just to let you know...So hopefully they will get it working

What Build is current cm9 ?
One Question, What is the Build Number of our cm9 ? because i want to patch LunarUi Theme ,but it has many zips for many builds of cm9 , thanks

[HELP] Porting G2's L to G1 [KERNEL]

Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
 @VictoriousShooter
 @rr46000
 @S0bes
 @yajnab​

I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..

only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.

AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.

I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...

S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken

Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?

Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.

yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)

@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.

Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]

reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.

for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?

For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.

I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...

Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...

fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.

Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.

Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.

Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time

F2fs ROMS and kernels to try.

Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks

GorfDroid said:
Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks
Click to expand...
Click to collapse
Interested as well. Did you ever manage to install Lollipop with F2FS?

raz123 said:
Interested as well. Did you ever manage to install Lollipop with F2FS?
Click to expand...
Click to collapse
I did actually but you'll need an f2fs compatible kernel like sabermod Franco kernel.
Everyone says you need an f2fs compatible ROM but that has not always been my experience. I've used it with just an f2fs kernel and it worked.
I no longer use f2fs though. I use ext4 with journaling off. I understand it is the same thing and my phone is just as snappy.

Tpwr no f2fs option!! Any fix?

As we know f2fs is the new optimized filesystem with 12 new patch ported by sources
it could improve performance by 2x as arter97 said.... But the problem is that there isnt a recovery with f2fs option
anyone can create one?
Watch the speed video of one plus 3 with ext4 and f2fs when opening asphalt 8 !!

Alessandro999 said:
As we know f2fs is the new optimized filesystem with 12 new patch ported by sources
it could improve performance by 2x as arter97 said.... But the problem is that there isnt a recovery with f2fs option
anyone can create one?
Watch the speed video of one plus 3 with ext4 and f2fs when opening asphalt 8 !!
Click to expand...
Click to collapse
The newest version of the official TWRP has the f2fs option, but as far as I know, all ROMs are still require/recommend ext4.

Alessandro999 said:
As we know f2fs is the new optimized filesystem with 12 new patch ported by sources
it could improve performance by 2x as arter97 said.... But the problem is that there isnt a recovery with f2fs option
anyone can create one?
Watch the speed video of one plus 3 with ext4 and f2fs when opening asphalt 8 !!
Click to expand...
Click to collapse
@arter97 also said this
https://twitter.com/arter97/status/884846437556604928

david19au said:
@arter97 also said this
https://twitter.com/arter97/status/884846437556604928
Click to expand...
Click to collapse
s
yes its true but i have used f2fs for long time and i never had a performance issue
i can say that performance increase with f2fs , especcially when opening games!
so i only want the OPTION TO SWITCH YO F2FS, nothing more!
anyone is responsible for everything that do on our phone!

I only had troubles with f2fs. yes the performance is nice, but don't be surprised when your system doesn't boot up anymore after a few months (happened to me twice, once on vacation without access to a laptop ) never happend with ext4. can be coincidence but I don't trust f2fs anymore

maikvitesse said:
I only had troubles with f2fs. yes the performance is nice, but don't be surprised when your system doesn't boot up anymore after a few months (happened to me twice, once on vacation without access to a laptop ) never happend with ext4. can be coincidence but I don't trust f2fs anymore
Click to expand...
Click to collapse
This exactly happened to me too while I was with F2FS on my older Galaxy S4, and also exactly while I was on vacation, F2FS can't be trusted anymore to either. But I got to admit, the performance boost is nice

F2FS on system partition

Hi,
I'm using a rom based on OOS (xXx). I'd like to test F2FS for my system partition, is this possible with OOS? Each time I flash a ROM, system is coming back to EXT4.
Thanks a lot.

F2fs on system is not supported with oos ROMs I believe. I'm not sure about los based roms

furious.builder said:
system is coming back to EXT4
Click to expand...
Click to collapse
...and it's doing the right thing :good:

Hitman478™ said:
...and it's doing the right thing :good:
Click to expand...
Click to collapse
It is indeed. Tried F2FS to many times and it's always causing issues after a few months. EXT4 is rock solid and the way to go

maikvitesse said:
It is indeed. Tried F2FS to many times and it's always causing issues after a few months. EXT4 is rock solid and the way to go
Click to expand...
Click to collapse
i can absolutely confirm this.. I came from a bad experience with f2fs as for now, ext4 is 10 way the best

Op3t has f2fs and it gave me no problems. I don't understand why they dropped it with the 5! Using f2fs on system partition is quite useless, no files are being written to that partition, ext4 is better in this case

I try use F2FS partition on my OnePlus 3T and everything smooth, no issue.
But when i use on OnePlus 5, got some little problem, such like cannot choose picture to upload on Instagram.
Honestly F2FS faster than EXT4 but F2FS still buggy, unstable i think and EXT4 stable hahaha
Wonder why on 3T, OnePlus using F2FS and on 5 using EXT4 -_-

There is still hope for f2fs. As arter97 from aospa team has a possible fix for the f2fs performance issues we might see later this year. But as for now its recommended to use ext4 on all partitions as it is more stable and doesnt get laggy after long usage.

Thanks a lot for your answers! I'm on f2fs only on data, I'll see if I have any trouble due to instability. For now I'm really happy w/ it 784.62 MB/s and 220.08 MB/s for reading and writing speed

furious.builder said:
Thanks a lot for your answers! I'm on f2fs only on data, I'll see if I have any trouble due to instability. For now I'm really happy w/ it 784.62 MB/s and 220.08 MB/s for reading and writing speed
Click to expand...
Click to collapse
Want to try the last beta with f2fs and just want to know if it still enough stable and fonctional ? And if I switch only for data or other partition ? I have see somewhere that with Oreo f2fs had a better support and I don't know if I need a special kernel or no ?