Related
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .
So here's the story. This morning I started out with a working 32GB GT-i9300 running a rooted variant of Samsung's android 4.2.2., and thought I'd have a go at overclocking it following this thread here. Look away now if you can't bear to read of the destruction of technology by ignorance and impatience.
The first road block I hit was needing siyah kernel if I wanted to try overclocking the graphics chip as well. Why not? I tried flashing Siyah via clockwork recovery and ended up with a status 7 error which I looked up to mean my OS was incompatible. (In hindsight I probably had the wrong file...) So I did a bit more research and found that Cyanogenmod 10.1 is also supported by Siyah. I've always thought it would be fun to try Cyanogen, so I grabbed the latest nightly and tried flashing it with mobile Odin. Mobile Odin started flashing then froze after something like 'clearing data'. I think I must have been using the wrong file here too... Anyway, I reset my phone, and it wouldn't boot, except into recovery or download mode. So in another flurry of impatient research I found a bunch of different sources that seemed to suggest re-partitioning with a .pit file was a sure fire fix. A link was provided, with no mention that pit files are specific for certain sizes. Next thing I know, I've re partitioned with a 64GB file on my 32GB phone, and recovery mode is no longer an option. I can still use download mode but Odin freezes typically on 'NAND Write Start!!'
Panic mode, activate.
Things I have tried so far to no avail:
Re-partitioning with a pit file for 32GB galaxy S3s - It finishes in Odin successfully, but no result.
Attempting to flash any ROM, specifically the original one, and the one I had before the screw up - 'NAND Write Start' freeze
Attempting to flash any kernel, specifically Siyah, Perseus and the stock kernel. - Same as above
Using multiple usb cables (4) - No result
Trying different USB ports, and different computers - Ditto
Different versions of Odin (1.3, 1.85 and 3.07) - Unsucessful
Throwing a tantrum - exhausting, but otherwise un-noteworthy
Things i haven't tried:
Jtag. - I don't know terribly much about this apart from what I found in a PDF. Would this be likely to work? Are there any trustworthy people that do this? Should I try it myself?
Returning to Samsung under hardware warranty - I don't think this would work, my flash counter is 2 - custom. Unless it's possible to triangle away in this state.
Giving up - I doubt this would help, but somehow it's looking more and more enticing... ;_;
So after wasting nearly a whole day trying to rescue it, and failing miserably. (Digging my own grave) I decided to post my specific case. As while I have found many descriptions of similar woes, nothing has worked.
Can you help? Please?
Its a damaged Nand from what you posted .
jje
If that's the case, is there anything I can do at all? Is it worth trying to Jtag it?
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.
This is a special case that requires extensive help from you guys (hopefully).
Problem: According to the ATT Samsung specialist the Bootloader I am using is corrupted
Attempted Solution: I have attempted to flash the stock SBL onto my phone but after trying every version of Odin3 (1.83-3.09) it did not work.
**The bar was entirely GREEN but it never finished**
Suggested Solution: Flash the stock ROM back onto the phone using Odin3
Outcome: After trying three different ROMs, all downloaded from Sammobile, using every version of Odin3 (1.83-3.09) only seemed to reach the end then fail at Modem.bin
I was wondering if anyone has any idea how to fix my phone, the original issue was that it never made it past the Samsung logo (not the Galaxy S2 Logo but the actual Samsung logo) the new issue is that it has the Samsung Galaxy SII Logo with the wrong model name (international model) and the small yellow triangle.
If my phone is permanently broken that's fine because I have a temporary phone I just want to get my files off of the phone before using my new one
I have a Jig
I can get it into Odin mode
I cannot get it into Recovery mode
I can get it into Factory mode
Help me please, I have no idea what else to do
Use this version of Odin, or just do more Google fu and find another place to download it from. [ http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 it may be the version of Odin you're using that's messing you up.
The link Phalanx7621 posted was supposed to point to the Download Repository (link is in my signature.)
The preferred version of Odin is 1.85. If you need it, the download link for Odin3 v1.85 at the top of the Download Repository is a working link.
If the boot loader was corrupt, the phone would be a true brick (no sign of life.) If the secondary boot loader was corrupt, the phone would not boot as far as the Samsung logo. It sounds to me like the AT&T Samsung specialist you received that information from was not fully informed.
The I9100 splash screen with the yellow warning triangle is due to flashing a custom kernel, so nothing to worry about. It can be cleared by flashing a stock kernel. Using the following procedure would have put that on your phone anyway by flashing the Siyah kernel, and then will removed it when stock Gingerbread is flashed.
Please note: The link in the Download Repository for the stock Gingerbread that you need to flash is not working, and I have yet to re-upload all these items to a new host. You will have to download this from the sammobile firmware page. It is the I777UCKH7 / I777ATTKH7 dated 2011 August. You'll need to sign in to download it. The registration is free. Edit: sammobile has not uploaded this file to a new host yet either. I will have to upload it and the sbl for you, but since today is Christmas, you may have to wait a day or two. At least you know that there will eventually be something to try.
Edit: The required files are now available with Dev-Host links in the Download Repository.
I think you will probably recover the phone by assuming it has nand read/write corruption and following this sequence:
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Attempt #1
When attempting to flash the Kernel in Odin3 v1.85 the bar was fully green but the program never said complete (I left it going for a few hours to no avail)
I tried flashing the SBL and the same issue happened, the bar was fully green but it never said complete (I had previously downloaded the SBL)
When attempting to flash the Gingerbread stock it does not even go past the SBL1 part, the bar does not have any green within it and the program still says NAND Write Start.
I'm not the best with this sort of thing but from observation it seems that my NAND is corrupt and isn't allowing anything to be properly flashed.
By the way: the Custom Binary Download now says: Yes (5 counts) which tells me that the phone recognizes that something is being flashed but it's not working properly
I'm back to being stuck and I think this phone may be truly broken :/
I don't think ur phone is broken.
Try a different usb/micro usb cable. Try a different usb port on ur pc (don't use a usb hub). Make sure the phone's micro usb port is clear of dirt/debris, etc.
Usually when i've had problems with Odin flashes it is something as simple as doing these things that results in a successful flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Same Issue
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
androidrequest said:
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
Click to expand...
Click to collapse
Did you follow exactly the sequence in post #3? If not, please try that.
creepyncrawly said:
Did you follow exactly the sequence in post #3? If not, please try that.
Click to expand...
Click to collapse
Yes, I tried that sequence exactly. It actually won't advance past #1. The green bar loads in Odin under kernel, but stops working at NAND Write Start. And trying the sbl ends with the same result (I believe it's the first download in the Download Repository). All of the flash attempts have failed or frozen, but the Custom Binary Download count is at 3.
Hello I've bricked my sgs2 it's not so hard bricked. It goes to download mode easily, but the problem is I can't find 3 file rom - probably 2.3.6 android, cause every link on the interer is down [2011, 2012]. I tried flashing it with 1 file rom through odin but it fail. I need to repartition it with full 3 file rom.
Please is there anybody who can help me? Simply provide 3 file rom for odin with pit file for Samsung Galaxy S3 i9100...
Thanks
I have an untested 3 part + pit gingerbread (multi csc) firmware.....
I also have a 3 part jellybean firmware.
I can provide links to either or both of them if needed.....that is assuming your device is the international variant.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa you didn't reply yet, but I'm guessing you still need the firmware....
Here are the links.....
Gingerbread
https://www.androidfilehost.com/?fid=24269982086991760
Jellybean
https://www.androidfilehost.com/?fid=24052804347838984
The Gingerbread zip contains a pit file, but the Jellybean one doesn't. There are posts on XDA that contain pit files, you just need to search for them.
http://i.imgur.com/rVnFwJM.jpg
Thank you I hope I will unbrick my sgs 2
You have a better chance of that if you use a pit with either of those firmwares than with just the firmware on it's own......
BUT......
You are advised to use the pit as a strictly LAST OPTION.
If flashing a pit fails, you end up with a device that CAN NOT be revived/recovered......
So...bearing that in mind, try with just the firmwares first.....The theory behind them is that they will format the partitions and erase ALL traces of previous software without rebuilding the partition layout....that is what the pit is for.....
And as I said, if the pit flash goes wrong, you end up with a device that has corrupted partitions which is then impossible to flash further.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa let us know how you get on.....
What files you flashed, what procedure you followed.....
That way, if other members face the same issue as you, they'll know what to or not to try.......
http://i.imgur.com/rVnFwJM.jpg
I tried to flash 3 files rom. Fail. I tried different computer, different cables nothing helps. Then I tried to flash kernel. Odin froze on nand writing I need to shutdown Odin after 30 minutes. I tried flashing bootloader and also Odin froze and I turned it of after 30 minutes.
I have no idea what to do....
I can turn on the phone to the download mode... Only that.
Is this possible to unbrick this phone?
Flashing with odin is a bit like the lottery....
It may not work the first 9 or 19 times, but the time after that, it does....
Perseverance is the name of the game.
Look at this thread.....
http://forum.xda-developers.com/showthread.php?t=2345831
It has been written for situations like yours.....
http://i.imgur.com/rVnFwJM.jpg