I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
More things I am noticing:
The Flashlight app doesnt work anymore
Camera doesnt work then causes the whole phone to become unresponsive.
Bump!
Can anybody help me out? Im dying over here without a phone that works.
the phone app keeps crashing. If i reboot, things work ok UNTIL I make a phone call....then nothing works.
Very strange!
I would try wiping 3 times
Sent from my EVO using Tapatalk 2
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Also are you restoring things from the titanium backup?
Sent from my EVO using Tapatalk 2
MerkoPCS said:
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
Click to expand...
Click to collapse
i say you should flash MEANBEAN, its a stable JB rom and some of the bugs like the proximity sensor have been fixed thanks to the devs here at XDA. its running very smooth for me. the only issue for me is that google's navigation doesnt work, but telenav works just fine. just wipe your phone about 3 or 4 times (i always do that to ensure i get a clean install on any rom). good luck!
I would re-download CM10 and verify checksum since you didn't mention that.
Sent from my EVO using xda app-developers app
Thanks for the replies.
Really all I want to do at this time is go back to stock, which I currently am on.
But even on the stock 3.15 ROM, it is very very unstable. The phone is majorly delayed. I get 1 ring on incoming calls before it goes to voicemail - but the person calling hears the normal 5-6.
For CM10, I used the same zip file (stayed on my SD card) that I used without problem for almost a month.
I took the phone to sprint (back to stock) and they couldnt figure it out. Getting a replacement tomorrow.
Could I just have a coincidental hardware problem? Seems odd if that is the case, the phone was working perfectly until I went back to stock using the 3.15 RUU
I got my replacement phone last night, did an OTA upgrade to JB in the store and the proximity sensor didnt work...
was about to tell the rep to just order me a GS3, but I said hold off....I really prefer the 4GLTE over the S3
Went home and flashed Meanbean......WOW!
Just like stock, and the prox sensor works!
so my plan is to just keep this ROM until HTC fixes the issue in their next maintenance release.
in TWRP, i made a backup and selected all the options Is this sufficient to get me back to stock, then do an OTA upgrade for the maintenance release, if and when it comes out?
Related
Hey XDA People!.
I have an S-Off HTC EVO 3D GSM
Originally had LeeDrOiD on my phone working fine, did a full wipe and updated to LeeDrOiD 9th January on my phone and found that if my phone screen was on for too long it would reboot. This also happens when i play games, web browsing or during phone calls. i will get around 10 reboots a day. I just switched Roms to ROMeOS3D. thought that might have changed things but still get the same thing.
I found that if my screen was on for longer than around 25seconds and wasn't doing anything(didnt touch the phone) it would freeze and then reboot. If i put the phone on standby no problems but i cant keep turning off my screen every time i have a phone call or every time i put my phone down. web browsing gets frustrating!
Any help would be great! thanks in advance XDA!
So still having this problem but now just happens less and doesn't reboot just turns off.. i have learnt to work around it a little. when i get phone calls i turn off the screen and i make sure i turn off the screen when i put my phone down. but still!! this is retarded!
So now when i go to work and put the phone in my pocket it will turn off. i only realise when i need to check the time.
anyone have any similar problems at all might help?
Have you tried to go to a stock rom? Just to test to make sure it isn't hardware related.
Hey Guys
thought i would update. last night tried out all of the ICS roms out and surprisingly my reboot issues went away. Flashed back to 3 other roms and reboot problem came back. i dont know what it is but the ICS roms fix my reboot issues.
so now Im using the [ROM/WIP/DEV] EVO 3D GSM/CyanogenMod 9 Unofficial v1.2 [ICS 4.0.3] 17.02.201 and no problems. obviously some glitches here and there. but sms, phone calls & internet work so im a happy.
Reaper Thanks for your reply. i did go back to stock and everything was working fine. so its not hardware related. however thanks for your reply. much appreciated!
sabaselection said:
Hey Guys
thought i would update. last night tried out all of the ICS roms out and surprisingly my reboot issues went away. Flashed back to 3 other roms and reboot problem came back. i dont know what it is but the ICS roms fix my reboot issues.
so now Im using the [ROM/WIP/DEV] EVO 3D GSM/CyanogenMod 9 Unofficial v1.2 [ICS 4.0.3] 17.02.201 and no problems. obviously some glitches here and there. but sms, phone calls & internet work so im a happy.
Reaper Thanks for your reply. i did go back to stock and everything was working fine. so its not hardware related. however thanks for your reply. much appreciated!
Click to expand...
Click to collapse
Glad it wasn't hardware man Sometimes stock is the way to go to confirm a hardware issue of just software or rom issues
Alright, so first off I've had a few phones which I have rooted and modded to the extreme. Got a great deal on a e3d and came over.
Saw that i had hboot 1.50 and *tear*, however I followed the directions to a T and unlocked the phone, installed recovery, and threw on some well known mods.
MeanROM
CleanROM
Virus ROM
etc etc
Anyway, in all of the ROMs the camera is distorted, and when you try to use 3d it comes out greenish pixelated and crashes. When you take a 2d picture you can't see what you're pointing at, but when you click it takes a picture but well...see attachment.
Now here's what i have tried:
Re-wiped ROMs several times.
Installed Stock Kernals, and every kernel I could find.
Used the Flash app, used adb reboot-bootloader and then booted into recovery to flash roms, and most recently I re-locked the phone and used the RUU updater and Unrooted and installed stock back on phone.
STILL having same problem with camera.
So I'm asking anyone who'd like to help please, because if I can't get it working I'm taking it to sprint hopefully they'll replace it.
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
wassti said:
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
Click to expand...
Click to collapse
Already tried unrooting and flashing RUU. Still nothing....
Edit: I tried a factory recovery and no dice.
I'm going to try re-rooting and sending the camera file to the phone. Maybe it got corrupted?
Still open to suggestions.
Nope....
Sent from my PG86100 using xda premium
Ok so camera is clearly hardware issue. I relocked and factory reset. Camera still didn't work, today I clicked camera to show a friend. I had a twenty and accidently rubbed it on the screen and magically a picture appeared but it was split. I took a picture and boom it works. I'm going to mod it again when I get home, and I'll document the results, need to find out what happened.
Sent from my PG86100 using xda premium
It's a software issue. I am going to attempt to flash the kernel again and see if I can get it to work, anyone want to give me some tips?
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
RavenFB said:
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
Click to expand...
Click to collapse
Mine was actually a hardware issue, it was coincidental that the camera stopped working when I changed roms. Anyway, I have a refurbished phone on its way and hoping for hboot 1.4 I doubt it though.....
Although I'm interested in explanations or theories as to what happened and why, this is more of a story than a question...
Like most of us, I've had this phone for over 2 years, and I've been running / testing / messing with a variety ROMs for a long time... My "daily driver" recently has been from the cm10.1 nightlies (updated every week or so).
I saw the March 16 availability of BAKED blackbean, and thought I would give it a try... Being lazy, my initial flash was "dirty" after clearing only the cache partition and dalvik. All looked good on boot, but I soon noticed the infamous "phantom key presses" that usually only occur in very low signal areas... This was happening even though I could see 3-4 bars of signal. 3G data was working to some extent.
I dialed *228+ to reactivate (not technically sure when it's a good idea to do this - I once heard it should be done whenever a new kernel is installed, but it rarely seems necessary). But, the call failed to connect... I rebooted to recovery, full wipe, reflashed, same issue. Reflashed back to "stock" cm10.1 (3/15 build - why does this feel like "stock" these days . Still no outgoing call capability and some phantom key presses. Couldn't send SMS messages either.
ODIN time - back to (truly) stock GB EH03. Still couldn't call to activate. My wife's fascinate, from the same room, could make calls and send texts, etc. so I mostly ruled out coincidental VZW network issues.
I went to VZW.com to "deactivate" my fascinate temporarily to a new phantom device and reactivate (an old trick), but VZW wanted me to choose a new data plan first and said I wouldn't be able to go back... So I called VZW tech support and got them to re-provision the phone from their end, and we finally got things working again only after using the EH03 stock function to factory reset (Settings --> Privacy --> Factory Reset), which kicks off an activation wizard on the next boot.
The VZW 2nd-level tech guy then called me, traded SMSes and verified I could call out to one of their test numbers... At this point, I seriously thought about staying on stock GB (or perhaps GeeWiz 2.9 - which is good stuff .
Anyway, now I'm back on cm10.1 with my usual data partition all nicely restored and everything is hunky-dorry. For a minute there I thought this old device may have been showing signs of old age and was about to die. But it seems good-as-new (better than new actually - given CM10.1 .
So, any ideas of what happened to my phone in what seemed to be the normal life of a flash-junky? I don't blame BAKED blackbean (no similar tales in that thread), although my dirty flash of that ROM coming from CM10.1 was where the problem started for me.
When should one really reactivate their phone via *228? How often is it necessary to update "roaming" capabilities?
When will the Galaxy SIII refurbs start showing up on VZW.com (I was contemplating my best replacement option there for a few minutes - why spend $200 on something new when you've got a perfectly good Fascinate)?
Very interesting story. Since I too am a Flash Junky. Hope nothing like this happens to me
Sent from my SCH-I500 using xda app-developers app
I haven't dialed *228 in 2 years lol I don't really see why you should have to
Sent from my SCH-I500 using Tapatalk 2
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
FistFull95 said:
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
Click to expand...
Click to collapse
The problem might occur because of memory which one of my friend had earlier. Can you tell me how long copying files into phone storage takes?? Do you feel like ROMs are geting installed slowly than previous, slow copying of files?
ASOP Roms like CM never come with baseband. they use the same baseband that you already have in your phone. Only Stock based comes with baseband in their firmware. Sometimes(not most of the time) it can be if you are using different baseband than the one of the firmware, like if you have 4.1.2 and installed baseband of older version like of 4.1.1 but this is exceptional..
Thanks for your reply!
I don't think the internal sd has gotten slower tbh. I tried to copy an 2gb dummy bin from the extsd to my infernal sd, which copied with an average speed of 9mb/s.
I have tried experimenting with different TW based roms in the past, so I might still have a wrong baseband / ril. Is there a way of checking this?
Sent from my GT-I9300 using XDA Free mobile app
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband