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
Related
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
I have the HTC g2 tmobile phone. I have just gotten into the flashing/modding scene, and am having a blast tweaking the phone. I have been trying a lot of roms in the past days trying new ones I like or may not like. Anyway I had the Cyanogen nightly rom on there before I flashed with the virtuous sense v2.0. Everything seemed good until I tried unlocking the phone after the looong reboot. Now when I unlock it I get a lot of force closes. Specifically for messages, and media, then the phone just reboots. Keeps doing the same thing over and over? Any help? If I could just figuire out a way to reboot into recovery and flash w a diff rom, or is there something missing since Im getting the FC from a few things? Thanks a lot!!
hi wtfd00d, if u new to flashing rom and wanna flash a stable rom, try keep yourself away of any custom with name "Nightly/Nightly build" because Nightly build, although is kinda ahead of time, is still in development build and merely for testing. try flashing other rom if you would.
I'm hoping I can provide information that may be helpful to developers about the Thunderbird's random rebooting problems.
For my phone it seems related to the ROM I'm running, so maybe this will help ID the problem?
ROMS w/o reboots:
Got the phone, got the OTA update, no reboots. None.
Rooted the phone, configured and ran PG05IMG_MR1_upgrade.zip, no reboots.
After bad experienced, unrooted, back to stock, no reboots.
OTA update again, no reboots.
Re-rooted, again ran the updated rooted ROM, no reboots.
Several listed below caused problems so I'm on Synergy with no reboots.
ROMs with reboots:
Liquid 1.5, reboots 2-3 times/hour
Liquid 1.4, reboots several times/day
Liquid 1.6, reboots several times/day
PUR3A05PTH3ORY v 1.2.2 reboots several times/day
Gingervitis 1.2, no reboots, powers off and won't come back on until I do a battery pull!
I'm really hoping this will help someone take a stab at fixing the problem! Changelogs for Liquid should help, why is 1.5 worse than 1.4 or 1.6? What's included or missing in the ROMs that fail as compared to the roms that work?
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
For example, I used Gingeritis based off of the GB leak and was getting a lot of reboots, but I tried BAMF and wasn't getting any. Meanwhile others get reboots on BAMF and don't on Gingeritis. Android is some trial and error before everything works just how you want it, IMO.
I was getting a lot of reboots almost non-stop from PUR3A05PTH3ORY. and I get 1 once in a while with CM7.
I know some TB's even rebooted a lot with the stock rom unrooted. My first one was like that.
I've flashed the mr2 radio and have used it for all roms and I've had no reboots
Bolted Down....
g00s3y said:
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
Click to expand...
Click to collapse
Partially true but there are common factors such as many having reboot problems with Liquid 1.5, etc.
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.
Hey everyone. I have a friend who has been attempting to root and install roms on his i777 device for a while now and every time it seems like something else gets screwy. I have an HTC so I know little about the process of working on his Samsung device, I thought it would be about the same but it seems way more complicated... Anyway I think all his problems started with a bad ROM he installed unknowingly when he first attempted to root his phone. And since then he has went to ICS then back to Gingerbread and it keeps getting more crazy. He has tried to do a factory reset on it but it fails half way through now so it wont even let him pull that off.
So my two questions are:
1) What is the best way to get this phone completely cleared up?
2) And what is a good/dependable Gingerbread ROM for this device?
I did a bit of digging on ROMs and found several in the "AT&T Samsung Galaxy SII i777 Index" thread. But since I dont have this device I cant try any of them out for him, and like I said early I know little on Samsung devices.
Thanks for any help!
Bakuro117 said:
Hey everyone. I have a friend who has been attempting to root and install roms on his i777 device for a while now and every time it seems like something else gets screwy. I have an HTC so I know little about the process of working on his Samsung device, I thought it would be about the same but it seems way more complicated... Anyway I think all his problems started with a bad ROM he installed unknowingly when he first attempted to root his phone. And since then he has went to ICS then back to Gingerbread and it keeps getting more crazy. He has tried to do a factory reset on it but it fails half way through now so it wont even let him pull that off.
So my two questions are:
1) What is the best way to get this phone completely cleared up?
2) And what is a good/dependable Gingerbread ROM for this device?
I did a bit of digging on ROMs and found several in the "AT&T Samsung Galaxy SII i777 Index" thread. But since I dont have this device I cant try any of them out for him, and like I said early I know little on Samsung devices.
Thanks for any help!
Click to expand...
Click to collapse
1) Full wipe in CWM.
2) No one uses Gingerbread ROMS anymore (for the most part). As a matter of a fact we'll be getting Jellybean soon! Stick to an ICS rom, I recommend either AOKP or CM9.
EDIT: If he wants more of a stock feel, try out Mystics Glory.
Ok. Number one, if he wiped with the stock ics kernel installed, there's a chance he messed up his phone. The stock ics kernel had a severe bug in it. Number two, after he's no longer in ics stock kernel , do a full wipe including system, data, cache, dalvik, and run kernel cleaning script. Thirdly, there are a number of roms out there. Tell him to try them and see which one fits.
Sent from my MB860 using Tapatalk 2
I thought about doing all the wipes as well. I wasnt sure if they would work or not though because he cant backup and the factory restore isnt working. I told him to try it through CWM and recovery apparently neither are working well.
And he doesnt want ICS anymore because they changed how the phone connects with tether. With Gingerbread he just had to freeze Tethering Manager to get it to work in ICS Tethering Manager doesnt exist anymore so the same process doesnt work.
However Im sure he would like an ICS ROM if it unlocked tethering for him. The illuminati ROM on my Vivid unlocked the tethering for me, is there something similar for the i777?
Bakuro117 said:
I thought about doing all the wipes as well. I wasnt sure if they would work or not though because he cant backup and the factory restore isnt working. I told him to try it through CWM and recovery apparently neither are working well.
And he doesnt want ICS anymore because they changed how the phone connects with tether. With Gingerbread he just had to freeze Tethering Manager to get it to work in ICS Tethering Manager doesnt exist anymore so the same process doesnt work.
However Im sure he would like an ICS ROM if it unlocked tethering for him. The illuminati ROM on my Vivid unlocked the tethering for me, is there something similar for the i777?
Click to expand...
Click to collapse
In AOKP you can tether with no issues(it also unlocks it). As far as the other stuff, if he did a full wipe like the post above said, with stock recovery. His phone may be messed up
Alright thanks for the help. I'll see if we can get anywhere this afternoon with AOKP. I'll be back after we see where that gets us! lol