Hi all,
I'm having a problem with my completely stock Note 2. It doesn't boot (stuck on logo), but I can access recovery and download modes. Recovery mode comes up with a lot of error messages (can't mount /efs, /system, /data or /cache - no such file or directory). Factory reset doesn't help either.
I tried flashing stock in Odin but that fails after "NAND Write Start ... Complete(Write) operation failed." Flashing the .pit file with it fails with "Re-Partition operation failed." I also tried with different versions of Odin, different USB ports, and different computers. What can I try next?
Any advice would be appreciated!
bubbleytea said:
Hi all,
I'm having a problem with my completely stock Note 2. It doesn't boot (stuck on logo), but I can access recovery and download modes. Recovery mode comes up with a lot of error messages (can't mount /efs, /system, /data or /cache - no such file or directory). Factory reset doesn't help either.
I tried flashing stock in Odin but that fails after "NAND Write Start ... Complete(Write) operation failed." Flashing the .pit file with it fails with "Re-Partition operation failed." I also tried with different versions of Odin, different USB ports, and different computers. What can I try next?
Any advice would be appreciated!
Click to expand...
Click to collapse
Sounds like it is a little more than a soft brick.. Can you explain what you did before this happened..
lacoursiere18 said:
Sounds like it is a little more than a soft brick.. Can you explain what you did before this happened..
Click to expand...
Click to collapse
Nothing special, it just rebooted and got stuck in a boot loop.
bubbleytea said:
Nothing special, it just rebooted and got stuck in a boot loop.
Click to expand...
Click to collapse
So no modding.. No flashing a New Rom..No Odin flashing back to stock or new modem..etc etc..
Bc it sounds like you have corrupted partitions.. I would try to see if you can use Heimedal and fix it by flashing each img seperatly.. If not you may need a JTAG service, if you eMMc is not borked..
lacoursiere18 said:
So no modding.. No flashing a New Rom..No Odin flashing back to stock or new modem..etc etc..
Bc it sounds like you have corrupted partitions.. I would try to see if you can use Heimedal and fix it by flashing each img seperatly.. If not you may need a JTAG service, if you eMMc is not borked..
Click to expand...
Click to collapse
No modding at all. I tried using Heimdall, but the .pit file failed again.
Code:
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
bubbleytea said:
No modding at all. I tried using Heimdall, but the .pit file failed again.
Code:
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Click to expand...
Click to collapse
Maybe a bad download.. You try to redownload it?
lacoursiere18 said:
Maybe a bad download.. You try to redownload it?
Click to expand...
Click to collapse
Yup, redownloaded everything and got the same stuff.
Related
I hard bricked my 4.0 Intl by flashing the wrong bootloader (stupid, I know). I have downloaded the recovery ROM and the correct PIT file and I can get into download mode by using the resurrector. But when I try to flash the recovery ROM, I get the following error in Heimdall:
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Is there any way to fix this or should I just send it back to Samsung?
skapebolt said:
I hard bricked my 4.0 Intl by flashing the wrong bootloader (stupid, I know). I have downloaded the recovery ROM and the correct PIT file and I can get into download mode by using the resurrector. But when I try to flash the recovery ROM, I get the following error in Heimdall:
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Is there any way to fix this or should I just send it back to Samsung?
Click to expand...
Click to collapse
Read through here.
http://forum.xda-developers.com/showthread.php?t=1386669
There is also a thread that has all the facts, incl. tips for flashing and recovery options for these players in the DEV section. Please read.
Chances are, if you can still get into Download mode, you should be able to get the player back to normal. The trick is to flash the right PIT, kernel and rom...
BTW... I don't think Samsung likes people messing with firmwares and send them back for warranty repair when they fail. I believe that the fact you flashed custom firmware and bricked it in the process, the factory warranty is now voided. You can maybe play dumb but... your results may vary.
skapebolt said:
I hard bricked my 4.0 Intl by flashing the wrong bootloader (stupid, I know). I have downloaded the recovery ROM and the correct PIT file and I can get into download mode by using the resurrector. But when I try to flash the recovery ROM, I get the following error in Heimdall:
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Is there any way to fix this or should I just send it back to Samsung?
Click to expand...
Click to collapse
Did you try flashing this with odin before flashing with heimdall?
zaclimon said:
Did you try flashing this with odin before flashing with heimdall?
Click to expand...
Click to collapse
Yes.
skapebolt said:
Yes.
Click to expand...
Click to collapse
I saw people reporting that they got the same problem with heimdall 1.3.2. Try to flash with heimdall 1.3.0
Source: http://forum.xda-developers.com/showthread.php?t=1286432&page=35
So I can't actually get in download mode. If there was something similar like this thread: http://forum.xda-developers.com/showthread.php?t=1386669 , but for the 4.0 it should work.
Hi all,
Sorry for my bad english.
I was using i9100 with the CM10 and wanted to flash the stock rom back.
Here is the problem now,
When I press the start button,
it goes smoothly but stuck on boot.bin for almost 45mins.
What should I do next?
I think I did everything right?
I tried change the USB port,
Kill all kies program in task manager,
Tried other stock rom....
Thanks all
If you did NOT check repartition and did NOT select a .pit file then you are safe. Then you can just try again. Or try again with a different rom and/or a different USB cable.
Sounds like the tar file you downloaded might be corrupt. Try downloading it again, and once you've done so/unpacked the tar, use 7Zip to test the integrity of the archive. If it comes up all files OK/no errors then that isn't your problem.
Flashing with Heimdall guide ;:http://forum.xda-developers.com/showthread.php?t=878686
devid801 said:
If you did NOT check repartition and did NOT select a .pit file then you are safe. Then you can just try again. Or try again with a different rom and/or a different USB cable.
Sounds like the tar file you downloaded might be corrupt. Try downloading it again, and once you've done so/unpacked the tar, use 7Zip to test the integrity of the archive. If it comes up all files OK/no errors then that isn't your problem.
Flashing with Heimdall guide ;:http://forum.xda-developers.com/showthread.php?t=878686
Click to expand...
Click to collapse
Heimdall said "Failed to detect compatible device"......
what should i do?
Thanks
alanlee4927 said:
Heimdall said "Failed to detect compatible device"......
what should i do?
Thanks
Click to expand...
Click to collapse
In debugging USB mobile phone enabled in Settings / applications / Development?
Install correctly the drivers samsung http://it.official-drivers.com/installer/?seed=samsung&local=it&gclid=CJ6K2ouIsLACFUdO3godUXHuWQ
Aare you sure that you want test your computer , Enter recovery and wipe data/factory reset.
hey i just got an s3 off a friend thats stuck on a splash screen and if i go to vol down power and home i get this
http://i.imgur.com/LbYNlrU.jpg
i am seriously at a loss here and i have no idea how to fix it, can it be fixed?
Partition corruption, try flashing a full stock firmware with Odin then factory reset in recovery afterward.
Odin fails every time. I don't know what else to do
Try the rescue firmware with pit, search general thread. If that fails then emmc chip is damaged.
boomboomer said:
Try the rescue firmware with pit, search general thread. If that fails then emmc chip is damaged.
Click to expand...
Click to collapse
I've got same problem but with more complications. bootloop.
It started after using CM11 4.4.4 2014.0904 nightly with 2.8.3 agni's KERNEL.
Installation was fine. Everything worked perfectly until I played "real racing". (I just write it to explain all things precedent the failure.)
While playing and doing something more on another app in the background Phone made full restart and started to bootloop.
1. I tried to flash same nightly - it failed - couldn't format /preload partition. TWRP, CWM, Philz - all failed to mount /preload
2. I flashed stock rom via odin - installation was fine, but still bootloop.
My thought is a problem with gaining acces to /preload partition.
Shall I do a repartition of stock rom but with PIT file and full re-partition?
boomboomer said:
Try the rescue firmware with pit, search general thread. If that fails then emmc chip is damaged.
Click to expand...
Click to collapse
Odin fails on that too
A while ago my phone started to restart itself for no good reason. Then it got worse and it starts randomly resetting itself (factory reset). To solve this issue I tried to do a manual factory reset myself, and the problem persisted.
I can deal with these random restarts, but then one day as it restarts it got stuck at the "Samsung Galaxy S3" screen. I tried to do another factory reset in CWM and clear the cache, but it says "E:\cache\...." isn't mounted. As I investigate further it seems the reason that it can't boot might be because the memory is not mounted I guess?
I can boot into Download mode and CWM perfectly fine, so I decided to try to flash the Stock Recovery and Stock ROM through Odin. Connection between Odin and the phone was set up fine, but then it stopped at this error message "Complete(Write) operation failed." Flashing either stock rom and recovery yields the same error . It simply can't write to the memory it seems.
Now I'm stuck at this start screen. I've heard flashing a PIT file might be able to fix it, but I have no idea what that is.
Is the phone bricked? How do I fix this? Should I use the Rescue Firmware in this post? It would be great if anyone can help me since I have been asking for help on other forums but got absolutely no response...
GT-i9300
If you can boot to download mode you can try to use the rescue firmware. No, it isn't bricked because it still works
Thanks for the response! I'm going to try the rescue firmware, but I see that it says "KOR" on the file name. Is that referring to "Korea"? My phone isn't bought in Korea does that matter? Also what's the CSC thing it's talking about?
Your description matches emmc corruption/failure, so it is a software brick.
Follow the guide for the rescue firmware it doesn't matter about the country or CSC, but make sure you include the pit file.
If that fails to flash then it's time for a new phone.
boomboomer said:
Follow the guide for the rescue firmware it doesn't matter about the country or CSC, but make sure you include the pit file.
Click to expand...
Click to collapse
I just downloaded the zip file, but it seems like it doesn't have a pit file inside. So where can I get that file? Thanks again.
DerekL. said:
I just downloaded the zip file, but it seems like it doesn't have a pit file inside. So where can I get that file? Thanks again.
Click to expand...
Click to collapse
There are two versions in the rescue firmware page 4.1.2 and 4.3 the pit file is in the 4.1.2 version and can be used on both.
Now I tried to flash them with Odin 3.07, it doesn't fail nor success. Instead it got stuck at "Get PIT for mapping.." I read that this might be a driver problem, but I've reinstalled my drivers, and I even tried all the usb ports on my computer. I've terminated Kies' process, but it's still not working!
What should I do to get Odin to write onto the device???
boomboomer said:
Your description matches emmc corruption/failure, so it is a software brick.
Follow the guide for the rescue firmware.
If that fails to flash then it's time for a new phone.
Click to expand...
Click to collapse
It won't write for a reason, the emmc chip is damaged.
-Bought a used S3.
-It enters dowload mode and recovery (CWM)
-If you turn it on normaly, it get stuck at Samsung Logo
-Tried to flash via ODIN but CSC, PDA, MODEM says
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
-Tried to flash pit files and re-partition but I get stuck at "Get pit for mapping" or "No partion" (depending on the version of ODIN)
I think there's no solution, I've already searched a LOT around XDA and no one has a solution for this
So this is my last call before replacing motherboard (maybe eMMC chip is broken)
Please, keep in mind that I'm not a noob (or at least not that bad noob) and I've already tested ODIN with different cables, ODIN versions, pit versions, USB ports, different computers, no KIES installed, drivers unistalled and reinstalled over and over so this is not the problem.
More details
-The man who sold me this phone told me that he was updating by KIES and electricity went off in his house (It's possible that this is not true, don't have evidence to confirm this)
-Wipes by recovery don't work. Only wipe battery stats. If I try to wipe cache, data, system or anything else, recovery gets stucked or phone rebooted
-SD card is not recognzied in recovery. Can't make a backup or flash files to external SD card. Internal SD card can't be mounted.
-Format system, or cache or data by Mounting settings neither work. It freezes the recovery
-Saw that there is a method to recover Verizon S3 phones by a sort of factory image. Didn't tried in my 9300 interntional, but read a few people who said that method didn't worked on her 9300. Wonder if it's posible to make a factory image of 9300. (Here is the thread http://forum.xda-developers.com/showthread.php?t=2660566)
Try downgrading just the boot loader to BLFB, if that flashes then try pit & firmware together.
The age of this model means nand wear is becoming more common, so it might mean nothing will flash.
boomboomer said:
Try downgrading just the boot loader to BLFB, if that flashes then try pit & firmware together.
The age of this model means nand wear is becoming more common, so it might mean nothing will flash.
Click to expand...
Click to collapse
I tried just flash only Bootloader file that comes with each firmawre I tried (didn't understand what do you mean by BLFB) but no difference.
jutopa said:
I tried just flash only Bootloader file that comes with each firmware I tried (didn't understand what do you mean by BLFB) but no difference.
Click to expand...
Click to collapse
After a year or so I have tried to flash again my old i9300, but I'm stacked in the same problem! I have tried with Odin 3.12.3 with different PIT files, and also with Heimdall under Ubuntu... I'm not also a super noob (i have flashed several time this and other phones)
Have you found a way to force to rewrite the PIT file? the only mode available in my phone (i9300 International) is the Download Mode (i have broken even the Bootloader and the Recovery trying to Flash it )
Nothor said:
After a year or so I have tried to flash again my old i9300, but I'm stacked in the same problem! I have tried with Odin 3.12.3 with different PIT files, and also with Heimdall under Ubuntu... I'm not also a super noob (i have flashed several time this and other phones)
Have you found a way to force to rewrite the PIT file? the only mode available in my phone (i9300 International) is the Download Mode (i have broken even the Bootloader and the Recovery trying to Flash it )
Click to expand...
Click to collapse
Tried J-tag yet?