02
Mar
image
Last Updated: March 4th, 2012

Last week, the CyanogenMod team launched the first CM9 nightly builds for the Galaxy Nexus, Nexus S, and Motorola XOOM. As of today, the following devices also have CM9 nightly builds available:

  • Samsung Galaxy Tab 10.1 Wi-Fi and I/O Edition (download: p4wifi) - yay for the latter, as it seems Samsung completely abandoned it - I believe mine is still running 3.1 with no updates in sight.
  • Samsung Galaxy Tab 10.1 SGH-T859 on T-Mobile (download: p4tmo)
  • Samsung Galaxy S II (download: galaxys2) - I wouldn't try this on carrier-specific U.S. variants if I were you, wait for those to surface separately.
  • ASUS Transformer TF101 (download: tf101)
  • ASUS Transformer Prime TF201 (download: tf201)

Update: It looks like the Tab 10.1 builds aren't nightlies just yet but rather available as snapshots, which presumably means one-time builds on the dates listed.

Definition: A "nightly" is a bleeding edge release that is built on a daily basis, usually at night after a full day's worth of new code has been committed.

It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.

If you have one of the above devices, welcome to the nightly club, folks - download, flash away, and report back with any problems.

Hopefully, the rate at which nightly support is added to other devices improves sharply once all the servers from the recent donation drive are in place and fully chugging along. You bet we'll be here to tell you.

image

image

image

image

image

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • Deltaechoe

    Lol I saw what you did there Artem...

    But seriously, this makes it tempting to unlock the bootloader on my prime.

    • http://www.AndroidPolice.com Artem Russakovskii

      What did I do this time (it wasn't me)?

      • Deltaechoe

        starts with double and rhymes with toast

        • http://www.AndroidPolice.com Artem Russakovskii

          :(

          On that note, I just put in some measures to make sure it doesn't happen in the future. Hopefully they work :)

        • Deltaechoe

          lol I'm just teasing you, the only reason I saw it is because I obsessively hit refresh on this blog. Android news is just that important to me

  • Cribology

    Can the 10.1 be used on the 8.9

  • Micah Madru

    Darn, no t-mobile gs2!

  • slurms mckenzie

    Come on tmo gs2 where are u. There's an alpha build but nothing works -_-

  • http://cafe-ti.blog.br Alroger Jr

    No, Sam, not P1010.

  • khartahk

    What about 10.1 3G?

    • ciakoc

      exactly... lots of people would like it

  • Rob

    This certainly makes my fleeting thoughts of picking up a GALAXY Tab 10.1 more concrete. This is definitely great news now that I've seen prices start to drop a bit here and there for this tablet model. Maybe I'll hold off for a few weeks and see if the recent news of the GTab2 pushes prices even lower; this will give the CyanogenMod team time to move us closer to a stable release of CM9. :)

    • http://codytoombs.wordpress.com Cody Toombs

      Wait until any of the assorted variations of the 10.1 release and you'll see the original drop in price pretty quickly, I'd ballpark about $300. I suspect it'll fall about another $100 for every major round of tablets that comes out (looks to be about every 9 months).

      • nullnvoid4prez

        What do you mean? The 10.1 is already below $350 at Costco. That pretty darned cheap for a great device like that.

        • http://codytoombs.wordpress.com Cody Toombs

          Really? That must have just happened, cause I walked through about 2 weeks ago and it was $389. I agree it was a great device (I have one), but it's time for some better hardware to surpass it...and in fairness, the pixel density still annoys me, it's just a bit too fuzzy for something you hold that close to your eyes.

  • http://codytoombs.wordpress.com Cody Toombs

    Really great timing on this post, I was looking for this less than 36 hours ago. I'm dying to try ICS, but the phone needs to stay Gingerbread for a while longer, but the tablet is in need of the powerup.

    I know some people like how Samsung did TouchWiz on the tablet, and I like the idea of it, but I don't like the apps themselves and I still accidentally activate the menu just often enough that it bothers me. I'd rather wipe out TouchWiz and reclaim some framerate.

  • ToastMan

    I thought SGH-T989 is the T-Mobile Galaxy S2. The T-Mo Galaxy Tab has the same code name?

    • http://www.AndroidPolice.com Artem Russakovskii

      Whoops, you're right. The right version is there now.

  • Graham

    Anyone know if the camera's working on the Galaxy Tab 10.1?

    • http://tecthirst.com Anuj Ahooja

      Not yet, but they're working on it.

  • Omkar

    Please help me out with how to install this perticular nightly build for my Galaxy S2.. Are the following steps correct??
    1) wipe data and factory reset
    2) wipe cache partition
    3) wipe dalvik cache
    4) wipe battery stats
    5) install the zip file
    Or is it necessary to install the very first nightly build (nightly 1) first and then install this latest one?? Please reply.. I am confused..
    And what about gapps??

    • Hal Motley

      CyanogenMod wiki has it all documented: http://wiki.cyanogenmod.com/index.php?title=Special%3ASearch&search=Samsung+galaxy+S+II&go=Go

      What you have to do is install both zip files at stage 5 (CM9 ROM and GApps) aside from that you are good to go.

      PS: I never wiped battery stats!

      • http://codytoombs.wordpress.com Cody Toombs

        A google engineer came out a couple of months ago and made a clear public statement that the battery stats are supposed to be wiped at each startup and they don't even last very long anyway...in other words (at least by his statement), the whole thing is just a placebo effect.

    • http://codytoombs.wordpress.com Cody Toombs

      If you're asking what I think you're asking then Hal's answer might not be completely clear (I'm just covering the bases in case you're a bit new to this stuff).

      They call these updates but they aren't done as 'delta' updates. You don't need to install a base version and then each subsequent update. Simply flash the zip from Recovery, and as soon as it's finished, flash on the GApps zip (do NOT restart the tablet before flashing on GApps or you'll supposedly have problems with market and gmail). Once GApps is flashed on, restart and let the tablet sit for approx 4-5 minutes while the boot animation rolls (I forgot to time it, but it does take just long enough that it feels you might be stuck in a boot loop). Unless the tablet is in the boot animation over 10 minutes, then restart the tab by holding Power+VolDown and try flashing again.

      One thing that's happening to a lot of people, they start to flash the rom and it errors out with 'Status 7', which is a failed assert in the update script. You can try to advice some people have, which is to delete the first line in the update script, rezip the rom and flash again, but I strongly recommend flashing a newer recovery to the tab (I used v5.5.0.4). Also, I'm not sure how accurate this is, but I saw a lot of comments suggest that you have to flash recoveries to the tab from ODIN; Heimdall will not work because of some minor difference in the protocol (I'm on a Mac and just started up VMWare). I think that's all of the tips I've got from just doing it myself.

      As an aside, LOVE ICS!!! ;)
      Damn I need a phone with ICS badly

  • Rob

    Be cautious the tf101 builds aren't usable. First one force closes and second one wifi is broken. Use at your own risk.

    • jordanjay29

      There are a couple ICS ASUS-based ROMs on XDA for the TF101 while CyanogenMod sorts out their nightlies and alphas and betas (oh my!).

  • Hal Motley

    I'll stick with my Codeworkx CM9 ROM and wait until the official CM9 nightly goes stable.

  • Nathan

    I assume this does not include the 10.1 4G LTE edition in this release....or will this one work?

  • sans

    Tried on AT&T GS2, couldn't flash with cwm 5.0.2.6. Running AOPK ICS 4.0.3 successfully.

  • http://www.spencerpablophotography.com Spencer

    I hope Samsung doesn't abandon the Tab 10.1. The just-announced ones seem to be very similar to it AND have ICS. CM9 is nice and all, but I really like how the Samsung printer driver is OS-wide on the stock ROM as I have a Samsung wifi-network printer/scanner and it works with it without additional software.

  • Deede

    can u please confirm ur post is correct or not, TQ---» Samsung Galaxy Tab 10.1 SGH-T859 on T-Mobile (download: p4tmo)

  • Stuart

    Did a backup then flashed my TF101. It stuck in a bootloop on bootanimation( gave it at least 20 minutes before I gave up on the boot). Tried to restore my backup. All looked well during that. Then on reboot, stuck on initial ASUS Splash img. Had to jump through numerous hoops to get it back to stock then re-root.

    I'll keep watch on the progress before I try it again.

    • Paulina

      how did you do exactly to get the phone back to normal?
      Because i have a samsung galaxy 1 that did the exact thing when i tried to flash it with cyanogenmod, this was lika a year ago and i gave up on the phone when i couldn't get pass the boot animation but i still have it and i would be so happy if i could resyore it to normal!

      • Resilienttroll

        tf101 is a tablet not a phone.

  • http://pinoydroid.net pinoy android

    Will test this tomorrow with my Galaxy S2

  • AEF

    Tried to flash on my Galaxy Tab 10.1 wifi and got an error - first time trying to do this so it could be I did something wrong but i followed everything step by step

    • http://codytoombs.wordpress.com Cody Toombs

      If you want help, you've got to be more specific than that

      • AEF

        ok - thanks

        I rooted and followed the directions from http://www.androidpolice.com/2010/05/08/complete-guide-how-to-flash-a-custom-rom-to-your-android-phone-with-rom-manager-full-backup-restore/

        I tried to load the ROM with ClockworkMod but got the following:

        (If there is other info I can give you let me know)

        Starting recovery on Sun Mar 4 15:05:25 2012
        framebuffer: fd 4 (1280 x 800)
        ClockworkMod Recovery v4.0.0.4
        recovery filesystem table
        =========================
        0 /tmp ramdisk (null) (null)
        1 /efs ext4 /dev/block/mmcblk0p1 (null)
        2 /recovery emmc /dev/block/mmcblk0p2 (null)
        3 /boot emmc /dev/block/mmcblk0p3 (null)
        4 /system ext4 /dev/block/mmcblk0p4 (null)
        5 /cache ext4 /dev/block/mmcblk0p5 (null)
        6 /data auto /dev/block/mmcblk0p8 (null)

        W:Unable to get recovery.fstab info for /sdcard during fstab generation!
        W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
        I:Completed outputting fstab.
        I:Processing arguments.
        I:Checking arguments.
        I:device_recovery_start()
        Command: "/sbin/recovery"

        ro.secure=0
        ro.allow.mock.location=1
        ro.debuggable=1
        persist.service.adb.enable=1
        ro.build.id=GINGERBREAD
        ro.build.display.id=full_p7100-eng 2.3.4 GINGERBREAD eng.koush.20110614.231606 test-keys
        ro.build.version.incremental=eng.koush.20110614.231606
        ro.build.version.sdk=10
        ro.build.version.codename=REL
        ro.build.version.release=2.3.4
        ro.build.date=Tue Jun 14 23:16:26 PDT 2011
        ro.build.date.utc=0
        ro.build.type=eng
        ro.build.user=koush
        ro.build.host=Koushik-OSx86.local
        ro.build.tags=test-keys
        ro.product.model=Full Android on Emulator
        ro.product.brand=Android
        ro.product.name=full_p7100
        ro.product.device=p7100
        ro.product.board=p7100
        ro.product.cpu.abi=armeabi
        ro.product.manufacturer=unknown
        ro.product.locale.language=en
        ro.product.locale.region=US
        ro.wifi.channels=
        ro.board.platform=unknown
        ro.build.product=p7100
        ro.build.description=full_p7100-eng 2.3.4 GINGERBREAD eng.koush.20110614.231606 test-keys
        ro.build.fingerprint=Android/full_p7100/p7100:2.3.4/GINGERBREAD/eng.koush.20110614.231606:eng/test-keys
        ro.cwm.prefer_tar=true
        keyguard.no_require_sim=true
        ro.ril.hsxpa=1
        ro.ril.gprsclass=10
        ro.config.notification_sound=OnTheHunt.ogg
        ro.config.alarm_alert=Alarm_Classic.ogg
        ro.kernel.android.checkjni=1
        ro.setupwizard.mode=OPTIONAL
        net.bt.name=Android
        net.change=net.bt.name
        dalvik.vm.stack-trace-file=/data/anr/traces.txt
        ro.factorytest=0
        ro.serialno=C16906153985B5E
        ro.bootmode=unknown
        ro.baseband=%s
        ro.carrier=unknown
        ro.bootloader=P7500XXKJ1
        ro.hardware=p3
        ro.revision=11
        init.svc.recovery=running
        init.svc.adbd=running

        I:Checking for extendedcommand...
        I:Running extendedcommand...
        Waiting for SD Card to mount (20s)
        W:using /data/media, no /sdcard found.
        SD Card mounted...
        I:Running script:
        I:
        ui_print("ROM Manager Version 5.0.0.6");
        ui_print("March 4, 2012");
        ui_print("Preparing to install ROM...");
        assert(backup_rom("/sdcard/clockworkmod/backup/2012-03-04-10.05.10"));
        run_program("/cache/dowipedalvikcache.sh");
        assert(install_zip("/sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip"));

        parse returned 0; 0 errors encountered
        ROM Manager Version 5.0.0.6
        March 4, 2012
        Preparing to install ROM...
        W:using /data/media, no /sdcard found.
        SD Card space free: 11150MB
        Backing up boot image...
        Backing up recovery image...
        Backing up system...
        Backing up data...
        tar: data/misc/wifi/sockets/wpa_ctrl_300-1: socket ignored
        tar: data/misc/wifi/sockets/wpa_ctrl_300-2: socket ignored
        tar: data/misc/dhcp/dhcpcd.sock: socket ignored
        tar: data/.pcsync_stream: socket ignored
        tar: data/.usb_stream: socket ignored
        No /sdcard/.android_secure found. Skipping backup of applications on external storage.
        Backing up cache...
        No sd-ext found. Skipping backup of sd-ext.
        Generating md5 sum...

        Backup complete!
        about to run program [/cache/dowipedalvikcache.sh] with 1 args
        mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy
        mount: mounting /dev/block/mmcblk0p5 on /cache failed: Device or resource busy
        mount: can't find /sd-ext in /etc/fstab
        umount: can't umount /sd-ext: Invalid argument
        run_program: child exited with status 1

        -- Installing: /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
        Finding update package...
        I:Update location: /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
        W:using /data/media, no /sdcard found.
        Opening update package...
        Installing update...
        script aborted: assert failed: getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi"
        assert failed: getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi"
        E:Error in /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
        (Status 7)
        Installation aborted.
        result was NULL, message is: assert failed: install_zip("/sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip")
        W:using /data/media, no /sdcard found.

  • AEF

    ok - thanks

    I rooted and followed the directions from http://www.androidpolice.com/2010/05/08/complete-guide-how-to-flash-a-custom-rom-to-your-android-phone-with-rom-manager-full-backup-restore/

    I tried to load the ROM with ClockworkMod but got the following:

    (If there is other info I can give you let me know)

    -- Installing: /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
    Finding update package...
    I:Update location: /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
    W:using /data/media, no /sdcard found.
    Opening update package...
    Installing update...
    script aborted: assert failed: getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi"
    assert failed: getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi"
    E:Error in /sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip
    (Status 7)
    Installation aborted.
    result was NULL, message is: assert failed: install_zip("/sdcard/update-cm-9-20120302-SNAPSHOT-p4wifi-signed.zip")
    W:using /data/media, no /sdcard found.

    • http://codytoombs.wordpress.com Cody Toombs

      Grr, the comment system won't let me post this full thing, I thinks I'm spamming, so I'll try posting in multiple parts...

      Download this Recovery image: http://dl.dropbox.com/u/18512051/andrewrecov.tar.md5

      Flash the recovery with ODIN on Windows (do not use Heimdall, supposedly it doesn't work, and I wouldn't recommend using WINE wrapped versions of ODIN either). That should fix the error you're getting.

      • AEF

        I'm a drop confused at how to do this (Sorry for sounding like a noob, but when it comes to this i am)

        I tried to flash the recovery you linked with ODIN and got the following

        Enter CS for MD5..
        Check MD5.. Do not unplug the cable..
        Please wait..
        andrewrecov.tar.md5 is valid.
        andrewrecov.tar.md5 is valid.
        andrewrecov.tar.md5 is valid.
        Checking MD5 finished Sucessfully..
        Leave CS..
        Odin v.3 engine (ID:4)..
        File analysis..
        SetupConnection..
        All threads completed. (succeed 0 / failed 1)

        • http://codytoombs.wordpress.com Cody Toombs

          Ahh, I see the problem. I assumed you you were installing to the Galaxy Tab 10.1 wifi (p7510) but you're installing to the 10.1v (p7100) which is the t-mobile version.

          I don't have the model to test with, but I believe you need a different recovery image than the one I linked to (sorry)? Try flashing the recovery that ROM Manager provides, if that doesn't work, let me know and I'll try to find a good image that can be flashed from ODIN (unless somebody else has a link or knowledge of which recovery is needed here).

          According to the error log, you're also trying to flash on the wifi version, which is definitely wrong (the wifi version only works on p7510 and ?maybe? p7500). You should be installing p4tmo instead of p4wifi.

          Any chance somebody knows why that error log has so many mentions of Gingerbread and even mentions API 10 (Gingerbread's API Level)??? Except for the OG 7" Tab, there's never been a Gingerbread tablet from Samsung, and that certainly doesn't make sense on a Honeycomb-based tablet.

      • AEF

        Cody - you are the best - I was actually fooling around and tried that and it worked. I went to go tell you it worked and I got an email saying that you commented.

        I didn't get the gapps thing to work yet (i know - i rebooted anyways) - but I'm playing around with it.

        • AEF

          I don't even know where I'm replying to anymore.

          I GOT IT WORKING (with gapps and all)

          I messed up and the file I was trying to load had stopped during the download process. Now everything is awesome.

          Now I need to go on the treadmill that I was supposed to go on an hour ago

        • http://codytoombs.wordpress.com Cody Toombs

          Sweet, glad we finally beat it!

          I feel a bit of sympathy for anybody who remained subscribed to this post, but hopefully a lurker somewhere will get a tip out of the mess of posts that are completely out of order :D

    • http://codytoombs.wordpress.com Cody Toombs

      The article you're following is pretty old but a quick skim didn't turn up anything particularly incorrect. You might look to the link Hal Motley posted above for CM installs instead: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide. Follow this process, but use ODIN to flash the recovery I linked to and make sure you flash GApps immediately after flashing the ROM (before restarting the tablet) as mentioned in step 9 (you'll have problems if you restart before flashing GApps).

      • AEF

        Hi Cody,

        It's not letting me reply to you last comment so I'm replying here.

        I do not have the t-mobile version - I bought the wifi version. I got it off of Amazon.

        • http://codytoombs.wordpress.com Cody Toombs

          Unless you already flashed a Frankenstein ROM with a mixed up build.prop I just can't see why it's reporting the wrong hardware. I don't mean this to sound insulting in any way, but are you totally sure it's the wifi model, possibly you were sent a mis-marked/packaged model or something? Different hardware is the only good reason I could see for the recovery image not flashing on from ODIN.

          I've tried looking in quite a few places without seeing any examples of the issue you're having. At this point, you might want to hit up the troubleshooting threads at XDA. Here's a couple of links you might check out first:
          Galaxy Tab CM Announcement:
          https://plus.google.com/115013390614274076135/posts/ArJsxBq3GuF

          Steve Kondik's post:
          https://plus.google.com/100275307499530023476/posts/1Lm5iULvf3w

          Baring success with these you might consider trying a KANG since there haven't been as many install issues with it.
          http://forum.xda-developers.com/showthread.php?t=1425631

          I'd like to help more but I'm at a loss for what would be causing the issues you're having.

        • AEF

          Just did a double check - my tablet model number is GT-P7510

      • AEF

        Not insulting at all but I am positive its the wifi version.

        I rooted following the video from http://www.thedroiddemos.com/2011/08/28/how-to-root-the-samsung-galaxy-tab-10-1-video-walkthrough/

        and then followed directions from http://www.androidpolice.com/2010/05/08/complete-guide-how-to-flash-a-custom-rom-to-your-android-phone-with-rom-manager-full-backup-restore/

        I'll play around with it a bit later - got to go to work.

        • http://codytoombs.wordpress.com Cody Toombs

          The best thing I can think to suggest is try downloading the recovery image again from http://dl.dropbox.com/u/18512051/andrewrecov.tar.md5 and retry the flash with ODIN 3 v1.85. Make sure you're setting PDA to the recovery image. I just redid this step and confirmed it worked and flashed correctly, and the recovery version shows as v5.5.0.4. If that doesn't work, the only other thing I can think of is you've got a locked bootloader that's preventing ODIN from flashing an alternate recovery; I didn't think that was a problem on these, but maybe the latest official firmware might have added it as a security measure.

      • AEF

        Ok - nothing seems to work. Is there a way to start from scratch - I have anything on there that I need.

        • http://codytoombs.wordpress.com Cody Toombs

          I am starting to feel like there's got to be some silly thing we're overlooking.
          Do you have full admin rights on your computer?
          Did you install drivers so your Tab is recognized in windows?
          Are you using ODIN 3 v1.85?
          A 'No' to any of those questions might explain the problem.

          Curious, what version of CWM do you already have on there from when you rooted (it'll say in the recovery screen)?
          Is the computer you're using now the same one you used to root the tab before?

          Other than the hardware revision on yours being slight different than mine (I've got 14, you've got 11), there's no difference. If one of the questions above doesn't give us a hint, go to the XDA forums and hit the Q&A section. I've only worked with my tablet, I haven't really had to help other people out with theirs, so maybe somebody has stumbled onto this issue and can shed some light on the problem.

          I'm mostly concerned that you can't flash a different recovery. That's the thing that should be easiest and most reliable, and it's definitely the thing that we've got to get working (while we could get CM9 onto your tablet with a minor fix, I'd be more comfortable if you had a recovery image that was up to date and not suffering the assert bug).

      • AEF

        OMG - I feel like an idiot. I did warn you I was a NOOB when it comes to this (although I do IT as a living, I never played around with ROMS and Rooting before).

        When I tried to flash the recovery you gave me using ODIN, I forgot to put my tablet in ODIN mode (or whatever it's called - holding the power button and vol down). That's why I couldn't do anything. Once I realized my mistake, your recovery loaded with ease. I then loaded the ROM linked in this article with ClockworkMod. It didn't give me the error I had before and now it's in what I think is the ICS boot animation. It's taking a while but I think I read somewhere that that is normal for the first time.

        • http://codytoombs.wordpress.com Cody Toombs

          HAHAHA!!! That's Hilarious!!! I swear I thought of everything but it didn't occur to me to double-check you went into download mode. The thing that makes that so embarrassing for me is that I just talked a friend of mine through most of the same steps for rooting her Epic 4G and that's the step I spent forever explaining to her :)

          You can't feel bad, I've been living and breathing computers and gadgets all my life, my first real memory is of using a TI computer (pre-x86 days, maybe pre-8088), and I'm still super cautious every time I flash any of my stuff cause I always feel like I'm still noob enough to screw up something obvious (mostly because I think of the price tag attached to making a mistake).

          Anyway, I can see by the clock that the bootscreen has to have finished a while ago and you're enjoying some ICS. I'm glad you got it worked out. While you'll surely be flashing a lot of CM9 versions to come, you shouldn't need to put on another CWM in the foreseeable future.

          One hint, before you set up your launcher too much, just go download Nova Launcher right now, it's a bit better than Trebuchet (at least for the moment) and you can backup/restore between flashes (important for the frequent flashes on the upcoming CM nightlies).

      • AEF

        Thanks for all your help, but I'm not in the clear yet.

        My boot screen never ended.

        I tried to shut it off and reboot it but I still get stuck in the boot screen.

        I tried to flash the recovery you sent me (correctly using odin this time) and it seemed successful, but I still get stuck in the ICS boot screen. Does that make sense?

        • http://codytoombs.wordpress.com Cody Toombs

          Go into recovery, wipe the 'cache', 'dalvik cache' and 'user data' (that's 3 separate things). Reflash the CM9 ROM. 9 out of 10 times that I've seen/read about, boot loops happen because of a bad ROM flash or something in the cache/user data is incompatible with some bit of new code. If you're still not getting anywhere, redownload the ROM (you might want to double-check the checksum to be sure the download wasn't corrupted). If you're still getting boot loops, let me know. It's a common problem on the Galaxy Tab, really easy thing to cause, but the list of causes tends to always trace back to a bad rom flash.

    • http://codytoombs.wordpress.com Cody Toombs

      I've posted the second part but it's waiting for moderation. Don't try flashing until the second part shows up ;)

  • AEF

    Can you email it to me at aefjunk at g male?

    thanks

    • AEF

      nevermind looks like it came through

  • Jamesy

    It seems like devices that nightlies are available for stay in night lies? Why is it that we always hear about night lies but there are very few actual releases?

  • Evan

    Dear, can i use it on my device ?

    GT-i9100G,The CPU IS OMAP 4430 from TI?

  • http://www.dipockdas.com Dipock

    :-( getting a 404 on p4wifi download. I want to upgrade my Google I/O Galaxy Tab ...

  • Dan Huddart

    I have a tmobile 4g  sgh-t859, I have rooted.  I can use aokp_p4_milestone 4 and load that rom thru rom manager. 

     However I cant seem to load p4tmo roms listed here. I get 
    assert failed: getprop("ro.product.device") == "p4tmo" || getprop("ro.build.product") == "p4tmo"E:Error in /sdcard/update-cm-9-20120512-SNAPSHOT-p4tmo-signed.zip(Status 7)Installation aborted.Suggestions?

  • Luke Raynor

    Is the camera and USB stll not working on the 10.1? I have this zip sitting on my sd and am dying to install ICS on my tablet, however, I cannot deal with the USB Connect not working. I am not going to email 60 mp3 at a time to myself or use blue tooth. The camera, OK. I dont care. Any updates??? Please?

  • Dan Huddart

    LUKE, usb not working, use kies air only for me.

  • Tomersaadi

    Hi why after installing rom me up and flashes the screen until it reaches Wallpaper ..? Samsung wifi tab 10.1

Quantcast