Database Users

[Q]Z4Root

i rooted my phone with the app Z4Root i have never done this before so is there some steps i do now to make sure this doesn't mess up my phone and will my phone un root when updates come out?

Rooting will not "mess up" your phone on its own, it all depends on the apps you decide to run and the modifications you make.
z4root has an option to unroot. Do that youself before you upgrade.

I have found to get Z4Root to work you need to enable usb debugging & unknown sources then reboot your phone the run Z4Root

Help! Rooting issues

Hey guys, so first I rooted my phone using this method:
Ugh it won't let me use the outside link. basically its the doroot batch file for sdk/adb
Basically installed the android sdk stuff and drivers and then used the doroot batch file. That came back as okay, and I have the superuser permissions app on my phone now.
But then I tried to deodex the phone to start putting themes on there. When i get to the part where i go into the adb shell and try to use 'su' it says permission denied. So I figured the root had failed, or something was messed up. Then I tried to use this method to root:
(DroidX root. the one click program with root me and unroot me.)
That hasn't been successful. The phone disconnects from the computer for some reason (the laptop gives me the disconnected hardware sound during the install, and the install never finishes.)
So I tried Z4root. I downloaded it online, and put it on the phone, and installed it. It gives me the 'unroot' option, so it thinks my phone is rooted, but then it says usb debugging must be enabled. It says it must be enabled for every option i can choose (temp or permanant root.) The thing is, it is enabled!
I've tried to run titanium backup to check if I have root access on the phone, and that app says I don't.
What do I do? I'm totally stumped, and I have no idea if i've screwed this thing up or what. Is there any way to get my phone back to its original state so I can try this whole thing over again?
Help!

lunchbox2 said:
Hey guys, so first I rooted my phone using this method:
Ugh it won't let me use the outside link. basically its the doroot batch file for sdk/adb
Basically installed the android sdk stuff and drivers and then used the doroot batch file. That came back as okay, and I have the superuser permissions app on my phone now.
But then I tried to deodex the phone to start putting themes on there. When i get to the part where i go into the adb shell and try to use 'su' it says permission denied. So I figured the root had failed, or something was messed up. Then I tried to use this method to root:
(DroidX root. the one click program with root me and unroot me.)
That hasn't been successful. The phone disconnects from the computer for some reason (the laptop gives me the disconnected hardware sound during the install, and the install never finishes.)
So I tried Z4root. I downloaded it online, and put it on the phone, and installed it. It gives me the 'unroot' option, so it thinks my phone is rooted, but then it says usb debugging must be enabled. It says it must be enabled for every option i can choose (temp or permanant root.) The thing is, it is enabled!
I've tried to run titanium backup to check if I have root access on the phone, and that app says I don't.
What do I do? I'm totally stumped, and I have no idea if i've screwed this thing up or what. Is there any way to get my phone back to its original state so I can try this whole thing over again?
Help!
Click to expand...
Click to collapse
have you tried unrooting it since you got the "unroot" option you said when you open up z4?...if you can sucessfully unroot keep debug on and reboot then run z4 again..worth a shot...if it was sucessful you should see the temp root or permenant root option chose permemnet and let it do its magic. hope it helps its worth a shot..

Weird...
Thanks paul. I ended up turning the phone off and pulling the battery, and then upon restart z4 let me unroot, and then let me root! I had probably ****ed something up by trying to root it 2 different ways and 20 different times. Thanks for the advice!

Wait a sec -
So I'm trying to use adb to finish de-odexing, and I'm getting permission denied on the following command:
su mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Does this mean I'm not rooted? Titanium backup works on the phone, and a notification popped up on the phone asking me if I wanted to give it superuser permissions or something...So I feel like I must be rooted. Any ideas?
If I leave out the su in the front of that command, it says Operation not permitted.
But If I type SU the cursor does switch to the dollar sign, so I think I have su privileges.

Droid X probably dead.
Haha hey everyone. So I managed to get root access through adb shell, and was in the middle of de-odexing the files. However, I ran rm /system/framework/*.odex before I ran rm /system/app/*.odex by mistake.
After the first command, the phone restarted and I lost connection to the phone for some reason.
Now when I start the phone up I get all these boxes that say (on a black background) Sorry! the application Voice Commands (process com.nuance.android.vsuite.vsuiteapp) has stopped unexpectedly. Please try again.
It gives me the option to force close, but the box just appears again. I can't get the phone to boot. What do I do!?
Edit: Found sbf. Flashed. Phone is alive.

Can not install TWRP with KF Utility

KF Utility is stuck at the <waiting for device> script
It also says
adb can not run as root in production builds.
the command prompt says <idme> invalid permissions.
and i notice in the video that it's supposed to reboot in fastboot and it doesn't do anything.
can anyone help? Nothing is working so far.

Dumb question, but are you rooted?

rolyatkcinmai said:
Dumb question, but are you rooted?
Click to expand...
Click to collapse
yeah, with burritoroot2
i think, well, i know i'm rooted, i just don't know if its with that or burritoroot3

I had the same problem. After the 6.2.2 update, I rerooted with burritoroot2. Apps requiring root work fine, but I was unable to use KFU 0.9.2 to install TWRP. So I basically followed the directions in this post and KFU was able to install TWRP.

Drivers
Make sure that your device manager has the fire listed as composite adb and not just adb. Sounds like you are having driver issues.

huchman said:
Make sure that your device manager has the fire listed as composite adb and not just adb. Sounds like you are having driver issues.
Click to expand...
Click to collapse
I figured it out. my ADB wasn't rooted on my computer itself. I must have messed up something while i was in the command prompt. My kindle was rooted, but my computer wasn't recognizing it as being so.
I now to CM7! and i love it!

Another dumb question: how do I know if I'm rooted
Is there a way to display the status (rooted or not)? Or do I always have to run the Kindle Fire Utility to check the status of my Kindle?

there are apps on the market like rootchecker

Bmcd37 said:
Is there a way to display the status (rooted or not)? Or do I always have to run the Kindle Fire Utility to check the status of my Kindle?
Click to expand...
Click to collapse
there is an app called root check
download, install and give it superuser permissions.
when you root it, it should stay rooted unless you tell it to not be rooted anymore.
or are you talking about the computer?
if you do the command prompt sequence for burritoRoot it should stay rooted.

Thanks.
I'm still getting used to the concept of rooting. I forget that it's more permanent that a network connection between the PC and Kindle Fire. I will download an app just to satisfy myself that things don't change in the way of root status, unless I change it.
Have a good weekend.
Thanks.

Trying to root again after 4.2.1 update

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.

2nd kindle root attempt

when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?

ksound said:
when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?
Click to expand...
Click to collapse
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?

wrexhamafc said:
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?
Click to expand...
Click to collapse
yeah I had meant to mention that, my other one is running 7.2.1
gonna try resetting to factory defaults on the new one and see if I can root it that way
eta- nope restes to 7.2.2 and still no root

never mind I figured it out