I've managed to screw the pooch and got the Yellow Triangle of Death for my efforts. This is a VZW Note 2 sch-i605 that had(has?) a rooted 4.4.2. I tried to get TWRP installed and... yellow triangle. OK, the bootloader's locked up tight.
How do I get back to 4.3? Odin works - that is, it sees the phone, tries to do a NAND write and... party over.
Would trying to get an AOSP ROM loaded help? Can I get Odin to do that? I have the SDK but I guess sideloading is a loss without recovery.
This is what a failure looks like on Odin 3.10.7:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what rev. of Odin, TWRP, CWM, or even I605VRUAND3_I605VZWAND3_I605VRUAND3_HOME.tar.md5 I use... FAIL. And it's always that NAND write.
What options do I have?
I'm happy to say I beat this problem with a stick. The process was brutally ugly but it worked out. It starts with this video from Root Junky: https://www.youtube.com/watch?v=4qtbEevn1VA. But things didn't quite work out. At the very end, the process tanked with, on the phone, a message saying "bad magic string". The good news is I didn't get the VZW Yellow Triangle of Death. I got the Kies or some Samsung utilities Yellow Triangle of Death. Out of simple desperation, I tried the same process seen in the video but... I used the ND7 file instead of the MC3 file. I kept the 16G.pit file (maybe I didn't need to repartition, maybe I did). And the who process passed, front to back. Even more amazing, my data is intact and so are the home screens. I did, however, lose root. I know how to root under ND7, so I'll do that next. And...
Root Checker gave me a scare and said the phone wasn't rooted. I had to install SuperSU first. The only thing this particular rooting process still doesn't do is install SuperSU and BusyBox. I can install them via Play Store, so it's not a real problem.
The procedure used to root at the end:
Originally Posted by NetworkingPro (*)
Everyone, please use this .zip from now on. Please test, and let me know how it goes. I have simplifed the root be a single click root method.
Steps:
Download and unzip file.
Connect phone, ensure usb debugging is on, and device is authorized.
Double click GhettoRoot.bat
Download - Attachment 2922670
In full disclosure I have no idea where the source for this came from, I just made it pretty, and tried to make it super easy. Credit goes to 25yvdgpo06 for finding it. This root very well may work any many other devices, including other Samsung devices. Looking at the source I dont see anything that should hurt another device. Worst case scenario it simply doesn't root it. Please let us know if you try another device with success.
Click to expand...
Click to collapse
Related
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
aeinola said:
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
Click to expand...
Click to collapse
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Parva4 said:
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Click to expand...
Click to collapse
Send it for repairs and wait for several weeks to get it back? Very tempting. :cyclops: Lets call that plan B.
If i can do something to wake this baby up today or tomorrow i'll take it.
It sounds like you somehow softbricked your phone without even rooting it lol.
Anyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Instructions for unrooting: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
Hope this helps!
chunghanjie92 said:
IAnyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Click to expand...
Click to collapse
I did try that and it did not work. Maybe i did something wrong? Dont know... Im pretty sure the problem is with broken partition. I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Do not use pit or repartition unless you know what you are doing.
jje
Sent from my GT-I9300 using xda premium
aeinola said:
I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Click to expand...
Click to collapse
NEVER CHECK RE-PARTITION trololololo .... and never use PIT unless you are know what you doing.
Wow! These "never use PIT unless you are know what you doing"-comments are really helpful. Thank you guys! :good:
Follow the instructions on this site:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
The site tells you how to root a phone (look at the picture to see what you need/don't need to check; usually all you need to check is Auto-Reboot and nothing else)
After the phone's rooted you can download a ROM from this site http://samsung-updates.com/device/?id=GT-I9300 and flash it into the phone using the same method you flashed the file to root your phone
Thanks for the help. Odin says: "There is no PIT partition" and FAILS.
So i NEED to Re-Partition, any help would be appreciated.
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
aeinola said:
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
Click to expand...
Click to collapse
Same thing for me, and I'm stuck with this problem for 2 months now!!!
I read that for some reason unknown, some S3 got these fuc*** motherboards!!!
If u can solve this without samsung service center, please post!!!:good:
Of course you can manage it without Samsng Service center, if you want.
The procedure is:
1. download to PC the I9300 Service Manual;
2. buy motherboard;
3. replace it by yourself.
I was using the MIUI rom and I sold the phone. To deliver to the buyer I decided to go back to the stock rom but forgot to wipe and now I have the following situation:
- I can only get into download mode
- Odin recognizes the phone
- I tried to repartition the Odin reported successful operation (my model is 16gb)
- Tried to put other roms on the phone including those downloaded from the site sammobile, selecting only auto-reboot and f.reset.time
- With these steps could only get stuck in "nand write start ..."
- Tried installing kies but do not believe it can be something with the drivers because the odin recognizes the phone.
I read many posts but after two days decedi post to see if anyone would help me solve this issue
I'll be waiting for directions on how to proceed without worsening the scenario.
Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_HOME.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
have you tried restarting your computer or using another computer? or even a different usb port or cable?
ages ago I had a similar problem - never moved beyond the start point - simple restart solved it for me...no idea if that's the same situation as you.
Just throwing out ideas here; otherwise I'm not sure.
Sent from my GT-I9300 using Tapatalk 2
Tried to do this, but still stucked at nand write start...
One thing I noticed is that the progress bar on the phone at the "downloading mode screen" runs quickly, and then it stops at nand write start.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_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> modem.bin
<ID:0/005> NAND Write Start!!
At least I'm not alone
I have the exact same problem you have. Intl i9300, cannot enter recovery, only download mode. Flashing 16gb pit file works ok, however attempting to flash Stock rom gets stuck at Nand Write Start. Not sure what to do now, I guess I'll wait for responses here as well.
RePartition .
Fail Nand write .
Assuming you have read and are following the basics re an Odin flash ( if not go and read them ) .
This sounds in both cases like a damaged Nand >>> service centre job .
jje
I've not done much to my S3. Trouble started when I decided to install an OTA of Foxhound 1.8. Installation completed successfully but during the application upgrade (...you know the first boot message of 'Android is updating x of 365 apps). It froze and stuck there for like 15min so I decided to reboot it and all hell broke loose.
Started with 'Foxhound cannot mount recovery command..' etc. Which made me decide to flash my 16gb pit file, and since then all attempts to flash back to stock stall at 'Nand write start'.
I have backups of everything, even my efs. Problem is I can't even get to recovery to restore anything.
I'll keep trying I guess, worst case I'll just return it back to Samsung.
pull usb devices except s3 and be sure to have correct drivers then try again. you may even try it on another pc of course with installing drivers. if none of them works try flashing a kernel or recovery if it flashes then try to flash stock rom.if stucks again at nand write there may be a problem at emmc sect. but dont worry just do what i said if it fails there should be a solution
if you can enter the recovery mode u should be happy
to kamau can u send me the pit file you flashed thanks
zhjackss said:
to kamau can u send me the pit file you flashed thanks
Click to expand...
Click to collapse
There it is. I"m now working on resetting the flash counter from odin since I obviously can't install triangle away in preparation of returning it to samsung.
Hello everyone,
I am not sure whether this is the right place for my question but my Galaxy S II stopped working and I was wondering if anyone might help me?
I tried updating the FW from 2.3 to 4.0 (I'm guessing) through Kies and after about 45 minutes of seeing both screens (PC and Phone) unchanged, I ended up removing the phone. Next, Kies suggested an "Emergency Firmware thingy" (it said it in German so I wouldn't really know how to translate it). Tried again, after 45 minutes gave up once more.
Since then, I downloaded ODIN and tried to follow instructions I found online to flash it (first I tried with Ice-Cream, then with Gingerbread).
Ever since I removed it from Kies, it would only show a phone connected to a PC with a yellow warning triangle in the middle. Whenevery I use the Volume-Menu-Power button, the warning on changing the OS appears and then, when I press "volume up", it shows the green android in the middle and tells me it's downloading and not to turn off the device, though there is no downloading progress.
When I try with ODIN, ODIN recognizes the device on both USB ports - I found md5 files for Germany but every time I start it the Message window says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_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.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
and doesn'tget any farther than "cache.img".
I am at a complete loss as to what to do or try. I have had this phone for a year now, this is the first time I tried to update with Kies - the phone had not been rooted or anything else. The phone has no simlock (I don't know if any other information is relevant).
Any ideas or has my phone thus become the infamous brick? *pleasenopleasenopleaseno*
Thanks in advance for your time and patience - in case I've overread a thread with this exact same problems, I apologize and would appreciate if someone could re-direct me. I've already spent so much time looking for solutions, my concentration may have suffered.
Best wishes,
Junivere
Before flashing with Odin, did you kill all Kies processes from Windows task manager? If not, do that and then start flash.
Edit: And since you can access download mode, its not bricked...so you can relax
Sent from my GT-N7100 using Tapatalk 2
I9100?
Flash JB.
And try an older ODIN version.
And check kies like the above poster suggested.
Other usb port/usb cable might do the work too.
Sent from the little guy
Thanks for the replies!!!
I stopped all the Kies processes over the task manager before (was that enough?) and tried from both USB ports of my laptop (006 and 007 I guess) with equal results.
I used Odin3 v1.85 - is that too old or too new? Which version should I try?
And I am sooooooooo relieved it's not a brick!!!
Thanks again!
kinda old, try 1.3 or 3.x
And flash siyah v5 just for kicks.
Sent from the little guy
I tried again and I'll try to explain step by step, ok? Maybe you notice something I did wrong?
I killed all the Kies processes in the task manager like before.
I downloaded Odin 3 v.07 and started it. I had "Auto reboot" and "F.Reset time" checked and clicked on "PDA" to add the *.md5 file with the firmware.
I started the phone in the download mode and connected it to the PC, Odin recognized it alright.
I started and the first time, with the USB port in front, it stopped at "cache.img" in the message window.
I tried a different FW file and the other USB port further back and for the first time the phone shows a tiny bit of blue in the progress underneath "Downloading..." but in Odin it is now stuck at "factoryfs.img" for the last ten minutes,
The entire message window says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<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.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> factoryfs.img
Any ideas???
Best wishes and thanks again!!!
Flash siyah V5.
Sent from the little guy
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Junivere83 said:
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Click to expand...
Click to collapse
gokhanmoral.com
Siyah v5 for SII.
Put it on PDA, press start and flash away.
Sent from the little guy
Ok, so now I am starting to get slightly terrified:
When trying to flash Siyah 5 (Siyah-s2-v5.0.1), it stops there:
<ID:0/007> Added!!
<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> zImage
:crying:
Keep trying, you'll come around.
Another usb cable could help.
Another pc would as well.
Sent from the little guy
Ok, so the Sivyah v5 flash worked when I tried Odin3 v1.3 but I'm still battling with the actual firmware.
Thanks for your help so far, though - I'm really greatful and I'll keep trying.
My mission for today will be finding someone's cable and PC to borrow...
I'll keep you posted, though!
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Junivere83 said:
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Click to expand...
Click to collapse
Depends on what ROM you are flashing.
For instance, if you flash LS8 you'll get a 22 mb update to get you to LSD.
I would flash LSD straight up tho.
If you don't want a headache with odin no more, feel free to try Mobile Odin, it will perform all the flashing for you.
Sent from the little guy
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
jeemer said:
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
Click to expand...
Click to collapse
have a look here, maybe same challenge you are facing (I just flew over the thread).
I tried a few other things since.
Using Odin I tried flashing a stock ROM, after ending the Kies process and using a different USB. It all said it had worked, gave me a boot screen and said android is upgrading - optimising apps. It hung doing this at 10 of 70 or something. I tried resetting and it hung at 5 of 70, and when i reset again it just wouldn't get past that.
Tried flashing with a more recent stock ROM using Odin 1.3 as above, but it hung at system.img
Tried flashing with the more recent stock ROM using the latest Odin. The blue bar counted right up to full on my screen, then the phone reset.
It was sitting with the little 3d android character with the spinning 3d mesh sphere in his stomach. A blue line started counting up but has frozen about maybe 25% of the way along. After a short while Odin said PASS! and it all seems to have completed according to Odin
The android graphic was still spinning but nothing else was happening, the blue line would not progress any further.
After a few minutes the phone screen went black, and came up with the black and white Samsung Galaxy SIII screen for a second or so. Then it just went black again.
Here is the Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
When I turn it on now the same thing happens - the black and white Samsung Galaxy SIII screen comes on for a second or so and then the screen goes black.
If I try and put it in recovery mode the same thing happens. If I try to put it in download mode, that works.
Am I right in thinking I still have a hope to save it here since Odin still sees it? What do I try now? :/
http://forum.xda-developers.com/showthread.php?t=1840030
this is the only other suggestion I've found so far and it seems quite scary!
Flash a full stock rom using latest odin, immediately boot into recovery and factory reset.
Because you left the phone for so long on a firmware that was not SDS safe you may have nand memory damage, even if the file structure is still intact.
Sent from my GT-I9300 using Tapatalk
I tried doing a full flash again with the older stock firmware I started with. Got right through the whole process again, says it passed and it hung at the Android guy with the spinning mesh sphere.
I've never managed to get it into recovery mode since i got it in clockwork recovery mode a couple of occasions last night and it reset each time
Any suggestions as to what I could try to get it past this stage?
If it looks like I have nand memory damage would it be worth trying what's in that "scary" link i posted? :/
I tried flashing again to see if I could instantly get it into recovery and it failed for the first time
Here is the log
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm guessing this is a nand issue then? Is my only option at that point the link above (http://forum.xda-developers.com/showthread.php?t=1840030) ?
really don't get it.. tried it again and this time the whole process passed according to odin
same again though, android guy with spinning mesh... nothing for a while
phone eventually goes black, resets, samsung galaxy s3 in black and white. goes black. if i leave it for a while that screen will come up again, then it'll go black etc.
do i bite the bullet and try that method that involves nand reset all? please advise i'm in a bit of a pickle here as i'm in the middle of interviewing for jobs so i could use my phone.. do need to try and fix this asap if i can...
You can try flashing the rescue firmware, search in general forum, but if that doesn't work then you need a new motherboard.
Sent from my GT-I9300 using Tapatalk
ok - that seems to be this one for the s3 - http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
that look right?
downloading now. fingers crossed, thanks for your help i really do appreciate it.
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.