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
Related
My phone is in download mode after using ODIN...it said completed and success, so i closed odin...now how do i get out of DL mode? is it safe to unplug/take out battery?
Phone should reboot, then unplug. If still in dl mode, odin did not flash
Take battery out you get out of dl mode
mcord11758 said:
Phone should reboot, then unplug. If still in dl mode, odin did not flash
Click to expand...
Click to collapse
I unplugged the phone cause I couldn't do anything else. I plugged it back in and apparently ODIN is doing it again...
Now odin is stuck on File analysis. What do I do?
Please give more details as to what is happening when you run odin
The first time it did everything I think. It said success on ODIN but my phone did not reboot, it stayed in dl mode. Now odin says this
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
last time it did the whole process in like 30 seconds
overkillogi said:
Now odin is stuck on File analysis. What do I do?
Click to expand...
Click to collapse
Un plug
Close odin
Pull battery leave out
Tell me your build number on phone under battery between 1006-1012.
mcord11758 said:
Un plug
Close odin
Pull battery leave out
Tell me your build number on phone under battery between 1006-1012.
Click to expand...
Click to collapse
1008...is that a problem?
overkillogi said:
1008...is that a problem?
Click to expand...
Click to collapse
No.
Open odin, let program boot all the way up.
Put battery back in
Vol up and down, plug usb in
Box in odin should recognize phone
Click start
mcord11758 said:
No.
Open odin, let program boot all the way up.
Put battery back in
Vol up and down, plug usb in
Box in odin should recognize phone
Click start
Click to expand...
Click to collapse
How long should it take to start rebooting? Odin says this
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Are you using odin one click
which odin? odin3 flashing util? V1.0 1.3 1.7 or 1.81?
or odin one click?
some people have better luck with different versions.
Trusselo said:
which odin? odin3 flashing util? V1.0 1.3 1.7 or 1.81?
or odin one click?
some people have better luck with different versions.
Click to expand...
Click to collapse
I'm using Odin3 One-Click Downloader. V1.00. File name says I897UCJF6-final-OCD-REV0. I downloaded this one a couple months ago.
Have your used it before, from what you listed it does not look like it is flashing anything
mcord11758 said:
Have your used it before, from what you listed it does not look like it is flashing anything
Click to expand...
Click to collapse
I think I've tried to use it before on my last captivate, but i was unable to get my phone recognized. What should I do now?
hmm
Delete the odin file out rename it. Dl this follow same steps
http://www.fileserve.com/file/emnCn2j
mcord11758 said:
hmm
Delete the odin file out rename it. Dl this follow same steps
http://www.fileserve.com/file/emnCn2j
Click to expand...
Click to collapse
kk thanks i'll let you know if it doesn't work.
You can let me know if it does as well ;p
mcord11758 said:
You can let me know if it does as well ;p
Click to expand...
Click to collapse
So the file you linked me cancelled DL at 99%. I looked around my downloads folder and found a different ODIN. I used 7zip on it and it opened. I tried this and it seems to be flashing. My phone is restarting! yes, thank you!
Good to hear
I messed up my phone trying http://forum.xda-developers.com/showthread.php?t=892297 I can't figure out how to get the phone into recovery now that it just goes to black screen after it boots. I can't turn on debugging mode, and I've tried all the button combination's I could find to boot in recovery.
It is a little tricky but with the phone powered off push and hold the volume up and volume down button at the same time while you push and hold the power button. Keep holding the whole volume button in until it gets into recovery. You will see the splash screen then recovery should come up.
holy hell thank you so much... now how to restore this thing... hmmm
How do I get ADB now?
Can I start ADB while in recovery?
You shouldn't even be in recovery seeing as how there is no recovery yet.
Sent from my SGH-T959V using XDA App
What do you mean.. I'm staring at it now.. appears legit as well:
Android system recovery <3e>
Samsung Recovery Utils
-for BML-
etc...
that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.
Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App
krylon360 said:
that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.
Click to expand...
Click to collapse
How exactly do I ODIN.. because its hosed...
aloneinshadow said:
Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I got ADB to work.. however it doesn't allow root.. so pretty much pointless. It was really odd though ADB would work on and off, if it didn't work I would reboot into recovery and try again and it would work, if I rebooted back into recovery it wouldn't work until I rebooted back into recovery again.
adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT
krylon360 said:
adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT
Click to expand...
Click to collapse
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS. Also maybe is there a guide for doing this? I really don't want to mess anything up.
Sario27 said:
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS.
Click to expand...
Click to collapse
you are correct.
krylon360 said:
you are correct.
Click to expand...
Click to collapse
<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> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Sario27 said:
<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> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Click to expand...
Click to collapse
keep trying. ODIN sucks like that.
Thanks everyone! It is now working and I still have root!
Thanks for all your help everyone especially krylon360 for the fixing advice.
New to Android, so please forgive a question that may be obvious to those more experienced.
On entering the recovery console, there are four options:
reboot system
reinstall packages
delete all user data
delete cache data
While the first is pretty clear, the others aren't so much. Any greater clarity would be helpful, as well as how these options differ from the user-land
Settings > Privacy > Factory data reset
which, I assume, returns everything except the SD card to as-shipped configuration, yes? I'm also guessing that there are things like usage counters that aren't reset either, yes?
One of the things I want to do before I go hog-wild with new firmware is to at least get a good tar of the stock configuration.
TIA
I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good. note: you need to make sure that the samsung USB drivers are installed in your computer properly for this to work. ( I assume they are if you got this far) Good Luck.
nwpro3 said:
I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good.
Click to expand...
Click to collapse
you'll also have better results if you remove your SD and sim as well.
Well Crap
After reading a lot of the post on this forum, it is clear that I'm an idiot. Since I seem to be the only one who screwed this up. I installed Gingerbread on my Galaxy S 4g. I was successful in that endeavour. However, I went looking for a root and screwed that up. Now my phone just says, "firmware upgrade fail! Try using recovery mode." The problem is that I can't get into recovery mode the same way anymore. I can't get into download mode either. Can anyone offer any help.
Hi everyone. I've been reading these forums for quite some time and I have been flashing some of the custom roms that the developers have made (I think they're all awesome). I thought that I was confident enough with flashing to give the CM7 rom a try. I followed FBis directions (not the one click but the slighter harder version) and upon flashing using heimdall I had an error saying that the PIT was flashed but the Kernel wasn't (unfortunately I was too stupid to write down the exact error).
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue but another problem exists, my computer (win 7) upon plugging in the phone only sees it as a unknown device. I tried changing the driver manually to Samsung USB composite but it gives an error saying device is not working properly. Is there anything I can do to fix this brick? I just can't get my computer to recognize that my phone is connected so it's not possible to heimdall since it also thinks no device is connected.
Any help is greatly appreciated it. I have searched the forums for a similar situation but I think mine is unique so I made a new post, I know people don't like to repeat what is widely available.
Whenever i had that happen trying to install cm7 i just used the 1 click gremlin remover and it flashed back to stock for me.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using XDA
Hi, nvm I fixed my issue
Yes I've tried to heimdall back to stock (or rather the new AntonX one-click that Bryan had made) but my phone was unrecognized. Instead of trying to update the driver manually through Device Manager I downloaded the Samsung 64bit drivers for our phones and ran the setup.exe. That seemed to overwrite the drivers and next time I put my phone into download mode it was recognized and all was well.
Sorry for taking up your time.
Turns out I haven't fixed my problem. My computer is able to recognize my phone now and so I've tried One-click heimdall back to Stock UVKJ6 under Bryan's thread. I flash it, however, I get the Samsung splash screen and nothing else happens. I go into recovery and it is still the blue CWM and it gives me errores that it cannot mount or open /cache/recovery/log. If a try a nandroid restore it cannot format volume and says make_extf4fs failed on /dev/block/stl10
I tried the one-click again, I flash once, let it restart, the flash again with bootloaders but still get blue CWM. Even if I try to flash bryan's SMSKJ6bml-rc2 kernel, I still end up with the blue CWM.
Anyone have ideas on what can be wrong?
http://sourceforge.net/projects/tea...T959VUVKJ6_STOCK-UVKJ6-One-Click.jar/download
oh wow, I was just flashing the one-click kernel, I'm a noob.
Thanks a lot FBis, I should have known better.
How did you solve it, now?
johndeere5 said:
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue
Click to expand...
Click to collapse
Hi! I'm having a similar problem with that "firmware upgrade encountered an issue" message, driving me crazy. I gather you fixed the issue? Maybe I'm dense, but I can't figure out exactly how you did it. What exactly is Heimdall? Is that what you used? Other posts in this thread mention Gremlin Remover, did you use that? Where can I get Heimdall, and how do I use it if I do get it? I'm definitely a noob, but my need is real, any help will be appreciated. Thanks! R
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Why Not ODIN?
lumin30 said:
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Click to expand...
Click to collapse
Thanks, a few things I want to clear up though? I've heard that Heimdall doesn't work with Galaxy S2. Is that correct? In any case, isn't it just the same kind of program that ODIN is? I've been trying to use ODIN to flash a file called
recovery-cmw-hercules.tar
but it always fails. What will Heimdall do differently?
You can tell I'm pretty new to this, have patience with me please.
Incidentally, when I try to run ODIN, on the assumption that I'm seeing a download mode screen, I can get ODIN to detect the phone and I see COM(6) usually in the yellow-highlighted screen. I check only "auto reboot" and "PDA," and in the PDA field I insert the location of the tar file (above). Here's the result:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Every single time.
Kindly, R
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Make sure you're using a samsung galaxy s 4g sgh-t959v. If that is not your phone stop flashing, look up the correct forums and only flash files from THAT forum, not from any other one.
lumin30 said:
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Click to expand...
Click to collapse
Oops! Where should I go then? Thanks, R
The T-Mobile galaxy s2 forums would be my first guess
So I was trying to root my phone. Kinda went through a quick crash course of it with Odin. For some reason it kept hanging up at boot.img but that's a different story. Long story short, after numerous tries, I forgot to unclick repartition. Why it clicks itself when you load up the PIT is beyond me. Personally, I think the developer got a kick out of people bricking their phones that way. **** him/her. Anyway, I can't get into download mode anymore, even with a JIG. Anybody got any ideas before I send it for JTAG?
crimsondragon said:
Personally, I think the developer got a kick out of people bricking their phones that way. **** him/her.
Click to expand...
Click to collapse
Talking like that will likely not get you any help here...
Please everyone refrain from posting the rule about searching and reading as this should resolve itself (should the OP actually search and read).
anactoraaron said:
Talking like that will likely not get you any help here...
Please everyone refrain from posting the rule about searching and reading as this should resolve itself (should the OP actually search and read).
Click to expand...
Click to collapse
I've searched through enough threads as it is with a combination of different keywords and all I've found is a bunch of people explaining how to get into download mode or others saying so and so can be fixed as long as you can get into download mode. With the latter, if you can't get into download mode, then what?
Just for the record, I've already tried reflashing it to stock with a .tar file. That failed miserably.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kind of an improvement as before it would just hang at boot.img but now at least I can get a confirmation of whether it works or not. Currently the phone is still showing the "Firmware upgrade encountered blah blah" crap. But I tried it anyway as I read that it's supposedly a front.
Can't get into stock recovery either. Top left corner says Odin mode. Odd as the JIG puts it into Factory mode. I've uninstalled/installed the Samsung drivers several times. I've changed the USB cable to a Samsung one that I got like a month ago. I have Kies installed. Can't connect the phone to it either. I've tried flashing with Kies not installed and with it installed and shut down/not shut down. Don't think I missed anything else but if I did I'll add it.
crimsondragon said:
Just for the record, I've already tried reflashing it to stock with a .tar file. That failed miserably.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kind of an improvement as before it would just hang at boot.img but now at least I can get a confirmation of whether it works or not. Currently the phone is still showing the "Firmware upgrade encountered blah blah" crap. But I tried it anyway as I read that it's supposedly a front.
Can't get into stock recovery either. Top left corner says Odin mode. Odd as the JIG puts it into Factory mode. I've uninstalled/installed the Samsung drivers several times. I've changed the USB cable to a Samsung one that I got like a month ago. I have Kies installed. Can't connect the phone to it either. I've tried flashing with Kies not installed and with it installed and shut down/not shut down. Don't think I missed anything else but if I did I'll add it.
Click to expand...
Click to collapse
I believe that has been discussed also. Pull the battery, re-enter download mode and flash again. When it doesn't complete properly it won't let you Odin again until the battery is pulled.
Just curious but are you on ICS 4.0.4? If so the Odin root is exclusive to gingerbread... Odin cwm and a flash a rom or just Odin back to stock. Root through ICS is obtained by flashing supersu zip through cwm when on ICS.
I realize you are frustrated, but the devs here are awesome and deserve respect, especially since they just brought 4.3 to us.
Sent from my SGH-T769 using xda app-developers app
anactoraaron said:
I believe that has been discussed also. Pull the battery, re-enter download mode and flash again. When it doesn't complete properly it won't let you Odin again until the battery is pulled.
Just curious but are you on ICS 4.0.4? If so the Odin root is exclusive to gingerbread... Odin cwm and a flash a rom or just Odin back to stock. Root through ICS is obtained by flashing supersu zip through cwm when on ICS.
I realize you are frustrated, but the devs here are awesome and deserve respect, especially since they just brought 4.3 to us.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Got it figured out. I was surfing the other subforums and landed on the thread talking about Odin 3.07 and I figured why the hell not. The flash to stock was a success. Then I did the root and CWM Recovery. All is well. 3.07 is much better than 1.85. For the record, I am on GB. Thanks for the help. I apologize for earlier as it was indeed frustrating.
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