I rooted my phone and wanted to flash back to stock so I can update with the OTA and re-root, but I downloaded the zip for the AT&T tar files and everything seemed to pass MD5 checks and went okay, but as soon as I hit Start, the program just continues to say NAND Write Start for over 20 minutes, and won't flash, how do I go about re-trying this without bricking my device? It's still plugged in atm in download mode.
What version of Odin are you using? I had this problem because I had v3.10 and the s6 is not compatible with that version, you have to have v3.10.6.
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
If Odin is having trouble flashing to your phone. Here is some simply tips and tricks to try.
1. Try flashing everything except for the bootloader .
2. Try running Odin as admin.
3. Try upgrading to the newest Odin available.
4. If all else fails, open Samsung Kies, and go to emergency recovery, put your model # and serial # in, and it will flash your phone to stock for you, then you can try again.
5. Also make sure all of the correct drivers are installed for your phone, sometimes Windows can be bad about that. Try getting drivers from samsung directly.
6. Try a new USB Cable, as crazy as that is, I have had some not work, and others work fine.
7. Try a different USB Port on the PC, or restart the PC.
I hope this helps.
I tried just flashing the ROM and CSC and it flashed just fine, I left out the CP file, what is that? Everything seems fine just flashing the ROM and CSC, but do I need to flash the CP file too, for anything?
CSC is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
I hope this helps
I didnt get it. Do you mean to put each .md5 file in all sections? ? Please help me
_Dennis_ said:
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
Click to expand...
Click to collapse
Please help me out. I am having same problem NAND WRITE stuck.
Solved
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Nand write start fail solved
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
NAND stucked
kishor1995 said:
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Click to expand...
Click to collapse
can u tell the steps u did? to do it
Help
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
bonniegertz said:
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
Click to expand...
Click to collapse
Were you finally able to get it to work?
Its working!
Zoide_ said:
Were you finally able to get it to work?
Click to expand...
Click to collapse
Yes, I gave up but a friend of mine found a thread that talks about using Kies to bring it back to factory default. You need to know the serial # and IMEI # If you can find this information, you can reset it using Kies.
Had the same problem. Used Odin 3.10.6
But before all this, I connected phone with debugging enabled in windows and authorized it, the problem never resurfaced
Related
I wanna know if you can help me, ...
I was on sprint gtab stock rom DJ30 which updated to EA24 and EB28. Data service worked very well. Then I flashed voodoo CWM in order to install Honeycomb rom. Then install the rom via CWM. The installation was indeed finished, but it stucked in samsung logo boot. I turned off device and boot in cwm mode. Sure, it was HC rom's CWM. But it couldnt mount system, Seems the convertion to ext4 didnt work. Worse thing it couldnt mount sdcard either. So I couldnt reinstall the rom. I also couldnt reboot, so i had to long press the power button.
Stop trying installing HC rom on my device, i decided to revert back to stock rom (DJ30>EA24). But it was weird, i cant revert to stock rom with modem.bin inside the package. It always stuck in modem.bin when flashed with odin. But, when i use the package with no modem, it can flashed succesfully. I had flashed that stock rom (with modem.bin) million times without fail, but now always fail.
Yeah, my gtab is running but without modem.bin so no signal and i cant use data services. Like wifi only tab.
Many ways i've tried:
- I've tried flashed DJ30 with no modem first. Okay, it is successful. But when flash with EA24 (with modem) it stuck on modem.bin.
- I've tried flashed DJ30 with modem.bin. And it also stucked on modem.bin. Trying flashed EA24 without modem.bin, it is succesful.
- Try using heimdall. Progress 100% but it wont reboot. But when i retry n uncheck modem. Flashing work flawlesly.
- Try using odin modem only flash. Progress bar is full but it wont reboot.
- Try flashing via CWM, but still no luck.
Weird, huh. Seems my gtab cannot use modem.bin anymore.
Any clue? Thanks before ...
I'd appreciate if you can help me flashing modem.bin to my device. Or it end up with wifi only tab.
EDIT: even OTA update, stuck on "verifying modem ... updating modem ..."
I would like to bump this as I am having the same issues also. I am flashing my Sprint Galaxy Tab to EA24, and it is held up at modem.bin.
I posted a question on this, and am hoping that someone helps us.
Thanks in advance,
Claud
try re-partition and flash pit by using odin,i suffered the same issue with my vzw tab
depending on which file you're using to restore. You need to use the .tar.md5 file from the EA24 flasher and rename it to just .tar, then flash with Odin. I've flashed this several times and it gets past modem.bin just fine. If you are using the 2 files 1 with modem (Epic 4g modem) and 1 without modem you're not using the right files. I ran into the same issue with the with/without modem files. Here's a link to the EA24 flasher and the .tar.md5 file you need to go back to stock.
http://www.multiupload.com/LXQKGX5RHL
Bumping this to avoid making a new thread.
I've done many reverts back to stock from different ROMs, but this past time coming from BTL or HC (Sprint Tab btw) I'm also getting hung up on modem.bin. Never had a problem here before, so not sure what's going on.
I didn't use a pit and only had reboot checked and it worked fine.
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Maniken50 said:
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Click to expand...
Click to collapse
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
pvtjoker42 said:
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
Click to expand...
Click to collapse
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Maniken50 said:
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Click to expand...
Click to collapse
I've never had to repartition a device, but i've read about it working for people to bring them back from boot looping etc. If somehow the partition table gets corrupted etc. If you're already soft bricked, there's no harm in trying.
Having the same issue, trying to go from Rooted GB to BTL then back to GB or EA24
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
ezitec said:
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
Click to expand...
Click to collapse
http://www.mediafire.com/?jb40cs460rf8aq7
Try that one.
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
mbanton said:
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
Click to expand...
Click to collapse
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
pvtjoker42 said:
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
Click to expand...
Click to collapse
I have the correct files for the tab for Verizon. I have the original files Following: Sbl.bin boot.bin cache.rfs dbdata.rfs efs.rfs factoryfs.rfs ldb.db modem.bin param.lfs param.rfs pit.pit zImage
But my problem is how to record using that pit. What other files should I use a recording that will restore the partition table?
I fear that a problem occurs with even higher tab.
I am having this issue as well, and I'm also coming from HC and on Sprint. I have no trouble flashing any kernel/rom of my choosing EXCEPT for the modem.
At this point, I'm just trying to reflash it back to stock. I've got the Sprint EA24 files, including the pit (tried with and without) but it refuses to flash the modem. If I omit the modem, it flashes perfectly fine and I'm left with a bone stock tab with no modem.
Is there anyone here who went to HC and then managed to go back? As stated by others, I've gone back to stock before without issue. The HC build seems to be what caused this problem
I ran spacemoose's HC port for a day or 2 and then went back to stock until the official GB came out. I've had no issues flashing the whole EA24, or any other updates.. with and without the modem..
Hmmmm. Maybe different hardware revisions? You have any suggestions? I'm completely out of ideas and it's of little use to me without 3G.
I just did a flash back to complete stock (including modem) 2 days ago, and it didn't hesitate once while flashing everything with Heimdall. Only thing I can say is keep trying.
At this point, I've attempted to flash it no less than a dozen times and still can't get the modem to flash. I'm completely baffled as to why it won't accept it.
So I've downloaded the following kernels from a link here on XDA that should be swapping kernels to allow me root on my recently upgraded, stock ROGERS 2.3.3 Captivate. Odin is telling me to "Check image files !!" when I load the .tar files into the Select Intergrated Package (and yes, the one package switch is on). I opened the tar to double check it wasn't double-compressed.
What else would be giving me this problem? I'm using Odin 4.28. Curiously, it is showing my phone as detected, my phone IS in downloading mode, but Odin just says (Android) in the Title, no specific model. But it says it's found it on COM 6. <1> Added!! and Detected!!
It's when I load up the kernel tar's and try to start that it yells at me. Is this triggering anything in anyone's mind that I'm doing wrong? Or do I need to provide more info?
I am using Vista 32-bit (legit) on a Dell studioXPS. And I ran it as administrator.
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Pirateghost said:
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Click to expand...
Click to collapse
Yeah. That is def the wrong version of Odin. Download the i9000 bootloaders in my sig. Unzip it. Delete the pda.tar.md5 file. Use the included version of Odin (1.82 I think) to flash your kernel.
Alright, quick question - I accidentally flashed the phone, not the pda. I tried to flash the KH2 modem back via phone but ODIN failed. Kies is currently not detecting the phone, and so I decided to try flashing the PDA while I had it open and I would figure the modem out after. ODIN hung, so I closed it and rebooted out of downloading mode and got the Phone ! Computer error. So I figure now I have to flash back to the stock rom and start over again, but this time I would like some advice as to which step to take next. I downloaded I896UXKH2-HOMEBINARY.tar.md5 from another thread here. Can I flash this with Odin - and if so, which is the place to load it? Bootloader? PDA? Phone? CSC? I have no PIT files.
Think it goes into the pda slot. Go back to the thread t you got it from and read the first post of the thread. Also restart your computer before trying to flash again.
can someone upload the modem.zip, please thank you
Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.
Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?
btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?
N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]
I have a ATT S4 Active SGH-I537. It can only access download mode and from there i've tried everything. What happened was the phone had a OTA to the newest update pushed from ATT and after it updated the touchscreen did not work and i noticed the scren was "burning in the text" if that's what it's called. So i tried to wipe cache, and factory reset. Same thing Happened. Well now the firmware update did not go through so i have the error and can only access download mode. I've tried everything in odin and just get FAILS. Blahhh.
Any help would be great, I'm not new to this kind of stuff. I'm just stuck and need some help.
Thanks
KHarper2015 said:
I have a ATT S4 Active SGH-I537. It can only access download mode and from there i've tried everything. What happened was the phone had a OTA to the newest update pushed from ATT and after it updated the touchscreen did not work and i noticed the scren was "burning in the text" if that's what it's called. So i tried to wipe cache, and factory reset. Same thing Happened. Well now the firmware update did not go through so i have the error and can only access download mode. I've tried everything in odin and just get FAILS. Blahhh.
Any help would be great, I'm not new to this kind of stuff. I'm just stuck and need some help.
Thanks
Click to expand...
Click to collapse
As long as you can get into Download mode you should be ok. I don't know what firmware you were originally on and what you were updating to, but to be safe you should flash the NE3 Odin package. Download it from the i537 Firmware Thread and flash it through Odin. Check the md5 of the file you downloaded with the md5 posted in the thread to make sure you don't have a corrupted download. If you need step-by-step instructions for Odin you can find a link to it in the same thread.
Make sure you are using the usb cable that came with your phone since that is the only one that is guaranteed to work. You can use others, but Odin is very picky about usb cables. Also, try different usb ports on your computer, again Odin is picky. Finally try Odin v3.07 and Odin v3.09. Most people have used those versions to flash things.
If you need more help I'm going to need a little more information:
What firmware were you on before the OTA?
What firmware are you trying to update to?
You mentioned Odin doesn't work, can you post the Odin logs so I can see where it fails?
Devo7v said:
As long as you can get into Download mode you should be ok. I don't know what firmware you were originally on and what you were updating to, but to be safe you should flash the NE3 Odin package. Download it from the i537 Firmware Thread and flash it through Odin. Check the md5 of the file you downloaded with the md5 posted in the thread to make sure you don't have a corrupted download. If you need step-by-step instructions for Odin you can find a link to it in the same thread.
Make sure you are using the usb cable that came with your phone since that is the only one that is guaranteed to work. You can use others, but Odin is very picky about usb cables. Also, try different usb ports on your computer, again Odin is picky. Finally try Odin v3.07 and Odin v3.09. Most people have used those versions to flash things.
If you need more help I'm going to need a little more information:
What firmware were you on before the OTA?
What firmware are you trying to update to?
You mentioned Odin doesn't work, can you post the Odin logs so I can see where it fails?
Click to expand...
Click to collapse
I will try the NE3 Package a few times, maybe stop by the store and get a different cable. If that doesn't work i will let you know. Thanks for replying and for the info. This is a frustrating mess.
Can someone help me out here? I am suffering from the major lagging and freezing with my Note 4 and i contacted Samsung about it. They told me to visit a local Samsung store and they can check out my phone, but i want to be back to stock before taking it in. Last night I tried to Odin back to stock Dok2 for roughly 4 hours and i couldnt get it accomplished. Am i missing something? I tried 3 different versions of Odin and downloaded 2 diffrent copies of the Dok2 firmware, but still no luck. Is there a specific processto follow? I tried factory resetting the phone before odin flashing, I even clean wiped the phone in Odin deleting internal storage as well.
Please help!
Anyone??????
Did you download Odin and DOK2 from sammobile? I was able to flash my phone with the downloads from there. I would double check and make sure you are using the stock samsung USB cable that came with your phone.
I'm having the exact same freezing and lockup issues as you are, by the way.
I dont beleive my odin and firmware came from sammobile, so i will give that a shot. I did make sure to use the samsung usb cable. I guess i need to make sure it was my usb cable and not my wife's S4 cable. Not sure if that makes a difference.
Ok. I still can't odin flash Dok2. I downloaded the new version on Odin from Sammobile and downloaded a copy od Dok2 (full) from a link to Mega. I couldn't get the sammobile link to work.
Any other suggestions?
It's possible that your DOK2 file might be corrupted or something. Try giving this one a shot, http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 to download the firmware. Input your phone model, set region to TMB, place check mark on "auto" box, and place a check mark on the "decrypt automatically" box. Click on "Check Update" and download. Don't worry about the .enc4 extension on the file name, once its done downloading and decrypting you will get a .zip file of the firmware.
I tried downloading the SamFirm program from the link you provided above, but I get an error in the program stating: "Could not load file or assembly "Microsoft.WindowsAPICodePack.Shell. Version= 1.10.0. Maybe this is because I am running Windows 10.
OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.
Gjohnson7771 said:
OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.
Click to expand...
Click to collapse
Can you elaborate on this Kies 3, I'm stuck I the same issue and I cant get back to Stock ROM for Note 4
Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.
Gjohnson7771 said:
Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.
Click to expand...
Click to collapse
So use Kies 3 as opposed to using Odin to flash the fw?
That's the only way I was able to flash Dok2 again. I tried at least 20 times in Odin and it failed everytime. I'm still having issues on Dok2, I wish I could flash back to Cod6.