Develop Bugs

Bricked phone. Please help!

Hello. Hubby tried to root his galaxy S3 thru Odin and now the phone is bricked. We have tried many things on forums and YouTube but the phone will not connect to the computer now. It won't even turn on. It's just stuck on the downloading screen. Please if you can help us in anyway, to get it unveiled we would appreciate it.
Sent from my SM-N900P using XDA Free mobile app

Just in case you haven't tried yet, first take the battery out of the phone and leave it out for at least half an hour, all night if you can stand it, reboot the computer that you're trying to connect it to, try a different USB port, even try a different USB cable.
What did he Odin to the phone?
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

He says it was a root method from qbking on YouTube. For his Android version. I'm guessing the phone is trash now?
Sent from my SM-N900P using XDA Free mobile app

No, it isn't necessarily trash. Try my suggestions from my previous post and let us know the results of at least getting Odin on the PC to see the phone when you put it back in Download mode after leaving the battery out for a long while. Also, what version Odin? Try running it as Administrator if on Windows Vista or newer. Don't actually try to Odin anything yet. We'll walk you through this if it's recoverable.
Does he know what version of Android he was on? And what, exactly, did the instructions have him try to Odin?
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Ty so much! We tried a different cable and the phone booted right up after Odin. The phone works and makes calls and all. Thanks again :thumbup:
Sent from my SM-N900P using XDA Free mobile app

Great! You're welcome! I'm glad it was that easy. So is it rooted alright now? If it isn't we can help, it's not hard.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Nope it isn't rooted. Can you provide steps to do it that won't mess it up again? Ty
Sent from my SM-N900P using XDA Free mobile app

Odin the very latest Philz Touch Recovery tar, then somewhere in its menus it has a reroot function. There's a thread for Philz in development (non-original).
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Woke up this morning and the phone is messed up again. If I try to get Sprint to replace it will they know we tried to root it?
Sent from my SM-N900P using XDA Free mobile app

pinkcandygirlx said:
Woke up this morning and the phone is messed up again. If I try to get Sprint to replace it will they know we tried to root it?
Click to expand...
Click to collapse
First, they are other things to try before going that route.
Messed up how? Will the phone boot? If it will, in Settings / More / About Device what Software version does it say?
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

[Q] Terrible 4.4.3 and 4.4.4 radio on Sprint network (LTE only lasts 2 mins)

When I am on 4.4.3 and 4.4.4 radio, my LTE connection is absolutely terrible. It has pitiful speed, and typically only last 2 minutes or less before reverting back to 3G.
Did anyone find a way to make these radios work? As far as I can tell, the only answer is to downgrade by flashing a 4.4.2 radio.
I heard something is wrong with band 26. Maybe it would be possible to disable that?

I haven't heard of any 4.4.3 or 4.4.4 radio/modem for the SPH-L710. ND8/NDC are the newest, both for the latest official stock ROM which is 4.4.2.
Could it be you were flashing modems not meant to be flashed on our phone? If so, you're lucky the phone wasn't bricked. You should flash the NDC modem or re-Odin the stock ND8 tar.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Merudo said:
When I am on 4.4.3 and 4.4.4 radio, my LTE connection is absolutely terrible. It has pitiful speed, and typically only last 2 minutes or less before reverting back to 3G.
Did anyone find a way to make these radios work? As far as I can tell, the only answer is to downgrade by flashing a 4.4.2 radio.
I heard something is wrong with band 26. Maybe it would be possible to disable that?
Click to expand...
Click to collapse
I know this isn't much of a fix but I have a similar problem. I always loose 4g even when I know it's there.
I just switch the phone into LTE only mode and it stays connected none stop, well unless you move out of a coverage area.
Sent from my SPH-L710 using Tapatalk

Merudo said:
When I am on 4.4.3 and 4.4.4 radio, my LTE connection is absolutely terrible. It has pitiful speed, and typically only last 2 minutes or less before reverting back to 3G.
Did anyone find a way to make these radios work? As far as I can tell, the only answer is to downgrade by flashing a 4.4.2 radio.
I heard something is wrong with band 26. Maybe it would be possible to disable that?
Click to expand...
Click to collapse
@roirraW "edor" ehT may be right. There are no 4.4.3 or 4.4.4 radios for the SIII. Did you flash ROMs that were AOSP that were "4.4.3" or "4.4.4"? If so, you didn't change your modem, because they don't flash modems. You were still on the 4.4.2 modem. With the SIII, there is no way to disable the bands. Tri-band is out for the S5, which if you have your MSL you can disable different bands, but if you go into your ##DATA# settings for the SIII, it's simply LTE enabled/disabled. What you may want to try is flash back to complete stock, run ##72786# to reactivate, update PRL and PROFILE, and see if that helps. Also, if you need 4G LTE and it's not coming up, and you know you're in a 4g area, then toggle airplane mode and it should re-lock into 4g once you turn airplane mode off. Good luck.

jdsingle76 said:
@roirraW "edor" ehT may be right. There are no 4.4.3 or 4.4.4 radios for the SIII. Did you flash ROMs that were AOSP that were "4.4.3" or "4.4.4"? If so, you didn't change your modem, because they don't flash modems. You were still on the 4.4.2 modem. With the SIII, there is no way to disable the bands. Tri-band is out for the S5, which if you have your MSL you can disable different bands, but if you go into your ##DATA# settings for the SIII, it's simply LTE enabled/disabled. What you may want to try is flash back to complete stock, run ##72786# to reactivate, update PRL and PROFILE, and see if that helps. Also, if you need 4G LTE and it's not coming up, and you know you're in a 4g area, then toggle airplane mode and it should re-lock into 4g once you turn airplane mode off. Good luck.
Click to expand...
Click to collapse
That is probably what happened. I had no idea which radio I was on, but getting the ND8 radio fixed the issue.
Thanks!

[Q] Time to update ROM with Knox bit tripped, how to avoid a brick

So back in December while updating to the newest version of MOAR, I made this mistake of taking the OTA update and getting Knox. I managed not to brick my phone at the time, but ended up with the Knox bit tripped and a lot of concern that further experimenting would result in a dead phone and a forced replacement. Anyway, fast forward to now and its time to update again (some apps are starting to get unstable because they have been updated but my ROM hasn't), but I want to make sure I don't risk bricking the phone thanks to Knox.
If I remember correctly, the fact that I'd contracted Knox and tripped the bit already meant that I was stuck with the same bootloader, but I could update everything else. Is this still the case, or has someone figured a way around the issue in the past six months so that I can get rid of Knox once and for all? Also, since I haven't looked at any of this in the last 7 months, what exactly would the process be to update to the newest version of MOAR without updating the bootloader (if that's still what needs to happen)?
Thanks

You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

roirraW "edor" ehT said:
You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this

treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
Yes, you can upgrade everything.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
The problem is the way in which those issues manifested. Samsung essentially slipped Knox into the update almost without warning and with virtually no documentation. As a result many of those who were affected found out about it as a result of a bricked phone which was now permanently marked as ineligible for warranty work. Had Samsung made it clear what Knox was capable of and provided proper documentation of its function then I don't think many people would have had any problems with it.
Sent from my SPH-L710 using XDA Free mobile app

Getting late notifications after KK

I installed the OTA 4.4.2 stock rom from the forums and ever since my notifications come sometimes hours later. I don't have cell service and haven't for awhile. I leave the phone on airplane mode but with wifi turned on. It's the same way I used it under Jellybean. However now I have to often open up Hangouts and Google Voice to check manually for messages. If I don't I'll sometimes get notifications of new messages 1 to 6 hours after the message was sent.
Even opening up the app and checking sometimes won't force me to get new messages. If I hit the refresh button on Google voice about 3 times then sometimes it'll force it to finally receive the message.
Wifi works fine though, I can surf the web, stream music, watch youtube, update apps perfectly. Never have a hiccup or stutter and never had this issue until I updated to KK. Before I flashed KK, I did a backup of my apps with Helium and restored them. I wondered if that could be the problem. Not sure why it would effect the messages I receive on Hangouts or Google Voice and nothing else though.
This is the rom and procedure I used, going from stock 4.3 rooted to KK.
http://forum.xda-developers.com/showthread.php?t=2738533

Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

roirraW "edor" ehT said:
Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks for the reply, I thought I had notifications setup for this thread, but I guess not. Anyways in the past 4 days I've flashed 2 different KK roms and still having the same issue. I've used Philz wipe and install option both times. I used a stock rooted rom first, and after a day of using it I still am not getting my notifications for Hangouts. I used another custom KK rom from the forum and flashed it as well using Philz wipe and install.
I've left the roms stock on both installs, except for signing into my Google account and letting the apps update. I'll send myself test messages and wait sometimes even an hour and not get any notification until I manually open the app and even then sometimes I cannot get it to load the message. Yet the internet connection is working and I can check email and browse websites without issue. The only way I can get it to load up any new messages is to reboot.
I want to try going back to Jellybean just to see if I'll have the same issue. Now that I've gone to KK though, is it possible for me to downgrade back to Jellybean? I know I've seen threads in the past saying downgrading will brick the device.

You can flash any ROM made for our SPH-L710 that you want without bricking. You just can't ever Odin anything older than ND8 or NDC.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

[Q] Can't receive sms after flashing stock

Hello everyone,
So ill start out telling you my long journey through the numerous roms I've flashed.
First flashed cm11 4.4.2, then to 4.4.3. Nothing out of the ordinary.
Next flashed liquid smooth 4.4.4, nothing else was wrong until I noticed my calls took
a while to connect. Then I got multiple and duplicate sms messages all at once that were usually late.
So I tried to restore my first cm11 backup, then I started to lose all texting ability. So I tried to revert back to
stock and unroot. Success
Now everything works fine (calls, data, sending sms etc.) But I still can't receive any text messages.
I am running the stock 4.4.2 Rom from Seminole with no root access. I've contacted sprint and gone
through all of those hoops to no avail. Is there a way to fix this? I would greatly appreciate any help..
Thanks

derder764 said:
Hello everyone,
So ill start out telling you my long journey through the numerous roms I've flashed.
First flashed cm11 4.4.2, then to 4.4.3. Nothing out of the ordinary.
Next flashed liquid smooth 4.4.4, nothing else was wrong until I noticed my calls took
a while to connect. Then I got multiple and duplicate sms messages all at once that were usually late.
So I tried to restore my first cm11 backup, then I started to lose all texting ability. So I tried to revert back to
stock and unroot. Success
Now everything works fine (calls, data, sending sms etc.) But I still can't receive any text messages.
I am running the stock 4.4.2 Rom from Seminole with no root access. I've contacted sprint and gone
through all of those hoops to no avail. Is there a way to fix this? I would greatly appreciate any help..
Thanks
Click to expand...
Click to collapse
did you flash the ND8 stock tar via Odin??

6th_Hokage said:
did you flash the ND8 stock tar via Odin??
Click to expand...
Click to collapse
I flashed the stick 4.4.2 from the Sam mobile site for the sph-l710. Ill see
how the nd 8 does.

6th_Hokage said:
did you flash the ND8 stock tar via Odin??
Click to expand...
Click to collapse
I flashed nd8 and the problem still persists. The thing is when I swapped phones with somone else on my plan I could text and I was able to get rel lies. Then I put my number back on the galaxy s3 and AGAIN no replies..
Any idea?

I don't know if this would help this particular problem, but did you try on a stock ROM in the stock dialer:
##72786#
Then when it finishes, update PRL and Profile from Settings / More /About Device
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

roirraW "edor" ehT said:
I don't know if this would help this particular problem, but did you try on a stock ROM in the stock dialer:
##72786#
Then when it finishes, update PRL and Profile from Settings / More /About Device
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks, I did that a couple times with sprint. Each time I ask for help they transfer me to another tech...
Ill try again though. Is it possible that flashing one of my previous roms caused the Id on my phone to change?