I've never rooted a phone before and was curious to get CM11 on my Galaxy S5. Since the installer isn't compatible with the S5, I figured I'd try rooting it. When I first got the phone I tried it (back in April) and it didn't work so I forgot about it and didn't try again until the other day. I looked it up on youtube and followed the instructions to the letter not missing a thing. Like I said earlier, I don't know much about rooting so the first time I tried I could have easily messed it up. Anyways, I downloaded what the video said, went through it step-by-step not missing anything and when I went to boot it up after doing whatever I was doing in Odin, unlike the guy in the video whose phone loaded up the Samsung Loading screen that had no text on the top left, mine did. I waited for a minute before retrying, following it to the letter and it did it again, so I looked in the comments. Some others were having problems and said they had to get the original ROM and do it from that to get the phone to boot. I did that, phone booted fine and here I am without a rooted phone and with no CM11.
I'm asking what I did wrong/what's going on with my phone/why can't I root it/am I just an idiot?
Root the stock version, I believe Chainfire's auto root works for the S5 (verify that before flashing anything).
Once you're rooted, install a custom recovery (ie... CWM, TWRP, or Philz) then flash the CM11 ROM you want to run.
Stryke_the_Orc said:
Root the stock version, I believe Chainfire's auto root works for the S5 (verify that before flashing anything).
Once you're rooted, install a custom recovery (ie... CWM, TWRP, or Philz) then flash the CM11 ROM you want to run.
Click to expand...
Click to collapse
Once I put my phone into download mode in the upper left hand corner it reads
(red)ODIN MODE
(white - ) PRODUCT NAME:SM-G900P
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOCK WARRANTY VOID: 0x1 (4)
(in gray) QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
(red)UDC START
Going into odin - went to Chainfires website downloaded the SM-G900P file and loaded up odin
PDA -> The file that came with the download
Message box:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
now I'm hitting start -
on my phone
(blue)RECOVERY BOOTING....
(red)RECOVERY IS NOT SEANDROID ENFORCING
(yellow)Set Warranty Bit: Recovery
in the upper left hand of the Samsung Galaxy S5 Loading screen
isn't doing anything ( this is what happened last time )
DJames609 said:
Once I put my phone into download mode in the upper left hand corner it reads
(red)ODIN MODE
(white - ) PRODUCT NAME:SM-G900P
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOCK WARRANTY VOID: 0x1 (4)
(in gray) QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
(red)UDC START
Going into odin - went to Chainfires website downloaded the SM-G900P file and loaded up odin
PDA -> The file that came with the download
Message box:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
now I'm hitting start -
on my phone
(blue)RECOVERY BOOTING....
(red)RECOVERY IS NOT SEANDROID ENFORCING
(yellow)Set Warranty Bit: Recovery
in the upper left hand of the Samsung Galaxy S5 Loading screen
isn't doing anything ( this is what happened last time )
Click to expand...
Click to collapse
Try using a different usb port or cable, if that doesn't fix the issue find the drivers for your device (can probably be found here on XDA or on your manufacturers/carriers sites) uninstall the current drivers if installed and install the ones you just downloaded and try again.
A good way to see if your drivers are functional is trying to connect to ADB with your device.
Related
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
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
Samsung S7 SM-930F. Rooted and running Lineage0S 15.1 for past year without problem. I've noticed over the past few weeks that it had rebooted when charging overnight.
Now it only loads to the Samsung screen. I've tried restarting it, taking the SD card out but the only screen I can access apart from the logo screen is the download mode. It won't turn off using the power button either.
I've used Odin 3.12.3 and a few other versions along with different cables and PC's but every time I try to install a stock rom (tried a few) Odin gets to this stage and nothing else happens..
<ID:0/003> Added!!
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Do you think there is a fault with one of the chips on the system board?
alfarom said:
Samsung S7 SM-930F. Rooted and running Lineage0S 15.1 for past year without problem. I've noticed over the past few weeks that it had rebooted when charging overnight.
Now it only loads to the Samsung screen. I've tried restarting it, taking the SD card out but the only screen I can access apart from the logo screen is the download mode. It won't turn off using the power button either.
I've used Odin 3.12.3 and a few other versions along with different cables and PC's but every time I try to install a stock rom (tried a few) Odin gets to this stage and nothing else happens..
<ID:0/003> Added!!
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Do you think there is a fault with one of the chips on the system board?
Click to expand...
Click to collapse
This model is really easy to flash and shouldn't give too many issues. The latest Odin for this model is 3.13.1 so try that first.
I've noticed myself going back to any ROM after Lineage can sometimes cause problems.
Got TWRP installed? Then put the ROM on the SD card and flash with TWRP
Want to flash stock? then use UK BTU unbranded flash with Odin,
To turn off when in download mode >>>>power+home+volume down. Once the phone goes off power+home+volume up to boot into TWRP is thats what you want.
I've tried the latest ODIN with the same results. The phone won't shutdown no matter what I try. Power + Home + Volume Up doesn't boot into twrp either (which is already installed). Just brings me to the screen where I can continue, which brings the logo screen up or press Volume Up to get to Downloading screen. The only way it turns off is by running the battery down.
I can't access the SD card either. The phone is recognised by ODIN but doesn't show up on the PC at all.
alfarom said:
I've tried the latest ODIN with the same results. The phone won't shutdown no matter what I try. Power + Home + Volume Up doesn't boot into twrp either (which is already installed). Just brings me to the screen where I can continue, which brings the logo screen up or press Volume Up to get to Downloading screen. The only way it turns off is by running the battery down.
I can't access the SD card either. The phone is recognised by ODIN but doesn't show up on the PC at all.
Click to expand...
Click to collapse
Ok, I've been here too but before you get the hardware looked at can i just check the following which may or may not make a difference. I know some questions may sound stupid but as i can't see the phone, please answer.
Is FRP lock on or off?
Is OEM enabled
Does holding down just the power button turn the phone off (i've never once not been able to force restart any android device when stuck on download screen).
Try a combination of different buttons to force start for example AND in this order
* home+volume down+power
* volume up+power (only)
* home+power (only)
If any of these work, as soon as the phone shuts off release power then quickly press volume up+home+power
Does Odin "add" the phone in download mode?
Before you press "volume Up" to continue to download mode, what text appears in the top left of the screen, please post a picture here if you can.
What exact firmware are you trying to flash and where did you get it from?
Is the firmware your trying to flash in 4 parts or just one .md5 file?
Do you know how to use SamFirm Tool?
Do you have Smartswitch running or installed on your PC?
Do you have antivirus running?
Also re flash TWRP via odin
Sorry for the interrogation but i need to eliminate possible causes.
Is FRP lock on or off?
Is OEM enabled
Don't know as I can't get into phone now.
Does holding down just the power button turn the phone off (i've never once not been able to force restart any android device when stuck on download screen).
Try a combination of different buttons to force start for example AND in this order
* home+volume down+power
* volume up+power (only)
* home+power (only)
Nothing seems to turn the phone off
Does Odin "add" the phone in download mode?
Yes, it shows up in Odin
Before you press "volume Up" to continue to download mode, what text appears in the top left of the screen, please post a picture here if you can.
I think it just has the standard text in the top left but I'll check when I get to the phone, shortly.
What exact firmware are you trying to flash and where did you get it from?
Is the firmware your trying to flash in 4 parts or just one .md5 file?
Tried various firmwares (all 4 parts) without success
Do you know how to use SamFirm Tool?
Do you have Smartswitch running or installed on your PC?
Do you have antivirus running?
Also re flash TWRP via odin
Haven't tried the SAMFIRM tool yet
SmartSwitch wouldn't work when I tried it.
Only AV running is Microsoft's built in product.
alfarom said:
Is FRP lock on or off?
Is OEM enabled
Don't know as I can't get into phone now.
Does holding down just the power button turn the phone off (i've never once not been able to force restart any android device when stuck on download screen).
Try a combination of different buttons to force start for example AND in this order
* home+volume down+power
* volume up+power (only)
* home+power (only)
Nothing seems to turn the phone off
Does Odin "add" the phone in download mode?
Yes, it shows up in Odin
Before you press "volume Up" to continue to download mode, what text appears in the top left of the screen, please post a picture here if you can.
I think it just has the standard text in the top left but I'll check when I get to the phone, shortly.
What exact firmware are you trying to flash and where did you get it from?
Is the firmware your trying to flash in 4 parts or just one .md5 file?
Tried various firmwares (all 4 parts) without success
Do you know how to use SamFirm Tool?
Do you have Smartswitch running or installed on your PC?
Do you have antivirus running?
Also re flash TWRP via odin
Haven't tried the SAMFIRM tool yet
SmartSwitch wouldn't work when I tried it.
Only AV running is Microsoft's built in product.
Click to expand...
Click to collapse
Ok, So Sanfirm Tool is easy to use and gets the files from Samsung servers much faster than Sammobile.
If Odin sees the phone i would first suggest flashing the latest TWRP for OREO again via Odin and hopefully you can boot into TWRP recovery and see whats actually still on the device. If you can get into TWRP then we're on our way
With regards to not being able to turn the phone, how long are you holding volume down+home+power for?
Also SD card....can you place it in your pc to drag and drop files to it?
Uninstall smartswitch as a precaution but ensure Samsung USB drivers are installed.
Odin sees the phone but I can't flash Twrp to it. It just stops on the initialization screen. Also, I can't access the phone through the PC even though you hear it connect and shows up in Odin.
I've tried every button combination I can think of and held them down for minutes at a time.
I'll try the SanFirm tool next.
I think I am using the wrong model and region in SamFirm. I've entered SM-G930 and XA but get this message
Could not fetch info for SM-G930/XA. Please verify the input or use manual info
I've found this link for UK Region..
United Kingdom: ---> BTU, BTC, CPW, EVR, H3G, O2U, ORA, OXA*, TMU, TSC, VIR, VOD, XEU
Just realised I should have been using SM-G930F. I'm downloading the H3G one now but should it be another if the phone was previously locked to Plusnet in the UK?
Downloaded firmware using SM-G930F and H3G but Odin still stops at Initialization.
Also, FTP Lock is Off according to the phone. Pic Attached..
Do you think this phone has a hardware issue, maybe a problem with the eMMC chip?
alfarom said:
Downloaded firmware using SM-G930F and H3G but Odin still stops at Initialization.
Also, FTP Lock is Off according to the phone. Pic Attached..
Click to expand...
Click to collapse
BTU is UK unbranded
It may have a hardware fault yes but unless it been dropped hard or got wet etc it's very rare for it to be hardware related
Just tried BTU with same result.
alfarom said:
Just tried BTU with same result.
Click to expand...
Click to collapse
Yeah i been chatting to a mate, you absolutely need to reboot into download mode every time a flash fails or it will get stuck at initialization. Is this the error you keep getting?
Also have you tried different usb port? and are you running Odin as Admin?
I can reboot into download mode without any problem but can't turn the phone off at all. Volume Down and Power buttons restarts as far as the logo screen and that's about it as far as I can do anything.
alfarom said:
I can reboot into download mode without any problem but can't turn the phone off at all. Volume Down and Power buttons restarts as far as the logo screen and that's about it as far as I can do anything.
Click to expand...
Click to collapse
Ok so that what i needed to know, if you can only reboot into download then yes that's what happens the phone just won't go off.
So what error are you getting in Odin when you attempt to flash, can you post a pic of what files are going where in Odin before you flash?
All Odin does is stop when it comes to INITIALIZATION. Nothing happens after that no matter how long I leave the phone connected. I've added the BL, AP, CP and CSC files into the appropriate boxes in ODIN. It never comes up with FAIL or any other sign of anything happening.
alfarom said:
All Odin does is stop when it comes to INITIALIZATION. Nothing happens after that no matter how long I leave the phone connected. I've added the BL, AP, CP and CSC files into the appropriate boxes in ODIN. It never comes up with FAIL or any other sign of anything happening.
Click to expand...
Click to collapse
Are you using the HOME_CSC file or CSC in Odin?
Have you also got a firmware in .md5 format? (one file?)
Swapped usb cables and ports on pc?
Tried HOME_CSC and just CSC. Haven't got an .md5 file. I couldn't find one. Swapped cables and pc.
Trying to flash a TWRP tar file using the AP option just stops at INITIALIZATION.
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.
Sim Unlocked S8+. Is it possible to flash unbranded firmware & XAA CSC without root?
Hello all. Thanks to all the developers spending countless hours and sharing with us. It's been some time since I have rooted and installed custom roms on an android (circa Evo Shift 4G times).
I've discovered this post:
https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
It makes it seem as if it is possible to install the SM-G955U1 using Odin without issue. I would like to keep my phone unrooted, standard bootloader, knox enabled and allow for OTA updates.
My question is as I am currently in India would there be an advantage to using a CSC for the region over XAA? (I'll be in India for another 45 days, then heading to Georgia, then Czechnia). I've seen the posts about flashing CSC's to enable WiFi calling and VoLTE, but I'm assuming that might be due to using a branded firmware phone rather than unbranded?
My primary aim is to eliminate all of the T-Mobile bloat and provisioning apps in hopes that it would improve my LTE speeds. Currently they're generally below what Airtel is rating my connection at (rated for 4-7 mbps, avg 1-3mbps). I notice that my battery life is just terrible ever since I left the USA and started using the local cell carriers in SE Asia.
I noticed this posting about opening up additional LTE bands on the phone, but need to research which bands in India are utilized, vs what my phone allows.
https://forum.xda-developers.com/galaxy-s8+/how-to/qualcomm-phones-add-lte-band-using-qxdm-t3785458
Any input or direction would be appreciated.
Does TMB/XAA/TMB (below) indicate that the phone has been sim unlocked from TMB's network? Would flashing unbranded firmware SM-G955U1 or custom CSC mess the sim unlocking up?
Model: SM-G955U
One UI: 1.0
Baseband: G955USQU7DSL3
Service provider SW ver: SAOMC_SM-G955U_OYN_TMB_PP_0026
98895a3739595a3653
TMB/XAA/TMB
?
Curious, what are the differences between CSC XAA & XAS? I read in one place the XAS might be a developer build?
From a reddit post 2 years ago:
"Samsung is consolidating its firmwares into multi-CSC firmwares. All of the G950U1 models use the same multi-CSC firmware, OYM. When you flash a multi-CSC that includes your existing CSC, it doesn't actually change the CSC, regardless of which variant of OYM you flash. So if your phone was already using XAA and you try to flash TMB, you'll keep XAA because both are included in OYM. Use Phone Info to check what your active CSC is. It will more than likely be XAA with TMB listed among the available CSCs."
https://www.reddit.com/r/GalaxyS8/comments/6jvb3b/all_g950u1_firmware_downloads_are_xaa_unlocked/
My active CSC is TMB, how can I change my CSC to XAA instead after flashing firmware "Galaxy S8+ SM-G955U1 XAA Unknown G955U1UEU7DSL5"?
When I try to use any secret codes in the samsung dialer eg: *#1234*# or *#272*imei# etc, nothing happens. If I hit the dial button it pops up a message stating: "Running USSD code" then provides error message "connection problem or invalid MMI code."
Going to flash the firmware later tonight as soon as it downloads over my tethered connection.
Having issues with Odin failing immediately.
FROM ODIN
<ID:0/005> Added!!
<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/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5933 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Here is the info from my bootloader in Download Mode
Carrier: TMB
RPMB fuse blown
RPMB PROVISIONED
Current Binary: Samsung Official
FRP Lock: OFF
Warranty Void: 0x0
Qualcomm Secure Boot: Enabled
RP SWREV: B7(2,1,1,1,1) K6 S7
Secure Download: Enabled
Click to expand...
Click to collapse
Prerequisites
Held down Power + Vol Down + Bixby to reboot into Download Mode
Used SamFirm to download SM-G955U1_1_20200131184615_sapzy2x6yh_fac
Uninstalled Smart Switch
Using USB 2.0 slot (also tried USB 3.0 slot)
Do not have original data cable but purchased a high quality data cable.
Odin x3.14.1 3B_Patched (also tried un-patched Odin with same result)
Samsung USB Drivers v1.7.23.0
Removed Google Accounts
No Samsung Account
FRP Lock: OFF
Disabled Screen Lock
Click to expand...
Click to collapse
Any ideas here? Could not using the stock usb data cable really be preventing me from progressing with the firmware flash??!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xFilthyxJesusx said:
Having issues with Odin failing immediately.
Any ideas here? Could not using the stock usb data cable really be preventing me from progressing with the firmware flash??!
Click to expand...
Click to collapse
You will need ver 7 ( or higher ) binary ( bootloader ). 5th number from right of firmware name.
Failing at setup connection on odin
Make sure ( according to your screen shot ) odin sees your phone. Should shows up upper left show up as com port in box that says ID:COM
Be in download mode
Other things you can try:
https://forum.xda-developers.com/galaxy-s9/help/s9-u1-flash-instant-odin-error-t4016919
Thank you for your reply.
I am using Intel system.
In screen shot I had unugged device after fail. Prior Odin had com port 05, and there was a blue box.
Have tried plug and unplug. May need a new data cable. Will try and find another Intel system to use.
Both phone and firmware I am flashing are boot loader 7
Current: G955USQU7DSL3
Flashing: G955U1UEU7DSL5
Would flashing combination file (BL5 Nougat) then upgrading to BL7 maybe work better? Will try that if I cannot get this to work with another data cable and pc
xFilthyxJesusx said:
Thank you for your reply.
I am using Intel system.
In screen shot I had unugged device after fail. Prior Odin had com port 05, and there was a blue box.
Have tried plug and unplug. May need a new data cable. Will try and find another Intel system to use.
Both phone and firmware I am flashing are boot loader 7
Current: G955USQU7DSL3
Flashing: G955U1UEU7DSL5
Would flashing combination file (BL5 Nougat) then upgrading to BL7 maybe work better? Will try that if I cannot get this to work with another data cable and pc
Click to expand...
Click to collapse
Combination and stock firmware work in the same repects with bootloader version number. ie if you on ver 7 bootloader you cannot flash anything lower ( 6 and under ).