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.
Related
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
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.
I have the EVO 3d and recently installed this ROM "MIUI.us 2.1.6 HTC EVO 3D CDMA [01-07-2012] by jdeloach" I just wanted to test it out a few days and see how well the EVO 3d handled it. I was impressed with the ROM and had no trouble with it but just wanted to go back to another custom Android ROM. So after flashing the new custom Rom and my phone booted up I started to get several MIUI force close. I used Rom Manager and Have done the same thing on my EVO 4g without any issue but this time on boot I still get the MIUI force close. After about 4 or 5 force close it stops until next reboot. Just wondering if anyone has seen this before and is there a quick fix? I couldn't find a thread on this issue so here I am. It may also be something simple but I have never had this problem and therefore have no idea how to stop it. I have done everything I can think of. Different ROM's, format SD card, factory data reset, put factory ROM back on, nothing seems to get rid of the MIUI force close at start up no matter what ROM I have flashed.
When flashing new ROMs, I generally like to run what's been termed a "Superwipe" or "Format All" script. You flash this just like you would flash a ROM, however it wipes all of the partitions (minus the WiMax one, and probably one or two others) so that no data is left over from the previous install.
I use myn's Warm Format All tool here. This is from this thread. It's NOT specific to the Warm TwoPointThree ROM, so it's a great tool to keep on your SD card whenever your ready to flash a new ROM.
Just flash it before you flash your new ROM.
Hope this helps!
Thank you very much.
Well I be darned. I spent three days trying to understand why it was doing what it was doing and your suggestion fixed it instantly. I did try something similar to what you said to do but with another zip with no luck. So I was a little skeptical, but after I flashed the zip file you told me to download and then flashed my ROM which is Infected ROM Eternity ROM for Rooted HTC Evo 4G![Sense 3.5] it was fixed
I owe them guys a plug cause this ROM is pretty darn good. Anyways I knew it was something pretty simple I just needed to be pointed in the right direction, so, many thanks to you for helping me get rid of those annoying MIUI force close. I really do appreciate you quick and helpful response.
HTC EVO 3D, Quietly Brilliant.
A man is not complete until he's married
and then he Finished.
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Suggestion of a stable custom ROM and additional info how to "cleanly" install it.
Hello to the community.
I need your help in choosing a stable custom ROM and some info on the steps on how to make a clean install.
I was using a galaxy S3 i9300 with CM11 and TWRP 2.7, 2 years ago. I bought a used htc m8 and put the S3 on the drawer. Last year i turned it on again and used it some time. I checked for updates and without thinking it, i installed cm 13(snapshot). After restarting it, i had the problem with the " trebuchet stopped" and "google play services stopped".After that, i did sth that i don't remember and had the flashing(boot loop?) twrp logo and not being able to boot to the phone. And i put it again in the drawer. Now i want to give it to my little brother and today i took it out again.
Through terminal and adb i booted the phone with the "reboot" command but had the "trebuchet + google play stopped" message again. After some time fiddling around, i flashed the latest version of TWRP with Odin, thinking that i could solve the problem like that but the phone is stuck on the CM logo trying to boot. Even if it boots i think it will show these 2 messages all the time(but it doesn't boot) .
So i want your advice on choosing a good and stable custom ROM to flash, possibly with Odin. The language will be in english and i don't care if it's Android 6 or 7 or 5 as long as it's stable. He will use the phone for basic stuff and not sth too extreme. I remember using CM11 without issues but i know that now there are lots of others roms. Also i want to make the cleanest install to minimise the possibilities of crashes and to give him a clean from everything, phone. But i have forgotten some steps in TWRP.
Thank you in advance and i'm waiting for your suggestions and advice.
The last official stock firmware is probably best as it is the most stable and he won't be able to break it unlike with custom roms.
Beamed in by telepathy.