Related
End of support. Thread closed.
If you get stuck in recovery and can't boot into Android, you need to install the stock recovery to get Android to boot.
Stock recovery flashable zip located HERE.
------------------------------------------------------------------------------------------------------
READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
CWM Recovery 6.0.4.8
(TWRP is in post 3, Philz Touch in post 4)
Click HERE for the latest version.
Please report any bugs here in this thread.
Thank you to everyone who has (and still will) help in testing!!!!
Credits go to:
@Unjustified Dev for device and kernel source trees
and of course Koush and the CyanogenMod team
Watch THIS VIDEO tutorial for a step by step visual guide for performing the instructions listed below (thanks @Tomsgt for the video).
Instructions:
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them). Also need to enable USB debugging.
7. Select "PDA" (or AP) then choose the recovery file you want to flash. (Unzip the file you downloaded so that you have a file named "recovery.tar.md5".)
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 9).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Watch this video to learn about the navigation issues and Rainbow Mode: http://youtu.be/iCNdxlNzdBI
If the highlight doesn't move on the recovery menu, the selection actually does change. Go ahead and hit Power to select. If the menu goes blank, just hit Volume Up or Down to get it to reappear.
It appears that the menu navigation issue only happens when you use the button combination to boot into recovery. If you use the Quick Boot app or "adb reboot recovery", it seems to work properly. Only use the 3-button method to boot into recovery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Flash at own risk!!!!
+++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++
Click HERE for the latest version.
Stock recovery flashable zip located HERE.
Nice!
Sent from the can using two ply
TWRP is reported to be causing problems for now. Please use CWM or Philz Touch (post 4) for now.
TWRP 2.7.0.1 (unofficial)
Click HERE to download the latest version.
I do not have a T110, so this recovery has not been tested by me. Please report if it works for you.
Same install instructions as above.
After installation, you may experience slow behavior in recovery if you use the button combination to boot into recovery. Using Quick Boot from the play store or any other software method to boot into recovery will solve this problem.
Internal card gets mounted as "/data/media/0".
Please report any issues here in this thread and be sure to include which recovery you are using.
+++++++++++++++++++++++++++++++++++++
If you already have root, you can extract the recovery.img from this zip and flash it without Odin by using Flashify from the Play Store.
+++++++++++++++++++++++++++++++++++++
Click HERE to download the latest version.
Unofficial Philz Touch Advanced CWM recovery HERE for testing.
Credits to Phil3759. Original thread located HERE.
Hey hey hey...
Sent from my SPH-L710 using Tapatalk
You are awesome!!!!!
This is so very awesome....thank you!!!!
Sent from my SM-T110 using xda app-developers app
This is amazing, super fast devs rooting the tab 3 lite in no time.
Now it's waiting for a good stock Google rom to speed up this nice tab and losing the awful touchwhizz laggynes.
I have tryed almost all your custom recoverys CWM and none were working. When i try to eneter in recovery i got only blackscreen and the device it is seen by adb
But TWRM is perfect!
Thanks
Getting a notification to update but I haven't rooted yet so I'm not sure if I should.... Had my tab for about a week now....it says some kind of security update anybody else get this
Sent from my SM-T110 using xda app-developers app
mhopewell41 said:
Getting a notification to update but I haven't rooted yet so I'm not sure if I should.... Had my tab for about a week now....it says some kind of security update anybody else get this
Sent from my SM-T110 using xda app-developers app
Click to expand...
Click to collapse
Security is something else. Not software update.
It is a new protection from samsung, generaly with knox from 4.2.2 software and newer!
TWRP updated to version 2.7.0.0
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
sewa2k said:
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
Click to expand...
Click to collapse
Did you wipe anything while booted into recovery? I sounds like system or boot was wiped. You may need to flash the stock firmware in Odin.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Did you wipe anything while booted into recovery? I sounds like system or boot was wiped. You may need to flash the stock firmware in Odin.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Stuck in bootloop in recovery as well after rooting. Using CWM recovery and did not wipe anything at all. Going to try again.
sewa2k said:
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
Click to expand...
Click to collapse
mhopewell41 said:
Stuck in bootloop in recovery as well after rooting. Using CWM recovery and did not wipe anything at all. Going to try again.
Click to expand...
Click to collapse
Me to.. and im looking for a solution..
Streykatorato said:
Me to.. and im looking for a solution..
Click to expand...
Click to collapse
Try wiping cache.
gr8nole said:
Try wiping cache.
Click to expand...
Click to collapse
Didnt work.. tried.. any other solution?..
Streykatorato said:
Didnt work.. tried.. any other solution?..
Click to expand...
Click to collapse
Tried a full data wipe?
Sent from my SCH-I605
gr8nole said:
Tried a full data wipe?
Sent from my SCH-I605
Click to expand...
Click to collapse
Yup.. tried that too..
Hi everyone I have a big big problem. My volume buttons are broken, so I can'n navigate through CWM revovery. I have cm10.2 and I want to try the kiktkat ROMs. What should I do? I tried to use goo manager but after I press "flash roms" it reboots in recovery, where I can't do anything unless reboot now. Is there a way to install TWRP touch recovery? I think of installing stock jellybean with ODIN and use a custon kernel through DD command method, but I don't know how to root without using the recovery. Any other solutions? Is there a way to install TWRP directly on cyanogenmod 10.2? Why goo manager doesen't work? Rom manager do the same thing, instead of flashing my rom, it reboots in recovery. Please help me, i'm desperate. Basicaly I want to install ROMs or TWRP recovery WITHOUT USING THE VOLUME BUTTON.
cristinel13 said:
Hi everyone I have a big big problem. My volume buttons are broken, so I can'n navigate through CWM revovery. I have cm10.2 and I want to try the kiktkat ROMs. What should I do? I tried to use goo manager but after I press "flash roms" it reboots in recovery, where I can't do anything unless reboot now. Is there a way to install TWRP touch recovery? I think of installing stock jellybean with ODIN and use a custon kernel through DD command method, but I don't know how to root without using the recovery. Any other solutions? Is there a way to install TWRP directly on cyanogenmod 10.2? Why goo manager doesen't work? Rom manager do the same thing, instead of flashing my rom, it reboots in recovery. Please help me, i'm desperate. Basicaly I want to install ROMs or TWRP recovery WITHOUT USING THE VOLUME BUTTON.
Click to expand...
Click to collapse
I think that we do not have any CM kernel that has TWRP. And you can't install separately recovery from kernel. Maybe you can do this, install CM11 kernel - it has touch CWM. When you swipe up it goes up, when you swipe down... But you must be carefull, and to get 100% working CM11 zip in your recovery, to avoid getting a bootloop. Unpack it on PC and see if zip of it is not broken,
You can install CM11 kernel by getting it from CM11 zip, copy it to the phone and use Universal Kernel Flasher from Play store. After installing it I think that you can't go back to CM10.2 anymore, you will end up with a bootloop. So you must install CM11. And another thing, I am not sure if reboot recovery works well, you will end up with nothing if it does not. So do everything at your risk, do not blame me if you fail...
We do not have working ROM manager or similar thing.
shut_down said:
I think that we do not have any CM kernel that has TWRP. And you can't install separately recovery from kernel. Maybe you can do this, install CM11 kernel - it has touch CWM. When you swipe up it goes up, when you swipe down... But you must be carefull, and to get 100% working CM11 zip in your recovery, to avoid getting a bootloop. Unpack it on PC and see if zip of it is not broken,
You can install CM11 kernel by getting it from CM11 zip, copy it to the phone and use Universal Kernel Flasher from Play store. After installing it I think that you can't go back to CM10.2 anymore, you will end up with a bootloop. So you must install CM11. And another thing, I am not sure if reboot recovery works well, you will end up with nothing if it does not. So do everything at your risk, do not blame me if you fail...
We do not have working ROM manager or similar thing.
Click to expand...
Click to collapse
So I should unpack the CM11 zip and flash the kernel in CM10.2 that I already have? If I will end up with bootloop how should I enter the recovery? The only way to do it is through reboot to recovery option in my rom, if I get stuck in the bootloop I will not be able to do anything. Can you explain one more time, step by step?
cristinel13 said:
So I should unpack the CM11 zip and flash the kernel in CM10.2 that I already have? If I will end up with bootloop how should I enter the recovery? The only way to do it is through reboot to recovery option in my rom, if I get stuck in the bootloop I will not be able to do anything. Can you explain one more time, step by step?
Click to expand...
Click to collapse
I can't guarantee that you can reboot to recovery, because sometimes it does not work. This process is risky... You can't go to download mode too after that.
1. Download CM11 zip, get boot.img from it
2. Install Universal Kernel Flasher and some root explorer
3. Install boot.img with Universal Kernel Flasher
4. Reboot recovery
5. Install CM11, do factory reset, wipe cache, dalvik cache...
I wouldn't try something like this with those risks, I will rather get my volume buttons fixed before trying this. I think chances to fail is greater then not to.
I understand now.. as you said is too risky. Can anyone help me with a method to get root on stock jellybean without using recovery or to use goo manager? I want so bad to try kitkat but I don't want to brick my phone in the process. Thank you Shutdown anyway for the help.
cristinel13 said:
I understand now.. as you said is too risky. Can anyone help me with a method to get root on stock jellybean without using recovery or to use goo manager? I want so bad to try kitkat but I don't want to brick my phone in the process. Thank you Shutdown anyway for the help.
Click to expand...
Click to collapse
I think Goo manager is not working because it is not compatible with our device. Its developer needs to make it work with our phone. So I think there is no other method for rooting except the one we have, zip file and flashing it in recovery.
Why there isn't an odin flashable method for root as for gingerbread? I am sorry for bothering you, but you are of the most experienced dev/user of our device.. My volume flex can't be fixed unless I change the motherboard wich is far too expensive compared with the value of the phone. I also have a very unstable version of cm 10.2 (I installed it like 10 months ago) so my camera doesen't work in video and I have the in call volume bug. If I just could root stock jellybean with other method, I could use twrp and install any 4.4 ROM I want. It is frustrating because I am so close yet so far..
cristinel13 said:
Why there isn't an odin flashable method for root as for gingerbread? I am sorry for bothering you, but you are of the most experienced dev/user of our device.. My volume flex can't be fixed unless I change the motherboard wich is far too expensive compared with the value of the phone. I also have a very unstable version of cm 10.2 (I installed it like 10 months ago) so my camera doesen't work in video and I have the in call volume bug. If I just could root stock jellybean with other method, I could use twrp and install any 4.4 ROM I want. It is frustrating because I am so close yet so far..
Click to expand...
Click to collapse
There is not Odin flashable root method because we got that Recovery method that is easy and does not increase binary count, and devs did not make the one for Odin. Anyway you can't go to download mode too if Volume buttons is not working. You need to press volume up to proceed...
I built a long time ago a CM10.1 kernel with TWRP recovery... CM10.2 CWM is touch recovery.
@cristinel13 Method by shut_down is perfect, but if you aren't not sure to do it do this:
I built this file for you, download it but don't extract, leave as it is
Open Odin and put that file in "PDA"
Open Terminal Emulator on your device and write first su, confirm access then write reboot download
Now your device is in download mode without need to press vol+ to confirm
Press "Start" on Odin
Let the device starts, then open again Terminal Emulator, write again su then write reboot recovery to enter in recovery. Now flash any KitKat ROM that you want
A little help? I flashed it with odin and now my phone is bricked. It boot to the samsung galaxy s advance logo and then it stops. My PC reconise it and I can charge my phone, but I can't start it. How can I enter recovery/download without the buttons? I am pretty scared right now :-s
cristinel13 said:
A little help? I flashed it with odin and now my phone is bricked. It boot to the samsung galaxy s advance logo and then it stops. My PC reconise it and I can charge my phone, but I can't start it. How can I enter recovery/download without the buttons? I am pretty scared right now :-s
Click to expand...
Click to collapse
I think that you need to do factory reset... Can you use ADB? Try to delete data/data folder in root with ADB. You can use this if you need GUI: http://forum.xda-developers.com/showthread.php?t=2105707
You can try with delete of folder data/dalvik-cache.
P.S. I forgot that you flashed just kernel, try adb reboot recovery.
The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.
cristinel13 said:
The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.
Click to expand...
Click to collapse
Try. Leave it sometime on that bootloop, and if it is possible it will give you adb access. Use reboot recovery command, like you did for download mode.
Sent from my GT-I9070 using Tapatalk
cristinel13 said:
The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.
Click to expand...
Click to collapse
Oh right, kernels compiled on 4.4 can't start on 4.2-4.3... Sorry, I forgot that, do you have at least a very little knowledge about hardware? If yes, we can use a "pro" method that will 101% work to enter in recovery
shut_down said:
Try. Leave it sometime on that bootloop, and if it is possible it will give you adb access. Use reboot recovery command, like you did for download mode.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Unfortunately to have ADB on boot you need to modify default.prop inside boot.img's primary ramdisk, and he can't actually flash again...
You cand explain the method to enter in recovery, I will give it a shot.
cristinel13 said:
You cand explain the method to enter in recovery, I will give it a shot.
Click to expand...
Click to collapse
In terminal emulator get superuser request nd then type 'reboot recovery' then u r good to go...........
kamalnath93 said:
In terminal emulator get superuser request nd then type 'reboot recovery' then u r good to go...........
Click to expand...
Click to collapse
I don't know why usually someone doesn't read previous messages in a thread. He can't actually boot his ROM, so no terminal emulator
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
elektronchika said:
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
Click to expand...
Click to collapse
install costum recovery via odin and flash supersu in costum recovery, thats it
9134
klemen241 said:
install costum recovery via odin and flash supersu in costum recovery, thats it
Click to expand...
Click to collapse
This is CF-auto-root, which as I said didn't work with 4.3
elektronchika said:
This is CF-auto-root, which as I said didn't work with 4.3
Click to expand...
Click to collapse
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
klemen241 said:
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
Click to expand...
Click to collapse
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
If you let the phone reboot after flashing custom recovery, it will overwrite the custom one with stock one - tried that earlier today
---
sorry, misunderstand, if you update supersu just open knox and close after it shows you options to lock screen - then the supersu handles knox blocking properly
---
edit2: I tried with supersu by chainfire, didn't test with other party superuser.apk
adamuadamu said:
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
Click to expand...
Click to collapse
This also doesn't work...
Try also Koush's Superuser.
Sent from my GT-I9305 using XDA Free mobile app
elektronchika said:
This also doesn't work...
Click to expand...
Click to collapse
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Thank you adamuadamu !!!
It works!
Regards Sonic76
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
sham79 said:
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
Click to expand...
Click to collapse
first attachment in the OP
direct link: http://forum.xda-developers.com/attachment.php?attachmentid=1680841&d=1359295479
Thanks for the explanation adamuadamu,
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Thanks in advance for the reply and explanation.
Cheers,
Da Fig
Do you have to flash the custom recovery first and then SuperU? Is it possible to just flash SuperU and then using Triangle Away in order to root 4.4.4?
I want root but want to stay as stock as possible.
Da Fig said:
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Click to expand...
Click to collapse
I remember using some older SuperSu (1.9xx) as the files were already on my SD Card
In case you need proper and updated files and you're a bit afraid of confusing them - google for skipsoft toolkit, choose your device, wait for the program to download appropriate files and then in order to get the files you need, you'd have to (all from my memory, in case you'd need more detailed info, let me know and I can check within couple of hours, as I'm not in front of my private PC now)
1. go to root options and use option to push supersu and recovery disabler to your card
2. let the program reboot your phone into download mode
3. contrary to the advice onscreen, use odin, but untick "Auto Reboot", flash your recovery (the program will show you the path to newest recoveries it downloaded upon first run)
4. wait for the recovery being flashed, disconnect the phone, pull the battery. DON'T CLOSE ODIN yet, you may need it if you fail to boot into recovery directly!
5. start the phone using 3-key combo into recovery. if you fail, you'll need to go back to step 2.
6. flash both files copied in step 1.
7. reboot into system
personally I stick with PhilZ touch, as it always checks for root when leaving recovery and offers to repair it
8. go to play store and download or update supersu by chainfire (whatever applies to you)
9. run SuperSU, agree to disable KNOX
Thanks for the reply adamuadamu, I'll try this and see. Apparently most supersu or the correspondent CF-auto-root will do the trick. I'll try your method first, otherwise I'll start playing with different files.
Cheers.
KennyMRos said:
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
Click to expand...
Click to collapse
SuperSU version 2.01 has the forced close problem on 4.4.4.
Download the SuperSU version 2.02 in following thread and install it. It will ask to disable KNOX. select YES.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
:good:
isn't there a way to instal just SU with towelroot installing an old samsung kernel without tripping knox like in this thread?
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
I installed Philz Touch Recovery and fix it all.
I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
GOOGLE APPS
1. Download the KitKat official signed package from Cyanogen gapps-kk-20140105-signed.zip - 83.1 MB
2. Copy gapps-kk-20140105-signed.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate gapps-kk-20140105-signed.zip on your phone and proceed with the installation.
5. Reboot your phone and you're done.
To remove/hide bloatware I suggest to use Titanium Backup.
CHANGELOG
16/10/2014
- updated SuperSU to 2.14
- added additional steps to avoid automatic stock recovery reflash
I added some steps to avoid stock recovery reflash, forgot that very important step!
Hi bubbl3,
I was wondering if you have tried to install the gapps without a custom recovery.? The reason I am asking is that when I try to flash gapps with stock recovery I get an error message that says: signature verification failed. Tried with and without root.
I don't have exactly your phone but close, Sm-g9008w.
//Jaco
Jaco_dk said:
Hi bubbl3,
I was wondering if you have tried to install the gapps without a custom recovery.? The reason I am asking is that when I try to flash gapps with stock recovery I get an error message that says: signature verification failed. Tried with and without root.
I don't have exactly your phone but close, Sm-g9008w.
//Jaco
Click to expand...
Click to collapse
Gave up on trying on stock recovery and installed custom recovery, then everything went smoothly.
//Jaco
Jaco_dk said:
Gave up on trying on stock recovery and installed custom recovery, then everything went smoothly.
//Jaco
Click to expand...
Click to collapse
Yes, sorry for the late reply, you cannot flash the gapps in stock recovery.
Which recovery did you flash on your G9008W, the one in this thread?
bubbl3 said:
Yes, sorry for the late reply, you cannot flash the gapps in stock recovery.
Which recovery did you flash on your G9008W, the one in this thread?
Click to expand...
Click to collapse
No problem at all, just meant I was forced to test a bit in the blind, as it really hard to find any information regarding the SM-G9008W.
Yeah, I used your recovery as your phone got almost the same firmware version(G9008WZMU1ANH3), so I expected that it would work and it worked like a charm.
How much bloatware did you remove with Titanium? I got a few things apps I am not sure if I can remove without any consequence.
Jaco_dk said:
No problem at all, just meant I was forced to test a bit in the blind, as it really hard to find any information regarding the SM-G9008W.
Yeah, I used your recovery as your phone got almost the same firmware version(G9008WZMU1ANH3), so I expected that it would work and it worked like a charm.
How much bloatware did you remove with Titanium? I got a few things apps I am not sure if I can remove without any consequence.
Click to expand...
Click to collapse
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
bubbl3 said:
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
Click to expand...
Click to collapse
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
bubbl3 said:
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
Click to expand...
Click to collapse
Hi. Even I have the Chinese version G9008W and was looking how to root it with English language.
The link you gave is of a Russian site. Is the recovery in English? Are the recoveries given in OP in English?
Thanks for your replies.
gverma1 said:
Hi. Even I have the Chinese version G9008W and was looking how to root it with English language.
The link you gave is of a Russian site. Is the recovery in English? Are the recoveries given in OP in English?
Thanks for your replies.
Click to expand...
Click to collapse
Yes, both recoveries are in English.
bubbl3 said:
I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
Click to expand...
Click to collapse
Thanks for your detailed step-by-step instructions. Just wanted to reconfirm in Step 8 when it asks to disable recovery reflashing - do I have to say 'yes' (disable recovery reflashing) or 'no' (don't disable recovery reflashing).
Thanks
gverma1 said:
Thanks for your detailed step-by-step instructions. Just wanted to reconfirm in Step 8 when it asks to disable recovery reflashing - do I have to say 'yes' (disable recovery reflashing) or 'no' (don't disable recovery reflashing).
Thanks
Click to expand...
Click to collapse
You should answer 'yes' (disable recovery reflashing)
bubbl3 said:
Yes, both recoveries are in English.
Click to expand...
Click to collapse
Great! I had got this phone pre-rooted by the vendor and he has messed up deleting apps and deleted important stuff like keyboard, etc. I will be flashing latest stock Samsung firmware from Sammobile.com and then try your method to root. Hope that goes through fine. Will I have to flash GAPPS as well?
Also, I hope I don't lose my dual SIM functionality by rooting the stock ROM. Will I?
Thanks
gverma1 said:
Great! I had got this phone pre-rooted by the vendor and he has messed up deleting apps and deleted important stuff like keyboard, etc. I will be flashing latest stock Samsung firmware from Sammobile.com and then try your method to root. Hope that goes through fine. Will I have to flash GAPPS as well?
Also, I hope I don't lose my dual SIM functionality by rooting the stock ROM. Will I?
Thanks
Click to expand...
Click to collapse
You will have to flash GAPPS as the original stock ROM doesn't include them, also I don't see how you can loose dual SIM functionality if you flash the stock ROM.
bubbl3 said:
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
Click to expand...
Click to collapse
Yes, I had a lot of problems finding any informations about the G9008W, that's also why I decided to write in your thread, hoped others could find it useful.
Nice, I will try to remove as much as possible myself then.
bubbl3 said:
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
Click to expand...
Click to collapse
Thanks for the help, however I don't have any problems what so ever, so I think I will keep using yours for now.
Does it work on SM-G9006W?
bubbl3 said:
I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
GOOGLE APPS
1. Download the KitKat official signed package from Cyanogen gapps-kk-20140105-signed.zip - 83.1 MB
2. Copy gapps-kk-20140105-signed.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate gapps-kk-20140105-signed.zip on your phone and proceed with the installation.
5. Reboot your phone and you're done.
To remove/hide bloatware I suggest to use Titanium Backup.
CHANGELOG
16/10/2014
- updated SuperSU to 2.14
- added additional steps to avoid automatic stock recovery reflash
Click to expand...
Click to collapse
I have seen these threads for a while and I couldn't find anything related to my SM-G9006W, even on other threads, I didn't see anything about SM-G9006W. I also recently updated it to Lollilop 5, not sure if that make more complicated to install GAPPS. If you know anything about how to root this phone and install GAPPS, please let me know, I would be really appreciated. Thank you
Hi. G9008W has got Lollipop update. I plan to flash it after downloading from sammobile site. Will this method be still valid to root the phone running Lollipop? Will this CWM work? Of course, I'll flash Lollipop CM gapps. Thanks.
Sent from my Nexus 5 using XDA Free mobile app
gverma1 said:
Hi. G9008W has got Lollipop update. I plan to flash it after downloading from sammobile site. Will this method be still valid to root the phone running Lollipop? Will this CWM work? Of course, I'll flash Lollipop CM gapps. Thanks.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi gverma1,
Have you tried it yet?
I am downloading the lolipop update right now, and I was wondering exactly the same if the CWM will work with Lolipop, as I need google play.
I will try and see if Chainfire is willing to make a new CFAuto root for Lolipop for SM-G9008W when I am done with downloading the firmware.
//Jaco
Downloading here myself. But on checking CWM versions for other phones including other S5 variants, the version required seems to be 6.0.4.8 whereas we have 6.0.5.0 here. So I don't think there would be any issues.
gverma1 said:
Downloading here myself. But on checking CWM versions for other phones including other S5 variants, the version required seems to be 6.0.4.8 whereas we have 6.0.5.0 here. So I don't think there would be any issues.
Click to expand...
Click to collapse
Hi gverma1,
I just finished updating to Lolipop, and I installed the 6.0.5.0 and it works just fine.
However it didn't like the PA Gapps Nano, got stuck att starting up apps. So I am going to test some different once now.
Update. The Gapps actually worked after a factory reset.
//Jaco.
I have been testing the latest KINGOROOT (not Kingroot) root app and had 100% success every time with it on my T805. I performed the process a least 10 times with success every time.
To get root it is required to downgrade to a XXU1ANF8 Kitkat or earlier firmware. If you are already running this firmware skip to step 3.
Video footage is included at the end of this post.
NOTE: THE USUAL WARNINGS APPLY. IF YOU FOLLOW THIS PROCEDURE YOU DO SO AT YOUR OWN DISCRETION.
1. If you are running Lollipop then downgrade to the stock firmware for your device as above with ODIN then boot into recovery and wipe/reset
THIS WILL WIPE EVERYTHING OFF THE INTERNAL STORAGE SO BACKUP YOUR STUFF FIRST!
2. Reboot and wait for the tablet to boot to Android. Do the usual setup or skip everything except wifi setup if you wish to upgrade to Lollipop afterwards.
3. Install KINGOROOT for Android then run it. After a short while you will hopefully have success. For me it quickly went to 40% then paused and then went to 95% and then paused for a while longer then said ROOT SUCCESS. No reboots.
4. YOU SHOULD NOW HAVE ROOT. DO NOT REBOOT AS THE ROOT IS ONLY TEMPORARY AS KNOX WILL BLOCK IT. YOU NOW NEED TO CONVERT TO SUPERSU
To convert to Supersu:
Install the Superuser apk and System app remover.
Supersu v2.49
System app remover
5. Run the Superuser app. Hit Continue and then Normal method to install the Super su binary. Wait for KingoUser to ask if you want to Grant root. Hit Grant . If you see a message pop up to disable Knox just hit cancel.
After a short while you should see that the su binary has been successfully installed. Hit OK, DO NOT hit Reboot. Run the Superuser app and make sure it starts ok then close it.
6. Now run the System app remover app and uninstall KingoUser(Now called Superuser in new version). You now have permanent root with Supersu and can now run it and disable Knox.
7. IF YOU WISH TO UPGRADE TO LOLLIPOP OR OTHER ROM THEN NOW REFER TO MY GUIDE BELOW FOR HOW TO PROCEED, STARTING FROM STEP 10:
http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
Kingoroot rooting video: https://youtu.be/ThDSmMHP_08
GOOD LUCK, PLEASE GIVE FEEDBACK :good:
.
Wow good to know! I cant believe you went ahead and actually downgraded that far just to try it xD
Sent from my SM-T800 using Tapatalk
i tried you new mode i was on 5.0.2 T805XXU1BOD2 T805
I tried to downgrade to kitkat i use your suggested file from 1 page XSG-T805XXU1ANF8-20140625 with ODIN. in download mode.
after booting i get only black screen with samsung logo.
i tried to go to recovery as u said POWER + HOME + VOL UP then select WIPE DATA/RESET
but nothing happen , i stock on samsung logo with black screen for 5 minute
i went again to download mode by POWER + HOME + VOL DOWN and flash again with T805XWU1BOD3_T805OJV1BOD3_XSG
thanks god im back on Lollipop device is working now and did not asked mi to go to setting.
what was wrong with my steps?
can i do WIPE DATA/RESET - when im running Lollipot , then go to download mode and downgrade to kitkat?
or first i should go for flash kitkat , then reboot and WIPE DATA/RESET ?
after downgarde to kitkat normally the device will log to kitkat, and setting procedure ? or it stock on samsung logo and i should do POWER + HOME + VOL UP
when i see black screen with samsung logo, shall i do POWER + HOME + VOL UP? or first i should turn device off and do the POWER + HOME + VOL UP?
im sure i did something wrong
thanks for your help
You have to wipe data/reset when downgrading to kitkat.
You can do it first before downgrade then flash kitkat with Odin.
ashyx said:
You have to wipe data/reset when downgrading to kitkat.
You can do it first before downgrade then flash kitkat with Odin.
Click to expand...
Click to collapse
wipe data/reset
E:unknown"volume for path C/sbfs]
E:unknown volume "/sbfs"
Data wipe complete.
I don't know what wrong.
alialexali said:
wipe data/reset
E:unknown"volume for path C/sbfs]
E:unknown volume "/sbfs"
Data wipe complete.
I don't know what wrong.
Click to expand...
Click to collapse
Nothing went wrong everybody gets that warning after a wipe.
ashyx said:
Nothing went wrong everybody gets that warning after a wipe.
Click to expand...
Click to collapse
i did Wipe, after wip my system reboot to Lollipop i did right? or after wip i should not go to reboot,?
so now aim gong to add kitkat by odin
do i get back to device after flash ( because i did Wipe, after wip my system reboot to Lollipop ) or if i stuck on samsung logo a should to wip again?
if i need to do wip , can i unchecked auto reboot on odin?
than who can i go to wip? after odin done his job, a should power off the device by power button ?
an then go to wip?
im not fast i can not do wip as i can see reboot singe
No DO NOT boot to Lollipop!
You have to boot to Download mode immediately after wipe/reset.
that was my Q who can i go to download mode after i wip?
i did not see such a choise.
after wip in recovery mode please tel mi who can i go to download mode?
and many thanks for ur kind help
REBOOT TO BOOTLOADER? shall i chose this one after wip?
Download mode = power +home + vol down.
ashyx said:
Download mode = power +home + vol down.
Click to expand...
Click to collapse
i now bro
but press this button when im in recovery screen?
or do reboot and in main time itt reboot doing the above fast?
alialexali said:
i now bro
but press this button when im in recovery screen?
or do reboot and in main time itt reboot doing the above fast?
Click to expand...
Click to collapse
1. BOOT TO RECOVERY
2. WIPE DATA/RESET
3. POWER + HOME + VOL DOWN
THATS IT!
ashyx said:
1. BOOT TO RECOVERY
2. WIPE DATA/RESET
3. POWER + HOME + VOL DOWN
THATS IT!
Click to expand...
Click to collapse
done bro now im in kitkat 4.4.2 :good::good::good::good:
base band version :T805XXU1ANF5
bulid version: T805XXU1ANF8
im on XXU1ANF8 yes? i can see 5 and 8?
u asked for T805XXU1ANF.
alialexali said:
done bro now im in kitkat 4.4.2 :good::good::good::good:
base band version :T805XXU1ANF5
bulid version: T805XXU1ANF8
im on XXU1ANF8 yes? i can see 5 and 8?
u asked for T805XXU1ANF.
Click to expand...
Click to collapse
T805XXU1ANF8 as stated in first post.
ashyx said:
T805XXU1ANF8 as stated in first post.
Click to expand...
Click to collapse
i now bro im reading your post since 3 week
.
but i get this 2 singe
base band version :T805XXU1ANF5
bulid version: T805XXU1ANF8
so im on T805XXU1ANF8 or T805XXU1ANF5?
I really dont think you should be doing this procedure as you dont seem to understand what you are doing. XXU1ANF8 is the firmware build number, thats all that matters.
ashyx said:
I really dont think you should be doing this procedure as you dont seem to understand what you are doing. XXU1ANF8 is the firmware build number, thats all that matters.
Click to expand...
Click to collapse
thanks bro for your kind help, and sorry if i made u angry from mi.:crying::crying:
i used this link as u advise:
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
but i did not now that Bulid number should be T805XXU1ANF8 not the baseband number
so im in correct frimware now as my BUILD NUMBER IS KOT49H- T805XXU1ANF8
Im going to root now, i think you will get headache from my dump Q when i done
Yes, you're all set to go. Good luck. :thumbup:
ashyx said:
Yes, you're all set to go. Good luck. :thumbup:
Click to expand...
Click to collapse
Q before Root by KINGOROOT
1- if i want to stay on Kitkat after rooting, can i unroot any time? ( for warranty if something happen to device )
do i need any special program, or just flash by ODIN the stuck firmware, and root will gone?
2 - if i want to update latter on to Unroot version of Lollipop or higher firmware can i do it ?or i just i stuck on kitkat forever after rooting my kitkat?
3) after rooting to check my knox is 0x0x, shall i go to download mode to check it, or any program can tell mi?
sorry for headache:crying::crying::crying:
You can unroot and go back to stock any time by flashing stock firmware. Knox will remain 0.