[Completed] <OSM> All threads completed. (succeed 0 / failed 0) - Samsung hates me - XDA Assist

Ok, My idiot cousin managed to somehow bring up an error saying "Custom binary blocked by FRP, SECURE FAIL: KERNEL"
I've went through a few videos to fix this but they don't work for some strange reason.
(Kies- youtube.com/watch?v=XKJy9VGV1oM )
Using Kies just dosent allow me to click the Start Upgrade button and Odin3 brings up a error,
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
*Presses start*
<OSM> All threads completed. (succeed 0 / failed 0)
Model : SM-G530W

Hi FullWithLag
Thank you for using XDA Assist
You didn't specified the Manufacturer & Model of your device and, as so, it will be difficult to point you to the right XDA Section.
The below thread reports successful actions tackling this same error message you have but for the Galaxy Gran Prime
Custom binary blocked by FRP
To improve out support could you please state the Manufacturer & Model of your device ?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
FullWithLag said:
]Ok, My idiot cousin managed to somehow bring up an error saying "Custom binary blocked by FRP, SECURE FAIL: KERNEL"
I've went through a few videos to fix this but they don't work for some strange reason.
(Kies- youtube.com/watch?v=XKJy9VGV1oM )
Using Kies just dosent allow me to click the Start Upgrade button and Odin3 brings up a error,[/SIZE]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
*Presses start*
<OSM> All threads completed. (succeed 0 / failed 0)
Btw, Video will be up in 30 mins
Click to expand...
Click to collapse

Kdio said:
Hi FullWithLag
Thank you for using XDA Assist
You didn't specified the Manufacturer & Model of your device and, as so, it will be difficult to point you to the right XDA Section.
The below thread reports successful actions tackling this same error message you have but for the Galaxy Gran Prime
Custom binary blocked by FRP
To improve out support could you please state the Manufacturer & Model of your device ?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
Click to expand...
Click to collapse
Thanks, Added model number

FullWithLag said:
Thanks, Added model number
Click to expand...
Click to collapse
Hi FullWithLag
Thank you for the prompt answer
If is indeed a Grand Prime, you already have a link to start digging a solution.
If you have any further questions regarding your device, our experts at the below forum should be able to help you. Please be welcome to post over in there.
Galaxy Grand Prime Q&A, Help & Troubleshooting
Nice regards and good luck.

Related

[Q] Odin not responding

I recently rooted my samsung galaxy s2, I'm trying to put android 2.3.4 on (original firmware) from this thread http://forum.xda-developers.com/showthread.php?t=1075278
I have followed the instructions and extracted the (only) file in the .zip file. After opening Odin v1.85 and putting the md5 file in the PDA section, I put my phone into download mode and then connect it to my laptop. It looks exactly like the picture in the thread and then click start.
This is what happens in message section:
<ID:0/18> Added!!
<OSM> Enter CS for MD5
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
It stops responding at 'please wait..'
Does anyone have any idea how i can stop this because i really want to be back on original firmware.
Thanks in advance, Harry.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

[Q] .md5 files always invalid

I am trying too root my Verizon Galaxy s3, but every time I run the VRALEC.bootchain.md5 or any .md5 file in this package in ODIN. It just gives this error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> VRALEC.bootchain.tar (7).md5 is invalid.
<OSM> End...
I have re downloaded the .md5 files multiple times but I keep getting the same error. Does anyone know a fix too this?
Also link too where I am downloading the .md5's http://forum.xda-developers.com/showthread.php?t=2046439
For starters, it should end ".tar.md5" The "(7)" tells me you tried downloading this seven times and it failed six times because of that. Delete those other downloads then try again. Are you using Odin 3.07? Have you tried download from a separate computer?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
For starters, it should end ".tar.md5" The "(7)" tells me you tried downloading this seven times and it failed six times because of that. Delete those other downloads then try again. Are you using Odin 3.07? Have you tried download from a separate computer?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh haha that was the problem. I had too delete the download number. Thank you a lot for the help!
wrong thread

[Q] Rooting - yes, I searched

So I have an N8013, completely and totally stock updated with all the latest from KIES/OTA.
I just want to root it. I have searched and what I have found so far is rooting via Exynos Exploit (can't because of OTA patch) and ODIN.
But from what I understand ODIN is for rooting, CWM and flashable ROM's.
I don't want to flash any ROM's. I wan't to root, run titanium backup and triangle away.
So the quickest current method to root a stock device and leave everything else intact is....?
Temetka said:
So I have an N8013, completely and totally stock updated with all the latest from KIES/OTA.
I just want to root it. I have searched and what I have found so far is rooting via Exynos Exploit (can't because of OTA patch) and ODIN.
But from what I understand ODIN is for rooting, CWM and flashable ROM's.
I don't want to flash any ROM's. I wan't to root, run titanium backup and triangle away.
So the quickest current method to root a stock device and leave everything else intact is....?
Click to expand...
Click to collapse
As you can't run the exynos exploit you will need to use ODIN... You Aren't changing roms or kernels but obtaining root and installing a custom recovery.
If you don't want to have a custom recovery use chainfires cf-autoroot - http://forum.xda-developers.com/showthread.php?t=1957002
This will give root access but leave everything else stock. You will need to run triangle away to reset flash counter...
ultramag69 said:
As you can't run the exynos exploit you will need to use ODIN... You Aren't changing roms or kernels but obtaining root and installing a custom recovery.
If you don't want to have a custom recovery use chainfires cf-autoroot - http://forum.xda-developers.com/showthread.php?t=1957002
This will give root access but leave everything else stock. You will need to run triangle away to reset flash counter...
Click to expand...
Click to collapse
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Temetka said:
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
From what I'm looking at there it seems like the Note hasn't been detected. There should be a value in id:com box....
All it looks like it did was check the MD5 sum...
Have you connected the Note to the PC before? If not, you might require the USB drivers needed by installing KIES. Remember to exit KIES before you try flashing with ODIN though as it can cause problems...
ultramag69 said:
From what I'm looking at there it seems like the Note hasn't been detected. There should be a value in id:com box....
All it looks like it did was check the MD5 sum...
Have you connected the Note to the PC before? If not, you might require the USB drivers needed by installing KIES. Remember to exit KIES before you try flashing with ODIN though as it can cause problems...
Click to expand...
Click to collapse
framaroot
Did you forget to set your Note to 'Download Mode'?
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Temetka said:
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Man I feel like a fool, lunadomain is correct. You need to go to download mode before using ODIN...
Should've thought of that myself but because I've been doing this for years it's a step that's sort of automatic... Also shift work over 8 or 9 days straight doesn't help....
lunadomain said:
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Click to expand...
Click to collapse
Yeah, I do that and I get this screen:
Android System Recovery (3e)
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CDC-code : XAR
Successfully applied multi-CSC.
After that I fire up ODIN, plug in the tablet and nothing.
I just synced it with KIES the other day, and backed up some files so I know the drivers are installed.
Ideas?
lunadomain said:
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Click to expand...
Click to collapse
I am an idiot.
I was swapping the volume +/- buttons.
Grr.
Ok so it's rebooting.
Will check SU in a sec.
Next is nandroid backup, then some other ROM.
Probably CM10. Who knows.
So I am rooted and de-triangled.
Yay.
But I am sticking with stock. I have almost 50 notebooks in Snote and my research has revealed that Snote won't run on non-Touchwiz ROM's.
Since I can't add Touchwiz to CM10, I am sticking with it.
You don't have to use cm Roms you can always check out touchwood touchwiz based roms
Sent from my HTC One using xda premium

[guide]twrp recovery+root gt-p5200

What's up, guys? So today i'm guiding you how to install TWRP 2.8.6.0 recovery and root on your GT-P5200 device. I'm very sorry for the delays of the download links, Squadron 3 is struggling with the bugs. But as i expected, it would be here for the next couple hours after this thread is posted. But before that, i'll head to the steps and requirements.
REQUIREMENTS
-Your device with more than 30% of battery charged
-A PC(Windows would be great)
-USB Cable
-Wi-Fi connection
-Your brain and riskiness that can drive your device to Cuckoo Clock City
Now that you have whatever those are up there and the files i will post soon enough, let's get REALLY started!
1.Open the USB drivers setup on your PC and install the drives.
2.Download the root file to your device, power it off and connect it to your PC via USB cable.
*Before the third step, make sure you've downloaded EVERY file except the root file to your PC:
-Drivers setup like in step 1
-Odin 3.07
-Recovery(.tar) file
3.Run Odin and boot your device into Download mode(Power+Volume Down)
4.(Odin)Uncheck "Auto Reboot" and click "PDA", then choose the .tar recovery file.
5.Click "Start" when there's a COM thing appears under the first big box
6.Wait until it says "PASS", then disconnect your device from your PC
7.Hold power button until the screen's completely dark.
8.Boot into recovery mode(Power+Volume Up)
9.After it is in the home recovery screen, choose "Install", then go to the folder where you put the root file in.
10.Choose the root file(Make sure you remember its name)
11.Swipe, wait for it to flash, then reboot your device(There'll be a reboot button after the flashing is done, so hit it to reboot your device)
12.Enjoy rooting! Download Root Checker to verify root access from SuperSU(will be automatically installed after flashing and rebooting)
Special thanks
Laguire Sien Tiamat
Matrixians Squadron 3
Kamensek Technology Labs
That Guy
Download Links
It arrived sooner than i expected.
On your PC:
-USB Drivers: https://www.androidfilehost.com/?fid=24269982087004084
-Odin 3.07: https://www.androidfilehost.com/?fid=24269982087004070
-Recovery: https://www.androidfilehost.com/?fid=24269982087004072
On your device:
-Root: https://www.androidfilehost.com/?fid=24269982087004078
Enjoy, may the cuckoo-bazookas never be with you.
The file of recovery is invalid!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TWRP-P5200.tar.md5 is invalid.
<OSM> End...
AntoLoLLista said:
The file of recovery is invalid!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TWRP-P5200.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
Rename it to "recovery" and it'll work. Sorry for the mess, especially if your device have gone to heaven.
i have a problem... i tried doing it but it said "reset!" on the blue box

Odin Flashing Failure

Hello,
I've been trying for the past 3 days to flash the latest version of Android 9.0 on my S8+ (SM-G955U) from Verizon, since updates for it have never come.
The baseband of the firmware I've been trying to flash on my S8+ through Odin is G955USQU5DSD3, but it keeps giving me this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4920 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Needless to say, I went on a Googling spree to try to fix this problem with no avail.
It apparently has something to do with my Laptop not being able to communicate with my phone, so I tried utilizing every other port it had, didn't work.
Then tried with different cables, even bought new ones, also didn't work. Utilized all sorts of different versions of Odin3 in Administrator Mode, such as v3.13.1, v3.13.1_3B, v3.13.3 and PrinceComsy, no dice.
And yes, I have the Samsung ADB Drivers installed, SmartSwitch uninstalled and USB Debugging on.
The OS my phone is currently running is the Android 9.0 Beta (G955USQU5DRL5) that leaked back in December and I installed doing this tutorial: https://bit.ly/2T7LhD0
I've tried all sorts of other methods such as https://bit.ly/2H7V7jY, but they didn't work. Heck, I've even tried downgrading the OS to G950USQS5CRK1 and G955USQS5CRL1 but again, same error, so at least I don't think its because of the firmware.
Any suggestions?
Arcane35 said:
Hello,
I've been trying for the past 3 days to flash the latest version of Android 9.0 on my S8+ (SM-G955U) from Verizon, since updates for it have never come.
The baseband of the firmware I've been trying to flash on my S8+ through Odin is G955USQU5DSD3, but it keeps giving me this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4920 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Needless to say, I went on a Googling spree to try to fix this problem with no avail.
It apparently has something to do with my Laptop not being able to communicate with my phone, so I tried utilizing every other port it had, didn't work.
Then tried with different cables, even bought new ones, also didn't work. Utilized all sorts of different versions of Odin3 in Administrator Mode, such as v3.13.1, v3.13.1_3B, v3.13.3 and PrinceComsy, no dice.
And yes, I have the Samsung ADB Drivers installed, SmartSwitch uninstalled and USB Debugging on.
The OS my phone is currently running is the Android 9.0 Beta (G955USQU5DRL5) that leaked back in December and I installed doing this tutorial: https://bit.ly/2T7LhD0
I've tried all sorts of other methods such as https://bit.ly/2H7V7jY, but they didn't work. Heck, I've even tried downgrading the OS to G950USQS5CRK1 and G955USQS5CRL1 but again, same error, so at least I don't think its because of the firmware.
Any suggestions?
Click to expand...
Click to collapse
Not sure I can help since you have done most of the of what I was going to suggest
Has odin worked before on your PC?
Try installing latest Samsung USB drivers on your PC ( not ADB drivers)
Try a different PC
I know you said you have tried everything but in the link you posted the technique seemed a littled different than what worked for me after about 4 days of trying everything.
I am trying to find the post that I got this from but there are so many to sort thru so I'm still looking. I'll try and give credit when i find it.
Make sure odin is closed and I just close everything honestly so i know there isnt any kind of interference.
So first step is reboot to download using the volume down, bixby button and power. Once there do not press any other buttons. Simply plug in your usb cord to the phone and set it down.
Next open odin as an administrator and load the firmware files to their slots.
Once that is finished and its not thinking anymore go ahead and push volume up.
Soon as you see "COM:XX" pop up hit start and cross your fingers. I bet I tried about 10 times before it finally worked. It would fail differently so I knew I was on the right track. My model is a SM-G955U but it would not accept that firmware. I ended getting the SM-G955U1 firmware that was from a month past the last firmware my phone had on it to work.
You may have tried all and like me thought it was a load of crap but it for real worked with a little perseverence, rode a unicorn to catch a leprachaun, under a falling store on my birthday while the birthday candle was still lit and it worked!!!
Good luck bro,
FreshOut
spawnlives said:
Not sure I can help since you have done most of the of what I was going to suggest
Has odin worked before on your PC?
Try installing latest Samsung USB drivers on your PC ( not ADB drivers)
Try a different PC
Click to expand...
Click to collapse
When I installed the Beta back in December, I did it on my old desktop PC. So technically no, Odin hasn't worked before on the Laptop I'm using right now, it's in fact the first time I try to use it there. Tried the Samsung USB drivers suggestion, looks like I already had those installed.
Using a different PC seems like the only thing left for me to try, which I unfortunately can't for a while, hence why I'm trying to find other solutions so desperately
2FrEsH99 said:
I know you said you have tried everything but in the link you posted the technique seemed a littled different than what worked for me after about 4 days of trying everything.
I am trying to find the post that I got this from but there are so many to sort thru so I'm still looking. I'll try and give credit when i find it.
Make sure odin is closed and I just close everything honestly so i know there isnt any kind of interference.
So first step is reboot to download using the volume down, bixby button and power. Once there do not press any other buttons. Simply plug in your usb cord to the phone and set it down.
Next open odin as an administrator and load the firmware files to their slots.
Once that is finished and its not thinking anymore go ahead and push volume up.
Soon as you see "COM:XX" pop up hit start and cross your fingers. I bet I tried about 10 times before it finally worked. It would fail differently so I knew I was on the right track. My model is a SM-G955U but it would not accept that firmware. I ended getting the SM-G955U1 firmware that was from a month past the last firmware my phone had on it to work.
You may have tried all and like me thought it was a load of crap but it for real worked with a little perseverence, rode a unicorn to catch a leprachaun, under a falling store on my birthday while the birthday candle was still lit and it worked!!!
Good luck bro,
FreshOut
Click to expand...
Click to collapse
Hey man thanks for the suggestion, been trying to do just as you say and honestly I'm not seeing any difference in the process, it's still giving me the same error just like it would if I had done it normally, no "failing differently" every attempt.
I'm guessing that each time it fails, you unplug and restart the phone as well as close Odin for another attempt?
i cant flash anything on drl4. tried everything also.
Arcane35 said:
Hey man thanks for the suggestion, been trying to do just as you say and honestly I'm not seeing any difference in the process, it's still giving me the same error just like it would if I had done it normally, no "failing differently" every attempt.
I'm guessing that each time it fails, you unplug and restart the phone as well as close Odin for another attempt?
Click to expand...
Click to collapse
Yeah each time it failed I would hold the three button combo down until it rebooted to the download mode confirmation screen and then start the whole process over again. One thing I did forget to mention but I'm not sure if it played a part in finally being able to flash with odin is that i completely disabled my firewall so that all ports were wide open. I read somewhere about the firewall causing issues so eliminated it while I was trying to use odin.
I was messing around with the same phone some more since I posted and still had issues with odin so im not sure exactly what Im doing differently sometimes. Im ready to crash out now but I will try and take a screenshot of my drivers when I flash with odin again so you can compare it to yours.
Hope you get it figured out man. Frustrating as hell I know!!! I was ready to smash the thing into into a wall and count how many pixels there really are lol. Good luck bro!!
P.S. One last thing I completely spaced. Im on a laptop also. (Acer Nitro 5 with AMD....) I have a powered USB 3.0 hub running off a my USB 3.0 port and its only when I was plugged into the fast charging with a 3.0 cable that I finally got success. Everything Ive read says flashing thru a hub is a no no but IDGAF anymore and it worked. Try at your own risk but that does seem to be what affected my whole debauchle.
Oh my god it finally worked.
I tried doing what was in this link again: https://bit.ly/2H7B9FW , which I remember trying before and not working. In my desperation I attempted to do it again and the rest is history.
I had turned my Firewall off, in case that did anything. Good luck to anyone else having this problem!
So I just use my SS10 usb 3.1 ports for odin and that takes care of the problems with odin. not sure which odins im using. maybe prince cosmy. but changing usb ports have solved all my odin issues and flashes on the s8+. Im now operating on G955U1UES6DSI1, the latest firmware on the unlocked 955u1.

Categories

Resources