Related
You know em, you love em, random semi-reproducible problems!
I have been playing with my phone and enjoying the freedom of root access every since the original 2.2 OTA root method was posted (the downgrade unrevoked method). Its been great, but I started to have an annoying reboot issue that popped up every now and then. At first it was annoying, but now it is getting worse.
It SEEMS like it is temperature related. It started happening while the phone was charging, 4g was on, and wireless tethering (pre8) was running. First the connection between my computer and the phone would drop, then I'd reconnect, surf for another 5 mins or so, and the phone would reboot. Battery temp was reporting ~44C. After I let the phone cool down everything was fine.
I found that if I didn't have the phone on the charger or if I put the phone (battery side down) on top of a cool metal surface, the problem would not arise.
But then it started happening more often and under circumstances where it had previously not had any problems. Things like turning off my alarm, answering a call, playing alchemy. Under those cases, the battery was sometimes warm, but usually cool.
Last night it entered a reboot loop, where it just returned to the white HTC EVO screen over and over and over. It eventually turned off and the green light began to flash. I could not boot it up until I removed the battery and cooled both the phone and battery down. It was charging with a file downloading over 3g.
The problem is defiantly getting worse.
--------------------
I know that people are going to fire at me to wipe and reinstall (like in all the other threads) but that is the craziest part: I have. Many times. When it started to happen I thought it was the ROM, so I would change ROMS when it happened, but now I realize the problem is independent of the ROM in use.
I have used (and hit rebooting issues while the batter is hot and cold)
Stock (rooted) 2.1 and 2.2
Ava V5, V6, and V7
Fresh 3.2 (and a previous version, I don't recall which)
BakedSnack 1.6 and 1.7
Evo Zone 8.29
Vaelpak 1.3 and (I believe) 1.2
A couple of Virus' ROMs
I have used the stock 2.1, 2.2, and 3.2 HTC kernels and King's #s 6, 8, and 5, all with the same problems.
I even nandroided to backups that I had previously NOT had the issue with, only to immediately reboot. It really looks like software is not the issue, but I'm not sure.
As you may gather from this, it has been an on going issue for quite some time. I always do a full wipe (all caches, dalvik, et all) between ROMS. I'm out of ideas, do I need to S-ON and OTA then return this bad boy to sprint? Any ideas?
EDIT
Forgot to add, I am using ClockWork recovery, and flashing ROMs manually (through recovery, not a ROM manager app)
Quick bump for interest and posible solution. I'm pretty sure it's a hardware issue, but I just want to be sure.
Even though I'm always going on about how clockwork always works fine for me, and wipes everything correctly, I'll be the guy here to suggest trying to flash with amon ra a few times. If you still run into issues, I'd say that your battery is borked. But before returning the whole thing, maybe pick up a cheap extra battery off of ebay, and see how it works with that?
Just so I am clear on what to do, if I want to return the phone for service, I need to run the S-ON tool from unrevoked, then accept the OTA and I should be good to take it in, right?
Yes flash s-on then run RUU
i am having exactly the same issue
i've been on cm6 for over a month and it started about 2-3 weeks ago, at first i thought it was the temperature too but recently it started rebooting at completly random moments. I flashed baked snack yesterday and put a new battery in, same thing, random reboot
i flashed deoxed newest update with no mods today to see if that would fix the issue, 3 minutes after i did, i was signing in to my google account - reboot
turned the phone on, and 1 minute later reboot and loops....
any ideas?
using RA recovery btw, wiped everything before i flashed.
It's the HARDWARE
Guys,
Just thought I'd share a little of my experience with this phenomenon.
I had a HW003 Nova since the release of the Evo. I started experiencing random reboots every so often about a month or so later.
These progressed regardless of what version of Android, or which rom, or which kernel, bootloader, OTA update, S-ON, S-OFF, Bone stock or rooted.
After barely managing to get the phone back to it's factory state, I replaced it no questions asked on my second visit to Sprint repair center.
My refurbished replacement (Also HW003) was fine for a whole 5mins before it started doing the exact same thing. I gave it back to the technician, and put in the order for my second replacement. As per the advice of the technician, if my next replacement has any problems at all, I'm supposed to call Sprint customer service directly in hopes of a longstanding solution (read: Ask for a brand new phone)
Not trolling or starting ****, because I love my Evo, but let's be realistic.
These phones are built like garbage. At least the original crop of them is.
They use some good parts, but they are manufactured in a cheap manner.
Probably in cheap factories using cheap labor, and cheap materials.
While not every Evo is junk (my girlfriend hasn't had any problems with her's in over 3 months) you have to figure that one out of every few thousand is probably going to have some kind of defect, be it light leakage, bad screen grounding, broken USB connector, or even the infamous nonsensical, irrational, arbitrary reboot/power-cycle.
Sounds like what was happening to me too. I just took it to repair center and after a couple trips they replaced it. First they put a new battery in, said they couldn't reproduce the reboot but in three minutes I did. After that they ordered a new one.
In the beginning it was so random and appeared to be a heating issue too, then it just got worse and worse. Seemed like I could use the phone without issues if I wasn't taxing the phone too much but it progressively got worse and got to the point of it being maddening. Then it was hanging on splash screen and boot looping. Uprooted and took her in. Sounds like thats your best bet. I tried different ROMs, stock, etc etc.
Just take it in after doing what you need to do. Good luck.
SWYPED from my SUPASONIC
Alright guys, I'm not exactly new here, I've been a member for awhile, but I had an iPhone 3g S for awhile and had no need of any help. I have since switched to Sprint and decides I was getting the HTC EVO 4G...go figure, I buy it no more then a ask before it takes a price cut of $50. Oh well, no big deal. Moving on to my problem, I've had it for about and overall, the phone is decent. Much like you guys, I want my phones to keep up with me and although it tries hard, it just can't. Recently I've been having two problems. The first one, a random reboot, which seems to be caused by heat/charging/overuse issues. This, I have found, is a very common issue with the EVOs and regardless of the inconvenience, its not serious, yet.
My second, albeit more troublesome, problem, is the rebooting loop, again seems to be a very common issue with the EVOs. Mine, however, seems to not fit the description. From what I've been reading, the reboots are typically on the original models, where mine is over a year newer. Another difference, my phone loads everything up, completes a sync, then reboot again. The only time it gets stuck in a reboot loop is when the phone, whether by itself or by my own doing, reboot AND has an SD card in there. I can remove the SD cars during the loop and everything works perfectly fine...except it takes me about 3 minutes to remove my SD card since I have an Otter box defender case on it.
My EVO is NOT rooted, has all current updates installed, has the OEM SD card...OEM everything actually, and all apps are installed on the phone now. When it first started happening, it was shortly after I downloaded an app update from the store for an app that was on my phone. I figured the download must have corrupted a file, the phone failed to load it, then reboots. I would uninstall the apps I thought to be the culprits, reinstated the SD card, everything worked, until a few minutes ago, when it reboot looped on me again and I realized I no longer have apps on my SD card...what do I do? Phone works perfectly fine without the SD card installed, but I like being able to take pictures and saving them. I don't even have the option to save them locally, which is bull.
Just a quick reminder, I have searched the forums, I've also searched al of Google with no revolting loops similar to my SD card issue appearing. I have a lot of pictures on my SD card currently and have another one to try, but I'm not sure how long I'd have to wait before the boot looping happens again. Any insight would be greatly appreciated and if I happened to have missed the post where there was already a fix for this, I'm sorry.
P.S. I'm sorry for any grammar or spelling mistakes, the autocorrect on Android isn't near as Goo as iOS. I love Android, but if I have to get a new phone, I'm going back to the iPhone.
Hey guys, mainly just a bump, this is a fairly big issue and I'd like to atleast know what you guys think. If it happened to you, what would be your first course of action. Is there maybe another thread that covers this that I missed? Should I just yell at Sprint and tell them I want a new phone? Is there more information I should provide? If so, what? Thanks for any help.
I would suggest running an RUU, first, I am on my phone so I don't have a link. Other than that, I would say take it in to the store
Sent from my PC36100 using xda premium
Found the latest RUU for you:
http://www.filefactory.com/file/cd5....15.00.0808_NV_2.15_release_209995_signed.exe
Download it, click on it. The instructions are self-explanatory
mrplow123456 said:
Hey guys, mainly just a bump, this is a fairly big issue and I'd like to atleast know what you guys think. If it happened to you, what would be your first course of action. Is there maybe another thread that covers this that I missed? Should I just yell at Sprint and tell them I want a new phone? Is there more information I should provide? If so, what? Thanks for any help.
Click to expand...
Click to collapse
you said you've had the phone "about a " but then you didn't fill in the time frame. So either you're Christopher Nolan or i'm assuming you meant a short period of time. if that were the case - in all honesty, i would just exchange it out.
you haven't rooted, it's all stock, you haven't really put much effort into it - why not just go swap it out.
that's what i would do anyway...
i got my evo pretty much at launch. i have a stuck pixel and the screen white issue - i was too lazy to return it and didn't want to wait for the exchange so i have just lived with it for 18 months. sometimes i wish i'd exhanged it, but i had already put quite a bit of time into rooting, tweaking etc. you haven't - so why not just start over?
And not to bash the iPhone - my wife has one - but after using the Evo i could never go back to using an iphone... just sayin
Any help here would be greatly appreciated.
My trusty Evo's USB port ripped off the PCB. It was a sad day. I did anything and everything with that phone. Amazing. So, I decided to buy a used Evo on eBay with a busted LCD but clean ESN. It came, looked as described, but it was remanufactured, I swapped in the front of my old phone (LCD, digitizer, front housing) onto the "new" one, booted it up, and all was well. For about 5 minutes. That's when I experience the first random FC. It kept happening, so I rooted it (Hboot 2.18 with this method), flashed some ROM (I have flashed so many now, I don't remember) and same thing.
Things I have learned:
This thing hates Mason kernels
I can't get tommytomatoe's "The Classic" ROM to even do a full boot.
ICS and CM7-based ROMs seem the best, but I still get random reboots, freezes, and FCs.
Things I have tried:
Reset Permissions - Things seem better after I do this, but after a few hours I get the same thing
Wiped everything, including the SD
I wipe everything but the SD, including the caches x3, before every ROM flash
I am currently running sharkboy0901's MokeeSharK, which is the most stable, but still get the same behavior
Does anyone have any ideas what to do from here, or do I just scrap this phone? I need to hold off for a few months to upgrade and am very sad that I have a bad Evo after having such a good one.
Xedroid said:
Any help here would be greatly appreciated.
My trusty Evo's USB port ripped off the PCB. It was a sad day. I did anything and everything with that phone. Amazing. So, I decided to buy a used Evo on eBay with a busted LCD but clean ESN. It came, looked as described, but it was remanufactured, I swapped in the front of my old phone (LCD, digitizer, front housing) onto the "new" one, booted it up, and all was well. For about 5 minutes. That's when I experience the first random FC. It kept happening, so I rooted it (Hboot 2.18 with this method), flashed some ROM (I have flashed so many now, I don't remember) and same thing.
Things I have learned:
This thing hates Mason kernels
I can't get tommytomatoe's "The Classic" ROM to even do a full boot.
ICS and CM7-based ROMs seem the best, but I still get random reboots, freezes, and FCs.
Things I have tried:
Reset Permissions - Things seem better after I do this, but after a few hours I get the same thing
Wiped everything, including the SD
I wipe everything but the SD, including the caches x3, before every ROM flash
I am currently running sharkboy0901's MokeeSharK, which is the most stable, but still get the same behavior
Does anyone have any ideas what to do from here, or do I just scrap this phone? I need to hold off for a few months to upgrade and am very sad that I have a bad Evo after having such a good one.
Click to expand...
Click to collapse
I'm new here so im not sure where to find things on here,except use the search,but anyway i know from experience,that if you partition your sd card,you might be able to resolve this issue your having mate,also try apps2sd method.Like i said sorry for not helping with links yet,until i get used to the forums,i know where nothing is,haha.
Thanks! I did partition the SD and upgraded to Ext4, to no avail. I guess I am stuck with a bad phone.
Sent from my PC36100 using xda app-developers app
I think you now know why the last owner sold it.
Best bet, do a full RUU for that phone, and start from scratch
Haha. True. You get what you pay for, and I am not naive enough to think there aren't risks in buying off eBay. I'll try the RUU and let you know. Thanks Hipkat.
So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..
plugging my phone into usb cable to laptop, driver goes to install: 'qhsusb_dload no driver found
looking this up in google just re-enforces my suspicions..
yeah dude your phone is now a doorstop. this happened to me once as a noob android "modder" as i was trying to install an rom made for the international version of the gs3 (i9300) onto my north american at&t gs3
(SGH-I747). luckily i was on warranty and got a new one for free. hopefully you are on warranty as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
20twins10 said:
So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..
Click to expand...
Click to collapse
Beanstalk 4.3??? Cause team chopsticks are saying there's a bug that can brick a phone maybe. So they suggest everyone wait before building or flashing cm based 4.3 roms.
****edit**** sorry ignore. Misread the first bit. You were on Beanstalk, nandroided back to pa, then tried liquid smooth. I got it now. Hope you figure it out!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
kj2112 said:
Beanstalk 4.3??? Cause team chopsticks are saying there's a bug that can brick a phone maybe. So they suggest everyone wait before building or flashing cm based 4.3 roms.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
BeanStalk 4.3 was yesterday morning. I had a hard time getting it to boot back up after wiping cache n dalvik. It was really unresponsive, holding buttons and releasing took forever to yield a result. So there was alot of battery pulling and buttons. I got pissed and just said **** it and left it alone and it booted up, I booted to recovery and switch back the Paranoid Android. There was a small handful of people in the thread all kinda saying the same thing, long delays and unresponsive..
My PA setup was stable, I've had it on for months.. I was in a flash kinda mood so I decided to try a different rom, something not 4.3 based.. So I downloaded the LiquidSmooth rom but it error'd during installing.. I wasnt able to restore, And when I shut it down it just seems I couldnt get it back up to do anything..
It could be a combination of events.. Just a minor bump in the road.. Not the first phone I had brick..
Eh.. Guess I get a new phone..
20twins10 said:
BeanStalk 4.3 was yesterday morning. I had a hard time getting it to boot back up after wiping cache n dalvik. It was really unresponsive, holding buttons and releasing took forever to yield a result. So there was alot of battery pulling and buttons. I got pissed and just said **** it and left it alone and it booted up, I booted to recovery and switch back the Paranoid Android. There was a small handful of people in the thread all kinda saying the same thing, long delays and unresponsive..
My PA setup was stable, I've had it on for months.. I was in a flash kinda mood so I decided to try a different rom, something not 4.3 based.. So I downloaded the LiquidSmooth rom but it error'd during installing.. I wasnt able to restore, And when I shut it down it just seems I couldnt get it back up to do anything..
It could be a combination of events.. Just a minor bump in the road.. Not the first phone I had brick..
Eh.. Guess I get a new phone..
Click to expand...
Click to collapse
Insurance wont cover it, TMobile is shipping one out under warranty protection.. Do they go back into the phones that are sent back and look at them or what??
Nah your good all they do is connect it to there program and restore it they have capabilities we dont lol
sent from my t mobile S4
20twins10 said:
So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..
Click to expand...
Click to collapse
Yeah dude that's a brick...sucks but no T-Mobile doesn't look into the device just basically do a higher form of JTAG an completely wipe the hardware to start over, or if it's real bad they just junk for parts and build somebody else a "refurbished" phone, there system makes the best dev look like a noob lol
Sent from my SAMSUNG-SGH-T989 using xda premium
soupysoup said:
Yeah dude that's a brick...sucks but no T-Mobile doesn't look into the device just basically do a higher form of JTAG an completely wipe the hardware to start over, or if it's real bad they just junk for parts and build somebody else a "refurbished" phone, there system makes the best dev look like a noob lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a laugh out of that, but I'm sure its true. With the amount of phones on the market, I'd love to know the percentage they take back in and replace.. It's gotta be astounding.. It's a small thorn in my side for a day and a half, but my phone should be here before noon. I just gotta go and find my rootkit folder and get it all ready
This is the 2nd phone I've wound up bricking. I didnt get my first true smart phone till October 3yrs ago. HTC droid incredible.. that phone was seriously tuffer then nails.. It was dropped so many times, i just stopped caring if it fell cause i knew it would be ok.. Went down a flight of wood steps into my basement during a call and didnt blink.. I wound up melting the back cover to the battery once, my daughters * i have twins* were destroying something and I had torch on looking for something. I wound up putting the phone down on a towel w/ torch on facedown.. I got busy cleaning what they messed up and by the time I remembered my phone I went to get it and it shut down as I picked it up.. It was extremely hot and around the LED you could see a ripple from where it melted. I pulled everything apart, let it cool off for like 10minutes and it booted right back up.. It bricked way later on, I was way more flash happy back then, then I am now. I'm pickier now, back then I was just trying anything..
This sII was bought in October of last year. But it's seen its number or battery pulls and restores.. Tomorrow we will follow up the same..
20twins10 said:
I got a laugh out of that, but I'm sure its true. With the amount of phones on the market, I'd love to know the percentage they take back in and replace.. It's gotta be astounding.. It's a small thorn in my side for a day and a half, but my phone should be here before noon. I just gotta go and find my rootkit folder and get it all ready
This is the 2nd phone I've wound up bricking. I didnt get my first true smart phone till October 3yrs ago. HTC droid incredible.. that phone was seriously tuffer then nails.. It was dropped so many times, i just stopped caring if it fell cause i knew it would be ok.. Went down a flight of wood steps into my basement during a call and didnt blink.. I wound up melting the back cover to the battery once, my daughters * i have twins* were destroying something and I had torch on looking for something. I wound up putting the phone down on a towel w/ torch on facedown.. I got busy cleaning what they messed up and by the time I remembered my phone I went to get it and it shut down as I picked it up.. It was extremely hot and around the LED you could see a ripple from where it melted. I pulled everything apart, let it cool off for like 10minutes and it booted right back up.. It bricked way later on, I was way more flash happy back then, then I am now. I'm pickier now, back then I was just trying anything..
This sII was bought in October of last year. But it's seen its number or battery pulls and restores.. Tomorrow we will follow up the same..
Click to expand...
Click to collapse
Yeah we've all bricked a device lol, I had a Samsung galaxy precedent that I beat to sh*t, threw, dropped, whatever n it always booted, still to this day actually lol its sitting in a draw somewhere, my daughter plays games on it lol, but yes honestly the amount of s2s that have been refurbished is astounding my buddy is a tech for T-Mobile which is how I know all this but they hardly ever even send u back the same device when u send for repair, just junk it for a new refurb, wipe and restore the broken one and someone else gets it lol, there tough and almost unbrickable but almost is the key word, how u bricked urs though is strange, I've never had it happen like that before, good luck with the new one and switch to twrp, much better recovery for all the new roms out there
Sent from my SAMSUNG-SGH-T989 using xda premium
I got this phone under the "free" section of craigslist.(lucky me)
this phone was perfect, no cracked screen, no scratches, just a bump in the side. The only major problem was that this phone was hard bricked.
What I did was that I went to ebay, and found a random seller with decent reviews for JTAG service. The whole thing cost about 40 dollars. (since I got the phone free, I would only lose $40 if this was a scam)
This dude was really nice! I got my GS2 back within a week completely fixed. with stock touchwiz loaded and prerooted alerady
new phone arrived a few hours ago. been running some errands and such.. now to root this one.. tmobile picked the tab up on this one..
so i threw cwm recovery on via odin, flashed my superuser zip. it failed a couple times, 3rd time it took.. booted up and titanium couldnt get access.. in the su update fixer its also failing at "gaining root access"..
any idea's?
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
DeafScribe said:
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
Click to expand...
Click to collapse
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Worth a try...
KennyG123 said:
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Click to expand...
Click to collapse
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
DeafScribe said:
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
Click to expand...
Click to collapse
I just hooked one of my old ones up to freedompop through the BYOD program. Nice to see the old girl getting use at least as an emergency phone.