Introduction:
This is a pure AOSP built ROM. Nothing has been added to it but for root, busybox, zipalign and kernel that is not secure for ADB . This is for the user who wants a pure vanilla Android experience. I will be back with my AOSP+ Neapolitan ROMs soon which add a few more options.
GApps are NOT included. You can download GApps below.
Info:
AOSP build
JZO54K - 4.1.2
Web Presence:
Twitter
Google+
Would be best to follow me on Google+ for latest updates and news. Sometimes I post stuff there more than I do here...
Change Log:
10/12/12
Updated to latest binaries.
Created add-on GApps package. GApps created from latest JB public images. Missing apps can be downloaded from Google Play.
Fixed Google Now crash.
Dev Tools and SpareParts now part of build.
Enabled Sound Recorder from Launcher.
10/10/12 - First release
Install Instructions:
Install Clockwork recovery if you have not done so
Download ROM
*Wipe cache
*Wipe Data/Factory Reset
Above steps are opitional but at the very least wipe dalvik cache
Install ROM
Reboot
Enjoy!
Downloads:
ROM
HERE
Filename - grouper_412_AU_101212.zip
MD5 - 0d2415836255a60452e32e805203849a
GApps
HERE
Filename - gapps-jb4.1.1-10112012.zip
MD5 - 1dc7ef9363615329545a744484c31112
Credits:
Google, AOSP, Sixstring, Codenamedroid, Braway, Romanbb, CM, peteralfonso, xplodwild and all others that I have gained knowledge and source from.
Einstein quote but modified a bit for this
I am often worried at the thought that my Android development is based to such a large extent on the work of my fellow developers and I am aware of my great indebtedness to them.
Reserved......
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Elting said:
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Click to expand...
Click to collapse
No...bootloader not included.
You're welcome!
Elting said:
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Click to expand...
Click to collapse
Only for a Google device will you see people actually asking for the new bootloader.
Thanks for your work OP.
Thanks a lot, giving this a go right now.
Loaded this without any problems. I've got 4.1.2 and build jz054k. I did have one issue of my own doing. The first time I loaded it I did not wipe data and on reboot I was stuck on the "android" screen. After about 10 minutes I did a complete wipe and then loaded it again and it booted right up.
Not sure if this was an improvement in the build but gps locked on immediately as soon as I loaded up google maps. I don't remember it being that fast before. I mean, it was fast before but it might have taken 5 seconds or so to get a lock. And landscape mode is pretty cool.
Thanks for this.
Hmm Pure Vanilla AOSP has Chrome instead of AOSP Browser now?
mmmmmmm，give you a hug.
Thanks, I needed that.
Downloading for an hour now.....is it really that slow or is it on my end?
Sent from my Nexus 7 using XDA Premium HD app
Anyone having issues with Google Now force closing?
Sent from my Nexus 7 using xda premium
Edit * uninstalled then reinstalled. Works fine.
chappy824 said:
Downloading for an hour now.....is it really that slow or is it on my end?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It took 5 minutes on my home pc.
I have a CM based ROM on my Nexus 7, JB 4.1.1 .. if i wanna flash this one over, shall i simply follow your same steps ? or do i have to do anything special since i'm running a CM based ROM ?
Thanks
Google Now crashing for me too.
Edit: fixed by removing velvet.apk from /system/app/ and then reinstalling Google Search from the Play Store.
Sent from my Nexus 7 using xda premium
Maybe i am confused, but why did you put this rom in the original section?
So, I ran into a problem. And now I can't get my Nexus 7 to load past the black and whit Google screen when you first power it on.
I was running the stock out of the box 4.1.1 JB that was rooted. I updated my ROM Manager and did a backup, then rebooted, and wiped the Davlik Cache and flashed. After about 30 seconds into the flash ROM Manager received and error and wanted to know if i wanted to reboot. So I did and now i'm stuck. Any suggestions or how i can get it into the correct recovery?
I can get to fast boot, (power and down volume) but when I choose Boot recovery or any option other than power off I just get back to the White Google on black background.
Fixing the Google Now crashing problem too and will have updated ROM with the latest binaries up in a couple of hours.
Updated ROM has been posted.
GApps are no longer included and can be downloaded from first post.
Droid8492 said:
So, I ran into a problem. And now I can't get my Nexus 7 to load past the black and whit Google screen when you first power it on.
I was running the stock out of the box 4.1.1 JB that was rooted. I updated my ROM Manager and did a backup, then rebooted, and wiped the Davlik Cache and flashed. After about 30 seconds into the flash ROM Manager received and error and wanted to know if i wanted to reboot. So I did and now i'm stuck. Any suggestions or how i can get it into the correct recovery?
I can get to fast boot, (power and down volume) but when I choose Boot recovery or any option other than power off I just get back to the White Google on black background.
Click to expand...
Click to collapse
Flash the Google images and start over or find the recovery file and use fastboot to load it up.
Related
Thread moved here: http://rootzwiki.com/showthread.php...genMod-7-for-Samsung-Fascinate-(fascinatemtd) - I'm not checking on this one any more.
This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Fascinate.
All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.
CyanogenMod is a free, community built distribution of Android 2.3.5 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).
Warning : Not for new users, flash this build only if you know what you are doing!!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
INSTRUCTIONS:
Latest version: http://download.cyanogenmod.com/?device=fascinatemtd (for when nightlies are working normally)
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Fascinate (or coming from another ROM)?
Start with a rooted device (do not ask us how to do this).
Flash ClockworkMod Recovery attached to this post.
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Wipe Data! Seriously! Do it!
Install the ROM zip from sdcard
Install gapps package linked below.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Fascinate (MTD). Then pick ClockwordMod 3.x.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
NOTE: Nightlies are NOT currently available from Rom Manager, but should be soon. Every time someone asks "when?" it makes the demons break the build-bot adding several more chunks of time you will have to wait. Nothing pisses off the demon's like stupid f*cking ETA questions.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for Fascinate (MTD), choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You must flash a full Odin package with PIT, and make sure to check "repartition". This will convert your filesystems back to BML/RFS. You will now need to re-root your device, install recovery, etc to flash other ROMs. Do not ask here how to do this.
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
teamhacksung:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
jt1134 - http://twitter.com/_jt1134_
Changelog:
Generic Changelog CMSRC Twitter
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
At this time (07/28) there are a few changes of mine that have not yet been merged into the main CyanogenMod codebase. This mainly includes fixes for MMS. As such MMS will not currently work on the nightly builds until the change is approved and merged. Also, the 2.3.5 merge inadvertently removed the fix for signal strength display, so signal bars will also show 0 for now. These issues should be resolved soon enough.
Also, any bugs pertaining to my original builds (low in-call volume, etc) are not going to magically be fixed just because nightly builds are being done. ALL NIGHTLY BUILDS MEANS IS YOU GET A NEW BUILD EVERY NIGHT. No hardware specific issues are magically fixed by this. Also, I am not planning on messing with any volume related issues until we have GB kernel source code. DON'T ASK. I CANNOT POSSIBLY EXPRESS HOW ANNOYING IT IS TO SEE IT ASKED EVERY OTHER POST.
Also, only kernels built from the official source tree will be included in these builds. Only minor differences because of this, such as BLN and dock audio will not function. I plan on making some custom kernels with these features and other changes soon.
****************************
If you would like to dig into the code, you may find information on the CM wiki here: http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Compile_CyanogenMod_(Linux)
Kernel source is available here: https://github.com/teamhacksung/android_kernel_samsung_aries
If you do your own builds, PLEASE do not post them in this thread, and do not discuss them here. These threads get cluttered enough as is, please don't add extra confusion for me to dig through. No one is discouraged from building or sharing their builds, please do so in another thread/forum/whatever. Thanks.
Thanks for this JT. Fantastic tutorial that you put together. Glad to hear ROM manager will be up and running to.
Thanks again.
Neat quirk. The newest CM7 Nightly (#3) is listed as Android version 2.3.5
Not sure how accurate it is, but that's what's listed.
You mean download by holding volume down and plugging into computer?
Sent from my SCH-I500 using XDA App
Will I still need to download and flash gapps separately? If so, where can I obtain those, and will it need to be a specifically Fascinate package?
seraphls said:
Will I still need to download and flash gapps separately? If so, where can I obtain those, and will it need to be a specifically Fascinate package?
Click to expand...
Click to collapse
gapps can be found and flashed from ROM manager once you have that configured.
Grimis said:
You mean download by holding volume down and plugging into computer?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Where are you referring to Grimis?
I'm on #3 as we speak, I was about to go back to stock since cm7 was a buggy nightmare, but I'm test driving the nightlies to see what gets fixed.
djk21108 said:
gapps can be found and flashed from ROM manager once you have that configured.
Click to expand...
Click to collapse
Thanks. The last time I flashed CM (about a year ago), gapps was included, so it wasn't an issue. Just wanted to make sure I'm fully prepared - surprises are the last thing I need here.
subbed 10chars
djk21108 said:
gapps can be found and flashed from ROM manager once you have that configured.
Where are you referring to Grimis?
Click to expand...
Click to collapse
He said make sure you can get into download mode only using buttons.
Sent from my SCH-I500 using XDA App
Grimis said:
He said make sure you can get into download mode only using buttons.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ah, you're correct. He's just letting you know that you need to be able to get into download mode when your phone has gone into a boot loop. Holding volume down while putting inserting the USB cable will take you to said download mode.
djk21108 said:
Ah, you're correct. He's just letting you know that you need to be able to get into download mode when your phone has gone into a boot loop. Holding volume up/down while putting the battery in will take you to said download mode.
Click to expand...
Click to collapse
That is the recovery not download mode. Download mode is when you need to ODIN. Hold volume down and plug into USB for getting into download mode.
I thought that is what he was saying, but, making certain before I began. Thank you.
Sent from my SCH-I500 using XDA App
What's broken in this ROM?
Im wanting to flash my roomies fascinate to fix the broken vodoo roms
XFreeRollerX said:
What's broken in this ROM?
Im wanting to flash my roomies fascinate to fix the broken vodoo roms
Click to expand...
Click to collapse
So far just the cellular signal bars for me.
In the op it says to use cwm 3.x but we are currently on 4.x. Why the down grade?
Sent from my SCH-I500 using XDA Premium App
wideopn11 said:
In the op it says to use cwm 3.x but we are currently on 4.x. Why the down grade?
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
cause 3.x is the one that you flash from ODIN first, then install this ROM. Then it gets "upgraded" via the bundled kernel with this ROM. yeah the signal bar thing kinda freaked me out. i also couldn't get MMS to send. but i came from the previous build and didn't wipe anything except dalvik. just wanted to try it... i'll do a full wipe and install tonight. I'm so freaking stoked we finally have a mainlined CM7 rom!!! Coming from a Droid 2 previously and being teased by my Droid 1 before that, it feels like this phone has finally arrived.
This seems to have killed my wifi. I'll retry and repost if I get a chance.
wideopn11 said:
In the op it says to use cwm 3.x but we are currently on 4.x. Why the down grade?
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
So I did some experimenting. Following the OP I flashed the cwm in ROM manager, booted to recovery via ROM manager and got orange 4.x. I then flashed CM7 again booted to recovery from ROM manager and got blue 4.x. Looks like ROM manager will use whatever recovery you have installed after you initially flash the included one.
Sent from my SCH-I500 using XDA Premium App
wideopn11 said:
In the op it says to use cwm 3.x but we are currently on 4.x. Why the down grade?
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Sounds like you're already on aosp. In that case there's no need to downgrade your recovery. Just use the one you already have to flash the nightly.
Another Fascinating post by my XDA app...
i am stuck. i tried to flash super charged hatka 320 dpi and i have gone in the wrong direction because my dna doesnt boot up properly. after super hatka gets past the boot i am able to get to the lock screen and once i swipe to unlock, it says unfortunately settings have stopped working. my launcher doesnt work. i cant operate the phone what so ever except for looking at the settings. when i get a text message i can reply, but thats pretty much it. i have experience in rooting and flashing the htc g2, gs2, and the gnexus. but this htc dna is something different and i am having extreme difficulties. i can go into much more detail if someone has the moment to help me out
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
If you came from another ROM or Stock, Factory Data Reset from recovery is advised ... you could also try flashing another custom ROM to get moving
Djmk4 said:
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
dj2muchxx said:
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
Click to expand...
Click to collapse
What's happening mate...really can't help you...the only thing I suggest to write exactly what you wrote here in hatka's Rom thread...maybe the dev that made the Rom....can help you or someone might had the same issue
Sent from my HTC Droid DNA
What recovery are you using? I had an issue with twrp at first and switched to cwm touch. And no issues. I've had issues though by going back after getting stuck at boot and wiped then installed Rom with full wipe. But if its an error not installing might try fastboot flashing a different recovery
Sent from my HTC6435LVW using xda premium
dj2muchxx said:
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
Click to expand...
Click to collapse
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
fixed
i may have had a bad download. i was using the 320 dpi senseless rom, my phone was unusable like i had stated, but i managed to get it running.
here is what i did to fix it:
in the settings, i linked my dna with my google account, and as i expected, i received play store notifications about updates, so i chose the notification and it took me to a fully functioning play store.
i downloaded apex launcher and it installed properly. pressed the home button and it automatically set itself as the default launcher and bam! my dna was beginning to function.
downloaded xda app and went to the super charged thread and downloaded the slim version of the rom instead of the senseless rom.
flashed the boot.img, flashed the modules, then flashed the slim rom and i didnt get any errors or failed messages this time.
i dont want to point fingers and i would never do that here on a fantastic community, but the senseless rom was giving me issues, maybe it just needs some more work. anyways phone is functioning like normal now, everything works and the battery is outstanding so far.
thank you to those for the advice. i was getting ready to call it quits and send this thing back to amazon wireless.
MustafaHadaKing said:
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
i think it was just the rom, if u need a guinea pig to test out your rom or anything, im in. i am enjoying super charged hatka very much:good:
This is the pre-alpha thread of OmniROM for the Samsung Galaxy Note 2 (i605). More information can be found here.
This build is very bare bones at the moment. Don't let flashing this now turn you down from trying it again in the future, a lot of changes are coming soon. I would still consider this much more of a tester than a daily driver unless bare bones is your style. The rom is very smooth and fast though probably for that very same reason.
Source:
https://github.com/omnirom
https://gerrit.omnirom.org/#/q/status:open,n,z
https://github.com/omnirom-slickrick
What doesn't work:
You tell me!
Installation method:
Wipe all if coming from another rom
Flash OmniROM
Flash GApps
Reboot
This rom does not come with root by default. Flash SuperSU in recovery if you want root!
Flash at your own risk! No one else is responsible if your device bursts into flames
To try out multiwindow, go to recents and long press an app. Click add to split view and repeat to add another app. Keep in mind its still buggy at the moment
Have fun and enjoy!
For "pre-alpha" this is a very solid stripped to the basics AOSP ROM. Obviously features like customizing and themes will get added in but for now this is pretty good. Basic stuff like wifi, bluetooth, phone, etc are working on my end here. Looking forward to seeing where this ROM goes. Will be keeping my eyes on this.
Excited to see this come together.
Sent from my SCH-I605 using xda app-developers app
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
dagod80 said:
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Boo so excited for 4.3... my socks are wet
ssmr2t said:
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Click to expand...
Click to collapse
There's a working art version on RootzWiki
Sent from my GT-N7105 using xda app-developers app
im definitely excited about seeing this rom come rogether in the future! thanks Rick!
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Pilatus47 said:
Try to flash the last Rom with the working baseband. And then flash Omni.
Saludos
Click to expand...
Click to collapse
Dirty flash on top of an existing rom with working data? I will try over CM 10.2 to see if that works.
Update: That was a no go. Stuck at boot...
R-Rizzo said:
Are you flashing any LTE fix zip?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I am afraid I have not seen that zip. Is it the one found here?
Update: Tried this and the apns-conf.xml from slick_rick found here just to see if it would resolve the issue but still a no go...
Click to expand...
Click to collapse
PapaJohnMc said:
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Click to expand...
Click to collapse
yeah i couldn't get data to show up, but I'm okay with that the rom was definitely smooth and I'll have to try it out again soon. thank you Rick! you kick ass like always
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here is what I have. I haven't done a logcat in quite some time. Hope this helps!
Thanks
This is my daily driver so I am flashing back to CM 10.2 for now... Gotta be accessible.
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'll have to restore my nan and run a log.
EDIT: here's my logcat @slickrick
EDITdos: if that's not enough I'll run another logcat just let me know!
Any progress on the data issue? I tried again and still a no-go on data.
Thanks!
sorry to bring up a semi old thread, but i wonder if because i flashed omni using twrp 2.6.3.0 that's why i didn't have data... ima try with cwm and see if i have data then
EDIT: yup that didn't fix my radio issues..
Data working
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Bluetooth
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
I wiped cache and dalvik rebooted and reconnected bluetooth and everything is good.
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
This worked for me! Thanks!
Sorry
Sorry, I am going to be "that guy" who proves my ignorance. I would love having the OMNI rom on my i605, but I couldn't get data or voice working. I saw the whole thing about backing up and restoring but I could not get that to work either. Are you working on a 4.3 or 4.4 release?
Thanks
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
maybe try this
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Joshua Mr PC Repair said:
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Click to expand...
Click to collapse
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
I just Tried it again .
Had No Issues ,
Can You Try with a new SD Card .
Then Do The Wipe
also load TWRP Via Recovery , If You have CWM Go to Install Click > TWRP .
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Put on SD Card and install
captemo said:
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
This is the one that works for KK
[TWRP_Recovery_2.7.0.0][Unofficial][quincyatt]
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices. So please provide a detailed step-by-step information if you can.
SockmanTGR said:
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices.
Click to expand...
Click to collapse
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
25625292 7345
captemo said:
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
Click to expand...
Click to collapse
I followed your instruction with the kernel(http://forum.xda-developers.com/showthread.php?t=2326786) Had to download it directly to my phone. It didn't like it from my laptop.
Successfully installed.
I'll let you guys know if my problem continues,
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
You are not using twrp from the thread linked. Also do NOT use the twrp app for the recovery as my recovery is not found there. It can only be found in my thread. Flash it in recovery & you're good to go.
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
i had the same problem and went to liquid smooth and is stable
jemsTV said:
i had the same problem and went to liquid smooth and is stable
Click to expand...
Click to collapse
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
SockmanTGR said:
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
Click to expand...
Click to collapse
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
delawaredrew said:
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
Click to expand...
Click to collapse
Would I need to reflash the ROM to ally another kernel?
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
As instructed, you need to do some reading. In my last post I gave you instructions on how to add kernel.
Help yourself first, then others will be more than happy to assist.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
I'll give you some slack 'cause I am still close enough to my first flash that I remember being full of questions, but at least read the OP and most recent pages in your ROM thread. You should skim through it all ideally but some are 100+ pages so....
Kernel switching in general does not require any ROM action, there are likely cases that it might be useful but I've never had a problem. You will need to ensure that the kernel is matched to your ROM; KitKat or Jellybean or whatever. I usually do it as I flash a ROM but I have gone back and installed a kernel on a running ROM plenty of times; Uber for instance was released after I had BeanStalk up and running, it is a good kernel so I switched to that.
As a more general point the Note is hard to brick, as long as you don't somehow mess up the recovery (CWM or TWRP) you are just a quick restore away from back to normal. Use the backup function in your recovery, it is your friend and savior. Keep a copy of the back-up on your PC (or Mac) and you will usually be golden.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
If you are on BS Rom you should know that all you need to to know is on the OP post-the rom and the patch. The latter contains about 5 different kernels which you can switch betw. to your hearts content. The patch is n00bie proof to make your switches. Really hit BS OP.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
Just like all the other kind gents adv'd, it's all in patch's OP:
http://forum.xda-developers.com/showthread.php?t=2535857
Including polluti0n's patches thread:
http://forum.xda-developers.com/showpost.php?p=50529734&postcount=854
He uses aroma installer, so when you flash it (personally, I did it with CWM) you don't need to wipe cache/dalvik nor wipe phone, he mentons this on patch's thread while answering questions I believe. The screenshots show you some differences between the kernels he has available, either CM, Uber or PAC.
Personally, I'm using PAC since for me it seemed to work better with the Xposed's Netflix workaround, whereas it didn't work that well with Uber.
Also, the patch provides fixes, for camera, screen flicker and such.. Give it a try, and you'll definitely love your phone more!
Here is the SM-T237P Stock Rooted Deodexed 5.1.1 BOH7 Base Knox Free Rom.
Features
Rooted
Deodexed
SD Card Write Fix
Updating from kitkat still has some bugs so I have pulled the files for now
Directions If Coming From KitKat
Odin Method To Update Firmware
Place rom on sd card
If comming from KitKat flash the firmware SM_T237P_BOH7_FIRMWARE_ONLY.tar.md5 using Odin Uncheck The auto reboot under options in Odin
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Recovery Method
Place Rom On SD or Internal Storage
Place SM_T237P_BOH7_Firmware.zip On SD or Internal Storage
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Install SM_T237P_BOH7_Firmware.zip Do Not Reboot
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Directions If Coming Lollipop Rom
Place rom on sd card
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Downloads
SM_T237P_BOH7_ROOTED_STOCK_DEODEXED.zip
Mini Firmware Update Files
SM_T237P_BOH7_FIRMWARE_ONLY.tar.md5 (Includes Custom Recovery by @moonbutt74)
KitKat Roms
Here is the SM-T237P Stock Rooted Deodexed 4.4.2 NL1 Base Knox Free Rom. Must have Custom Recovery Installed.
Feel Free To Use As A Base If Anyone Wants Too!
Custom Recovery Found Here
Or You Can Use Odin and Flash NL1 Firmware Only Including Bootloaders, Modem, Kernel, and Custom Recovery(By @moonbutt74).
Directions
Place rom on sd card
If on Older Firmware Flash The NL1 Firmware With Custom Recovery Already included Using Odin
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
Enjoy!
Downloads
SPR_T237_STOCK_NL1_DEODEXED.zip
Mini Firmware Update Files
SM_T237P_NL1_FIRMWARE_ONLY.tar.md5 (Includes Custom Recovery by @moonbutt74)
SM_T237P_NL1_KERNEL_ONLY.tar.md5
Mods/Updates
Coming Soon!
Thanks for making a deodexed version.
I have had this awhile I just forgot to post it.
Downloaded...
Will install and check it out as soon as I get time.
Thanks !
will this work on the SM-T230?
jdmsohc22 said:
will this work on the SM-T230?
Click to expand...
Click to collapse
No
Anybody getting the notification bar not working in fact it doesn't matter what app is open but the top won't work for a bit then it'll work again?
It did it on straight up stock with root. I've redone the recovery and flashed this ROM and its happenening again. It took a while to do it like a few hours or so. Any thoughts?
Smirky Guitars said:
Anybody getting the notification bar not working in fact it doesn't matter what app is open but the top won't work for a bit then it'll work again?
It did it on straight up stock with root. I've redone the recovery and flashed this ROM and its happenening again. It took a while to do it like a few hours or so. Any thoughts?
Click to expand...
Click to collapse
I don't think I've had any issues with the notification bar not working while using this build. But I'll double check when I get out of work for you.
VerneVerne said:
I don't think I've had any issues with the notification bar not working while using this build. But I'll double check when I get out of work for you.
Click to expand...
Click to collapse
Its not just notification bar, its anything at the top like settings buttons or tabs. It literally just did it again for 10 mins after booting from being off. Its working normal again. Weird.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Smirky Guitars said:
Its not just notification bar, its anything at the top like settings buttons or tabs. It literally just did it again for 10 mins after booting from being off. Its working normal again. Weird.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I just got home and asked the wife if our tablet had been acting up lately and her response was no. I did have a slight issue with my brightness and volume slider bars disappearing but that was the original stock rom. That was fixed by reflashing using Odin.
I assume you tried a factory reset and all the other standard fixes?
Sorry I can't help you more. Good luck
Are you familiar with kernel development? I see there are custom kernels for other galaxy tab models and even other SM-T23X models but nothing for the sprint variant. Or would anyone have any resources for me to possibly learn how to build my own ? thanks
work great in my tab, thanks for share mate!!
hi
hi is the French language???
Uploaded New 5.1.1 Lollipop Rom
jrkruse said:
Uploaded New 5.1.1 Lollipop Rom
Click to expand...
Click to collapse
Super! I will check it out ASAP
I thought about learning this and creating one myself but haven't had time.
Thank you very much!
Rick
PS - I had recently gone back to factory defaults since it had been so long since last rom I felt i needed security updates.
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
jrkruse said:
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
Click to expand...
Click to collapse
Well, I downloaded it but haven't been able to get it installed just yet. Maybe sometime tomorrow if all goes well. Thank you
jrkruse said:
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
Click to expand...
Click to collapse
Did you create a custom kernel? What method of root are you using (system-less, or full system root)? @moonbutt74 is working a custom kernel for the t237p, but not really sure how long it'll take...
fiddy619 said:
Did you create a custom kernel? What method of root are you using (system-less, or full system root)? @moonbutt74 is working a custom kernel for the t237p, but not really sure how long it'll take...
Click to expand...
Click to collapse
This is a systemless root method, so if you factory reset you will loose root and have to reflash the beta 2.66 root zip. The kernel source has not been released yet for our device so until we have that there will be know custom kernel.