Hi !
I think that I followed all of the unlocking the bootloader instructions, and then root,
but I am not sure if I have been successful.
I install-superboot-windows.bat with the himem option and all seemed to go well.
but trying to run Torch, just gives me a black SU Request screen.
Is there another way to prove whether I have successfully rooted or not?
for example, 'about information' shows build plus rooted?
Any advice appreciated!
Ofiaich
http://forum.xda-developers.com/showthread.php?t=630021
St.Jimmy!
thanks for your quick reply!
Off for a read before I sleep...
Ofiaich
Go to terminal on your Mac (or whatever it is on PC)
type "adb root"
If you get a message saying it is already running then you are rooted.
thanks cymru,
I will try that,
got a reply from another forum,
"I had the same problem before. It happened to me because I hadnt
Enabled USB debugging, So do that and then run Torch.
It should request superuser permissions and show a screen asking for
it. Just hit always allow and your good to go.
(That should prove your rooted.. if it works, im not sure of any other
ways to tell)"
and it worked... but don't understand why..
Ofiaich
Related
Hello everyone, Im new here so please dont kill me if this is a common question. I have searched all over but cant find the answer I need. Im excited to learn from all the wonderful information here and cant wait to get started.
Anyway, I had a Nexus S 4g flashed to work on Boost. I would like to root it so that I can change some things. However, I do not know if my phone was previously rooted. Is there anyway to find out? If it was, and I rooted it again, would that cause problems? Also, does rooting the phone cause problems with the flashing, or will it keep all of the necessary network information intact (so that it doesnt screw up my service)?
Rooting doesn't cause problems with the flashing, it just -potentially- opens up the system to damage. This is a user responsibility and not a fault of the rooting process; it's a possibility of having too much power over the system.
Most likely it would have had the bootloader unlocked and have been rooted. Turn off the phone and turn it on again by holding Vol. Up and Power simultaneously for a few seconds. If it was rooted, the best way to know is if it says "bootloader unlocked" in the upper half of the screen. If not, there is a high chance it isn't CURRENTLY rooted. If it is unlocked, the most work you need to give root access to android is going into recovery and installing a .zip file.
Exactly so after finding that out just look over one of the many guides we have here at XDA to flash the superuser package.
Sent from my Nexus S
I didnt see anything saying unlocked. I see 'Lock State - Locked', so Im assuming this means that it is not currently rooted. I guess now I will go through some guides and learn which method would be best for me. Thanks for the quick reply and help.
Most likely you aren't rooted either - you can test by typing "su" in terminal emulator.
Just remember if u unlock bootloader the internal data and sdcard will all be deleted.
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.
Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.
Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.
I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I tried looking for troubleshooting guides, but unfortunately Marshmallow no longer has a "forgot code?" option. Also, I tried Android Device Manager, but it tells me since my phone already has a lockscreen, I no longer need to add a password (which I intended to do, in order to know said password)
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.
xdmatt said:
I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.
Click to expand...
Click to collapse
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
edit: this does not work on marshmallow[tested]
i think this will help you http://forum.xda-developers.com/note-4/orig-development/bypass-lock-screen-pattern-password-pin-t2948336
bablu048 said:
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
Click to expand...
Click to collapse
hopefully he enabled the usb debugging option
pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.
pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
bablu048 said:
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.
Click to expand...
Click to collapse
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.
bablu048 said:
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.
Click to expand...
Click to collapse
He wouldn't have been able to use it because you need a custom recovery to flash that file.
Well... I guess you know the system works? Probably not great for there to be an easy or sure-fire way to unlock a phone if you don't know the security details.
If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.
AtomicStryker said:
If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.
Click to expand...
Click to collapse
i want to know how to copy data from the device through recovery. do you know the process or where to find a guide?
edit: thanks for the idea. i hadn't thought that way.
xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
For preventative measures, Tasker is your friend. Have a "Plan B" microSD with a special .txt file on it, and have Tasker detect SD inserted and scan that file. If the file matches, then Tasker should wipe /data/system/gesture.key and password.key, and sqlite3 into settings.db and "update system set value=0 where name='lock_pattern_autolock' " to unlock your device.
In the case of an aftermath, it is now (as of today) possible to recover files/photos from the lockscreen without root, ADB, or custom recovery. Just an internet connection, linked Google account, and access to the notification drawer. I just published my first app, Locked-out Phone Backup, that is similar to the old Screen Lock Bypass Pro for Gingerbread, but instead recovers files instead of disabling the screen lock, so no root is required!
Hope this answers your question!
Well, try some password remover.
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Did you activate developer settings with USB debugging
ewingr said:
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Click to expand...
Click to collapse
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
FijNNY said:
Did you activate developer settings with USB debugging
Click to expand...
Click to collapse
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
jinkerz9430 said:
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
Click to expand...
Click to collapse
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.dump
Click to expand...
Click to collapse
All being on the same line.
Any idea if that's a bad idea?
[edit]
I just found that I can do a similar command for Greenify and have it do an aggressive doze. I think I'll try that. I may pop back into my Journey thread to update what's going on.
ewingr said:
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
All being on the same line.
Any idea if that's a bad idea?
Click to expand...
Click to collapse
Hmm it wouldnt hurt to try. I mean, without root priviliges there are not changes that can affect the system of the phone internally speaking. So... What adb did you download? I used the one from the pixel because my system wouldnt show me the prompt box asking me whether i want to allow my laptop to make changes to my phone.
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
ewingr said:
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
Click to expand...
Click to collapse
see? hahaha that's what you needed to find. the prompt asking you to authorize. in my case it didnt show it until i used the adb from pixel's forum since it appear that the adb shown on the rooting method's thread is missing a file which wouldnt allow to work properly so, then after i opened the adb , it did ask me for the authorization box