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.
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.
Hi you all guys, few days ago i purshaced an skyrocket sgh i727 and it was working perfect, then when i was using the
internet browser my phone ramdomly turn off, i just powered on but it never boot up so i decide to boot it up on clockwork
mode and restore to factory data after that the phone did no boot anymore neither in clockwork mode, when i try to power it
on it shows the samsung splash but stuck there, the phone can be put on download mode which is a good signal however when i
try to install a stock rom from odin this does no start, it keep saying initializing step, i though my battery was
discharged and i tried the battery in a friend's phone but the battery was full charged, so i discarded that was a battery
issue, i installed the lastest kies driver, i got differents odin version, downloaded few times differents stock rom version and re tried to intalled; but odin keep sticking on initializing step, tried differents batteries (full charged), differents usb cables, differents computers, but its seems the phone is completely bricked i tried almost everything also i found that kies can make an emergency restore but when i try to do it, kies request me the error code to proceed, but i dont have such code since my phone never give me an error on installing, it just doest start the restore with odin, when i plug my phone its recognized from odin and shows as added, can you suggest me something? im tired of trying all what i described above and the phone does no have warranty since i purshaced it on ebay and the seller doesnt no accepted to be responsible since the phone worked when he sold it, i cant find any place to purshace a main board but before to purshace one i think there will be posibility to fix it since its still easy to power it on download mode without the JTAG, i cant get it on clockwork mode anymore http://forum.xda-developers.com/images/smilies/crying.gif
First off, I can't really make complete heads or tails of your problem. Please use sentences and paragraphs.
Second, is Odin recognizing your phone when you plug it in? Read the ODIN sticky.
Third, how long is your phone "stuck" on the Sammy splash for? You're definitely booting into CWM recovery and not factory recovery, right?
Honestly, if your phone turns on, it's not hard-bricked and it can be saved. There are lots of stickies here that walk you through how to root/unroot, restore to stock, use ODIN, etc. Read through those and that'll give you your best shot at finding an answer.
response
Hi im sorry if i writed it with sentences and paragraphs, well actually odin does recognized the phone and shows as added, but when i start the restore the phone keep in download mode and odin just stuck in the step that says initializing.
I used another battery, another usb cable and other computer but odin keep sticking in that step.
I tried downloading differents odin versions and differents stock rom version from differents sites but i can see its not a corrupt download.
the phone had CWM but in the time i made a factory reset from the CWM the phone did no boot anymore on CWM neither the OS because it stuck on the Samsung splash, this splash stuck permanently maybe hours if i dont remove the battery.
I think im booting on CWM im not sure because (it does no appear the menu to install zips make factory reset, clear cache partition etc)
Kies recognize my phone also but unable me to make an emergency restore until i put the error code in the box that pop up (i dont have such error code since my phone does no give me any error the process just doesnt start)
i tried killing kies in the task manager because i read sometimes kies intefere with oding while restoring, i can make put the phone in download mode as i said but im not able to make the restore because ODIN Stuck on INITIALIZING MODE.
I read some forums and post before i post but i havent found nobody with the same issue i just found this http://forum.xda-developers.com/showthread.php?t=1240333 but this didnt work for me
jakeharriss said:
I think im booting on CWM im not sure
Click to expand...
Click to collapse
In fairness, at least you're not out flashing ROMs and saying this.
How are you trying to boot into recovery? Are you holding both volume buttons and the power button down, and keeping them down until the Sammy splash comes up? Or are you just using the power button? If you're just pressing power, you're trying to boot a phone that has no ROM, and you'll have the same result every time.
Second, are you positive you're using the right version of Odin? v1.85?
Third, when you plug your phone into the computer and Odin, does the screen look like the screenshot in the OP of this thread?
http://forum.xda-developers.com/showthread.php?t=1773659
I'll be really honest, this screams of user error, and that's really the only explanation I can think of--especially because the phone can apparently still be forced into download mode. Maybe someone more experienced has seen this happen before and can help more than I can, but from the panicked style of posting and your asking questions about whether it's booting into recovery or not, I have to assume that it's user error. We just have to figure out what that error was.
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
jakeharriss said:
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
Click to expand...
Click to collapse
read this, its a sticky for newbs, follow it to the t, read the the whole post 3x b4 you proceed http://forum.xda-developers.com/showthread.php?t=1652398, if that doesnt work, either user error or hardware problem with nand
Make sure in Odin Only the reset time and reboot boxes are checked. Don't re partition.
Hmm... Well I occasionally have your initial problem, where my phone randomly turns off. Here, it doesnt boot right away, but I have to remove all power sources (battery, cable), put the battery back in, then it turns on fine, no questions asked.
What ROM were you using at the time? My phone started doing this after I installed the Liquid Beta 2Jellybean Rom. If you were using that at the time, it may have just been a ROM issue. Hope I helped...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Brick LOGS PIT
Hi, well actually i was running the stock rom 2.3.5 GINGERBREAD, that was the rom that came with my phone, i tried the step to enter my skyrocket in recovery mode but im not able to do it, the odin keep sticking on initializing i have tried the steps you gave me, is there a way i can get an error code to try the emergency restore from kies? because i dont know where to get an error code,
i tried to re flash the CWM but odin also stick on initializing
<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..
and this is the log when i disconnect the phone from my computer
\<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>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i have reading a post about PIT
PIT – the PIT file refers as ‘Partition Information Table’. This is only useful for fixing bricked devices if somehow something changed with the partition table layout of the phone’s system memory. But in normal flashing, you should not use this file, or you may screw up your phone if handed carelessly.
does anyone have any idea how can i remap my partition in my phone or if it nessesary?
also here i leave the log when i try to make a restore with odin to an stock rom
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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.. (in this step my phone stuck while trying to install and never advance)
when i unplug this is what appear
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition. (It keep saying i dont have a PIT partition)
<OSM> All threads completed. (succeed 0 / failed 1)
do you all guys have any idea what is going wrong? i tried to turn in restore mode following this steps
ENTERING IN TO RECOVERY MODE IS THE SAME METHOD FOR BOTH STOCK AND A CUSTOM RECOVERY (CWM)
Now turn off your phone, unplugged(might work plugged in)
Press and keep both volume keys down
Then press the power button while still holding down the volume keys
When you feel the phone vibrate or see a logo on the screen, release the power button but not the volume keys.
When screen goes black release the volume keys.
Wait a few seconds to boot in to recovery
You are now in recovery mode
But when i release the power but and keep holding the volume button my screen keep stuck in the samsung splash even when i release the volume butto + the power button after the splash comes up
I appreciate your time and im sorry if i dont write in paragraph senteces etc i just tried to explain my issue as it was posible for me thanks
i think your problem was this "odin v3.04 also the odin rom installer", never heard of the odin rom installer used for our phones, you could of fracked up the partitions, but i dont know the fix for that, if there is even a way to fix it
edit: nvm, i read that it was a prob b4 you tried that, then its a bad nand, there might be a way to push a recovery back onto the phone using adb, just cant find the post on how
here it is, it will get you started, you need to learn how to use adb http://forum.xda-developers.com/showpost.php?p=31172875&postcount=19
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
jakeharriss said:
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
Click to expand...
Click to collapse
The thing you are taking about is an Odin one click.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
jakeharriss said:
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
Click to expand...
Click to collapse
We don't have a pit file for the skyrocket. At least as far as i know. You should be able to flash the stock firmware if you can get into dl mode. Use Odin 1.85 and follow vincoms guide
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes so do i think the same, however for any extrange reason everytime i put my phone in download mode my phone stick in this step
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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.. (in this step my phone stuck while trying to install and never advance)
i tried using differents odin version, differents stock roms, different usb cables, differents usb ports and computers, also reinstalled the right drivers for my phone and i verified it in the device manager from my computer, so i can say the issue is in the phone
i tried to reinstall the CWM but it also keep on the initializing step so if this dont pass there is no way to get in CWM and neither to the factory recovery mode, as i said everytime i try to get in factory recovery mode i cant due my phone stuck in the samsung splash and never goes black as it should to say that now is on factory recovery mode.
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I did it but keep sticking in download mode with the odin in initializing step even my kies download the emergency restore firmware and it stuck while trying to install is there a way a can make a dual boot without the cwm or factory recovery working?
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
UBetchYa said:
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
Click to expand...
Click to collapse
Hi well i tried the whole method i could but i realized that would be quicker buying a new motherboard for the phone i got it on 50 usd on ebay it was a look that a guy tried to change his broken screen but he couldnt and decided to put his phone on auction i won and i repaired my phone however i send the mainboard to a friend of mine and he said the he couldnt repair it, i talked with a guy that said he could create the partition map again but i couldnt understand him maybe you can talk to him but he explained me that what killed my phone was to put a leaked firmware and make a wiping on the partition from the restore mode http://forum.xda-developers.com/member.php?u=3597010 this is the guy just send him a message wish you good luck with that
Watching TV last night I noticed out of the corner of my eye my Galaxy Note 10.1 light up and display the logo boot screen. I thought it must be updating or something but an hour later it was still showing the same logo screen. I plugged it in and left it another hour, still the same screen. I then tried to reset it holding the power button down. It turned off and came back on and stopped on the logo screen again. I've tried restarting in safe mode but it never gets past the logo screen. I tried kies with no success. Today I downloaded Odin, the latest firmware and usb drivers. The odin firmware loading screen is the only screen I can get to other than the "off and charging" battery display and of course the logo screen. So I thought "what the heck" and reloaded the firmware through Odin. Odin reported a successful load and the tablet restarted...... and its still stuck on the logo screen.
So what I'm asking of you guys who know much more than I do is. Am I right in now thinking it must be a hardware problem? I've reloaded the software fresh through Odin so it must be hardware right. What can I do next to try and fix it or is it now an expensive paper weight. I was put off buying another Samsung before this happened as they haven't updated this tablet since Android 4.1.2 but the fact its just bricked itself means I'm definitely no longer considering the Galaxy s6 when my contract is up.
Any advice greatly appreciated. Thanks.
If it helps I used Odin v3.09, firmware BTU-N8010XXUCMG1-20131023133812.
<ID:0/023> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUCMG1_N8010OXXCMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/023> Odin v.3 engine (ID:23)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> SingleDownload.
<ID:0/023> tz.img
<ID:0/023> NAND Write Start!!
<ID:0/023> sboot.bin
<ID:0/023> system.img
<ID:0/023> boot.img
<ID:0/023> recovery.img
<ID:0/023> cache.img
<ID:0/023> hidden.img
<ID:0/023> RQT_CLOSE !!
<ID:0/023> RES OK !!
<ID:0/023> Removed!!
<ID:0/023> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Usually I can easily access the boot menu and start in safe mode or or do a wipe to factory reset if that doesn't fix it but it won't go to that menu. I've had 6 android devices and had my fair share of freezing, crashes and dodgy app installs. I've replaced screens and batteries. But the programming and software behind it all. I don't know about that and that is where I think the problem is.
From further reading of similar problem with the Galaxy s3 phone being "soft bricked" I can only guess that either some section of the memory that should be R/W is now R/O and the Galaxy can't write to it when its booting up so it gets stuck. Or, as happened with my old Sony Xperia X10, something physical is broken inside and when the Galaxy gets to that part of the boot the hardware doesn't respond and so it gets stuck waiting for a response. I've had that happen with a computer before and as soon as pulled the offending card it booted up.
How ever its died so suddenly I'm not sure it is that. My Sony phone would turn of once a week and then it got worse, to once a day, to several times a day and then finally would no longer turn on even with a new battery. But that happened over months. Same as my Nexus 5 battery problem slowly got worse until I replaced the battery. The Galaxy Note just decided to restart itself last Friday and has been stuck ever since. Zero problems or glitches before it happened.
I need someone with a lot more knowledge than me to look through the log results from Odin and say "Yep, its dead, buy a new one" or give me instructions like "You need to download file x and install it in y with box 1 and 2 checked but NEVER box 3 and then reinstall the OS at high tide on the 3rd tuesday of the month" that kind of thing.
Anyone?
Did you ever solve this problem? I have had the same issue and tried the same download with Odin.
You may be out of luck
Jamesian said:
Watching TV last night I noticed out of the corner of my eye my Galaxy Note 10.1 light up and display the logo boot screen. I thought it must be updating or something but an hour later it was still showing the same logo screen. I plugged it in and left it another hour, still the same screen. I then tried to reset it holding the power button down. It turned off and came back on and stopped on the logo screen again. I've tried restarting in safe mode but it never gets past the logo screen. I tried kies with no success. Today I downloaded Odin, the latest firmware and usb drivers. The odin firmware loading screen is the only screen I can get to other than the "off and charging" battery display and of course the logo screen. So I thought "what the heck" and reloaded the firmware through Odin. Odin reported a successful load and the tablet restarted...... and its still stuck on the logo screen.
So what I'm asking of you guys who know much more than I do is. Am I right in now thinking it must be a hardware problem? I've reloaded the software fresh through Odin so it must be hardware right. What can I do next to try and fix it or is it now an expensive paper weight. I was put off buying another Samsung before this happened as they haven't updated this tablet since Android 4.1.2 but the fact its just bricked itself means I'm definitely no longer considering the Galaxy s6 when my contract is up.
Any advice greatly appreciated. Thanks.
Click to expand...
Click to collapse
It's either the partition table is corrupt or the efs flash memory is corrupt.
If the partition table is corrupt, tell me what model no you have and storage space and I may be able to send you a pit file to restore.
If it's the efs, you may be out of luck. I have an efs backup on my note 10.1 which had the same problem as you and restoring my efs backup worked. I am scared to share my backuo with you since I may get caught or worse, hacked.
Good luck.
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.