Database Users

[Q] Bricked my At&t galaxy s iii

So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?

anonymous78 said:
So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?
Click to expand...
Click to collapse
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.

NightSkylar said:
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.
Click to expand...
Click to collapse
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?

anonymous78 said:
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?
Click to expand...
Click to collapse
Its rare that you would have to use a PIT File, mostly for the fact that it can mess up the bootloader.
As you have performed a soft brick, you likely do not have CWM, thus you cannot flash any custom firmware. *
My advice would be to wait to see if someone will upload the stock firmware for your model. I would also visit AT&T and say that your phone suffered a software crash.
:good:
* However, it is possible to flash a custom ROM if they can be flashed VIA ODIN, such as the CM9 Resurrection edition. (Does not exist for the AT&T Edition just yet)

I considered going into the store and playing dumb, but I heard they just replace the phone on the spot and sometimes later check the bricked phone before fixing it. I don't want to risk receiving a $600 bill in two weeks.
Can they tell the difference in my case?

I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?

NightSkylar said:
I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?
Click to expand...
Click to collapse
Product name: SGH-I747
Custom Binary download: yes(3 counts)
Current Binary: Custom
System Status: Official

In this case, as it is a custom Binary, it would most likely void your warranty. However, if they do not know how to check, then you should be good

So I went down to the at&t store and they couldn't do anything without sending it to tech or having them come in or something. She also said that if the warranty is void they won't do anything, not even for a fee.
I suppose I'll have to activate my old phone until the rom is released.

I'm sorry to hear that mate, but no worries, it wont be long till someone post's the official stock firmware

I hope you had taken a efs backup before this blunder.
Sent from my GT-I9300 using XDA

Man, I feel for you but just got to be patient with things like this. You're performing something that can and will damage your phone if you don't read the directions.
Sent from my GT-I9300 using xda app-developers app

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

Mystery Frankenstien S4 Multiple Errors and Inconsistencies

I've got a strange S4 on my hands. Its stock 4.4.2 was reporting it as i9505, international S4 LTE version.
However the download mode is reporting it as SPH-L720. Nvm, just a little hiccup I thought, let's go ahead.
I managed to get it to root and install TWRP 3.0.1.0 S4 LTE version. However after this it started throwing the Recovery is not SELinux enforcing error. It was still booting fine however. Could enter both S4 Stock rom and TWRP.
I wiped its data, cache, dalvik, and system, formatted to F2FS. So far so good. Installed AOSP 6 by JD Team, installed stock GApps. Booted straight into
Great. Everything's working perfect. Now I inserted my sim and whoop-de-doo. Sim shows up in home menu, but no antenna activity.
That's strange, why isn't it working? I thought the modem firmware was out of date or incompatible with Android M. Decided to find the latest FW matching my modem description and flash it.
Except, this is what showed up in the data I'd taken care to gather before beginning anything:
Model Number: GT-I9505
Baseband version: I9505OLBFNB4
Build Number: KOT49H.V1
AP: I9505XXUBFNB7
CP: I9505OLBFNB4
CSC: I9505DXUFNB3
Found a firmware I thought matched and flashed it. Rebooted, and suddenly phone won't boot at all.
Can't find a firmware now. PIT's gone. Phone is showing "SECURE FAIL: KERNEL" and "System software not authorized b Samsung has been found on your phone" on normal power on where it refuses to boot at all. Can't access TWRP either.
I can still go into Download mode and Odin can still access the phone.
I'm completely lost with how to proceed with this now however. Phone model numbers do not match anything, PIT gone, TWRP gone, serial numbers do not match anything, Kies refuses to initialize the phone, etc etc.
Any help would be welcome. I had opened over 50 tabs before I suddenly lost heart and closed all of them and took to writing this post. Thanks for reading.
EDIT: Further checking the IMEI shows the phone is actually a i9500 according to SNDeep.com. This just keeps getting worse.

if you bought this from a second hand from a phone shop it's state is down them not having a clue what they are doing and flashing firmware onto it. pretty much everyone here has the not enforcing SEandroid on recovery and kernel it's nothing to worry about.
AOSP 6.0.1 is almost a unified rom so it works with all but a few variants of s4, the problem is whatever you tried to flash after that, you didn't mention what that was. but it's kinda beside the point now.
when you enter download mode whatever model it mentions there is the firmware want to download and flash via odin.

3mel said:
if you bought this from a second hand from a phone shop it's state is down them not having a clue what they are doing and flashing firmware onto it. pretty much everyone here has the not enforcing SEandroid on recovery and kernel it's nothing to worry about.
AOSP 6.0.1 is almost a unified rom so it works with all but a few variants of s4, the problem is whatever you tried to flash after that, you didn't mention what that was. but it's kinda beside the point now.
when you enter download mode whatever model it mentions there is the firmware want to download and flash via odin.
Click to expand...
Click to collapse
I flashed a MDCModemOnly version of the CP firmware. Since the phone said its a SPH-L720, I thought the latest unlocked European rom would fix the antenna problems.
Clearly I screwed that up.

blackroseblade said:
I flashed a MDCModemOnly version of the CP firmware. Since the phone said its a SPH-L720, I thought the latest unlocked European rom would fix the antenna problems.
Clearly I screwed that up.
Click to expand...
Click to collapse
The SPH-L720 is a Sprint S4. So you'll have to flash that firmware. I believe sprint is a US carrier only, is that right?
So it's a CDMA (or CMDA?) device I guess. That means it uses different frequencies to connect to the network. I'm not really sure what I saying, lol. I just know that GSM and CDMA are a bit different when it comes to network connectivity.

GDReaper said:
The SPH-L720 is a Sprint S4. So you'll have to flash that firmware. I believe sprint is a US carrier only, is that right?
So it's a CDMA (or CMDA?) device I guess. That means it uses different frequencies to connect to the network. I'm not really sure what I saying, lol. I just know that GSM and CDMA are a bit different when it comes to network connectivity.
Click to expand...
Click to collapse
Won't flashing the original firmware lock my bootloader back to sprint?

blackroseblade said:
Won't flashing the original firmware lock my bootloader back to sprint?
Click to expand...
Click to collapse
Sprint, as far as I know, don't lock the bootloaders. Only AT&T and Verizon do.
Here you have the CF Auto root thread for the SPH-L720 if you still are concerned.

Is there any place to download the firmware aside from sammobile.com? They're demanding I pay them to download a firmware at more than 15kb/s!

blackroseblade said:
Is there any place to download the firmware aside from sammobile.com? They're demanding I pay them to download a firmware at more than 15kb/s!
Click to expand...
Click to collapse
You could try SamFirm. It's a tool for downloading Samsung firmwares, but it requires some info about the phone and, since you can't boot up, it will be hard to get.

GDReaper said:
You could try SamFirm. It's a tool for downloading Samsung firmwares, but it requires some info about the phone and, since you can't boot up, it will be hard to get.
Click to expand...
Click to collapse
Wow, thanks, that worked like a charm! Already had pulled my PDA, CP and CSC, knew the region and Downloading mode reported SPH-L720.
Currently downloading at 400kB/s.

Voila! Works. Stock SGS4 5 installed, only Knox Warranty set to 0x1, everything else's fine.
I've already rooted the phone with cf-auto-root and Odin, installed TWRP Manager, now what?
TWRP manager is asking me to install Busybox, should I do that? I'm attempting to install TWRP recovery and flash JDCTeam's AOSP 6.

blackroseblade said:
Voila! Works. Stock SGS4 5 installed, only Knox Warranty set to 0x1, everything else's fine.
I've already rooted the phone with cf-auto-root and Odin, installed TWRP Manager, now what?
TWRP manager is asking me to install Busybox, should I do that? I'm attempting to install TWRP recovery and flash JDCTeam's AOSP 6.
Click to expand...
Click to collapse
TWRP can be flashed with Odin or with an app called Flashify.
I recommend the Odin method.
But if you want to install it with TWRP manager, there is no harm in that. But you do need to install busybox. Just follow the app's prompts.

Followed your advice, installed TWRP 2.8.4 via Odin, upgraded it via TWRP to 3.0.1.0.
Following this I've tried installing JDCTeam's AOSP 6.0.1 again. However, my cellular network has been deactivated. AGAIN.
Now what?
EDIT: My baseband is reporting L720VPUGOK3 according to the current ROM.

blackroseblade said:
Followed your advice, installed TWRP 2.8.4 via Odin, upgraded it via TWRP to 3.0.1.0.
Following this I've tried installing JDCTeam's AOSP 6.0.1 again. However, my cellular network has been deactivated. AGAIN.
Now what?
EDIT: My baseband is reporting L720VPUGOK3 according to the current ROM.
Click to expand...
Click to collapse
Is that the most recent?
It could be caused by the fact that the phone was repaired with mismatched parts.
Or kernel related. They have a stock aosp kernel that you can flash. Try with that.

GDReaper said:
Is that the most recent?
It could be caused by the fact that the phone was repaired with mismatched parts.
Or kernel related. They have a stock aosp kernel that you can flash. Try with that.
Click to expand...
Click to collapse
Flash it via ODIN's AP command?
EDIT: Yes, I believe so. It is the one that was returned as most recent by both Sammobile and Samtool, as well as according to official samsung releases.
EDIT 2: Flashed it via TWRP, no difference. Still no network.
I don't get it, this is odd. The team lists L720 as supported, and my phone is unlocked, after all I can use the default SGS4 stock ROM with my SIM and network, so why isn't it working on this?

blackroseblade said:
Flash it via ODIN's AP command?
Click to expand...
Click to collapse
No. It's done with TWRP.

GDReaper said:
No. It's done with TWRP.
Click to expand...
Click to collapse
I've done that, still not getting cellular however.
Baseband version was NB4 on the original rom. Moving it to latest stock SGS4 brought it up to OK3. That is what JDCTeam's AOSP6 is also reporting it as.

blackroseblade said:
I've done that, still not getting cellular however.
Baseband version was NB4 on the original rom. Moving it to latest stock SGS4 brought it up to OK3. That is what JDCTeam's AOSP6 is also reporting it as.
Click to expand...
Click to collapse
You can try and update the modem and bootloader even further, manually, via Odin.
There is a dedicated thread in the general section.
I don't think it will work, but it may be worth a try.

If I look further...
Phone Model = GT-I9505
Bootloader = SPH-L720
IMEI = a GT-I9500 phone
I think it's a GT-I9505 phone with SPH-L720 motherboard and IMEI that tampered from a GT-I9500 phone. Really, I would bring back this phone to the seller.
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
If I look further...
Phone Model = GT-I9505
Bootloader = SPH-L720
IMEI = a GT-I9500 phone
I think it's a GT-I9505 phone with SPH-L720 motherboard and IMEI that tampered from a GT-I9500 phone. Really, I would bring back this phone to the seller.
Click to expand...
Click to collapse
GDReaper said:
You can try and update the modem and bootloader even further, manually, via Odin.
There is a dedicated thread in the general section.
I don't think it will work, but it may be worth a try.
Click to expand...
Click to collapse
Exactly. Things are really weird with this. But returning this isn't an option. Phone belongs to a friend and he's been using it a while. Can't take this back now.
Also restoring to stock wiped out the international unlock. Phone is showing Sprint in top left corner.
Right now the phone is 101% stock 5.0.1. If anyone can please help guide me through unlock this permanently for all future foreseeable ROMs and flashes, please.

Managed to unlock it via the S4 Unlocker, following the instructions in that thread.
Still can't get 4G LTE to run on it like it was before, but can confirm 3G HSPA+ mode is working fine on it.

Samsung Go Prime, Unauthorized Software Notification Locked My Phone

Ok so I'm not sure where to put this thread and please forgive my bad grammar and punctuation if I have any. I already read some threads on this forum about a problem like mine and tried to follow the instructions to get back into my phone, but none of it worked so....
I have a Samsung Go Prime that I bought from Wal-Mart for around $100. I rooted it, and got the message "unauthorized software has been found on your phone, please take it to nearest AT&T etc etc". So I did just that, took it to AT&T, called up Samsung customer care on the phone, and took the phone to some sort of Samsung representative or worker person in Best Buy and nobody seems to be able to help me. I downloaded Odin and Philz Touch and tried to flash that and I kept getting Nand fail. I tried Kies and evidently Sammobile website doesn't seem to have the firmware I need either.
Somebody plleeeaassee help me. I had to pay another $100 just to get another phone so now I feel like I wasted $100 for a phone that wont work now. Maybe I didn't use Odin or Philz Touch firmware properly or didn't follow a certain instruction correctly at some point?
Any help would be massively appreciated.

Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk

marioca said:
Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I tried that and after clicking for it to start it again said something like "please check the serial number" etc like I put in the incorrect number. I'm pretty sure what I put in was the correct serial number. It was on the sticker under the battery....
model: SM-G530A
SN: R28H30GVPCN

I'm pretty sure your phone is bricked, nand fail was the superbrick error on the i9100 (Galaxy S2 Int) if I'm remembering correctly.
If I'm right, sorry man :/

Anybody know how to fix the nand fail? Anything I can flash to fix it?
When I tried to flash Philz Touch I read in one of the threads that I had to do something like putting the file in some kind of folder (might have been called tar tool) and click a certain batch.bat file. i tried that and nothing happened, so I just loaded the Philz Touch file directly into Odin.
Did I make a mistake somewhere? Is there anything at all that I can do to fix this? If not, then how and where would I find the contact info and address of the manufacturer so I can send the phone in for fixing?

Another boot loop problem please help

Hello
I searched the forums for similar problems but unfortunately couldn't find an answer to my specific questions so hopefully i can get some help here
Like the title says i have a problem with my phone (g900v)
it just keeps bootlooping and worst of all i cant even access the recovery menu
every time i tried that it says "recovery booting..." in blue letters but few seconds later the phone restarts again and again with the same results
its bootlooping at the samsung logo not verizon logo
One important thing to consider is that i dont know which android version the phone had before this problem since i got the phone from a co-worker and she doesn't know that info
This is What i tried so far:
I tried flashing the stock firmwares
G900VVRU1ANE9 android 4.4.2 and G900VVRU1ANK2 android 4.4.4
No luck odin gave me an error both times something about *FAIL! (Auth)
So then i jumped to this one
G900VVRU2DPF4 android 6.0.1
And everything went good according to odin but unfortunately the phone is still bootloping and no recovery menu either
So what about flashing a stock PF4 kernel to make sure it matches the firmware?
Do you think this could help?
Please let me know what you think any help would be appreciated
By the way if you think its worth a shot
do you know where can i download the kernel?
Im kind of looking myself but no luck so far
Thank you

Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.

bbsc said:
Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.
Click to expand...
Click to collapse
Ok sorry didn't know that but let me try your firmware and let you know what happens
Thank you for the quick reply

N.B. The first boot takes 10 min. or even more (but not more than 20 )
So be patient.
Good luck.

Unfortunately didn't work
same thing happened
it still looping at the samsung logo
I also tried the verizon Software Upgrade Assistant
i used the option to repair
It recognizes the phone in download mode and goes with the repairing process just fine
but at the end guess what? Yes still boot loping
So thats it then?
Is the phone beyond repair?
What about a bootloader flash is that even posible?
Flashing only the kernel
there is an option in odin to repartition
What about a new pit file?
Sorry im kind of newbie to this just throwing some ideas before i start salvaging the phone

Well, to clarify the things:
You've flashed that firmware successfully, waited for 20 min and there was no red verizon logo, right?
Asking because everybody understands "bootloop" in a different way.

bbsc said:
Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.
Click to expand...
Click to collapse
bbsc said:
Well, to clarify the things:
You've flashed that firmware successfully, waited for 20 min and there was no red verizon logo, right?
Asking because everybody understands "bootloop" in a different way.
Click to expand...
Click to collapse
Well like i said before according to odin yes everything flashed correctly
But no i didn't wait that long for the verizon logo to appear because the phone keeps restarting after the samsung logo usually after 18-20 seconds
From what I understand is that when you flash a new rom or do a factory reset the phone takes a long time to fully boot for the first time
but in this case the phone keeps restarting (boot loop)
The only difference that i see is that after flashing the firmware the phone is always trying to boot into recovery mode without success

I'm sorry, but I think it's a hardware problem caused by a defective EMMC (memory) chip in your phone.
It cannot be repaired by "flashing a bootloader" or something.
That firmware you've flashed already contains everything you asked about: bootloaders, modems, kernel, system, etc. It contains a proper pit-file too.
The difference you talk about caused by an attempt to reformat memory and execute so called "cache commands" before reboot which definitely was unsuccessful.
So, there's nothing more to do with Odin, sorry.
The EMMC chip can be replaced (in theory), but this operation requires a qualified person and complicated equipment. I'm afraid this procedure may be too expensive.
That's why, in my opinion, your choice is to swap the main logic board (motherboard) of the phone (if your phone still is in a good physical state and has a good display, certainly). It will cost you $25-35 if you do it yourself.
You'll need, say, this and this (I'd buy 2 or 3).
You'll also need to solve the problem how to disassemble the phone (remove the screen) because it's the most complex and dangerous part of work.

bbsc said:
I'm sorry, but I think it's a hardware problem caused by a defective EMMC (memory) chip in your phone.
It cannot be repaired by "flashing a bootloader" or something.
That firmware you've flashed already contains everything you asked about: bootloaders, modems, kernel, system, etc. It contains a proper pit-file too.
The difference you talk about caused by an attempt to reformat memory and execute so called "cache commands" before reboot which definitely was unsuccessful.
So, there's nothing more to do with Odin, sorry.
The EMMC chip can be replaced (in theory), but this operation requires a qualified person and complicated equipment. I'm afraid this procedure may be too expensive.
That's why, in my opinion, your choice is to swap the main logic board (motherboard) of the phone (if your phone still is in a good physical state and has a good display, certainly). It will cost you $25-35 if you do it yourself.
You'll need, say, this and this (I'd buy 2 or 3).
You'll also need to solve the problem how to disassemble the phone (remove the screen) because it's the most complex and dangerous part of work.
Click to expand...
Click to collapse
Yes i think youre right
i have been reading some other posts and info related to my problem and apparently it is going to be the emmc chip
I own another s5 with a cracked screen so im going to use this one for parts
Hey thank you very much for taking the time to help me

Molotov22 said:
I own another s5 with a cracked screen so im going to use this one for parts
Hey thank you very much for taking the time to help me
Click to expand...
Click to collapse
And definitely use it for training in LCD removing.
You're welcome.