[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)

Search This thread
By:
Advanced…
Q

qkster

Retired Recognized Developer
Apr 5, 2011
3,276
4,422
USA
Entropy512 said:
Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://xdaforums.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
Click to expand...
Click to collapse

I can also confirm that flashing just boot loaders with heimdall is "relatively" safe.

---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------

Adam,


Do you know if flashing boot loaders for the purpose of eliminating froyo rainbows require boot.bin, sbl.bin only - or should it have params also?

Thanks
 
J

jblparisi

Senior Member
Jun 12, 2007
572
508
Entropy512 said:
Kernel source is at: https://github.com/Entropy512/android_kernel_samsung_dempsey

Aries-common repo at: https://github.com/Entropy512/android_device_samsung_aries-common

Device repo at: https://github.com/Entropy512/android_device_samsung_infuse4g

To build, first prep your system for a Cyanogenmod build by following the instructions at:
http://wiki.cyanogenmod.com/wiki/Building_from_source

Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
Code: 
  <project path="device/samsung/infuse4g" name="Entropy512/android_device_samsung_infuse4g" remote="github"/>
  <project path="device/samsung/aries-common" name="Entropy512/android_device_samsung_aries-common" />

Run "repo sync" again

Run device/samsung/infuse4g/extract-files.sh when your device is connected and running CM9 to pull the proprietary files. (I will make this step a bit easier later in the week)

Run:
Code: 
. build/envsetup.sh && brunch infuse4g
Click to expand...
Click to collapse



Literally put my drink and dinner plate down to tip my hat to you sir. :)

Thanks for everything that you do once again, i truly appreciate it!
 
  • Like
Reactions: jonnyboy_jbmatrix and Clark Joseph Kent
deathblade

deathblade

Senior Member
Dec 19, 2011
1,552
406
Nexus 7 (2013)
OnePlus One
Awesome work, still using jt a ics ATM but really excited about your version, well test out after everything is sorted out, also, as I mentioned before, to keep users up to date setting up with goo.im is a great way to do so, though idk what's all in to seeing it up (ex. Idk if it's free hosting or not) but my dad has an Xoom and I installed a ROM from team EOS and they use goo.im manager app to keep users up to date, and it works great, just an idea

Sent from my SGH-I997 using xda premium
 
AdamOutler

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,827
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
qkster said:
I can also confirm that flashing just boot loaders with heimdall is "relatively" safe.

---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------

Adam,


Do you know if flashing boot loaders for the purpose of eliminating froyo rainbows require boot.bin, sbl.bin only - or should it have params also?

Thanks
Click to expand...
Click to collapse
the params.lfs file is responsible for rainbows. I'd recommend using the defuse one-click here http://files.teamkomin.com/files.php?dir=Infuse4G/ I think I included bootloaders... I may not have.

if that doesn't work, use one of my packages on that same page, like UCKJ4, then use the defuse kernel to get ClockWorkMod. Don't forget Params.lfs is considered bootloaders.
 
  • Like
Reactions: Clark Joseph Kent and qkster
mg2195

mg2195

Senior Member
Dec 5, 2011
2,983
2,572
29
RSM
nghia3d said:
Please add MyFile to this rom.I can not see MyFiles.
Click to expand...
Click to collapse

Just download a file manager from the market...i suggest es file explorer...its free, also has root browser, also has .zip support

I don't think MyFiles is compatible anyways...I've tried many different stock apps from gingerbread...none worked. Which makes sense since this is not gingerbread

Sent from my SAMSUNG-SGH-I997 using XDA
 
  • Like
Reactions: nghia3d
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
qkster said:
I can also confirm that flashing just boot loaders with heimdall is "relatively" safe.

---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------

Adam,


Do you know if flashing boot loaders for the purpose of eliminating froyo rainbows require boot.bin, sbl.bin only - or should it have params also?

Thanks
Click to expand...
Click to collapse
param.lfs is not needed - only boot+sbl (otherwise, I would've included param in the file I posted)
 
  • Like
Reactions: Clark Joseph Kent, kikin81 and qkster
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
jblparisi said:
For those having trouble OC' to 1.6 ghz, trying lowering the voltage on 1.6 to 1350mV on setcpu and report back.

I have set a custom profile on performance to 1.6 when awake and 100-200 mhz conservative on sleep :)

Very stable!
Click to expand...
Click to collapse
No clue what you're talking about - as stated in the OP, this build does not have OC support yet as the OC code really needs a rework.
 
  • Like
Reactions: Clark Joseph Kent and kikin81
Q

qkster

Retired Recognized Developer
Apr 5, 2011
3,276
4,422
USA
AdamOutler said:
The dude is complaining of rainbows. He has a bad params.lfs. Modification is not required to run CM9. He needs it though.
Click to expand...
Click to collapse

Thanks.

I guess I should have made my question clearer.

The issue I was try to sort out is whether bootloaders should include params. Entropy's opinion and what I remembered from your 1click package OP differs.

:) Looks like they still differs.

It seems according to Entropy, only boot.bin and sbl.bin is needed to eliminate the rainbows. But bootloaders by definition, may also include params.

I've had the GB BLs since I had flashed your heimdall 1 click uckj4 back in Sept/
Oct 2011. (Your UCKJ4 had boot.bin, sbl, sbl2 and params) I have not yet witnessed the rainbow effects myself.
I have only seen it from other user's description.

I have made a few 1 clicks from your packaging. I have flashed both the boot.bin, sbl.bin package by themselves. AND have flashed another with boot.bin, sbl.bin and params.
I could not tell there was any differences.
Neither did any harm.
I could not tell if it was better to offer just the bootloaders in a 1 click containing params or not.

It sounds like either one works.
 
  • Like
Reactions: GoSooners345 and Clark Joseph Kent
C

cakoisee

Member
Nov 12, 2009
47
7
sabak bernam
Google PLAY / market

neither Google PLAY nor Android Market is packed along with this rom. i downloaded a few apks for google PLAY and market but none of them worked. any ideo how to get Google PLAY on my infuse running this awesome build? thanks
 
drwario

drwario

Senior Member
Oct 19, 2010
487
83
cakoisee said:
neither Google PLAY nor Android Market is packed along with this rom. i downloaded a few apks for google PLAY and market but none of them worked. any ideo how to get Google PLAY on my infuse running this awesome build? thanks
Click to expand...
Click to collapse

Flash ice gapps package. Thru rom Manager is eisiest way.

Sent from my SAMSUNG-SGH-I997 using xda premium
 
  • Like
Reactions: GoSooners345
T

tmease1

Guest
cakoisee said:
neither Google PLAY nor Android Market is packed along with this rom. i downloaded a few apks for google PLAY and market but none of them worked. any ideo how to get Google PLAY on my infuse running this awesome build? thanks
Click to expand...
Click to collapse

Read the OP. You have to download gapps and flash it after you flash the initial rom.

Sent from my MB865 using xda premium
 
N

nghia3d

Senior Member
Feb 12, 2012
232
23
mg2195 said:
Just download a file manager from the market...i suggest es file explorer...its free, also has root browser, also has .zip support

I don't think MyFiles is compatible anyways...I've tried many different stock apps from gingerbread...none worked. Which makes sense since this is not gingerbread

Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse

tmease1 said:
It's not included. The play store has plenty of file managers to choose from.

Sent from my MB865 using xda premium
Click to expand...
Click to collapse

I think I like RootExplorer:eek: so I don't want to download another file manager software and delete after install root explorer.So many step:cool:
 
  • Like
Reactions: GoSooners345
You must log in or register to reply here.

Similar threads

scott.hart.bti
[ROM][JellyBean][4.3]Unofficial CM10.2 - 10/27/2013 - Butter - MTD - OC Kernel
Replies
8K
Views
2M
G
GerardSamija
P
[REF] Infuse 4G Super Everything Thread -(updated APRIL 14, 2012)
Replies
199
Views
281K
meanhacker
meanhacker
L
  • Sticky
[ HowTo ] Samsung Infuse 4g Free Unlock and Root on all O/S's
Replies
523
Views
463K
D
dchobo
uberamd
[ROM][UNOFFICIAL] Compiled CM 7 for Infuse 4G - Automated Nightly Builds
Replies
870
Views
224K
R
reactorcooler
LinuxBozo
[SOURCE] [UNOFFICIAL] CM7 for Infuse (Updated: 2011-09-29)
Replies
990
Views
201K
H
Hobbbez

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 215
    E
    Entropy512
    DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.

    Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.

    Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.

    http://d-h.st/vN1 - 06/20/2012 build
    http://d-h.st/ahW - 06/27/2012 build
    http://d-h.st/Pfr - 07/28/2012 build

    Installation instructions-from a Gingerbread firmware with "red CWM":
    Place this release and an ICS gapps release on your SD card.
    Flash this ZIP in CWM
    Reboot - you will get stuck at the Samsung screen
    Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
    Go to Mounts and Storage and format: system, data, cache
    Flash this ZIP a second time, then flash gapps
    Reboot and enjoy

    Coming from any AOSP-based firmware with "blue CWM":
    Flash this, flash gapps, wipe. That should be all you need.

    What is working:
    Calls
    GPS
    Sound
    Video playback

    What is partially working:
    Camera (minor flakiness, but mostly working)
    Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
    Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
    Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
    Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.

    Not working:
    TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.

    Known issues:
    SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
    Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
    View
    63
    E
    Entropy512
    Building - Use the Source, Luke

    Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey

    Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g

    To build, first prep your system for a Cyanogenmod build by following the instructions at:
    http://wiki.cyanogenmod.com/wiki/Building_from_source

    Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
    Code: 
      <project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
  <project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />

    Run "repo sync" again

    Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung

    Drop the contents of the attached tarball into vendor/samsung

    (I really need to clean that process up...)

    Run:
    Code: 
    . build/envsetup.sh && brunch infuse4g
    View
    51
    E
    Entropy512
    FAQ

    Q: I get weird rainbows in recovery and when my device boots? What gives?
    A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.

    Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)

    Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
    Flash the bootloaders from the file attached to this post using Heimdall as follows:
    Code: 
    heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin

    DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!

    Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://xdaforums.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
    View
    49
    E
    Entropy512
    Change Log

    7/28/2012:
    Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
    Fixed 1200 MHz step (it was using the wrong PLL settings)
    Moved to open source sensor HAL

    7/22/2012:
    Major improvements to camera flash functionality - torch is still broken but most other flash functions work
    EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
    Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
    CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.

    6/27/2012:
    Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues

    6/20/2012:
    Various upstream stuff
    Wifi Direct support added - partially glitchy (see OP)
    Bluetooth support brought up to CM7 levels (Audio stuff is still broken)

    5/27/2012:
    New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
    New LPM (charging while off) code from I9100
    All upstream changes since last build, including lockscreen weather

    5/19/2012:
    Lots of upstream CM9 changes, including theme engine and customizable lockscreen
    Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
    A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)

    5/2/2012:
    Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.

    4/23:
    Fixed wifi MAC address getting set randomly on every boot

    4/22:
    Misc stuff from CM9 upstream
    New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
    USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.

    4/19:
    No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
    FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
    Various upstream changes
    View
    36
    E
    Entropy512
    I'm going to push out a build that hopefully fixes some of the wifi driver issues tonight, it pulls a few patches in from gokhanmoral's I9100 tree. (I9100 users have had occasional issues with wifi reliability too.)

    Since I can't reproduce the issues I don't know if it will help things or not.

    I do plan on staying with this wifi driver. The benefits of working tethering and (hopefully) eliminating the BT-AMP wakeup bug (as it did when backported to the Tab 10.1) outweight the small issues it has.

    Currently on my list, time permitting:
    Try to identify why the broadcast/ARP packet filters don't enable when the screen is off. This seems to be a common issue to all devices using the I9100 wifi drivers and CM9 - It can hurt battery life for those on "dirty" networks with lots of broadcast spam. It's not a problem for most developers as we run clean networks, which might explain the unusual discrepancies in battery life between the developers and some users.
    Attempt to see if there's a way to shoehorn the I9100 camera HAL onto the Infuse, which seems to use the exact same cameras. If possible it will provide a much more robust camera experience. If not - I've lost enough sleep to the damn camera HAL, I welcome someone else trying to fix it. I hate going from an open-source HAL to a blob - but the open source HAL isn't working too well.

    I'm probably not going to be doing too much over the next few days on any device, I'm generally exhausted.
    View

New posts