Samsung Go Prime, Unauthorized Software Notification Locked My Phone - Galaxy Grand Prime Q&A, Help & Troubleshooting

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?

Related

[Resolved via warranty] Phone bricked overnight and Re-Partition operation failed

Hello everyone,
Upon waking up this morning, I found that my phone was stuck on the (very first) Samsung logo. Before going to sleep, I was already booted and everything was stable.
I attempted to enter CWM recovery, but it would not work. It would continue to show the Samsung logo.
Entering download mode, I see the following -
Product name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
This is strange, and pretty wrong. My product name is empty, custom binary download is "No" instead of at least "3" (I never have used TriangleAway), and I wasn't using an official Samsung ROM before the problem.
The very first thing I tried was flashing the Siyah .tar file. I get this:
"<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed."
If I attempt to flash a full, multi-part .tar.md5 file in PDA, ODIN v3.04 shows a "There is no PIT partition." error and fails. Re-partition is not ticked.
Therefore, I've tried to flash each of the following, with re-partition ticked:
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
Each of them fail with a "Re-Partition operation failed." error.
If I try to flash a .pit file and the full .tar.md5, I get the same "Re-Partition operation failed." error. The same happens when I try to flash the .pit and Siyah at the same time.
Once a flash fails, I need to turn my phone off and on into download mode again, or else ODIN will stop on "<ID:0/004> SetupConnection.." and not continue for every type of flashing attempt.
The same thing happens for both ODIN v1.85 and v3.04, I've taken my battery in and out, I've tried this on two different computers, I've used every USB port, my Samsung drivers are up to date and Kies it not running in the background.
I've searched Google and XDA for hours, and I'm pretty sure the the problem I need to resolve is the "Re-Partition operation failed." error. However, almost no one on the internet has ever had this error.
The absolute very last abnormal thing I did with my phone was use the app "GetRIL" app as recommended on page 857 of the Siyah thread. The process said it succeeded, but the RIL didn't match the Baseband in the end. My phone was completely functional after, and I don't think the app even asked for root privileges at any point, so I'm not sure if it could have been capable of causing an issue this dire.
Is there anything I can do? I just can't imagine how my phone could have broken itself overnight while charging...
Any help would be greatly appreciated.
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Kangburra said:
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Click to expand...
Click to collapse
CWM is completely inaccessible!
I'll try a service centre after I've tried absolutely everything with this phone... I don't think I'm covered by warranty after rooting (Although they maybe won't be able to tell given how messed up the download mode seems to be right now)
Same problem here!
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
nicoroldan1 said:
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
Click to expand...
Click to collapse
If you can't get to recovery then you must return to Samsung.
Kangburra said:
If you can't get to recovery then you must return to Samsung.
Click to expand...
Click to collapse
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
nicoroldan1 said:
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
Click to expand...
Click to collapse
I don't know, it would depend on your terms of warranty.
If you are stuck you could try to unbrick it yourself.
Mine woke up to the exact same thing. Sadly I don't have a solution for you, this happened 1 week after being bought so I just had it replaced. I had not modified it in any way nor I tried any repair on my own (no reason to).
Sorry for your phone bro... id still try sending it to Samsung, if it's that screwed maybe they won't try to figure what happened.
Sent from my GT-I9300 using XDA Premium App
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
kart_y_26 said:
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
Click to expand...
Click to collapse
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
I would suppose the nand chips are damaged for whatever reasons, which makes a trip to the service center inevitable.
aegixnova said:
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
Click to expand...
Click to collapse
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
kart_y_26 said:
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It's a stock ICS taken from sammobile.
I've tried running ODIN v3.07 on my 32bit Windows 8 tablet, and my 64bit Windows 8 notebook across both 1.5.4 as well as 1.5.5 Samsung drivers, in both XP compatibility mode and default. Nothing.
Windows updates the drivers after my phone enters download mode, so I've tried flashing both before and after the driver download and installation. Same result.
I haven't tried running ODIN v3.07 on my Windows 7 computer (But I have for v3.04), so I'll give it a go later. I think I know what the result will be
I've given up, and will contact Samsung to get the phone repaired by them. I'll edit this post or bump the thread later with details of how the warranty was handled. I'm hoping that the end result will be favorable for me.
Thanks for the help, everyone. :good:
Same thing happend to me :/ Tried to flash PIT partition via odin again and it failed! Official service center voided my warranty. My phone is now at the unofficial service and i am waiting if it can be unbricked! He said if the phone gets to DL mode it should be OK!
Good luck buddy
Sent from my GT-I9300 using xda premium
I took my phone to an unofficial phone repair shop, 'Fonebiz'.
They replaced the entire phone circuit board within the hour, and Samsung was billed due to my phone still being under warranty. I don't know whether they were unknowledgeable of warranty checking procedures, uncaring of warranty procedures, or simply could not tell due to the extent of the phone's brokenness. Needless to say, I lost the contents of my internal SD, but thankfully most things were backed up.
Either way, I recommend unofficial repair centres which can be funded by Samsung, and my few days without the phone really let me appreciate the quality of the product and service I received.
I'm guessing that the problem was either a pure hardware fault, or Siyah kernel's dual-booting functionality messing up how partitions can be flashed to the phone. I'm not placing blame on anything, however.
I'm very pleased with both Samsung and the end result. :good:
I wish the very best of luck to everyone. This seems to be one of the few ways these solid phones can be bricked, and it's heartening to see that it can be resolved under warranty.
hey,
thanks for making this thread.
it is indeed devastating to find that other people experience my same problem and how they needed to replace the phone
i did nothing to my phone, no root, original firmware.
maybe dropped it once or twice but it worked fine afterwards for plenty of time.
last night i went to bed after putting it to charge as i usually do, while it was on and perfectly working.
this morning it was showing the s3 logo (weird thing is that the led was flashing as if the phone was still on and notifying about new emails)
then everything happens as in the OP
- no stock recovery abailable - reboot loop showing only the logo and nothing else
- normal boot stuck only showing the logo
- people haven't been mentioning this but: with the phone completely off, if i connect the charger it shows the battery empty with just the "in progress" circle and nothing else happens..
- download mode accessible but no "product name", and the unseen before "system status: custom"?
- what does that mean? anybod with a working s3 can tell us what they have in download mode? much appreciated
- all the while firmware is "samsung official" and custom binary is "no"
1. are people certain i cannot bring this back to life?
2. can anybody suggest a way to maybe retrieve at least some of my data?
3. warranty is a little tricky - bought on ebay.... anybody claim warranty in this situation? or have any pointers how to go about it?
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
DorinAlex said:
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
Click to expand...
Click to collapse
http://www.freesamsungrepairs.com/

[Q] Help a Noob please? Flashing the Stock ROM won't work

Hello, I am new to these forums as well as owning an Android device, and was directed here from Reddit when I posted my question there. to save time, I'll simply copy/paste my explanation of my predicament from Reddit, but if I seem to be leaving something out, please tell me so I can offer up as much information as I can.
"I've owned a Galaxy S5 for a little over 2 weeks, and for the past 4-5 Days, any time I try to Turn it on, I receive a message that says "Secure Fail: Modem", in red letters at the top left of the screen, and in the middle there is a yellow triangle with an exclamation point with the following text underneath "System software unauthorized by verizon has been detected on your device. please shut Down and go to the nearest verizon store" I'm 17, and currently staying at Governor's school, so I didn't have a ride until yesterday when my Dad and Uncle came to help me try to fix my phone. We went to the Verizon store, where they said that it looked at though I had tried to "root" the phone, which I haven't. My theory is that this is the result of a pokemon game I downloaded from the internet for an emulator. We Called tech support who couldn't help us, but after a little Research, I tried downloading Odin and flashing it with the Stock Rom, but every time I do that, I get the same Error message, regardless of whether I wipe the phone first, or Remove the sim card or whatever, so I don't know what I'm doing wrong and thought that maybe reddit could help me."
I've tried to flash the stock rom several times as per the following video: apparently I cannot link to outside content; however, the video is titled "How to Flash Stock Firmware for Galaxy S5 [All Variants] by Odin3" on youtube
if anyone could help me I would greatly appreciate it.
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted
Regelope said:
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted
Click to expand...
Click to collapse
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.
Misterxtc said:
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.
Click to expand...
Click to collapse
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over
Regelope said:
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over
Click to expand...
Click to collapse
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app
calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.
elliwigy said:
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.
Click to expand...
Click to collapse
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
Other than what I posted in the recovery thread and what I posted a few posts up that's pretty much it. You could try the nand erase all and efs clear options, check the screen shot and make sure your check boxes are correct. Also if you didn't download the files from the thread I posted I suggest you do. Honestly if none of what was already suggested doesn't work I would contact Samsung. I've had and seen your error before and successfully reset my phone before.
View attachment 2813604
Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app
elliwigy said:
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.
Regelope said:
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.
Click to expand...
Click to collapse
theres a soft brick (recoverable) and a hard brick (not recoverable).. normally a hard brick your phone wont come on or go into any mode at all.. soft brick is when it starts up but either bootloops or wont boot at all into the os (like yours).. im just lost as to why it wont work! crazy.. if u got at vzw and dont know what a dev edition is then u most likely have a retail s5 so mister odin guide should work..
Sent from my SM-G900V using XDA Premium HD app
johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Click to expand...
Click to collapse
Yea man it worked for me too. If you can get to stock recovery or Odin mode you should be able to do it. Factory reset and clear cache a whole bunch of times.
Just wanted to add I had the same error recently and tried everything. Nothing would fix
Seeing this twice in just a few days has me wondering if VZW has something buried in NK2 ...
I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.
radicalXace said:
I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.
Click to expand...
Click to collapse
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?
Rapunzl said:
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?
Click to expand...
Click to collapse
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.
radicalXace said:
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.
Click to expand...
Click to collapse
I couldn't even get my phone to start yesterday... just a black screen. I thought it was hard bricked. I did a chat with Samsung support, and they helped me recover in less than five minutes.
tr889 said:
Just wanted to add I had the same error recently and tried everything. Nothing would fix
Click to expand...
Click to collapse
I'm in the same boat. I've tried everything to get this issue resolved and I'm not having any luck.
Anyone know how I determine which tar file I should be using (NE9, NCG, etc)? I've got a SM-G900V and I think I've pretty much tried all of the tar files via this link - http://forum.xda-developers.com/showthread.php?t=2784880.

[Q] I would like some help.

Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?
nneely said:
Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?
Click to expand...
Click to collapse
You would be better off asking in your relevant forum, this is for the i9505
nneely said:
Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?
Click to expand...
Click to collapse
Just came across the below guide after searching a bit, have you tried this process yet? Or firstly have you tried downloading your full firmware from samsung-updates. com and manually flashed it through Odin?
http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
DSA said:
You would be better off asking in your relevant forum, this is for the i9505
Click to expand...
Click to collapse
sorry. i wasn't paying attention. I've moved a my thread to a different area
gsmyth said:
Just came across the below guide after searching a bit, have you tried this process yet? Or firstly have you tried downloading your full firmware from samsung-updates. com and manually flashed it through Odin?
i do realize im in the wrong forum area, but yes i tried the guide with kies and kies says that it can't update anything on my device
i've also tried full firmware updates and manually flashed through Odin and they fail every time.
Click to expand...
Click to collapse

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!

Samsung I9505 flashed with wrong firmware of another S4 model

First of all, thank you in advance for helping me!
I got an GT-I9505 for free because the guy didn't want it anymore, but there's a problem.
It's flashed with the rom of another S4 model, SGH-I337. Because of that some things don't work really well (WiFi don't work at all)
Trying to flash the correct rom with Odin, or with the rom on SD in the recovery menu, both fails.
Someone can give me some directions on this? I would really appreciate!
Thank you all!
Use the original cable and the rear USB ports.
Try every Windows and Odin version possible.
Flashing a stock ROM through the original recovery is not possible.
Boot into download mode and confirm that the model # is gt-i9505. What is the Odin error?
It shows "START [224, 1440]" in download mode, and Odin says "Can't open the specified file".
Yes, I have admin rights, the file is on a folder located on C:\stuff\, yes I have redownloaded the file, and shows the same error.
Boot into download mode and confirm that the model # is gt-i9505. What is the Odin error?
If my post was helpful, click the Thanks button
Click to expand...
Click to collapse
No point doing that, as I said it's flashed with the rom of a different model. In download mode shows SGH-I337 but thats incorrect. Behind the battery says i9505 and i'm pretty sure that it's correct, since it's the model sold on my country.
Thank you all!
-edit-
I managed to install ClockWorkMod using Odin to see if I could install it from there, but no luck...
iohanntachy said:
No point doing that, as I said it's flashed with the rom of a different model. In download mode shows SGH-I337 but thats incorrect. Behind the battery says i9505 and i'm pretty sure that it's correct, since it's the model sold on my country.
Click to expand...
Click to collapse
You're wrong.
That sticker can be easily replaced. You can put the sticker of an S7 on it, but that doesn't make an S7, does it?
Anyway, download mode is not affected in any way, shape or form, by a software change.
If download mode says it's that model, then it sure as hell is.
Pwnycorn said:
You're wrong.
That sticker can be easily replaced. You can put the sticker of an S7 on it, but that doesn't make an S7, does it?
Anyway, download mode is not affected in any way, shape or form, by a software change.
If download mode says it's that model, then it sure as hell is.
Click to expand...
Click to collapse
I had seen the phone before the guy that gave me mess it up.
It was I9505.
-edit-
I think I started to understand what is going on here...
Right now I noticed a really really small sticker that says "Serviço Técnico" (Technical Service) like a small warranty...
I think someone repaired this thing and replaced the main board! Is that possible...?
iohanntachy said:
I had seen the phone before the guy that gave me mess it up.
It was I9505.
-edit-
I think I started to understand what is going on here...
Right now I noticed a really really small sticker that says "Servi�o T�cnico" (Technical Service) like a small warranty...
I think someone repaired this thing and replaced the main board! Is that possible...?
Click to expand...
Click to collapse
Yes, it is possible.
As I said, no matter how many times you change the software, the model in download mode will not change.
Download mode is hard-coded. I'm pretty sure it's not possible (or very very hard) to change the info displayed there. So if it says it's a I337, then it is a I337.
Info in "About phone" or stickers can be easily changed or replaced with something else.
Looks like the phone is an i337 as I suspected which means you will need to flash the i337 rom via Odin or flash fire, depending on whether the bootloader is locked.
audit13 said:
Looks like the phone is an i337 as I suspected which means you will need to flash the i337 rom via Odin or flash fire, depending on whether the bootloader is locked.
Click to expand...
Click to collapse
He already has the correct ROM. He says it's a GT-I9505 flashed with a I337 ROM.
But download mode says it's a I337. So it means he has the correct ROM.
If the phone is flashed with the correct at&t rom, the wifi should work. The wifi may need a complete reflash to work or the wifi chip defective.
Thank you all for your time. How can I mark this as resolved?
I don't think you can. But you can change the title and add "Solved" to it or something.

Categories

Resources