Hi all, I am attempting to flash the latest stock image ( G9860ZHS3DUC1 G9860OZW3DUC1) onto a S20+ G9860 and it gets stuck at the same point every time I've tried it. I've tried it with Odin v3.14.1, patched v3.14.1 and v3.14.4. On their own the BL will flash fine, as will the CP and CSC. FRP: OFF, OEM: ON (L). I've also tried it on two instances of Windows. The same outcome each time. What would cause the flash to hang?
Previously it was the original stock image (v10) and I now can't put an older image on as it is not possible to downgrade the bootloader. Even the image before (G9860ZHU2DUB6 G9860OZS2DUB6) is rejected as it detects it as an older version.
I've also tried extracting the PIT from the CSC tar and used with a flash including an erase NAND and repartition with the same outcome.
How long are you leaving it when it hangs? It does take quite a while to flash
About 20-30 mins with no movement on the progress bar. It looks to get to about 50%.
try to flash a diff. firmware and also try changing your cable
I'm limited by the firmware as the latest image has bumped the version bit and it won't allow a downgrade without blowing the knox warranty bit.
However it is going via a thunderbolt port at the minute and I've ordered a usb-a/usb-c cable in the hope that'll be the fix as it's come up in other posts as causing issues.
sfbgsbtsrtbtbrt said:
I'm limited by the firmware as the latest image has bumped the version bit and it won't allow a downgrade without blowing the knox warranty bit.
However it is going via a thunderbolt port at the minute and I've ordered a usb-a/usb-c cable in the hope that'll be the fix as it's come up in other posts as causing issues.
Click to expand...
Click to collapse
You're using a Mac? Have you ever successfully flashed with Odin on a Mac? I've not heard of it being possible before now due to drivers
Worked!
So, avoid the thunderbolt port.
sfbgsbtsrtbtbrt said:
Worked!
So, avoid the thunderbolt port.
Click to expand...
Click to collapse
Thanks, I got the same issue with thunderbolt port. Works with USB
sfbgsbtsrtbtbrt said:
Worked!
So, avoid the thunderbolt port.
Click to expand...
Click to collapse
Dear God.. Thanks, this really saved me.
Worked too, avoid it!
Good tips. I did this & worked:
# unzipped the files again (BL AP etc) in case one was corrupted
# Flashed again, once again stopped (Red FAIL) on super.img
While going to look for other cables started it again anyway, by the time I got back it had succeeded!
So just unzip files again, try different cables & ports & give it a few tries. It might work. My S20 wasn't hooked up to my Dell XPS 13 thunderbolt anyway.
Hope helps some.
Related
Can someone please help? I bricked my phone trying too flash the modem and I keep trying too recover using Odin. I put the tar file in the pda part and the pit file in the pit section. I got both these files from the how to recover brick thread. But when I click start, it gets stuck on the param.lfs part. And the words PARAM go into the white box above the progess bar. Can someone please help? Im scared its bricked for good.
EDIT: I was able too get passed param.lfs but it keeps freezing in different spots, it never completly finishes. Odin is soo unreliable :/ At one point it got too 50% but my phones screen turned pink and it froze. Is there any other program I can use? Or a more stable/reliable version of odin? I have version 1.0 and i've tried 1.3 and no luck too
sasha101 said:
Can someone please help? I bricked my phone trying too flash the modem and I keep trying too recover using Odin. I put the tar file in the pda part and the pit file in the pit section. I got both these files from the how to recover brick thread. But when I click start, it gets stuck on the param.lfs part. And the words PARAM go into the white box above the progess bar. Can someone please help? Im scared its bricked for good.
Click to expand...
Click to collapse
And this is why I didn't want it going out.
Ok, can you put your phone in downloader mode? If so, go to this thread...
http://forum.xda-developers.com/showthread.php?t=794138
Im using that thread too try too restore, I downloaded the tar and the pit, i tried the one ending with 12 and it didnt work so I tried the pit ending with 13 and it still didnt work. I am a able too go into download mode but it doesnt flash through odin
Can you get into the download mode? If so, you're not bricked.
Sent from my SPH-D700 using XDA App
herzzreh said:
Can you get into the download mode? If so, you're not bricked.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yeah I can, but when I try too recover too stock, and flash the tar through odin it freezes on param.lfs Can anyone help me with this? Or link me to a thread that someone had this same problem?
sasha101 said:
Im using that thread too try too restore, I downloaded the tar and the pit, i tried the one ending with 12 and it didnt work so I tried the pit ending with 13 and it still didnt work. I am a able too go into download mode but it doesnt flash through odin
Click to expand...
Click to collapse
I had a similar problem awhile ago with a 2.1 flash. It worked out fine. As long as you can get into download mode you should be ok. You don't have a brick.
Just follow the instructions on the flashing back to stock link that is in whodamans post.
I used the .pit in this post http://forum.xda-developers.com/showthread.php?t=773032 with the DI18 update in this one http://forum.xda-developers.com/showthread.php?t=794138
I did have an issue once where I fixed it by just using the DI18 update and not the pit file(it seemed to find the pit in the update i guess...anyone feel free to correct me on this if i'm worng)
If that doesn't work
3a: Reboot your PC and pull the battery on your phone
3b: Wait for PC to reboot
3c: Open Odin
4c: Put batter back in phone, boot to download mode
5c: Once in download mode connect via USB to the PC
6c: Run it again
Click to expand...
Click to collapse
I've yet to see a truly bricked Epic. People that use that word should take that as a sign that they shouldn't be flashing.
I had the exact same problem with Odin freezing at "param.lfs". First of all, Odin is hit and miss. A lot depends on the USB cable as well. I ended up having success with Odin once I switched back to the original cable that came with the phone. Also try different USB ports on your PC. Some people have reported problems when using front panel ports. Try ones in the back that are directly on the mobo.
leatherneck6017 said:
I had the exact same problem with Odin freezing at "param.lfs". First of all, Odin is hit and miss. A lot depends on the USB cable as well. I ended up having success with Odin once I switched back to the original cable that came with the phone. Also try different USB ports on your PC. Some people have reported problems when using front panel ports. Try ones in the back that are directly on the mobo.
Click to expand...
Click to collapse
good point about the cable, although most of the time I see recommendations against using the stock one for anything but charging.
I use a BB cable that seems to be thicker than the stock epic one and haven't had any issues.
Ok, ive gotten passed param but It keeps freezing at different spots! is there anything I can do?
sasha101 said:
Ok, ive gotten passed param but It keeps freezing at different spots! is there anything I can do?
Click to expand...
Click to collapse
try again...
unplug the phone, pull the battery, restart the computer, walk away for 5 minutes and take a breather, then come back and try it again. As the above poster said, Odin can be screwy and it can take multiple times to go through sometimes.
Make sure to use a better usb cable if you have it available, or borrow one from a friend.
also, make sure to restart Odin in between attempts
drakkahn said:
try again...
unplug the phone, pull the battery, restart the computer, walk away for 5 minutes and take a breather, then come back and try it again. As the above poster said, Odin can be screwy and it can take multiple times to go through sometimes.
Make sure to use a better usb cable if you have it available, or borrow one from a friend.
also, make sure to restart Odin in between attempts
Click to expand...
Click to collapse
I've been trying since like 12 PM and its 5 PM now :/ but ill keep trying, thanks.
sasha101 said:
I've been trying since like 12 PM and its 5 PM now :/ but ill keep trying, thanks.
Click to expand...
Click to collapse
Have you tried different USB ports?
leatherneck6017 said:
Have you tried different USB ports?
Click to expand...
Click to collapse
Yea, ok so i kept trying and it none of the tries worked so I just wanted too see if maybe it worked but it wasnt showing that it did. So i click power and it starts too BOOT! it said samsung then went into a black screen, then it went into stock recovery. Can anyone tell me what to do from here? I think there is no rom in my phone and I need a stock samsung one too flash through samsungs recovery. Can anyone help? I apreaticate everyone whos tried too help.
I am using Odin 3 v1.3
I don't use the .PIT file at all.
I put the SPH-D700-DI18-8Gb-REL.tar.md5 in PDA and make sure it's checked
I uncheck F.Reset time
Put the phone in download mode and hit start.
I you still are having problems try a different micro usb cable. Samsungs cable sucks.
Good Luck
Whosdaman said:
And this is why I didn't want it going out.
Click to expand...
Click to collapse
I clicked on this thread because I knew this attitude would be present here. You're saying 1) the reason for the problem is 100% this ROM and 2) no one can be trusted with this ROM because some have had problems... great.
bigray327 said:
I've yet to see a truly bricked Epic. People that use that word should take that as a sign that they shouldn't be flashing.
Click to expand...
Click to collapse
And I also came in to say this, almost. I don't have too much Epic experience, but yes, people always say ZOMG ITS BRICKED and what they MEAN is it isn't behaving how they expected after a flash and it may require a reflash/recovery. If something is bricked, it is a useless mass of plastic and metal that might have some value sold on Ebay as parts.
...though I'm not discouraging people flashing. Just wish people would stop using 'bricked' as a catch phrase, and instead just tell the story and ask for help.
Sasha if you cant use Odin to restore it, then it's bricked. My advice? Take it back to Sprint and get a new one.
infamousjax said:
Sasha if you cant use Odin to restore it, then it's bricked. My advice? Take it back to Sprint and get a new one.
Click to expand...
Click to collapse
What should I say too the sprint employees? I thought bricking the phone ruins the warranty. Also I am able too get too stock recovery and download mode, but odin doesnt flash any rom fully, it always stops. I tried too just flash pit and that worked. Is there any other program you can use or can you flash the tar from the stock recovery which I can get too?
sasha101 said:
What should I say too the sprint employees? I thought bricking the phone ruins the warranty. Also I am able too get too stock recovery and download mode, but odin doesnt flash any rom fully, it always stops. I tried too just flash pit and that worked. Is there any other program you can use or can you flash the tar from the stock recovery which I can get too?
Click to expand...
Click to collapse
Take it from me...only like 1 out of 10 reps even know what bricking means lol
Use this one!!
I was having the same problem, hopeful this one works for you..I wish I can remember who posted this so I can give the person the credit for this find, but anyhow, hope it works...
I need help any ideas or similar experiences?
I flashed a bad renamed tar file that ended up being [email protected] gt i9100 firmware
Now when i go into Odin mode which I still have , I get no USB to PC recognition ?
No yellow com port in Odin?
Even when u plug USB in it just turns on automaticaly and shows gti910 on boot up then goes right intob 3e stock recovery and no button options are compatible with phone and the charging mode is at a standstill with a small circle not moving ,the battery was very very low before this all happened but enough to power up as well.
I've tried 4 USB cords uninstall kies,reinstall kies, tried other Odin versions ,
Tried 2 desktops and a laptop ,thanks to a botched tar file for a i9100 that was named eg30.tar!!
Could it be that USB mounting has been cut internally or not compatible with the device having wrong firmware? What about USB debugging obviously not enabled because the phone won't even boot
My binary count was at 8 when I got phone now its 11 does to many flash attempts affect anything
I think it would flash correct tar if only could get USB to work
If I atleast have Odin am I in luck? Any any similiar experiences or info would help!
I can't return it cause was bought used and sprint knows esn was tied to an alternate line over a month ago
Try this ..... By the way next time just bump your other post it didn't need another thread
http://www.forums.acsyndicate.net/s...din-Completely-Stock-EG30-Restore-your-system
Sent from my SPH-D710 using xda premium
I have the same problem. Any solution? The above link doesnt work.
seawind107 said:
I have the same problem. Any solution? The above link doesnt work.
Click to expand...
Click to collapse
If you did flash an non-Sprint ROM your USB is likely disabled. You can try moving something to an MicroSD card and flashing from recovery, JTAG or take to Sprint. (Flashing from recovery, at least from other posts, will not restore the USB use.) I'll try to find the last post on this, someone else had this recently.
*EDIT* Here's the support for my post:
http://forum.xda-developers.com/showthread.php?t=1577734&page=2
garwynn said:
If you did flash an non-Sprint ROM your USB is likely disabled. You can try moving something to an MicroSD card and flashing from recovery, JTAG or take to Sprint. (Flashing from recovery, at least from other posts, will not restore the USB use.) I'll try to find the last post on this, someone else had this recently.
*EDIT* Here's the support for my post:
http://forum.xda-developers.com/showthread.php?t=1577734&page=2
Click to expand...
Click to collapse
Oh,thanks for your quick reply.
Hey guys,
I had a look around the forum found some similar issues but nothing that fit exactly.
I am stuck with my note 8, in an awkward position, I was flashing a new ROM onto the device, it was having some issues doing it (It wouldn't work, Would always fail) was using Odin, and the Note 8 toolkit. I was changing the recovery from CWM to TWRP and then it all went bad, now i have some firmware error come out whenever i turn the device on, I can still get into download mode, but nothing else. I tried using Odin to flash the stock ROM or even a recovery back onto the device and it fails every time. I also tried using Kies to do a firmware restore, it downloads the firmware then it can't see the device.
Any help would be great =\
Thanks =D
Ascel said:
Hey guys,
I had a look around the forum found some similar issues but nothing that fit exactly.
I am stuck with my note 8, in an awkward position, I was flashing a new ROM onto the device, it was having some issues doing it (It wouldn't work, Would always fail) was using Odin, and the Note 8 toolkit. I was changing the recovery from CWM to TWRP and then it all went bad, now i have some firmware error come out whenever i turn the device on, I can still get into download mode, but nothing else. I tried using Odin to flash the stock ROM or even a recovery back onto the device and it fails every time. I also tried using Kies to do a firmware restore, it downloads the firmware then it can't see the device.
Any help would be great =\
Thanks =D
Click to expand...
Click to collapse
Make sure you have a good USB cable... I have gone through 2 Samsung OEM cables, as one did a melt down and the other had intermittent charging disconnects. Have gone to Blackberry OEM cable as it is one of the best OEM stock cables I have had for some time, 5 years now and has never failed.
Second, did you enable USB debugging before doing the custom rom?
Are you using Odin 3.7?
I am surprised that Kies downloaded a ROM, it should have detected that the device was custom. Maybe what you are seeing with Kies is normal for custom ROMs. Don't know... What is the ROM info for the Kies download. I have an odd feeling that you flashed with an incompatible ROMs as the Note 8.0 has three different hardware configurations.
gooberdude said:
Make sure you have a good USB cable... I have gone through 2 Samsung OEM cables, as one did a melt down and the other had intermittent charging disconnects. Have gone to Blackberry OEM cable as it is one of the best OEM stock cables I have had for some time, 5 years now and has never failed.
Second, did you enable USB debugging before doing the custom rom?
Are you using Odin 3.7?
I am surprised that Kies downloaded a ROM, it should have detected that the device was custom. Maybe what you are seeing with Kies is normal for custom ROMs. Don't know... What is the ROM info for the Kies download. I have an odd feeling that you flashed with an incompatible ROMs as the Note 8.0 has three different hardware configurations.
Click to expand...
Click to collapse
Tried a different Cable before and it still didn't work, But I thought I would try a different one again (From a nexus 7 I have) worked like a charm, As if I have 2 Damaged cables Haha.
Thanks for the Help Mate =D.
So, the 5.1 update is here. YAY! Now, one problem. I am rooted. I go to odin, put my phone in download mode, grab the stock firmware from SamMobile, and then started it. It gets stuck at "NAND flash starting" and does nothing for about 15 minutes and then says it fails. I reset to stock to see if it would work, and still nothing. I can't get the PIT file as the commands don't work, does anyone know how to do this, I want to use 5.1!
I had the same issue last month, when you extracted the Odin files, did you leave the files all in one folder? I made the mistake of placing the Odin UI on my desktop and leaving the other files in a separate folder. Once I placed them all in the same folder it was nice and smooth
scott_0 said:
I had the same issue last month, when you extracted the Odin files, did you leave the files all in one folder? I made the mistake of placing the Odin UI on my desktop and leaving the other files in a separate folder. Once I placed them all in the same folder it was nice and smooth
Click to expand...
Click to collapse
THey are all in the same folder. They are the only things there.
try a different usb cable and or usb port
scott_0 said:
try a different usb cable and or usb port
Click to expand...
Click to collapse
I've tried different USB port and cable, and still nothing.
On the newest version of ODIN?
It doesn't make sense to me but after trying a bunch of stuff today to fix my ODIN being stuck at NAND writing starting, I ended up downloading a newer version of ODIN. I thought I had the newest 3.09, but found 3.10.6 and as soon as I did that it worked instantly. Wasted a bit of time when the solution took about a minute. Hope this helps someone, someday.
It worked for me too! Upgrading to Odin 3.10 solved the NAND Write Stop... thank you very much!
Hey guys, so I used googles flash tool to update December patch and it keeps failing at writing to phone 1 of 11.
It's now in a bootloop but can access fastboot.
Ive tried to completely reset the phone manually using adb but it fails. It just doesn't work and aborts basically the phone rejects all data transmission.
What am I doing wrong or can I get a more detailed way to reset the phone completely.
-Edit-
I was also rooted and was following the guide for rooted December 12.
The main error is
(Error reading sparse file)
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
fonix232 said:
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
Click to expand...
Click to collapse
Because I'm rooted and recovery doesn't work.
I should have just done it manually instead of the flash tool method published here.
I just don't get why the system image isn't flashing now, the bootloader and radio flash work, but not the actual update. It's the correct version and all.
If the online flash tool isn't working for you, download the factory image from google's website and use the flash-all.bat to flash the device. Ensure that you modify the flash-all.bat file to not wipe data before running. This can be done by modifying one line in the file. Which is the following:
Code:
fastboot -w update image-raven-....zip
to
Code:
fastboot update --disable-verity --disable-verification image-raven-....zip
When flashing ensure that phone is in bootloader first.
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
holla420 said:
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
Click to expand...
Click to collapse
edit---
first try this method that was posted - sometimes you can save your phone this way. if that doesn't work: you can download the factory image and remove the "-w" command in the flash-all.bat file (save it properly) - this will prevent wiping your phone. you'll need adb/fastboot tool and drivers. if you need help with this just reply.
if that doesn't work, you can go this route (but it will wipe your phone) you can use the "flash" link on the factory image page here. if you press the "flash" link in blue, it will take you to the correct build at flash.android.com (click on the build version 12.0.0 (SD1A.210817.037, Nov 2021) - that's the one that worked for me.
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
V0latyle said:
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
Click to expand...
Click to collapse
no root, just unlocked bootloader i manually installed using adb
holla420 said:
no root, just unlocked bootloader i manually installed using adb
Click to expand...
Click to collapse
Use the Android Flash Tool to flash the latest December update. Don't check any of the boxes.
ayye thanks this method worked
holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Az Biker said:
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Click to expand...
Click to collapse
oh i know but this was a different message. it was in red and wouldnt boot pass the bootup screen,
coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
sounds like a user error; if it's fixed you might want to update your first post with solutions in case others have similar issues.
coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
There are definitely better and worse USB-C cables. I've successfully fully flashed my P6P connected to a powered USB-A (3.2 Gen 2) Hub in one room through a USB extension cable 10-15 feet from my computer in another room. The hub and the extension cable are reasonably "robust", and I've found them reliable, but they're not particularly reputable name brands by any means. The USB-A -> USB-C cable I have connected to that hub is from my old HTC 10, too.