Related
Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker
Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?
Hope somebody comes up with an answer - same thing happened to me.
did you use the d3 root method? thats the only one that works 100% on gingerbread.
Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.
SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni
Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.
Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?
Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.
This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!
Awesome! Thanks!
Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!
Awesome!
Thanks! This worked for me as well! (after additional reboot)
Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.
Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew
awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer
It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Huskehn said:
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Click to expand...
Click to collapse
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Yea i've tried the drivers from LG's site and the drivers that come on the phone itself. Definitely no luck so far.
Darkestred said:
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Click to expand...
Click to collapse
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
Software update would probably break current root method though sadly.
bose301s said:
Software update would probably break current root method though sadly.
Click to expand...
Click to collapse
ADB > root! ADB is usually essential to achieve root anyway.
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
emplox said:
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
Click to expand...
Click to collapse
This sucks, now we wait for a software update... without the ability to use ADB or any way to fix it. Oh well, worse things have happened.
I just got off the phone with LG. They specifically told me that there are no drivers that currently work on the VZW G2 and they should have the released 'in less than a week' and it should solve all ADB issues. Not sure I believe it...but I guess we'll see.
emplox said:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
chrisexv6 said:
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
Click to expand...
Click to collapse
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
ok i'm having issues with getting adb to find my device and this is an old thread and the chinese root wasn't working right. anyway to get the phone to list in adb yet, not using the chinese method?
Edit: could drivers from my previous phone have anything to do with this?
Edit2: Still could use an answer just in case, but i just realized that i haven't had to use adb on a device since before 4.2.2 so i possibly need to update my abd from pdanet, so i'll give that a go later tonight. but any other help would be appreciated. thanks in advance
drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
bigox said:
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
We figured out how to enable ADB a while ago. You need to plug in your phone to PC, select Internet then Ethernet (or something similar) instead of Media Sync or Charge Only. Also ADB must be enabled in Settings. Then, it should show in PC devices, you can install the Google ADB driver, and use ADB. First time using it, your phone should pop up with an RSA key window to allow ADB.
1. Install drivers can be found here: http://d-h.st/fBw
downloaded this file but i dont see how to install it. no .exe or anything
how do i install drivers? http://i.imgur.com/J5dax87.png
thanks
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Click to expand...
Click to collapse
Having the same problem
I have the Verizon phone and tried using the 3.1.1 driver on Windows 7 (latest driver linked on the rooting post). When I went to the LG website and downloaded the 2.11.1 driver there, everything worked perfectly and I can see the phone on the PC using ADB devices command.
question:
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
will this work for d800 d80010o?
does this ( VZW LG G2 Drivers) work for at&t g2 also?
It will works for Sprint LS980?
With some help on the cyanogenmod forums, I worked out a way to enable the integrated superuser manager to actually function!
REVISED EDITION:
WARNING! DO NOT ATTEMPT UNLESS YOU KNOW WHAT YOU ARE DOING.
This is an experimental step to bring a feature from regular Cyanogenmod to 11S. You have been warned.
This requires adb and fastboot to be installed.
Please read all the instructions before attempting
1)-- Optional-Flash a custom recovery of your choice. There are threads out there that explain this.
2)Next flash the debuggable kernel, found at the bottom of this post. You can easily flash it via fastboot.
fastboot flash boot ./path/to/boot-debuggable.img
2)Download su.zip I created.
3)Boot into custom recovery(a requirement). This can be done without actually flashing it. Look up how, plenty of threads already.
4)Flash su.zip
8) Reboot.
9)If you didn't before doing this, go to Settings => About Phone and enable developer mode. Under Settings => Developer Options select Root Access and change it to Apps and ADB. Now install any root application or root checker and test it out.
Debuggable Kernel is downloadable here at the bottom:
https://cyngn.com/products/oneplusone/
su.zip
http://www.androidfilehost.com/?fid=23578570567721138
https://mega.co.nz/#!sp8nmL5J!Pj2Z4UI-7vG2YsMwEpIbDLTWOwiyWwu398oLE9edFdk
RESERVED
RESERVED
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
joaocadide said:
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
Click to expand...
Click to collapse
What current superuser manager are you using? SuperSU?
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
How can I get rid of the menu when I use SuperSU instead?
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
That only makes the menu visible. The menu will not actually function as a Superuser manager. For that, you would need the debuggable kernel and the proper compatible su binary which is why I wrote my instructions.
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
jbass350z said:
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
Click to expand...
Click to collapse
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
vladashram said:
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
Click to expand...
Click to collapse
I had this same exact issue with secure settings, and elected to follow the instructions on this page to activate the cyanogenmod root settings - it worked just fine. Interestingly, even after losing the "built in root" after updating to XPNH300, secure settings still seems happy.
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
chenkeikari said:
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
vladashram said:
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Click to expand...
Click to collapse
As of right now, the stock debuggable kernel for 30O is live and available.
Thanks for your work.
But could you please update to the latest version of the SuperSU binaries or could you tell me, what you modified comparing it to the normal SuperSU.zip?
Would you please share how and why would this be different than a straight forward install of SuperSU?
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Not working for me
Titokhan said:
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Click to expand...
Click to collapse
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
remortr said:
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
Click to expand...
Click to collapse
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Pls help me step by step procedure..
sendhiloo7 said:
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Every thing done but fast boot wont work in my case pls help me sir .pls see my attachment...
Hi everyone,
I'm having trouble getting root on my Oppo Find 5 ever since I switched to cROMs based on Android 4.4.x or higher.
Until 4.2.x Framaroot apk did the trick for me, but it doesn't seem to work on the newer versions anymore. Right now, I'm using MIUI v7 (Android 4.4.4) and I'm pretty happy with it, but I hate not having root and I can't find anything useful online. Most English threads are from way back where .zip downloads are down already and/or the info is terribly outdated.
Did anyone find a method to root their X909 on Android 4.4.x and above?
I would greatly appreciate any help.
Go to security app in MIUI and go to permissions => Root acces.
boertjeg said:
Go to security app in MIUI and go to permissions => Root acces.
Click to expand...
Click to collapse
It only says that no apps have root permission. Does MIUI have a built-in root access? The Security stuff seems to me like a root manager only, similar to SuperSU and Superuser.
I also downloaded Root Check for whatever it is worth and it says my device is not rooted.
edit: I just checked some other threads and apparently developer versions of MIUI have built-in root access. My X909 is currently running the ported ROM by wuxianlin000000 though. I'm not sure if it's supposed to have root as well.
I tried starting Titanium Backup in hopes of getting a root access request, but it just showed an info box that no root access could be acquired.
I'm running the same rom and I have root acces. Dont know how I enabled it but it wasn't anything I had to flash and pretty sure it was something in settings. Try checking security app root options again and grant root acces to the apps that are listed.
boertjeg said:
Go to security app in MIUI and go to permissions => Root acces.
Click to expand...
Click to collapse
boertjeg said:
I'm running the same rom and I have root acces. Dont know how I enabled it but it wasn't anything I had to flash and pretty sure it was something in settings. Try checking security app root options again and grant root acces to the apps that are listed.
Click to expand...
Click to collapse
I think I'm going to reinstall once again to see if it fixes anything (doesn't bother me that much since I wanted to try LVM installation anyway). Are prerooted cROMs the norm after 4.2.x? Else, I'd still really like to know a root method that works regardless of the ROM.
Short update:
I don't know why but MIUIs root worked when I checked again today. I don't know why, but beforehand there were no "requests" from apps shown under Security > Permissions > Root access. Today, however *something* (I really have no clue what) apparently changed and apps requesting root access are shown and I can grant them access.
Hello!
So I recently rooted my Samsung Galaxy S5 (SM-G900i)
I flashed the kltedd .tar.md5 file through odin (downloaded the .tar.md5 file through Chainfire's CF Auto Root Website)
Everything worked, after going through the whole process my phone rebooted and everything seems normal.
All my data has been preserved and it all works fine.
The only problem is to check that my phone actually has root access I need to download one of those root-checker apps from the play store, but I need to sign into my Gmail account to get to the play store in the first place.
I just wanted to know if it is safe to log into my gmail account on a rooted device - is it possible in any way shape or form that I might have a sneaky keylogger or some spy-ware that could potentially see my Gmail password?
Any help would be appreciated
Sincerely, a noob to XDA Forums.
If you have rooted then there should be a SuperSU app or similar, and when you enter it it should tell you somewhere if root is working fine.
There's an easy way to check for root, which doesn't involve any app, but you need to be able to connect the phone to a PC and you will need USB drivers, and to get your hands on adb.exe (or android-tools-adb package on Linux). Assuming you've done that:
* Enable developer options. (Settings > About Phone, tap Build number 10 times, you will get a popup telling you that Settings > Developer options has appeared.)
* Enable "USB debugging mode".
* Connect via USB to the PC.
* Run `adb devices`.
* You will be asked if you want to accept the debug connection, and possible if you want to enable MTP, say "yes" to both.
* Run `adb shell`.
* Once inside the shell you can type "su[ENTER]". The terminal should freeze and you should get a popup from your SuperSU app asking if you want to grant root access to ADB. If you don't get a popup and "su" fails in the terminal, you don't have root. If you don't get a popup but you get a "#" prompt in the terminal, you have root, but you don't have a root controller app, which is not good (anybody can get root).
Another even simpler method would be to use a terminal app... provided you already have one installed. Most custom ROMs do, stock ROMs don't. Then you just use the same "su[ENTER]" stuff in the terminal.
also, you can bypass the whole thing of logging into your gmail acct and go directly into your phones main screen, go into menu, settings, about phone and tap on the build number until you see the message stating that you are now a developer, back up one step, go into developer options, check the box to allow the installation of third party apps and just download the root checker apk from elsewhere. Sounds compllicated, but its easier than CLI stuff for the uninitiated
---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------
also also, ive never heard of anyone getting a keylogger after merely rooting their phones
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
security should be fine as long as you dont lose your device or download apps from unsafe sites.
as for whether it is rooted or not, already answered above.
Good to see another aussie here.
I'm still a bit of a noob too but happy to help with any endevours regarding phone, especially model specific ones (I have G900I too).
wirespot said:
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
Click to expand...
Click to collapse
really mate!?
i have my rooted S5 with my 3 gmail accounts logged in
and i didnt have any secuirty issue at all in past and now