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] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!

PIT File n910k note 4

Having major issues with my note 4.
I rooted the device with CF and had no problem, I think tried to install the CWM recovery and kept getting a FAIL in odin.
Tried different USB ports, different cables and 3 different computers.
I read to try unrooting then flashing recovery and then root again.
Once I unrooted the phone was stuck in a boot-loop and I still can't flash anything to the phone, not even CF-Root now, just bombs out with a fail.
I think I might need to re-partition the device, but need a PIT file for the note 4 please. All the phone displays now is a picture of a phone a yellow triangle and a computer, I have tried connecting kies but it says the phone is not supported, maybe because it is a korean model.
Thank you in advance

Ok starting to get massively confused now.
I have managed to flash the original firmware back to the phone, I can now do this everytime without fail via odin
But I cannot flash CF-Root or CWM recovery, everytime I get a fail error, even though i was able to flash CF-Root the other day.
Anyone got any ideas please, thank you in advance

Right I have sussed it, reactivation lock was enabled, disabled this and all working fine
Sent from my SM-G900F using Tapatalk

lysaer said:
Having major issues with my note 4.
I rooted the device with CF and had no problem, I think tried to install the CWM recovery and kept getting a FAIL in odin.
Tried different USB ports, different cables and 3 different computers.
I read to try unrooting then flashing recovery and then root again.
Once I unrooted the phone was stuck in a boot-loop and I still can't flash anything to the phone, not even CF-Root now, just bombs out with a fail.
I think I might need to re-partition the device, but need a PIT file for the note 4 please. All the phone displays now is a picture of a phone a yellow triangle and a computer, I have tried connecting kies but it says the phone is not supported, maybe because it is a korean model.
Thank you in advance
Click to expand...
Click to collapse
How do you manage to fix the bootloop without a pit file?

I got the original firmware from sammobile and flashed that
Sent from my SM-G925F using Tapatalk

lysaer said:
I got the original firmware from sammobile and flashed that
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Have you encounter "NAND write start" "FAIL"?

fannyman said:
Have you encounter "NAND write start" "FAIL"?
Click to expand...
Click to collapse
I did, but I cannot remember what I was trying to do at the time.
Are you flashing the original firmware from Samsung?
Sent from my SM-G925F using Tapatalk

Hello everyone. Can anyone help me to solution problem. I have Note 4 SM-N910K after unsuccessful attempts firmware via Smart Switch. I got error and no successful firmware. And want to back., but get fail via odin. I think i need pit file. If someone have just put link please. Thank's for advance.

[Q] ODIN stuck at Initialization step

hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..

awesim said:
hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..
Click to expand...
Click to collapse
Did you try to unzip the stock ROM to receive the .tar file for ODIN?

Joku1981 said:
Did you try to unzip the stock ROM to receive the .tar file for ODIN?
Click to expand...
Click to collapse
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..

awesim said:
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..
Click to expand...
Click to collapse
Change USB cable/port, other pc or close Kies 3 on the task bar.

It sounds more like a hardware failure.

Joku1981 said:
Change USB cable/port, other pc or close Kies 3 on the task bar.
Click to expand...
Click to collapse
Ive already tried changing USB ports.. I dont have Kies installed in the first place.. I'll try repeating the procedure on a different system though..

i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..

awesim said:
i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..
Click to expand...
Click to collapse
did you solve your problem?

jkamz said:
did you solve your problem?
Click to expand...
Click to collapse
I am also facing the same problem. Were you able to solve it.

no

Buy another motherboard.that solved my problem.There is no other work around

I'm also facing same issue

Bro's, gotta start somewhere, right!
The fact that you're phones are boot looping is actually a good sign - it means that they're not totally useless but salvageable.
Question: Are you able to boot into your custom recoveries, e.g. TWRP? If yes, please reply.
If no, kindly uninstall your old samsung driver, reboot pc, install new driver, put your phone into "Download mode", connect phone to pc, run Odin & hope for the best! If you can get passed this step, then it's smooth sailing...

jkamz said:
no
Click to expand...
Click to collapse
I'm having this issue with mine today, anyone able to resolve this without going true warranty?

Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.

audit13 said:
Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.
Click to expand...
Click to collapse
i'm facing the same problem with mine,any Fix??need help guys:crying::crying:

Odin is not working because the phone was not assigned a com port.

audit13 said:
Odin is not working because the phone was not assigned a com port.
Click to expand...
Click to collapse
He is right should be blue in com port is it latest Odin 10.7
Sent from my SM-A720F using Tapatalk

The obligatory obvious question here. Do you have the Samsung driver installed?

Just repartition the eMMC chip using .pit file with odin that it is suitable for galaxy S4 i9500.
If anyone has tried, please tell us, that it is work or not.
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Thanks!

Huh, i really bricked it! (SM-910F, endless recovery loop)

Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop

I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..

Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.

I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)

rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:

Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")

Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?

Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?

sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:

android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...

Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.

ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!