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
Related
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?
Title says it all. Will putting one of the froyo based ROMS on my phone get rid of the dreaded silent bug? I am currently running 2.1 with aloysius v12 and I get it pretty often.
I don't believe that there is anyway to be able to tell that just from which rom you run as everyone's phone is different. With that in mind though, the good thing about being rooted is that you can do a Nandroid backup, then flash another rom and see if it works out for you. If it doesn't, then you've only lost a bit of time with playing around with the new system. If you don't like it, then restoring your phone only takes a couple more minutes, then you'll know for certain. Good luck!
try a rom without sense. on the regular v3 leak i was getting the silent bug constantly, but after rooting and installing xtrrom(highly recommended) i have yet to get it
Ok so i've done just about everything i can think of to stop these reboots except ask and now i'm at that point.
I'm running:
das bamf remix 1.8 ROM
2.6.32.21_bamf_4.47 KERNEL
I used to use 1.7 and still had reboots, switch to bamf 2.1 for GB, and still had reboots, and have tried all 4 radio downloads from the obligatory radio thread. The reboots are truly random. I've had them while charging, idle, browsing web (went and downloaded another browser (which im thoroughly enjoying)) and using pandora.
So what's left at this point? I doubt it's the kernel, but i really don't know, and i want to download the control freak 2.1 kernel because i had it on 1.7 and loved the battery life.
Should i look for more updated radio downloads or just wait and see what happens with verizon?
Go back to stock, call Verizon and get a refurb. Then start new from there. If you have done that much already it may be a hardware problem.
I see. I have a warranty on mine, i can probably take it back to the store. I made a backup of my phone just after i finished rooting, if i wanted to go this route should i just flash that backup and unroot? Or just install the stock rom, kernel and radio?
Follow this
http://forum.xda-developers.com/showthread.php?t=1009423
thank you for that
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
Before you reply - let me lay a story for ya!
I bought a bran new TBolt off of my friend. I was using a fascinate up to that point and never had any issues. I loved my fassy - it was fast, reliable, and everything worked well.
Now onto the TBolt - I got the SOFF, rooted, got recovery, and got a few Roms. It is still working fine. What's the issue?
Well, I posted this on this forum and other forums more than once, but I can never seem to get an answer. After a few ROMS - Infected, Vicious, ThunderShed - I get a splash screen, or if it does boot it freezes as soon as it accesses the radio components. I have CM7.1 on it right now, ran liquid, vicious miui and other roms. Most roms do work in fact without any problems - but the few that I heard are amazing - do not.
What I have done:
Made sure my recovery is upgraded: I have tried latest CWM, EXT, CWM Touch, and the other one that was popular - all updated and did not work.
Always make sure to wipe: I always format all partitions. I have even used the Superwipe script as well, but to no avail.
I have installed a stock rom, wiped and then installed: Someone said that would work - it did not.
Double, no - triple checked my roms': Checked the MD5 sum of all ROMS and Recoveries.
Different Radios: My phone came with newest radios, and I downgraded, upgraded, and nothing.
Now, I do not mean to sound picky - but I am not happy with the TBolt at all. It works at half the quality that I had from my fassy. Wifi errors out sometime, Tether errors out sometime, it lags some of the time, and most of all - no ICS. Liquid worked well, but the touchscreen wouldn't respond during some games - not that I use it for gaming much anymore - but the idea remains.
It sounds like you are trying all of the right things, so unfortunately I don't really have anything helpful to offer. Just curious though, If you were happier with the fascinate, why stop using it? Did it break?
As far as your issues, I have found CM 7 based ROMs (or any roms not based off of sense builds) to be less reliable and have more "glitches" than sense roms. That certainly could explain some of your gripes with the TB. Have you been able to install any Sense roms other than stock?
I have long since settled on Chingy's gingeritis rom as the most reliable and feature filled, but obviously that opinion differs depending on who you talk to.
To answer your question first: I started using the TBolt because it was 4G and that was important for me at the time (I was a student and had no reliable internet). Things have changed now and I am most likely going to change back sooner than later.
I haven't tried many Sense roms. Which would be the most reliable and recommended?
I know you said you tried downgrading your radios and that your phone came with the newest ones flashed but if you haven't already done so, check this out.
http://forum.xda-developers.com/showthread.php?t=1048128
and here is the radio I've been using with no problems:
gu1dry said:
From the 2.11.605.3 RUU:
CDMA: 1.48.00.0906
md5: c6a5a9eee78e0f33267fa80ced3c49b8
LTE: 0.01.78.0906
md5: 6f33809cf2253c38a3c6bb970f030eee
Click to expand...
Click to collapse
One thing with switching to a AOSP rom from a sense based rom is that you have to use very specific radios. this page will help you find the exact radios you need to use for the rom you are running.
I am running Thundershed 1.6 with these:
http://forum.xda-developers.com/showthread.php?t=1605557
newest leaked radios and they work fine for me.
I use...
I use these with no problems.
Rom: http://forum.xda-developers.com/showthread.php?t=1409703
I use the 605.19 Radios.. http://forum.xda-developers.com/showthread.php?t=1605557
Flashed this kernel.. http://rootzwiki.com/topic/603-kern...minimalistic-kernel-620-6312-camcorder-fixed/
Click the "v6.2.0dev13 - Fixed camcorder again." link at the bottom.
I am running the kernel in "normal" mode.
No issues that I know of but I am still a noob with a post count of 2...
Alright. Thx for the help guys - for the time being I am back to the fascinate, but I will try your suggestions.
One thing I am also trying is the using the "non-semsung" micro sd card in the TBOLT.
I will report back after this weekend with the results.