Hello
I wanted to run custom neatrom and when I was uploading PhilZ-cwm6-XXMS1-OXA-4.53.tar with (custom rom + root) with odin, mobile didnt turn on - was hanging on samsung logo. So than I have decide to go with 3 files rom with odin and it failed !
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Right now my battery is drained - probably it is not charging anymore I can't go to download mode (probably because of drained battery). Is there a way to rescue my phone or I have to buy new motherboard ?
Motherboards are *way* more expensive than buying a second battery and standalone charger......have you tried charging the battery normally?
There's a whole shed load of things to try before considering a new motherboard....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Motherboards are *way* more expensive than buying a second battery and standalone charger......have you tried charging the battery normally?
There's a whole shed load of things to try before considering a new motherboard....
Click to expand...
Click to collapse
OK - I will try to charge my battery from external charger - maybe it is a fault of newly mounted charging board from china.
If I will manage to run download mode again what should I do - try to send that 3-file rom with PIT, MODEM etc. ?
baszek said:
OK - I will try to charge my battery from external charger - maybe it is a fault of newly mounted charging board from china.
If I will manage to run download mode again what should I do - try to send that 3-file rom with PIT, MODEM etc. ?
Click to expand...
Click to collapse
You have the i9100 international variant...correct?
Wait until you have a charged battery then follow this guide (every step, as many times as it takes)......
Troubleshoot a failed odin flash by hopper8
http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
There is a link in that guide to a guide I wrote that covers replacing the usb board....you might want to read that too, because it isn't as simple as just taking the old one out and putting a new one in......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
You have the i9100 international variant...correct?
Wait until you have a charged battery then follow this guide (every step, as many times as it takes)......
Troubleshoot a failed odin flash by hopper8
http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
There is a link in that guide to a guide I wrote that covers replacing the usb board....you might want to read that too, because it isn't as simple as just taking the old one out and putting a new one in......
Click to expand...
Click to collapse
OK I have charged the battery at external charger - now phone can go to download mode - but when I was trying to flash with XXLSJ - PDA PHONE CSC files - then I get fail in odin with thesame <ID:0/006> Complete(Write) operation failed.
baszek said:
OK I have charged the battery at external charger - now phone can go to download mode - but when I was trying to flash with XXLSJ - PDA PHONE CSC files - then I get fail in odin with thesame Complete(Write) operation failed.
Click to expand...
Click to collapse
Have you read those two threads I mentioned?
(Hint....read the guide about the USB Connector first)
http://i.imgur.com/rVnFwJM.jpg
Yep I have read about usb connector - usb charging board must be thesame rev version as previous one. For sure my charging board from china is wrong version - you think that after changing it to proper version ordered from EU I will manage to flash it with odin ?
@baszek
Mebay. Chinai micro USB connctor are usualy faulty. Please use a non-china one.
But if NAND warite keeps failing i"m afraid you need to replace your motherboard.
MikiGry said:
@baszek
Mebay. Chinai micro USB connctor are usualy faulty. Please use a non-china one.
But if NAND warite keeps failing i"m afraid you need to replace your motherboard.
Click to expand...
Click to collapse
I have allready bought proper rev 2.3 charging board - I hope that this time Odin flash will work.
MikiGry said:
@baszek
Mebay. Chinai micro USB connctor are usualy faulty. Please use a non-china one.
But if NAND warite keeps failing i"m afraid you need to replace your motherboard.
Click to expand...
Click to collapse
If it isn't 'official Samsung' then whatever you buy is going to have been made in China and not everything that comes from China is automatically faulty.
And please don't advise the op that the first choice and the only way to rectify the nand write issues is to replace the motherboard. The guide I linked him to provides a whole list of processes that have been shown to get other users successfully past this point and recover their devices.
http://i.imgur.com/rVnFwJM.jpg
@keithross39
I'm not "forcing" anybody to buy sth new. Thing that i'm writghting are based on my personal expirience / expirience "gained" on XDA.
By "non-china" one i meant a official signed motherboard.
But there is another thing. He olso had wrong USB bord revison. O
0.2 i think. The one , that should be there is 2.3.
Now he has 2.3.
If the process doesnt go any further than NAND write failure (even with 2.3 revison) + all the drivers , cables and other staff is 100% ok , than motherboard is dead.
Hello
So I have mounted new charging board with a proper rev number. It looks like phone is not charging or there is no charging animation - I am not sure - anyway I have run ODin and flashed some 4.1.2 RoM with Pit and repartition with success - status pass - green status etc, but after restart phone is still hanged on samsung logo. Tried other Rom 4.1.2 without Pit and phone is hanged at samsung logo too.
Should I try different roms or it is bricked ? (still can go to download and flash without a problem any rom)
Can you get into recovery?
If you can, you could try flashing PhilZ recovery, and then flashing a custom rom......probably best to stay away from the lollipop cusRoms though....
Try one of the Jellybean or KitKat based cusRoms.....when I used my S2 as a daily device, it was running Markox89's KK based CM.
Here's the link to the PhilZ thread......Look for the recovery flashable zip rather than the odin flashable tar.....
http://forum.xda-developers.com/showthread.php?t=1877270
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Can you get into recovery?
If you can, you could try flashing PhilZ recovery, and then flashing a custom rom......probably best to stay away from the lollipop cusRoms though....
Try one of the Jellybean or KitKat based cusRoms.....when I used my S2 as a daily device, it was running Markox89's KK based CM.
Here's the link to the PhilZ thread......Look for the recovery flashable zip rather than the odin flashable tar.....
http://forum.xda-developers.com/showthread.php?t=1877270
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Nope I can't go to recovery - it shows only samsung logo - I can go only to download mode. I have allready tried 3 roms and phone is not starting (stuck at samsung logo after successful odin flash)
baszek said:
Nope I can't go to recovery - it shows only samsung logo - I can go only to download mode. I have allready tried 3 roms and phone is not starting (stuck at samsung logo after successful odin flash)
Click to expand...
Click to collapse
The fact that you are getting successful firmware flashes indicates that the motherboard isn't in need of replacing....
So it's just a case of persevering with the device until you recover it.....
The guide I mentioned (Troubleshoot a failed odin flash) really is the 'definitive' resource for people in your situation. You need to follow every suggestion/step in that guide as many times as it takes to get your phone up and running again.....any other advice is irrelevant...
Recovering the device is entirely in your hands.......
http://i.imgur.com/rVnFwJM.jpg
Try to flash CWM recovery from Odin (using the .tar file) from the link keithross39 had posted.
Ok So I know what was wrong.
It appeared that I have i9100G - version G - I am ****i** silly.
Flashed right now - first PIT File - then Rom from sammobile - now it had bootloop - went to Recovery mode - full wipe/cache etc - it is working now THannk you guys Could you plz recommend me some good stable custom rom for i9100G ?
I manage to flash neatrom - it sucks
Right now I am using CM 10 from http://forum.xda-developers.com/gal...ficial-cyanogenmod-10-2-i9100g-t3175239/page3
and it is much better feel then neatrom with stock.
Related
Hi all,
My GS3 (International version) is on a constant boot loop. I was browsing the internet and then it crashed into a loop, The phone was getting on my nerves abit as i was constantly having to reboot just to use it...but this time it crashed on me for good (Yes it was rooted on firmware 4.1.1)
I managed to get into CWM and wipe all data, then get into Download mode and flash a stock rom via ODIN.
All seemed to be going well, ODIN said PASSED and the phone rebooted.
Then i got the little green android robot with the blue spinning box in the middle of him/her....Boots back to initial start up screen, then little green android, then intitial start up etc etc etc....Never leaves these screens.
I cannot enter recovery nor can i enter download mode. There is nothing i can do to stop this.
I have tried repeatadly taking out the battery and puttin back in but no results.
Any tips?
Thanks in advance
From a very stressed out GS3 owner
After much playing around i managed to get back into DOWNLOAD mode...Unfortunatly no matter which STOCK rom i put on i can never get past the initial loading screen where it states my Phone device name/brand etc. Someimes i get to the little android with the spinning blue square in its belly...But then it loops again.
Ive tried about 6 different fimwares now, all stock.
Ive managed to put CWN on them too and done the whole WIPE DATA/DELVIK cache...but nothing changes!
Help please
I am in a right pickle now, Any help would be really really really appreciated. Feel gutted!
Tried everything i can think of or find, but my problems are just getting worse. I can now no longer use ODIN as i get the following:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300ODDALF1_I9300DDLEA_HOME.tar.md5 is valid.
<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>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The firmware i was trying to flash is suppose to be the ORIGINAL S3 firmware.
On the DOWNLOAD MODE screen on the S3, next to product name i have nothing.. Used to say GT-I9300
Custom Binary: No
Current Binary: Samsung Official
System Status: Custom
I can get into DOWNLOAD MODE but cannot access Recovery.
What to do now?
The phone is 4 months old :crying::crying::crying::crying:
ToonTonic said:
I am in a right pickle now, Any help would be really really really appreciated. Feel gutted!
Tried everything i can think of or find, but my problems are just getting worse. I can now no longer use ODIN as i get the following:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300ODDALF1_I9300DDLEA_HOME.tar.md5 is valid.
<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>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The firmware i was trying to flash is suppose to be the ORIGINAL S3 firmware.
On the DOWNLOAD MODE screen on the S3, next to product name i have nothing.. Used to say GT-I9300
Custom Binary: No
Current Binary: Samsung Official
System Status: Custom
I can get into DOWNLOAD MODE but cannot access Recovery.
What to do now?
The phone is 4 months old :crying::crying::crying::crying:
Click to expand...
Click to collapse
Code:
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is the troublesome part..in your flashing frenzy you have somehow corrupted the partition layout...now try flashing the 3 part method..search for it..you will need to use mx.pit to repartition you flash memory..tread cautiously and do only what you understand..
Why do people use Odin??????? Still escapes me
i see a post with a bootloader a pit and a rom to repair gs III and get a phone like the first time try to flash it and see
edit = i find it http://forum.xda-developers.com/showthread.php?t=1825272
Thank you for your replies, I am still stuck but am currently downloaded the emergency firmware that kondronaute posted a link too.
Fingers crossed it works!
kondronaute said:
i see a post with a bootloader a pit and a rom to repair gs III and get a phone like the first time try to flash it and see
edit = i find it http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
Unfortunatly this didnt work for me, ODIN said FAIL
Then 2nd time around it just got stuck at SetupConnection
What is the exact model (aka "variant") of your phone? (if you don't know, you can use this app to find out)
Simonetti2011 said:
What is the exact model (aka "variant") of your phone? (if you don't know, you can use this app to find out)
Click to expand...
Click to collapse
I cant use tha app as im stuck on a boot loop, i can only access Download mode. I have a GS3 GT-I9300 International version UK. Just took it to the store i bought it at and theres nothing they can help me with other than telling me to contact samsung.
I have tried nurmerous files via ODIN, even PIT files but i get no results. ODIN just says FAIL.
When i enter DOWNLOAD mode on my GS3..prior to pressing volum up i have a small yellow triangle, but it still allows me to go on. Prior to Download mode i can only get as far as the initial boot screen.
ToonTonic said:
Unfortunatly this didnt work for me, ODIN said FAIL
Then 2nd time around it just got stuck at SetupConnection
Click to expand...
Click to collapse
sorry send it back to samsung
i see another post for repair that but need a Jtag ... not for simple user... :crying:
ToonTonic said:
I cant use tha app as im stuck on a boot loop, i can only access Download mode. I have a GS3 GT-I9300 International version UK. Just took it to the store i bought it at and theres nothing they can help me with other than telling me to contact samsung.
OK what ssn is listed under the battery .
Its pointless proceeding until the model is confirmed as your symptoms are identical to flashing wrong firmware .
I have tried nurmerous files via ODIN, even PIT files but i get no results. ODIN just says FAIL.
Possible corrupt NAND then .
jje
Click to expand...
Click to collapse
JJEgan said:
ToonTonic said:
I cant use tha app as im stuck on a boot loop, i can only access Download mode. I have a GS3 GT-I9300 International version UK. Just took it to the store i bought it at and theres nothing they can help me with other than telling me to contact samsung.
OK what ssn is listed under the battery .
Its pointless proceeding until the model is confirmed as your symptoms are identical to flashing wrong firmware .
I have tried nurmerous files via ODIN, even PIT files but i get no results. ODIN just says FAIL.
Possible corrupt NAND then .
jje
Click to expand...
Click to collapse
SSN: I9300GSMH
Whats the number to samsung lol
Click to expand...
Click to collapse
I have spoken with Samsung who have sent me out a jiffy bag to send back to them with my phone and they will fix under warranty. Im at my wits end with it. So in the mean time im back my iPhone (errrgghh i hate it).
Out of interest is there anything i need to do to the phone prior to sending it back?
On the download scren (after pressing Volume Down + Home + Power) prior to pressing volume up i have a small yellow triangle on the bootom of that screen, is this normal??
When pressing Volume Up it goes into ODIN mode with the big green android robot..Text underneath says DOWNLOADING...I know this is right.
Top left of screen looks as follows:
ODIN MODE
Product Name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Anything i should try and fix? Not that i can lol
zoot1 said:
Code:
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I met the similar message it it is very bad.
Most likely died MMC.
You can try to flash PIT file but it seems to me its partition is dead, however as well as all remaining partitions. Now only motherboard changeover
as i9000 said:
I met the similar message it it is very bad.
Most likely died MMC.
You can try to flash PIT file but it seems to me its partition is dead, however as well as all remaining partitions. Now only motherboard changeover
Click to expand...
Click to collapse
ToonTonic said:
I have spoken with Samsung who have sent me out a jiffy bag to send back to them with my phone and they will fix under warranty. Im at my wits end with it. So in the mean time im back my iPhone (errrgghh i hate it).
Out of interest is there anything i need to do to the phone prior to sending it back?
On the download scren (after pressing Volume Down + Home + Power) prior to pressing volume up i have a small yellow triangle on the bootom of that screen, is this normal??
When pressing Volume Up it goes into ODIN mode with the big green android robot..Text underneath says DOWNLOADING...I know this is right.
Top left of screen looks as follows:
ODIN MODE
Product Name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Anything i should try and fix? Not that i can lol
Click to expand...
Click to collapse
Any answers to this?
Yeh its pretty messy
ToonTonic said:
Any answers to this?
Yeh its pretty messy
Click to expand...
Click to collapse
All the actions are meaningless and do not lead to nothing...
Stuck in bootloop, help please!
ToonTonic said:
Hi all,
My GS3 (International version) is on a constant boot loop. I was browsing the internet and then it crashed into a loop, The phone was getting on my nerves abit as i was constantly having to reboot just to use it...but this time it crashed on me for good (Yes it was rooted on firmware 4.1.1)
I managed to get into CWM and wipe all data, then get into Download mode and flash a stock rom via ODIN.
All seemed to be going well, ODIN said PASSED and the phone rebooted.
Then i got the little green android robot with the blue spinning box in the middle of him/her....Boots back to initial start up screen, then little green android, then intitial start up etc etc etc....Never leaves these screens.
I cannot enter recovery nor can i enter download mode. There is nothing i can do to stop this.
I have tried repeatadly taking out the battery and puttin back in but no results.
Any tips?
Thanks in advance
From a very stressed out GS3 owner
Click to expand...
Click to collapse
Hi, did you manage to get yours solved?
I have the exact same problem i was on a custom samsung 4.1.2 rom and while browsing the net it crashed was in bootloop now i cant get out, went into recovery mode and factory reseted didnt help, now i cant go back into clockwork mod at all, so i went into download mode and opened odin flashed a stock rom just keeps saying fail after nand write, tried a custom rom and same issue and fails, now when i pull the battery out and turn it back on all i get is a message saying firmware upgrade encountered an issue please select recovery mode in kies and try again! Helppppp!
Thankss
Contact Samsung, or seller, will need to be repaired under warranty.
In all that did you even try using kies to get back to original rom?
Even if it's rooted? Thanks
Sent from my Nexus 4 using xda app-developers app
At some point in the phones life I must have flashed a stock att because now I can't return to stock I717M. ODIN MODE say I am using a Product: SGH-I717 : Instead of the intended SGH-I717M. I am investing the time because the phone is crashing imminently and/or immediately after a odin stock flash.
Oddly enough my Product numder and SN: are coming back with an error in Kies aswell. At this point I am flashing in circles :silly: and really just want to start from the lowest common denominator for this phone as a base with proper .pit and CSC ... etc. so this is 100% official stock I717M and all the threads I read are resolved by standard flashing protocol but not mine!
Many of the automated flashes that you just drop on the PDA line cause issues in stock recovery mode by missing the CSC and I can't account for all the crashing. Perhaps SOMEHOW finding my way back to "M" will do this ? I think... : )
Thanks ahead of time everyone for your help :good:
Go back to Gingerbread using these files flashed through Odin:
http://forum.xda-developers.com/showthread.php?t=1657279
Agoattamer said:
Go back to Gingerbread using these files flashed through Odin:
http://forum.xda-developers.com/showthread.php?t=1657279
Click to expand...
Click to collapse
Thanks for the quick reply ... I have done this though and receive an error with the .pit file.
I am using ODIN 1.85 it starts the process and ends in error. The phone reads SECURE CHECK FAIL : PIT
But unlike the individual in the thread I have a more serious issue because I am using a I717M and using this method and receiving the error he had with a mismatched phone !?! This to me indicate somehow my phone thinks it's a i717( ) not a I717M. Kies sees only a I717 and when I force a "Firmware and Upgrade Initialisation" from the menu it stays exactly the same. When I use SGH-I717M and my SN to restore to factory I get : Model name: SGH-I717M : 'SGH-I717M' does not support initialising. All you can click is OK,
Now what ?
Thanks again for the help ...
futiless said:
Thanks for the quick reply ... I have done this though and receive an error with the .pit file.
I am using ODIN 1.85 it starts the process and ends in error. The phone reads SECURE CHECK FAIL : PIT
But unlike the individual in the thread I have a more serious issue because I am using a I717M and using this method and receiving the error he had with a mismatched phone !?! This to me indicate somehow my phone thinks it's a i717( ) not a I717M. Kies sees only a I717 and when I force a "Firmware and Upgrade Initialisation" from the menu it stays exactly the same. When I use SGH-I717M and my SN to restore to factory I get : Model name: SGH-I717M : 'SGH-I717M' does not support initialising. All you can click is OK,
Now what ?
Thanks again for the help ...
Click to expand...
Click to collapse
not that I am a brainchild in this department, or any other for that fact, but I read a lot and have not heard of this one.
I sometimes think if I ask questions, would or could this inspire others to come up with the solution.
have you called your carrier? can they not help you?
have you tried uninstalling drivers and re-installing for Kies purposes? to try an "emergency firmware recovery" (I think that's what it was referred to as)
what modem shows on phone? and can you flash appropriate modem to carrier?
you mentioned PIT file in PDA slot? I have always used .TAR files (maybe same thing, different terminology?)
as I said, just questions that come into my mind. maybe help troubleshoot?
good luck my friend
one more***********************
I just went to link recommended by the GOAT guy ( sorry for raping your name).
noticed post #1 was titled for BELL and listed files. then I went down and saw post #4 were files for ROGERS. did you notice that?
you didn't say which was your carrier
The only thing I can think of is I had a brick at one point and me and a service tech JTAG'd in the files : could this explain why my phone thinks it isn't a I717M?
I using Mobilicity and a AWS modem/hack
Thanks for advice everyone this is quite the problem and is clearly unresolved as it just wont take the .pit file and if I use the pda/phone part only only the pda will even flash from that post. So no CSC, graveyard, pit... all of which I need.
:crying::crying:
I think this phone is a mess.
Sean
Not sure of it make any difference at all.....but I used Odin the other day and it was version 3.0.7 located in this post:
http://forum.xda-developers.com/showthread.php?p=42806745
Bubbajoe40356 said:
Not sure of it make any difference at all.....but I used Odin the other day and it was version 3.0.7 located in this post:
http://forum.xda-developers.com/showthread.php?p=42806745
Click to expand...
Click to collapse
I used it and it proceeded unlike 1.85 but I still have a fail on the PIT : and when I reset and go into download mode it says SGH-I717 and Secure Check Fail: PIT at the bottom: in recovery mode i get a smashed android and a error about a genaric CSC and that it is still using ATT CSC !?!? Also a very concerning error regarding sdcard E: cannot be found ?!? this is new...
Yes and it WILL NOT BOOT '.':crying:
Can anyone confirm too if I should be seeing I717M in odin and recovery modes
At one point I worked with a service tech at the local JTAG shop took us all afternoon but we got it to boot out of a hard brick loopback dongle wasn't working. I THINK he put the ATT kit on my phone from JTAG and that is the problem now ...
Does anyone with a good handle on this stuff know if I can use the feared "NAND ERASE ALL"I am scared but it seems to make sense that is what it is ...
Anyone care to say they agree I have no right to hold anyone accountable and at this point I am running out of optinos ... it would semm..
Sincerely S:silly:
Does not matter what region phone you have. Whether it is att or a Canadian carrier this ROM should install. Did you follow directions in that thread fully? Since you are using a pit you have to select repartition in the check boxes.
Sent from my SAMSUNG-SGH-I497 using xda premium
Couldn't be more straight forward and I followed the instructions exactly. There were frankly no more than 2 sentences of instructions. Which I followed, regarding the check box for repartition it got selected automatically when you put something on the .pit line. I have not tried without repartition checked. I figure this might be a case for NAND ERASE ALL
See If it takes the csc..and firmware
the partition table shouldn't need flashed, all variants are partitioned the same.
What is up with these canadian variants? There are so many posts about not being able to flash, superuser not taking, modem having to be reflashed. Just don't see this with the ATT version. I wonder if there is another script causing all this....
studacris said:
See If it takes the csc..and firmware
the partition table shouldn't need flashed, all variants are partitioned the same.
Click to expand...
Click to collapse
Here is the log from Odin 3 3.07 : (1.85 just crashes with a PIT error as specified before) However Odin 3 proceeds as follows for those who can shed more insight I will be grateful to no end:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ABOOT_SGH-I717M_I717MUGLA2_user_CL875155_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_KERNEL_AMSS_SGH-I717M_I717MUGLA2_user_CL875155_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I717MUGLA2_phone_secure_Q1_BMC_REV_00_CL870799.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-I717M-CSC-BMCLA2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> rpm.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> cache.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> tomb.img.ext4
<ID:0/006> userdata.img.ext4
<ID:0/006> amss.bin
<ID:0/006> mdm.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
-----------------------------------------
here we can see odin blazing through without an issue but !! the same .pit error occurs and after reset the system boots to TWRP recovery instead of stock !?!?!! A huge log of errors also occur regarding not being able to find internal storage the TWRP directory and EMMC not formatted or mounted ?!?
When I boot to ODIN it says current binary : CUSTOM ?!
I am really confused now..
I need a couple things answered :
1) does I717(M) varient display the (M) in ODIN when on the proper download mode or do they all say I717 ?
2)When Odin mode says stock binary : Yes (for all intents and purposes is it a mirror copy (modem,boot,recovery,pit etc.) ?
3) If not what is likely different ? (ie how could I send it back for stock repair or resell as the original)
4) Now everything seems to be worse in the sense that every rom is locking and freezing after you click android to start setup after a long wait possibly the second screen it reboots ?
5) in stock recovery I get a Update from RB fota mode now ? how does that work from recovery ? I thought it would need internet access at least.
THANKS EVERYONE :good::good::good::good::good::good::good:
A couple questions for you..... You mention in stock recovery you get "Update from RB fota mode now" but you said earlier that after you install and it reboots you back to TWRP? Now which is it?
Are you installing the stock gingerbread ROM with ODIN when in "Download Mode" on the phone? Hold "Power" and "Volume Down" down. Can you get the phone to boot enough to format the internal (usb) memory? I don't know if that option is available in stock recovery or if it functions correctly in TWRP. This is not the same as a full wipe. I know stud will say it has nothing to do with installing ROMs. But I know 2 people that had a similar issue as you ( 1 being me) and the only way the write would take is if the internal (usb) memory was formatted. This leads me to believe there is some kind of script stored there on Canadian variants.
Agoattamer said:
A couple questions for you..... You mention in stock recovery you get "Update from RB fota mode now" but you said earlier that after you install and it reboots you back to TWRP? Now which is it?
Are you installing the stock gingerbread ROM with ODIN when in "Download Mode" on the phone? Hold "Power" and "Volume Down" down. Can you get the phone to boot enough to format the internal (usb) memory? I don't know if that option is available in stock recovery or if it functions correctly in TWRP. This is not the same as a full wipe. I know stud will say it has nothing to do with installing ROMs. But I know 2 people that had a similar issue as you ( 1 being me) and the only way the write would take is if the internal (usb) memory was formatted. This leads me to believe there is some kind of script stored there on Canadian variants.
Click to expand...
Click to collapse
That is a very intelligent perspective; presently I can say that I got the stock recovery in but only with ODIN 1.85 with phone boot-loader update checked off (gret in the new 3.x versions of ODIN). So I could never get the phone to format without error when using all 5 items
For the record THE ONLY WORKING STOCK SO FAR is :
[Stock ODIN] AT&T Jelly Bean Download
http://forum.xda-developers.com/showthread.php?t=2261598
I found a Stock ODIN JB Bell Download from another site but it froze at every screen during setup until it would just reboot itself (seems like Kernel might be wrong though)
None the less me and all other (1717M)'s are in fact isolated in this condition to ATT stock roms and honestly; to be frank it could explain why I have been frustrated with the blaze modems on this thing since last July when I got it. I have spent days at a time trying to find a modem that wont drop and require a power cycle + 10 minutes to come back online.
Maybe Mr. Goat you are right, maybe me and a bunch of others are literally stuck with a I717 because of lingering scripts, wouldn't surprise me because TWRP was sticking around for a long time until I checked the bootloader format and only in 1.85 oddly enough.
WHAT I think the rational ones reading this should be questioning is why does my Download Mode ODIN read I717 no (M) after all these attempts to wipe and format and when using (M) varient stock roms the phone wont boot and crash like it has the wrong kernel (or modem) fixed with a ATT stock rom (on the surface anyhow). This would be fine if I didn't have a BELL serial number and clearly its something else.
For the extremely advanced I once found a thread (can't for the life of me find it again) where someone managed to change the model of the phone because it got changed I think during a JTAG. This would make sense as I had to do this too. I downloaded an app on the play store which used root and I allowed it to adjust SD-EXT for SD caching (BIG MIS-TAKE) Hard brick was the result. While I was getting help the app would auto execute on startup and time was running short so I imagine he pushed me to ATT stock. I want to make it bell again as my phone crashes a lot and I am not sure if this can even relate to it or not.
THANK YOU EVERYONE I AM VERY GRATEFUL
Did you even try the Odin version for Bell Jellybean?
http://www.hotfile.com/dl/213003896/d4f7f24/I717MUGMD1_I717MBMCMD1_BMC.zip.html
Or how about Bell ICS version for odin?
http://www.hotfile.com/dl/163095548/c1447e9/I717MUGLF4_I717MBMCLF4_BMC.zip.html
If you install a stock ATT ROM, the phone will report back as an I717. It has nothing to do with serial number. It has to do with software.
If you can install a stock ROM and it works then immediately format that USB memory and then do a factory reset.
And if your phone crashes alot, try a new battery. You might think it is good but it could be giving an incorrect voltage.
wish i could say this worked as it didn't still stuck without the (m) : using those downloads it loads to black screen have to hold power 15 seconds and it vibrates and back to the black screen...
Hello every one ... I know as a fact that I717M could be hard on patience .. as Bell uses HSPA and LTE instead of 2G and the others .. hard to find the right modem and others.
When i had that problem to revert to stock ... I got the full file for Stock Bell Jellybean (around 700 meg file zip) ... unzipped .. used odin 3.07 (recently seen 3.09 really good too) and placed the .MD5.TAR file into the PDA (called AP in odin 3.09) section .. had just the auto reboot checked and flashed good with it (important that it is the in second line option (the PDA one or AP in odin 3.09)
PS: I had my phone in download mode when flashing as it should ... (reboot holding volume down)
For the customer rom or counter that says you have been a bad boy .. I had to go on the thread for counter reset and that did it ....
hope it will help .. (recently had to do that often as I am trying tons of ROMs)
Cheers
---------- Post added at 11:39 AM ---------- Previous post was at 11:38 AM ----------
I've been trying to convert the firmware on my M250S to I9100. I've followed the guide to the letter and all the drivers are installed as well as Kries. I also made sure Kries was inactive while Odin was up. This is how far I get before it fails.
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If anyone has any ideas I would appreciate it. I've tried everything I can think of including using different firmwares, pits, as well as versions of Odin. That's as far as I get before it fails.
How are you trying to do it? As I recall (I don't have an M250 so didn't pay crazy attention) there's two ways to convert one to an i9100. One involves Odin failing intentionally. Although, the method involving a pit file doesn't intentionally fail. If you're flashing pits and they're failing that's definitely not good... Potential brick.
Search for a guide in the s2 general section, I read one a couple weeks back which members were using with success.
You can also click the link in my signature and follow the steps there. As you're not doing a 'regular' Odin flash bear in mind some things will be a little different.
Sent from a galaxy far, far away
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Edit: I tried another computer and it worked flawlessly. So now I'm running on i9100. Although I'm having a few issues. It doesn't show my battery charging when the usb is plugged in. Also when I shut down my phone it doesn't completely shut down. It goes to a screen with a green battery. This actually happened before but I thought perhaps changing firmware would fix it. Before this the device would come back on automatically when I tried to shut it down and I read it could be the usb port so I cleaned the usb port with alcohol.
Slywolf15 said:
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Click to expand...
Click to collapse
Ah so it may not be a case of what you're trying to do, it might be a case of how the flash is set up/what hardware (pc, cable etc) you're using. In that case, use the link in my signature to troubleshoot it. Perseverance is key. Also have a look here : http://forum.xda-developers.com/showthread.php?p=45131292
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
ZivC12 said:
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
Click to expand...
Click to collapse
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Slywolf15 said:
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Click to expand...
Click to collapse
it happened to me with bad uk unbranded rom, try to flash new rom, if you cant turn on the phone switch battery
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 3.185 will install this ROM successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated. I have also tried other Odin versions including 3.07.
Thank you!
jvaldez33 said:
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 185 will install this rom successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Note II Won't boot.
dragonstalker said:
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Click to expand...
Click to collapse
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Warranty costs if phone has been rooted
jvaldez33 said:
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Click to expand...
Click to collapse
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
jvaldez33 said:
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
Click to expand...
Click to collapse
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
miketoasty said:
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Update on events
mikelikesbikes said:
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I have been in the IT business for nearly 25 years and have seen many problems resolved if you have the time and desire to put forth the efforts to investigate the problem every day with a clear head. With that being said I for some unknown ADD moment and decided I wanted to troubleshoot my sons girlfriend's Note II that was having problems. Now here I am wrestling with a problem like a drug addict looking for their "next fix". I am very stubborn and extremely capable of diagnosing hardware and software problems but this one truly has me stumped!
With this being a problem I decided to purchase another Note II off EBay to experiment with and was listed with similar problems, Red Light and wouldn't boot.. I figured for $125 the worst that could happen is I could disassemble it and part out the LCD/Digitizer and recuperate my investment. There are some problems I like researching and resolving and this is one. I personally believe the problems on both Note II's may both related to the charging board based on the information on the following post on another forum: http://forum.xda-developers.com/showthread.php?p=45678812#post45678812. I will elaborate a little more shortly.
Let's go over my three day 50 hour marathon. Here is the only download that successfully downloads but the phone will only splash the "GALAXY NOTE II" screen and turn off after a successful install. I have downloaded Odin 3.185 and 3.07 and get the same results:
sch-i605-16gb.pit
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
Unless the problem resides on my laptop I think I have eliminated the issue of having a good cable(s) by using official Samsung cables, NEW RocketFish cables and they all seem to work fine for viewing and transferring files via USB. I also have an external battery charger and can guarantee an excellent charge on the battery(s). The current files I was recommended to use came from a single Zipped file: GalaxyNote2UnlockVerizon. Please let me know if there are a different set of files I should be using?
Unless I have downloaded the wrong files? I have attempted to install the following bootloader with Odin versions 3.07, 3.13 and 3.185 and they all fail: BootloaderBaseline2.tar.md5. All I know at this moment i am stuck at a point that I have the Note II in a state that will not allow me to boot.
Lets discuss some hardware issues that I need to explore a little further. Since I have a spare phone to test with I thought I would swap logic/motherboards and see if I had any different results. Unfortunately they are exactly the same on both Note II's. Now comes an interesting issue I stumbled upon. When I VERY CAREFULLY reassembled it on an ESD Mat I somehow dislodged or did not securely fasten the display cable to the logic board and when the power was pressed the phone seemed to start booting but there was no display. The sound and the blue light came on normally. I had hoped the original ROM was now installing. I powered off the phone, removed the battery and disassembled it to discover my mishap, so I reconnected the display cable and reassembled the phone only to see the original problem was still present.
Has anyone else had a charging port issue that caused similar problems? I was planning on ordering a new charging port off Amazon today just to try. Any additional information would be greatly appreciated.
Thank all of you that contribute to this site. It is amazing how many problems can be resolved when great minds are put together.
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
No Red Light
droidstyle said:
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
Click to expand...
Click to collapse
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
jvaldez33 said:
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
Click to expand...
Click to collapse
look for a n7100 tar, or maybe "I think, can't remember" there was a stock tar in the I605 mega roll thread somewhere. flash one of them. Try not to use the kies tar as i've had problems with them being corrupted before. Know you've tried both the methods already. Just a suggestion in case you have not. Also check and make sure you have the right pda file.
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Which version of ODIN did you use? What kind of file(s) were you trying to flash?
Sent from my GT-I9300 using Tapatalk
I'm not sure but think it was Mobile Odin 3.65 and I was trying to flash CWM touch from xda.
Additionally, I think my battery charge may now be low after many attempts to recover it but will that matter bearing in mind I'm using Odin on my PC and the phone is connected to the PC by USB cable?
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
JJEgan said:
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
matrixmainframe said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
Click to expand...
Click to collapse
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
JJEgan said:
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
Click to expand...
Click to collapse
Kies is not installed on my computer and I have tried Odin versions 1.83, 1.85, 3.04, 3.06, 3.07 and 3.09.
I have also tried 'Samsung_USB_Drivers_1.5.27.0.exe' and 'SAMSUNG_USB_Driver_for_Mobile_Phones.exe' and remembering to uninstall then reboot and then install.
On one occasion it got as far as (can't remember the exact words) "Get PIT Mapping" but then just stopped there.
I cannot believe I have done anything other than corrupt the CWM recovery because all I did was try to flash CWM Touch and as soon as I pressed OK the screen went black with the word "Samsung Galaxy SIII GT-I9300". Those words just stay there because since then I can't switch the phone off. I thought that if I just reflashed CWM via Odin on my computer I would be able to get back into recovery mode and just restore my backup.
Appears I am mistaken and have ruined a very new and vey expensive phone.
The only other thing I seem to recall is that before I tried the Mobile Odin flash the battery was below 50% charge but I'm not sure if that's relevant?
This is usually a wrong file flash symptom .
JJEgan said:
This is usually a wrong file flash symptom .
Click to expand...
Click to collapse
Do you mean I'm trying to flash something I shouldn't?
Initially I tried to flash CWM Recovery but then decided just to try and get it back the way it was by trying to flash Android 4.1.2 again.
The file I have been using is "KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5" which I believe is from Sammobile and which is, I believe again, the ROM that the Galaxy S3 comes pre-installed with. Do you think it worthwhile me trying some other ROM?
I have been doing a lot more web research and some say that the battery charge should be more than 80%. Does this matter?
Won't the battery have been charging all the while the phone was plugged into into the Computer via the USB lead?
If I buy a separate charger and charge my battery to 100% do you think the Odin reflash will work then?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.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)
so close
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.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)
so close
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
llcoolveer said:
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
Click to expand...
Click to collapse
Nice to know I'm not alone but sorry you're having the same problem. Have sat down to do some more web searching and will let you know if I find a solution
Service centre new motherboard .
JJEgan said:
Service centre new motherboard .
Click to expand...
Click to collapse
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
llcoolveer said:
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
Click to expand...
Click to collapse
Please can you tell me what is "OG Recovery"?
Thanks
matrixmainframe said:
Please can you tell me what is "OG Recovery"?
Thanks
Click to expand...
Click to collapse
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
llcoolveer said:
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
Click to expand...
Click to collapse
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
matrixmainframe said:
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
Click to expand...
Click to collapse
I couldn't also....only when my battery was full charged....:good:
Succes....
The end
Okay, I started this thread so will end it now as follows:
1 Thank you to all those who offered help/advice/suggestions.
1a Some people do not read posts properly because even though I had specifically stated that I could not get into recovery mode some people proceeded to tell me to go into recovery mode and restore my rom.
2 Whilst I have recovered the full use of my phone I can no longer root it but that's ok because at least I have a phone that is comparable to the vast majority who choose not to root.
3 I will explain how I rescued it but obviously I don't really understand what the result is other than a usable phone so please don't copy.
4 Whilst I have no doubt one could damage a motherboard, that could only be done with very specialist software that most people would not have so the advice of some that I needed a new motherboard was ill informed. If you don't know the answer don't offer an unhelpful answer. Recommending a new motherboard is like a motorist taking his car into a garage with a blown fuse and the mechanic saying the only cure is a new car.
5 After a lot of research I found one lone website that explained that from July 2013 Samsung introduced a change to their ROMs which introduced an efs 2 file. Additionally it appears that once you have flashed/upgraded to an efs2 ROM you cannot then go back to an efs ROM.
6 This is above my understanding but I do know I did go from efs to efs2 and when I then encountered a problem I thought it a good idea to go back to my original (efs) ROM which I now believe caused my problem.
7 I did not know if I had found the answer but as I believed my phone was a paperweight at that point anyway I had nothing to lose and downloaded the GT-I9300.pit file and flashed with repartition selected. I then flashed Android 4.3 knowing it would be an efs2 ROM and my phone is now working again.
8 However, although my phone is now working again, I find that I cannot install a custom recovery nor can I root the phone but that is a small price to pay to have a brand new S3 working again.
9 Whilst it may not be wise to mess about with the pit file, it seems nothing can be lost to give it a go because even if it doesn't work you can still go for the new motherboard option happy in the knowledge you have tried everything.
10 I may start a new thread for advice on that matter but for the time being I'm just relieved to have my phone back and I stress again that it did work for my specific problem and whilst it might work for you please only do it knowing it may not work for your problem.