[Q] Phone is DEAD! - HTC Sensation

My phone will not switch on. The battery is fully charged, i checked it with a reliable voltmeter and it read 3.7 volts. I put a different working battery from a different working sensation and still nothing. The led does not come on when i connect it to the charger and i am losing patience.
The back story is, yesterday i flashed SENSEay onto my phone and all was good. I used titanium to restore the apps, no data, I made a backup and left the phone alone for a while. I decided later on that i was going to play a game of samurai vengeance, but to do so i had to install chainfire3d. I did this and tried to install the beta part of chainfire, unfortunately this caused a bootloop. I pulled the battery and went into recovery to restore, restore went fine and my phone was back to working. Before i went to bed i put my phone on charge and when i woke this morning the bugger would not switch on. Because it has happened during the night i have no idea what occurred to kill it, all i do know is that no-one else has played with it. What the hell has happened to my phone?
All help will be gratefully accepted.

Your in the same boat as me buddy
I started going through the same issue yesterday, finally gave up and called HTC. Your phone (like mine) should still be under factory warranty with HTc so they are willing to fix it for free. I am gonna send mine in but am hesitant because idk if they will be able to tell if its rooted or not.

I have no idea if they will be able to tell if its rooted. What have you tried to get your phone to power on? Most threads with similar problems seem to be battery related, but thats not the case with my phone.

big_smurf said:
I have no idea if they will be able to tell if its rooted. What have you tried to get your phone to power on? Most threads with similar problems seem to be battery related, but thats not the case with my phone.
Click to expand...
Click to collapse
This happened to me too, I tried all my batteries just to make it power up but it won't so o just called tmobile and they sent me a new one. Hope they will not charge me because the phone I sent back for.replacement.is rooted and flashed with arhd.
Sent from my HTC Sensation 4G using xda premium

i it wont turn on your good cuz it wont turn on for them they just force phone to d/l mode and reinstall if it will take it them resell as refreb

I have got myself a new phone and the old one is history. Thanks to everyone that helped but this thread is more dead than the old phone. Might as well close it!

Related

[Q] Restarting

So I've had the phone for about 3 weeks now and never had the restarting problem but now it's done it twice in the past 24 hours. Anyone know why it's doing it and how to fix it?
no one???? it's done it more again
hockeybpr25 said:
no one???? it's done it more again
Click to expand...
Click to collapse
need details what rom/kernel are you using? or is it completely stock? whats running when it restarts if anything? check new apps maybe one is being screwy
blazing through on my VZ Droid Charge
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
hmm if its completely stock I couldn't say why, but maybe someone with more experience than me could chime in... as for a fix, perhaps if you backed everything up first, then a factory reset might do the trick
blazing through on my VZ Droid Charge
hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
I'd look at any apps you recently installed. My Fascinate would reboot quite a bit at times for no reason, it could be a Samsung glitch.
What I tell my customers to do is;
-check that there isn't any software updates
-pull the battery and wait 30 sec. I know it is the generic answer but it fixes most problems, it just like a computer if it not working right, restart. (Laptops mainly in pulling the battery.)
-or factory/data reset. It often will fix the issue but there are the few cases where it will not solve the problem. (and you will lose all of your stuff on your phone, contacts are backed up by Google or backup asst.)
-lastly, root it!!! no problems on my GummyCharged, v1.5, 2.3.4 (I don't tell my customer this choice)
Yeah I'm going to root soon. I just keep on reading these forums everyday so I can hopefully prepare for rooting with no issues.
Sent from my SCH-I510 using XDA Premium App

I'm I lucky..LOL or my phone is crap?

Hi, all.
Here is the situation....
In the past week or so I been getting update notices for .....45.....
Message was so brief that I haven't had a chance to get all numbers..
After accepting an update phone was hanging on the exclamation mark doing absolutely nothing over night...
Of course, I have my phone S-off and rooted. Nothing else was done yet, same stock ROM with no alterations. Now the tough part. Since that attempted update battery life was awful... Needed to charge almost twice a day...
NOW!!!! Does not take the charge at all... Charger works, charging my HD2 + USB computer charger nothing works. When plugged in and I remove the battery, insert it back it gives me an amber light for 5 seconds, then goes dark. Cannot boot with power cable plugged in..... Bunch of crap...
Did anybody else ran in to the same problem? Was that update meant to kill the phones with S-OFF? Or it's just my phone crapped up or battery?
Please give me some guide... 3 week old phone and so many problems.
Thanks all!!
No problem to bump my post.
Phone doesn't charge at all
Never, really never install an ota on a rooted ROM, even if its stock. I guess you should start by reinstalling stock ROM and wipe before. The charging thing is a known bug due to recovery. An update is available which you should install. You will have to manually charge the battery with a cut charging cable. Instructions can be found in this forum.
Sent from my HTC Sensation Z710e using Tapatalk
Did you look here, http://forum.xda-developers.com/showthread.php?t=1192300 I havent got my phone yet just been reading
70challenger said:
Did you look here, http://forum.xda-developers.com/showthread.php?t=1192300 I havent got my phone yet just been reading
Click to expand...
Click to collapse
You don't have a Sensation yet and you are educating yourself in a proper way? I wish more people would be like you. Now, if only natural selection would work on online forums as well.
Tester30 said:
No problem to bump my post.
Phone doesn't charge at all
Click to expand...
Click to collapse
I have the same as youuuu one week ago.
first I try S-off, root, and install new rom In XDA rom.
Every thing work fine, until the night my phone go to sleep, then It never weak up anymore.
And my phone have the same acting as you.
I call my local HTC service. he say he will take my phone to check.
After one day HTC told me the problem is the mainboard. He have to change for me, but do not have the spare prats now, so I have to wait.
But today HTC call me he will change the new phone!!!!!.
I am waiting to confirm for the date.
thanet said:
I have the same as youuuu one week ago.
first I try S-off, root, and install new rom In XDA rom.
Every thing work fine, until the night my phone go to sleep, then It never weak up anymore.
And my phone have the same acting as you.
I call my local HTC service. he say he will take my phone to check.
After one day HTC told me the problem is the mainboard. He have to change for me, but do not have the spare prats now, so I have to wait.
But today HTC call me he will change the new phone!!!!!.
I am waiting to confirm for the date.
Click to expand...
Click to collapse
They told you its the Mainboard without looking at it?
This is stupid!
Search for the solutions in this forum its a well known and discussed bug!
Thanks all for educating links and replies!
Got the phone exchanged today. Not gonna do anything yet, until all dust settles and all updates will be in place.
THANK YOU!!!
Tester

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

[Q] Unpleasantness... Bricked phone?

So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...
Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app
+1
Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium
The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:
keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.
Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos
A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..

Strange Issues with my Infuse

I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
djfourmoney said:
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
Click to expand...
Click to collapse
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
qkster said:
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
Click to expand...
Click to collapse
I mentioned that in the post, I did it while in Mexico City. It worked fine until this week, late last week. The battery only gives me about 5 hours now with just 32% audio playback and about 10% web access.
I guess I'll order a Anker battery from Amazon.
I rooted the phone again last night but before I did that, the phone became unresponsive three times in an hour. Which microSD card are you talking about? I just bought a 32GB Class 6 card and that works fine, I play all my audio from it, no problems.
If you mean the internal microSD card, that could be possible. I assume I can crack open the phone and replace this easily?
I should mention it never does that while plugged into a power source, so maybe this is all battery related.
Possible Fix...
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
djfourmoney said:
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
Click to expand...
Click to collapse
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
qkster said:
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
Click to expand...
Click to collapse
Thus far, that issue has not returned. Yes the battery holds a charge, but last only about 5-6 hours now, not 7-8 hours.
It seems it was a minor software issue. I did a factory reset, you keep missing that.
I did it in Mexico City (7 days ago).... Since that point and returning to the US, I have put my apps back on the phone. I had already updated to Gingerbread and it just reset to that.
I won't know more until I am out and about with my phone. I will be watching various auto racing events and don't plan on leaving the house this weekend.
Aussie V8's at COTA
NASCAR All Star Race @ Charlotte
World Challenge @ COTA
ELMS @ Imola
DTM @ Brands Hatch
WTCC @ Sazburg
Nurburgring 24 Sunday-Monday
elbscorp said:
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
Click to expand...
Click to collapse
No problem, I've never had a problem with TB. I updated the rom to a rooted version of the AT&T Gingerbread release so I could even use it... lol
The phone was rooted for Froyo, I downloaded the AT&T Gingerbread from Samsung via Kies when it was released and it remained rooted.
But resetting it back to stock, TB didn't work until I put the rooted rom on the phone.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
elbscorp said:
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
elbscorp said:
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Well like this, I will not go into the details but somebody else put Swipe Lock on the phone and of course I didn't know what he put into the phone. I was trying to resolve data issue on TelCel.
I had to do a hard reset outside of the operating system. Since the ROM was already upgraded to Gingerbread but unrooted, it went back to its unrooted state meaning I couldn't use TB.
So I re-downloaded apps from my memory. All of them are free so it wasn't an issue, just time consuming.
qkster said:
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
Click to expand...
Click to collapse
See above.
I used download mode to get out of Swipe Lock. I never used Swipe Lock, a-hole wanted to charge me 120 pesos ($7) to wipe it and put it back to stock, I wasn't going to do it, I know enough about Android phones to do it myself.
Oh well, lesson learned, I believe wiping the cashe from TwLauncher has solved the problem.
I did re-install all the apps from the store. I wasn't able to use TB until Thurs night (5/16). I noticed the errors Friday afternoon, wipe the cashe and no issues since.

Categories

Resources