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.....
Related
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
I rooted my phone about two months ago and didnt have any problems at all. Used HTC's website and loaded cleanrom reborn 1.1 and the kernel that came with it is 2.6.35.13-g277012f
Recently, about a week or two ago, I noticed the camera starting to fail. It occasionally wouldnt load in 2D mode, just give me a black screen. Now, it rarely loads at all. Either the whole screen is black or it brings up the camera app (stock, instagram, fb, all the same) but the part of the screen that would show the picture is black. When I turn it to 3D mode the screen freezes, then flickers, and quickly closes to the home screen and still flickers for about 3 seconds then is fine.
My questions are this, could this be caused due to needing an update, a new ROM or new hardware? Also what do you all recommend as far as the best ROM for taking pictures?
And on an unrelated note, does anyone know a good ROM that supports 4G hotspot instead of it just automatically switching to 3G??
Thanks
As for the camera failing sorry to here that but you can down load the amaze camera from the dev section and they have all different version of it and its for both CDMA and gsm
Sent from my HTC EVO 3D X515m using xda premium
That sounds like a software issue.. Might be the rom or the kernel.
Are you on ics?
Sent from my EVO 3D S using xda premium
My camera just started acting up also, I went ahead and wiped everything and installed bone stock rom (rooted only) and camera is still messed up.
When I use the main camera it works fine, when I switch to front facing camera - it stays on the main camera and just inverts the image
Is this a hardware or software issue? I am guessing it is the hardware
Let me know what you guys think.
Heaterz16 said:
My camera just started acting up also, I went ahead and wiped everything and installed bone stock rom (rooted only) and camera is still messed up.
When I use the main camera it works fine, when I switch to front facing camera - it stays on the main camera and just inverts the image
Is this a hardware or software issue? I am guessing it is the hardware
Let me know what you guys think.
Click to expand...
Click to collapse
Nobody has seen this issue???
Try running an ruu.
#Root-Hack_Mod*Always\
laie1472 said:
Try running an ruu.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
If am S-off would I have to re-root if I tried that?
Yup. Running an ruu removes root. Just don't run the hboot1.5 ruu if your on hboot1.4. It will save you a headache.
#Root-Hack_Mod*Always\
I would reflash the rom before ruuing
Sent from my PG86100 using Tapatalk 2
Nah. Just run the ruu. Make sure your battery is over 85% imo things go a lot smoother.
#Root-Hack_Mod*Always\
I really do appreciate the replies, but not sure I am willing to run the RUU and re-root since it is a pretty high likelihood that it is a hardware failure since I went back to completely 100% stock (only rooted) ROM. Torn on getting a replacement and having to deal with the Hboot 1.5 mess just so I can use the face unlock feature in ICS or stick with what I have an no FFC.
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Not positive but fc'ing cam is a sense 4 bug.
Sent from my ADR6425LVW using xda app-developers app
adamsaur said:
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Click to expand...
Click to collapse
If you have face detection on, it could crash the camera.
adamsaur said:
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Click to expand...
Click to collapse
The camera seems to be an issue. Some say to uncheck face recognition and then it works...I don't know. Mine works when I've needed it. Some also have had luck with 3rd party apps. Eventually it will get fixed. You don't have to 'fall back' to a desensed rom, there are several good roms out there not using sense 4.0.
Update the firmware..? Well, there is a post today hinting at something coming in the next two weeks. Perhaps the long awaited OTA. So you should update to the new firmware. Either with the update or with one of the leaks. NilsP has some instructions on running the RUU in post #3 of one of his ROMS...the sense 4 one I think. Check it out if you want.
That's odd. I've ran all the sense 4 roms here and the only one that gives me problems is one xxx but is rare.
Sent from my ADR6425LVW using Tapatalk 2
I'll have to check the face recognition, I wasn't using it but it's worth a shot.
Anyone know of any hq camera apps to use if the default fcs again?
FYI - Since you're s-off, you don't need to flash a whole RUU to get the latest firmware, take a look at this thread - http://forum.xda-developers.com/showthread.php?t=1614366&highlight=firmware
Since you are running ICS on GB firmware, if you update, you need to flash the New firmware patch afterwards to revert what the old firmware patch does.
It won't help with your camera most likely cause as others has mentioned, it's a issue with Sense 4 roms for now, this makes it easier to upgrade though.
thanks mjones finally updating the firmware
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?
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