[Q] HELP WITH Galaxy Note N7000 Bricking - General Topics

Sigh, so i'm back again, 2nd time messing up my phone in 3 weeks......This time its going to cost me if I don't get an answer. I bricked my phone, i tried everything, and I mean everything, and it just won't finish flashing via Odin "pc" and I can't my mac to find the Pit files because of Stupid Kies.
Anyway, what did I do again? well i flashed the abyss kernel and then immediately via CWM tried to restore my Criskelo ROM and it would not get past the boot up screen, "the one before the animation" ....i wiped cache, tried restoring my stock Rom, tried wiping dalvick cache, you name it. None of that work, the only thing i could get into at the time was CWM and Odin mode "download mode".....I continued to try to figure it out for my self, and tried repeatedly to flash via odin.....back to a stock rom and i screwed up so much more now because of that. I can't get into clockworkmod anymore....i can't get into recovery, NONE OF THAT ....Only thing i see when i put on my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." ...I can get into Odin mode, but NOTHING ELSE. PLEASE SOMEONE HELPPPPP ME!. I don't know what I am going to do if i don't back my phone.
btw, if you wanted to know how far I got in the whole flashing via Odin.
It is showing this:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N7000XXLPY_N7000OXXLPT_N7000ATOLP2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
cache.img
NAND Write Start!!
factoryfs.img
"then it gets stuck and doesn't go beyond it....turn oof the phone and then i see this"
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1):crying::crying:

You are the victim of the eMMC bug. Welcome.to the club...
If your SGN is still under warranty and your binary counter is zero, rush to your nearest samsung service center. Tell them the phone booted after the update and never started.
If you arent in warranty, try repartitioning method explained by Forest in his detailed guide @ http://forum.xda-developers.com/showthread.php?t=1661590 check the 12th post.

Related

[Q] cp_modem.bin won't flash

I've seen a few others with this problem with no resolution.
First off... My drivers work, I can move files back and forth, and odin and pst both recognize the phone. I have tried multiple computers, and multiple usb ports, and multiple cables, 'F reset time' & 'Auto Reboot' checked and unchecked, battery in and battery out, SIM in and SIM out, even had Verizon replace the SIM. I have tried multiple ROMS (stock and custom, rooted and unrooted) and all exhibit the same behavior... and yes I am in download mode. I've factory reset both ways (recovery mode, and privacy settings), and tried to clear the cache in recovery mode to see if that helped.
When flashing a ROM everything goes fine until it gets to cp_modem.bin and then odin/pst hangs for a minute and then fails. I have tried to just flash the radio and i get the same failure. Other bins in ROMs flash fine.
Any ideas on how to fix???
Odin output:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EE4_Radio.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> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> cp_modem.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)
What Odin are you using to flash?
Why are you trying to flash a new radio? Where did you get the radio?
Have you tried downloading a new radio?
Have you tried a different phone.
You said you have new sim, different roms. All of which are of no importance, because your Radio does not have anything to do with these 2.
I've tried both Odin 1.85 and 1.3.
I started out trying to flash a new ROM, however, all the ROMS fail in the same place (while flashing cp_modem.bin). That's why i tried to just flash the radio. I got the radio from the XDA thread post for people who flashed to gingerbread but wanted to use the EE4 radio. I do not have another phone to try. The SIM was a red herring... and I agree it has no bearing on the problem, which is that I am unable to flash a radio to the phone as part of ROM or by itself.
How do I know other parts of the full ROM flashes are successful? Because after the failure I can boot the phone (obviously it wont connect to the cell network though without a valid radio though).
try using Odin3 v1.7. See if that is any different. trying to narrow down the errors here.
same result... It's definitely the phone, because if I flash stock ED2 (which fails on cp_modem.bin) then boot the phone, and take the EE4 update from verizon, it also fails. Not sure what on the phone could be causing this... There ought to be a way to just blast EVERYTHING off the phone and start from scratch with a fresh file system. It's like the thing needs to be reformatted.
After you put the phone in download mode, re-insert the battery, before flashing. See if that helps.
tried that (1st post)
This may seem silly, but have you tried to flash again without restarting the phone after you get the error?
j9murphy said:
if I flash stock ED2 (which fails on cp_modem.bin) then boot the phone, and take the EE4 update from verizon, it also fails.
Click to expand...
Click to collapse
Now THAT is interesting. Like the guy above me said, sometimes just running Odin again fixes it, however, if the OTA update fails too, the only thing that makes sense is a hardware failure.
Wait, how can you attempt to take the OTA without a radio installed?!
Sent from my Droid Charge running Humble 1.4
Have you tried flashing with Samsung PST lite? It is much more reliable than Odin.
Sent from my SCH-I510 using Tapatalk
From the previous replies...
I'm taking the update from verizon over wifi.
I have tried PST lite and get the same result.
I really don't think this is Odin/PST/USB/ROM/Battery etc.. problem. I think the phone is in a state that is preventing the modem from being flashed. either a hardware failure occurred, or the first flash which failed left the phone in a FUBAR state.
Unless there is a way to completely wipe/format the phone (or at least the area where the modem gets flashed) I think the phone is toast. Does such a process exist?
I know when flashing the Samsung Galaxy tab you do the Odin repartition feature. This clears everything and pretty much starts you over. I had to use this to flash my TMO Galaxy Tab using the European build so it could be rooted.
Not saying try it, but as far as wiping completely, take out your sdcard and try and Odin using the repartition feature.
Check out IMNUTS "HOW TO FIX YOUR PHONE" Post. Hopefully this will get you fixed.
tried re-partitioning to no avail. Verizon is replacing the phone, however I was hoping I could figure out what caused the phone to end up in this state in the first place to avoid it in the future!
Thanks to those that had suggestions. Hopefully, someone will figure it out in the future.

[Q] My Dead Infuse

I think my infuse finally died completely. For the past couple days I was getting SOD every 2 or 3 hours. Finally I decided to do the back to stock http://forum.xda-developers.com/showthread.php?t=1092021. I follow all of the instructions, but the program stopped working. Then I decided to try again, but this time only pixels came up. I removed the battery and tried again and all I'm getting is a white screen with pixels. Recovery mode does not work, nor does download mode. The phone also starts overheating if I plug it into a charger. Is there anything I can do?
Update: After trying to blindly navigate download mode and 20 tries of odin, it finally succeeded
Fireaxil said:
Update: After trying to blindly navigate download mode and 20 tries of odin, it finally succeeded
Click to expand...
Click to collapse
One more proof to prove that as long as you can see something on screen, it is not dead.
diablo009 said:
One more proof to prove that as long as you can see something on screen, it is not dead.
Click to expand...
Click to collapse
I had a similar problem but that same day i became a DL mode pro so i knew the combination by heart LOL.
I couldn't for the life of me do it now but thankfully it's good to know it's possible, glad you got yours working OP!
Plz Reply to get my infuse back
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
bindas.sanju said:
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1524081
Ok you have download mode so that is good...I dont use odin much I prefer the one click method, check these links out...
post one will give you stock...post two will give you cwm to install a custom rom if you want to..
If you want to go stock with root...try these links.
http://forum.xda-developers.com/showthread.php?t=1629079
I just did post two works great...
read all op directions and give us a status or if you need more if, just holler..
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
ndhanta said:
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
Click to expand...
Click to collapse
Ha...we are on the same thought process...I never use odin...qkster one clickers for me.... "why u no 1 click?"
Tru Universal Brotherhood makes our thoughts same Joi
Had same problem
I had kinda same problem and it always failed at facory.rfs. i tried everything but then i discovered the weirdest fix ever. i switched usb cable and worked perfectly so you should try new usb cable. good luck
ndhanta said:
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
Click to expand...
Click to collapse
^ This. Let us know results please.
bindas.sanju said:
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
Click to expand...
Click to collapse
I had the same thing happen to me last night when flashing the Entropy Kernel GB BL and all that jazz wtih odin. I unplugged cable after it froze up pulled battery attempted to return to dl mode but it went to the firmware update failed try kies recovery or whateves then I just tried odin again and it worked like a charm. I don't know what the deal was but froze up at factoryfs.rfs place and everything. So might just try that if this hasn't been resolved.
When its running rfs you should se a blue progress bar it takes about 5-8 mins to finish in my experience how long are you giving it
pink unicorn with swagga
This should work!
1. Download Blue CWM recovery on ur pc. http://www.mediafire.com/?2000k5y512spft4
2. Use odin and flash blue recovery (PDA)
3. May reboot into recovery or ull need todo 3 putton
4. Wipe/factory reset
5. Flash gingerbread rom on
6.go to advance>reboot recovery
7. Reflash that gingerbread rom on
8. Reboot!!

[Q] GT-S7500T stuck on CWM recovery

Yesterday something happened to my wife's phone - Galaxy Ace Plus GT-S7500T. The details are unclear, but she received notification of some sort of "software or firmware update" that was "not a normal update". After that it told her to reboot and since then the phone has been stuck on the CWM Recovery screen.
Things I have tried:
1. Cleared cache and Dalvik Cache.
2. Wipe data/factory reset
3. Update firmware using Odin 1.85 - gets stuck at "setup connection"
4. Update firmware using Odin 3.09 - gets stuck at "setup connection" - tried various USB cables including original Samsung cable
5. Update firmware using Kies - doesn't seem to do anything
6. Update firmware from CWM Recovery
a) GellyBread ROM
b) Elruki ROM
c) Elruki ROM with boot.img substituted from S7500TDVMJ1_S7500TTLPMJ1_TLP.zip
7. Update using Heimdall from Linux - fails to detect phone
Both the GellyBread and Elruki ROMs are meant for the 7500L but at this point I'm getting desperate.
I've wasted two evenings on this and I am just about ready to give up and buy her a new phone. Is there anything else I should try?
StevePER said:
Yesterday something happened to my wife's phone - Galaxy Ace Plus GT-S7500T. The details are unclear, but she received notification of some sort of "software or firmware update" that was "not a normal update". After that it told her to reboot and since then the phone has been stuck on the CWM Recovery screen.
Things I have tried:
1. Cleared cache and Dalvik Cache.
2. Wipe data/factory reset
3. Update firmware using Odin 1.85 - gets stuck at "setup connection"
4. Update firmware using Odin 3.09 - gets stuck at "setup connection" - tried various USB cables including original Samsung cable
5. Update firmware using Kies - doesn't seem to do anything
6. Update firmware from CWM Recovery
a) GellyBread ROM
b) Elruki ROM
c) Elruki ROM with boot.img substituted from S7500TDVMJ1_S7500TTLPMJ1_TLP.zip
7. Update using Heimdall from Linux - fails to detect phone
Both the GellyBread and Elruki ROMs are meant for the 7500L but at this point I'm getting desperate.
I've wasted two evenings on this and I am just about ready to give up and buy her a new phone. Is there anything else I should try?
Click to expand...
Click to collapse
if you dont have a firmware in your phone and it gets to download mode there is no reason to fail at updating with odin
to solve that try reinstalling your drivers but uninstall KIES!
otherwise try a different port or a different computer but it seems like odin is the only solution
the point from your post "since then the phone has been stuck on the CWM Recovery screen."
It means you have CWM installed device [ Correct me if I'm wrong here ] even I guess you've root.
at this stage even if you get any official firmware/software update you strictly don't have to update your device.
you've rooted device, unlocked system at this stage if you update your device with official firmware you'll surely face these kind of bricking issue.
Solution as given above reinstall kies to update drivers also try to check unroot thread from General section once,
Detailed guide & firmware download links are there...
wish you get back your device soon... ​
ShadowsDie said:
if you dont have a firmware in your phone and it gets to download mode there is no reason to fail at updating with odin
to solve that try reinstalling your drivers but uninstall KIES!
otherwise try a different port or a different computer but it seems like odin is the only solution
Click to expand...
Click to collapse
Just to be clear, the CWM Recovery screen means it is in download mode?
This morning I have uninstalled Kies and tried Odin again.
Then I uninstalled and reinstalled the USB drivers and tried Odin again. It now fails after a while rather than getting stuck.
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500TDVLK1_S7500TTLPLK1_S7500TDVLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I may be able to try on a different computer tonight.
j.posarekar70 said:
the point from your post "since then the phone has been stuck on the CWM Recovery screen."
It means you have CWM installed device [ Correct me if I'm wrong here ] even I guess you've root.
Click to expand...
Click to collapse
Correct, I rooted it when we first got it. I was hoping to but Cyanogenmod on it but only after buying it discovered it was a 7500T and not a 7500.
j.posarekar70 said:
at this stage even if you get any official firmware/software update you strictly don't have to update your device.
you've rooted device, unlocked system at this stage if you update your device with official firmware you'll surely face these kind of bricking issue.
Click to expand...
Click to collapse
Understood, I am not surprised about this. Just frustrating that I'm having so much trouble getting the phone back to life.
I will try unrooting it.
StevePER said:
Just to be clear, the CWM Recovery screen means it is in download mode?
This morning I have uninstalled Kies and tried Odin again.
Then I uninstalled and reinstalled the USB drivers and tried Odin again. It now fails after a while rather than getting stuck.
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500TDVLK1_S7500TTLPLK1_S7500TDVLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I may be able to try on a different computer tonight.
Click to expand...
Click to collapse
download mode is not recovery mode,
volume down+home+power
if you are not in download mode odin will not work
ShadowsDie said:
download mode is not recovery mode,
volume down+home+power
if you are not in download mode odin will not work
Click to expand...
Click to collapse
Thank you. I do feel a bit stupid not realising this earlier - but now it seems to be working.
I guess I was confused about what it was that CWM Recovery replaced, and I'm sure I tried Volume Down + Home + Power earlier but obviously didn't press it quite right.

Boot loop after trying to flash phone.

Hello,
I came here to look for help. I have a Verizon Samsung Galaxy s3. I rooted my phone and had CM10.2 on my phone.
I used casual to root phone/unlock boot loader and everything.
I decided I wanted to put CM11 on my phone. I downloaded everything from CM site for my phone. I made sure it was for my phone. I have TWRP recovery on the phone. put on debugging and everything.
I went into TWRP and started the process of putting CM11 on the phone. I made a nandroid back up in TWRP. I did a wipe data/factory reset.Once did all this, I went into install and installed zip file from my external sd-card. I believe it said failed, but i don't remember the exact thing that happened or the message I got. I know that doesn't help, but I am going to try and type everything I have done. Once that happened, I think i stupidly went to reboot and it said about super user rights needing to be fixed. I think i pushed fix. I know i probably did a big mistake there. The phone started to reboot.
When the phone is rebooting what happened was it would got to samsung galaxy logo and then CM logo. It would then immediately reboot. It just kept going through this cycle. So i tried to boot into recovery. It starts to attempt to boot in recovery. TWRP logo starts popping up. Boom it reboots again. So i can't get into recovery mode.
So i started to read around about my problem. I found articles saying about using odin to correct this boot loop (soft brick i think from what I read). I started to follow this article: http://forum.xda-developers.com/showthread.php?t=1840030
When I followed that article I got steps one through six done with odin saying pass. I start to do step 7. I actually tried to do step 7 twice. I got fails both times. I don't have the results form the first time. I downloaded the root66 tar file from somewhere else. I don't remember. When I got the failure, I pulled the root66 tar file i found here: http://forum.xda-developers.com/showthread.php?t=1984436 I used the main on on there. I go through and it fails: Here is the log from it.
<ID:0/005> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> root66_VZW_I535VRBMB1.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> Erase... <ID:0/005> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
I am completely stuck on what to do at this point. I am growing tired of trying stuff and I am completely stuck. I have tried to look around, but no luck.
Have you tried Odin flashing the VRBMF1 4.1.2 stock image? You would need to root and unlock your bootloader afterwards. This file formats /sdcard as well.
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
thunderisraw said:
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
Click to expand...
Click to collapse
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
SlimSnoopOS said:
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
Click to expand...
Click to collapse
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
thunderisraw said:
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
Click to expand...
Click to collapse
Great! You'll have CM11 installed in no time :thumbup:
Sent from my SCH-I535 using Tapatalk 4

Did a factory reset. Stuck on the initial setup phase.

I did a factory reset, clicked "Start", connected to a wi-fi network, agreed to the terms, etc... and then the phone got stuck in the "Checking network. Adding a few finishing touches. This may take a minute or two" phase. I waited hours, but it would always get stuck at that part, so I skipped connecting to a wi-fi network.
That helped, and got me further through the initial setup phase, but now, and no matter what I do, it'll just get to a point where it tells me "Not signed in. To use this phone you first have to sign in to an owner's Google account in use on this phone when it was last reset. Because you haven't done so, you have to set up the phone again".
The ****ed up part is that, during the setup stages that precede this message, I'm not asked to sign in to Google. I've tried doing a multitude of things but I cannot get past that.
I can't even go back through the recovery menu, now, as doing the power+volume+home button combination just starts the phone normally.
How did this happen and how do I fix it?
Bumping.
Bumping
Sounds like you need to do factory reset. I take it you've tried holding power+home+volume up while phone is off and keep it held down until recovery appears?
Alright, it just got more frustrating.
I tried doing the button combo to get to the recovery menu, but every time I'd try that it would just start the phone normally. Now, for some reason, it did get me to the recovery menu, so I did a Factory reset once again, and wiped the cache.
But the issue is STILL there. Same thing. It got stuck in "Checking Network", so I went with not having the wi-fi activated, I went through the menus, etc... I even set up a pin and a fingerprint, but right after the window where you select weather stuff and location stuff, I get the exact same error message: "Not signed in. To use this phone you first have to sign in to an owner's Google account in use on this phone when it was last reset. Because you haven't done so, you have to set up the phone again."
Why on earth is this happening??? Why would it even mention google accounts that were in use before the phone was reset IF I'VE WIPED ALL THE DATA??? Shouldn't it start fresh? Like, zero, nada?
When I purchased my phone the initial setup didn't have that message. What gives? I mean, I had rooted my phone before doing a factory reset, but that has nothing to do with this issue, right?
Can anyone help?
Please, can anyone help? What do I do? What solutions are there? I saw some dude with the same issue on a forum somewhere, and he said that he went to settings > apps > Google play services and enabled all permissions, but I can't even access the settings in the first place, since the phone's in the initial setup.
What can I do? Do I flash some sort of custom firmware into it or something? There's gotta be something... How on earth is this error not talked about more? Is it a rare thing? I never knew **** like this could happen. Just what is going on?
Please.
Anyone?
I tried flashing the S6's default firmware through Odin onto my S6 yesterday, but right after select the .md5 file and then click "Start" in Odin's interface, it'll run for a few seconds, but then "Failed" comes up at the top.
What specific firmware can fix this?
Just tried it again, and this time it took a bit longer before failing but it still failed. Here's the log in Odin:
<ID:0/004> 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/004> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the phone's download mode screen I can see something in red saying: [CM] SW REV. CHECK FAIL. DEVICE: 5, BINARY: 3
What does that mean?
I would stick to odin part
be very careful
put your phone right under the usb port when flashing since it can lose connection very easly
use odin 3 07
i think flashing rom is the only thing that could help you here
(or maybe custom recovery flash over odin then wipe and try other rom)
SOLVED
??
Crystalline3 said:
SOLVED
Click to expand...
Click to collapse
Please tell me how you did this. I am also having this issue with more than 1 device...please help.
hung in checking network
This just happened to me. I had to do a factory reset, and it just kept hanging on setup. Eventually, I just powered it down and turned it back on a few minutes later. And then the setup magically proceeded normally.

Categories

Resources