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 .
Hey all!
Wanting to upgrade my firmware from ICS to Jelly Bean (as a definite noob, though having flashed firmwares before) I opened Odin and added what I considered the correct .tar file from Sammobile in the PDA field. In short, it failed and I thought I had a new brick*. Following Phistacio's guide to fixing an unflashable GSII I've now got my phone back (woohoo!!), but am stupid enough to want to give it another go!
My question really, is what could have gone wrong, and more largely, what are the variable errors that us noobs make when trying to flash? I'm using Odin, but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
I'm rooted, on an unlocked GSII, recently moved from O2 to Everything Everywhere (T-Mob), currently using an O2 issued ICS, stock kernel and tried flashing Jelly Bean from Sammobile.
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Thanks in advance for any light you can shed!
*I think I was softbricked - could enter download mode but not recovery, flashing would hang on either "Nand write start!!" or Sbl.bin or Cache.img.
my two cents
Hi joelinit,
First of all, should congratulate you on taking the first step of flashing the roms..
Second, good you got an issue while flashing. It helps you understand the intricacies better once you try to solve it yourself.
You need not worry about the brick. Try flashing back to stock rom available from sammobile using Odin(3.04). (United Kingdom (O2) 2013 March 4.1.2 PDA-I9100XWLSD CSC-I9100O2ULS7). Yes carrier is important as Modem file differs based on which carrier you use.
This will fix the recovery and will get you on stock JellyBean.
but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
Click to expand...
Click to collapse
CWM is clockworkmod recovery which provides options for flashing custom roms(CM10, SlimRom, NeatRom etc, there are so many).
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Click to expand...
Click to collapse
Searching in sammobile for firmwares you will find different firmwares for different carriers. You can flash a UK firmware for some other country, but might have issues with call reception, 3G connectivity, etc. as the modem files are different.
It is possible to go from some firmwares to others.
Stock Roms come with Stock Kernels. When you flash a ROM, kernel will remain the same.
You need to change kernels if your phone is consuming too much battery, crashes etc. This normally happens after flashing custom roms as the kernel is not capable enough to handle the updates in the rom.
Dont stop trying, you will love your phone, once you start flashing the awesome roms,kernels found in xda.
Cheers,
Maddy
Galaxy S2 || CM10.1 nightly 4.2.2 || Dorimanx 9.24
Most of the above is good advice. ....apart from the kernel bit.......
All custom roms and firmwares come with their own optimised kernels. These kernels get flashed during the rom/firmware flash. You can choose to install a custom kernel after you have flashed your chosen rom/fw. Custom kernels offer more control over your OS. All custom kernels offer cwm or twrp (depending on the kernel) and will root an unrooted phone. Most need to be Odin flashed, but some (PhilZ) can be flashed via stock recovery........
Sent from my GT-I9100 using xda app-developers app
Hey guys! Thanks so much for the friendly replies - I thought I might have got abuse as a noob, possibly asking very repetitve questions!!
So then with my recovered GSII, I decided to give it another blast and, inevitably, it's bricked again! Seems to be the same bahaviour - though instead of hanging on either "Nand write start!!" or Sbl.bin or Cache.img., it's failing on them. And this time, I can't seem to fix it,following Phistacio's guide to fixing an unflashable GSII .
I also tried flashing that firmware you suggested (although as I mentioned, I'm now on T-Mobile, not O2? So also tried T-Mobile's Jelly Bean), though with no success.
To clarify, I've installed Kies, then closed down all Kies processes, started Odin and put the .tar file into the PDA field, left Re-Partition unchecked, with both Auto Reboot and F.Reset Time checked, connected my phone and waited for Odin to recognise it, then pressed Start!
Can you suggest anything obvious that I've done wrong or suggest what I should do next? Thanks so much in advance!
4 things to try.....
Use the original usb cable. ..
Try different usb ports on your pc....
Disable any firewalls......
If you are running windows 7, open odin as an administrator. .....
Oh and a fifth suggestion.....
Try different odin versions...
Edit.....Don't ever flash/select pit
And don't select repartition......
Sent from my GT-I9100 using xda app-developers app
These steps are originally posted by MistahBungle. Follow all these steps, he knows what he's talking about.
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Turn off antivirus/antispyware/antimalware.
*Check the rom/kernel you download for corruption. Either check the MD5 sum if you have it (use md5summer or similar), if you don't have the md5 sum or can't check it, programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all these steps fail, try a different PC. And if it won't work first go on a 2nd PC, go thru the above steps on that PC. Still doesn't work ? User error (will be almost impossible to say what given we're not there looking over your shoulder, almost always something very obvious being missed) or borked phone - return to service centre or local mobile shop.
I suspect many cases where people (say) they do all the above & still can't get it to work involve problems with the USB ports on the machines they're using. Something along the lines of the port is unable to maintain a constant connection between PC & phone; if that connection drops for even a millisecond (probably not even long enough to be registered as a broken connection by the PC in the normal way), you end up with a constantly failing flash at best and a bad flash which borks your phone at worst.
Obviously the only way I'd be able to test the theory would be to examine/test a bunch of PC's belonging to people who experience this issue, but I've given this issue a lot of thought over the past 18 mths & it's the best explanation I've got for those instances where people are being completely honest about having tried all the steps over & over and on multiple machines (a very very small % of people, most people either simply don't do every step over & over and say they do, or they forget they've forgotten they did A, B & C but not F) & still find they can't flash successfully (and it isn't a case of the phone being borked).
See how you go with that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Thanks so much for all these useful replies - really was expecting to get fobbed off for my noob questions! What a nice community!
I'll try all the above and report back. I have successfully flashed on this computer before and did manage to restore the phone last time, though perhaps the cable is faulty and slightly intermittent? I'm using the USB port that's connected to the mother board too.
Thanks again...
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
joelinit said:
perhaps the cable is faulty and slightly intermittent?
Click to expand...
Click to collapse
MistahBungle said:
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
Click to expand...
Click to collapse
Thanks! Yeah the cable will be the first thing I'll try changing. It's odd that the flash seems to fail at the same point each time though, kind of implying that it's not an intermitted cable? Unless this particular cable is falling short at those particular functions or something?
Anyway, thanks again - I'm actually kinda enjoying learning about my phone, even though there's the fear it's now a brick!! Fingers crossed that's not the case though...
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
joelinit said:
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
Click to expand...
Click to collapse
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
Will do! Looking forward to exploring new firmwares so will get as clued up as poss! Have now successfully flashed SentinelROM and loving having a "new" phone! Much more exploring to come.
Thanks v.much to all who've helped me in this thread...
Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).
Hi,
I got my hands on an i9300 that the previous owner had broken while trying to do a sim unlock.
I've tried flashing various ROMs and recoveries using Odin (1.85 and 3.07), and also from within the recovery.
I'm not able to determine if the EFS partition is completely intact, but I believe it is.
So far I have tried flashing the rescue firmware (http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6), various stock firmwares, resurrection remix, android revolution hd, and a few others.
I have philz recovery installed at the moment, and have tried the latest CWM as well.
I've even tried using kies to do an emergency recovery, but this also failed.
No matter what I do, I'm unable to make the phone boot up.
I do have adb access to it.. Anyone got any suggestions for what else I can try?
In odin mode it *does* display the model number, so from this I believe that it is safe to say that the emmc is still ok.
Any thoughts or suggestions?
Cheers!
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Benko111 said:
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Click to expand...
Click to collapse
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
EqUaTe said:
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
Click to expand...
Click to collapse
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Benko111 said:
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Click to expand...
Click to collapse
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
EqUaTe said:
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
Click to expand...
Click to collapse
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Have set that file downloading, and have also grabbed TWRP.
Will give it a shot when I get home from work tonight. Cheers for your help so far Sometimes it helps just to have another set of eyes on these things!
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
EqUaTe said:
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
Click to expand...
Click to collapse
Ok, found the password.. Extracting a bunch of zips atm, fingers crossed one will help!
Benko111 said:
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Click to expand...
Click to collapse
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
EqUaTe said:
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
Click to expand...
Click to collapse
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Benko111 said:
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Click to expand...
Click to collapse
It's the 16gig model, will have another go this evening
k-semler said:
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Click to expand...
Click to collapse
I'm curious, which version of Odin did you use when you fixed yours?
Interestingly, while I've had it available before, the bootloader update tickbox isn't available on 3.07/3.09 at the moment, stays grayed out..
Going to give 1.85 a whirl
So flashing with 1.85 has resulted in the same thing.. Wondering if it may actually be a 32gb one.. I don't think it is, but at this point I have no idea.. Are there any identifiers that distinguish it on the unit itself? FCC ID, SSN, etc.
Fairly sure it's not a 32gb as it hangs flashing if I use that pit.. Trying another flash at the moment.
So no joy with this so far.. Getting a bit annoying really, tried quite a few combinations now..
Fairly certain at this point it's a 16GB model, using the 16GB PIT I can flash other ROMs, but no joy on actual resurrection of the device.
Odin logs seem fine, with and without a bootloader update.. After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot, and then the sick android (little red triangle coming out his chest).
All stock roms have the following text at the bottom (though the actual position varies from rom to rom as some of them have recoveries at much higher res than others):
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC.
And yes, the typo is on the screen.. Appling.. Really?
Anyway, don't know if that is normal (while I've used other s3's, I can't remember what they showed with stock recovery as I rooted them pretty early on, and never really touched them again).
I can say I'm glad I still had the jig from my s2, as it makes getting into download mode much easier
I've tried several odin versions, different USB ports, different cables.
I can go through and provide details of the various ROMs I have downloaded, the majority of which are stock at the moment, and am happy to grab others if people think they may work..
Cheers,
EqUaTe
That's not nice, still busy with it... I must say, when I read the bit you wrote
After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot
Click to expand...
Click to collapse
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC
Click to expand...
Click to collapse
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Benko111 said:
That's not nice, still busy with it... I must say, when I read the bit you wrote
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Click to expand...
Click to collapse
I figured the spelling was normal, just a little disappointing Also thought it was normal that this appeared, but wasn't sure. Makes sense though.
I have tried a factory reset after pretty much every flash attempt, but will give it another go. Getting to the point where i'm tempted to try and do the sd card recovery, just to see if there is something fundamentally broken at that level.
I'm also downloading the latest ROM for the carrier (Vodafone UK) to see if flashing that here makes any difference..
Well, factory reset and wipe cache don't help. Other ROM won't be donwloaded for a bit, so will have to try it after work. grr.
Hi,
i try to repair the Galaxy S 2 (GT-I9100) from my cousin.
I don't know the internal size nor the original android version... (he can't remember)
I can boot into download Mode but not into recovery.
I tried to flash from linux and windoof using heimdall and Odin (differ versions).
Both programs don't show any error while flashing and the phone display the progress bar and reboots...
But no difference ... phone just display Samsung logo. And i can't start recovery mode.
Because i don't know the android-version or filesystem size i tried to flash different pits and bootloader but nothing is different to beginning...
With heimdall i get the current PIT flash an different pit-file and check md5sum - no differ ...
Has anyone a tip what i can try anymore? Or is it an nice paperweight ?
I tried this but it doesn't work for me...
http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
Regards
erdo
There is a 'stickyed' guide in general by a member called hopper8. It's called 'Troubleshoot a failed odin flash'
Read the first post IN FULL and follow all the steps as many times as it takes to get your phone working....It sounds like there isn't any hardware issue with the phone, just that it's not accepting the flash.....sometimes it can be like that, and only perseverance will 'win the day'.....
If your device is the i9100 international variant, that guide has a link to a 3 part test/leak firmware which will have a slightly better chance of sorting the device than a normal firmware.....
It completely erases the device before flashing, so it gets rid of any leftovers that might be causing issues during a regular FW flash.....
http://i.imgur.com/rVnFwJM.jpg