[DEV][ROM] TeamGalaxyR-Cyanogenmod7-Prealpha Release 3
- Thread starter CallMeVentus
- Start date
-
- Tags
- development
Well I guess it the boot.img should not be included in the ROM since it is still the pre-built one.
we have trust in u
u can bring cm to our device.Sent from my GT-I9103 using Tapatalk 2
Well were u using stock kernel for your pre-alpha 1 release? ..... if so my recommendation is to modify the update-script and do not flash the boot image via CWM. You just need to use the same kernel you used in pre-alpha 1 to test with I guess. And you also need to boot into recovery and use adb to cat /proc/last_kmesg as well. The last_kmesg shows any kernel panic happened on previous boot.
I will flash it tonight or tomorrow after finishing my ROM. And will report what I found to you very soon.
Just now checked the Samsung OpenSource Site for Source Codes and found our Device Open Source Codes!
Just search for i9103 and you will get the List..
Hope this helps you with your CM7.!
I am just a Noob who is trying to help
Download the Zips of GB Opensource and TW Open Source
Just search for i9103 and you will get the List..
Hope this helps you with your CM7.!
I am just a Noob who is trying to help
Download the Zips of GB Opensource and TW Open Source
Just now checked the Samsung OpenSource Site for Source Codes and found our Device Open Source Codes!
Just search for i9103 and you will get the List..
Hope this helps you with your CM7.!
I am just a Noob who is trying to help
Download the Zips of GB Opensource and TW Open Source
Thanks for info! They are stock sources n we have nothing to do with them as of we are working on Open Sources !
Thanks
Eag!
can you guide me how i can upload on my mobile or this file has some pre-requiste
sorrry for english
---------- Post added at 09:14 AM ---------- Previous post was at 09:01 AM ----------
it getting on download mode again
sorrry for english
---------- Post added at 09:14 AM ---------- Previous post was at 09:01 AM ----------
it getting on download mode again
after flashing ROM its automatically going to Recovery instead of booting... i tried by replacing the Boot.IMG with AOSP Boot.IMG but no luck..
---------- Post added at 01:52 PM ---------- Previous post was at 01:50 PM ----------
There is some problem with ROM so its not booting and going back to Recovery.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
19HELLO GUYS
I compiled CM7 from newest sources and I would want to see if it works like AOSP
I've not done any tweaking as of yet because I don't know what will work for the R .
Features:
- Theme Chooser (freedom to install any CM7 theme)
- Ability to take Screenshots directly from Power Menu
- Extended power menu
- Allows rebooting normally , to recovery and even bootloader (not applicable)
Anyway , I need a kind soul to take screenshots (you will be credited)
Main developers:
Me
FranzJesus
UnknownzD
And eaglerazor
Here's the status report by bhargav143:
DOWNLOAD HERE PEOPLE (thanks to FranzJesus):
http://dl.dropbox.com/u/3020667/AOSP-GalaxyR/cm-7-20120711-UNOFFICIAL-galaxyr.zip14Latest Build
Hi!
Here comes a newly compiled CM7.2 from our sources without the erratapatch (Thanks Adam77Root).
Same functionality as the latest AOSP build but without working phonecalls.
cm-7-20120711-UNOFFICIAL-galaxyr.zip
This will be the last that I do on these sources, so let us all try to support Adam77Root and Epsylon3 to make a final and working build!!!10
Would you be kind enough to donate one or money to them ??
If not, nonconstructive comments best kept to oneself.
We are very fortunate to have a forum after much debate and even more fortunate to have kind devs doing this for next to nothing.
Please choose your words carefully in the future.
Cheers !9I will make a thread tomorrow... i was in kernel and sensors code the whole journey... but now it s time to sleep a bit
I dont have pushed the kernel stuff for the moment... i need to clean that... nothing big
but a new build is uploaded.. 14 Jul... changelog available in rom updater and my tpruvot repo on github
Sent from my GT-I9103 using xda app-developers app7I have found a bug (or better say the config that not yet enabled is wrong) in your github repo for BoardConfig.mk
https://raw.github.com/EmoBoiix3/android_device_samsung_galaxyr/master/BoardConfig.mk
# BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
# BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00780000
# BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
# BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000
The correct value should be
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p9
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
I know that someone has said the mmcblk0p* size is in 2048 bytes / unit before, however it is wrong as most of the partitions on mmcblk0 are using 512 bytes / unit only. btw I am trying to dump the pit file out of the device ... wish me luck for that
In addition, this is the recovery.fstab that someone provided to me (and I have confirmed that it should be right)
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/data ext4 /dev/block/mmcblk0p6
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/prebuilt ext4 /dev/block/mmcblk0p11
/sd-ext vfat /dev/block/mmcblk1p1
