Develop Bugs

How to verify your phone is "rooted"

Hi all,
I've recently flashed to MoDaCo 2.2 however I'm just assuming my device got rooted at the same time - but I don't know for sure.
What's the easiest way to verify it has been rooted?
Thanks!

1. use search forum or google..
2. adb shell su
thats it

It keeps saying device not found, but works for my mytouch and G1. Any ideas?

Breakthecycle2 said:
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Click to expand...
Click to collapse
Have you enabled USB debugging? Settings-Applications-Development

trice1921 said:
Have you enabled USB debugging? Settings-Applications-Development
Click to expand...
Click to collapse
Yup did that too...my other phones pick it up no issues.

I also get the exact same problem (i.e. Device not found) - I guess it is a hint that it isn't rooted maybe (although I assumed it was automatic with flashing MoDaCo 2.2)?

Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before

Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before

robboy said:
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Click to expand...
Click to collapse
OK I got a work around. You need to restore your PC to a point BEFORE you plug in your hero. I did this and now works great.

How I might undo root process?
I think that replace chmod 4755 permision to default in the "su" file, but I don't know how to
No need to do, but I'm intererested in the concept

There is a thread on how to unroot:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse

ZenorGR said:
There is a thread on how to unroot:
Click to expand...
Click to collapse
I'm sorry but could don't find ...Thanks!!!

its a sticky.. its really hard NOT to find it
edit: okay it WAS a sticky, but its also on the first site in this subforum.. so no problem to at least SEE it

Adb Problems? Read this.

--This thread is recommended to be viewed on a Pc/Linux (I included you guys too ), OR on your ANDROID-POWERED phone (with XDA or in browser now ).--
--This is for PC and LINUX problems.--
Hallo!
You may have adb errors such as: cannot connect to daemon. This is a common problem beginners commonly forget. Also MAKE SURE you have installed android sdk
If you get adb error like :
adb server is out of date * killing***
daemon still not running
error:cannot connect to daemon
Click to expand...
Click to collapse
That means your device can't be found in adb.
Simply:
1) Make sure USB debugging is on
Found in Settings>Applications>Development
Click to expand...
Click to collapse
2) Make sure you have YOUR PHONES DRIVERS INSTALLED.
They can be installed via HTC Sync.
Click to expand...
Click to collapse
3) Still not working? Instead of using the USB option Charge Only/Disk Drive.
Use HTC Sync USB option.
Click to expand...
Click to collapse
________________________
RUU Problem [May encounter in the future](Thanks miguelca)
--Not for RUU Setup exe.
Out of date daemon error
Click to expand...
Click to collapse
Step 1) Browser to your android sdk folder
Its probably in: C:\android-sdk-windows OR C:\Program Files (x86)\Android\android-sdk (In 64bit edition of windows) OR C:\Program Files\Android\android-sdk
Click to expand...
Click to collapse
Step 2) Enter the platform-tools folder
Its simple just press Platform-tools
Click to expand...
Click to collapse
Step 3) Copy all of the files except: Source.propties, NOTICE.txt, lib, renderscript folder.
Hold Ctrl-A then press the files, then when done right click and press copy.
Click to expand...
Click to collapse
Step 4) Browse to your RUU Folder, and paste the files there.
Enter the RUU folder, right click anywhere press paste (If asks to overwrite press yes.)
Click to expand...
Click to collapse
Step 5) Should be done now!
________________________
[Linux ADB Problems (Thanks Tectas)]
Hallo, now this part of the thread is about linux ADB Problems .
permission denied ?????????
Click to expand...
Click to collapse
If you use Linux and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
[B][I][U][COLOR="DarkOrange"][FONT="Lucida Sans Unicode"]adb kill-server
(be sure the path to the adb directory is inside the .Bashrc file or CD to the right directory)
adb start-server[/FONT][/COLOR][/U][/I][/B]
Afterwards you can exit to normal shell and use it like ever.
[End of thread. Please scroll up or down to read reply's, or to read on ]

One addidonal thing,
if you are an linux user and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
adb kill-server
(be sure the path to the adb directory is inside the .bashrc file or cd to the right directory)
adb start-server
to start the adbd in su context, afterwards you can exit to normal shell and use it like ever.

It's not as trivial as you say. I had the out of date daemon error while trying to update my phone with the 2.3.5 European RUU by football. The solution was to uncompress the RUU and replace the ADB executable and dll's with updated ones from the Android SDK I had installed. It had nothing to do with USB connections or settings. Probably the RUU wasn't prepared for Windows 7 x64 SP1... I guess.
Sent from my HTC Wildfire S A510e using XDA App

Thanks!
Updated the thread.

XDA_h3n said:
Updated the thread.
Click to expand...
Click to collapse
You're welcome!
Thank you for the nice thread, for updating it quickly and for crediting me too.
It's great when several experiences are compiled in a way that might help many other users.
That's what a community is all about.

My trick is Download Vroot on your Pc and it will install everything you need. (Might replace your current Root Manager if you don't cancel the process of it rooting.) Once you connect your phone to your pc with Vroot it's ask you to install a apk just click okay. Once you see the apk installed wait for it to get a green backrground with wire connected image. Then there you go. Sorry for my Bad English. Hope it Helps.

[Q] Problems with adb/fastboot after updating to Android 5.0.1

I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.

djr83 said:
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
Click to expand...
Click to collapse
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine

Heisenberg420 said:
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Click to expand...
Click to collapse
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.

djr83 said:
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
Click to expand...
Click to collapse
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device

Heisenberg420 said:
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Click to expand...
Click to collapse
Exactly, I'm not getting any devices.

djr83 said:
Exactly, I'm not getting any devices.
Click to expand...
Click to collapse
Have u enabled USB debugging in developer options?

Heisenberg420 said:
Have u enabled USB debugging in developer options?
Click to expand...
Click to collapse
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Edit: Tried another USB port on the computer and it's working now.

djr83 said:
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Click to expand...
Click to collapse
I'd say its the drivers. Try to reinstall
You can try adb over WiFi without the drivers, download an adb wireless app from the market, enable it, get the IP address of your phone in the app, then connect through adb
Adb connect <IP[emoji14]ORT HERE>
then try adb devices

adb disable-verity

SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?

atulclassic said:
SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?
Click to expand...
Click to collapse
It should not work on stock OOS as it is not a userdebug build.

MisterCoolBeans said:
It should not work on stock OOS as it is not a userdebug build.
Click to expand...
Click to collapse
but we can change it to userdebug build by modifying the build.prop

atulclassic said:
but we can change it to userdebug build by modifying the build.prop
Click to expand...
Click to collapse
You can try but I believe it won't work.

Our build prop has "ro.build.type=user", Did some searching and found several mods that required changing
"ro.build.type=user" to
"ro.build.type=userdebug"
Go ahead and try it and let us know if it works.

Generating a new adb key

Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards

MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?

After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk

ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.

Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?

MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h

When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all

Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!

MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem