Related
I just bought a brand-new TF700 and it is fortunately still on .26 - I haven't even removed the wrapper from the tablet itself.
I want to (safely) end up rooted and on JB when I am finished, but some of the steps between are confusing, for example:
I see that there are issues with .30 and the nvflash backup procedure, correct?
I also am on the fence about unlocking. I guess I would be willing to void the warranty (gulp) but I really do not plan to run anything but a stock rom. On the other hand, having an nvflash backup appeals to me very much but if I understand it correctly, I have to be unlocked first?
But, while not crazy about a custom ROM, I do want to use a custom recovery because I like being able to do a nandroid backup. I see TWRP isn't ready for JB yet, but a modified CWM is?
So, I have downloaded several files, and read the various guides as to root, unlock, etc. But, what I still don't understand is what steps I should perform in what order. I understand that rooting .26 is probably the first step, but here are some of my questions:
1. At what point do I unlock? before .30? Do I even install .30 if I want to end up on JB
2. I know I need to root, update su, and then use Voodoo to preserve it prior to the JB update
So, I suppose what I really need the most help with is what order to perform what steps in. All the guides are helpful, but the info seems to contradict in some places.
With the clean slate on what I have with .26, what order do I do what to avoid a soft or hard brick?
Thanks in advance!
-Rob
robroy90 said:
I just bought a brand-new TF700 and it is fortunately still on .26 - I haven't even removed the wrapper from the tablet itself.
I want to (safely) end up rooted and on JB when I am finished, but some of the steps between are confusing, for example:
I see that there are issues with .30 and the nvflash backup procedure, correct?
I also am on the fence about unlocking. I guess I would be willing to void the warranty (gulp) but I really do not plan to run anything but a stock rom. On the other hand, having an nvflash backup appeals to me very much but if I understand it correctly, I have to be unlocked first?
But, while not crazy about a custom ROM, I do want to use a custom recovery because I like being able to do a nandroid backup. I see TWRP isn't ready for JB yet, but a modified CWM is?
So, I have downloaded several files, and read the various guides as to root, unlock, etc. But, what I still don't understand is what steps I should perform in what order. I understand that rooting .26 is probably the first step, but here are some of my questions:
1. At what point do I unlock? before .30? Do I even install .30 if I want to end up on JB
2. I know I need to root, update su, and then use Voodoo to preserve it prior to the JB update
So, I suppose what I really need the most help with is what order to perform what steps in. All the guides are helpful, but the info seems to contradict in some places.
With the clean slate on what I have with .26, what order do I do what to avoid a soft or hard brick?
Thanks in advance!
-Rob
Click to expand...
Click to collapse
Do not upgrade to .30 before you do the following (very important and life saving).
Make a full backup of all your apps. (not system apps)
1. Root and unlock bootloader then install custom recovery and Voodoo OTA root keeper from the market.
2. Use NVflash to backup your bootloader (very important, can recover from brick)
3. Use Voodoo OTA root keeper to temporary unroot and save a copy
4. Upgrade to .30 then restore root using OTA root keeper, download "root checker" from the market and verify that you still have root
5. Upgrade to JB then install latest custom recovery CWM (twrp is not working with JB)
6. Restore your apps.
here is the detail how to link:
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
buhohitr said:
Do not upgrade to .30 before you do the following (very important and life saving).
Make a full backup of all your apps. (not system apps)
1. Root and unlock bootloader then install custom recovery and Voodoo OTA root keeper from the market.
2. Use NVflash to backup your bootloader (very important, can recover from brick)
3. Use Voodoo OTA root keeper to temporary unroot and save a copy
4. Upgrade to .30 then restore root using OTA root keeper, download "root checker" from the market and verify that you still have root
5. Upgrade to JB then install latest custom recovery CWM (twrp is not working with JB)
6. Restore your apps.
here is the detail how to link:
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
Click to expand...
Click to collapse
Is there any benefit in going to .30 before going to JB?
Reason I ask is that I went from .26 straight to JB (using the 444MB download from the Asus website).
Is the intermediate step only for those that want the OTA update?
Nope. You should be fine since there is no advantage.
Sent from my ASUS Transformer Pad TF700T using xda premium
Galaxea said:
Is there any benefit in going to .30 before going to JB?
Reason I ask is that I went from .26 straight to JB (using the 444MB download from the Asus website).
Is the intermediate step only for those that want the OTA update?
Click to expand...
Click to collapse
If you install using the file on Asus's website you will likely lose root indefinately. Better to root and use OTA Rootkeeper and use the dlpkgfile method to keep root for the future.
an extremely easy step by step guide i put together (including files for WW and US tablets) is linked here
Hi, I have an HTC One M8 on 5.0.1 and I have little knowledge with rooting. I want to root my phone because there are some apps I want to use that are only capable of being used if my phone is rooted. I've tried Kingo root and it doesn't work on my phone so I was wondering if someone can give me instructions and download links so I can root my phone. If you can it would be much appreciated, thanks.
Boltz111 said:
Hi, I have an HTC One M8 on 5.0.1 and I have little knowledge with rooting. I want to root my phone because there are some apps I want to use that are only capable of being used if my phone is rooted. I've tried Kingo root and it doesn't work on my phone so I was wondering if someone can give me instructions and download links so I can root my phone. If you can it would be much appreciated, thanks.
Click to expand...
Click to collapse
You have 2 options at the moment.
1) Ship device to one of the many great people with a Java Card/XTC2 Clip - Look at the OP of this thread to see where the people are located.
2) With some time and luck - King Root, which has been proven to work for a number of M8 users.
http://forum.xda-developers.com/showpost.php?p=61920423&postcount=3652
http://forum.xda-developers.com/showpost.php?p=62161028&postcount=47
I was able to get S-Off using the KingRoot and Sunshine method. Now what? Although I did get root long enough to get S-off, I lose it after each time I get temp root with the KingRoot app again. KingRoot will say that I have root, but I can't get SuperSU to install.
I am doing a factory reset now and will try to use KingRoot to get temp root, then install SuperSU. Will I then be able to install TWRP after SuperSU is installed correctly?
Koblek said:
I was able to get S-Off using the KingRoot and Sunshine method. Now what? Although I did get root long enough to get S-off, I lose it after each time I get temp root with the KingRoot app again. KingRoot will say that I have root, but I can't get SuperSU to install.
I am doing a factory reset now and will try to use KingRoot to get temp root, then install SuperSU. Will I then be able to install TWRP after SuperSU is installed correctly?
Click to expand...
Click to collapse
If you are S-OFF, then I would flash a custom recovery and then a custom ROM (if you want)
or flash superSU in the custom recovery if you just want root.
Once S-OFF you are in full control of your device, so do some reading about it as you can end up with an expensive paperweight easily if you don't know what you're doing.
Or try vroot, i rooted my phone in just 1 tap
dexter0218, I think it would be BIG BIG news here if there were a one-click root solution for the newest M8. 5.01 phones aren't rootable easily.
boltz111, no need to fiddle with SuperSU. Now that you are S-Off, make sure you have ADB and get the latest TWRP for the M8. Drop to your ADP shell and do:
adb reboot bootloader
fastboot flash recovery twrp.zip
(sub in the name of your zip)
That's it. Then:
- Power down
- Power up in bootloader (hold down vol)
- Go to recovery
You have to go to recovery before booting or else the rom will overwrite the recovery.
Once you're in TWRP, you can load up SuperSU from a .zip and it will do its thing.
Or flash a rooted ruu from fastboot, loads you back to stock but with perm root, never had an issue
I had Android 5.0 (PB1) and was rooted. I updated to Marshmallow using the posted method, and everything went well, but I did lose root access after updating to Marshmallow, which I did expect. I did downgrade to 5.0 (PB1) and tried to root using the posted directions, but to no avail. I am now attempting to update back to marshmallow. I also have a LOCKED bootloader.
Goto rooting the S5 thread as locked 6.0.1 is rooted for days now.
Killing Them Loudly
Molon-Labe said:
Goto rooting the S5 thread as locked 6.0.1 is rooted for days now.
Killing Them Loudly
Click to expand...
Click to collapse
So I still can root with 6.01 with a locked bootloder?
No, you cannot. This is discussed in numerous threads. Such as Muniz_ri's root thread and the unlock bootlooder thread. Please search before posting a thread which this has been mentioned. Thank you
Got to downgrade then root etc..
Killing Them Loudly
Molon-Labe said:
Yes look after method 4
http://forum.xda-developers.com/showthread.php?t=3337909
Killing Them Loudly
Click to expand...
Click to collapse
I read that article, but you need to be rooted do that, I tried to downgrade to 5.0 (PB1) and tried to root according to the directions from the link that is also referenced to on that page, but it did not work. Is there a specific way to downgrade to 5.0 (PB1) and to root? What iI did was I used Odin and flashed the PB1 image and then tried the rooting method mentioned, but it did not work. If there is a specific way to downgrade to PB1 and root, then I can follow the directions that you suggested to me.
Uptime73 said:
I read that article, but you need to be rooted do that, I tried to downgrade to 5.0 (PB1) and tried to root according to the directions from the link that is also referenced to on that page, but it did not work. Is there a specific way to downgrade to 5.0 (PB1) and to root? What iI did was I used Odin and flashed the PB1 image and then tried the rooting method mentioned, but it did not work. If there is a specific way to downgrade to PB1 and root, then I can follow the directions that you suggested to me.
Click to expand...
Click to collapse
i did this a bunch of times with my S5 with a locked bootloader (i have a Toshiba 11 emmc) --
flash stock PB1 and follow the Get Root instructions on PB1, http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
then follow upgrade instructions for locked bootloader to PD1. try this thread: http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943 (this worked for me)
( there is also this one, but it didnt work for me: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 )
All the info is here in the forums. good luck!
stras1234 said:
i did this a bunch of times with my S5 with a locked bootloader (i have a Toshiba 11 emmc) --
flash stock PB1 and follow the Get Root instructions on PB1, http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
then follow upgrade instructions for locked bootloader to PD1. try this thread: http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943 (this worked for me)
( there is also this one, but it didnt work for me: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 )
All the info is here in the forums. good luck!
Click to expand...
Click to collapse
I was initially on PB1 with root access, and looking back, I should have followed the link of how to unlock the boot loader and to update to PD1. Unfortunately, I followed the directions on the last link you gave me, the one you said that didn't work for you.....the one about updating to PD1 for locked boot loaders. Unlike you, it worked for me. I was on PD1 without a problem, but I wasn't rooted.. So I tried to downgrade back to PB1 and then follow the rooting directions, but it didn't work for me.
From what I have been told, since I upgraded to 6.0 (PD1), it is IMPOSSIBLE to downgrade to 5.0 and root. Is this correct?
Also, if that is the case, then is it possible for me to apply a pre rooted 5.0 image, so I can unlock the blootloader and update to 6.0?
Thanks in advance.
THERE IS NO ROOT FOR PD1 (MashMellow) for LOCKED BOOTLOADER yet. Once you're on MM 6.0 you will lose root. If you want root, you need to downgrade back to PB1 (LP), then get root working again. Once up upgrade from PB1 LP to 6.0 MM you will lose root.
buhohitr said:
THERE IS NO ROOT FOR PD1 (MashMellow) for LOCKED BOOTLOADER yet. Once you're on MM 6.0 you will lose root. If you want root, you need to downgrade back to PB1 (LP), then get root working again. Once up upgrade from PB1 LP to 6.0 MM you will lose root.
Click to expand...
Click to collapse
I am aware that once I got to PD1, I will lose root. I am also aware that I need to downgrade to PB1 and get root working again, but that is my precise problem. I have gotten back to PB1 flashing PB1 image, but I can't seem to get it rooted, at least not by following the directions mentioned on http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370.
Question. After flashing back to PB1, do you I need to flash the PB1 bootloader? For some reason, I am unable to root when I get back to PB1.
Uptime73 said:
I am aware that once I got to PD1, I will lose root. I am also aware that I need to downgrade to PB1 and get root working again, but that is my precise problem. I have gotten back to PB1 flashing PB1 image, but I can't seem to get it rooted, at least not by following the directions mentioned on http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370.
Question. After flashing back to PB1, do you I need to flash the PB1 bootloader? For some reason, I am unable to root when I get back to PB1.
Click to expand...
Click to collapse
You don't need to flash PB1 bootloader. Did you try install Kroot manually as suggested? Please show me where it failed? Did you run root.bat and if not working install Kroot manually and run roo2.bat.
Sent from my SM-G900V using Tapatalk
buhohitr said:
You don't need to flash PB1 bootloader. Did you try install Kroot manually as suggested? Please show me where it failed? Did you run root.bat and if not working install Kroot manually and run roo2.bat.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I can tell you that when I tried to run the root and root2 batch files, I got a message that said the files were missing, so I looked at the root.bat file, and I ran the individual tasks in the batch file manually., including the manual install of king root. When I ran king root, it said no methods were available.
Uptime73 said:
I can tell you that when I tried to run the root and root2 batch files, I got a message that said the files were missing, so I looked at the root.bat file, and I ran the individual tasks in the batch file manually., including the manual install of king root. When I ran king root, it said no methods were available.
Click to expand...
Click to collapse
Try to run the bat files in regular mode too, not as administrator.
Sent from my SM-G900V using Tapatalk
buhohitr said:
Try to run the bat files in regular mode too, not as administrator.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Thank you so very much!!! I ran the root.bat file in regular mode, and not as administrator, and it worked!!! I didn't think it would matter, but apparently it did. I now have root access on PB1. Unfortunately, I am unable to unlock the bootloader as I have a Toshiba 11 emmc.
Now that both CF-Auto-Root has been found and is working to root and TWRP has been ported, what method for root would be easiest for a new phone owner?
Am I right to think to easiest way would be to use Odin to install TWRP then use TWRP to root by flashing SuperSU, as that would bypass issues of any incompatible recovery being installed as well as the benefit of having TWRP already installed if a custom recovery is needed later?
http://forum.xda-developers.com/galaxy-j7/how-to/guide-samsung-galaxy-j700p-root-twrp-t3442671
Or would it be easier and just as effective to just use Odin to root using the modified CF-Auto-Root, which is closer to a single step, rather than booting into recovery and flashing something else after using Odin?
http://forum.xda-developers.com/showpost.php?p=68060852&postcount=37
No, emphatically no.
TWRP isn't yet equipped for the J700P. The best and easiest way is to just flash CF Auto Root via Odin
Interesting. Can you explain and link more about what you mean that TWRP isn't equipped for J700P? There is an official port.
https://dl.twrp.me/j7ltespr/
I'm new here so I'm not sure if this is the right place for this, but here goes. I've been trying to root my '19 Galaxy Tab A T290 [T290XXU3CUF8] for a couple months now on and off. I manage to get a success message from Odin when flashing TWRP but when I try to reboot into it, it goes straight back to the OEM recovery. I have the bootloader unlocked. I have read every forum and website I could find, but to no avail. I've tried different versions of Odin and the TWRP for my model. I'd imagine once I get TWRP flashed I'll be able to successfully install SuperSU. I've read to take the battery out after getting the success message from Odin but the battery isn't removable in my model. Any help would be greatly appreciated.
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
jwoegerbauer said:
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
Click to expand...
Click to collapse
I'm obviously not very good with Android. Do you have any suggestions for me ? From what I've read, it sounded like, among other methods, I needed to flash SuperSU via TWRP in order to get root.