Received my TFP today. I also have a Galaxy Nexus with unlocked bootloader, rooted and running a custom ROM. So when Play finishes downloading all of my apps (same ones from the GNex of course) I notice that it has installed Super User and Root Explorer. So I decide to try to open Root Explorer, just for the hell of it, but it's not going to open because Root Explorer requires root and Super User. So after tapping the icon I get the Super User request for permissions, and I check grant su permissions.
What do you know; Root Explorer opens and I'm able to edit and delete system files just like it's rooted. Note that I haven't done a thing to my TFP; it's bone stock. I'm delighted, but I can't say that I understand why?
Where did you get your prime from?!
Sounds like you might have gotten a return from someone else? Was the box and everything sealed?
Can you mount the system as RW? Root explorer will still let you access the root directory, just wont let you change anything thats protected... but if the notification comes up asking for root access then that usually means your rooted.... weird indeed.
Can you install busybox?
Sent from my Unlocked WSG Transformer Prime
David522d said:
Where did you get your prime from?!
Click to expand...
Click to collapse
Purchased second hand from the Market Place on this forum.
pileot said:
Can you mount the system as RW? Root explorer will still let you access the root directory, just wont let you change anything thats protected... but if the notification comes up asking for root access then that usually means your rooted.... weird indeed.
Click to expand...
Click to collapse
Yes, I can mount as RW.
jiffy1080 said:
Can you install busybox?
Sent from my Unlocked WSG Transformer Prime
Click to expand...
Click to collapse
Yes, I was able to install Busybox.
I tried to boot into recovery, but I can see no evidence that there is any custom recovery loaded.
There is no message on the splash screen indicating an unlocked bootloader.
So, it appears that my TFP is rooted, but running the stock .21 ROM, with no custom recovery.
Any other diagnosis I can do so I know the state of my TFP, prior to loading CWM and custom ROMs?
FWIW: it's like brand new, and works great. I'm really happy with the purchase. Running MrCannady's browser/system lag workaround.
lol, purchased from someone on XDA... who on XDA does NOT have their prime rooted?
Glad your happy with your purchase, have fun with your new toy
cam30era said:
Purchased second hand from the Market Place on this forum.
Yes, I can mount as RW.
Yes, I was able to install Busybox.
I tried to boot into recovery, but I can see no evidence that there is any custom recovery loaded.
There is no message on the splash screen indicating an unlocked bootloader.
So, it appears that my TFP is rooted, but running the stock .21 ROM, with no custom 7 recovery.
Any other diagnosis I can do so I know the state of my TFP, prior to loading CWM and custom ROMs?
FWIW: it's like brand new, and works great. I'm really happy with the purchase. Running MrCannady's browser/system lag workaround.
Click to expand...
Click to collapse
Well, it sounds like you're definitely rooted
Good thing too, because (been rooted/unlocked for months) I don't think you can root .21 just yet. Someone rooted the Prime before the update, most likely using rootkeeper.
Go ahead and install a recovery and pick a ROM
I would suggest Androwooks new custom ROM with motleys kernel ( I'm running it and also running Cannadys dev tweaks, even though this ROM has no such problems, and the performance is crazy fast) For a totally custom ROM I'd go with AOKP from jermaine151.
You'll have to Google it though, he left XDA and went somewhere else.
Welcome to Prime time
Have fun
jaycustom said:
Well, it sounds like you're definitely rooted
Good thing too, because (been rooted/unlocked for months) I don't think you can root .21 just yet. Someone rooted the Prime before the update, most likely using rootkeeper.
Go ahead and install a recovery and pick a ROM
I would suggest Androwooks new custom ROM with motleys kernel ( I'm running it and also running Cannadys dev tweaks, even though this ROM has no such problems, and the performance is crazy fast) For a totally custom ROM I'd go with AOKP from jermaine151.
You'll have to Google it though, he left XDA and went somewhere else.
Welcome to Prime time
Have fun
Click to expand...
Click to collapse
There is a workaround, you can downgrade to like .15 or whatever, use rootkeeper, then OTA to .21 and have it work. Good news to us who dont want to void our warrenties with unlocking.
jaycustom said:
Well, it sounds like you're definitely rooted
Good thing too, because (been rooted/unlocked for months) I don't think you can root .21 just yet. Someone rooted the Prime before the update, most likely using rootkeeper.
Go ahead and install a recovery and pick a ROM
Click to expand...
Click to collapse
Thanks.
I haven't decided if I am going to unlock the bootloader yet, with the Asus tool.
True story. I gave in to the darkside
Sent from my Transformer Prime TF201 using xda premium
Related
I once had a rooted tf201 when in v.10.4.2.15
after upgrading to v.10.4.2.17 by manual, it seems that I totally lost my root (not partial)
I tried wolf's method that downgrade to ICS to regain my root
http://forum.xda-developers.com/showthread.php?t=1622628
when I use method2
Code:
mv /data/local/tmp /data/local/tmp.bak
I always get "permission denied"
is there any way to root my tf201
Simple answer : NO
Long answer: If you would have searched the forum, you would have seen numerous thread in regards to rooting Jelly Bean. No methods is succesful for TF201 with a locked bootloader. If you are ready to unlock your prime. TWRP method has been found succesful.
urself25 said:
Simple answer : NO
Long answer: If you would have searched the forum, you would have seen numerous thread in regards to rooting Jelly Bean. No methods is succesful for TF201 with a locked bootloader. If you are ready to unlock your prime. TWRP method has been found succesful.
Click to expand...
Click to collapse
What about one that is unlocked? Mine remains unlocked after going to 10.4.2.17 but root is gone, gone, gone. I also tried flashing Superuser-3.2-arm-signed.zip after re-flashing the ROM (which worked fine going to 10.4.2.15 from ICS) but no go. The SuperUser app doesn't get installed either.
Come to think of it the JB bootloader is unlocked to begin with. What other rooting methods are there? If they've made this thing unrootable I'm kicking it to the street for the sheer joy of seeing it crushed. No more ASUS anything, ever. They really don't need to be pissing anyone off right now.
Oh, the 10.4.2.17 flash also took out TWRP but you can flash that back with fastboot.
Install TWRP, then you can use that to flash root and a superuser control app (via the "install" option in it).
Rydian said:
Install TWRP, then you can use that to flash root and a superuser control app (via the "install" option in it).
Click to expand...
Click to collapse
Thanks, TWRP is what I use. I tried flashing Superuser-3.2-arm-signed.zip immediately after flashing 10.4.2.17 to no avail. It did work, though, when I previously flashed 10.4.2.15. Is there another root/superuser .zip I might try?
I wonder if I can just re-flash 10.4.2.15 and superuser over 10.4.2.17. There doesn't seem to be much in 10.4.2.17 other than denying root.
I've just got my hands on a Prime, and it has JB on it. Meaning, TWRP, in SOME CASES, work to unlock the bootloader, which is needed to root.
Am I right at this one? Because Samsung phones has it a LOT easier...
HKboy92 said:
I've just got my hands on a Prime, and it has JB on it. Meaning, TWRP, in SOME CASES, work to unlock the bootloader, which is needed to root.
Am I right at this one? Because Samsung phones has it a LOT easier...
Click to expand...
Click to collapse
If it has TWRP that implies that it is already unlocked. When you power up what does it say in the upper left corner of the display? If any event here is a good set of instructions:
http://forum.xda-developers.com/showthread.php?t=2038464
If you are already unlocked with TWRP, just skip down to where is says "Super SU:" download it, skip again down to where it says "Install Super SU:" and go from there.
DonGateley said:
If it has TWRP that implies that it is already unlocked. When you power up what does it say in the upper left corner of the display? If any event here is a good set of instructions:
http://forum.xda-developers.com/showthread.php?t=2038464
If you are already unlocked with TWRP, just skip down to where is says "Super SU:" download it, skip again down to where it says "Install Super SU:" and go from there.
Click to expand...
Click to collapse
Nope, doesn't. Just the Asus message with the Tegra in the bottomright. I was asking if it was the only option, which doesn't have an 100% guarantee rate. I'm pretty happy with stock though. Built-in backup manager, all I need
Hey Guys,
I own a Samsung Galaxy S4 from Verizon and have followed the guide on how to root it posted on the forums. For a while things were good. My phone booted up with the correct loading screen and my device detected that I was on an official kernel. Now for reasons I'm not sure of, my phone is saying that the kernel is custom and the lock icon has returned when I restart or cold boot my phone. I'm not running custom firm ware, I'm running a stock Verizion kernel. I tried to delete SuperUser, but it isn't installed. My binaries for SuperSU are up-to-date. I'm still rooted, but I would like to get rid of the unlock icon when I boot up and I would like to get the system to recognize that this is an official kernel.
Also ES File Explorer is unable to mount r/w privilages on my phone in order to delete busybox and su so that I could try to re-root the phone again. Any help would be appreciated, thanks!!
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
Most of the time mine is gone. Maybe once a week I might see it.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
So I managed to get rid of it. I'm not sure if it's permanent, but here's what I did. I couldn't delete the stuff in the root directory (and this was before I found solid explorer which has better root access programming than es does). So I did a factory reset and found that that worked for a while, but then I noticed that downloading Triangle Away seemed to be causing the problem because the lock icon returned after I installed it and gave it root access. So I deleted it and chose the 'unroot' option from the list of options in supersu. Then I re-rooted the phone using the guide. Now the lock icon hasn't returned, and the device status under the about phone menu says that my firmware is the official one. Another thing I noticed is that I'm running an older version of busybox (version 1.17.1 I think, as installed by motochopper).
Again I'm not sure what I did differently, or changed as a result of my method, but it seems to have worked. Perhaps someone with more development knowledge can let me know what's happened for my own personal information.
Let me start off by saying I'm a total noob. I have rooted my device before, but that was so long ago I forgot everything. Anyway I don't remember how my tablet got this way because I haven't used it in a while, but I have superuser installed yet I have no root access. I opened up the Voodoo Rootkeeper and it says super user app is installed, device is rooted, but root permission hasn't been granted.
So I tried to root again on top of it hoping it would work but now I just have another superuser app. Somebody please help me get root access.
Transformer Prime TF201
Android Version 4.1.1
Build number 10.4.2.18
tbw1116 said:
Let me start off by saying I'm a total noob. I have rooted my device before, but that was so long ago I forgot everything. Anyway I don't remember how my tablet got this way because I haven't used it in a while, but I have superuser installed yet I have no root access. I opened up the Voodoo Rootkeeper and it says super user app is installed, device is rooted, but root permission hasn't been granted.
So I tried to root again on top of it hoping it would work but now I just have another superuser app. Somebody please help me get root access.
Transformer Prime TF201
Android Version 4.1.1
Build number 10.4.2.18
Click to expand...
Click to collapse
Use motochopper to root it properly.
sbdags said:
Use motochopper to root it properly.
Click to expand...
Click to collapse
Thats what I used this last time when I tried to root it. It installed the second superuser app and when I opened it, it said that I needed to update binary or something like that. But I still had no root access after using motochopper.
tbw1116 said:
Thats what I used this last time when I tried to root it. It installed the second superuser app and when I opened it, it said that I needed to update binary or something like that. But I still had no root access after using motochopper.
Click to expand...
Click to collapse
I had the same issue after the last OTA. Root was lost and OTA rootkeeper didn't work.
This worked for me: http://forum.xda-developers.com/showthread.php?t=2038464
After successfully unlocking and installing TWRP and root, I went on to install this (but you can stop here if you don't want a different ROM): http://forum.xda-developers.com/showthread.php?t=1674827
I'm delighted by this ROM. Much better than stock.
ascallop said:
I had the same issue after the last OTA. Root was lost and OTA rootkeeper didn't work.
This worked for me: http://forum.xda-developers.com/showthread.php?t=2038464
After successfully unlocking and installing TWRP and root, I went on to install this (but you can stop here if you don't want a different ROM): http://forum.xda-developers.com/showthread.php?t=1674827
I'm delighted by this ROM. Much better than stock.
Click to expand...
Click to collapse
I dont want to unlock the bootloader though. Have any suggestions of how to root without unlocking?
tbw1116 said:
I dont want to unlock the bootloader though. Have any suggestions of how to root without unlocking?
Click to expand...
Click to collapse
I did a lot of searching, and tried several methods, but I couldn't find a solution which worked. Is your Prime still under warranty? If not, there's no reason not to unlock.
ascallop said:
I did a lot of searching, and tried several methods, but I couldn't find a solution which worked. Is your Prime still under warranty? If not, there's no reason not to unlock.
Click to expand...
Click to collapse
No its not. I just have no reason to unlock. I dont care about custom ROMs and I would like to be able to return it to stock if I want to later.
Do we know a root procedure that will work after the 4.3 update?
I too am curious to know!
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Shane_pcs said:
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Click to expand...
Click to collapse
Does it matter if mine is s-off?
Alright, I got mine rooted with no problems.
Just install TWRP, CWM, or CM2 for the recovery and then install SuperSU to get the root.
If you do TWRP like I did, when you go to reboot the system for the first time, it will say that you aren't rooted and ask if you want to run SuperSU to root. Pretty straight forward.
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
I rooted mine specifically to disable updates. I'm not so much afraid of root exploits getting patched as I am any potential bootloader exploits being patched. I came from the galaxy s3, which got a bootloader update mid way through that was never cracked, so I'm little worried about that if I wait to long I can never unlock the bootloader. So far I've installed titanium backup, root explorer, and the kit kat sd card fix (no need for hotspot hack since I don't have unlimited data). I'm holding off on anything too major until the bootloader is unlocked and I can do a nandroid first.
I rooted the day I got my g3. I rooted and installed custom roms on my g2 and can't wait to do the same on my g3
Sent from my LG G3
I actually got a demo model from VZW, rooted that one, just to see how hard it was going to be, When I got my permanent one a few days later I rooted it out of the box, before installing anything else.
rooted and uninstalled what I could installed xposed tweaked to my liking and waiting for bootloader recovery and roms
Sent from my VS985 4G using Tapatalk
I rooted mine before I even set it up.
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
As with most of my phones, my G3 was rooted as soon as the battery was charged, and usually before being activated. Now if we could just get a bootloader unlock. :fingers-crossed:
bkhorn said:
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
Click to expand...
Click to collapse
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
tu3218 said:
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
Click to expand...
Click to collapse
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
tu3218 said:
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
Click to expand...
Click to collapse
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
tech_head said:
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
Click to expand...
Click to collapse
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
bkhorn said:
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
Click to expand...
Click to collapse
Great thanks! If I root, I'll be sure to follow your instructions.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I used "ioroot". Stump root did not exist when I got my phone.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I also used IORoot and it's very easy, Stump wasn't out when I rooted mine but from what I've read Stump is super easy and reliable.
I walked out of Best But, phone activated and Battery at like 70% and hopped on my laptop which I had with me and rooted the phone right there in the parking lot so that I could freeze System Updates right away.
Although Verizon is so slow with OTA updates anyways I really could have waited lol
Root that thing then remove all the Verizon junk and use Greenify... You'll be even more happy with how your G3 runs after doing that and it's quite easy to do.
- Tapatalked from the G3
nrage23 said:
I rooted mine before I even set it up.
Click to expand...
Click to collapse
yup me too
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
bobcat987 said:
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
Click to expand...
Click to collapse
Yeah I've seen some remarkable things done my fellow members.
spotmark said:
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
Click to expand...
Click to collapse
Very true. Thanks for that link. I'm just afraid of my screwing up my brand new toy haha Not sure why though, it seems stump root is really straight foward. I just know once I do it, I'll start messing with xposed a lot. I know when I had my S3, I was flashing roms like once a day. My gf thought I was crazy.