Hi All,
Ok, here is my problem.
I cannot update my SGS2 and I'm stuck in a problem I can't seem to do anything about.
I (foolishly) downloaded a JB ROM and attempted to install it, but it failed. Since then I have been getting the error:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
These are my details:
Phone: Samsung Galaxy S 2 - UK on Three Network
PC: Windows 7
This is what I have done.
I have tried to connect my phone to Kies, but it will not connect - no matter how many times I try to re-install the driver.
I have downloaded maybe 6 or 7 ROMS that apparently would work in an attempt to "downgrade" to Ice Cream Sandwich. Everytime I try to install using Odin, I get the "FAIL!" message after "NAND Write Start!!" (using the reset to download ROMS on my phone).
I am lost as to what to do, and Odin will not allow any ROM I try to write.
Can anyone please help me? My Nokia N95 is just not up to the job!
Many thanks in advance,
Simon
http://forum.xda-developers.com/showthread.php?t=1457458
Please read all instructions carefully before attempting anything!
"To err is human, to forgive is divine"
Sent from my SGS II
you need to flash a new rom using odin.
just download any rom that can be flashed through odin and read the instructions on any of the many threads on it
immortalneo said:
http://forum.xda-developers.com/showthread.php?t=1457458
Please read all instructions carefully before attempting anything!
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Ok, I've gone over and over this - there doesn't appear to be a .PIT file in any of the downloads, so I can't complete some of the steps mentioned.
Here is a selection of ODIN's responses:
<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> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<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> boot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Can't open the specified file. (Line: 1828)
<OSM> All threads completed. (succeed 0 / failed 1)
I have a feeling I have now totally screwed everything up and there is no-way back.
Can anyone else help me from this nightmare?
Many thanks
Simon
Can you still get into download mode (power..vol down..home key combo)?...if you can, all is not lost...
As for Odin.....
1) Make sure Kies is NOT running....use laptops task manager to kill it lf it is
2) disable any firewalls
3) open Odin as an administrator
4) use the usb cable that came with your phone....don't rely on just one usb port...try them all...
5) put your phone in download mode and connect to laptop via usb....
6) wait for com box in odin screen to change colour and begin (following any/all instructions given TO THE LETTER)
7) leave the option to repartition WELL ALONE
.....And.....
8)......DO NOT play with .pit files unless you have ABSOLUTELY NO OTHER CHOICE.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Thanks Keith ... I will work through your suggestions...
No problems fella.....let us know how you get on...... good luck..
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 08:37 PM ---------- Previous post was at 08:26 PM ----------
Also...take a look at this thread...
http://forum.xda-developers.com/showthread.php?t=1449771
It might well be able to help if you are still having no success after retrying the above steps.....
Edit....ahh, I see that immortalneo has already beaten me to it with the link.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Btw.....if it's any use, I've copied my copy of 3 UK's branded 4.0.3 ICS firmware up to dropbox
LINK REMOVED
Feel free to download it if you need it. I've used it on both my and my wifes S2's without issue.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Btw.....if it's any use, I've copied my copy of 3 UK's branded 4.0.3 ICS firmware up to dropbox.....
http://db.tt/iEoOLHaT
Feel free to download it if you need it. I've used it on both my and my wifes S2's without issue.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Fantastic - thanks Keith ... I'll let you know!
AGGGHHH!
Ok, followed all your advice Keith, and it got further than ever before, but failed at the boot.bin process (see below)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPI_I9100H3GLP4_I9100NELP4_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> Firmware update start..
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I feel we may be getting somewhere, but not sure what to do next!
Any ideas?
One more thing......maybe....
Can yiu still get into recovery (CWM)
If you can, try wiping cache, dalvic and data before going into download mode to odin flash the firmware....alternatively try flashing a custom rom through cwm then using Mobile Odin to flash the firmware.....otherwise I'm outta ideas....sorry fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 04:25 PM ---------- Previous post was at 04:02 PM ----------
Edit......
This next idea is untested and entirely hypothetical.
As a starting point, you need a working rooted kernel. From what you said in your OP, I *think* you're running JB (sort of).......
SOMEBODY PLEASE CORRECT ME IF THE FOLLOWING IS WRONG.........
1) download an odin flashable JB compatiable PhilZ modified stock kernel with CWM and flash in Odin
2) download any recent CM10.1 cusROM + GApps
3) use the newly installed CWM to flash the cusROM & GApps
4) wipe cache, dalvic and data and reboot.....hopefully with success........
Don't try this until someone else has commented as to the sanity of this idea........
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
One more thing......maybe....
Can yiu still get into recovery (CWM)
If you can, try wiping cache, dalvic and data before going into download mode to odin flash the firmware....alternatively try flashing a custom rom through cwm then using Mobile Odin to flash the firmware.....otherwise I'm outta ideas....sorry fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 04:25 PM ---------- Previous post was at 04:02 PM ----------
Edit......
This next idea is untested and entirely hypothetical.
As a starting point, you need a working rooted kernel. From what you said in your OP, I *think* you're running JB (sort of).......
SOMEBODY PLEASE CORRECT ME IF THE FOLLOWING IS WRONG.........
1) download an odin flashable JB compatiable PhilZ modified stock kernel with CWM and flash in Odin
2) download any recent CM10.1 cusROM + GApps
3) use the newly installed CWM to flash the cusROM & GApps
4) wipe cache, dalvic and data and reboot.....hopefully with success........
Don't try this until someone else has commented as to the sanity of this idea........
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Thanks Keith ... I appreciate you having spent time on this...
The only option I have is with Odin as I cannot get into any recovery mode. I also do/did not have CWM installed on the phone.
I can also get to the "Firmware upgrade encontered an issue ...." message on boot, but I cannot connect my phone to Kies. It just wont recognise it (I did uninstall it anyway!).
It *starts* to flash, as when I look on the screen, the progress bar starts to move, but after a very short time it then "FAILS!"...
I will hang fire until someone looks into your other idea before trying anything else.
EDIT: It was a JB ROM that seems to have gone wrong, but it never actually ran so now trying to downgrade - even tried Gingerbread ROM which failed too.
Also just thought I'd mention that the "CUSTOM BINARY DOWNLOADS:" now shows "YES (11 counts)" which has gone up... Don't know if that is significant, or helpful!
Just a quick question before I dash out...
Do I need to have my SIM installed when I flash? I have it in another phone at the moment as its my work number, but have not even thought I might need it in...
ratzz said:
Just a quick question before I dash out...
Do I need to have my SIM installed when I flash? I have it in another phone at the moment as its my work number, but have not even thought I might need it in...
Click to expand...
Click to collapse
No, u don't need a SIM.
"To err is human, to forgive is divine"
Sent from my SGS II
Go pay a friend a visit, ask him/her to use their computer (Windows), get 3 samsung cables fron where ever, download 3 different odin versions, install latest kies, reboot, kill all 4 kies applications. Do the odin thing.
Just to make sure, get a couple of Custom into a flash drive, along with siyah v5 and v6 from Gokhnanmoral.com (I9100 right?).
Flash only code, phone and csc.
Forget about the existance of pit files for now.
Sent from the little guy
Gastonw....can you comment on my "hypothetical idea" comment? Does it have ANY merit?
Is there even a *possibility* it could help?
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
@keithross39
I think it would work, as long as the OP can flash the CWM containing kernel via Odin!
"To err is human, to forgive is divine"
Sent from my SGS II
Keith, the man who got a Ph.D in Mobile Odin via xda
I always read your posts on workarounds and step-by-step guides, you truely are into android, keep it up.
I actually overlooked what you just posted because I was thinking on suggesting the same thing with a different kernel, so yeah, what you are suggesting can work, because it did in the ICS era.
Whenever you get stucked at nand you could flash a custom kernel (.tar) so it'll allow you to get to CWM. Once you get there, you can flash whatever you want.
I mentioned siyah in case he was on ICS ( siyah v5 ) or on jb ( siyag v6), Philz indeed is a better option for all jb related ROM.
Sent from the little guy
Lol....thanks for your vote of confidence Gastonw....it's been a steep learning curve.....got my first smartphone 15 months ago, didn't start modifying it until 9 months ago....and since then I've modded 2 other phones (3 in total) and a Tab.......if you find something interesting, learning becomes enjoyment....but I'm still far far away from PhD level....lol
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Lol....thanks for your vote of confidence Gastonw....it's been a steep learning curve.....got my first smartphone 15 months ago, didn't start modifying it until 9 months ago....and since then I've modded 2 other phones (3 in total) and a Tab.......if you find something interesting, learning becomes enjoyment....but I'm still far far away from PhD level....lol
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Sounded cool, didn't it?
Sent from the little guy
Related
I have a Telecom NZ-branded GT-I9100.
I flashed it to Android 4.0.3 courtesy of XXLPH on The Android Soul's website: http://www.theandroidsoul.com/xxlph/
Then, I decided I wanted vanilla Android 4.0.3 rather than having the Samsung apps (especially Contacts. I wanted to see Android's People app).
So I went to this link and downloaded CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.zip as I'm running XXLPH.
ODIN seemed happy with this and was successful. I had the yellow triangle on boot, which I was expecting except that's as far as my phone went.
So I've gone back to ODIN to flash the original XXLPH files again but now it fails. Here's the output from ODIN.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please tell me that my phone is salvageable, and how I can do this?
If you can get into download mode, either get stock firmware from Samfirmware.com, or alternatively find the PC version of Checkfus which will enable you to download the latest firmware available for your carrier/country you'd normally get with Kies. In the case of Samfirmware stock, follow whatever instructions they have for firmware downloaded from their site. For Checkfus downloaded stock, follow the instructions in Intratech's official firmware thread on here.
If you can't get into download mode, try a jig. And if the jig doesn't work, you'll need either a JTAG repair or return it to Samsung/your carrier for repair.
Thanks MistahBungle - I *can* get in to download mode and ODIN recognises that I've plugged the phone in. It's just that when I try to flash the XXLPH files it fails.
I'll give the stock firmware from Samfirmware a go.
Update: found this firmware http://www.hotfile.com/dl/147082515/6c9ebc0/I9100TDOKH1_I9100TTNZKH1_TNZ.zip.html
Will download & see how we go.
Make doubly sure Kies & any of of it's processes aren't running in Task Manager in Windoze. If they are, kill em.
That error you got sounds like a corrupt download. But I guess we'll know more when you try that stock you found.
I used the .tar in the PDA section of ODIN and it went cleanly.
Now my phone boots with the Telecom splash, then the Samsung GALAXY SII (with the pretty glowing S) splash. It seems to be cycling through those two screens. And has been doing so for about 5 minutes now.
Pulled the battery, replaced & rebooted. Same thing is happening, the phone seems to be stuck between the Telecom splash (although after the first time it doesn't play the jingle) and the Samsung Galaxy SII splash.
Factory reset.
I can't get into the phone to do that though.
you sure you have a 9100 or a 9100T ? , i have a telecom nz s2 and its a 9100t.i have flashed the kernal but havent flashed over to remove that yellow triangle, the hotfile.com rom is the same one im using, should be fine,if your phone boot loops then you should still have a chance or be able to boot into recovery/download mode?
boot loop thread
http://forum.xda-developers.com/showthread.php?t=1108499
it's absolutely the GT-I9100T.
I've figured out how to get into Recovery. Have "wipe data/factory reset" and rebooting now.
Sorry. What I meant was go into recovery & wipe data. Brain not working too well today
MistahBungle said:
Factory reset.
Click to expand...
Click to collapse
Thank you dude - the factory reset did the trick.
Of course, now I'm back on 2.3.3!
Good man No worries
haakuturi said:
Thank you dude - the factory reset did the trick.
Of course, now I'm back on 2.3.3!
Click to expand...
Click to collapse
EDIT: SOLVED. ANSWER IS ON PAGE TWO. REMOVE BATTERY BEFORE ODIN REBOOT YOUR PHONE, AND THEN BOOT IN RECOVERY AND FLASH SUPERUSER. THANKS TO KINGHORSEY FOR THE FIND.
Hi guys,
I'm using a Rogers Galaxy Note on ICS 4.0.4. I'm trying to root it at the moment. I downloaded Odin version 3v 1.85 with CMW found at this link: http://forum.xda-developers.com/showthread.php?t=1584576
So, installed the driver, the phone is recognized in device manager as Samsung Mobile USB CDC Composite Device, and when I plug it into Odin it gives me com 4 ok.
Clicked PDA, added the CMW tar.md5 and pressed start. Odin tells me it has installed the image properly. My flash counter went up one notch, but when I reboot into recovery I still get to Android's stock recovery (which does not allow me to flash Superuser from my SD card).
I'm probably missing something here. What am I doing wrong?
Thank you
Technically....nothing
I'd run it again.....g
I'm at round number 7 haha and still no CWM.
theinvisiblehand said:
I'm at round number 7 haha and still no CWM.
Click to expand...
Click to collapse
Holy cow !!...LOL
Fort Knox note.......:laugh:
Can you list your step sequence ??
Wasn't there a script installed on the Rogers ics OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
Try flashing cwm but don't tick reboot phone on Odin. Once flash is succesful , use 3 button combo to get into recovery. Flash su zip and reboot. Use file explorer of your choice to remove recovery script. Once that's done flash cwm again and hopefully it will stick.
Gubment Cheeze
Froid said:
Wasn't there a script installed on the Rogers ice OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
Click to expand...
Click to collapse
just reviewed the Rogers ICS 4.0.4 root from braway's thread, and didnt see it, but still looking..
this is the 3rd user root issue in 24 hours....
something is going on....g
gregsarg said:
Holy cow !!...LOL
Fort Knox note.......:laugh:
Can you list your step sequence ??
Click to expand...
Click to collapse
There you go. I'm running all of this on Windows 8 preview 32 bits. The samsung driver I use is the version 1_3_2200. I think its the most recent.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Froid said:
Wasn't there a script installed on the Rogers ics OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
Try flashing cwm but don't tick reboot phone on Odin. Once flash is succesful , use 3 button combo to get into recovery. Flash su zip and reboot. Use file explorer of your choice to remove recovery script. Once that's done flash cwm again and hopefully it will stick.
Gubment Cheeze
Click to expand...
Click to collapse
Might as well try that. Where will I find said recovery script? Thank you
Try mount/system/etc folder. It would start with install.recovery or something similar. It won't let you delete it until you're rooted using es file explorer or root explorer type of app.
Gubment Cheeze
---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------
I'm going from memory here so you might wanna search for more info and if this is even your issue..
Gubment Cheeze
theinvisiblehand said:
There you go. I'm running all of this on Windows 8 preview 32 bits. The samsung driver I use is the version 1_3_2200. I think its the most recent.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
yep...root is good,....
still looking for this script issue....g
If you pull the battery after flashing cwm but before it reboots then going into recovery and flashing superuser you'll bypass the install script.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
gregsarg said:
yep...root is good,....
still looking for this script issue....g
Click to expand...
Click to collapse
thanks a lot
Kinghorsey got it.......g
All right it worked! I pulled the batterie before it rebooted and it worked. Thanks a lot everyone. I'm backing up my system as we speak before I reboot.
Thanks!
Probably should put a " solved" into the thread title...so other users can find this..
King ?
Is this info in the root thread ??
Edit:
He's gone I guess....thanks King.....Great find....g
I don't recall if its in the root thread or not. It seemed to be an issue specific to Canadian Notes and their OTA ICS updates. I'm not sure if it also applies to the AT&T version.
There was a thread about it a while back.
Surest way to bypass the script completely is to flash a copy from samfirmware. The script isn't in that copy and you don't get all the bugginess associated with an OTA update.
I highly recommend that method.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
kinghorsey said:
I don't recall if its in the root thread or not. It seemed to be an issue specific to Canadian Notes and their OTA ICS updates. I'm not sure if it also applies to the AT&T version.
There was a thread about it a while back.
Surest way to bypass the script completely is to flash a copy from samfirmware. The script isn't in that copy and you don't get all the bugginess associated with an OTA update.
I highly recommend that method.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the reply....
Bigjoe has added your "trick " into the super thread, and I think it's a great addition to users here ...(credit given )
I searched the thread completely, and found no mention of that trick .....but it's in the thread header now.
Again ...THANK YOU !!!!...g
Just a heads up to anyone who needs to go this route....pulling the battery will get you into cwm recovery the 1st time. Once the phone is booted up the user will lose their custom recovery and will be replaced by stock 3e recovery.
Gubment Cheeze
I'd love to take credit for this fix but I can't - I only read about it here and didn't discover it on my own. In fact, I never had this problem since I used Odin + samfirmware.com as opposed to OTA updating.
The moral of the story is that even stock.upgrades are better when you are in control.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ----------
Froid said:
Just a heads up to anyone who needs to go this route....pulling the battery will get you into cwm recovery the 1st time. Once the phone is booted up the user will lose their custom recovery and will be replaced by stock 3e recovery.
Gubment Cheeze
Click to expand...
Click to collapse
From what I understood this only happened if you didn't pull the battery.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The script is still in place. Pulling the battery just gets you into recovery to root. Once you're rooted you can delete the script. Then you need to flash cwm again and you should be good to go.
Gubment Cheeze
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
'<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Baraa01 said:
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
' Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Heya!
Your SIII looks bad with this stripes!
Have you flashed your StockROM via Odin while you were in DownloadMode? If it don't be in DownloadMode, it also can't be flashed.
Try to download a firmware from samfirmware.com and to flash it via Odin in the PDA field while your device is in DownloadMode!
And when you have finished, go to Recovery and Wipe your Data&Cache!
Greetings...
Sent from my GT-I9300 using xda app-developers app
Of course I used ODIN to flash stock rom, it didn't work.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Of course I used ODIN to flash stock rom, it didn't work.
Click to expand...
Click to collapse
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
TheRealFelix0212 said:
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you read my first post, yes, I did flash it in Download Mode via ODIN.
Well, it obviously had a problem writing the rom into the phone (nand write failed). You may have a hardware fault. Do you have the nand chip that suffers from sds?
Sent from my GT-I9300 using xda premium
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
ratatattata said:
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
Click to expand...
Click to collapse
Still failed in ODIN. You reckon the eMMC chip is damaged?
Baraa01 said:
Still failed in ODIN. You reckon the eMMC chip is damaged?
Click to expand...
Click to collapse
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
jmpmjmpm said:
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Same isssue here, same screen and everything.... I tried for over a month and nothing... got an expensive door steep. If you have any lights about this... let me know!!
try flashing recovery only and then flash 3.8 again through recovery.
try flashing the resurrection rom from the checkrom site through odin in download mode..
galaxys3lover said:
try flashing the resurrection rom from the checkrom site through odin in download mode..
Click to expand...
Click to collapse
Been there, done that. Nothing happens. Same error, Re-Partition failed.
please help?
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
I hope I've not ended up with this phone mentioned in this thread....purchased a phone from ebay and the seller said its stuck on Android SIII logo...I can get into download mode but before I attempt anything can someone tell me if this is a UK phone so I can apply the correct ROM (if it works!).
Also, currently the phone does not charge, battery is fine as i've tried the battery from own s3 and vice versa...both batteries are fine but the phone does not appear to charge...I'm hoping this is ROM related....
Any help will be much appreciated otherwise its an expensive gamble!
BTW...In the download mode the product bit is blank and does not say Samsung galaxy s3 like my own working phone does...
So my unrooted, Jellybean SG2 decided to crap out on me. It's stuck in the dread boot loop! OH NOES! I got a new SG2, so I don't care if my SG2 what software is put on it. I just want my precious data (music, photos, videos). Some said it couldn't be done, but I found this thread on here that said otherwise.
Making use of SiyahKernal, it should be possible to mount my SG2 to my laptop. I decided to Odin this puppy up. I wanted to go by the tutorial the other thread posted, so I tried using the Jellybean T-Mobile rom (which my SG2 was using). I used the ROM, for my device, from Samsung Updates. I made sure to restart my PC, shut down any processes by Kies, etc, etc before starting Odin. When I went to flash the ROM, Odin froze for a good 15 minutes. I decided that nothing was going to happen and unplugged my S2.
So, here I am, stuck with the message, "firmware upgrade encountered an issue in Samsung Galaxy S2." I, somehow, made the problem worse. I just want my data. As you can see, I'm a total noob with this stuff. Please help!
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
MistahBungle said:
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
Click to expand...
Click to collapse
Thanks. I'll give it a try and post my results.
Ricequakes said:
Thanks. I'll give it a try and post my results.
Click to expand...
Click to collapse
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
thuva06 said:
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
Click to expand...
Click to collapse
Let's hope. If only it would even flash. Just tried and this is what I got on Odin:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> amss.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what it said on my SG2:
nand_write: flash write fail
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
theunderling said:
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
Click to expand...
Click to collapse
I'm a bigger noob than I thought. Sorry, guys.
Mod Edit
Thread closed
[OP] found correct forum
malybru
Forum Moderator
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.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)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2