Develop Bugs

Should I flash...help

Here's the deal. I have one of the gnex's that had the bad 4g radio and couldn't stay connected to the network logger than 10 minutes. The jb update finally came and fixed. Scared to flash custom Rom in fear old problem might return. Has anyone had one the previously faulty phone and has since flashed a custom Rom with success?
Sent from my Galaxy Nexus using xda app-developers app

nlcgadgetman said:
Here's the deal. I have one of the gnex's that had the bad 4g radio and couldn't stay connected to the network logger than 10 minutes. The jb update finally came and fixed. Scared to flash custom Rom in fear old problem might return. Has anyone had one the previously faulty phone and has since flashed a custom Rom with success?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You have nothing to lose but some time if you flash something and don't like it. If the update fixed your problem, almost all custom roms will be using an android version at least equal to what you are running now (most probably newer). You can make a nandroid to restore if you find you have problems with whatever rom you flash. If you don't want to do that, you can always use the factory images posted by google and restore your phone back to the version you are using now. Updated radios probably helped more than anything in a kernel or /system (which is all most custom roms contain - I don't think I've ever seen any that contain radios for the galaxy nexus).

Now running liquid smooth. 4g still strong thanks for the info.
Sent from my Galaxy Nexus using xda app-developers app

nlcgadgetman said:
Now running liquid smooth. 4g still strong thanks for the info.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Just enjoy your freedom

Help... Bootloop? But not a bootloop? Confusion.

Rooted my i317 2 days ago with the "no triangle counter" method. All was good, got TWRP installed, nandroided stock and did my thing. Been rooting phones for many years and have yet to brick anything *knocks on virtual wood*. Installed paranoid android, and all was awesome. Decided to give another rom a try... Cant remember which, but im not thinking thats the issue.
Wiped, flashed, no errors, rom booted normally, but as i unlock the device i get three force close errors. Then reboot. Over and over. Restored three different backups and all three do the same thing. Never run into this one before. Admittedly i am worried. Not a rich man and bought this phone outright...
I am hoping flashing in odin the original root tar file will correct the issue. But honestly wanted to do some reading and post this first. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I957 using Tapatalk

Did you try flashing a touch wiz kernel before going back to a nandroid? If not try that and if so try a factory reset and then a good old reboot!
I assume you tried a cm10.1 rom?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Same thing happened to me and I did just use odin to push that tar file through, rerooted, and flashed in my rom. That to me seems to be the fix for the bootloop imo. But someone with more knowledge could correct me if im wrong. Probably didnt help you any but just thought I would share my experience and fix when I was in the same position.
Sent from my SGH-I317 using xda premium

Both of you are good people. Alleviated is a drastic understatement. Was afraid it was a bad internal storage (bad hard drive) and was an issue limitec to my device. Others have done it, it can be fixed.
Cheers, gonna odin reflash now. If not will figure it out.
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

Let me know im always ready to help and trouble shoot had lots of devices and theyve all lived through my tests and bad flashes :thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Keep us posted.
Sent from my SGH-I317 using xda premium

jdc5 said:
Keep us posted.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Help full group over here, Appreciated greatly. Ive messed up a couple devices pretty good in my day, but never beyond repair. Always credited to people round these forums.
The factory reset didnt seem to help. But if system apps are missing... Reflashed the original tar file, and am just sitting here with a lump in my throat watching the Samsung logo hang...
Anyone got a link for the original rogers firmware?
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

*edit* back to stock. Dont wanna speak too soon, kinda superstitious with phones. But i think im good. Took two trys to flash original firmware.
Thanks guys, **** not so bad when ya got communication in a forum.
Cheers
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

What I did when it was stuck at the Samsung logo was I took out the battery> held down volume up, center home, and power to go into the system and did a factory wipe> then it pulled through nack to stock. Give it a try and keep me posted.
Sent from my SGH-I317 using xda premium

I tried the factory wipe through the cwm recovery included, didnt work. Was still stuck on samsung logo. Reflashed with odin a second time which allowed a successful boot and recovery of my paranoid android backup. Im good to go... Gonna do some more reading though. Im missing something important with this phone. Moving from 4.1 to 4.2 roms or vice versa seems to be... Weird.
Anyways all good. Thanks.
Sent from my SGH-I317 using Tapatalk 2

Getting a Different Phone

I have a Samsung Galaxy SIII from AT&T (d2att ), and I have it rooted, running task650's AOKP, and TWRP 2.4.1.0 for recovery. It works fantastic, and I love it I have, however, been trying everything I can think of to try and get ktoonsez's kernel to work on it, for the features that his kernel offers. I am having a funky issue, which according to task, kt, and a few others on the boards, is device-related. It seems that my phone, individually, is the problem. This leads me to my question.
How feasible is it to get AT&T (or Samsung?) to replace my phone, based on the fact that there is something different hardware-wise between mine and the vast majority of other peoples?
It seems that nearly everyone who runs this combination of task and ktoonsez has nothing but good things to say, and I have yet to see anyone gripe about the same issues that I have had, and not be able to fix them, usually by a simple full wipe. I have tried to do full wipes with and without letting Google initialize/restore my account. I have tried going back to stock everything, and trying again. I have made sure to turn off Performance Control, so there should be no conflict there. I have tried setting up my phone in its entirety, restoring information, restoring apps with TiBu, and then installing the kernel. I have tried with and without deleting mpdecision. I am following all of the directions posted per OP for both threads, and with the gapps posted by task himself. Nothing works, and I end up in a glitchy boot loop almost immediately after flashing the kernel, even if my phone was running buttery stable before the flash.
I have come up with a couple things to try tonight, but if they don't work, I would like to pursue getting a new phone to replace this one. Is that an option?

You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.

task650 said:
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
Click to expand...
Click to collapse
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company

drinfernoo said:
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
Click to expand...
Click to collapse
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.

task650 said:
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
Click to expand...
Click to collapse
Time to get creative lol
Sent from my SGH-I747 using xda app-developers app

Settling In
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.

bsam55 said:
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
Click to expand...
Click to collapse
I suppose that is possibly what's going on with mine, I'll give it a couple more tries
Sent from my SGH-I747 using xda app-developers app

Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

pcshano said:
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app

drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not intentionally brick your device. That could be just as bad as leaving your phone rooted when you take it in (depending if Samsung can see any part of the storage). As far as warranty exchange "excuse" that is on you to decide. Follow the post quoted below to help your chance at warranty exchange. This has been discussed quite a bit all over the place.
hednik said:
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse

You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium

G-Man. said:
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I completely agree. I'm on tasks currently using his underwear kernel provided. I've also tried KT's kernel as well. Yes you can get more customization with KT's and his custom governor, but is it worth it to go through all the hassle to get a new device? I would say no. Like I said I've tried both kernels, I'm currently using tasks underwear kernel, I may try KT's again, may not. When I did before, I didn't notice a drastic difference between the two, esp not enough to warrant going through a device replacement.
Consider this. You are running tasks rom with absolutely no issues with the kernel he provides. Is that not good enough? I know it is for me. His rom is absolutely the most stable rom I've ever tried on any device. Remember it's just a phone. Just some food for thought.
Sent from my SGH-I747 using xda app-developers app

Probably right, but i don't always run task's ROM, either. My favorite ROM so far has actually been ParanoidKANGDroid, but I wanted 4.2.1, so I went to task. I'm actually running PACman right now, and for the time being, even his PC is broken
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium

G-Man. said:
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Of course, but if it allows me more flexibilities and control over my phone and what it does, I'm all over that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app

liltitiz said:
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium

G-Man. said:
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
When the s3$ first come out, a lot of people were bricking them. Trying to root or installing an international ROM. I'm pretty sure Samsung staff was aware of that but they still gave free replacement. Some people even got a replacement from att or others carriers for free.
Sent from my SGH-I747 using xda app-developers app

If I do end up getting a replacement, can I take a nandroid, and restore it to the new phone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Can someone please help a semi-noob???

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

Problem after update

After I updated my phone to 4.4.2 I lose service and have to restart my phone multiple times a day to get service back. I called T-Mobile and after resetting the phone they said they would replace it. Then I called Samsung and they said to bring it to best buy to have it reflashed. I can go there but I could also flash it via Odin at home. Now my question is, if I flash the stock rom via Odin will it trip the Knox counter? I read that it won't and I read that it can. I just want to make sure it won't before I flash it incase I have to have it repaired or replaced.
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
After I updated my phone to 4.4.2 I lose service and have to restart my phone multiple times a day to get service back. I called T-Mobile and after resetting the phone they said they would replace it. Then I called Samsung and they said to bring it to best buy to have it reflashed. I can go there but I could also flash it via Odin at home. Now my question is, if I flash the stock rom via Odin will it trip the Knox counter? I read that it won't and I read that it can. I just want to make sure it won't before I flash it incase I have to have it repaired or replaced.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Did you update it officially or via a ROM flashed in a custom recovery?
Sent from my SGH-M919 using Tapatalk

elesbb said:
Did you update it officially or via a ROM flashed in a custom recovery?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I updated ota. I haven't rooted this phone yet.
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
I updated ota. I haven't rooted this phone yet.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I would try flashing the stock official update through Odin. That's pretty much what best buy is going to do.
Sent from my SGH-M919 using Tapatalk

elesbb said:
I would try flashing the stock official update through Odin. That's pretty much what best buy is going to do.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
That's what I was thinking. I just wanted to make sure that wouldn't trip the Knox counter going through odin. I wouldn't think so but I read somewhere when I did a Google search that someone said it did.
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
That's what I was thinking. I just wanted to make sure that wouldn't trip the Knox counter going through odin. I wouldn't think so but I read somewhere when I did a Google search that someone said it did.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
So long as it's a 100 percent stock ROM it shouldn't. It only trips if system partition or a custom recovery are detected.
Sent from my SGH-M919 using Tapatalk

elesbb said:
So long as it's a 100 percent stock ROM it shouldn't. It only trips if system partition or a custom recovery are detected.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well I flashed the stock rom from sammobile yesterday morning and so far so good. I haven't had a problem since. Tmobile said there is no way I could flash the firmware again even though I knew I could through odin, just wasn't sure if I used odin if it would trip the Knox counter. I didn't want to replace my phone that is in mint condition through tmobile and get who knows what in return so I called Samsung and they said to go to best buy to have it reflashed. I saved myself a trip by doing it myself. thank you elesbb for your help.
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
Well I flashed the stock rom from sammobile yesterday morning and so far so good. I haven't had a problem since. Tmobile said there is no way I could flash the firmware again even though I knew I could through odin, just wasn't sure if I used odin if it would trip the Knox counter. I didn't want to replace my phone that is in mint condition through tmobile and get who knows what in return so I called Samsung and they said to go to best buy to have it reflashed. I saved myself a trip by doing it myself. thank you elesbb for your help.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yeah, i hate getting replacements from them. I no longer have insurance as any repairs (aside from shattered screen, this denotes an upgrade ) i will just do myself. I have gotten replacements for my S3 through them and they ALL were horrible. I ended up having to take apart both phones when they sent me the new one and made a good working one out of it and reassembled the bad pieces into a bad phone and sent that one back. Ha. It was pathetic. lol.
Always come here before swapping out your phone or anything. There is so much information available and helpful people anyone can really solve their own problems.

elesbb said:
Yeah, i hate getting replacements from them. I no longer have insurance as any repairs (aside from shattered screen, this denotes an upgrade ) i will just do myself. I have gotten replacements for my S3 through them and they ALL were horrible. I ended up having to take apart both phones when they sent me the new one and made a good working one out of it and reassembled the bad pieces into a bad phone and sent that one back. Ha. It was pathetic. lol.
Always come here before swapping out your phone or anything. There is so much information available and helpful people anyone can really solve their own problems.
Click to expand...
Click to collapse
Well I spoke too soon. I had to restart my phone again to get service back. The problem is still there. I had data but no cell service. Even if I turn airplane mode on then back off to reset it it still doesn't work. I have to restart my phone. Do you think it could possibly be a simple card issue? It started the day after I updated my phone when 4.4.2 came out.
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
Well I spoke too soon. I had to restart my phone again to get service back. The problem is still there. I had data but no cell service. Even if I turn airplane mode on then back off to reset it it still doesn't work. I have to restart my phone. Do you think it could possibly be a simple card issue? It started the day after I updated my phone when 4.4.2 came out.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
It could be a SIM card issue. Do you have another phone you could test the SIM card with?

elesbb said:
It could be a SIM card issue. Do you have another phone you could test the SIM card with?
Click to expand...
Click to collapse
I'm going to go to the tmobile store today to get a new one and hopefully that's it. I tried to get a replacement for my girlfriend's phone and got 3 that I sent back because they were worse and just kept hers so I don't want a replacement from them
Sent from my SGH-M919 using xda app-developers app

After replacing my SIM card on Friday, it's been good. I figured I'd give it a few days before I said something this time. It's weird that it happened right after I updated to kit kat
Sent from my SGH-M919 using xda app-developers app

Mr. bird said:
After replacing my SIM card on Friday, it's been good. I figured I'd give it a few days before I said something this time. It's weird that it happened right after I updated to kit kat
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I've had SIM related issues before. Sometimes an older SIM card won't work correctly with a system update. With a new card problems disappear. Let's hope this is the case for you.
Steve

in the same boat
Ever since I got the OTA Kit Kat my phone is in nightmare mode. Wifi wont stay on or ever even come on. Wake screen freezes and numerous other issues. I got same responses from TMO and Sammy and have spent 100 hours on here searching for HOW to fix. Ive used Odin 307 and 309 with various files CWM OUDHS, etc and never get anywhere. Just fails with "no PIT" errors every time.
Ive rooted phones before with NO problems , G2, and other HTCs, but Sammy driving me nuts.Im assuming its because I have 4.4.2
So your saying using Odin with a stock ROM will work? or errors again? samobile the site you need to pay to join right?
Ive seen THOUSANDS of people with SAME issues, various carriers as well as S4s and Nexus
Im so stinking frazzled from this

madhitsblog said:
Ever since I got the OTA Kit Kat my phone is in nightmare mode. Wifi wont stay on or ever even come on. Wake screen freezes and numerous other issues. I got same responses from TMO and Sammy and have spent 100 hours on here searching for HOW to fix. Ive used Odin 307 and 309 with various files CWM OUDHS, etc and never get anywhere. Just fails with "no PIT" errors every time.
Ive rooted phones before with NO problems , G2, and other HTCs, but Sammy driving me nuts.Im assuming its because I have 4.4.2
So your saying using Odin with a stock ROM will work? or errors again? samobile the site you need to pay to join right?
Ive seen THOUSANDS of people with SAME issues, various carriers as well as S4s and Nexus
Im so stinking frazzled from this
Click to expand...
Click to collapse
Go here, this will help you figure it out.
http://forum.xda-developers.com/showthread.php?t=2336392
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)

PanchoPlanet said:
Go here, this will help you figure it out.
http://forum.xda-developers.com/showthread.php?t=2336392
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
Click to expand...
Click to collapse
Thanks, but Ive done all that already. Odin never gets through its process..ALWAYS fails no matter what TAR I use. "no PIT" error every time

madhitsblog said:
Thanks, but Ive done all that already. Odin never gets through its process..ALWAYS fails no matter what TAR I use. "no PIT" error every time
Click to expand...
Click to collapse
What do you have checked in Odin? And are you flashing 4.4.2 firmware?
Sent from my SGH-M919 using Tapatalk

PanchoPlanet said:
Go here, this will help you figure it out.
http://forum.xda-developers.com/showthread.php?t=2336392
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
Click to expand...
Click to collapse
serio22 said:
What do you have checked in Odin? And are you flashing 4.4.2 firmware?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
depends on files directions, but usually have nothing checked according to k0nane directions. i have tried everything BUT 4.4.2 firmware, but never gets but few seconds in before that error right away

madhitsblog said:
depends on files directions, but usually have nothing checked according to k0nane directions. i have tried everything BUT 4.4.2 firmware, but never gets but few seconds in before that error right away
Click to expand...
Click to collapse
Well either way you'll never get anywhere without 4.4.2 because you said that's what you have.. It won't flash anything below that so try 4.4.2
Sent from my SGH-M919 using Tapatalk

serio22 said:
Well either way you'll never get anywhere without 4.4.2 because you said that's what you have.. It won't flash anything below that so try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
no error now for 4.4.2, NB4 TAR, just says "get PIT" see pic attached