[Q] Noob questions on Droid x from a former WinMo user - Droid X General

How do I know if my phone successfully rooted? I see lots of posts about using z4root to root (I want to use wireless like I did on my TouchPro2) but no one really says where to look to see if it's actually rooted. I ran z4 "temporary" and got the message that I was rooted til my next reboot but the wireless tether program doesn't start - I get an error message. Do I need to be permanently rooted for this to work? When I reinstalled my wireless tether program, it told me that I was NOT rooted, even though z4 thinks I am.
I received the OTA update so I am on stock 2.2.1 on a 2-week-old Droid X that I really want to like but.... I need tethering (preferably wireless) on a regular basis and I just can't get it to work. PDAnet won't install on my PC and the help from june fabrics was not helpful, so that is not an option. Using the multi-step turn radio on/off, etc. didn't seem to work either.
Any help would be most appreciated as I seem to be stuck in a bad loop.

Use z4root to permanently root.
Sent from my DROIDX using XDA App

Easy way to check is download android terminal emulator free from the market. Open it and type "su" (without the quotes) and hit enter. If the $ sign changes to #, you're rooted.
Sent from my DROIDX using Tapatalk

get a tool called "Root Explorer" Your gonna need it anyways also Koush "Recovery bootstrapper" you NEED this also.
Once installed see if they work. If not your not rooted .
Use Z4root to root as suggested from the other posters.

So apparently my problem was that I was only using the "temporary" option from z4root, not the "permanent". Thanks also for the advice on the other apps I need - once installed, I was able to figure out that I was not rooted until I used the "permanent" option.

Related

[Q] failing to root after OTA 2.2.1

Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
Find the APK file for Z4 root and give it a go that way or Superoneclick has always worked for me. Just make sure you have the latest drivers from Motorolla for your phone and PC OS. It's far easier then rageagainstthecage.
Thanks, some of the things I've tried... Z4 all 3 editions, they dont hang and run through as if there sucessful, but when the X reboots and i try running an app like root explorer. It says phone not rooted. Super1click gets stuck in a loop and using adb devices, shows device connected but offline. Rebooting phone is the only way out. I Just can't see what im missing here, other than I should have unrooted b4 the OTA update.
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
There's been a coupe threads already started with your issue..I think there's one on the 3rd page called can't reroot after the ota update...find it and follow the directions..
Sent from my DROIDX
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
DasNas said:
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
Click to expand...
Click to collapse
That's good..Enjoy
Sent from my DROIDX

Root problem....

Guys I had rooted my tab with the iconia root 1.3.....I wanted to unroot so I clicked on the option to unroot annd at the end I got a message......*something went wrong....are you still rooted?!?!....but the superuser apk is gone......so am I rooted or not......also when I click root again It says starting with root process..
extracting..
And then nothing happens....
Need imediate solution for this guys...
Sent from my XT720 using XDA App
Ok.....uninstalled iconiaroot....switched off and.rebooted my device.....installed iconia root again(v1.2 now)...it rooted me back.....but the same problem occurs with unrooting!
Sent from my XT720 using XDA App
Same problem
I'd like a fix for this as well. I'm trying to test whether it is my rom or the fact that I am rooted leading to market errors on such apps as "Kindle", "Nook", "Overdrive" etc.
I realize that rooting removes the ability to rent movies on the market, but if it also screws up access to the ebook software (or any DRM restricted software), we really need a method to unroot, get what we need, and then reroot. Stealth root?
If they're going to purposefully block legitimate means of obtaining things... Well, that just saves me a lot of money.
Why don't you guys try asking in the Iconiaroot thread?
easiest way to tell is download terminal emulator from the market.
after it installs open it ant type "su" without quotes
if it says permision denied you are NOT rooted.
if it gives you a "#" sign you ARE rooted

Solve this puzzle...

Alright... I am having a bit of an issue... looking for interesting solutions.
Have a replacement MT4G with stock 2.3.4. I am trying to downgrade to Froyo so I can root it.
Unfortunately, my usb cable must not be working. It starts charging when I plug it into the PC, but Windows won't recognize it (I have tried different ports, and double checked drivers...). When I had my first Mt4G, if I needed to use ADB, I used a market app that allowed me to connect to ADB using Wifi. It has some limitations, but it is a good substitute if needed.
But those Wireless ADB apps only work with Root (at least the ones I found), and well, obviously that was the goal all along... so I am thinking temporary root... but didn't think there was a temp root...
Question: does anyone know of a way to access ADB wirelessly without root, or know of a way to gain temp root via terminal emulator so I could then connect via the wifi ADB app and be able to complete downgrade/permroot?.... or are there any suggestions for what I could do to get the USB working?.....anything would be appreciated.
I can use the SD card with my laptop.. so downloading/getting files on the phone's SD card is not a problem... just access to ADB is a problem.
PS: Since the USB cable still functions as a charger (if that is actually the problem), I am trying to avoid spend $40 for the replacement.... since I would really only need it once.
Did you try TrueBlue_Drew thread about adb/fastboot set up ?
Sent from my HTC Glacier using XDA App
If you need to gain root access, there are other methods than the regular ADB .
Refer this post to find way that suits you.
http://forum.xda-developers.com/showthread.php?t=834225
If you need Wireless ADB, refer to this post.
Thank you both.... question however...
2kwic25: I checked the trueblue thread, and this seems to be a method for rooting which does not require the full sdk. However, it still uses the usb cable to connect to the phone. I am trying to gain temp root either through the emulator alone, or using adb (which is already installed on my pc) via wifi, but without having any su or root permissions as I don't have them and that is what I am trying to achieve ultimately.
febycb I read/scanned the link on rooting.... I went through to the end of it, and it doesn't seem to apply to the gingerbread 2.3.4 stock. This is what is on my phone now. I have a brand new phone, everything is factory locked, no root, s=on, etc.. The one post I found originally which seems to be the route most are using is to gain temproot, then downgrade to Froyo.... THEN attempt rooting to get a real permroot with s=off. So, in order to downgrade, I need to connect via USB, and use adb initially. But my USB does not work, so I am left with trying to connect via wifi. However, the thread on using adb over wifi seems to say that while you may not need to use su when running the necessary commands in the emulator, your device must still be rooted. So I cannot seem to figure out how to do this trying to use adb over wifi to get root, yet you need root to use adb over wifi.
Lastly, while I did note that your first link says only updated devices, I believe they are talking about the update to Froyo.
I guess this is the one main question I have:
Does anyone know -- or has anyone heard or read about -- a method to get temporary root on a MT4G with stock Gingerbread 2.3.4 using only the emulator???
Thanks... I am going crazy without root, and as said, I really want to avoid (as I am on a tight budget) purchasing another usb cable for $40, just to get a temp root.
I will try to sort out the issue as simple as i can
1. There is no method right now to root the 2.3.4 upgrade (even temproot).
2. To enjoy root access, you need to downgrade to Froyo (stock 2.2.1)
3. Do Permroot and then upgrade to GingerBread 2.3.4 or 2.3.5
4. Every post related to rooting is based on the stock Froyo Rom.
To downgrade, follow this post. Select the option best suited to you.
Also don't spent $40 for an OEM data cable. A replacement cable is available at price tag as low as $0.99
Just go to ebay & search for "micro usb cable". Just go through this link.
Have you installed the "HTC_drivers" file that comes on the root of the sdcard?
Possibly the reason why windows doesn't see it.
Or Make sure "USB Debugging" is enabled..
Not saying you haven't done either. Just putting it out there.
Sent from my HTC Glacier using xda premium
Thanks mahato... But yes. I have loaded the htc drivers, htc sync, pdanet.... All of them. Plus, I know all about usb debugging and it is on.
I have had it with this problem. The other thing that drives me crazy about my issue (which is why my phone was replaced in the first place, is that wifi calling keeps dropping), is that in my comprehensive research, I read one person's post that said that they confirmed that their 911 address needed to be filled out. Will I have done this and have done it through tmo. But I don't know if this was the problem, because I STILL KEEP GETTING THE DIALOG BOX which instructs me to complete my 911 address.
One more thing, since I need a cable to root this (which I know I can order cheaply), I might try to get a free usb cable from tmo...
But, before, I acquiesce to these problems and accept a new phone and just deal with it...
Can someone tell me how to confirm whether I have the ”bad chip” or ” bad screen”? I put a new screen protector on the new phone, and I thought that might be it, but I don't think so. My usual wall paper is the beautiful widgets living wallpaper which shows the blowing grass, etc.
However, when I look at my phone at an angle, the screen turns lighter, with practically zero contrast. I had read somewhere that this is a symptom, although I may be paranoid considering everything....
So does anyone know how to confirm a ” bad screen” or a ”bad chip” (I didn't even know there was a bad chip). Is there something I can check in the bootloader screen or something like that to confirm a component part number?
Sent from my HTC Glacier using xda premium
Reposted to new thread.
Ok, there are a lot of wrong statements in this thread and I don't have any time to cover them all.
Temp-rooting 2.3.4 requires running fre3vo. That's the only currently existing method.
fre3vo runs by exploiting msm_rotator.
I believe it's not documented whether the exploit absolutely requires link through ADB.
So, you could just try and see for yourself. In the worst case you'll discover that the temp root shell is given only to ADB and not to emulator.

[Q] Extremely confused Droid X GB - Need Help

So I've searched around the net, and am not 100% sure what to do. Here is my situation.
I "rooted" my phone awhile ago, or so I thought, but now despite having superuser and trying to do the fix and update for it, it doesn't work, and no app can gain root access, however when I try to run droid easy root, it says i'm already rooted.
I'm running GB with build # 4.5.1_57_DX5-35 (if that helps).
All I want to do is re-root or whatever and install a rom (miUi specifically) over the default gingerbread motoblur one. I'm on a Mac btw and don't know much about this stuff...Any help is appreciated.
mdemps9190 said:
So I've searched around the net, and am not 100% sure what to do. Here is my situation.
I "rooted" my phone awhile ago, or so I thought, but now despite having superuser and trying to do the fix and update for it, it doesn't work, and no app can gain root access, however when I try to run droid easy root, it says i'm already rooted.
I'm running GB with build # 4.5.1_57_DX5-35 (if that helps).
All I want to do is re-root or whatever and install a rom (miUi specifically) over the default gingerbread motoblur one. I'm on a Mac btw and don't know much about this stuff...Any help is appreciated.
Click to expand...
Click to collapse
use the zergrush (aka doomlord) method posted in my signature, should fix you right up
edit: eww just saw where you said you were on a mac, not sure if this will work for the mac, i know that superoneclick also now uses the zergrush method. perhaps there is a mac version of that.
I'll try it out using VMware fusion and my XP partition...Hopefully it works. Might have some questions on the process if there aren't detailed instructions. Thanks.

Trying to install update on my VZW Note 3.

Hello.
I have a towel rooted VZW Note 3. I'm trying to install the update but it keeps giving me a error message. Currently I have used the super Su and selected full unroot. And it still has the saresults. Any help would be great.
Chris
[email protected]
I'm in the same boat.. initially did towel root to get CM installed but my laptop wouldn't run Heimdall due to a dll issue I couldn't work out, so I never used root access. The update notification has been super pushy and obnoxious for several weeks now. I didn't realize SU had an unroot option but it looks to be moot?
EDIT: I went into SU and tried the unroot option. It gave a message about some kernals possibly rooting on their own again on boot so after SU closed I chose to start the software update now thinking it would go and do it's thing before the kernals could.... and it worked to upgrade it to 4.4.4
Maybe this needs some testing before I'd recommend it safely as I don't have an understanding of these things like I used to... I didn't even try to make a backup FFS
I'll give that a try thx
Sent from my SM-N900V using XDA Free mobile app

Categories

Resources