This post pertains to the SOKP MS3 Release for the Evo 4G LTE - This Thread here - http://forum.xda-developers.com/showthread.php?t=2739621
however because I am able to flash and repair my phones on my own and have been for years and do not post a million questions on these forums everytime something doesn't go as planned, I can not post this there. Maybe if a mod could move it, thanks.
-----
With that being said, this isn't a "O i'm stuck, someone remote connect to my phone and fix it" post.
I wanted to pass along feedback from the MS-03 release yesterday.
Flashed SOKP-MS-03-KK444-KTU84P-20140709-jewel.zip late last night:
Rom looks great, super fast.
This release had the gapps included, did not have to flash gapps separately.
I did notice after flashing and rebooting, it seemed to go into a boot-loop at least twice; It started the boot animation, restarted, came up again with boot animation, went to starting up apps, rebooted again and then came up just fine. I did not have to touch the phone during this process, I assume this just had something with first time use.
WIFI seemed to work fine, data was working ok (can't comment about LTE, I would have to drive a couple blocks over to check)
The only thing I noticed that is a no go for me is the ever so evident internal storage problem - I won't mount the internal SD card and Camera FCs. Gallery FCs and says no external storage.
Flashed back to RC3 and it's working fine so far. I will sit on this a few days and see how it reacts. Hopefully the storage bug can get ironed out of the milestones. I am looking for a non-sense rom to go with, coming from Viper which worked ok, just became a little slow. Tried PA and had to many random lockups and FCs for my liking.
Thanks,
Steve
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
A little background, I've run Alien 4 for a few months with no issues whatsoever. About three weeks ago, CM7 (the stable atrix build Ba2TF), and shortly after I Flashed Neutrino 2.1GT (1.3), with the patch and assorted addons.
Within the last 1-2 weeks, my internal speaker began going in and out. I flashed 2.2 EE last week, and still had the speaker issues. In that last week, I've also been virtually unable to connect to a PC in any capacity. It's worked at random a couple of times, but that's it.
I reverted back to CM7 attempting to fix the issues, and no luck (this was before the charging issues).
Yesterday, I flashed Faux's Unified CM7 024_r2, thinking maybe it was just wigging out on me. No luck there, so I reverted back to a stable (with the exception of the speaker issue) restore.
Now, my phone will not charge, except when the demon inside it wants too. I've done a factory restore, manually formatted everything but the SD card via CWM, and restored back to the supposed stable CM7 restore. I've tried Neutrino 2.1 & 2.2, CM7, and am currently downloading the MFBSR stock restore.
If it helps, I'm using Rom Racer's current recovery.
Any thoughts here? I'm still pretty new to all this. Could the overclock to 1.3 (Neutrino 2.1GT) have done some damage? My phone was in an otterbox defender. Is there anyway to tell that you guys can think of?
Dumbass me procrastinated on getting my usual Square Trade insurance, and they've now stopped insuring phones past 60 days of purchase. I've had this one since June.
Sorry for the long windedness. If I missed anything, please let me know.
From a powered off state, when I plug the phone in to the PC, it turns on. I'd think this would mean it's seeing something via the data cable, right?
Anyone?
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?
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
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