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/

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!

I've tried everything - someone please help

The Core Prime will not boot into recovery, or safe mode, or to the home screen. The only way to sometimes get it into download mode is leave it plugged into the wall charger for a couple minutes, then it will SOMETIMES go into download mode to charge. Holding down every combination of keys does not work, please don't suggest holding down keys.
All I ever see is a mmc confirmation fail movinand checksum confirmation fail error no matter what I try. I never see the Samsung intro, boot intro, or tracfone intro anymore, just a black screen that leads to that error message in red letters.
Regardless of which computer or cable I use, Windows never sees the phone. Doesn't try to install the drivers, doesn't make a sound that something was plugged in, nothing shows up in device manager, nothing (even in download mode)
I called 800 Samsung (4 times asking the same thing to different people to make sure I didn't just get helped by a noob over the phone). I went and talked to the Samsung guys inside worst buy (didn't do anything except informing me there is a Samsung store in LA). I called the Samsung store in LA and talked to a technician and the technician supervisor (I could drive there if their answer wasn't factory reset)
But EVERYONE from Samsung is saying all that can be done is factory reset.
I do not need a factory reset. I need my data.
I have posted numerous threads, and even though there was good advice given, none of it worked.
All I did before this error was try to update Google maps. The phone has never been backed up/rooted/nothing its stock.
At this point, I'm willing to negotiate paying someone to get my data back.
Someone please help.

Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ?? hope to be helped you .

The x man said:
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ���� hope to be helped you .
Click to expand...
Click to collapse
Thank you for trying to help me. I do not yet have a Linux box set up. Can you recommend a distro, version, or live cd of Linux to use?

You can use Ubuntu 14.04

The x man said:
You can use Ubuntu 14.04
Click to expand...
Click to collapse
I will post my results here as soon as I try

If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.

AJOKER21 said:
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
Click to expand...
Click to collapse
Core prime model is also G-360* (main number) not just SM-820L .

The x man said:
Core prime model is also G-360* (main number) not just SM-820L .
Click to expand...
Click to collapse
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.

AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
Never mind i just wanted to share info. + mine reply was before twrp or cwm being ported to core prime ,and at this time no custom roms for 360* Models

Is TWRP ported to other versions of this phone? It seems like it is atleast the VE one has it and my TracFone version does I'm sure most of the others ones do and you also do not need a Custom ROM just a stock one which is probably floating around out there somewhere. For the OPs phone which if the model was posted this would be a billion times easier. So Mr. OP please post your model for us to help if your issue is still happening.

G360 Rom
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
I have a SM-S820L that i flashed with a 360 and now its bricked

Hii @android_n this is also happen with me on My core 2 G355H I also try to flash Offical frimware but it only boot for few second and shut down
I replace battery with new one and it booted
Problem is in battery it only boot when charger is connect or you can charge your phone battery by booster charger hit thanks if I help

I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed

noxqes said:
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
Click to expand...
Click to collapse
Check out this thread here http://forum.xda-developers.com/gal...stock-rom-deodex-busybox-root-t3378999/page1. Hope this helps
Sent from my SM-G360T1 using XDA Labs

900V stuck in bootloop after FW upgrade

My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!

RetroRider said:
My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
Click to expand...
Click to collapse
I have not tried the first method so I cannot say if it will work for a stock debrick. If you are going to use that, make sure the phone is on a PB1/PD1 firmware.
The second one is rooting the phone. I have usedthis one with both CIDs and have had no issues. Since the phone wont boot, you might not be able to locate the CID, so please read the following thread before starting:
https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
UPDATE: Also, Here is a link to a firmware with the pit file:
https://forum.xda-developers.com/ve...rmware-pit-verizon-samsung-galaxy-s5-t3757416
You may want to try that first before doing the other ones. Having a pit file during the firmware install sometimes helps to fix it.
Try it, see if it works, if you have any more issues, let me know.
Good Luck!

Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again

RetroRider said:
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
Click to expand...
Click to collapse
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.

Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....

RetroRider said:
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
Click to expand...
Click to collapse
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
Ibuprophen said:
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
here's what I see when I go into download mode:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
Is there anything there that tells me what version of firmware I should be using?

RetroRider said:
Is there anything there that tells me what version of firmware I should be using?
Click to expand...
Click to collapse
Product name is correct.
I'd flash this one: https://androidfilehost.com/?fid=818070582850486654
It's the latest firmware with full-wipe.
The first boot should take 12-15 min.
If the phone does not boot within 20 min. it will mean a hardware problem.

Note 4 boot loop (no acces to recovery)

Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience

Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?

Mufrad said:
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Click to expand...
Click to collapse
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)

Altrath said:
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Click to expand...
Click to collapse
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.

Altrath said:
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Click to expand...
Click to collapse
Mate, the 910F is a Snapdragon - famous for it's eMMc problem. You may search about this and get more info.
In short, there's a big chance it's not going to get to work again.
Sorry for your loss.

The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?

Mufrad said:
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Click to expand...
Click to collapse
btw flashing TWRP or any recovery doesn't work so i'm pretty sure it's the eMMc chip

If it really is your eMMC chip, you are better off trying to get a new device. The eMMC chip isn't removable without a lot of time, effort and risks. Also you'll need a head Gun or something and a new identical chip that will cost you a new device worth.

Altrath said:
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Click to expand...
Click to collapse
try
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448