Now that CM 11 nightlies are available for the Jewel, I felt it would be appropriate to post a Q&A thread to keep the clutter out of the dev thread for Deck's builds. Please keep in mind this is for questions and answers related to CM 11 nightly builds ONLY. Hit the link below for download links.
CyanogenMod Nightlies
Please note that before flashing this build, you MUST install the TWRP recovery that is specifically for Android 4.4. Link can be found below. This recovery is not the same as the TWRP recovery found on Goo or on the TWRP website. The ROM flash will fail if you attempt to flash this ROM with the standard TWRP recovery. Make sure you make a backup in TWRP prior to flashing this ROM, and remember, if S-on, you will need to install the kernel via fastboot or Flash Image GUI.
TWRP Recovery
Bootloader flashable TWRP (thanks to @Osirus71 for providing this):
Bootloader flashable TWRP
If you'd like to run CWM recovery instead of TWRP, try out PhilZ Touch CWM recovery for Android 4.4. This recovery does not have the issue that previous CWM recoveries had for our device. Get it here.
Tried the 12/09 nightly, WiFi wouldn't connect. About to try the 12/10.
EVOlved human
dneal44 from the cm 10.2 forum said WiFi works but no SMS coulda been that ur flash went wrong or something
Sent from my EVO using xda app-developers app
I believe the WiFi issue only affects WPA-encrypted connections. WPA2 should work (not sure about WEP - do people still use that?)
Yea, still no luck. Data works but no matter what I try, it won't connect to WiFi.
EVOlved human
Damn, I'm going to flash today's nightly will report anything buggy
Sent from my EVO using xda app-developers app
ultimatelegend1 said:
dneal44 from the cm 10.2 forum said WiFi works but no SMS coulda been that ur flash went wrong or something
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I started getting sms after a few reboots. It all started working. Was trying to play with voice + settings. This build is working flawlessly. (12-9)
Sent from my EVO using Tapatalk
ok flashed 10/12 nightly wifi is working and so is gps and so is the camera txting and calling r working too i tried ART but the settings and the gapps crashed and phone became completely unusable so i had to flash again so it's maybe the gapps that i downloaded if anyone here got the gapps to work with ART on cm can u plz post a link thank u
xda wont install on my phone dont know why and es file manager cant open my external sd keeps saying invalid path
12/11 still can't get WiFi. I'm at a loss. Tried rebooting. Tried WPS. It detects my WiFi, but it won't connect. Just stays locked. ???
EVOlved human
ultimatelegend1 said:
ok flashed 10/12 nightly wifi is working and so is gps and so is the camera txting and calling r working too i tried ART but the settings and the gapps crashed and phone became completely unusable so i had to flash again so it's maybe the gapps that i downloaded if anyone here got the gapps to work with ART on cm can u plz post a link thank u
Click to expand...
Click to collapse
Sorry to ask, but what nightly did you flash? I am reading that as Dec. 10, surely not Oct. 12 (I'm in America if that is why I am being weird about this).
PxPx said:
Sorry to ask, but what nightly did you flash? I am reading that as Dec. 10, surely not Oct. 12 (I'm in America if that is why I am being weird about this).
Click to expand...
Click to collapse
Yeah its Dec 10
---------- Post added at 04:32 AM ---------- Previous post was at 04:28 AM ----------
atheistevofreak said:
12/11 still can't get WiFi. I'm at a loss. Tried rebooting. Tried WPS. It detects my WiFi, but it won't connect. Just stays locked. ???
EVOlved human
Click to expand...
Click to collapse
Can't help u on that one but I'm guessing it's the phone not the ROM maybe u should try flashing the superwipe zip before the ROM and the gapps
But it will format ur internal memory completely I think (can't remember)
I am on the latest nightly but so far in all the KitKat builds I have flashed I do not get any sound (notifications, ringtones, ect) when I have my phone docked in my car dock.
Its safe to delete the downloaded nightly after its been installed right? Also with the encryption for messaging, once set up, can it work with hangouts?
So I'm on the 12/12 build and have only to issue I have ran into.
1. Very random reboots. 1 or 2 so far.
2. losing data, toggling airplane mode on/off resolves
Other than that I really can't complain. Overall this has been the Best rom I have ever used.
Great work CM team.
used correct twrp and gapps but when flasing i get... error executing updater binary in zip ... also said no md5 file found ... is there a fix for this ?
chico260 said:
used correct twrp and gapps but when flasing i get... error executing updater binary in zip ... also said no md5 file found ... is there a fix for this ?
Click to expand...
Click to collapse
Might be a corrupted zip. Try redownloading.
andrew378 said:
Might be a corrupted zip. Try redownloading.
Click to expand...
Click to collapse
actually i think i found the problem... im trying to flash the correct recovery but i keep getting error .. remote not allowed ... im stuck
chico260 said:
actually i think i found the problem... im trying to flash the correct recovery but i keep getting error .. remote not allowed ... im stuck
Click to expand...
Click to collapse
Are you flashing the recovery in Deck's thread? And what process are you using?
Sent from my EVO using xda premium
numel007 said:
Are you flashing the recovery in Deck's thread? And what process are you using?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I'm pretty sure and I'm.. fastboot flashing.. could you give me the link to decks thread so I know for sure.. just looked.. yes it's recovery from op
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...
This thread is for anyone/everyone with questions or problems with jokers CM9 or the ICS-MIUI that spleef/the_bill have been working on. The point is to try to clean up the Dev thread with the repeated questions/problems.
Here is the main thread:
http://forum.xda-developers.com/showthread.php?t=1413349
[Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 3/10/12
And here is the fixes and mods thread:
http://forum.xda-developers.com/showthread.php?t=1514963
Photon CM9/MIUI V4 Fixes and Mods
sent from my MIUI MoPho
So my unicorn won't crap rainbows. I fed it fruit loops and all it crapped was at most like three colors. Glitter is funny because it farts sparkles but the sparkles won't boot.
Ideas?
It'd be nice if moto would like sneak out some unicorn food.
Sent from my MB855 using XDA
How's this for a noob/newb question?
So I'm using a Photon 4G, which is on SBF 198_7, is rooted and unlocked (obviously), and for some reason absolutely refuses to boot the CM9 Beta. Currently I'm flashing 0.3.3 but previous attempts with .4 had the same result. I follow the instructions step for step (meaning I format system, cache, and data as well as perform a factory reset in CWM (running 5.0.2.7-photon3, although I've also tried the newest of the versions posted by Jokersax). When I install and reboot the phone sits on the red circle screen.
My logcat says:
exec '/system/bin/sh' failed: No such file or directory (2)
which to me is saying that /system may not be mounted at all.... I've read the CWM 5.0.2.8 has this problem but not with 5.0.2.7. Any ideas on what I should try to get past this issue?
Thanks!
maarekelets said:
So I'm using a Photon 4G, which is on SBF 198_7, is rooted and unlocked (obviously), and for some reason absolutely refuses to boot the CM9 Beta. Currently I'm flashing 0.3.3 but previous attempts with .4 had the same result. I follow the instructions step for step (meaning I format system, cache, and data as well as perform a factory reset in CWM (running 5.0.2.7-photon3, although I've also tried the newest of the versions posted by Jokersax). When I install and reboot the phone sits on the red circle screen.
My logcat says:
exec '/system/bin/sh' failed: No such file or directory (2)
which to me is saying that /system may not be mounted at all.... I've read the CWM 5.0.2.8 has this problem but not with 5.0.2.7. Any ideas on what I should try to get past this issue?
Thanks!
Click to expand...
Click to collapse
jokersax11 said:
Or just flash the rom twice
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Try this first, of course.
If no worky, then this miggghhhtt:
This are the steps to be able to boot into 4.0:
1. Wipe everything as usual in CWM by Joker
2. Flash 0.3.1 and only 0.3.1
3. Reboot, into 0.3.1
4. Let it sit for 1 minute, mess around in it for that time.
5. Reboot into Recovery(CWM by Joker).
6. Flash 0.4.0, gapps and or the usual.
7. You can now reboot into it.
Or just flash the rom twice
Sent from my MB855 using XDA
jokersax11 said:
Or just flash the rom twice
Sent from my MB855 using XDA
Click to expand...
Click to collapse
The issue comes from wiping system
Sent from my MB855 using XDA
Thank You for that. It's booting now.
Curious, but what magic is performed on the 2nd flash that makes it bootable?
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
jokersax11 said:
The issue comes from wiping system
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Since the instructions for coming from another rom says to format system, should the OP on the dev thread mention the double flash issue or is this something that doesn't happen that often?
maarekelets said:
Thank You for that. It's booting now.
Curious, but what magic is performed on the 2nd flash that makes it bootable?
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Since the instructions for coming from another rom says to format system, should the OP on the dev thread mention the double flash issue or is this something that doesn't happen that often?
Click to expand...
Click to collapse
I'll update the op soon enough. However a proper update script is better in the long run
Sent from my MB855 using XDA
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
thatguy07 said:
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Those recoveries are made every time I build. I need to make a specific recovery update thats got everything working
Sent from my MB855 using XDA
thatguy07 said:
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
Click to expand...
Click to collapse
I've been using jokers cwm and everything is on my sd card. It reads it just fine. I have the newer v3 recovery. Once I choose install zip it gives me the menu for either sd card or internal, along with "update". I would use jokers recovery just cause it seems to work :beer:
sent from my MIUI MoPho
bullfrog527 said:
I've been using jokers cwm and everything is on my sd card. It reads it just fine. I have the newer v3 recovery. Once I choose install zip it gives me the menu for either sd card or internal, along with "update". I would use jokers recovery just cause it seems to work :beer:
sent from my MIUI MoPho
Click to expand...
Click to collapse
Odd. Can't imagine why it won't read mine. I've just tried v2 and v3. Several downloads and flashes of each.
No dice
I've also tried ext3 and ext4 sdcard.
Wonder if its because they are partitioned?
Its really not that big of a deal , just a few extra steps for me.
Edit : I take that back, it is kinda a big deal as nandroid won't work due to not being able to read my sdcard.
Sent from my MB855 using XDA
that is weird, maybe it is because you card is partitioned. You might want to try a different card or format your existing. I usually do that every month or so, just to clean it up
sent from my MIUI MoPho
So i installed 0.3.2 on Friday and i corrupted it somehow by restoring all my CM 7 apps and data with TB. Oh well live and learn. This am i see now there is 0.4 and a new CWM. Argh i cant keep up! You da man joker. Gotta read up on the 0.4.0 install. Thanks.
bullfrog527 said:
that is weird, maybe it is because you card is partitioned. You might want to try a different card or format your existing. I usually do that every month or so, just to clean it up
sent from my MIUI MoPho
Click to expand...
Click to collapse
well its not the fact that my sdcard is partitioned. I tried a new one, fresh download of v3 and multiple flashes. Still wont read them. Going back to romracer for now.
Its the oddest thing...
Sent from my MB855 using XDA
Huh, I'm all out of ideas bro. Sorry
sent from my MIUI MoPho
If yours won't boot..
This has been a similar issue for me on .4 and the version before.
If it seems like you followed the instructions but you are still stuck at the motorola dual core screen try installing one of these kernels. http://forum.xda-developers.com/showthread.php?t=1520417
They are at the bottom of the post and I used the 1.0 ghz one.
It solved the problem both times for me! Idk if Jokers' CM9 comes with a kernel or if you are supposed to track one down but this worked for me ..
OK a couple things with CM9 0.4.0 i'm noticing. These may or may not be known. Camcorder lags badly and then crashes everything. No macro option in the camera. Also, is there a way in ICS to have USB storage enabled by default when connecting to computer as it is in GB?
jbb2388 said:
OK a couple things with CM9 0.4.0 i'm noticing. These may or may not be known. Camcorder lags badly and then crashes everything. No macro option in the camera. Also, is there a way in ICS to have USB storage enabled by default when connecting to computer as it is in GB?
Click to expand...
Click to collapse
the camcorder is a known issue, and i dont know about the usb. i dont use it much. i use wifi file explorer to move anything i need to my phone.
OK thanks. Sucks that you need 3 keystrokes to turn usb on. Another thing I'm noticing is that once the phone goes to sleep the backlighting on the soft keys does not come back on. I wish i was smart as the devs to help with this stuff. I don't wanna sound like i'm complaining. Just making some bugs known.
I have the Evo 3d, and i flashed the meanrom ics. After i had flashed it wifi doesnt work, there is an error. I have the OTA update from sprint before i flashed it. I do not have s-off, but his thread says you do not need it. i have done a superwipe and then tryed to reflash it after i did the superwipe and still the same problem.
Did you flash the new firmware? Radios? Have you tried flashing another rom?
Yeah i did try flashing a new rom and its still the same problems, wifi doesnt work. If you know were i can find the legit stock rom ill try to download that but i cant seem to find it anywhere.
Once again, Did you flash the new firmware? Radios?
If you know were i can find the legit stock rom ill try to download that but i cant seem to find it anywhere.
Click to expand...
Click to collapse
Rooted stock roms are in the CDMA Development section.
I had the same problem. Solution I used was to flash kernel from the mean Rom using flashimagegui. Worked fine after a reboot!
Sent from my SPH-L710 using xda app-developers app
Just be very careful in which kernel you flash, s-off is required for flashing certain kernels
sent on my Evil Evo running the so called developers kernel
flashallthetime said:
Just be very careful in which kernel you flash, s-off is required for flashing certain kernels
sent on my Evil Evo running the so called developers kernel
Click to expand...
Click to collapse
OK but on his thread it says its of the 2.17 kernal so that anyone can do it no matter the gboot. But it doesnt matter anymore i finnaly got s-off to work and just super wiped it and re-flashed it again and it works.
Mclarkiin said:
OK but on his thread it says its of the 2.17 kernal so that anyone can do it no matter the gboot. But it doesnt matter anymore i finnaly got s-off to work and just super wiped it and re-flashed it again and it works.
Click to expand...
Click to collapse
As you can see from yet another success story, anybody who sees this in the future, stop fooling around with s-on. Just get s-off and be done with it. :good:
I have A solution
Mclarkiin said:
I have the Evo 3d, and i flashed the meanrom ics. After i had flashed it wifi doesnt work, there is an error. I have the OTA update from sprint before i flashed it. I do not have s-off, but his thread says you do not need it. i have done a superwipe and then tryed to reflash it after i did the superwipe and still the same problem.
Click to expand...
Click to collapse
I think i have a solution for your problem it worked for me , By the way I used 4ext touch Recovery
in recovery when you are going to flash the new Rom make sure you select { wipe data/factory reset,,wipe cach ,, wipe dalvik cach } and most important select {format all partitions (except sdcard)
after all that you are ready to install the new Rom then Reboot the device and you shall not have any problems with your WiFi But Bluetooth still wont start or work
mobi from my Nexus 5 using XDA Free mobile app
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
my Nexus 5 using XDA Free mobile app
you
I
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
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Odin stock tar file.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
Sounds to me like you have bad download of CM12. I would download it again. Compare properties of both downloads see if you have the same number of bytes. Make sure you are rooted, stock OS, and a custom recovery installed. With the bootloader current binary and system status both having a "custom" status. Then try to flash CM12 through your custom recovery again. For more info just click flashing roms in my signature.
Get your carrier to check if your imei is blacklisted on their eir node connected to imeidb.org
Sent from my D5803 using XDA Free mobile app
rbeavers said:
Odin stock tar file.
Click to expand...
Click to collapse
Sorry I'm fairly new to this, you're gonna have to tell me how to find that
Sent from my SM-N9005 using XDA Free mobile app
Philux-X said:
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Click to expand...
Click to collapse
I did the secret testing menu and changed the preferred network to LTE/CDMA and my calls started working and I started receiving sms (thank you). I can't send SMS though. Plus I lost data connectivity.
Also, I did do clean installs.
Sent from my SM-N9005 using XDA Free mobile app
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
Download from here
http://download.cyanogenmod.org/?device=hltespr
Philux-X said:
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
I tried downloading hltespr using TWRP but it kept saying unsuccessful, so I looked it up and others were having the same problem. So I switched to cwm recovery and it also said unsuccessful, and It gave the message saying that the ROM was hltespr and this device was hlte. Also all the other ROMs I downloaded in the past were all hlte and they worked fine.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Philux-X said:
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Click to expand...
Click to collapse
Okay I'll try that now, what is ViSXN3N custom ROM? I can't find anything on it
Sent from my SM-N9005 using XDA Free mobile app
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Philux-X said:
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Click to expand...
Click to collapse
Same problem, it says that this is for sm-n900p hltespr and i have hlte... also i just noticed that the message i have on the bottom of my posts say sent from my Sm-N9005..? is my phone confused? lol
update
So I installed cm11 to see if it would work and it did... I guess that means it was just the ROM? Although I loved the interface of cm12, so im going to try and flash a different version to see if that works.
Turns out when I first rooted my phone I downloaded a hlte recovery. After flashing a hltespr recovery using Odin and then flashing the correct hltespr ROM, everything worked fine. Thanks for the help guys
Sent from my SM-N900P using XDA Free mobile app