I have my Sprint Mogul, and Sprint service, and i am currently running the 2.16 ROM. I am deciding whether or not to upgrade to a custom ROM (if so which one) or to just do the update to the new stock ROM 2.17, or even to just wait for the new ROM with GPS and EVDO REV.A. So if someone could please help me in deciding cause I really don't know which one has more benefits. I want it to be able to run fast, with good RAM, but also to run well with my Sprint service, cause ive been looking at the custom roms and i see that some of them don't work to well with sprint. So to sum it all up, which is better, a custom Rom for my Sprint Mogul, with sprint service, or the stock 2.17 Rom, which I know will work with my sprint service well because it was made for it. Thanks
A custom rom if a good one like dcd's newest rom then it will be fine since it is based off of the sprint rom anyway and will just allow you to choose what you want to install but it is all up to your preference. If you don't like it you can always flash back can't hurt to try right i personally would never use stock rom again since dcd's actually works with sprint better ex no glitches
mastachillz said:
A custom rom if a good one like dcd's newest rom then it will be fine since it is based off of the sprint rom anyway and will just allow you to choose what you want to install but it is all up to your preference. If you don't like it you can always flash back can't hurt to try right i personally would never use stock rom again since dcd's actually works with sprint better ex no glitches
Click to expand...
Click to collapse
x2. The new DCD 1.6.7 is the best ROM I've run yet. You'll be pleased.
Does it fix the memory leak problem that is with the stocks? and does everything like MMS and Internet, and all the other sprint service based stuff work? and lastly about how much faster is it and how much free ram do you have? Thanks for all the help.
Memory leak is still present from my experience.
So how is it running better than the stock ROM (newest 2.17)? Is it alot faster? since for me, the only problem with my phone is the memory leak, other than that, it barley ever freezes or locks up, and i only soft reset it about once a week, just to get my memory back (although the device would be running fine without soft reseting, I just like doing it). I just want to know, if it would be worth it for me to have to reinstall all my programs and settings, for a ROM that is not that different. Thanks
also on stock rom right now. kinda scared to do the do the custom rom but I will this friday. I will let u know if the 5 meg page pool speeds it up nutz on chin style. my biggest issue right now is when I click to write a text message. the text message compose screen takes forever to load. a good 5 to 10 seconds. and when I press the msg button at top of phone. that also takes forever and I bout done with it
Definitely get off of 2.16, it was horrible. My phone has been a LOT more stable on 2.17.
And, the "memory leak" isn't really a memory leak, it's a feature. I've seen this repeated over and over again. It's caching to make the system feel faster. It only becomes a problem if you actually run out of memory.
Either these roms are very easy to update or I'm missing something.
I read through the Kitchen thread and the Rom thread for dcd. Very interesting thread although i could not find any form of instructions. I searched instructions and it provided a link to the unlocker.
So I'm guess you run the hard spl unlocker and then the dcd rom update and its that easy?
calisoldier83 said:
So I'm guess you run the hard spl unlocker and then the dcd rom update and its that easy?
Click to expand...
Click to collapse
yes
eventually i will get instructions up..sorry
Well I have tried a few custom roms, made a few with the kitchen, and of coarse used the stock rom. I now find myself falling back on the stock rom because I feel it is the most stable for my use. I would recommend using a backup such as spb or something. That way if you ever jack up your mogul you can just do a hard reset and then restore it to how it was from the last backup. I really like what people have done with the custom roms, but I have just had a few minor issues that I do not have with the stock rom. Chad
By stock ROM, I am assuming you are using 2.17 right?
So I am thinking about isntalling the gingervitis 1.0 rom, I am currently on 1.12.605.6 radio and stock os w/root, I was wondering what radio i need to be on for this rom( he does have a link for a radio but dont know if it is ok to upgrade from the verison i am on) and after i do flash this radio and rom, and say i dont like the rom, if i restore back to stock os w/root am i able to keep the radio i upgraded to or am i going to have to downgrade to a different one, sorry about posting this in general i tried in the actual thread and got no answers.
You should be fine upgrading as long as you follow his steps.
As far as going back, I don't think that radio works on froyo roms. That's why when you flash the radio first and boot your phone back up, you don't have service. I could be wrong, but that's what I've gathered from everything.
I have GB right now and the only problem I've had so far is my text messages are out of order. Other than that, everything works great. I do know a lot of people are having trouble placing phone calls, and having random reboots though. It seems pretty hit or miss, but the developers are working hard trying to get everything as stable as possible.
Seems like every day since the leak a new version comes out with more bug fixes and different sense 3.0 additions. If you don't like the downfalls you see today, wait until tomorrow and see if they've fixed it yet.
I've been very impressed with the amount of bugs have been fixed so far and how fast they've fixed them.
I was having Force Close issue on beta 6 but beta 5 rocked
k i think i am going to do it, do you know if its easy enough to just flash the old radio back on it or am i going to run into problems if i decide to restore back, also when he comes out with updates i should just be able to flash the newest beta on top the other or should i do a wipe and then install again.
I'm having serious charging problems with this rom and the test 4 kernel. Talking like, 3% charged in 45 minutes off the wall.
I'm using the beta 6 Rom with the kernel that came with it and no problems so far not even reboots, have tried the newest kernel by imoysen?
Sent from my ADR6400L using Tapatalk
Hi, everyone. I'm used to rooting/ROMing/etc. on the Samsung Epic, but I'm very new to the Thunderbolt. I rooted my girlfriend's phone and had some problems with the data connection being inactive following a kernel install. I went back to as close to stock as I could in order to get everything working again, but new problems have surfaced:
1. GTalk crashes
2. Camera fails to open
3. Documents fail to open, as in Word
4. Phone fails to update, though it indicates an update is ready
Right now, she's on a pretty much stock Froyo ROM and what I believe is the stock kernel, or something very close.
I've read a bit about the camera and gtalk problems. I saw a link to a CWM flashable zip that apparently fixes the date problem that causes the closes. However, it wasn't clear if that zip was only for GB for if it also works for Froyo. Please advise on that.
I haven't seen any reference to the document opening problem, unfortunately.
As far as the update thing goes, I'd rather keep her on a custom ROM, as I assume the update will kill her root.
Basically, I'm looking for a stable and reliable kernel, ROM (preferably GB), and radio combination that is known to run without issues. Last time I tried to pick a combo myself, it ended up killing the data connectivity, so I'm trying to figure out the "best" combination that is known to work. Also, if there are any Thunderbolt-specific flashing procedures that tend to cut down on force closes and errors following a flash, please let me know.
Thanks a lot,
-Rob
When you say update, you mean OTA? If so, you have to be 100% stock to get an OTA to install. You can't have a custom recovery installed.
Pretty much all the GB ROMs out there are pretty stable. The question is, do you want a Sense ROM, or AOSP?
As far as kernels go, Imoseyon's kernels are top notch. I prefer jdkernel for AOSP ROMs though.
I use the latest OTA radio and have 0 problems, and it works for both froyo and GB ROMs.
...
Thanks a lot for the response. I'd like to keep on the Sense side of things, just to keep the user experience sort of like stock for the girl.
So, to go one step at a time:
First, the radio. Is this the latest OTA radio that you mentioned (MR2?): http://forum.xda-developers.com/showthread.php?t=1154010
Second, the kernel. It looks like nerozehl has a great kernel that's based off of Imoseyon's leankernel. There are so many versions, though. Would the latest Sense kernel 2.3.6 (from http://forum.xda-developers.com/showthread.php?t=1099996) be appropriate, considering the ROM below?
Last, the ROM. It looks like SynergyROM is a good place to start. I believe the latest one is found off the download link near the top of this page: http://infectedrom.com/showthread.p...IGHTLYS-2.3.4-SENSE-3.0-★-☆-★?p=4368#post4368 Any thoughts on SynergyROM?
Does that combination seem like one that should work correctly?
Also, just so I have the steps correct for installation:
1. Flash radio in hboot.
2. Wipe in CWM (cache, dalvik cache, anything else?)
3. Flash kernel in CWM.
4. Flash ROM in CWM.
5. Reboot.
Thanks again for any help. It is definitely much appreciated. Can't go around breaking the girlfriend's phone, after all...it just looks bad!
-Rob
There is an issue with the lib files for the Camera ,which is messing up Gtalk. There is a fix in several threads, something HTC did on the new base.
Here is the fix:
http://themikmik.com/showthread.php?8436-Flashable-G-talk-Camera-Fix
...
Thanks, fillyo! I assume this works for both GB and Froyo ROMs?
-Rob
If you flash the kernel before the ROM whatever kernel comes built in to the ROM will overwrite the kernel you just flashed. I would say ROM, kernel, radio.
Oh and when you wipe I would do:
1. Wipe data/factory reset
2. wipe cache
3. Advanced, wipe dalvik cache
4. Under mounts and storage select format /system
Sent from my HTC Thunderbolt
JBO, thanks for the advice. That makes a lot of sense. Do you have any comments on the radio, rom, kernels I've selected above? Particularly the radio. I was told the latest OTA radio works well, but is that the one also knows as MR2?
Thanks,
-Rob
Sent from my SPH-D700 using XDA App
Yes the MR2 radio will work with that ROM as well as any leaked radio that is newer than the MR2. What radio works best is kinda subjective and seems to vary from person to person. I don't know if the kernel you linked is compatible you would need to ask in the Synergy thread. Honestly as far as the kernel goes I would just use the one built into synergy. I hear its quite good and has a great set of features.
Sent from my HTC Thunderbolt
I've used SynergyROM and it is an awesome ROM. It comes with Ziggy's kernel, which is an awesome kernel. The OTA Radio basebands are 1.39.00.0627r, 0.01.69.0625r
I hope you find a ROM/kernel/radio combo that works for you!
That's exactly the info I needed. I'll just stick with the built-in kernel and the MR2 radio. Thanks for all the help, guys.
-Rob
Sent from my SPH-D700 using XDA App
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4