and sorry for the v6 supercharher i installed the latest version. here is the link
http://xdaforums.com/showthread.php?t=1379564
[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)
- Thread starter Entropy512
- Start date
-
- Tags
- development
http://xdaforums.com/showthread.php?t=1379564
Same for me. CM9 runs awesome so far, but I think the lack of BT audio is going to end up being the dealbreaker for me, same as it was for CM7.
Hopefully you guys, in your development wisdom, can find a way around this eventually. That will be a happy day for me.
what zip did you use i did a search and found 2 diff ones and would like to have it install with out getting boot loops or have to install everything again
thanks in advanced
http://db.tt/vAKuxSSQ us this one. I've flashed it several times and never an issue.
Sent from my SGH-I997 using XDA
unofficial cm9 for infuse 4G screenshots
unofficial cm9 for infuse 4G screenshots
unofficial cm9 for infuse 4G screenshots
Attachments
Last edited:
I need some serious help here
my infuse is currently running zues build 6, with ics theme (framework) and custom theme from UOT. ive downloaded this rom from multiple sources, two devices (phone and laptop) and 3 different networks (2 wifi networks and my 4g[ish] network) and none of them will flash...they all abort the installation because its a "bad" DL. it says:
bla bla bla.zip cannot be opened
(bad)
installation aborted.
WTH! i have a gingerbread rom and red cwm, and ive tried flashing from stock zues, with the same result. ive even tried flashing from ICS recovery (which is rainbow, i thought i had gb?!?! RED recovery ) i really dont want to flash the boot loaders due to A. can it use older roms?(i need to be 100% on this one) B. what if its not the boot loaders... C. im a noob at hiemdall. need som real support here....
my infuse is currently running zues build 6, with ics theme (framework) and custom theme from UOT. ive downloaded this rom from multiple sources, two devices (phone and laptop) and 3 different networks (2 wifi networks and my 4g[ish] network) and none of them will flash...they all abort the installation because its a "bad" DL. it says:
bla bla bla.zip cannot be opened
(bad)
installation aborted.
WTH! i have a gingerbread rom and red cwm, and ive tried flashing from stock zues, with the same result. ive even tried flashing from ICS recovery (which is rainbow, i thought i had gb?!?! RED recovery
) i really dont want to flash the boot loaders due to A. can it use older roms?(i need to be 100% on this one) B. what if its not the boot loaders... C. im a noob at hiemdall. need som real support here....
T
tmease1
Guest
my infuse is currently running zues build 6, with ics theme (framework) and custom theme from UOT. ive downloaded this rom from multiple sources, two devices (phone and laptop) and 3 different networks (2 wifi networks and my 4g[ish] network) and none of them will flash...they all abort the installation because its a "bad" DL. it says:
bla bla bla.zip cannot be opened
(bad)
installation aborted.
WTH! i have a gingerbread rom and red cwm, and ive tried flashing from stock zues, with the same result. ive even tried flashing from ICS recovery (which is rainbow, i thought i had gb?!?! RED recovery
I have never ran zeus so i don't know what all is added in that rom. What i would do is Odin back to froyo and then odin the lb3 leak to give it a clean slate. After this odin a gb kernel, pull the battery and get into cwm. Then follow the instructions in the op. Lb3 has the bootloaders you need. Someone else probably has an easier way but this is just how i would do it.
Sent from my SAMSUNG-SGH-I997 using xda premium
Last edited:
Even after changing my APN settings and moving the modified apns_config.xml file in the /system/etc folder to replace the default copy as provided by dman, I still cannot send or receive MMS messages.
Does anyone have a working solution? It's not that big of a deal, since Email is readily available, just curious.
I'm currently using these APN settings:
Name: AT&T
APN: wap.cingular
Proxy: leave blank
Port: leave blank
Username:WAP@CINGULARGPRS.COM
Password:CINGULAR1
Server: leave blank
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: 80
MCC:310
MNC:410
APN Type: leave blank
Does anyone have a working solution? It's not that big of a deal, since Email is readily available, just curious.
I'm currently using these APN settings:
Name: AT&T
APN: wap.cingular
Proxy: leave blank
Port: leave blank
Username:WAP@CINGULARGPRS.COM
Password:CINGULAR1
Server: leave blank
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: 80
MCC:310
MNC:410
APN Type: leave blank
the weird thing is that Zeus 6 is an lb3 ROM with an infusion kernel...does infusion not use GB boot loaders...and you suggest i use Odin to flash to stock... i have a backup of my original Froyo ROM. could i not just restore that and then do a manufactures reset in CWM or should i just start 100% clean? And any suggestions as to were i get the leak? thanks
Proxy: wireless.cingular.com
Port: 80
MMS Proxy: 66.209.11.32
Reboot
.Sent from my SGH-I997 using Tapatalk 2 Beta-5
T
tmease1
Guest
I would start clean. I can't copy and paste with the xda app for some reason so i can't give you the link but if you search down the threads here in the dev section you will see the lb3 leak.
Sent from my MB865 using xda premium
try changing "apn type" to " internet + mms
although im not running cm9 (YET!!!), here are my apn settings, they quite different
NAME: AT&T 310 410
APN: wap.cingular
Proxy: not set
port: not set
user name: not set
Password: not set
server: not set
MMSC: Http://mmsc.cingular.com
mms proxy:wireless.cingular.com
mms port: 80
MCC: 310
mnc: 410
Auth.type: none
APN type: internet + mms
everything woks fine, even tethering...
edit:
^^^^thanks tmease1, will try
Play Store
Thank you Entropy. I flashed your from twice then flashed the gapps.ics and I now have Play Store. I don't know but it may have been your version but I am a happy camper. Now I am going to test it all out and set it up.
Thank you Entropy. I flashed your from twice then flashed the gapps.ics and I now have Play Store. I don't know but it may have been your version but I am a happy camper. Now I am going to test it all out and set it up.
Can you flash other roms? Why are you concerned abt flashing froyo roms (not meant to be rude, just asking)? Any from that is on xda forums that is gb based will still flash, and I might be wrong, but I am pretty sure that even froyo Roms will still flash. Once you flash gb boot loaders, you CANNOT go back to froyo boot loaders. Probably the easiest thing to do is flash the community kernel. This should fix the CWM issue. It definitely has to be an issue specific to your phone. As far as the process of using heimdell, if you follow the directions to the t, you should be OK. I didn't think twice abt doing it, and I have only used heimdell once.
Sent from my SGH-I997 using XDA
Need Help
Sorry because my idiot question!I am using Entropy ICS Rom.
Before I flash this rom,i have used ICS of JT.This is my progress to go to Entropy ICS:
Go back to stock rom Froyo with GTG ulimited..>Root>Install CWM>Flash CM7(Unoffical)>Install Recovery of JT>Flash CM9 of JT>Flash Entrophy CM9
So what is my boot loaders???GB or Froyo???What is happen if i go back to froyo with GTG unlimited?
Sorry because my idiot question!I am using Entropy ICS Rom.
Before I flash this rom,i have used ICS of JT.This is my progress to go to Entropy ICS:
Go back to stock rom Froyo with GTG ulimited..>Root>Install CWM>Flash CM7(Unoffical)>Install Recovery of JT>Flash CM9 of JT>Flash Entrophy CM9
So what is my boot loaders???GB or Froyo???What is happen if i go back to froyo with GTG unlimited?
yes i can flash gtg's, S7, any other rom but this.
no concern on flashing froyo (just hate downgrading, plus i REALLY like zues)
was also reading on the GB leak. says it cant be rooted via SOC. theyre not implying ill lose my root, are they.
so just to get things stright:
odin to stock (rooted stock or not?)
odin GB leak (is this rooted or not)
odin community kernel
boot recovery
follow OP
cross my fingers and hope like hell that cm9 flashes properly.
sound right?
btw should i flash the ics recovery...i read somewhere that it cannot flash previous backups (and i can confirm this B/C i had to flash zues to get back Red CWM, then restore) i just need to be 100, ok, 90% sure this will work and i dont fuq my phone for good ( that recovery loop scared the **** outa me!)
---------- Post added at 02:08 AM ---------- Previous post was at 02:01 AM ----------
Sorry because my idiot question!I am using Entropy ICS Rom.
Before I flash this rom,i have used ICS of JT.This is my progress to go to Entropy ICS:
Go back to stock rom Froyo with GTG ulimited..>Root>Install CWM>Flash CM7(Unoffical)>Install Recovery of JT>Flash CM9 of JT>Flash Entrophy CM9
So what is my boot loaders???GB or Froyo???What is happen if i go back to froyo with GTG unlimited?
you should be using froyo bootloaders, as you havent flashed a GB BL. as to flashing froyo you should be fine as you either have GB or FROYO Bootloaders, which can both flash froyo roms...but then again you see the issues im having right now so im kinda cloudy right now. and why the HELL would you want froyo back after all that work to flash ICS.....
I just did that and now i get force close when i press download...
Sent from my SGH-I997 using xda premium
Im to blazed to understand anything you all just said. Ill say this everything you need to understand to flashing this rom is located in the OP. As Entropy said do not flash bootloaders youll hard brick. At all costs you should always odin back to stock using GTG Ultimate. Root phone. Put phone into download mode and Flash ICS recovery thru Odin in PDA slot. Do 3 button into recovery. Format everything, Mount system. Flash ICS Rom, then flash gapps and then reboot.
This rom is for experienced Users, if you dont know what your doing then just stay with the gb roms.
Sent from my SGH-I997 using xda premium
This rom is for experienced Users, if you dont know what your doing then just stay with the gb roms.
Sent from my SGH-I997 using xda premium
Last edited by a moderator:
You're not guaranteed to hard brick - but it's the only thing you can do that contains a risk of hardbricking.Im to blazed to understand anything you all just said. Ill say this everything you need to understand to flashing this rom is located in the OP. As Entropy said do not flash bootloaders youll hard brick. At all costs you should always odin back to stock using GTG Ultimate. Root phone. Put phone into download mode and Flash ICS recovery thru Odin in PDA slot. Do 3 button into recovery. Format everything, Mount system. Flash ICS Rom, then flash gapps and then reboot.
This rom is for experienced Users, if you dont know what your doing then just stay with the gb roms.
Sent from my SGH-I997 using xda premium
There might be problems with script asserts if you're on an improperly ported I9000 firmware (Hellraised should be fine as it changes build.prop), but in general, the instructions in the OP should work. Flash, reboot to recovery, format system, data, and cache, flash again, flash gapps, reboot and enjoy.
Bootloaders are only necessary if you encounter rainbows. Bootloaders will never affect your ability to flash something in CWM, with the exception of whether you can use CWM at all due to the rainbows.
I think I partially fixed the front camera - It's fully working without cropping at 640x480 now, but getting still image capture at 1280x960 to work right is a different story. That still crashes the Camera app. I may clean up the code tomorrow and then release - I need a break and the code is an ugly hackjob at the moment that needs cleaning before release.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
215DO 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.63Building - 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 infuse4g51FAQ
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.49Change 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 changes36I'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.
