Database Info

[GUIDE] Installing CWM, Making Backup and Rooting on Galaxy R I9103

Installing CWM, Making a Backup and Rooting on the Galaxy R I9103:
All you need is:
ODIN
CWM
Superuser
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in Download mode by pressing Vol Down + Home Button + Power button simultaneously
You will see a warning for installing custom firmware, just confirm it by pressing Vol Up and enter in download mode.
Start ODIN software on your PC
Connect your Galaxy R I9103 to your PC via USB cable
Now you should see "Added" in ODIN message box, if not please check and install Samsung USB drivers again.
Click on PDA tab and browse to the ".tar" inside the CWM file
Don`t change any other option in Odin, make sure Re-Partition is not checked
Press start button and you will be done within 2 minutes and Odin will show as Pass.
Now your mobile will reboot automatically
CWM Recovery is installed.
* NOW MAKE A CWM BACKUP OF YOUR DEVICE! *
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in CWM recovery mode by pressing Power button, waiting for "Galaxy R" splash screen, and then pressing Vol Up + Home Button simultaneously
Make a Backup (Use Vol keys to scroll)
Now its time to root your device by installing Superuser
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in CWM recovery mode by pressing Power button, waiting for "Galaxy R" splash screen, and then pressing Vol Up + Home Button simultaneously
Click on to “install zip from SD card” (Use Vol keys to scroll)
Select Zip from SD card >> select the superuser ZIP file
After the ZIP is installed, reboot the device by going to main menu
Now your Samsung Galaxy R I9103 is rooted, without yellow triangle.

Thanks Mate For Full Tut

Where have you been before?!
My phone have a yellow triangle on a screen, is there any way to remove that? This is my first android phone and i did not backup and i was complete noob about all this

Nephilim983 said:
Where have you been before?!
My phone have a yellow triangle on a screen, is there any way to remove that? This is my first android phone and i did not backup and i was complete noob about all this
Click to expand...
Click to collapse
You can remove the yellow triangle by
1) Flashing back to the original Kernel
2) resetting the binary counter using USB Jig (Check Ebay for "USB Jig Samsung Galaxy S2" and Youtube for instructions)
The yellow triangle is just a warning that you have flashed insecure kernel and i see no danger in that.

Thanks for the reply
as i sad before, i didn't made a backup of stock kernel... where can i find a stock kernel for europe model? i kind a need it... i'll may be returning my phone for service check

Can use CheckFUS to download the European firmware. See this thread.
http://forum.xda-developers.com/showthread.php?t=1408610

ishafiq said:
Can use CheckFUS to download the European firmware. See this thread.
http://forum.xda-developers.com/showthread.php?t=1408610
Click to expand...
Click to collapse
Dude you are a genius
I found my firmware on it...downloading now
...but what should i do with it? use odin and pda option?

Nephilim983 said:
Dude you are a genius
I found my firmware on it...downloading now
...but what should i do with it? use odin and pda option?
Click to expand...
Click to collapse
Yes..Use the ODIN and PDA option to flash the firmware..
You mentioned you will sent phone to service.
Your binary counter will not be reset even though you flash the original firmware.
See if you can buy a USB jig. It might be handy for you always to unbrick you device, in case u brick/semi-brick it.
http://forum.xda-developers.com/showthread.php?t=1068522
You can also home make USB jig from a spare micro USB cable. See instructions here. But be careful of the terminals. http://www.youtube.com/watch?v=Rdn5GoRjhn0

ishafiq said:
Yes..Use the ODIN and PDA option to flash the firmware..
You mentioned you will sent phone to service.
Your binary counter will not be reset even though you flash the original firmware.
See if you can buy a USB jig. It might be handy for you always to unbrick you device, in case u brick/semi-brick it.
http://forum.xda-developers.com/showthread.php?t=1068522
You can also home make USB jig from a spare micro USB cable. See instructions here. But be careful of the terminals. http://www.youtube.com/watch?v=Rdn5GoRjhn0
Click to expand...
Click to collapse
Thank you so much
...will look into the usb jig thing
Thanks again

ishafiq said:
You can remove the yellow triangle by
The yellow triangle is just a warning that you have flashed insecure kernel and i see no danger in that.
Click to expand...
Click to collapse
The main function of the Yellow Triangle, is to show to Samsung Service that you did something that violates the warranty.
So Samsung Service can tell you:
"You have to pay to repair this device, you have violated the warranty."

legion1911 said:
Installing CWM, Making a Backup and Rooting on the Galaxy R I9103:
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in Download mode by pressing Vol Down + Home Button + Power button simultaneously
You will see a warning for installing custom firmware, just confirm it by pressing Vol Up and enter in download mode.
Start ODIN software on your PC
Connect your Galaxy R I9103 to your PC via USB cable
Now you should see "Added" in ODIN message box, if not please check and install Samsung USB drivers again.
Click on PDA tab and browse to the CWM file
Don`t change any other option in Odin, make sure Re-Partition is not checked
Press start button and you will be done within 2 minutes and Odin will show as Pass.
Now your mobile will reboot automatically
CWM Recovery is installed.
* NOW MAKE A CWM BACKUP OF YOUR DEVICE! *
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in CWM recovery mode by pressing Power button, waiting a second, and then pressing Vol Up + Home Button simultaneously
Make a Backup on you SD Card (Use Vol keys to scroll)
Now its time to root your device by installing Superuser
Completely Switch off your Galaxy R I9103 (wait for vibration to confirm switch off)
Switch on in CWM recovery mode by pressing Power button, waiting a second, and then pressing Vol Up + Home Button simultaneously
Click on to “install zip from SD card” (Use Vol keys to scroll)
Select Zip from SD card >> select the superuser ZIP file
After the ZIP is installed, reboot the device by going to main menu
Now your Samsung Galaxy R I9103 is rooted, without yellow triangle.
Click to expand...
Click to collapse
Hi,
I installed the CWM and made a backup of the ROM, but when I try to install the SU file (Superuser-3.0.7-efghi-signed.zip) I get this error (see attached file).
MD5 Mismatch from both locations; the MD5 I get from the files is "fc462fa0630379edbe10006b1d19d9b1"
Thanks a lot

Chapter said:
Hi,
I installed the CWM and made a backup of the ROM, but when I try to install the SU file (Superuser-3.0.7-efghi-signed.zip) I get this error (see attached file).
MD5 Mismatch from both locations; the MD5 I get from the files is "fc462fa0630379edbe10006b1d19d9b1"
Thanks a lot
Click to expand...
Click to collapse
Download the file n try again.
Sometimes it may get corrupted during initial download.
Cheers !

I tried few times but the problem don't disappear; Can anybody post the file in another server?
Thanks a lot
Enviado desde mi Galaxy R con tacatá

I've got the same error when flashed superuser over new 2.3.5 today. Surprisingly all still worked perfectly - su is installed and superuser app works.
Maybe because I didn't hard reset and I already had my previous firmware rooted.

Very useful,thanks for all!
Works perfect on my device.

Chapter said:
Hi,
I installed the CWM and made a backup of the ROM, but when I try to install the SU file (Superuser-3.0.7-efghi-signed.zip) I get this error (see attached file).
MD5 Mismatch from both locations; the MD5 I get from the files is "fc462fa0630379edbe10006b1d19d9b1"
Thanks a lot
Click to expand...
Click to collapse
astax said:
I've got the same error when flashed superuser over new 2.3.5 today. Surprisingly all still worked perfectly - su is installed and superuser app works.
Maybe because I didn't hard reset and I already had my previous firmware rooted.
Click to expand...
Click to collapse
A MD5 mismatch means your file is corrupted.
I think superuser should not be installed over another superuser. It is not clear to me why you do that.
If you have problems with superuser, please contact ChainsDD, the developer of Superuser.

DarknessDragon said:
Very useful,thanks for all!
Works perfect on my device.
Click to expand...
Click to collapse
Thank you for the feedback.

Hello.
Quick question/s
1. Will my download count increase if I make a backup of my current android version?
2. Will my warranty be voided when I install CWM in my GSR? I do not have acess to a USB jig so I can not reset the counter....
Thank you.

alister214 said:
Hello.
Quick question/s
1. Will my download count increase if I make a backup of my current android version?
2. Will my warranty be voided when I install CWM in my GSR? I do not have acess to a USB jig so I can not reset the counter....
Thank you.
Click to expand...
Click to collapse
Installing CWM with Odin does not increase the counter.
Making a backup with CWM does not increase the counter.
Installing superuser with CWM does not increase the counter.
Installing the "ardatdat custom kernel with root+overclock" with CWM does not increase the counter.
Installing a stock rom does not increase the counter.

Hi,
I installed CWM and and made a backup of the stock-rom. Then I wanted to copy the backup-file to my pc, but i cant find the clockworkmod/backup folder. There is only a clockworkmod folder and that one is empty. Its the same on the pc and in android. The weird thing is, that i can see the folder and the backup-file in CWM. So I can restore in cwm, but I want to make a backup of the backup to my pc.
Who can help?

Need some wisdom

my s6 g920f was on 5.1.1 it was running fine after I updates to 6.0.1 came up with issue emergency calls only tried all sorts to fix it but with no luck asked some expert he told me that its the modem and flashing would fix it could anyone guide me in the right direction and help me resolve this issue my phone still says emergency call only thank you

huzi7868 said:
my s6 g920f was on 5.1.1 it was running fine after I updates to 6.0.1 came up with issue emergency calls only tried all sorts to fix it but with no luck asked some expert he told me that its the modem and flashing would fix it could anyone guide me in the right direction and help me resolve this issue my phone still says emergency call only thank you
Click to expand...
Click to collapse
You could try flashing stock 6.0.1 firmware doing the following:
1) Find your firmware here ( http://www.sammobile.com/firmwares/database/SM-G920F/) and download the correct one. (Extract to desktop after)
2) Download Odin 3.10.7 ( http://odindownload.com/ ) and open.
3) Click 'AP' and select the firmware you downloaded (May take a few minutes for it to load)
4) Turn phone off, put into download mode (Hold Volume down, Home button and Power button) and continue
5) Connect phone to laptop (while in download mode) and when it says 'Added' in Odin, click start.
Only solution I could think of to fixing your problem, remember to back up all data if you're going to flash.
Also clear cache before flashing firmware. (Phone off, hold volume up and power) and select the option, then go ahead and do your thing

emcardle660 said:
You could try flashing stock 6.0.1 firmware doing the following:
1) Find your firmware here ( http://www.sammobile.com/firmwares/database/SM-G920F/) and download the correct one. (Extract to desktop after)
2) Download Odin 3.10.7 ( http://odindownload.com/ ) and open.
3) Click 'AP' and select the firmware you downloaded (May take a few minutes for it to load)
4) Turn phone off, put into download mode (Hold Volume down, Home button and Power button) and continue
5) Connect phone to laptop (while in download mode) and when it says 'Added' in Odin, click start.
Only solution I could think of to fixing your problem, remember to back up all data if you're going to flash.
Also clear cache before flashing firmware. (Phone off, hold volume up and power) and select the option, then go ahead and do your thing
Click to expand...
Click to collapse
Hi I did what U mentioned I used this version full with pit
http://samfirm.net/threads/android-6-0-1-galaxy-s6-sm-g920f-g920fxxu3dpbg-btu-03-09-2016.62/

huzi7868 said:
Hi I did what U mentioned I used this version full with pit
http://samfirm.net/threads/android-6-0-1-galaxy-s6-sm-g920f-g920fxxu3dpbg-btu-03-09-2016.62/
Click to expand...
Click to collapse
I had to flash 6.0.1 for my UK unlocked phone and all went well, try the same firmware I used: (If your phone is UK and unlocked):
http://www.sammobile.com/firmwares/download/66426/G920FXXU3DPBG_G920FBTU3DPB1_BTU/, BUT without the pit file, when I messed my phone up, I downloaded the firmware only from this link, just one file, and flashed it without pit or anything else (and everything went perfect). Might be able to help you too, if not then I'm not sure what else to do
EDIT: Also, after flashing and everything is done, you MAY have to turn on using safe mode (only on first time), I had to as it wouldn't go past the samsung logo first time after flashing. Phone does NOT actually go into safe mode, but gets it to boot correctly (Not sure why, or how it worked after, but it did)

emcardle660 said:
I had to flash 6.0.1 for my UK unlocked phone and all went well, try the same firmware I used: (If your phone is UK and unlocked):
http://www.sammobile.com/firmwares/download/66426/G920FXXU3DPBG_G920FBTU3DPB1_BTU/, BUT without the pit file, when I messed my phone up, I downloaded the firmware only from this link, just one file, and flashed it without pit or anything else (and everything went perfect). Might be able to help you too, if not then I'm not sure what else to do
EDIT: Also, after flashing and everything is done, you MAY have to turn on using safe mode (only on first time), I had to as it wouldn't go past the samsung logo first time after flashing. Phone does NOT actually go into safe mode, but gets it to boot correctly (Not sure why, or how it worked after, but it did)
Click to expand...
Click to collapse
Thank you for that but now do I turn on safe mode

huzi7868 said:
Thank you for that but now do I turn on safe mode
Click to expand...
Click to collapse
Well if you've flashed and the firmware boots up fine, then just ignore the last part.
If not, and you get the same problem as me:
Make sure phone is off. turn on as normal (but while holding the volume down button until phone fully boots), do NOT hold the power button all the way though, just volume down

emcardle660 said:
Well if you've flashed and the firmware boots up fine, then just ignore the last part.
If not, and you get the same problem as me:
Make sure phone is off. turn on as normal (but while holding the volume down button until phone fully boots), do NOT hold the power button all the way though, just volume down
Click to expand...
Click to collapse
still the same bro not working says emergency calls only

[help]Creating a back up from an Admire 2 and using it for one that its stuck in boot

Hello, I have two Galaxy Admire 2, one of them is stuck in the boot animation and the other one is working fine. I want to know how to make a backup from the phone thats working and fix the other one. I tried making a nandroid backup to an sd card and then trying to "Upgrade" the other phone in recovery mode but it did not work (signature verification error). Then I tried to flash it (I dont know if thats the correct term) with odin and the md5 file from the backup that I previously made but I got the "value invalid error". I renamed it and deleted the ".md5" but then Odin just crashed each time I choose it. I dont find any md5 file for this phone anywhere so I turn to you guys for help on making one myself or whatever I need to do to fix the other phone. I just need directions. Thanks and please explain like im five.

You can try to restore the bricked phone using Kies. You need a PC, a usb-micro USB cable and your phone in downltad mode(if you don't know how to set the phone in download mode you need to turn it on by pressing the power button, the volume down button and the home button both)

joe2k01 said:
You can try to restore the bricked phone using Kies. You need a PC, a usb-micro USB cable and your phone in downltad mode(if you don't know how to set the phone in download mode you need to turn it on by pressing the power button, the volume down button and the home button both)
Click to expand...
Click to collapse
Thanks you! I tried it but for some reason it just stays in "connecting" when I connect the phone and then like 10 minutes later it says that the phone is not responding.

It can be a problem with your drivers or with the kies version. Try to update the driver and if is still not working try to download a previous version of kies.

Please tell me i didnt kill my phone!!!

Ok so my fiancé pointed out that her phone got an update and I liked how it looked so I wanted to update mine. but I couldn't because of root. and so since I never use my root I went into super su and hit the unroot button and then my phone reset I have been in bootloop ever since. before someone suggests NO I cannot use ODIN because it wont register my phone being plugged in. YES I have the proper driver installed I triple checked and no my computer does not register the phone either. is there anything that I can do?

You didnt kill your phone!!!
The reason of bootloop is that when you press unroot in superSU it also restores unpatched stock boot.img which doesn't boot with custom recovery.
Hold power + home + volume up + volume down for 7 seconds to hard reboot your phone and enter download mode confirmation page. Press volume down to exit downloading mode and immediately hold volume up + power + home until you enter recovery. Do a factory reset.
Enter download mode confirmation page again by same method and press volume up, connect phone to your PC. Now if Odin doesn't recognize your phone then that 100% Driver or USB Cable problem. Flash latest official firmware and you should be good to go.

Aria.A97 said:
You didnt kill your phone!!!
The reason of bootloop is that when you press unroot in superSU it also restores unpatched stock boot.img which doesn't boot with custom recovery.
Hold power + home + volume up + volume down for 7 seconds to hard reboot your phone and enter download mode confirmation page. Press volume down to exit downloading mode and immediately hold volume up + power + home until you enter recovery. Do a factory reset.
Enter download mode confirmation page again by same method and press volume up, connect phone to your PC. Now if Odin doesn't recognize your phone then that 100% Driver or USB Cable problem. Flash latest official firmware and you should be good to go.
Click to expand...
Click to collapse
Nice tut! Anyway, if he still can't get recognized by PC, i suggest to try different PC, i had the same problem a while ago, my pc wouldn't recognize my phone in odin no matter what. Then i checked on my friends PC and it worked like a charm. It must be USB ports problems.

if your pc does see your phone but the odin still fails you can just use smartswitch and do emergency recovery tyoe your model number and imei in and sit back and relax and you are done

Thank YOU!!!!!!
Aria.A97 said:
You didnt kill your phone!!!
The reason of bootloop is that when you press unroot in superSU it also restores unpatched stock boot.img which doesn't boot with custom recovery.
Hold power + home + volume up + volume down for 7 seconds to hard reboot your phone and enter download mode confirmation page. Press volume down to exit downloading mode and immediately hold volume up + power + home until you enter recovery. Do a factory reset.
Enter download mode confirmation page again by same method and press volume up, connect phone to your PC. Now if Odin doesn't recognize your phone then that 100% Driver or USB Cable problem. Flash latest official firmware and you should be good to go.
Click to expand...
Click to collapse
You are a genius It was my cable that I was using... I was sitting here reading your post and I'm thinking to my self "yeah like I haven't tried that already thanks for nothing." then I saw the part about my cable and said its worth a shot. thank you so much I was so scared and frustrated about possible being without a phone... Thank you again

Xeodia said:
You are a genius It was my cable that I was using... I was sitting here reading your post and I'm thinking to my self "yeah like I haven't tried that already thanks for nothing." then I saw the part about my cable and said its worth a shot. thank you so much I was so scared and frustrated about possible being without a phone... Thank you again
Click to expand...
Click to collapse
Hey guys since my s6 SM-G920F is with tripped knox status 0x1 i can't use smartswitch for emergency recovery it stucks on 94% always with hours,what is the main reason of that i tried on other pc it is the same,my cable is ok because it charges s6 without any singl problem!sorry for interuppt in this thread like idiot but what is about smartswitch stucks always on 94%?!!!
anyone help me:crying:

vlatkonexus4 said:
Hey guys since my s6 SM-G920F is with tripped knox status 0x1 i can't use smartswitch for emergency recovery it stucks on 94% always with hours,what is the main reason of that i tried on other pc it is the same,my cable is ok because it charges s6 without any singl problem!sorry for interuppt in this thread like idiot but what is about smartswitch stucks always on 94%?!!!
anyone help me:crying:
Click to expand...
Click to collapse
just use odin to flash firmware.

vlatkonexus4 said:
Hey guys since my s6 SM-G920F is with tripped knox status 0x1 i can't use smartswitch for emergency recovery it stucks on 94% always with hours,what is the main reason of that i tried on other pc it is the same,my cable is ok because it charges s6 without any singl problem!sorry for interuppt in this thread like idiot but what is about smartswitch stucks always on 94%?!!!
anyone help me:crying:
Click to expand...
Click to collapse
Nonsense.... I used it when I trashed my EFS / Modem
Smart Switch does work, check your USB drivers and internet connection.
At the end of the process smart switch does verify a lot of thing, when your CPU from your computer is slow it will hang a long time on 94%

i can try via teamviewer to help you

SM-G920F - Bootloop during installing systemupdate

Hi, a friend of me has a Samsumg Galaxy S6 (SM-G920F), which runs continuously in a bootloop while installing a system update. It goes to 29% and then restarts himself to start installing the system update again and returns to exactly 29% again, followowd by a restart again, and again, and again ........ Attempts to start-up in recovery mode (Power, Volume +, Home) or download mode (Power, Volume -, Home) do not work. Also my PC does not recognize the phone. :crying::crying:
Does anyone have got an idea to got my phone working, or any other idea to get my phone in recovery- or download-mode?

Anyone?

The Phone boot ?

zworx said:
The Phone boot ?
Click to expand...
Click to collapse
No, unfortunately not. It keeps restarting when system update is at 29% and after the restart keeps comming back in "installing a system update" ......

Try the Pit files ans flash firware via odin

zworx said:
Try the Pit files ans flash firware via odin
Click to expand...
Click to collapse
For that I have to boot to download-mode, right? Problem is that the phone isn't booting to download-mode, recovery or sytem at all. At least not by the "normal" procedure. It constantly booting to "installing systemupdate" ......:crying:

When you connect To odin. The Phone is recognized?

You are not holding volume down+power+home long enough. Keep holding it until you get to the download mode prompt screen.

zworx said:
When you connect To odin. The Phone is recognized?
Click to expand...
Click to collapse
No, the phone is not recognized by ODIN. Drivers on PC are oke, because my S7 edge and my girlfriends S5 are recognized by ODIN ......

benjamen50 said:
You are not holding volume down+power+home long enough. Keep holding it until you get to the download mode prompt screen.
Click to expand...
Click to collapse
I'm holding these buttons for more then 60 seconds ....... but nothing seems to be working .....

Were the volume down, home and power button functioning fine before hand?
Looks like one of the buttons don't work.

benjamen50 said:
Were the volume down, home and power button functioning fine before hand?
Looks like one of the buttons don't work.
Click to expand...
Click to collapse
As far as I know, buttons worked fine before. I guess phone is brikked and not much I can do about it anymore ....... :crying::crying:

I'm guessing you already tried running it flat? There is still a chance download mode is bootable once you get the phone to go off due to flat battery.
This phone is a pretty bad brick, I've fixed up to DRK corrupted but this one seems unrecoverable.

benjamen50 said:
I'm guessing you already tried running it flat? There is still a chance download mode is bootable once you get the phone to go off due to flat battery.
This phone is a pretty bad brick, I've fixed up to DRK corrupted but this one seems unrecoverable.
Click to expand...
Click to collapse
Yes, I already let the phone running empty battery. But as soon as I plug in the powercord, the same process starts over and over again .......

And with adb ?

same trouble
Hi everybody, i had the same trouble on my G-920F (S6), and the only strange way i've find, is to keep button volume up AND down and power, once it's turn off for rebooting, i've add the home button pressed.
finally by that way it show me the recovery menu. Another time it show me the download menu !!??
Well but now my trouble is that i cannot succeed to flash correctly the last official samsung firmware using Odin .
i've tryed to erase nand (i know i should not), but without succeed.
so i'm looking for pit file, and i will try an older firmware.
so try with the volume up and down and power, in case of it works like for me