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

Search This thread

tavito05

Senior Member
Dec 30, 2011
361
188
Englewood
I tried most of the JB roms and my sd card does vanish after a reboot. It only happens on JB and I keep coming back to CM9.

Whenever I had that issue I always flash without the SD card in. I take it out. I flash. Since the charger should be plugged in I remove the battery to put the SD back on , the screen won't turn off since charger is plugged in. Then I insert the battery and hit reboot. Let the rom simmer down. I never had a vanishing SD. Also try to search for a .nomedia file with root explorer and erase w.e it finds

Sent from my SGH-I997 using xda premium
 
  • Like
Reactions: selw0nk

neohemp

Member
Nov 29, 2008
13
1
Ok I apologize in advance if I'm being daft but I've worked on this for days and I just can't get it to work. Whenever I install CWM and put the recovery on, I can reboot into the right recovery UNTIL I flash this (since I have to flash it twice) when I reboot to do it the second time the original/regular recovery comes back up and I can't follow the rest
 

Christrumentalist

Senior Member
Jun 28, 2010
65
8
Barrie, Ontario
The download links on the first page are all dead or do not work. Does anyone have a mirror location where I can download the latest release? Thanks!!

EDIT: NVM, it's working now, must have been my connection here at work or something. Thanks
 
Last edited:

cammykool

Senior Member
Sep 6, 2011
1,510
378
27
Colorado
Samsung Galaxy Tab S2
Google Pixel 6
you need GB bootloader.

http://xdaforums.com/showthread.php?t=1878458

Sent from my GT-I9300 using xda app-developers app

So I need to Odin up to GB?

Sent from my SCH-I535 using Tapatalk

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------

you need GB bootloader.

http://xdaforums.com/showthread.php?t=1878458

Sent from my GT-I9300 using xda app-developers app

Right now I'm stuck at Samsung screen with rainbow recovery.

Sent from my SCH-I535 using Tapatalk
 

andros11

Senior Member
May 8, 2012
852
1,270
So I need to Odin up to GB?

Sent from my SCH-I535 using Tapatalk

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------



Right now I'm stuck at Samsung screen with rainbow recovery.

Sent from my SCH-I535 using Tapatalk

you only need the bootloader to get rid of the rainbows, but since you are already stucked, going to stock GB shouldn't hurt.

also install instructions on OP suggest you flash cm9 using the red cwm

Sent from my GT-I9300 using xda app-developers app
 
Last edited:

andros11

Senior Member
May 8, 2012
852
1,270
I was following the GB recovery steps.

Sent from my SCH-I535 using Tapatalk

yes but you flashed from froyo with the green recovery, not the red one. not sure if it would work that way.

my suggestion is you odin twice, the second time with the bootloader box checked, and then flash entropy's dd kernel to get the red recovery.

Sent from my GT-I9300 using xda app-developers app
 
  • Like
Reactions: SpleenWeen

cammykool

Senior Member
Sep 6, 2011
1,510
378
27
Colorado
Samsung Galaxy Tab S2
Google Pixel 6
I found a thread that had the GB update plus root

Sent from my SCH-I535 using Tapatalk

---------- Post added at 11:25 AM ---------- Previous post was at 10:51 AM ----------

ena4ety3.jpg


Tried to Odin to GB. it failed then this happened.

Sent from my SCH-I535 using Tapatalk

---------- Post added at 11:59 AM ---------- Previous post was at 11:25 AM ----------

I got it to boot but still have a green recovery.

Sent from my SCH-I535 using Tapatalk
 

andros11

Senior Member
May 8, 2012
852
1,270
I got it to boot but still have a green recovery.

Sent from my SCH-I535 using Tapatalk

that screen from the picture is a backup download mode fyi

for the recovery you need a custom kernel. in the 3rd post of the how to flash jb guide there are links to both heimdall one-click & odin kernels.

Sent from my SGH-I997 using xda app-developers app
 
  • Like
Reactions: Fullmetal Jun

Goraksha

Member
Mar 2, 2012
22
1
pune
Iam on AOSP-based firmware with "blue CWM",

Unable to flash Entropy's CM9 it is throwing error saying- Error in cm-9-****.zip
(Status 6)
installation aborted...
what can be done
 

Fullmetal Jun

Senior Member
Sep 10, 2013
835
290
Camp Kidney
OnePlus Pad
Iam on AOSP-based firmware with "blue CWM",

Unable to flash Entropy's CM9 it is throwing error saying- Error in cm-9-****.zip
(Status 6)
installation aborted...
what can be done

When it aborted the installation, back to menu and reboot to recovery again! Flash CM9 with CM9 Gapps again!
Did you do each step on 1st page??
U need to flash the CM9 ROM twice!!
Try this for some help if u want:
http://xdaforums.com/showthread.php?p=49141460#post49141460
 

Aareon

Member
Jul 5, 2014
15
0
I seem to get past the install of CM9, but when trying to boot to recovery, I get the dreaded torn/rainbow screen. There is a faint outline of what I can easily tell is supposed to be the Cyanogen gear with top hat. It sticks at Samsung and I can't make out what's on-screen when this happens.
 

Tank Weston

Senior Member
Jan 2, 2013
114
19
I seem to get past the install of CM9, but when trying to boot to recovery, I get the dreaded torn/rainbow screen. There is a faint outline of what I can easily tell is supposed to be the Cyanogen gear with top hat. It sticks at Samsung and I can't make out what's on-screen when this happens.

It sounds like you need to flash the GB bootloader first, then install CM9.
Try this first, http://xdaforums.com/showthread.php?t=1705260
Then flash CM9.
 
Last edited:

JGriffy

New member
Mar 24, 2018
1
0
I Know its a long shot but wondering if anyone still has the zip file. Trying to upgrade to a Jelly Bean or KitKat for my son to use as a games phone. But can't get past the Gingerbread with out this.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 215
    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.
    63
    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
    51
    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.
    49
    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
    36
    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.