Related
Hey Guys,
I'm sure all of you get lots of these questions, however I have been trying for a couple of days to get this S3 going so I can just asking for help.
My main issue is I cannot flash any ROM's via Odin.
Here is some background infomation:
I started with a stock Galaxy S3 GT-i9300 International 16GB model.
Flashed the correct version of Cyanogen Mod for my Model/Sub Model.
I install this rom by flashing CWM (Clock Work Recovery Mod) and installing the update.zip from my external SD card.
I have done this before with other Samsung devices, No big deal, just factory rest and wipe the davik cache and flash the new ROM.
Well I decided to backup the original ROM via CWM's backup option. The backup completed fine but I backed it up to the phones internal storage instead of my External SD card. The new ROM worked fine till it ran out of space. So I selected the Delete option back in CWM to remove the backup file, rebooted the phone only to find I was still using 8 or so GB of storage.
So my phone was not happy. No room to download updates or save new pictures, etc.
This week I decided to flash the stock ROM back over the phone. For some reason the firmware was incorrect for that model or something was wrong with the phone.
After looking around I decided to flash a .pit file for the Galaxy S3, One problem, I did not know that different storage sizes of S3's have different .PIT files. However it flash and I still could not restore my phones ROM.
So after a few days of looking around I downloaded the stock ROM from Sam-Mobile.com for my phone and country and download GT-I9300_mx_20120220 PIT for for what I read and understood was for a 16GB GT-I9300.
So the new PIT file flashes fine, however I still cannot flash any new ROMS. I have tired the stock rom from Sam-Mobile or trying to flash Recovery-cwmtouch-6.0.3.2-GTI9300.tar (clock work recovery mod).
None of these flash. Odin3.04 just sits on "NAND Write Start!!" and there is a blue "downloading" bar that is across the screen and that's it.
Nothing else happens. I have also attached a screen shot of this.
I have a water damaged 16GB GT-i9300T that I have used to create a .PIT file from Heimdall, But that sits there for about 10 Min before Odin says "Unable to get pit map"
I have also tried this: http://forum.xda-developers.com/showthread.php?t=1916796
I get all the way to shorting out the resistor (R313) on the PCB but the phone does not turn on and fails to display "SD Card Mode"
So, can anyone help me?
I know it might be a long shot but at this point I'm willing to try anything. Any ideas would be much appreciated.
Cheers
Mitchell
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Thanks for that!, The recovery firmware failed to flash but the pit file flashed allowing me to install Cyanogen Mod.
Thanks for your help on this one :good:
boomboomer said:
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Click to expand...
Click to collapse
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Did u fix !!!
leo_hacker82 said:
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Click to expand...
Click to collapse
Did u fix ur phone??? same problem happend me
You're using the original Samsung USB cable?
audit13 said:
You're using the original Samsung USB cable?
Click to expand...
Click to collapse
yes.
What file is failing in Odin?
jtk585 said:
Did u fix ur phone??? same problem happend me
Click to expand...
Click to collapse
For getting error when flash in Odin no matter what kind of error. Just need to flash out and repartition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Yumiko87 said:
For getting error when flash in Odin no matter what kind of error. Just need to flash out and re-partition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Click to expand...
Click to collapse
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 :laugh: tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...:laugh::laugh:
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
jtk585 said:
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 [emoji23] tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...[emoji23][emoji23]
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
Click to expand...
Click to collapse
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Yumiko87 said:
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Click to expand...
Click to collapse
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash :laugh:
thanks
jtk585 said:
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash [emoji23]
thanks
Click to expand...
Click to collapse
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Yumiko87 said:
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Click to expand...
Click to collapse
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
i forget say one thing, when i choose boot loader file BL sboot.bin file is stuck... freeze.....
jtk585 said:
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726[/QUOTE]
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on
jtk585 said:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on [/QUOTE]
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
audit13 said:
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
Click to expand...
Click to collapse
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.[/QUOTE]
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks
jtk585 said:
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
Click to expand...
Click to collapse
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks[/QUOTE]
This will only for n9005. Not 9305.
I will not go into detail but suffice to say I was running my Samsung Galaxy S3 GT-I9300 on a stock Samsung Android 4.1.2 ROM and it was rooted and had a custom CWM Recovery.
I then flashed to CM 10.0.0 but encountered problems and tried to revert to my original ROM. This resulted in my phone displaying the initial black background boot screen with the words "Samsung Galaxy SIII GT-I9300". It stuck there and I could not switch it off nor could I get into Recovery Mode.
I was able to get into Download mode and connect to Odin to reflash my original ROM but Odin continually got stuck in the process at "Setup Communication" and on the odd occasion it got past that it then stuck on "Get Pit Mapping".
After much research of this and other forums found one lone article about Samsung introducing new ROMS from July 2013 onwards which had efs2 and that once upgrading to an efs2 ROM you could not go back to a previous efs1 ROM which I think I tried to do.
I eventually decided therefore to bite the bullet and I downloaded GT-I9300.pit and flashed it using Odin with Re-Partition selected. I was then able to flash Samsungs latest Android 4.3 (I9300XXUGMK6) ROM for the I9300.
The result is that whilst the phone is again fully functional I am unable to install a custom recovery nor can I root my phone.
I thought that if I used the GT-I9300.pit file it would re-partition the phone as a I9300 should be partitioned but it seems I was wrong.
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
matrixmainframe said:
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
Click to expand...
Click to collapse
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
ag4751 said:
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
Click to expand...
Click to collapse
When I try to flash a recovery or try to root I get the following.
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see from the above it looks as though the process falters at "<ID:0/003> Get PIT for mapping.." which would appear to have something to do with the fact that I had to re-partition using GT-I9300.pit and that is what prompted my question in the first place.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
matrixmainframe said:
When I try to flash a recovery or try to root I get the following.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
Click to expand...
Click to collapse
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
ag4751 said:
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
Click to expand...
Click to collapse
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
That problem in Odin might be related to incorrect drivers for your phone.
Remove any kies or Samsung softwares and reboot pc. Reinstall kies and connect phone 2 pc for drivers install. Then try a different usb port to flash smth on the phone.
Trimis de pe al meu GT-I9300 folosind Tapatalk
matrixmainframe said:
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
Click to expand...
Click to collapse
I think i had the same problem with rooting and done reinstalling drivers and change the port so it is now rooted.
Also try unticking autoreboot then after the instalation is done disconnect the phone and remove/reinsert battery and boot to recovery so the auto root files start to install...
Of course everything you do is at your own risk...
BR
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
I tried again using I9300XXEMC3 stock rom, but odin 3.04 says
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And fails. My phone says "unsupported dev_type" in red.
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
zhinkk said:
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
TheoDores said:
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
Click to expand...
Click to collapse
I tried following those instructions. I managed to flash the .PIT file. Now I don't see the error message at boot, my screen is just black. BUT I can "sorta" boot into recovery mode (starting recovery message shows for one second, then black screen again). So I'm still stuck.
I can STILL boot into download mode though. And if I try to use CF-Root Odin fails again (same error) and my phone says "unsupported_devtype".
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
JJEgan said:
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
Click to expand...
Click to collapse
Everytime I flash the stock rom odin fails and phone says "unsupported dev_type". In Download mode it says my phone model is T999, but it's actual GT-I9300.
And I don't think I did. I think I had clockwork mod recovery, I'm not too sure though.
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
boomboomer said:
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
Click to expand...
Click to collapse
That really depresses me. Are you sure this is the only solution? Because I remember when my phone WAS working I booted into download mode once and it said the same "T999 Model" and I could still use it. This only happened after I tried flashing the stock i9300 stock rom.
I think it's the cyanogenmod installer that flashed this T999 bootloader for me. When I used the cyanogenmod installer it detected my phone as a AT&T phone and I was dumb enough to click "install" thinking it would work for all galaxy S3's.
I think this guide is exactly what I need (since it restores bootloader), but I can't seem to complete all the steps: http://forum.xda-developers.com/showthread.php?t=2535367
I get to #5 but once I try to install CF-ROOT through odin it says the same unsupported dev type error on my phone.
This is the error I get when trying to use CF-ROOT through Odin3 v1.85:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
(along with the red "Unsupported dev_type" on my phone in download mode).
I think it was already rooted though, maybe someone could help me reinstall the recovery (cwm) so I can install the bootloader from that guide I just linked?
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will this delete my EFS? I remember I backed up efs with this guide: http://forum.xda-developers.com/showthread.php?t=1852255
I did: "adb reboot nvbackup"
By restoring to "complete" factory settings, won't this efs be deleted? Can I still backup my efs in my 'soft brick' mode I'm in?
Alright, I've tried using the rescure firmware and all the files, but every time I try I get it a FAIL on odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says in red "SECURE CHECK FAIL : PIT".
I've spent 12 hours on this now...
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
DualJoe said:
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
Click to expand...
Click to collapse
I tried Kies on two different computers, but whenever I connect my S3 it just says "connecting" forever and never connects to my phone. Tried solutions online, couldn't get it to work.
And I have root access, but can't boot into recovery (says "recovery booting" for a few seconds then goes black screen). So I don't know if I can flash the bootloader manually, unless I did it with odin.
And those seem like busy developers, would they really have time for me? I don't even know what I would ask. :S
Sorry I seem so clueless, I'm just upset/sad/confused/everything right now. Saved up for this phone for a while.
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
DualJoe said:
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
Click to expand...
Click to collapse
Hmm when I had a functional phone it said I had the ZSEMC1 stock rom, so the "bootLoader_ZSEMC1.tar.md5" flashed from odin should work? I got it off this thread: http://forum.xda-developers.com/showthread.php?t=2189063
But I don't know if I'm still on ZSEMC1 since I flashed XXEMC3 with odin (but I think it failed) and I got soft bricked.
What could go wrong? Could I hard brick it by installing that bootloader?
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
DualJoe said:
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
Click to expand...
Click to collapse
I tried the ZSEMC1 and XXEMC3 and XXEMG5 bootloaders from this thread and they didn't work: http://forum.xda-developers.com/showthread.php?t=2189063
(shows unsupported dev type)
How do I get the 'latest' boot loader? That thread is the only one I could really find.
And also I did try installing cwm through odin. It didn't "fail" but it doesn't work when I try to boot into recovery. I'm guessing this has to do with my locked bootloader?
Really don't know what to do at this point. :/
New motherboard if you have tried the fixes .
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
DualJoe said:
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
Click to expand...
Click to collapse
I tried cwm and twrp. They both install successfully on odin but have the same "recovery starting...." message and they don't work. I've tried connecting the USB when it's in this "recovery" mode but my computer doesn't detect it so I can't start up adb and interface with it.
And also, I doubt I'm going to be able to find any in northwest ohio.I wonder if this service is any good?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Looks promising for $50.
Sorry I've been on this problem for so long guys, I'm just stubborn and can't get over the fact that it's a software brick and I need to replace hardware. :/
I am trying to fix my i9300 UK.
I Had it running just fine with Ultima ROM and TWRP with Googy kernel.
Then one day it suddenly would not boot. Just got stuck on the samsung boot logo. I could not even boot to recovery.
So I asked and got a very short answer that I should flash the stock rom. So I downloaded the stock rom for my phone from sammobile and tried to flash it with ODIN.
However, I just get a FAILED sign when I try. What can I do?
Spacedementia87 said:
I am trying to fix my i9300 UK.
I Had it running just fine with Ultima ROM and TWRP with Googy kernel.
Then one day it suddenly would not boot. Just got stuck on the samsung boot logo. I could not even boot to recovery.
So I asked and got a very short answer that I should flash the stock rom. So I downloaded the stock rom for my phone from sammobile and tried to flash it with ODIN.
However, I just get a FAILED sign when I try. What can I do?
Click to expand...
Click to collapse
The i9300 is the international version. The us one is another depending on ur carrier.
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
The i9300 is the international version. The us one is another depending on ur carrier.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know,
I made sure to download the correct file
Spacedementia87 said:
Yeah I know,
I made sure to download the correct file
Click to expand...
Click to collapse
Try running as an administrator if you have done that try Odin v 1.85.
tallman43 said:
Try running as an administrator if you have done that try Odin v 1.85.
Click to expand...
Click to collapse
Yeah, I am running as admin.
I will try 1.85 now.
Thanks
tallman43 said:
Try running as an administrator if you have done that try Odin v 1.85.
Click to expand...
Click to collapse
When I use 1.85 I get:
Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is Kies running .
Download a clean stock rom and try again ,
Reads as faulty download/ wrong firmware/ damaged nand .
Spacedementia87 said:
When I use 1.85 I get:
Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Mmm! Couple of things you could try.. Try adb boot into recovery also try and flash PhilZ recovery with Odin look here and choose .tarmd5 version >> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 << also what does it say on your screen when you are in download mode.
tallman43 said:
Try running as an administrator if you have done that try Odin v 1.85.
Click to expand...
Click to collapse
JJEgan said:
Is Kies running .
Download a clean stock rom and try again ,
Reads as faulty download/ wrong firmware/ damaged nand .
Click to expand...
Click to collapse
This the the file I am trying:
I9300XXEMD2
Should be ok. I am on three.
I have looked in the task manager and can't see any reference to Kies on there. I guess I could uninstall just in case.
What is very worrying now is that I just tried to flash again using ODIN 3.04 and it said I needed a .pit file to repartition. Re-partition is not checked so I don't know why it is asking for this.
tallman43 said:
Mmm! Couple of things you could try.. Try adb boot into recovery also try and flash PhilZ recovery with Odin look here and choose .tarmd5 version >> << also what does it say on your screen when you are in download mode.
Click to expand...
Click to collapse
what do you mean by adb boot into recovery?
I will try to flash that custom recovery now.
While in download mode it says:
ODIN MODE
PRODUCT NAME: i9300
CUSTOM BINARY DOWNLOAD: 4
CURRENT BINARY: Samsung Official
System Status: Custom
UPDATE: Trying to flash that PhilZ recovery says I have not included a PIT file again. This is bad isnt it?
Spacedementia87 said:
what do you mean by adb boot into recovery?
I will try to flash that custom recovery now.
While in download mode it says:
ODIN MODE
PRODUCT NAME: i9300
CUSTOM BINARY DOWNLOAD: 4
CURRENT BINARY: Samsung Official
System Status: Custom
UPDATE: Trying to flash that PhilZ recovery says I have not included a PIT file again. This is bad isnt it?
Click to expand...
Click to collapse
Sorry Yes :crying: I think you need service damaged partition..
tallman43 said:
Sorry Yes :crying: I think you need service damaged partition..
Click to expand...
Click to collapse
How do I do that?
Spacedementia87 said:
How do I do that?
Click to expand...
Click to collapse
Warranty service center..
You can try what JJEgan suggested Quote:
Is Kies running .
Download a clean stock rom and try again ,
Reads as faulty download/ wrong firmware/ damaged nand .
But it's not looking good i'm afraid
tallman43 said:
Warranty service center..
You can try what JJEgan suggested Quote:
Is Kies running .
Download a clean stock rom and try again ,
Reads as faulty download/ wrong firmware/ damaged nand .
But it's not looking good i'm afraid
Click to expand...
Click to collapse
Damn
I guess I will have to pay for the repair.
Is there no way to find the official pit file and flash that?
Spacedementia87 said:
Damn
I guess I will have to pay for the repair.
Is there no way to find the official pit file and flash that?
Click to expand...
Click to collapse
Well I was going to suggest that but most of the posts I have seen from people who try to do that ended up with hard bricked phones I have never tried that and to be honest would never like to try doing it...But it's your phone!! if you try search option top of page their are some threads somewhere with instructions and pit files to download. Good Luck
Spacedementia87 said:
Damn
I guess I will have to pay for the repair.
Is there no way to find the official pit file and flash that?
Click to expand...
Click to collapse
Yes search the forum .
(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international
tallman43 said:
Well I was going to suggest that but most of the posts I have seen from people who try to do that ended up with hard bricked phones I have never tried that and to be honest would never like to try doing it...But it's your phone!! if you try search option top of page their are some threads somewhere with instructions and pit files to download. Good Luck
Click to expand...
Click to collapse
Well thanks for the help.
I think I will take it in to get it fixed. I had the screen die on me not so long ago and had to take it in for a replacement screen then, so this is a little frustrating.
Oh well
Thank you very much
I have searched threads here as well as other places and have had no success.
Device: Verizon Samsung Galaxy S3 (SCH-I535)
Info: Stock, non-root and no ROMS
Current firmware: KitKat 4.4.2
I was trying to use Odin 3.09 to revert to the firmware version 4.1.2 (which I got from http://www.sammobile.com/firmwares/) in order to install CM 11. I entered the phone into download mode and entered the 4.1.2 firmware file. Everything loaded and connected fine. I clicked Start and it stopped at aboot.mbn and failed because I think 4.4.2 has a locked bootloader. I also think I tripped the Knox Security flag and therefore it is now softbricked. The phone can still go into Download mode but not recovery mode.
I followed two guides to unbrick it:
1) http://forum.xda-developers.com/showthread.php?t=2581166
The microSD card method did not work. I have not tried JTAG.
2) http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Odin once again fails and cannot flash the VRALEC.bootchain.tar.md5 file, leaving the same error as before:
HTML:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This error appears on my phone:
HTML:
SW REV CHECK FAIL: Fused 2 > Binary 0
What can I do now?
scorpadorp said:
What can I do now?
Click to expand...
Click to collapse
you could post your question in the correct forum http://forum.xda-developers.com/galaxy-s3-verizon
this here is i9300 international forum, so probably no one can help, espacially because i9300 has no knox.
scorpadorp said:
I have searched threads here as well as other places and have had no success.
Device: Verizon Samsung Galaxy S3 (SCH-I535)
Info: Stock, non-root and no ROMS
Current firmware: KitKat 4.4.2
I was trying to use Odin 3.09 to revert to the firmware version 4.1.2 (which I got from http://www.sammobile.com/firmwares/) in order to install CM 11. I entered the phone into download mode and entered the 4.1.2 firmware file. Everything loaded and connected fine. I clicked Start and it stopped at aboot.mbn and failed because I think 4.4.2 has a locked bootloader. I also think I tripped the Knox Security flag and therefore it is now softbricked. The phone can still go into Download mode but not recovery mode.
I followed two guides to unbrick it:
1) http://forum.xda-developers.com/showthread.php?t=2581166
The microSD card method did not work. I have not tried JTAG.
2) http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Odin once again fails and cannot flash the VRALEC.bootchain.tar.md5 file, leaving the same error as before:
HTML:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This error appears on my phone:
HTML:
SW REV CHECK FAIL: Fused 2 > Binary 0
What can I do now?
Click to expand...
Click to collapse
I know my post maybe can't help you but I has the same problem with a Samsung Galaxy Mini 2 and I go to a SAMSUNG service and they resolved me. And I think this brick is because any Samsung device is not able to downgrade to an old version...
Read this about downgrade:
http://forum.xda-developers.com/showthread.php?t=2613745&page=2