Hello
I was trying to flash an stock ROM in my i9300 when it got stucked and i bricked my phone.
Now when i try to flash a rom or a kernel odin gets stuck at "NAND Write Start". I tried to flash a PIT first with only repartition checked and them flash a kernel with the pit and auto boot and F reset chechek (saw this mehtod in a forum ). When a flashed the pit odin said pass but when i try to do the kernel odins gets stuck at setting up connection
Can someone help please??
( tried to take of the baterry, reboot the pc, tried all drives, installed drivers again, and i am not running kies on second plane)
Visit the rescue firmware thread:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Follow the instructions exactly, if that doesn't work then you've damaged the nand and need a new motherboard.
Sent from my GT-I9300 using Tapatalk
I wil try thank you for the answer
Sorry, but the download link is dead, do you know where can i find a similiar link
I was able to find it and flash it and everything went all right, my IMEI changed!!!
Is there anything i can do restore my original IMEI???
If you flashed an rom earlier than EMG then update to EMG, if you are on a later rom then your efs partition is probably corrupt after your brick.
If so then restore the backup of efs you made before you flashed, there is no other way to regain imei number apart from a service centre.
Sent from my GT-I9300 using Tapatalk
Related
Well i was playing with my phone, flashed a new rom everything was fine but i had no mobile connection. I had an Efs backup already created with Ktool and wanted to restore it. Restored the img. file nothing happened. Restored the .tar file and my phone just broke. It's not even a bootloop the phone freezes on the boot logo. I tried kies recovery and flashing a stock rom with odin but nothing works. The only firmware that works is the stock ICS 4.0.4 and when i instal it the pc doesn't recognize it and i can't access anything else than odin. Someone please help !
If you can get ics to boot then it isn't bricked.
Panic flashing can brick it, however, so slow down and think. afaik JB won't boot if the efs partition won't mount.
Try flashing Philz recovery via odin, use that to restore/fix your efs then factory reset and flash an official 4.1.2 stock rom.
Also, go read the stickied help for efs:
http://forum.xda-developers.com/showthread.php?t=2393289
boomboomer said:
If you can get ics to boot then it isn't bricked.
Panic flashing can brick it, however, so slow down and think. afaik JB won't boot if the efs partition won't mount.
Try flashing Philz recovery via odin, use that to restore/fix your efs then factory reset and flash an official 4.1.2 stock rom.
Also, go read the stickied help for efs:
http://forum.xda-developers.com/showthread.php?t=2393289
Click to expand...
Click to collapse
Well since i already tried to flash a stock rom the efs backup got deleted probably. Could you please explain me step by step the Philz recovery and what to do after.
Sorry, no. You'll have to learn how to install and use it.
I'll just get it to service today, still thanks for your help
Hi,
I have a Samsung i9300 with Miui V5 up to date and I was trying to go back to stock firmware.
To do this, I downloaded a stock firmware (I9300XXUGMK7) and flashed it through ODIN. All the flashing process went without problems but when the device rebooted it was stuck at the Samsung Logo. I waited around 10 min but it was completely stuck. I tried rebooting and then again was stuck. I believe it was a problem with the flashing process so I tried it again with a new stock firmwares but I got always stuck at the logo.
The device enters both download mode and recovery mode (android 3e - stock recovery i believe, although it shows the android laying down with an exclamation point).
I already tried several stock firmware and yesterday I also tried flashing through ODIN with PIT File and Re-partioning but I always got the same issue.
Is it another way to move from miui to stock that I am not aware? Is there any solution for this problem?
Help Please.
Thanks a Lot
Pit and repartion then you may well have destroyed the partitions on the memory .
Who ever told you to use pit files and repartition should buy you a new motherboard .
Are their any error messages in odin ??
JJEgan said:
Pit and repartion then you may well have destroyed the partitions on the memory .
Who ever told you to use pit files and repartition should buy you a new motherboard .
Are their any error messages in odin ??
Click to expand...
Click to collapse
Hi JJEgan,
I used the Pit file as last option because I already tried several regular flashes through ODIN. No error messages during the flashing process in ODIN. The flashing process always goes apparently well until it reboots and stucks at Samsung logo.
Have you tried factory reset wipe data in recovery?
Sent from my GT-I9300 using Tapatalk
1380 58895229
hierarchy666 said:
Have you tried factory reset wipe data in recovery?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot. It solved the problem!!
today my battery went down to zero and then my phone stuck on the menu screen.
i rebooted but then my phone got stucked on the samsung galaxy 3 logo.
i tryed to wipe files and catche but it didnt helped,
i tryed to install the ROM again but it didnt helped...
i can get to the recovery and download mode, but my phone still stuck on the stuped logo...
what to do?
sry if i have spelling mistakes...
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
thx but...
boomboomer said:
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
sorry but what "flash a stock firmware means?"
how do i do that?
do you have links?
ty!
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
ok so i should download the firmware achieve from my area
then i just flash original ROM?
this is the instruction page: http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
then im done?
i need to change the recovery thing too?
or i can just start from procces 4?
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
orial10 said:
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
Click to expand...
Click to collapse
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
dxppxd said:
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
Click to expand...
Click to collapse
can you explain or give me some links how to do that?
orial10 said:
can you explain or give me some links how to do that?
Click to expand...
Click to collapse
I mean, go to the stickies in the general section and read. They're there for a reason, including steps before rooting, flashing, information on the efs partition, and pretty much everything else you could have done to avoid the situation you're facing right now.
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.
Hi I have one samsung Galaxy S3 which is stuck on Boot Screen. I tried to flash it but odin shows fail. I tried pit file same. Is there any way to fix it. I have Z3X also with me
@arjun_anil, in the worst case your internal memory is gone. So before threwing away, try firmware again: download your firmware, drivers, Odin from sammobile.com and follow exactly instructions, given there. If Odin finishs with failed again, post the log.
I tried to flash efs file and this is what I got
This is what I got from odin flashing efs file
Boot screen huh? Sounds like is missing/corrupted is files. Have you tried recovery an factory wipe? Also if you can connect to Odin, then you could reflash. But first your gunna need to know a few things about this brick here. Like the android version, carrier, an kernel version. So you can download an flash the proper files. I'm guessing your on a Verizon phone and or you didn't install Samsung drivers to help Odin's successful flashing chances. If you don't know your phones info, you can find out in recovery an Odin modes on the phone if accessible.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app