Related
Hi guys, my desire has been rooted and was running fruit burst. Every now and then it would crash leaving the "HTC quietly brilliant" permanently on, which to get round i just removed the battery and turn back on (i could live with that).
Any way this afternoon i was just using it as normal, put it back in my pocket and thought nothing of it. Got it back out and it was switched off. Switched it back on and it comes up with the white screen with the green HTC writing, the just keeps doing that over and over again.
Any ideas?
Nope, this problem is completely unfixable and has not been fixed multiple times, and there is no listed guides that can help you due to it's complication. You now need to defenestrate your phone and acquire a new one.
Hahahahahahaha
Swyped from my CM7.1 Desire using XDA Premium App
guys, theres no need go be a total di*k about it. just point him in the right direction.
Sent from my SGH-T959V using xda premium
Juls317 said:
guys, theres no need go be a total di*k about it. just point him in the right direction.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
There's a guided STICKIED on the Q&A forum which fixed this problem almost directly. Not only that, it is now also linked on this thread (twice). Not to mention, this works wonders..
There could be a number of reasons why that is happening:
1) sd card has broke
2) stuck in a bootloop (run adb logcat).
Can you access recovery/hboot?
Sent from my HTC Desire using XDA App
chevli said:
There could be a number of reasons why that is happening:
1) sd card has broke
2) stuck in a bootloop (run adb logcat).
Can you access recovery/hboot?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
hence why i suggested that people point him in the right direction instead of flaming him
Sent from my Kindle Fire using xda premium
Hi Guys, thanks for you help ( some of you (-; ). I got the phone sorted (guy who falshed it, talked me through). Anyway, since this post i have played with a good 3 or 4 roms, problem is i want something which looks nice but is practical with the battery.
I am currently on AceSMod007-lite v14, but the battery life is shocking. Any ideas to something better?
UK_Akita said:
Hi Guys, thanks for you help ( some of you (-; ). I got the phone sorted (guy who falshed it, talked me through). Anyway, since this post i have played with a good 3 or 4 roms, problem is i want something which looks nice but is practical with the battery.
I am currently on AceSMod007-lite v14, but the battery life is shocking. Any ideas to something better?
Click to expand...
Click to collapse
Use AOSP ROMs for better battery life and performance. Try CM7 and see if it improves.
UK_Akita said:
Hi Guys, thanks for you help ( some of you (-; ). I got the phone sorted (guy who falshed it, talked me through). Anyway, since this post i have played with a good 3 or 4 roms, problem is i want something which looks nice but is practical with the battery.
I am currently on AceSMod007-lite v14, but the battery life is shocking. Any ideas to something better?
Click to expand...
Click to collapse
I totally recommend you CM7, I experienced a big improvement in battery life
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.
How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA
Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA
Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium
Hi my new Note II has just decided to reboot and it's sitting on the Samsung Logo. I'm only running the stock ROM. It's been sitting there for 10minutes now. I'm worried it might be SDS but I don't want to take battery out and reboot it as I'm scared it could be? it wouldn't be automatic updates? They don't take that long do they??
Someone help please!
DaBountyHunter said:
Hi my new Note II has just decided to reboot and it's sitting on the Samsung Logo. I'm only running the stock ROM. It's been sitting there for 10minutes now. I'm worried it might be SDS but I don't want to take battery out and reboot it as I'm scared it could be? it wouldn't be automatic updates? They don't take that long do they??
Someone help please!
Click to expand...
Click to collapse
If it was sudden death you wouldn't even see Samsung logo.
Sent from my GT-N7100 using xda premium
rodrigoyasuda said:
If it was sudden death you wouldn't even see Samsung logo.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
An update shouldn't take this long right? It's been 15minutes like this. I haven't flashed anything on the device only run Expynos abuse to root it and put Xposed framework for multi app but that's it. Nothing else. Guess it softbricked itself somehow wtf?
EDIT: I took battery out and put it back in and rebooted. It's back!! but why the hell did it do this??
DaBountyHunter said:
An update shouldn't take this long right? It's been 15minutes like this. I haven't flashed anything on the device only run Expynos abuse to root it and put Xposed framework for multi app but that's it. Nothing else. Guess it softbricked itself somehow wtf?
Click to expand...
Click to collapse
I don't know what happened there but 15 minutes is a lot of time. You'll probably need to remove your battery or hold power button until it reboots.
If it still gets stuck on samsung logo you'll probably need to wipe
Sent from my GT-N7100 using xda premium
rodrigoyasuda said:
I don't know what happened there but 15 minutes is a lot of time. You'll probably need to remove your battery or hold power button until it reboots.
If it still gets stuck on samsung logo you'll probably need to wipe
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
That's what I was thinking hmm.
This happened yesterday, I had the usual random freeze on my phone. Thought I just had to wait for it to restart, but this time it didn't. So I had to pull the battery out, and power it on from there.
Only, it didn't want to. No matter how long I press the power button, no response. I can't get into recovery or download mode. I have a spare stock battery and it won't power up with that too. The phone does however, heat up when the battery is inside. I tried leaving it without the battery overnight and then placing the battery back, but still no luck.
My phone is rooted, running AOSPAL ParanoidAndroid (4.3), with fancy kernel.
I hope someone can help me, and I hope my phone isn't bricked.
That happened to me once and yes, the phone was briked...
Just bricked randomly? No real cause?
Sent from my Galaxy Nexus using xda app-developers app
frimpasi said:
That happened to me once and yes, the phone was briked...
Click to expand...
Click to collapse
was it random just like mine?
kalizu said:
was it random just like mine?
Click to expand...
Click to collapse
Yep...
kalizu said:
This happened yesterday, I had the usual random freeze on my phone. Thought I just had to wait for it to restart, but this time it didn't. So I had to pull the battery out, and power it on from there.
Only, it didn't want to. No matter how long I press the power button, no response. I can't get into recovery or download mode. I have a spare stock battery and it won't power up with that too. The phone does however, heat up when the battery is inside. I tried leaving it without the battery overnight and then placing the battery back, but still no luck.
My phone is rooted, running AOSPAL ParanoidAndroid (4.3), with fancy kernel.
I hope someone can help me, and I hope my phone isn't bricked.
Click to expand...
Click to collapse
Generally speaking if the device doesn't even power up, then yes its bricked. sorry to tell you my friend. The main part of the device that powers up initially is the main bootloader in the logic board, so what has happened most likely is it just failed. kinda of like the bios on a pc. if the bios fails, then the computer can no longer be told to turn on.
Try omap flash..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Try omap flash..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Already tried that. I just get stuck on a failed operation. Something about an EMMC driver missing. Would you happen to know a solution to that?
kalizu said:
Already tried that. I just get stuck on a failed operation. Something about an EMMC driver missing. Would you happen to know a solution to that?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=omap+4460+driver
Sent from my Galaxy Nexus using XDA Premium HD app
So here is the fun story.
I was trying to get Firefox OS to work on my Sprint LG Optimus G and TWRP saud it failed. I have done this before with no issues really, but the second time made it angry. I know the device powers on because when I plug it up to my computer and hold the power button, the red LED light comes on. I can not get it to boot into anything. No Fastboot, TWRP, Download, or even CM11. All I can do is see a pretty red light. ? Can anyone help me?
Sent from my LG-LS980 using xda app-developers app
Try asking autoprime
http://forum.xda-developers.com/showthread.php?t=1984622
Sent from my LG-LS970 using xda app-developers app
did you try cwm instead
TWRP has been kind of picky when it comes to installing some roms like when i would try and install cm11 it would not work in TWRP but then after a quick flash to CWM it installs just fine i think its because cwm has the upper hand when it comes to installing possibly broken things where TWRP is for those people who don't want to accidentally ruin their devices because of lack of experience cwm has worked allot better for me and as far as your boot issue goes i would let it charge for a couple hours then hold the power button for 15 seconds so that way its powered off and then attempt to get into download mode. If you can do that then you can use LGNPST_ACG to do a secure boot loader unlock so that way you can flash cwm and go from there. I hope my experience and advice helps you out in your time of need. Good luck we are rooting for you
cpberndt said:
TWRP has been kind of picky when it comes to installing some roms like when i would try and install cm11 it would not work in TWRP but then after a quick flash to CWM it installs just fine i think its because cwm has the upper hand when it comes to installing possibly broken things where TWRP is for those people who don't want to accidentally ruin their devices because of lack of experience cwm has worked allot better for me and as far as your boot issue goes i would let it charge for a couple hours then hold the power button for 15 seconds so that way its powered off and then attempt to get into download mode. If you can do that then you can use LGNPST_ACG to do a secure boot loader unlock so that way you can flash cwm and go from there. I hope my experience and advice helps you out in your time of need. Good luck we are rooting for you
Click to expand...
Click to collapse
You have to use the freegee version of twrp to flash cm11.
Sent from my LG-LS970 using xda app-developers app
i have tried that before
mcog said:
You have to use the freegee version of twrp to flash cm11.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I have tried using the FreeGee verison of TWRP and it doesn't play nicely with some roms however with the roms that are incompatible with twrp i have installed successfully using cwm v.6.0.4.5 non touch enabled and it has proven to be much more compatible with some roms due to CWM and their relationship with the cyanogenmod team. twrp has a nicer ui however it does tend to have some compatibility issues. I have been developing for about 3 years and i have mainly used cwm until i got a galaxy tab 2 7in wifi with ir blaster then i moved on to twrp and loved it but when i got my ls970 twrp proved to have some issues with a couple of roms. when i tried the same files on cwm they worked just fine. so give cwm a shot it might work let us know how it goes
achunt2143 said:
So here is the fun story.
I was trying to get Firefox OS to work on my Sprint LG Optimus G and TWRP saud it failed. I have done this before with no issues really, but the second time made it angry. I know the device powers on because when I plug it up to my computer and hold the power button, the red LED light comes on. I can not get it to boot into anything. No Fastboot, TWRP, Download, or even CM11. All I can do is see a pretty red light. ? Can anyone help me?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem but for a completely different reason a few days ago. I plugged it into the wall for a few minutes and finally got it past that red light and into TWRP. I can't say it will work for you because the causes are completely different(mine was a kernel overclock error - my battery went from 100% - 0% in around 10 minutes and overheated). I plugged it in and saw that red light but it wouldnt turn on - ofcourse panic sets in bc its my only phone and I thought I fried it by overclocking. But I took a deep breathe, left it plugged in and when I came back it booted up. When I got into TWRP my battery read 1%, so I did a full wipe and restored my backup, then my battery read 99%, lol. Again mine was a kernel issue so that may not work for you. Partimus is right, autoprime would surely know - but you may have to do the dreaded battery pull(there are videos on youtube) to reset the phone.
cpberndt said:
I have tried using the FreeGee verison of TWRP and it doesn't play nicely with some roms however with the roms that are incompatible with twrp i have installed successfully using cwm v.6.0.4.5 non touch enabled and it has proven to be much more compatible with some roms due to CWM and their relationship with the cyanogenmod team. twrp has a nicer ui however it does tend to have some compatibility issues. I have been developing for about 3 years and i have mainly used cwm until i got a galaxy tab 2 7in wifi with ir blaster then i moved on to twrp and loved it but when i got my ls970 twrp proved to have some issues with a couple of roms. when i tried the same files on cwm they worked just fine. so give cwm a shot it might work let us know how it goes
Click to expand...
Click to collapse
The only problems I've had with TWRP were AOSP 4.4.x related. TWRP 2.5.0.0 has still been the most stable and trustworthy for the ls970 imo. However you need TWRP 2.6.3.x for anything 4.4. And you are right the FreeGee version of TWRP works with CM11 but has issues with other roms. twrp-geespr from chadouming works well on the other roms but not with CM11. However most of the "failed" issues happen with TWRP because of the asserts in the updater-script. If you open the zip and edit or flat out delete the assert it will almost always flash perfectly. I've even flashed unported nexus 4 roms to my device this way(obviously not much worked network wise besides wifi but it still installed and booted into android). CWM 6.0.4.5 seems to flash 4.4 roms fine but since my efs backups are TWRP, I will personally always have to flash back to TWRP if something goes wrong.
But the reason TWRP has compatibility issues is because of those asserts in the updater-script, which are absolutely safety measures. Our phone has been named a lot of things by the devs(ls970, geespr, geehrc4g, etc) so if TWRP checks for geespr but thinks your phone is an ls970, the flash will fail. Even if they are the same thing just named differently - TWRP doesnt know that and will stop the install to protect your device. Noob or not, that's a good thing and could possibly save you from bricking your device. The other issue(and why we can't flash 4.4 from TWRP 2.5.0.0) has to do with the SELinux changes that came with 4.4. Only one 4.4 rom would install for me via TWRP 2.5.0.0 and that was a port of houstonns AOSP4.4 because he disabled the SELinux changes.
So while I agree that CWM 6.0.4.5 seems to work great when installing 4.4.x roms, for as long as Ive had this phone, TWRP 2.5.0.0 has been all around the most stable. If I want to flash 4.4 I will install CWM or TWRP from recovery but always end up going back to TWRP 2.5.0.0 because I know it keeps my efs safe. But if you are keeping your 4.4 rom, you have no choice but to stick with updated TWRP or CWM and in this case I have heard of less issues with CWM than TWRP.
Yeah, I never had compatibility issues until 4.4
Sent from my LG-LS970 using xda app-developers app
mcog said:
Yeah, I never had compatibility issues until 4.4
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
It's that damn SELinux! :silly:
I tried plugging it in for like an hour and when I came back, it had the charging light. It still wouldnt boot. I have ordered a torx 5 and torx 6 screwdrivers so I can do a battery pull.
Sent from my LG-LS980 using xda app-developers app
Did you get the plastic pry bar as well? The outer case can be a pain in the as$ and you don't want to break anything. Also take your time with the battery, when I did mine I felt like they put way to much adhesive on it.
Sent from my LG-LS970 using xda app-developers app
Yes. I did. I also have a spare guitar pick if it doesnt work.
Sent from my LG-LS980 using xda app-developers app
I finally got the screwdrivers, which took forever to ship, and doing a battery disconnect does not help the phone reboot. What do I do now? Any help suggestions?
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
I finally got the screwdrivers, which took forever to ship, and doing a battery disconnect does not help the phone reboot. What do I do now? Any help suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Ouch, battery pull didn't help? How long did you leave the battery out before putting it back in? And is still doing the exact same thing, no lg logo, nothing but red blinking light when trying to power on?
And how did you get this phone? Did you get it from Sprint or from a place like BestBuy, etc?
Well, it's still doing the red light thing and when I plug it into my computer, it shows that it shows up and wants me to install drivers for QHSHUB_DLOAD. LGNPST doesn't recognize the device. I got the phone from Sprint, but I have upgraded since and have flashed the phone a few times, so the warranty may be void. I left the battery unplugged for a few minutes.
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
Well, it's still doing the red light thing and when I plug it into my computer, it shows that it shows up and wants me to install drivers for QHSHUB_DLOAD. LGNPST doesn't recognize the device. I got the phone from Sprint, but I have upgraded since and have flashed the phone a few times, so the warranty may be void. I left the battery unplugged for a few minutes.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
The upgrade is your biggest worry for voiding the warranty. Rooting does not void a sprint warranty - they wont advertise it but it's true - so I would try to take it back to them. If you upgraded and it's no longer on their network, meaning your phone number was switched to your upgrade, they probably won't help. If you were still able to use it as a phone before it went down, meaning it's still a line on your plan, they might. QHSUB_DLOAD means it's hard bricked, I don't think there is anything you can do if you see that. QHSUB_DLOAD is pretty universal when it comes to being hard bricked across devices.
There is a fix for phones with removable storage but since we don't have an actual sd card slot, it's bricked, and sadly unless Sprint gives you a new one, you're screwed.
Oh, so if I activate it, will they help me?
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
Oh, so if I activate it, will they help me?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That means it's no longer activated, so probably not. It's bricked so they can't activate that particular phone, and if it's no longer a line on your network I think it's warranty is up. However, I don't work for Sprint so I would still take it to them and see if they can do anything but I wouldn't get my hopes up. If it was still a line and had a phone number attached, you would still be under warranty and they would replace it with a new lgog.
HP's right. That Dload is a brick. The only fix I know if is "jtag". It a service that's getting more popular but at a price. I think, and I hope it's OK if I say this, but autoprime performs this service on our phones I think.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
HP's right. That Dload is a brick. The only fix I know if is "jtag". It a service that's getting more popular but at a price. I think, and I hope it's OK if I say this, but autoprime performs this service on our phones I think.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Learn somethin new everyday! And actually I did know about jtag, but I forgot about it, lol. It's where they send signals directly to 6 circular pins on the board. It's obviously more in depth than that, but yeah, good catch as always @engine95.
It can be expensive because the hardware boxes that deliver the code are very expensive. If Sprint doesn't do anything(and they probably won't), I'd ask autoprime - nicely.
EDIT: Thanks for reminding me @engine95. I'm yet again out of thanks for the day. You're the man!
Well, the phone is only a few months old. I took an upgrade on another phone because said person didn't want to upgrade. I will take it to Sprint sometime this week. It just snowed bland this is an area where it hardly snows, so everything is closed due to panic. I may take it Thursday and see if they can do anything.
Sent from my LG-LS980 using xda app-developers app