mess-up my S3 and please HELP~ - Galaxy S III Q&A, Help & Troubleshooting

Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.

Wrong thread.. Needs to be in Q&A

Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app

Kingybear said:
Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

NatTheCat said:
Wrong thread.. Needs to be in Q&A[/QUOT
I put it on Q&A already, but just wanted to have more people can help, so I put it on here. sorry for any disturb.
Click to expand...
Click to collapse

The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk

anyone can tell me how to delete the thread? Thanks

aguerito said:
The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
show the poor guy some love dude, your comments are abrasive he only wants help for his expensive phone sheesh
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
I wouldnt panic yet they say its very hard to brick an S3?
check around and see what you can find out
kk12175 said:
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium

jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
i was using Omega since v.9 until v33.2 at the last minute. and I found a video in youtube to resurrect my s3 by flashing Checkrom v4:
http://www.youtube.com/watch?v=ZNaQfdOi56E
tried it as well, but it seems doesn't work as it kept rebooting / hanging at the Galaxy S3 logo. And I tried to flashed some stock rom (combo file) from Samfirmware, no luck neither. Tried to flash some stock rom (3 files + pit) HK base rom. Same happened. Fail after Nand Write Start.:silly:
and now, couldn't get into CWM neither.

jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Been using adblock for a while myself and never had a hiccup .. excellent app..

Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium

johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I had flashed custom rom before, do you think I can still use the warranty? If yes, definitely going.

kk12175 said:
Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.
Click to expand...
Click to collapse
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg

johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ya i think so,,Same incident for previously after flashed one of the rom from this thread i went to sleep..The phone was reboot itself (stuck in bootloop) till i found at morning, my phone fuc**ing hot stucked in Samsung Galaxy SIII. After tried flashed using odin & using cwm not worked because my phone keep on rebooting. Once send to sammy centre i said that i put in charge, once wakeup in morning my phone keep on rebooting & so hot. So after one week they replace me new board for my s3 even they can see my cwm. I tried to delete cwm but cant. Thank god atlast they replace my s3. so only way is send to samsung centre. I face exactly same issue previously as you facing now

KKTHX said:
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg
Click to expand...
Click to collapse
sounds good. give it a try .. thanks MATE

kk12175 said:
anyone can tell me how to delete the thread? Thanks
Click to expand...
Click to collapse
Thread closed.

Related

bricked my phone SOLVED

I installed CWM touch, and superuser zip folder on my Galaxy note (att)
So I read a tut that said to wipe everything so I did on recovery mode, booted it up, worked good, went back because superuser didnt work right. I installed 3-4 times before it said success, now its goes to a crisp samsung logo, then goes blurry and stops.....
Stupid noob mistake I didnt backup anything. Figured it was simple as jailbreaking an iphone (which you cant mess up on, plug in, hit button, done)
I been trying it all but just cant get it to work.
If your phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
jayRokk said:
If youre phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
Click to expand...
Click to collapse
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
It boots to the samsung logo, but not lock screen. And I'm phoneless now Lol.
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
welchertc said:
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I been reading alot but seems like there is a hundred different explanations or ways to do it, and hard to find the right way?
liftedzuki said:
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
Click to expand...
Click to collapse
Yes its a .tar file
And search for it buddy there is a whole thread on official ICS and with it the CWM file and SU file to get you going
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.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> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
liftedzuki said:
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.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> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
jayRokk said:
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
:silly: I got it from a link in this note section, I should have seen that though.
So if I flash it, does it flash over the other flash? or does it add to it.
I'll continue readin.
Not all Samsung's are the same. You should only be getting tar files from your specific section. Keep in mind you need to match the model number
Sent from my SPH-L710 using Tapatalk 2
I would suggest going here and flashing one of these one clicks in Odin:
http://forum.xda-developers.com/showthread.php?t=1647756
Sent from my SPH-L710 using Tapatalk 2
And if I'm not mistaken you want the first link. I don't have a note so maybe someone here can chime in.
Sent from my SPH-L710 using Tapatalk 2
That link worked good. Thanks so much to everyone, I about had a heartache as I got my phone like 3 months ago, and just got ICS on it.
This time I'm gonna read alot more before I try it again.
Good idea. Glad it worked. If ya ever have any questions in the future , don't hesitate to ask BEFORE flashing.
Sent from my SPH-L710 using Tapatalk 2
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Haha it happens. Just be glad ya didn't end up with a huge note shaped paperweight
Sent from my SPH-L710 using Tapatalk 2
liftedzuki said:
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Click to expand...
Click to collapse
OP if your good to go, can you put Solved in your title....
thank you sir

[Q] Able to Flash 'Root66' but not true Stock ROM, ODIN Fails at Modem.bin

I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ArcelasTheNoob said:
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I605_VRALJB_Restore.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
cache.img
hidden.img
modem.bin
FAIL!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hey bro, have you unlocked the bootloader? if so and you're trying to go back to stock try the alternative stock odin file from imnuts.
EDITuno: http://www.androidfilehost.com/?fid=9390225151984927096
theres the link to his alt restore odin package. idk if that'll help fix the modem.bin failure, but it should help someway. hope it does! if you need anymore help you can pm me if you need to.
I'm curious to what rom you flashed. Was it for a Verizon note 2? If you get no network, try flashing the modem in recovery. That should solve it
Link for modem download.
http://www.androidfilehost.com/?fid=22946563261203878
Follow droidstyle's guide. Read his thread.
http://forum.xda-developers.com/showthread.php?p=34891181
EDIT: Just realized you are making multiple threads for the same question. Sorry dude, that's my only rule. No more help. Also noticed that you flashed an international rom. Good job :thumbup: This is why you are supposed to READ before flashing
Sent From My Sticky Note, Too?
Not needed
I apoligze if it looks like I posted this question multiple times. I was told to post in a different forum, but figured more info=better.
I returned my phone to Best Buy, replacement in a few days. So thank you for all the help, next time I'll be more careful.

[Q] Odin fails on SCH-i605 with CF-Auto-Root

Looks like I'm running into a brick wall trying to root this damn phone. first I soft bricked I but thankfully recovered but now after trying to root unlock using Casual and getting errors with generic usb drivers while in download mode I figured I'd be happy enough with just a root but ran into issues there as well. I'm currently running android 4.3 and every time I run Odin I get the following. I have tried v3.09. 3.07 and 1.87 and get the exact same error. I never had this much trouble rooting and unlocking my AT&T note 2 but Verizon is a nightmare. BTW I tried about 6 different versions of Casual and none worked. All of them take me to the recovery download screen and error out due to various reasons. In any case If anyone can guide me to get my I605 rooted, I would greatly appreciate it. On a side note could I downgrade to root66 rom and get rooted that way or would that brick my device? After that can I install custom roms? I don't have warranty any more and don't care about that. Just want root and custom roms and maybe an unlock
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.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> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This won't work on stock 4.3 rom.... There is only one way of rooting and that is not recommended at xda.... But bootloader will not unlock at present
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
This won't work on stock 4.3 rom.... There is only one way of rooting and that is not recommended at xda.... But bootloader will not unlock at present
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the response, I was afraid of that I guess ill have to wait until there is a bootloader unlocker available for it. That one method you talk of is kingo right?
Ya... Kingo is the only option that I know
Sent from my SCH-I605 using XDA Premium 4 mobile app

[Q] Bricked

Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
drunkensunday said:
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
Click to expand...
Click to collapse
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Oh then the first thing I did was try to odin this file: N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5
That failed, then I tried the 2 previously mentioned one click odin stocks.
Oh and I was on TWRP 2.6.1 but now I have no recovery.
drunkensunday said:
Oh and I was on TWRP 2.6.1 but now I have no recovery.
Click to expand...
Click to collapse
Have you tried odin twrp to your phone maybe it doesn't like you not having any recovery?
Cheryl
drunkensunday said:
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Click to expand...
Click to collapse
The MJ4 tar would've worked had you flashed it (you were on MJ4, JellyBean, but on a prerooted rom).
Having failed at MJ4, going with the NAB and NC5 (both KitKat), may have sent your system into a nosedive of confusion.
Tell me if you can get into download mode at all home + power + volume down).
Your version of TWRP is old, but that has nothing to do with this. You need to put your phone back to stock, then upgrade if you want to flash a KitKat rom.
The MJ4 tar file will put stock everything back on your phone, even recovery, so your TWRP will be gone...but you can get it back.
Let me know if you can get into download mode, and we can take it from there.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
drunkensunday said:
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
Click to expand...
Click to collapse
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
kaos420 said:
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
Click to expand...
Click to collapse
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
drunkensunday said:
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
Click to expand...
Click to collapse
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yes, but in a usb 2.0 port if it matters....
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
kaos420 said:
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
Click to expand...
Click to collapse
I think either trying it from a Windows PC (shouldn't matter, but why not try) or carefully selecting a Sprint store (root friendly tech, knows what he or she is doing) for an over-the-wire update, are worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a possibility that you had a bad download and also are you using the odin you from chain fire when you rooted? I had the same problem last month. I spent 5 hours trying to figure it out. Turns out I just had a bad download.
Sent from my SM-N900P using xda app-developers app
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
drunkensunday said:
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
Click to expand...
Click to collapse
did you have tep? did you tell them what you tried?

Bricked it? (Note 2)

So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> 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)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> 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)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!

Categories

Resources