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.
Related
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
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
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.
Hello everyone,
I tried installing my devices firmware from the samobile site, after having it boot loop. I got it into download mode, connected it to my pc running odin, and tried flashing the firmware. It got as far as loading the recovery, then tried the rest but failed in the end, saying flash write failed or something like that. Would a custom firmware work better? It seems there are tools for other versions of the s3 mini, but not mine, so I'm not sure of the next step.
Thanks in advance,
Nick
You could try using kies to flash the firmware and there is safestrap(twrp) available for the g730v. If kies doesn't work make sure you are following the steps to flash the odin firmware correctly.
Sent from my Google Nexus 5 using XDA Labs
turnert said:
You could try using kies to flash the firmware and there is safestrap(twrp) available for the g730v. If kies doesn't work make sure you are following the steps to flash the odin firmware correctly.
Sent from my Google Nexus 5 using XDA Labs
Click to expand...
Click to collapse
I believe I followed the directions correctly for odin, and the kies software should have worked since my phone had an error message that it couldn't see the phone. I tried installing twrp, didn't take. I tried finding the correct safestrap file, but the only one close was for the s3 and the person said it was too big for their screen.
I appreciate your help, and any more would be much appreciated.
startreksuite said:
I believe I followed the directions correctly for odin, and the kies software should have worked since my phone had an error message that it couldn't see the phone. I tried installing twrp, didn't take. I tried finding the correct safestrap file, but the only one close was for the s3 and the person said it was too big for their screen.
I appreciate your help, and any more would be much appreciated.
Click to expand...
Click to collapse
Maybe you downloaded some bad firmware, where did you get your odin package from?
I would recommend downloading this for odin.
https://www.androidfilehost.com/?fid=817550096634742565
also here is a link to safestrap for when you unbrick your phone.
https://forum.xda-developers.com/ga.../recovery-locked-verizon-s3-mini-ne2-t3361624
So the different firmware didn't work. I went so far as to uninstall kies software, used odin 3.07, 3.09, and the latest one with my the same issue. I even used a different cord. I guess the next step is to hook up my phone to my computer using ADB and see if it's stuck in write only mode.
Sent from my KFGIWI using Tapatalk
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
shaharofir said:
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
Click to expand...
Click to collapse
I don't. I was looking at that post earlier and noticed that it mentioned the G998B/N model. Mine is the G998U1, so I was worried that it wouldn't work or cause more problems. I couldn't find any versions of TWRP that matched my specific model.
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
ffuser1 said:
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
Click to expand...
Click to collapse
I was actually able to get it to boot into recovery mode this morning. The download mode timed out and the phone shut off which allowed me to finally get into it. I tried redownloading the same rom I got from sammbolie again a few mins ago but still no luck.
Try another firmware with the same BL revision, CVC9 for example
dipotis said:
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Click to expand...
Click to collapse
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
JG96EVO said:
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
Click to expand...
Click to collapse
No, I bought my phone directly from Samsung, and I bought the unlocked model. I chose the rom from sammobile that looked to be exactly what my phone originally had on it based on the model and PDA/carrier info I found when looking through the recovery logs on the phone when the issue first occurred, before flashing anything onto it. If you think the modded Odin might work, I'd be willing to give it a shot.
I can't tell you the exact differences, but I would flash with the patched odin. it's on xda if you search for it.
No luck so far. I've downloaded the patched Odin software and have tried flashing my device numerous times with the same result. I also tried tried flashing firmware that I found on Frija instead of the firmware I originall downloaded from sammobile to see if anything would be different, and that didn't seem to make a difference.
My best guess (could be wrong) is that it doesn't like the bootloader tied to the firmware I've tried to flash onto the device. I've spent a good while searching firmware that uses the version of the bootloader it wants, but I can't find it anywhere. At this point, I'm all out of ideas, but I appreciate everyone's responses and advice.
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
You can extract the CSC file using 7zip. In there you will find the PIT file and you can try flashing it with repartition selected and inserting the PIT file in developers section of Odin.
ffuser1 said:
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
Click to expand...
Click to collapse
Interesting. I did not try it with only the AP slot populated. I thought you needed to always flash with the BL, AP, CP, and CSC.
wait, i messed up. if it has all of those files, flash them. my bad. i was thinking about custom roms - sorry about that.
Hey everyone, just wanted to make a final update.
I ended up bringing my phone into ubreakifix after trying just about everything I could, and they were not able to fix it either. They suggested that it might be a hardware issue and recommended sending it to Samsung for repair. I then sent it over to Samsung, and they confirmed that it was an issue with my motherboard. Samsung replaced my motherboard, and the phone is back in action. Since I only had my phone for about 6 months, it was still under warranty.
I appreciate everyone who took their time to provide me with advice. I hope that this post may help someone experiencing a similar issue to mine in the future.