Related
Hey all,
I've been flashing ROMs since the old Windows Mobile days and recently have run into a problem that has me stumped and I haven't been able to fix it. I beg you experts for help, I'm not sure what else to do.
My wife had some complaints that her Infuse was acting slow so I thought a new flash of something might help. I attempted to flash CatyRom but was stuck at the rainbow loading animation for over an hour. At this point I was getting nervous so I figured I would go back to stock. I used the link http://forum.xda-developers.com/showthread.php?t=1331381 for Heimdall One-Click Back to Stock. After doing that the phone just froze on the Samsun logo and after retrying it twice and restarting I was making no progress. I've tried some other back to stock threads and the latest was I loaded the ultimate unbrick from http://forum.xda-developers.com/showthread.php?t=1367099 and now the phone is stuck in a red Clockwork Recovery v2.5.1.3 - Voodoo Lagfix. When I try rebooting it sits at the Samsung logo, when I try to flash the one thing on the phone(CatyRom) it says:
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount /dev/block/stl9(file exists)
Error mounting SYSTEM:!
At this point I'm not sure what else to do/try. I can get into this version of Clockwork which I suppose is kind of good, but all that's on the phone is CatyRom and that won't install. If anyone can help I'd truly appreciate it.
Try flashing the community gingerbread kernel with Odin to reset your recovery and do a complete wipe and fix permissions...that happened to me once and that fixed it for me....after that you should be able to flash caty
Sent from my SAMSUNG-SGH-I997 using xda premium
For some unknown reason Odin isn't seeing the phone. Heimdall detects it in Download Mode fine, but it never shows up in Odin.
Also, when I tried one of the GTG back to stock Heimdall repackages everything goes fine and then at the end when it says Ending session.. it then says:
ERROR: Failed to send end session packet! Heimdall crashed!
The phone just sits in download mode, if I pull the battery and restart it's like nothing was done.
I'm not too experienced on hemidal but I believe there is a way to flash that same kernel I mentioned thru hemidal...but I don't use it so I would ask Dani897 he knows hemidal very well...hope that helps..
Sent from my SAMSUNG-SGH-I997 using xda premium
On heimdal or however you spell it click flash boot loaders ive used it many times it should work
Sent from my SGH-I997 using XDA App
Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.
Truckerglenn said:
Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.
Click to expand...
Click to collapse
What he said. Uninstall the driver in device manager. For me, it shows up under a main section called libusb.
Did you use the straight up repackage link or the one with the community v8 kernel in it? Since you have red CWM recovery, it would seem that you either used the community v8 which has voodoo lagfix enabled by default or you had a bad flash with the straight up repackage. I think I have a heimdall package that has all the gtg unbrick files in it. I'll post it up here if I find it.
EDIT: I threw a heimdall package together based on gtg's unbrick and just flashed it to my phone as a test. Yes, it worked just fine.
heimdall package back to uckd5 stock using gtg's unbrick files - http://www.multiupload.com/QL5BCRG1CI
the exact same thing happened to me... try different usb ports ..try different usb cables.. i didnt believe my usb cable was bad....it was. i used gtgs unbrick once i got odin to see the phone!!! im back to normal!!
Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?
Try a fresh download of the file your flashing in Odin and restart Odin before hand
Sent from my SAMSUNG-SGH-I997 using xda premium
Griffon23 said:
Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?
Click to expand...
Click to collapse
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997
jayson94538 said:
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997
Click to expand...
Click to collapse
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.
Griffon23 said:
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.
Click to expand...
Click to collapse
Some people got it to work by switching to a different usb chord, or trying on a different computer.
Sent from my SGH-I997
Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
If it flashes, boot into recovery, it should be Red. Scroll down and disable Voodoo lagfix or enable it if it's disabled.
Rebooting should put you in a loop after the kernel fixes the partitions. Good.
If you disabled lagfix, boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
If you enabled it, boot to recovery, but this time disable it. Rebooting should put you in a loop after the kernel fixes the partitions. Good. Boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
The loop should only occur if the rom is messed up.
Booting after flashing shouldn't take more the 5-10 minutes. At least from what I've seen on my phone.
Truckerglenn said:
Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
Click to expand...
Click to collapse
Thanks, I'll give this a shot, but I'm not finding anything called Enthroy's kernal, I've tried searching for it but no luck, I may be missing it.
Go into the infuse super thread and look under kernels for the download. If nothung works, contact me because my phone (im sending it from) was rezurected with mobile videos jtag repair. Turns out my phone wont connect to computers even with a new usb slot installed. Anyway its forty bucks but its well worth it . If you still have warranty go ahead and use that up if you do not care about the info on your phone.
dude..try a different usb!!!!!! i kept getting the same errors.. it would get 1/4 way throught the process and get stuck... i used my sons usb cable from his HTC inspire and it worked perfectly!!!! USB CABLE !!! TRY IT!!!
i used gtgs very carefully ..step by step !!!
once i did it with a new usb, it downloaded in 3 minutes!!!!
good luck!!!!
oh and happy new year everyone!!!
did you get it working?? just curious
mejori said:
did you get it working?? just curious
Click to expand...
Click to collapse
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!
Griffon23 said:
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!
Click to expand...
Click to collapse
That's the first thing I do after I Odin back to stock. Do a hard reset to erase what ever was left behind, or else you will keep having problems. GL
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave
Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje
JJEgan said:
Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje
Click to expand...
Click to collapse
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.
davaze said:
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.
Click to expand...
Click to collapse
perhaps a different version of ODIN? just spit balling here
EDIT: oops jje already said that, wipe cache, dalvik, factory reset??
davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse
JJEgan said:
davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse
Hi thanks for your comments!
Is there anyway to flash without modem.bin? What does modem.bin include?
Rooting the device works with no problem, installed the clockwork recovery and SU succesfully.
When trying the CSC changer it gives me no options.
The device seems to work normal but i must say that i never cleared any cache before starting to flash. The reason is that in some tutorials it is not mentioned unitl after the flashing completed. Also i'm a little affraid now to try it before flashing because i don't know what will happen if it fails again and i cleared cache etc. before.
I'm still hoping someone experienced the same issue and found a reason or solution to this. Untill now i'll do nothing as it seems to work inlcuding the google apps. Not sure if the unknown CSC will cause any issues in the future with specific functions though.
Will keep following this topic to hopefully find someone with similar experience.
Thanks to all that leave some help or comments!
Click to expand...
Click to collapse
Modem.bin is the radio you use to make and receive calls, use 3g internetsms and mms with. You should be able to flash a separate modem.bin file either through cwm or through ODIN...
I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.
demandarin said:
I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.
Click to expand...
Click to collapse
ODIN 3.07 didn't work for me, switched to 3.04 and that worked, not sure the version you have
I have rooted, unrooted and flashed a bit on mine with no issues, you seem to have attention to detail, but just make sure it's the right firmware for your model some folks have flashed regular galaxy tab ROMs with tragic results
EDIT: does KIES recognize it?
Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.
demandarin said:
Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.
Click to expand...
Click to collapse
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?
jaydubbbbs said:
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?
Click to expand...
Click to collapse
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.
demandarin said:
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.
Click to expand...
Click to collapse
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing
jaydubbbbs said:
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing
Click to expand...
Click to collapse
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.
demandarin said:
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.
Click to expand...
Click to collapse
like I said, it takes me like three tires to get the timing on the recovery mode. wish I knew more, good luck!
since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.
demandarin said:
since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.
Click to expand...
Click to collapse
No idea about the NAND options, ODIN 3.07 didn't work for me, I have 3.04 and haven't used it since I updated to 4.1.2. That sucks that the peel update borked your %ยข#! . Especially because it's a stock app! I updated peel about a week ago with no issue. Not being able to get into recovery is probably a bad sign. I keep hoping someone smarter than I would chime in. I hope Samsung takes care of you
thank you for the suggestion to use another version of ODIN....i have been screwing with this for a day and half thinking that every version of stock rom that i tried was broken in some way....turned that ODIN v3.07 does not work so well...found ODIN v3.04 and worked perfectly.
Recovery mode is easy, from power off hold down volume up and power. Hold both buttons in until you see the samsung logo, release power but keep holding volume up until recovery appears... Works everytime...
Same problem - half solved
davaze said:
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave
Click to expand...
Click to collapse
Hi Dave and all
I am i EXACTLY the same situation - Just bought n8000 in china with chinese firmware and wanted to change for European. I encounterted the same problem.
After formum research and many tests of softwares/ usb ports/ odin versions. I got to a point when after crashing during instalation (like in davids situation) i couldnt turn on the device anymore (black screen saying that i should do recovery via kies)
I installed CWM via Odin and it helped.
The tablet started again with european system and applications and seemd to work well.
UNFORTUNATELY: The S note is crashing before it's even loaded and while using tablet i experiece lags for ex when typing address in internet app.
I made a factory reset and cleaned cache - still nothing.
Please help if you have any ideas.
David: How did you managed to solve your problem? Did you managed to finish the update withou a crash?
Best regards
Filip
Yesterday my phone started boot looping and it eventually got to the point where it wouldn't load past the Samsung screen. I did a bit of googling and followed the instructions here http://forum.xda-developers.com/show....php?t=1591601 to a T. Everything worked on Odin, but now I'm stuck at the firmware upgrade encountered an issue. I tried to do it again and it all works but I get a NAND WRITE: ptn_erase fail on my device over and over, but Odin says it passed. I feel like I've tried everything. Any suggestions would be wonderful. Thanks!
After re-reading your post, I'm not entirely sure that I can help, but here goes ..
Please read my ENTIRE post before doing anything, please!
What's the problem? Well, I'm not familiar with the error you provided, so I'm not sure.
What needs to be done? Well, We're going to fix it (hopefully)
Go to THIS thread, within this thread is a download link for a file called "UVLB7.tar.md5", download it and follow the instructions in the thread to flash it. You now have a pre July 16th image of GB.. You can do two things from here
1) Kies will (or least should) recognize the firmware on your phone and push you to the latest Official ICS Stock ROM.
OR
2) You can root the phone, Follow THIS thread to root your phone. After you follow the directions in this thread, you should be fully rooted and ready to flash to your hearts desire.
NOTE!!!
YOU NEED TO FOLLOW THE INSTRUCTIONS IN BOTH OF THE THREADS, IT IS POSSIBLE FOR YOU TO HARD BRICK YOU PHONE! IF THAT, OR ANYTHING ELSE HAPPENS, ME NOR THE CREATORS OF THOSE THREADS ARE RESPONSIBLE, YOU'RE CHOOSING TO FOLLOW THEM! BE CAREFUL!!
Sorry for that, lol, just had to cover my grounds
FroBreadCreamJellyPie said:
After re-reading your post, I'm not entirely sure that I can help, but here goes ..
Please read my ENTIRE post before doing anything, please!
What's the problem? Well, I'm not familiar with the error you provided, so I'm not sure.
What needs to be done? Well, We're going to fix it (hopefully)
Go to THIS thread, within this thread is a download link for a file called "UVLB7.tar.md5", download it and follow the instructions in the thread to flash it. You now have a pre July 16th image of GB.. You can do two things from here
1) Kies will (or least should) recognize the firmware on your phone and push you to the latest Official ICS Stock ROM.
OR
2) You can root the phone, Follow THIS thread to root your phone. After you follow the directions in this thread, you should be fully rooted and ready to flash to your hearts desire.
NOTE!!!
YOU NEED TO FOLLOW THE INSTRUCTIONS IN BOTH OF THE THREADS, IT IS POSSIBLE FOR YOU TO HARD BRICK YOU PHONE! IF THAT, OR ANYTHING ELSE HAPPENS, ME NOR THE CREATORS OF THOSE THREADS ARE RESPONSIBLE, YOU'RE CHOOSING TO FOLLOW THEM! BE CAREFUL!!
Sorry for that, lol, just had to cover my grounds
Click to expand...
Click to collapse
Ok, so I downloaded the link and tried to flash it. Goes through the same thing, Odin says it worked, but I get the nand_write: ptn erase fail. I forgot to mention that it won't connect to Kies.
nm192790 said:
Ok, so I downloaded the link and tried to flash it. Goes through the same thing, Odin says it worked, but I get the nand_write: ptn erase fail. I forgot to mention that it won't connect to Kies.
Click to expand...
Click to collapse
This is odd, when flashing through ODIN what exactly are your steps?
nm192790 said:
Ok, so I downloaded the link and tried to flash it. Goes through the same thing, Odin says it worked, but I get the nand_write: ptn erase fail. I forgot to mention that it won't connect to Kies.
Click to expand...
Click to collapse
I really can't help, and for that I apologize, but I'm assuming you've rooted or attempted to root, which would explain why you can't connect to kies.
FroBreadCreamJellyPie said:
This is odd, when flashing through ODIN what exactly are your steps?
Click to expand...
Click to collapse
I connect the phone, check PDA and add the file, make sure all but auto reboot is unchecked and push start. No fails. When it gets to "<ID:0/004> system.img.ext4" this step that's when the erase fail shows up on my device.
njstein said:
I really can't help, and for that I apologize, but I'm assuming you've rooted or attempted to root, which would explain why you can't connect to kies.
Click to expand...
Click to collapse
The first step of my how to would fix that, problem is, ODIN is failing to write anything, kinda weird ..
---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------
nm192790 said:
I connect the phone, check PDA and add the file, make sure all but auto reboot is unchecked and push start. No fails. When it gets to "<ID:0/004> system.img.ext4" this step that's when the erase fail shows up on my device.
Click to expand...
Click to collapse
What ODIN are you using ? And the error is your device not ODIN?
FroBreadCreamJellyPie said:
The first step of my how to would fix that, problem is, ODIN is failing to write anything, kinda weird ..
---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------
What ODIN are you using ? And the error is your device not ODIN?
Click to expand...
Click to collapse
Very strange that ODIN isn't writing anything here. Way beyond me!!
FroBreadCreamJellyPie said:
The first step of my how to would fix that, problem is, ODIN is failing to write anything, kinda weird ..
---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------
What ODIN are you using ? And the error is your device not ODIN?
Click to expand...
Click to collapse
I'm using v3.07 and yes the error shows up on my device, multiple times.
nm192790 said:
I'm using v3.07 and yes the error shows up on my device, multiple times.
Click to expand...
Click to collapse
I apologize, I misunderstood, I thought the error was showing on ODIN itself..
Now, I have one last trick up my sleeve, It could be because of the version you're using, I use ODIN 1.85 .. Download that ODIN and try my tut again, I'm hoping this will work .. lol
FroBreadCreamJellyPie said:
I apologize, I misunderstood, I thought the error was showing on ODIN itself..
Now, I have one last trick up my sleeve, It could be because of the version you're using, I use ODIN 1.85 .. Download that ODIN and try my tut again, I'm hoping this will work .. lol
Click to expand...
Click to collapse
Nothing. Failed real quick, lol.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
nm192790 said:
Nothing. Failed real quick, lol.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You sir have a very interesting issue on your hands, what were you doing before hand that caused the phone to start doing this ?
FroBreadCreamJellyPie said:
You sir have a very interesting issue on your hands, what were you doing before hand that caused the phone to start doing this ?
Click to expand...
Click to collapse
Nothing that I could think of. I updated to ICS via Kies about a month ago and it all worked fine. I was at work yesterday when it just started turning off and on, over and over. I followed those instructions to get back to stock using Odin v1.85 and it failed, so I used the 3.07 and got this erase fail. I'm completely stumped. I never rooted it or did anything to it really.
nm192790 said:
Nothing that I could think of. I updated to ICS via Kies about a month ago and it all worked fine. I was at work yesterday when it just started turning off and on, over and over. I followed those instructions to get back to stock using Odin v1.85 and it failed, so I used the 3.07 and got this erase fail. I'm completely stumped. I never rooted it or did anything to it really.
Click to expand...
Click to collapse
JUST IN CASE! You are putting your phone in download mode right? (Sorry, but I gotta ask) .. And when you are what does it say just curious?
FroBreadCreamJellyPie said:
JUST IN CASE! You are putting your phone in download mode right? (Sorry, but I gotta ask) .. And when you are what does it say just curious?
Click to expand...
Click to collapse
I've wondered this myself. I can't do anything with the phone. Holding volume buttons and power down bring me to the same firmware issue screen. Turning it on and plugging it in I still get this screen. I can't find anything that allows me to leave the Odin mode.
nm192790 said:
I've wondered this myself. I can't do anything with the phone. Holding volume buttons and power down bring me to the same firmware issue screen. Turning it on and plugging it in I still get this screen. I can't find anything that allows me to leave the Odin mode.
Click to expand...
Click to collapse
You should take the battery out of the phone then plug it into the computer, then replace the battery and hold the power button, after the vibration immediately hold both volume buttons, you then should be in download mode, if that doesn't work then something is seriously wrong ..
FroBreadCreamJellyPie said:
You should take the battery out of the phone then plug it into the computer, then replace the battery and hold the power button, after the vibration immediately hold both volume buttons, you then should be in download mode, if that doesn't work then something is seriously wrong ..
Click to expand...
Click to collapse
I've tried that too. As soon as I plug the phone in it starts vibrating and I can get to the warning screen about a custom OS and whatnot. Pressing volume up just brings me back to the same screen.
nm192790 said:
I've tried that too. As soon as I plug the phone in it starts vibrating and I can get to the warning screen about a custom OS and whatnot. Pressing volume up just brings me back to the same screen.
Click to expand...
Click to collapse
Then something is wrong deep down inside your phone, lol, this is now out of my league. Hopefully someone will be able to get to you soon that can help. Good luck .
FroBreadCreamJellyPie said:
Then something is wrong deep down inside your phone, lol, this is now out of my league. Hopefully someone will be able to get to you soon that can help. Good luck .
Click to expand...
Click to collapse
I figured as much. Thanks for all of your help though!
nm192790 said:
I figured as much. Thanks for all of your help though!
Click to expand...
Click to collapse
No problem
Hi guys,
My galaxy note 10.1(2013) is was on <Stock> Android Kitkat .
Out of curiosity of rooting, i flashed CF Auto Root using odin.
The device restarted, and features seemed fine with new Root App too.
In few minutes however, device rebooted.. and went into a bootloop. :crying:
which still is, as long as device is on - has battery.
SUMMARY:
1. Recovery mode is not accessible now - device goes into recovery mode and restarts.
2. Normal boot is going into bootloop.
3. Download mode - HOWEVER is available !
PROBLEM :
-on trying to reflash stock rom/any Tar File for my device using odin,
odin fails with message :
NAND WRITE START
FAIL
----------------------------------------------------------------------------------------------------------------
Please help solve.
I do not want my beloved<soft bricked> device to die a sudden death .
Will appreciate you guys putting life back in it !
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
will get back with update tomorrow.
glorifiedg said:
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
Click to expand...
Click to collapse
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Anand.prashar said:
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Click to expand...
Click to collapse
'Cause you probably didn't try the 4.0.4. I have nand write fail with the most recent versions also :S
Suggestion to no avail
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Anand.prashar said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Click to expand...
Click to collapse
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
[/COLOR]
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.[/QUOTE
same problem here but i thing we need to clear all those built up cache in order to proceed right? but no boot recovery just the Odin downloading image. now if we can find a way to clear all those cache i'm sure'll work but don't know how to clear it from the "downloading do not turn off target" unless somebody figure this out.
Click to expand...
Click to collapse
* Serious issue awaiting resolution *
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
Click to expand...
Click to collapse
Sorry for delay, work kept busy.
You have the N8000. Correct?
-Yes
If you're working on a desktop ?
-No
- On laptop :
same laptop i used to root my tab using CF-Auto Root.
and have flashed ones in past on the older rom for this tab.
- Port : used USB 2.0
TWRP recovery ?
- Getting same error on odin as stock Rom.
<< I am attaching 3 snapshots >>
- Odin desktop Software in work
- Download mode of device
- Texts on download mode screen of device
<i believe it says custom, coz i had already 'seemingly' rooted stock rom>
------------------------------------------------------------------------------------------------------------
It would be worthwhile to mention the last flashing trial.
- it was upgraded to Kitkat released for this device
2 months ago : using Odin [as i had rooted the previous Default firmware too]
- having gotten bored with non-SU controls,
i flashed CF Auto Root
that would give me "SuperSU app" control without changing existing Firmware.
- Device rebooted after flashing (hopefully correct steps, i think)
"Super SU" app was available for me.
- Note : Upon opening app, i was prompted with a message
"KNOX has been detected on this device... would i like to remove/disable ?"
- I hit Yes.
Got a popup soon, that KNOX was successfully removed.
- and then, it went FINE for about an hour.
AND THEN CAME THE BOOTLOOP all of a sudden.
------------------------------------------------------------------------------------------------------------
Summary:
I am not able to figure out what could have caused this...
flashing/knox/ anything else ?
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
Did you already tried to flash the 4.4 leaked version with the 5 files over odin?
And also the pit file provided there.
That solved my problem a couple of months ago.
ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
hey,
what do you mean by "useless" ?
please explain clearly.
i just got one of these the other day,gt-n8013, maybe it's possible to whip up a fix.
a thought i have is that a boned odin install may take on the same behaviour
as a certain kernel function where a temporary kernel to be booted to
may be being stored into ram, meaning when you reboot to odin mode
you basically pick up where you left off. poweroff your tab and then plug in
your charger like normal. if your battery image shows up then, your kernel is intact or mostly so.
if that's the case maybe running your battery dead or disconnecting it will
work like pulling the cmos battery in a pc to correct a bad bios configuration.
meaning after the power is finally and truly off then ram will clear completely and when
you recharge and reboot back to odin you will be at baseline again.
the above approach has worked with some lower end tabs i've owned
including the galaxy tab 2 7.0
m
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
dough30i said:
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
Click to expand...
Click to collapse
okay, try for odin now, but try recovery first.
@dough30i
going back through this thread if you did the same thing with cf-root-crap you may have
damaged you bootloader. which is very not good. if you've gotten recovery up let me know.
you will need to get adb running and just for verification i need your model i.d.
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
dough30i said:
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
Click to expand...
Click to collapse
okay, are you trying to write a full firmware image or just a recovery or boot tar.md5?
or is it flat out no go?
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
dough30i said:
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
Click to expand...
Click to collapse
okay,
first, we do not put ourselves down. technology is unnatural, we make mistakes.
second, we do not panic or act rashly.
that being said if you can still get into odin, all is not yet lost. while i am pulling the pit file from
my device you will need to look up the correct way to write it to your device using odin.
i will be back in about 10 - 15 minutes.
use the force.
m
@dough30i
okay,
this is the pit file pulled from my n8013 . what i've read it should do the trick.
however, let's be clear.
1 you are in a bad situation, with nothing to lose.
2 this may not work but, then again it might.
3 you are the the final say as to wether or not you will attempt this
4 you have secured the correct knowledge on applying the pit file and writing in odin.
if yes to all of the above, download the attached file and remove the .txt extension
m
this is the thread i pulled the information from
http://forum.xda-developers.com/showthread.php?t=2268735
So I tried flashing Nougat BTU firmware on my S7
I'm pretty sure I forgot to enable OEM unlock, because the odin flash failed and after that I got the screen "an error has occurred while updating the device software use the emergency recovery function in the smart switch PC software"
So I tried going to "Emergency Software Recovery and Initialization" and then Device initialization", the first problem was I didn't have my S/N, because I stupidly peeled off the sticker on the phone and thew it away, then I found a random S/N through google for the my phone model, I tried it and it seemed to work at first, It download just fine, but when it came to "Software update and initialization for Galaxy S7 is in progress" it just stayed on 0% until it asked me to unplug the usb and try again. One time after several tries it moved to 4% then stopped and asked me to use the recovery code and try again from another PC, but it didn't give me a recovery code, so I was stuck on the in download mode, with only a tiny part of the progress done, as I couldn't continue the progress I restarted and tried again, no luck.
When I try to flash the firmware now, whether it's flashing Nougat or my orginal phones firmware I get the following after it FAILED:
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I don't know what to do, I screwed up big time, is there anything to do here? Any help is extremely appreciated.
let me know if you need any more info
EDIT: Also is there any way I can turn of my device? I'm thinking of calling it a night and try again when I wake up
Vol - Home and Power. Hold and when prompted to press for recovery - Press HOME button, to display your serial. Press it again to go to download. BTW, serial is engraved on the bottom of backplate.
voolandis said:
Vol - Home and Power. Hold and when prompted to press for recovery - Press HOME button, to display your serial. Press it again to go to download. BTW, serial is engraved on the bottom of backplate.
Click to expand...
Click to collapse
Thanks for the suggestion, I tried with my own S/N but it didn't make a difference, it still stuck on 0% on "Software update and initialization for Galaxy S7 is in progress" after downloading.
zaneyk said:
So I tried flashing Nougat BTU firmware on my S7
I'm pretty sure I forgot to enable OEM unlock, because the odin flash failed and after that I got the screen "an error has occurred while updating the device software use the emergency recovery function in the smart switch PC software"
So I tried going to "Emergency Software Recovery and Initialization" and then Device initialization", the first problem was I didn't have my S/N, because I stupidly peeled off the sticker on the phone and thew it away, then I found a random S/N through google for the my phone model, I tried it and it seemed to work at first, It download just fine, but when it came to "Software update and initialization for Galaxy S7 is in progress" it just stayed on 0% until it asked me to unplug the usb and try again. One time after several tries it moved to 4% then stopped and asked me to use the recovery code and try again from another PC, but it didn't give me a recovery code, so I was stuck on the in download mode, with only a tiny part of the progress done, as I couldn't continue the progress I restarted and tried again, no luck.
When I try to flash the firmware now, whether it's flashing Nougat or my orginal phones firmware I get the following after it FAILED:
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I don't know what to do, I screwed up big time, is there anything to do here? Any help is extremely appreciated.
let me know if you need any more info
EDIT: Also is there any way I can turn of my device? I'm thinking of calling it a night and try again when I wake up
Click to expand...
Click to collapse
Can you charge the device and download the official nougat firmware from sammobile. The download speed is really slow and should give you that two hours to charge the device.
Can you put the device in download mode and flash it via odin to see what happens. There are times when the firmware flash goes correctly on second or third time. Use HOME_CSC rather than the file starting with CSC if you do not want to lose your data.
I have the BTU (UK unlocked) firmware and can share it with you via Google drive which will give you better download speed.
kamranali44 said:
Can you charge the device and download the official nougat firmware from sammobile. The download speed is really slow and should give you that two hours to charge the device.
Can you put the device in download mode and flash it via odin to see what happens. There are times when the firmware flash goes correctly on second or third time. Use HOME_CSC rather than the file starting with CSC if you do not want to lose your data.
I have the BTU (UK unlocked) firmware and can share it with you via Google drive which will give you better download speed.
Click to expand...
Click to collapse
I tried to flash the BTU Nougat firmware from http://live.samsung-updates.com don't know if it's any different from the one on sammobile?
Anyways, I tried flashing the one from live.samsung, and it just seems to be stuck right now, with this odin log:
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> param.bin
<ID:0/008> modem_debug.bin
<ID:0/008> Home Binary Download
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
What version of odin are you using. Try 3.12.3.
I updated odin to 3.12.3 and changed the cable is was using, and I'm now running Nougat, thank you for taking the time to reply to my problem.
Btw for all of you I had to do the same and SamMobile speeds are verrrry slow but I found a site called UPDATO.com and it owned by and xda-developers member and I tried it and it works absolutely fine.If you ever need to do this again go there
Odin Cant open serial(com)port
I have a Samsung s7 phone - sm-G930F. It is stuck on the front title page with frp lock due to the fact I did something wrong when putting a custom rom in. Pretty much every time I use any type of odin, it either says "Cant open serial(com)port" for the most part or it stops just after sb.boot and says cant finish writing or something to that affect. I have tried every version of odin from 6 to 13. And every stock standard firmware for that phone that I can find. Including ones specifically for my phone company Optus. NOTHING WORKS. I am beginning to think I may have to buy a new phone. Please help. Tell me what I am doing wrong
help an idiot
Please help me!
I've been a complete moron and tried to flash my s7 g930f without actually knowing what i was doing.
I have followed so many different guides and walkthroughs and it keeps leading me deeper into nothing with a reboot loop that won't stop on normal boot up.
At the moment, I've got it as far as working TWRP but i have no idea what i need to download and where it should go in Odin or on the SD.
Any help would be life saving - i've got old family pictures that are very dear to me on the phone and would hate to lose them.
locotoro said:
Please help me!
I've been a complete moron and tried to flash my s7 g930f without actually knowing what i was doing.
I have followed so many different guides and walkthroughs and it keeps leading me deeper into nothing with a reboot loop that won't stop on normal boot up.
At the moment, I've got it as far as working TWRP but i have no idea what i need to download and where it should go in Odin or on the SD.
Any help would be life saving - i've got old family pictures that are very dear to me on the phone and would hate to lose them.
Click to expand...
Click to collapse
Did you confirm that the model # is g930f in download mode? I recommend performing this step before flashing anything to the phone as flashing the wrong ROM can cause further issues.
Do you know which is currently on the phone?
The phone has TWRP installed? If yes, boot into TWRP, mount the data parition, and try to copy off your data.
audit13 said:
Did you confirm that the model # is g930f in download mode? I recommend performing this step before flashing anything to the phone as flashing the wrong ROM can cause further issues.
Do you know which is currently on the phone?
The phone has TWRP installed? If yes, boot into TWRP, mount the data parition, and try to copy off your data.
Click to expand...
Click to collapse
yes it is g930f as confirmed in the download mode.
I had TWRP installed (one of the steps i tried to follow to fix but i think the later steps i have taken (of which i have no idea what i was doing) may have removed TWRP. So im trying to reinstall TWRP to remove the data - but once i do that what do i do.
Currently im waiting for a very slow download of the stock ROM for 8.0 to give it a try
locotoro said:
yes it is g930f as confirmed in the download mode.
I had TWRP installed (one of the steps i tried to follow to fix but i think the later steps i have taken (of which i have no idea what i was doing) may have removed TWRP. So im trying to reinstall TWRP to remove the data - but once i do that what do i do.
Currently im waiting for a very slow download of the stock ROM for 8.0 to give it a try
Click to expand...
Click to collapse
You want to copy the data or remove the data?
Flashing TWRP will allow you to mount the data partition to copy off the data.
Stock firmware can be downloaded from updating.com or samsung-firmware.org.
locotoro said:
yes it is g930f as confirmed in the download mode.
I had TWRP installed (one of the steps i tried to follow to fix but i think the later steps i have taken (of which i have no idea what i was doing) may have removed TWRP. So im trying to reinstall TWRP to remove the data - but once i do that what do i do.
Currently im waiting for a very slow download of the stock ROM for 8.0 to give it a try
Click to expand...
Click to collapse
i've managed to download a copy of the stock rom for 8.0 but all the guides i seem to be following don't seem to be working.
i may have to take it to a shop and pay for them to do it for me.