I "flashed" the stock ICS leak 3.11.605.22 and it worked awesome for like 2 weeks. Today I restarted the phone and it never came back on, it never booted up no matter what I did. I now have the replacement rezound and want ICS again, was this just a freak accident or did the RUU mess up?
Did you try a different battery? Id say the ruu had zero to do with it.
I certainly will not flash the leak on my phone. Its working too perfect to risk messing with uncertainties.
Personally, with all the reports of bad devices I would just wait a week or so to make sure your new phone doesn't have any issues before flashing anything.
I really wonder how many people blame the leak for bad phones. Seems like HTC had bad quality control when it came to the rezound. I feel lucky to have had no problems with my phone after reading all the reports of returns and heating issues.
I have had the ICS leaked RUU on my phone since the day it came out and have not had the first problem with it. The RUU didn't mess your phone up, a dead or faulty battery probably did.
It wasn't the battery, the Verizon rep tried a new one and he also tried both batterys in the new phone and they worked fine in the new phone.
The phone that messed up, I had for about 3 weeks or so with no problems. Then I used the RUU and it worked flawlessly for about 2 weeks, then BAM! now I have a brick.
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
tspderek said:
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
Click to expand...
Click to collapse
See I never had problems with the RUU itself. The radio worked tons better than it did before the RUU.
Now my new rezound won't read my sd card. I tried reformatting still doesn't read it.
For those of you who have flashed the RUU and are having problems, try flashing it a second time.
I paid particularly close attention during the flashing process and hand verified the versions of subsystem I could after the update. It turned out that the first flash only applied the hboot, kernel/boot, and a few minor systems successfully. After a second flash, everything applied correctly.
For instance, a number of people reported that the radio versions didn't change from the update, when in fact the radio changed significantly (currently running @ 1.22.10.0310r, 1.22.10.0308r).
After the update, I've found my battery life is significantly better than the GB kernels (I used BAMFs modified, Incredikernel and the Stock OTA). My reception is noticeably better, but I can't give a qualitative judgement other than that. And, most importantly, the phone is easily 100% more responsive. I used the stock OTA and BAMF 1.0.2 on and off for a while and unless I repeatedly killed background tasks my home screen (ADW Launcher EX) would stutter and lag, games would periodically slow down, web browsing would periodically freeze, etc. Now, my phone consistently has 300MB of RAM free (before it was usually less than 100MB). The leaked RUU is the best thing to have happened to the Rezound so far.
Note: despite my complaints above, my phone was always more usable than my OG Droid and my wife's dinc2, I'm just giving a comparative description.
Related
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
So I am a proud owner of the Thunderbolt now and I am loving this phone a lot. I’ve moved over from the Sprint EVO. I was rooted since day 1 with that phone. I ran CM7… and while my overall phone and speed test were faster than the stock phones in the house… I still seemed to have constant issues… be it from the phone itself or the network.
Of course I can’t leave well enough alone with this phone. I wanted to put Gingerbread on it (it still has 2.2 WTF?!) and I wanted to put Sense 2.1/3.0 on it. So I successfully rooted (WOW that was easy) and installed clockwork recovery. I decided on SHIFTS3NS3 V1.4F as it seems to have exactly what I want (I kind of don’t want to go back to CM7, everyone claims they have no signal issues but I am sure they do, especially when my Sense loaded Evo could get 4G where CM7 could/would not).
So BEFORE I rooted or did anything, I did several speed test throughout my home and work. Smooth scaling and great speeds. After rooting and installing Shifts3ns3, I started running test. My speeds dropped… and now I was seeing “skipping” with the speed test (gets to a point, stops, drops, stutters going back up, drops again, etc). So I get to work this morning and the speed test is doing the same here. I did a nandroid backup of my stock set up last night before I installed the new ROM… restored it this morning… and ran the test at work again… lo and behold I am getting faster speeds and no stuttering.
So perhaps a radio issue? I noticed there are Froyo radios and GB radios (http://forum.xda-developers.com/showthread.php?t=1048128)... When installing the GB ROM does it update the radios? Was I running Froyo radios on a GB rom and is that bad? Should I try upgrading to the latest GB radios and run test again? Does any of this Rom switching/radio switching affect the simultaneous voice and data ability (that’s actually huge for me and the main reason I got this phone)?
I appreciate any help. I’ve been a XDA board reader with EVO since 11-2010… so while everything is familiar to me… this all seems different with the Thunderbolt.
First off I would upgrade to the latest radio. Although these are *beta* radios, they work much better than the stock radios.
Second, after installing the latest radio try, Bamf 2.4.1. Just like you I like staying close to stock, but like extra elements with my ROM. To me Gingeritis is just too far from stock, plus the Carousel home screen is a pain in the ass. Bamf 2.4.1 is just stock with sense 3.0 weather and lockscreen, and without the location icon in the status bar.
Also, my speedtest on Bamf 2.4.1 was a straight shot. No drop offs what so ever.
And, of course this is all just my opinion but I strongly believe that Bamf 2.4.1 is what you want.
miketoasty said:
First off I would upgrade to the latest radio. Although these are *beta* radios, they work much better than the stock radios.
Second, after installing the latest radio try, Bamf 2.4.1. Just like you I like staying close to stock, but like extra elements with my ROM. To me Gingeritis is just too far from stock, plus the Carousel home screen is a pain in the ass. Bamf 2.4.1 is just stock with sense 3.0 weather and lockscreen, and without the location icon in the status bar.
Also, my speedtest on Bamf 2.4.1 was a straight shot. No drop offs what so ever.
And, of course this is all just my opinion but I strongly believe that Bamf 2.4.1 is what you want.
Click to expand...
Click to collapse
Reading up on their site now
Quick question, since I am on page 10 and not seeing this answer... what is the difference between ADR and non ADR? He mentioned on page one that its "Adrynalyne. Its what I made according to my own wants"... but I am not sure what that means LOL. Only reason I am concerned is that there still seems to be a sense 3.0 lock screen bug that someone said is a known bug and to flash the non ADR version.
miketoasty said:
First off I would upgrade to the latest radio. Although these are *beta* radios, they work much better than the stock radios.
Second, after installing the latest radio try, Bamf 2.4.1. Just like you I like staying close to stock, but like extra elements with my ROM. To me Gingeritis is just too far from stock, plus the Carousel home screen is a pain in the ass. Bamf 2.4.1 is just stock with sense 3.0 weather and lockscreen, and without the location icon in the status bar.
Also, my speedtest on Bamf 2.4.1 was a straight shot. No drop offs what so ever.
And, of course this is all just my opinion but I strongly believe that Bamf 2.4.1 is what you want.
Click to expand...
Click to collapse
Gingeritis doesn't have a carousel home screen. Gingeritis3D does.
meteron said:
Reading up on their site now
Quick question, since I am on page 10 and not seeing this answer... what is the difference between ADR and non ADR? He mentioned on page one that its "Adrynalyne. Its what I made according to my own wants"... but I am not sure what that means LOL. Only reason I am concerned is that there still seems to be a sense 3.0 lock screen bug that someone said is a known bug and to flash the non ADR version.
Click to expand...
Click to collapse
The ADR version uses elements of sense 3.0 while the normal version is basically stock. You want the adr version.
meteron said:
So I am a proud owner of the Thunderbolt now and I am loving this phone a lot. I’ve moved over from the Sprint EVO. I was rooted since day 1 with that phone. I ran CM7… and while my overall phone and speed test were faster than the stock phones in the house… I still seemed to have constant issues… be it from the phone itself or the network.
Of course I can’t leave well enough alone with this phone. I wanted to put Gingerbread on it (it still has 2.2 WTF?!) and I wanted to put Sense 2.1/3.0 on it. So I successfully rooted (WOW that was easy) and installed clockwork recovery. I decided on SHIFTS3NS3 V1.4F as it seems to have exactly what I want (I kind of don’t want to go back to CM7, everyone claims they have no signal issues but I am sure they do, especially when my Sense loaded Evo could get 4G where CM7 could/would not).
So BEFORE I rooted or did anything, I did several speed test throughout my home and work. Smooth scaling and great speeds. After rooting and installing Shifts3ns3, I started running test. My speeds dropped… and now I was seeing “skipping” with the speed test (gets to a point, stops, drops, stutters going back up, drops again, etc). So I get to work this morning and the speed test is doing the same here. I did a nandroid backup of my stock set up last night before I installed the new ROM… restored it this morning… and ran the test at work again… lo and behold I am getting faster speeds and no stuttering.
So perhaps a radio issue? I noticed there are Froyo radios and GB radios (http://forum.xda-developers.com/showthread.php?t=1048128)... When installing the GB ROM does it update the radios? Was I running Froyo radios on a GB rom and is that bad? Should I try upgrading to the latest GB radios and run test again? Does any of this Rom switching/radio switching affect the simultaneous voice and data ability (that’s actually huge for me and the main reason I got this phone)?
I appreciate any help. I’ve been a XDA board reader with EVO since 11-2010… so while everything is familiar to me… this all seems different with the Thunderbolt.
Click to expand...
Click to collapse
i came from the evo too so welcome. IMO the reason people are having soo many data issues is not from the radios but from the 2.3.5 build that was meant for the nexus s phone. 2.3.4 doesn't have those kinds of problems. just my 2 cents!
fixxxer2008 said:
i came from the evo too so welcome. IMO the reason people are having soo many data issues is not from the radios but from the 2.3.5 build that was meant for the nexus s phone. 2.3.4 doesn't have those kinds of problems. just my 2 cents!
Click to expand...
Click to collapse
I'm inclined to agree.
loonatik78 said:
I'm inclined to agree.
Click to expand...
Click to collapse
if i could find a decent 2.3.4 aosp build id jump on it. the only thing keeping me from sense is the low volume issues.
fixxxer2008 said:
if i could find a decent 2.3.4 aosp build id jump on it. the only thing keeping me from sense is the low volume issues.
Click to expand...
Click to collapse
Low volume in call? Geeze... I wish I could turn it down! Gingeritis3D is blaring loud. I never use it more than half way up.
Thanks everyone for the responses!
I guess I am just scared to do anything to mess up my phone. I trouble shot and tinkered with the Evo so much so often.
Right now the phone works. And works great. I just wanna help the battery life some... and remove Verizons bloatware.
It seems the Thunderbolt handles radios differently depending on the build? With the Evo I would just flash a radio and I could bounce around from sense to AOSP, froyo to GB, and it wouldnt matter. The thunderbolt has MR2 radios... Froyo radios... GB radios. So my last question here is... right now I am on stock. If I go to a GB based rom, do I flash the radio first? And if I go back to the stock rom, do I flash the MR2 radios first (my phone updated to 1.70.605.0 while it was being set up in the store) then flash back to stock? Basically do the radios persist throughout the builds and I flash them according to what ROM I am using?
Thanks again.
meteron said:
Thanks everyone for the responses!
I guess I am just scared to do anything to mess up my phone. I trouble shot and tinkered with the Evo so much so often.
Right now the phone works. And works great. I just wanna help the battery life some... and remove Verizons bloatware.
It seems the Thunderbolt handles radios differently depending on the build? With the Evo I would just flash a radio and I could bounce around from sense to AOSP, froyo to GB, and it wouldnt matter. The thunderbolt has MR2 radios... Froyo radios... GB radios. So my last question here is... right now I am on stock. If I go to a GB based rom, do I flash the radio first? And if I go back to the stock rom, do I flash the MR2 radios first (my phone updated to 1.70.605.0 while it was being set up in the store) then flash back to stock? Basically do the radios persist throughout the builds and I flash them according to what ROM I am using?
Thanks again.
Click to expand...
Click to collapse
The latest radio's available will work with all ROM's out right now (Including the latest Froyo ROM's).
If I remember correctly you should be okay to just flash the ROM (No need to flash the new radio as MR2 works with both GB and Froyo).
The Radio's persist through everything except a RUU or PG05IMG.zip flash (Depending on what you are flashing of course).
miketoasty said:
The latest radio's available will work with all ROM's out right now (Including the latest Froyo ROM's).
If I remember correctly you should be okay to just flash the ROM (No need to flash the new radio as MR2 works with both GB and Froyo).
The Radio's persist through everything except a RUU or PG05IMG.zip flash (Depending on what you are flashing of course).
Click to expand...
Click to collapse
OK so it IS like the Evo then. The radio thread isnt stating that they are Froyo/GB radios... but where the radios got pulled FROM. I was totally reading it wrong.
Thank you for the clarification!
Hi,
I have been having a having an issue with my Evo3D since I got this replacement phone and I am trying to figure out if it is the phone or the software/firmware.
Simply put,
when the phone's screen is off (asleep and locked), sometimes when I press the power key to wake it up and then swipe to unlock, about a second later, the screen goes black, then I get the HTC splash screen, ie it does a full reboot;
at other times, the phone will be in my hip case or in my pocket, I won't touch it or do anything to it and the thing will reset itself, I am fairly sure this occurs when it is scanning for a tower or when it is changing to/from roaming as this occurred mainly while I was in the middle of nowhere this past weekend; and
this can happen immediately after a phone call, or right after I turn off/on one of the wireless subsystems, but this is less common.
I am unlocked, I downgraded using the bricking method, I have used both Freeza's and TreVe's firmware packages, I have used the 2.17 stock RUU twice.
I have run Mik's 3.6 rom, D3rp's 3.6 rom, dropzeroc's ROM, MeanRom's ICS and gingerbread ROMs, and some others and I still get this problem. I have also tried multiple different batteries. I always superwipe between ROMs.
Because I have used so many different ROM's, I am fairly sure the issue is either firmware or hardware.
Anyone have any thoughts before I send this back to Sprint for 2nd replacement because I REALLY don't want to have to brickroot ANOTHER phone. Took me 8 f***ing hours to get this one done.
Thanks,
Osiris
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Moonbloom said:
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Click to expand...
Click to collapse
Which radio would you use if you want to run ICS Sense 3.6? I guess I am confused though, wouldn't the 2.17 radio jive with the 2.17 firmware (radio 1.06 should be fine with 2.17 firmware right?)
I had the same issue. My phone would randomly reboot on screen on or sometimes i would check it and would see it restarting.
I went back to full stock and still had the same issue.
Took it to sprint and they get me another replacement.
I suggest you take it back.
I am trying the radio suggestion but thank you for the suggestion and I will probably take that advice if it continues having issues.
Well, I am not sure what to say.
Like any BAD troubleshooter, I changed two factors at once.
I switched to PKMN and downgraded the radio to .97
Well, it hasn't reset itself since.
Who the hell knows why either thing would fix my issue.
Downgrading the radio to .97 (from the 2.08 ruu) when everything else is 2.17 ruu makes no sense.
Going to Sense 4.0 ROM makes even less sense as a fix.
Anyone have a clue?
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