Hey everyone I'm new to this forum. After I updated my bionic to ICS last week I have had nothing but problems. The phone constantly reboots itself. It might stay on for 5 seconds or 3 hours. I was wondering if there is anyway to go back to Gingerbread or a way to install a rom that will work. Any help would be greatly appreciated.
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Sir_Eagle said:
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Click to expand...
Click to collapse
I have reset it 3 times. Still reboots all the time. I tried taking out the microSD card doesn't help either.
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
stevendbrady said:
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
Click to expand...
Click to collapse
I should be getting a new battery in the mail tomorrow. I will let you know what happens. Thanks for the help.
Ha, it's been a month, but did it work? Or did you get it working otherwise?
I experience the same issue.
I RSD Lite and FZX my phone back to stock and it seems to work for another 5 days or so. I've tried to nandroid a backup when it's good then restore it when it goes nutty but that doesn't help. I've flashed the FZX image, then used Safestrap to flash a CM-based ROM in Slot1, but when the stock goes TU, so does the other.... and vice versa.
I haven't tried batteries.
I just got this phone in the mail yesterday off of e**y and it has been rebooting all the time too. Not consistently though but enough to make it aggravating. I just got it rooted and somehow was able to get safestrap3 on it. Went into the twrp recovery and wiped cache and dalvik and rebooted from there. So far ok but it has only been about 10 minutes since I did that. I have already done 3 factory resets and even wiped cache in stock recovery. I used my X2 to record the craziness of this phone doing it's own thing but with the guy above talking about the battery maybe being faulty I might have to try that because the phone has at 0% when I got it and I don't know how long it was dead for. Does not being charged for a long time ruin a battery?
Related
I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.
Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable
Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build
You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.
Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.
I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.
I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.
Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks
No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.
I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks
I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks
I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.
This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.
Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks
Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.
My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Andy.WP7 said:
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Click to expand...
Click to collapse
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
What firmware/ROM are you using?
What firmware/ROM are you using?
Click to expand...
Click to collapse
I am still using the stock Froyo ROM that the phone came with. The phone is rooted and I've installed a SpeedMod Kernel. However, both (rooting and new kernel) have happened months ago, so I doubt that they have anything to do with the problem.
(partial) solution found
Since a phone that crashes every night, using all settings in the process, is fairly useless, I decided that I might just as well trash it completely by trying (and maybe failling ) to install a custom firmware. So I downloaded Darky 10.1 and thanks to an excellent installation guide, I actually managed to install it.
Since then, my phone does no longer crash every night - it now reboots a couple of times a day The good thing is, though that after the reboot, the phone is back "in action" after maybe two minutes and it does not lose any data, setting or anything. So, it's not ideal, but much better than before ...
I was going to recommend trying a new ROM, but I found that as a workaround rather than a solution to your problem.
Did you perform a wipe or no-wipe install?
Kops said:
Did you perform a wipe or no-wipe install?
Click to expand...
Click to collapse
As I had pointed out in my first post, the crash that happens every night breaks something so that I can no longer receive calls and have to do a factory reset. Thus, the phone was basically wiped, already, before I did the installation and I then did a no-wipe install.
You are right, of course that this is more of a work around than a solution, but since I was thinking about putting on a new ROM for a while, already, anyways, it is a fairly good work around for me - and I really like Gingerbread and DarkyROM so far.
Kops said:
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
Click to expand...
Click to collapse
In the end it turned out to be a hardware problem and I needed to get the phone replaced.
Hey guys, I get the sickening feeling that I"m totally hosed right now, but I wanted to confirm with others who know more than I do.
Back at the end of December, my phone freaked out and the data partition was corrupted. I had to reflash recovery via ADB, and then do a manual formatting of my data partition. (using this guide: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html) It was fine for about a month and a half, and then it started freaking out again (about two weeks ago.) I then had to reformat the data partition about every 2 days. Eventually I read that the version of TWRP I was using might have been the cause (2.8.3.0,) so I upgraded to 2.8.5.
That seemed to somewhat fix it for this past week, though I've had it force reboot a few times, it still ran. Today I started getting the Google Play services and other google apps crashing notifications, so I went to go a complete backup via TWRP and then restore to stock for good measure. TWRP backup was about 80% done when I last checked it (battery was still at roughly 70%), and then the next time I went to check the phone, absolutely no signs of life. Ice cold, no reaction when plugged in, or anything.
I think it sounds like I may have had a memory hardware failure, in which case I'm totally screwed... What do you guys think?
Thanks!
enterflux said:
Hey guys, I get the sickening feeling that I"m totally hosed right now, but I wanted to confirm with others who know more than I do.
Back at the end of December, my phone freaked out and the data partition was corrupted. I had to reflash recovery via ADB, and then do a manual formatting of my data partition. (using this guide: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html) It was fine for about a month and a half, and then it started freaking out again (about two weeks ago.) I then had to reformat the data partition about every 2 days. Eventually I read that the version of TWRP I was using might have been the cause (2.8.3.0,) so I upgraded to 2.8.5.
That seemed to somewhat fix it for this past week, though I've had it force reboot a few times, it still ran. Today I started getting the Google Play services and other google apps crashing notifications, so I went to go a complete backup via TWRP and then restore to stock for good measure. TWRP backup was about 80% done when I last checked it (battery was still at roughly 70%), and then the next time I went to check the phone, absolutely no signs of life. Ice cold, no reaction when plugged in, or anything.
I think it sounds like I may have had a memory hardware failure, in which case I'm totally screwed... What do you guys think?
Thanks!
Click to expand...
Click to collapse
yeah if it died during an operation in recovery it's not good, unfortunately this seems to be happening to quite a few people now that the phone is 2 years old and most likely out of warranty
clsA said:
yeah if it died during an operation in recovery it's not good, unfortunately this seems to be happening to quite a few people now that the phone is 2 years old and most likely out of warranty
Click to expand...
Click to collapse
I sort of wondered if it was on its way out when all of this trouble began, but I was kind of in denial... Do you think there's any hope of fixing it off of warranty/is it worth it?
enterflux said:
I sort of wondered if it was on its way out when all of this trouble began, but I was kind of in denial... Do you think there's any hope of fixing it off of warranty/is it worth it?
Click to expand...
Click to collapse
Well considering the phone now sells for $150 new at Best Buy in the US, I would say just buy another one
clsA said:
Well considering the phone now sells for $150 new at Best Buy in the US, I would say just buy another one
Click to expand...
Click to collapse
Suckage... Well, thanks for confirming my fears. I wanted to get some XDA feedback before I gave up all hope.
Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.
Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.
MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.