I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Image lives at: dropbox.com/s/bfzetvhnb00mx69/2014-05-02%2015.58.11.jpg
andyshannon3 said:
I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Click to expand...
Click to collapse
Philz Touch doesn't root your phone, CF-AutoRoot does. You can find it here: http://forum.xda-developers.com/showthread.php?p=51421053
andyshannon3 said:
I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Click to expand...
Click to collapse
I used Odin v3.07 to root Chainfires root and then I used the Philz recovery tar file to get the recovery... maybe you can Odin back to stock with Odin v3.07 and try that method with a fresh start.
I know its kinda late for this answer but what you have to do is disable the auto reboot option , now hit start when it shows you pass on the odin screen you can manually remove the battery and proceed to power the phone into the recovery mode and its done
I have the same problem as well. Have you found any solution to this?
Zororasto said:
I have the same problem as well. Have you found any solution to this?
Click to expand...
Click to collapse
You need to disable the auto-reboot option in Odin before installing the custom recovery. If you do not do this, android will reboot normally which will cause the custom recovery to be replaced by the stock recovery.
So disable auto-reboot, when the Odin status bar is full and Odin says PASS, you have to manually boot your phone into recovery (home, vol+, and power) and immediately install the latest supersu zip
dynospectrum said:
Philz Touch doesn't root your phone, CF-AutoRoot does.
Click to expand...
Click to collapse
Technically correct but misleading and off-point to the point of being incorrect. CF-autoroot is usually dependent on having a specific version of android. However, on any version of android, you can install a custom recovery (TWRP or Philz) with Odin, immediately boot into that recovery (without first booting into normal android) and flash the latest supersu zip file. This method is safe, easy, and universal in the fact that it works with any version of android.
Related
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Informatic_dev said:
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Click to expand...
Click to collapse
did you try a different usb port? also I'd try heimdall and see if that works and sees your phone. which stock odin package are yup trying to flash?
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Informatic_dev said:
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Click to expand...
Click to collapse
You should have read a little but noe I'm going to tell you what to do head over to droid styles guide here http://forum.xda-developers.com/showthread.php?t=1238070 now download cwmfixedforcm7.zip and atlas 2.2.zip and put it on your computer now download this. http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip put it on the root of your SD card now power on your computer run Odin as AMINISTRATOR put the atlas.zip in the pit space in Odin check mark beside the place that said PDA and put the cwm.zip there now put your phone in download mode hook it to the computer and when Odin recognizes it press start wait for it to say PASS it may take up to 20min when its done reboot the while while holding the volume buttons, Home key button, power button when you see the Samsung logo flash twice let go of the volume up button and the home key button continue holding volume down button and the power button you should now boot into a menu with blue text now release the buttons navigate with the VOLUME BUTTONS AND THE POWER BUTTON TO SELECT go to install zip from SD now choose zip from SD navigate to the .zip I told you to put on your SD card select it then you will see a bunch of no's and a yes select yes AFTER its finished press go back then press reboot system now ONCE IT REBOOTS CONGRATS YOUR ROOTED AND SHOULD HAVE SUPERUSER!!!
Sent from my SCH-I500 using Tapatalk 2
I managed to get it working, maybe the SU.tar was corrupted as it worked this time. Thanks.
So, I was off attempting to root my phone with CF-Auto-Root. I have an S6 Edge from T-mobile, and so I selected the one for the SM-G925T, which was my phone's model number. On using Odin, following all the steps from the youtube video titled "How to Root Galaxy S6 or S6 Edge!" by Max Lee at High on Android (Sorry I can't post a link, I'm too new) Anyway, once I got to the part where I was rooting, upon restart, my phone seems to be locked in the startup screen. In the upper right corner in red, it says "Recovery is not seandroid enforcing" other than that, the screen is black with some white text that says "Samsung / Galaxy / S6 Edge / Powered By / Android" With each "/" representing a line break.
When I hold down the power button, nothing happens. Did I just ruin this phone, or is there something I can do to fix it? (I fear I may have unplugged it too early... I waited ~5 minutes before I figured it was totally frozen and that I would need to do something. Hopefully that didn't ruin the root...)
Thanks for any help!
Disclaimer, I'm no expert.
First, take a couple of deep breaths, your phone is not lost to the world.
Sounds like your stock firmware is kicking up a fuss about being booted from a non-samsung recovery.
There are several threads about this particular error already, but the general gist seems to be to get your phone back into Download Mode (power button + volume down + menu button) and flash your stock firmware back in.
That will probably remove root and clear your data though.
Do a Google for "Recovery seandroid enforcing s6" if you havn't already
Sent from my SM-G925I using Tapatalk
This is quite normal. The same thing happened to me.
If you've got as far as flashing TWRP via Odin then it should just be a matter of booting into recovery. As you're in a place where your phone will keep trying to boot even if you power off, it's just a matter of timing.
To shut the phone down you need to hold Power and Vol Down for about 10 seconds. What you'll find though is the phone will boot up again straight away and show you the annoying Seandroid screen so what you need to do is power off the phone then as soon as the screen goes black hit Vol Up, Home and Power. Keep holding them and instead of booting to Seandroid it should boot to TWRP. If you get Seandroid just try again. You need to get those buttons pressed as soon as the phone starts to boot-cycle though.
Once you're in TWRP you can install root, and then install the kernel which will allow the phone to boot normally again.
Good luck!
Mischala said:
Disclaimer, I'm no expert.
First, take a couple of deep breaths, your phone is not lost to the world.
Sounds like your stock firmware is kicking up a fuss about being booted from a non-samsung recovery.
There are several threads about this particular error already, but the general gist seems to be to get your phone back into Download Mode (power button + volume down + menu button) and flash your stock firmware back in.
That will probably remove root and clear your data though.
Do a Google for "Recovery seandroid enforcing s6" if you havn't already
Sent from my SM-G925I using Tapatalk
Click to expand...
Click to collapse
Yeah, I was just googling around to see if anyone had more luck. I'm currently downloading 5.1.1 (I didn't know that Samsung changed the bootloader, so I'll have to wait for that root to come out. Oh well...) Hopefully it goes well I'll update with results once it's done downloading!
The s6 is weird. This is the first Samsung phone that when using cf-auto root it soft-bricks my phone. You have to flash recovery through odin, then root through recovery for it to work. Dont forget the no sleep fix while you're there.
Here are the steps and links:
1. Download ODIN v 3.10.6 from http://forum.xda-developers.com/show....php?t=2711451 and extract it to a folder.
2. Download TWRP v2 by eousphoros (Odin Flashable Version) from https://mega.co.nz/#!aQhTnQRR!k-M-j9...swZO3CWYi0mMtI
3. Download the latest SuperSu Beta from http://forum.xda-developers.com/apps...v2-05-t2868133 and transfer it to your internal storage on the phone.
4. Download Deep-Sleep flashable fix from http://forum.xda-developers.com/show...7&postcount=56 and transfer it ot your internal storage on the phone.
5. Put your phone into Download Mode. Power Off, then hold Power+Home+VolDown. At the warning press VolUp to continue.
6. Connect your phone to your computer via the USB cable.
7. Launch ODIN.
8. You will see the text Added! in the status panel (left side).
9. Checkmark the box beside AP and then click on AP.
10. Browse to the TWRP tar.md5 file you downloaded earlier and select it.
11. Wait a few seconds for MD5 check to finish successfully.
12. Press Start. You will see the progress bar at the top and when it's complete status window will have message "All Threads Complete (Succeed 1, Failed 0)".
13. Boot into TWRP (Button combination Power+Home+VolUp) and then flash/sideload SuperSu beta zip and then the deep sleep fix zip that you have on internal storage.
14. Reboot to system. Congratulations, your phone is now rooted.
Click to expand...
Click to collapse
H00pyFr00d said:
This is quite normal. The same thing happened to me.
If you've got as far as flashing TWRP via Odin then it should just be a matter of booting into recovery. As you're in a place where your phone will keep trying to boot even if you power off, it's just a matter of timing.
To shut the phone down you need to hold Power and Vol Down for about 10 seconds. What you'll find though is the phone will boot up again straight away and show you the annoying Seandroid screen so what you need to do is power off the phone then as soon as the screen goes black hit Vol Up, Home and Power. Keep holding them and instead of booting to Seandroid it should boot to TWRP. If you get Seandroid just try again. You need to get those buttons pressed as soon as the phone starts to boot-cycle though.
Once you're in TWRP you can install root, and then install the kernel which will allow the phone to boot normally again.
Good luck!
Click to expand...
Click to collapse
I'm confused... When I use the Vol Down + home + power button, it boots into the normal (as far as I can tell) samsung bootloader thing (at least, the one from 5.1.1) So I don't think I have TWRP installed even. Anyway, it shows up in Odin, so how do I start loading everything? In the Files [Download] section in Odin, I see boxes that say BL, AP, CP, and CSC. Which of those do I select to load up the full backup that I got? (It's about 4GB of data with an .iso, if that makes a difference)
Edit: Basically, I have no MD5 files in the download. (I got it off high off android)
KaminKevCrew said:
I'm confused... When I use the Vol Down + home + power button, it boots into the normal (as far as I can tell) samsung bootloader thing (at least, the one from 5.1.1) So I don't think I have TWRP installed even. Anyway, it shows up in Odin, so how do I start loading everything? In the Files [Download] section in Odin, I see boxes that say BL, AP, CP, and CSC. Which of those do I select to load up the full backup that I got? (It's about 4GB of data with an .iso, if that makes a difference)
Edit: Basically, I have no MD5 files in the download. (I got it off high off android)
Click to expand...
Click to collapse
You will not be able to flash anything in odin if youre not in download mode. If you have trouble getting in download mode, you're doing it wrong. Turn off phone, then press Vol down + power + home and dont release any of those until you see something unusual, such as an android robot. While using odin, NEVER EVER load anything in any other option than AP. As far as backup goes, I don't know what backup you made but you don't restore it though odin thats for sure, you will hardbrick your phone.
polish_pat said:
You will not be able to flash anything in odin if youre not in download mode. If you have trouble getting in download mode, you're doing it wrong. Turn off phone, then press Vol down + power + home and dont release any of those until you see something unusual, such as an android robot. While using odin, NEVER EVER load anything in any other option than AP. As far as backup goes, I don't know what backup you made but you don't restore it though odin thats for sure, you will hardbrick your phone.
Click to expand...
Click to collapse
I can get into the stock Samsung download mode (light blue screen, it says downloading on it..) On the links posted in post number five, none of them worked for me... The thing is, I was trying to load TWRP while my phone was updated to 5.1.1 if that makes any difference... Anyway, it appears that the stock download mode is working, so what do I do now? (From what I've read, I can't really put TWRP on it??)
Alright, I got it working! (Hopefully this will help others get redirected to the right thread, since it took me a while to find this!) Depending on whether or not I am allowed to post links at this point, I may need to post repeatedly here, and I apologize for that, but it's all with the best intents in mind!!!
Anyway, if you do what I did, which is this:
No backup, attempt to root GS6 Edge (SM-G925T from T-mobile) with the 5.0.2 CF auto root, while your phone has already been updated to 5.1.1. It puts you in a boot loop, which really isn't fun, because it doesn't appear that you can fix it... Anyway, I went to the thread, which you can find here: http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002 . Anyway, what you need to do is boot into download mode (which you can still do when you are in the boot loop, just hold the volume down + home + power buttons until the device boots into the downloader screen. At that point, you use Odin, and install the file called "OF6 Stock Recovery". That should fix it! Anyway, go to the thread above, it helped me a TON!!!
This isn't really rocket science. Yes, there are different root options for 5.0.1 and 5.1.1 but this is clear in the OP when you decide which root to use.
The only things you need to consider are, if you flash a custom recovery (not the 'download mode' that you use for Odin) then the stock rom won't boot. It's not bricked but you just need a custom kernel. Therefore the steps are:
Download and copy the custom kernel and root to the phone
Boot into Download mode -Vol down, home, power - and flash recovery (TWRP etc) via Odin
Boot into TWRP custom recovery - Vol up, home, power - and flash kernel and root
Reboot
Profit
It really is just a matter of reading the steps carefully and doing exactly what they tell you.
My Rogers S6 edge W8 got an OTA OG2 yesturday so I went back to stock to get the new update. Now I want to root back but somehow the previous method of installing TWRP in odin, then flash SU and nosleep fix just doesnt work...actually only the recovery doesnt want to install. Odin tells me everything was a success, the phone seems to have installed TWRP but when I boot into recovery, it goes back to stock again.
Any ideas what could have gone wrong?
Also please dont suggest usuing CF-Auto root because it brick my phone every single time.
Here are the instructions I followed, the first time the process went without a hitch.
1. Download ODIN v 3.10.6 from http://forum.xda-developers.com/show....php?t=2711451 and extract it to a folder.
2. Download TWRP v2 by eousphoros (Odin Flashable Version) from https://mega.co.nz/#!aQhTnQRR!k-M-j9...swZO3CWYi0mMtI
3. Download the latest SuperSu Beta from http://forum.xda-developers.com/apps...v2-05-t2868133 and transfer it to your internal storage on the phone.
4. Download Deep-Sleep flashable fix from http://forum.xda-developers.com/show...7&postcount=56 and transfer it ot your internal storage on the phone.
5. Put your phone into Download Mode. Power Off, then hold Power+Home+VolDown. At the warning press VolUp to continue.
6. Connect your phone to your computer via the USB cable.
7. Launch ODIN.
8. You will see the text Added! in the status panel (left side).
9. Checkmark the box beside AP and then click on AP.
10. Browse to the TWRP tar.md5 file you downloaded earlier and select it.
11. Wait a few seconds for MD5 check to finish successfully.
12. Press Start. You will see the progress bar at the top and when it's complete status window will have message "All Threads Complete (Succeed 1, Failed 0)".
13. Boot into TWRP (Button combination Power+Home+VolUp) and then flash/sideload SuperSu beta zip and then the deep sleep fix zip that you have on internal storage.
14. Reboot to system. Congratulations, your phone is now rooted.
Click to expand...
Click to collapse
Did you uncheck Auto Reboot when you flash the recovery in Odin?
There is no such option with the newer odin
Sent from my SM-G925W8 using Tapatalk
I have heard that this update also breaks ping-pong root. We'll have to wait and see if those are updated
Ok, i found a fix. The problem was when i flashed recovery with odin, the custom recovery was overwritten as soon as the phone would boot back to system. I was able to keep TWRP installed by pressing Volume Up + Power + Home the second the recovery installation was finished and kept holding until Samsung Galaxy S6 edge logo appeared, then it booted me right in TWRP where I was able to flash SU and Sleep Fix.
I am using 3.10.6 and it has the option on one of the tabs on the left side. Yea, that's what I meant not to let it auto reboot. Reboot by holding Volume Down + Power + Home. When the screen goes back, hold Volume Up + Power + Home to boot into Recovery.
ShermanCheng said:
I am using 3.10.6 and it has the option on one of the tabs on the left side. Yea, that's what I meant not to let it auto reboot. Reboot by holding Volume Down + Power + Home. When the screen goes back, hold Volume Up + Power + Home to boot into Recovery.
Click to expand...
Click to collapse
Yeah. Sorry bud i was so used to it being in plain vue i didnt even see the tabs
Sent from my SM-G925W8 using Tapatalk
polish_pat said:
Yeah. Sorry bud i was so used to it being in plain vue i didnt even see the tabs
Click to expand...
Click to collapse
No problem at all. I am glad that you found the solution. I am still waiting on Rogers to update the W8 bootloader.
To begin, my phone is functioning and I am trying to install a custom recovery application CWM/TWRP. I just replaced the LCD and screen on my phone after not using it for a year. I THOUGHT I had TWRP installed, but after I factory reset (to start fresh) I tried to root my phone and noticed the recovery is stuck in manual mode.
I followed many online guides for assistance with using Odin3 to install the custom recovery, but every forum or instruction set tells you to go into "download mode" which isn't accessible from the manual version of recovery. Here are all the options I have:
Android system recover <3e>
KTU84P.M919UVUFOH3
Reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipre cache partition
apply update from cache
(Picture of droid with red triangle!)
# Manual Mode #
-- Applying Multi-CSC....
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I am familiar with command line and if anyone has a suggestion for using CMD in windows to load a custom recovery, I'd REALLY appreciate it. So tired of KitKat!
That's just the stock recovery. You reach Download Mode via Power + Volume Down + Home and then Volume Up to continue.
es0tericcha0s said:
That's just the stock recovery. You reach Download Mode via Power + Volume Down + Home and then Volume Up to continue.
Click to expand...
Click to collapse
Thank you for the help! All the guides I saw said to use Vol Up to access download mode. I was able to successfully upgrade my S4 to use S6 software with 5.1.1! I'm very excited to have trusted devices and not have to enter my unlock code every 5 minutes!
I don't understand the idea of writing a guide and getting the most basic things wrong..? Glad all is well. ☺
I flashed newest twrp for gs3 with flashify. Now when I hit the button to reboot, the screen has samsung and at the top says recovery booting for a second then goes black. I posted this in the noob forumin reply to the person that told me to flash but i am not getting an answer
Are you sure you installed the right recovery? THIS should be the latest TWRP recovery for i9300 (3.0.2-1). Flash this with flashify (make sure you are rooted) or boot into Download Mode (Vol Down+Power+Home) and flash THIS (same as above but flashabe by Odin) and use a program like Odin to flash it.
First, give us device model, because on my i9300 it doesnt say recovery booting at the top. I have the exclamination mark
It's the sprint one. I went to the twrp site and found my phone and the newest version with .img cause I was using flashify. When it was done, it asked if I wanted to reboot, and I said yes. it turned off and never turned back on. So I pressed vol up, home, power. The usual Samsung came on the screen and at the top in blue it says recovery booting for a second, then black. when I plug my charger, it pulse vibrates. I took out the battery, tried vol down in the combination. I'm in a bind because I don't have a computer at home. Please help