Related
I'm more confused than ever on trying to find the *correct* guide to root my TF300T. The development forum has mislabeled threads, and most guides I found were guiding the root process for a device with a 9.x.x.x firmware. So, that said, can anyone point me to the CORRECT guide so I can root my TF running 10.4.2.17 please? Thanks.
Ramrod421 said:
So first off I totally understand the apprehension. I have rooted a lot thingd and this tablet seems especially technical and convoluted.
First read through this thread:
http://forum.xda-developers.com/showthread.php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
2) Now go to this thread, http://forum.xda-developers.com/showthread.php?t=1845377, scroll down to Part 3 and download the "fastboot + JB recovery" files. Extract them into the Fastboot folder that they are zipped in. There will be two .dll files, an ADB file, a Fastboot file and a twrp.blob file.
3) Turn off your tablet. Once it's off press the power and vol/dwn buttons at the same time. Keep holding them down until you see the screen with "RCK", "android", a usb symbol, and "wipe data". Once in that screen let go and use the Vol/dwn to move the cursor and vol/up to select the USB icon. Plug your tablet into your computer and the computer should recognize it as a "fastboot" device. You can check under "devices and printers".
4) Enter the "Fastboot" folder and while holding down shift, right click the mouse. In the menu you should have the option "open command window here". Select that and it will open a cmd window. Type in the line:
fastboot -i 0x0b05 flash recovery twrp.blob
This will copy the TWRP recovery file to the tablet and flash it. You will see a blue progress bar on your tablet while this is happening. Once that is done type:
fastboot -i 0x0b05 reboot
This will reboot your tablet and you will now have TWRP recovery installed.
5)Once in android again, go to this thread, http://forum.xda-developers.com/showthread.php?t=1668173, and download the "root-signed.zip" file in the second post and copy it to the tablet.
6)Turn off the tablet and boot into recovery by holding power and vol/dwn again. Once at the menu select "RCK" with Vol/up. It will boot into TWRP recovery now. Install the "root-signed.zip" file, reboot and the tablet should be rooted.
At this point I recommend creating a backup in recovery in case anything goes wrong from here on out.
Now you can flash any ROM your heart desires. I recommend CleanROM 2.7. It's fast, clean and very easy to install.
TWRP is easily the best recovery for this tablet. I have had many problems with CWM not installing ROM's properly and causing boot issues.
I hope this help you out. I know it's kind of a mine field of information but it works very nicely.
Click to expand...
Click to collapse
Sent from my Incredible 2 using xda app-developers app
Sent from my Incredible 2 using xda app-developers app
I was just about to link you to the same thing. This process will flash recovery and root your tablet.
d08speed3 said:
http://forum.xda-developers.com/show....php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
Click to expand...
Click to collapse
This is a relatively big deal: while you could root stock ICS ROMs pretty easily, you can't do it on stock JB ROMs without unlocking the bootloader, Once you're unlocked, however, it's a piece of cake.
For the amateurs. Could you elaborate on these steps?
Step (1) (a) which file to download? the .apk for the .exe file?
(b) Download to where (the tablet or onto a laptop/desktop)?
Step (2): (a) Again, download to where? Tablet or laptop/desktop? And extract to where?
Step (3) & (4): This make it sounds like the files in previous steps should be downloaded and extracted to a laptop/desktop?
Step (5) & (6): CleanRom 2.7 is already rooted. Do we need to run these steps? Or can we install CleanRom after Step 4?
Backup: What files to back up? Everything?
Critical Questions:
Do the above steps work for tablets already on Android version 4.1.1 with .29 (or .17) builds?
Sidenote: Last night, my tablets had an ASUS update and it went from build .29 to .17. Is this strange? It's going backward?
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
smokarz said:
For the amateurs. Could you elaborate on these steps?
Step (1) (a) which file to download? the .apk for the .exe file?
(b) Download to where (the tablet or onto a laptop/desktop)?
Click to expand...
Click to collapse
Download the .apk and put it on your tablet. Install it. Run it.
Step (2): (a) Again, download to where? Tablet or laptop/desktop? And extract to where?
Click to expand...
Click to collapse
These files are to be put on your computer. It doesn't matter where you put the directory.
Step (3) & (4): This make it sounds like the files in previous steps should be downloaded and extracted to a laptop/desktop?
Click to expand...
Click to collapse
Yes
Step (5) & (6): CleanRom 2.7 is already rooted. Do we need to run these steps? Or can we install CleanRom after Step 4?
Click to expand...
Click to collapse
These steps are not technically required but I put them in there because then you have a backup copy of stock JB that is rooted.
Backup: What files to back up? Everything?
Click to expand...
Click to collapse
Run TWRP. Press the back up button.
Critical Questions:
Do the above steps work for tablets already on Android version 4.1.1 with .29 (or .17) builds?
Sidenote: Last night, my tablets had an ASUS update and it went from build .29 to .17. Is this strange? It's going backward?
Click to expand...
Click to collapse
This method works for any version.
---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------
rboutin2 said:
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
Click to expand...
Click to collapse
Have you confirmed that you are truly rooted or are these apps the only ones that can't access the root directory?
So you have to root first in order to do a backup?
No you do not have to root first to do a backup.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
rboutin2 said:
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
Click to expand...
Click to collapse
I would try and clear the cache and data for supersu under settings>apps and that might make it start working properly.
jerry43812 said:
I'm more confused than ever on trying to find the *correct* guide to root my TF300T. The development forum has mislabeled threads, and most guides I found were guiding the root process for a device with a 9.x.x.x firmware. So, that said, can anyone point me to the CORRECT guide so I can root my TF running 10.4.2.17 please? Thanks.
Click to expand...
Click to collapse
I read the reply's to your Q, but as I have the same build as you I still haven't found one that anyone claims has worked.
You have any success?
Root TF300T
Thank you so very much for that very helpful post. Much appreciated.
After reading your instructions, I'm happy to proceed but may I ask one question first.
I've unlocked my TF300 with the ASUS application.
My build number is 10.4.2.18-20121122. It's a UK model.
Am I safe to use your instructions with this build?
Kind regards
I never obtained root, and since my OP, I've gotten an OTA as well, so it's back to square one in finding a viable root method.
Sent from my LG-P500 using xda app-developers app
I'm in the same boat. Got a 300 for Christmas, bumped up to JB w/o reading here first (yeah...that was dumb). So from looking around the only way to root is to unlock and the only way to unlock right now is via the ASUS tool which - from what I've gathered - will send my serial number to ASUS and void my warranty correct?
A few questions:
1.) does anyone know if work is being done to be able to unlock/relock w/o voiding the warranty? I love root, but I won't do it while in warranty in case something unthinkable happens . I'm not sure how much of this would be true, but can't we use nvflash to download the locked bootloader then find a way to spoof the ASUS unlock authorization? Hell, unless each tablet uses a different signature couldn't we just post the nvflash-able locked/unlocked bootloaders? I'm thinking back to the flash processes from my Tegra2 gTablet. I could be way off base, but it seems plausible with my limited knowledge.
2.) is it possible to root w/o unlocking? I know I won't get CWM/TWRP and the ability to load non-stock ROMs but I can live with that. I'd like to be able to run TiB, ES File - Root, etc though. I thought I saw something about obtaining root w/o unlock, but I can't find it and it might have been ICS instructions.
3.) I take it there's no downgrading back to ICS that would fix this either....
NeoMatrixJR said:
I'm in the same boat. Got a 300 for Christmas, bumped up to JB w/o reading here first (yeah...that was dumb). So from looking around the only way to root is to unlock and the only way to unlock right now is via the ASUS tool which - from what I've gathered - will send my serial number to ASUS and void my warranty correct?
A few questions:
1.) does anyone know if work is being done to be able to unlock/relock w/o voiding the warranty? I love root, but I won't do it while in warranty in case something unthinkable happens . I'm not sure how much of this would be true, but can't we use nvflash to download the locked bootloader then find a way to spoof the ASUS unlock authorization? Hell, unless each tablet uses a different signature couldn't we just post the nvflash-able locked/unlocked bootloaders? I'm thinking back to the flash processes from my Tegra2 gTablet. I could be way off base, but it seems plausible with my limited knowledge.
2.) is it possible to root w/o unlocking? I know I won't get CWM/TWRP and the ability to load non-stock ROMs but I can live with that. I'd like to be able to run TiB, ES File - Root, etc though. I thought I saw something about obtaining root w/o unlock, but I can't find it and it might have been ICS instructions.
3.) I take it there's no downgrading back to ICS that would fix this either....
Click to expand...
Click to collapse
Hi!
You can try to unlock your device with AsusUnlock app ! - is the safe way to unlock bootloader ! ( certainly will void your warranty ! )
I don't think that's cause for concern ...I've unlocked bootloader in the very next day after I bought it ( in august this year )
- so far I think I made five hundred " flash and reflash rom " - ( for testing "custom roms" ) - and the device shows like the first day when I bought it
So, be more confident - the device is not so easily to break , you can install as many "custom roms" as you want - you just have to be very careful about the steps that you make - when you try to install a custom rom !
Good luck ! :good:
regards,
Surdu Petru
Not worried so much about flashing causing issues. I've flashed my gTab more times than I can count. More worried about pre-voiding the warranty should I have any hardware issues. Like my battery life seems to be horrible and it might need sent in for that.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
I was wondering if its possible to install TWRP or another type of customer recovery on the Galaxy s3 verizon that has 4.4 running on it? I've gotten root (towelroot) Ive unlocked the bootloader(Unlocked symbol on boot) But everything i've tried to do to install twrp fails. I've tried odin and the TWRP app. TWRP app just deosnt work and odin says "Fail! (auth)" Is it even possible to install TWRP on the s3 with 4.4?
Thanks in advance.
andriodfanatic said:
I was wondering if its possible to install TWRP or another type of customer recovery on the Galaxy s3 verizon that has 4.4 running on it? I've gotten root (towelroot) Ive unlocked the bootloader(Unlocked symbol on boot) But everything i've tried to do to install twrp fails. I've tried odin and the TWRP app. TWRP app just deosnt work and odin says "Fail! (auth)" Is it even possible to install TWRP on the s3 with 4.4?
Thanks in advance.
Click to expand...
Click to collapse
No, it is not. My friend, you are doing everything in your power to hardbrick your S3. There is only root access via Towelroot which you've accomplished and Safestrap which will only let you use another 4.4.2 VRUDNE1 based rom. I'm surprised you haven't hard bricked it yet upon reboot.
Any info you need is here in our 4.3/4.4.2 OTA guide
SlimSnoopOS said:
No, it is not. My friend, you are doing everything in your power to hardbrick your S3. There is only root access via Towelroot which you've accomplished and Safestrap which will only let you use another 4.4.2 VRUDNE1 based rom. I'm surprised you haven't hard bricked it yet upon reboot.
Any info you need is here in our 4.3/4.4.2 OTA guide
Click to expand...
Click to collapse
/: Actually already hard bricked...like twice! I have my precious unbrick SD card...that was a 6h+ adventure to find something that actually worked. Live and learn right?
Anywho, got safestrap etc...but safestrap doesnt seem to want to work, says it installed, and shows state: Installed, but it wont boot into safestrap recovery! Did something i've done before screw it up?
andriodfanatic said:
I was wondering if its possible to install TWRP or another type of customer recovery on the Galaxy s3 verizon that has 4.4 running on it? I've gotten root (towelroot) Ive unlocked the bootloader(Unlocked symbol on boot) But everything i've tried to do to install twrp fails. I've tried odin and the TWRP app. TWRP app just deosnt work and odin says "Fail! (auth)" Is it even possible to install TWRP on the s3 with 4.4?
Thanks in advance.
Click to expand...
Click to collapse
You did not unlock the bootloader on your device. Can't be done on an S3 running 4.4. That unlock symbol on boot has nothing to do with the bootloader.
landshark68 said:
You did not unlock the bootloader on your device. Can't be done on an S3 running 4.4. That unlock symbol on boot has nothing to do with the bootloader.
Click to expand...
Click to collapse
Well i stand corrected then! I guess im just used to nexus'es! Safestrap isnt being nice though /:
andriodfanatic said:
Well i stand corrected then! I guess im just used to nexus'es! Safestrap isnt being nice though /:
Click to expand...
Click to collapse
Are you using the "Recovery Locked/NE1" version of Safestrap from the link I posted?
I'm sure the bootloader can still be unlocked. I mean it's Android 4.4! We're on 8 right now. I personally believe that because it took so long to unlock it the first time, once that hole was closed the same people did not want to put that much time in again when times have changed so much in 4-5 years.
I wish I just had more experience actually writing code utilizing exploits in a useful manner, instead of being able to put 2 & 2 together for a flowchart.
andriodfanatic said:
I was wondering if its possible to install TWRP or another type of customer recovery on the Galaxy s3 verizon that has 4.4 running on it? I've gotten root (towelroot) Ive unlocked the bootloader(Unlocked symbol on boot) But everything i've tried to do to install twrp fails. I've tried odin and the TWRP app. TWRP app just deosnt work and odin says "Fail! (auth)" Is it even possible to install TWRP on the s3 with 4.4?
Thanks in advance.
Click to expand...
Click to collapse
I have tried to get a custom rom on my Samsung Galaxy S3 Verizon with Android 4.4.2 but failed. The closest I have ever gotten to get a custom rom was by using Safestrap. Link: Safestrap- https://forum.xda-developers.com/showthread.php?t=2797314
Delgoth said:
I'm sure the bootloader can still be unlocked. I mean it's Android 4.4! We're on 8 right now. I personally believe that because it took so long to unlock it the first time, once that hole was closed the same people did not want to put that much time in again when times have changed so much in 4-5 years.
I wish I just had more experience actually writing code utilizing exploits in a useful manner, instead of being able to put 2 & 2 together for a flowchart.
Click to expand...
Click to collapse
Unfortunately, from my research I have not found any way to unlock the bootloader . However, the closest I have ever gotten to get a custom rom was with Safestrap. Link: Safestrap- https://forum.xda-developers.com/showthread.php?t=2797314
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Wazzer21 said:
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Click to expand...
Click to collapse
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Spaceminer said:
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Click to expand...
Click to collapse
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
triumfanto said:
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
Click to expand...
Click to collapse
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Spaceminer said:
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Click to expand...
Click to collapse
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
Click to expand...
Click to collapse
I love hearing good news! I'm willing to bet that whatever they're doing to get root will also work for you too. You'll have to do a little digging over there. You also have the same chipset as them and they have twrp already! It should be portable to your device without much of an issue. It really sounds like anyone with an A series can rejoice. I'm tempted to get one myself at this point.
Flash failed
Hello,
I have also a Samsung galaxy a20e and I followed the instructions, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normaly, but fails when I use the magisk generated file for the AP . The operation stop when Odin reading the recovery image.
I uncheck the Auto Reboot option like specified
Can someone help me please?
Have a look at this:
https://unofficialtwrp.com/galaxy-a20e-sm-a202fd-root-twrp/
this is what i am trying now, seems to be working to get TWRP and root in one go
(You May also need this: https://www.youtube.com/watch?v=mF2Nxck4FtM
because when i tried this the OEM Unlocking option in Developer Options was missing, follow the instructions in this link, get the OEM Unlock Enabled then follow the first link)
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
smda said:
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
Click to expand...
Click to collapse
Hi,
No I am still having the same issue as you, OEM Unlocked, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normally, but fails when I use the magisk generated file for the AP.
It says "Can only flash official images"
1. extract the boot.img from the firmware of your device
2. unzip with zarchiver
3. download magisk manager and choose install then select the boot.img file
4. flash the patched boot.img in Odin
Done
there is no TWRP yet cause it would need to be build from source.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
ParadoxLogic said:
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
Click to expand...
Click to collapse
I have the same problem please help to root and put my hand I have tried to do things has this mobile to see if we give a little life thanks
Hello,
Sorry for chiming in, but maybe there is a misunderstanding? The original boot.img file (extracted from the stock firmware) needs to be first patched by the Magisk app. Only after it has been patched, the boot.img file should be flashed by Odin. Maybe the guide over there helps to make it clearer: https://www.getdroidtips.com/root-galaxy-a20-a20e/
EDIT1: I see posts about "vbmeta warning", so there might be some further hurdles, see e.g. there:
https://forum.xda-developers.com/galaxy-a20/help/root-method-twrp-samsung-a20e-help-t4017763
EDIT2: You might also want to have a look into the A20 (i.e. without the "e") section:
https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4
EDIT3: vbmeta.tar attached there:
https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237
Good luck!
PS:
I understood that no TWRP or other custom recovery was needed for this, but I assume that by unlocking the bootloader via the developer options (before flashing) or/and by flashing the patched boot.img (and vbmeta.tar?) file via Odin, the Knox counter is triggered, voiding warranty and some apps not working anymore (e.g. Samsung billing etc.), and OTA updates by Samsung not working anymore. Is that correct?
This thread was started by @Wazzer21. Actually, his first post so far remains the only one. And interestingly, I found this website:
https://www.androidinfotech.com/root-samsung-galaxy-a20e-pie/
...
How to Root Samsung Galaxy A20e Pie 9.0 (SM-A202F, SM-A202K)
First of all, thanks to Wazzer21 – XDA developer for TWRP support and topjohnwu – this genius is a one who discovered and maintaining Magisk. Samsung Galaxy A20e International variants come with a flexible bootloader.
...
Click to expand...
Click to collapse
Er, what does this mean?
When you read further through that page and come to the comments, you learn:
Chris says December 1, 2019 at 3:32 am
This does not work…..at all…
once completing, there is an error VBMETA error…..
Click to expand...
Click to collapse
Selva Ganesh says December 1, 2019 at 11:53 am
The problem is Magisk 20.0. Did you use that Magisk version? If so, Try with Patch version 20.1.
Click to expand...
Click to collapse
Can somebody please confirm this? Or is this all a hoax? Sorry for asking so bluntly, but I have mixed feelings (and still do not want to appear rude or something).
PS:
On this website about rooting the Samsung A20e ("SM-A202")...
https://www.flashfilebd.com/2019/07/samsung-a20-root-file.html
... there are several files for download and the following info:
...
Here You Find Samsung A20e Root File With Magisk Manager Apk. Samsung SM-A202/F/FN/S/K Binary U1 And U2 Root File Available Here.
...
Click to expand...
Click to collapse
What do "U1" and "U2" binaries mean, i.e. how do they differ? There is no explanation (unless I have missed something).
According to some hints from @physwizz in the A20 forum, the root methods described for the A20 also work for the A20e as pointed out in several posts there.
However, currently neither TWRP nor custom kernel seem yet to be available/working for the A20e.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Hello, i read that you have root your phone, i am trying to do the same thing now but i don't know how please can you give me the process that you followed
I'm curious if at least the 20e version can be rooted, thank you all
ninowebs said:
I'm curious if at least the 20e version can be rooted, thank you all
Click to expand...
Click to collapse
Yes it can be rooted, just install TWRP, then dowbload magisk and flash it in TWRP.
which TPWR?