Database Users

[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] Stuck in boot animation-Can't mount \data after KK update with odinPc

Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance

have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77

Hundsbuah said:
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?

Contruk27 said:
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Click to expand...
Click to collapse
Did you try it with different Odin versions?

Pierre118 said:
Did you try it with different Odin versions?
Click to expand...
Click to collapse
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!

Contruk27 said:
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Click to expand...
Click to collapse
No problem. Let us know the result.

I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...

ultramag69 said:
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
Click to expand...
Click to collapse
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...

Contruk27 said:
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Click to expand...
Click to collapse
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....

ultramag69 said:
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
Click to expand...
Click to collapse
It's going to be difficult that someone has it, since most people prefer 1 file roms. I will pray to sammobile haha
I'm not an expert, so I don't know if it's something critical for the phone (data mounted) to boot, but whenever I had this problem before with my previous phones, I was able to fix it by flashing a sock rom with odin or going back to the previous rom. So, my main concern now is that after all the flashing I've made, I still can't mount \data.

Help please

Hello everyone i have a note 3 and it is rooted and has a a kernel flashed on it, now i want to revert back to my stock rom and i know i have to download the software and flash it with odin but i cant find my software anywhere could anyone give me a link to the firmware for my specific device here are its details
build number: N9005XXUDMJ7
CSC:N9005DTUDMJ4
NAME:NOTE 3 N9005
PLEASE HELP ME I WOULD BE REALLY GRATE-FULL TO THE PERSN WHO CAN LEND ME THE LINK I TRIED FLASHING A STOCK ROM WITH A SAME BUILD NUMBER BUT DIFFERENT CSC AND IT WAS A FAIL LUCKILY MY DEVICE STILL WORKS BUT I REALLY WANT TO GO BACK TO STOCK PLEASE. THANKYOU

go to sammobile.com and search for your model there

kewlkaka1203 said:
Hello everyone i have a note 3 and it is rooted and has a a kernel flashed on it, now i want to revert back to my stock rom and i know i have to download the software and flash it with odin but i cant find my software anywhere could anyone give me a link to the firmware for my specific device here are its details
build number: N9005XXUDMJ7
CSC:N9005DTUDMJ4
NAME:NOTE 3 N9005
PLEASE HELP ME I WOULD BE REALLY GRATE-FULL TO THE PERSN WHO CAN LEND ME THE LINK I TRIED FLASHING A STOCK ROM WITH A SAME BUILD NUMBER BUT DIFFERENT CSC AND IT WAS A FAIL LUCKILY MY DEVICE STILL WORKS BUT I REALLY WANT TO GO BACK TO STOCK PLEASE. THANKYOU
Click to expand...
Click to collapse
Install app called "phone Info" from google store, it will take you to correct firmware as per your country origin.

kewlkaka1203 said:
I TRIED FLASHING A STOCK ROM WITH A SAME BUILD NUMBER BUT DIFFERENT CSC AND IT WAS A FAIL LUCKILY MY DEVICE STILL WORKS
Click to expand...
Click to collapse
That shouldn't have failed, CSC mismatch is not a cause of flash failure. Can you provide more details?

Hm...
Hi guys,
I had an issue similar to this and have no recollection what I did to fix it. I don't even think that I fixed it, ever. Meaning - no stock ROM install for me for months and months now.
I just downloaded some AOSP/TW ROM and flashed. Are you able to get to the custom recovery? Please confirm - I've read somewhere that you can flash stock from custom recovery. I did try a few "PIT" files, with no help.
P.S. I remembered a bit now. I was finally able to flash it through Odin, but entered boot loop. So, no go!
My eyes are on this thread.
Good luck,
Sonny B.

details↓↓↓↓
Bulbous said:
That shouldn't have failed, CSC mismatch is not a cause of flash failure. Can you provide more details?
Click to expand...
Click to collapse
Um sorry for the late reply. So what happens is i down the firmware from sammobile sure that it was for my model and build number but the csc was of switzerland different than mine next i flashed the rom from 3 different versions of odin starting from v.3.10 it started saying checking md5 file and it was taking too long and we had lost hope then suddenly it said md5 read succesfully and then brought up another dialouge saying setup connection and then cam up with a fail message usb debugging and all the process was done correctly i know this is a late reply but please reply back if you are there thanks

if....
sonny_b_bih said:
Hi guys,
I had an issue similar to this and have no recollection what I did to fix it. I don't even think that I fixed it, ever. Meaning - no stock ROM install for me for months and months now.
I just downloaded some AOSP/TW ROM and flashed. Are you able to get to the custom recovery? Please confirm - I've read somewhere that you can flash stock from custom recovery. I did try a few "PIT" files, with no help.
P.S. I remembered a bit now. I was finally able to flash it through Odin, but entered boot loop. So, no go!
My eyes are on this thread.
Good luck,
Sonny B.
Click to expand...
Click to collapse
If it was a pass message on odin it shouldve worked go into recovery mode and do a factory reset from there it should work it happened with me too but remember dont leave the phone switched on as its stuck in boot loop cause when the powers dead ur phone wont charge any more it would keep thinking as if its not bieng charged if thats what u did i recommend making a factory cable search it on google and charge from that so the device knows its bieng charged once the wipe data is done reset and hopefully it would work if not i think u should flash another stock rom again i hope i helped

kewlkaka1203 said:
If it was a pass message on odin it shouldve worked go into recovery mode and do a factory reset from there it should work it happened with me too but remember dont leave the phone switched on as its stuck in boot loop cause when the powers dead ur phone wont charge any more it would keep thinking as if its not bieng charged if thats what u did i recommend making a factory cable search it on google and charge from that so the device knows its bieng charged once the wipe data is done reset and hopefully it would work if not i think u should flash another stock rom again i hope i helped
Click to expand...
Click to collapse
Did you solve ur problem?

........
Joku1981 said:
Did you solve ur problem?
Click to expand...
Click to collapse
NO

Hi guys ,
There're three possibilities about the country origin by comparing the data on sammobile.You can try to flash these three versions firmwares.one of them must be correct! Portugal PDA:N9005XXUDMJ7 CSC:N9005OPTDMJ4 SLOVENIA PDA:N9005XXUDMJ7 CSC:N9005OXXDMJ4 POLAND PDA:N9005XXUDMJ7 CSC:N9005PRTDMJ4.download link is also on sammobile.com!
Good luck!
Sent from my SM-N9005 using XDA Free mobile app

Install Phone INFO ★Samsung★ app > Menu > 'Firmware Browser'. Download the firmware for your device and flash it via Odin.

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!

Wifi and Bluetooth Problem!

Flashed Phoenix,used several days,suddenly wifi disconnected then in a few seconds connected again,it looped and I rebooted to find wifi isn't working at all,stuck at opening and grey button.
Then I flashed back to morphose,still the same.
So I flashed via Odin the latest Chinese official firmware(ZC???OH2) with 11G pit.This time I got about 15 mins of stable connection.After that the problem occurred again,exactly the same.:crying::crying:
Below is what I have done:
Pressing around the sdcard (it is said to be where the wifi chip is located,and it maybe caused by poor contact)
Reboot a thousand times
Changing kernel(kingz,stock,voltaqe)
Wiping cache and Dalvik
Mortifying build.prop to ro.securestorage.support (maybe not exact)from true to false(said to be a solution)

Forgot to mention :
1.the firmware was a repair firmware(five .md5 files)
2.in that firmware not only wifi but also Bluetooth fails to open

Download the latest single tar.md5 file from sammobile.com or updato.com and flash again. Don't forgot to perform a factory reset from stock recovery before letting the stock ROM boot for the first time.

audit13 said:
Download the latest single tar.md5 file from sammobile.com or updato.com and flash again. Don't forgot to perform a factory reset from stock recovery before letting the stock ROM boot for the first time.
Click to expand...
Click to collapse
Thanks for your reply
Should it be 8gb pit or 11gb?
And should it be my region or just the latest firmware no matter from where?

Flash the version for the region that the phone was made for.
Pit file is not needed unless Odin can't read the phone partition information.

audit13 said:
Flash the version for the region that the phone was made for.
Pit file is not needed unless Odin can't read the phone partition information.
Click to expand...
Click to collapse
Sorry for bothering again,but i found it was made for Europe.On updato there seems to be no region "europe",only Germany.So which one shall i flash?
Thanks in advance☺

You can try one for Germany. If it is not made for your phone, Odin will halt the flash process.

audit13 said:
You can try one for Germany. If it is not made for your phone, Odin will halt the flash process.
Click to expand...
Click to collapse
I began to wonder if it is correct that the device is European,for it was bought in offical China mainland market?But imei also showed that?
I am such a noob at coping with this kind of weird issue
Anyway i will download both ones and give a try in several days,the download speed is rather slow from updato:crying:
Sent from my Samsung Galaxy S4 using XDA Labs

Wait, if it was purchased in China, it's probably made for the Chinese market and will need the firmware version made for one of the Chinese carriers. Odin will not flash non-China firmware on a made-for-China phone.

audit13 said:
Wait, if it was purchased in China, it's probably made for the Chinese market and will need the firmware version made for one of the Chinese carriers. Odin will not flash non-China firmware on a made-for-China phone.
Click to expand...
Click to collapse
Attachment is my imei searching result,it is shown made for Europe.Besides,I remember flashing other region firmwares and booted normally
And with China baseband I have very bad signal but after flashing other ones it is far better...so I guess it might be a phone wrongly sent to China market or something like that?
The connection to updato is so unstable that I still haven't finished downloading?
Edit:screenshots removed

Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.

audit13 said:
Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.
Click to expand...
Click to collapse
No,still no luck at all,wlan still does not work...Whats more in germany firmware i also get "com.android.media has stopped"
This is killing me,my network provider uses TD-SCDMA for 3G,but i9500 don't support that,so i can only use EDGE network,which is extremely slow.Anyway maybe I'll get another phone next month:victory:

audit13 said:
Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.
Click to expand...
Click to collapse
Finally discovered something new.I am on miui8,when charging to 100％ wifi connects,and it wont disconnect even unplug the cable until you do a reboot!Dont know if it works on other roms,but it does throw new light on the issue.
But...how does this happen?

This is very strange. I've never come across this situation with any phone.

audit13 said:
This is very strange. I've never come across this situation with any phone.
Click to expand...
Click to collapse
Thank you!It is said that Wifi and bluetooth are on the same chip,so if bluetooth is now always working even wifi is broken then it cannot be a hardware failure,can it?

It could be a hardware failure but now I'm not sure since you got it to work on a custom ROM.

audit13 said:
It could be a hardware failure but now I'm not sure since you got it to work on a custom ROM.
Click to expand...
Click to collapse
After testing for an afternoon I discovered:
Wifi will be unable to use the moment battery drops to 81%,it doesnt turns off,but simply shows no item in the list.
If I plug the charger and restart wifi,then it works properly.
If I restart wifi without charging,wifi will be stuck and I have to charge then reboot the phone to get it on again.

Wow, this is even more strange.
Do you have a cell repair shop that can diagnose it for you?

audit13 said:
Wow, this is even more strange.
Do you have a cell repair shop that can diagnose it for you?
Click to expand...
Click to collapse
Yeah,but i'd rather get a new phone if it takes much time or money to repair it.The phone is still my daily driver,though i love it,it is indeed out of date,plus the problem.Getting something like a Redmi 5A might be a better choice?Moreover the rom is not that stable,battery life is also poor,but i dare not flash another rom for fear that wifi gets totally broken.
Thanks again for your time?

In this case, have you looked into getting a used motherboard?
I'm not sure where you are located but there is a big market in my city for used phones. When I need a motherboard, I look for people selling phones with smashed screens and working internal components.