[Q] Fingerprint scanner TiBU - Atrix 4G General

Hi guys, I know there was a thread on here before about how to fix the fingerprint scanner after a bad restore in TiBU but for some reason those methods aren't working for me. I am using Terminal Emulator and when I enter in adb.exe shell it gives me an error and I can't get past there. Can someone please guide me through because I don't really feel like doing all this work to get back to 1.57 rooted again and then install all the extra goodies again as well
http://forum.xda-developers.com/showthread.php?t=977600
heres the thread

milesjohnson said:
Hi guys, I know there was a thread on here before about how to fix the fingerprint scanner after a bad restore in TiBU but for some reason those methods aren't working for me. I am using Terminal Emulator and when I enter in adb.exe shell it gives me an error and I can't get past there. Can someone please guide me through because I don't really feel like doing all this work to get back to 1.57 rooted again and then install all the extra goodies again as well
http://forum.xda-developers.com/showthread.php?t=977600
heres the thread
Click to expand...
Click to collapse
If you're using a terminal emulator on the phone it self then you skip the step that says adb.exe and just type su then everything else that follows
Sent from my MB860 using XDA Premium App

Related

EVO 4G & Hero Root & the Eris

Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
jvward said:
Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
Click to expand...
Click to collapse
well just plug in to your pc and go to your adb command window and enter adb remount
adb shell
if you get a # you have root...
jvward said:
Hi All,
I viewed the video posted by the Unrevoeked team a little while back about their EVO 4G root and it definitely caught my attention.
http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/comment-page-1/#comment-8123
I just noticed today they posted an update on the thread and a link to:
http://unrevoked.com/
If you follow the site they let you download unrevoked.apk
If this APK running in some way means we can root. Well It installs successfully and when you actually run it it says "done." So I believe it does what it is suppose to do on the Eris, I just dont know what steps to take from their.
I have tried installed 2 different superuser apks and neither seems to work. Not sure if I should be doing something else.
PS I am using unrooted OTA
Click to expand...
Click to collapse
By meaning neither one of them "work" you mean when you press on the app and all you see is a black screen thats all it will do until a program that requires root requires permission to do whatever the app was designed to do. Ohh usb debugging in setting->applications->Development-> USB debugging should be checked.
Hey,
I tested out ADB its not working and by not working I mean neither prompt for superuser permission.
doesnt work
It doesn't work sadly. The Dev's blog is shadowmite. com/blog/ (without the space) if you are looking for any followups though.
It looks like all it does is try and replace/write /system/bin/su but I can't entirely tell. This app is supposed to run something on boot so you may want to try rebooting. Also, it creates a log: /data/DxDrm/unrevoked.log

Can not open Terminal Emulator, keeps crashing

I have a Mytouch 4G
I have allready temprooted with R14
I am trying to permroot, but for some reason i can not get Terminal Emulator to run, everytime I start it, it just crashes/wont open.
Thanks for any help
Arley
Which terminal emulator program are you using? While this may not fix your problem, it may workaround if you use a different emulator program.
Have you installed RomManager? If so, you could run fix permissions to try to fix resolve the FC issue as well. I am not sure how well that works with temproot but it is worth a try.
Arley1337 said:
I have a Mytouch 4G
I have allready temprooted with R14
I am trying to permroot, but for some reason i can not get Terminal Emulator to run, everytime I start it, it just crashes/wont open.
Thanks for any help
Arley
Click to expand...
Click to collapse
have you tried creating multiple posts on a forum asking the same question until someone answers?
no sorry, one was from a different section and got moved here by a mod
Arley1337 said:
no sorry, one was from a different section and got moved here by a mod
Click to expand...
Click to collapse
I posted the answer you may be looking for in the other one

[Q] Quickest way to check if phone is still rooted?

I rooted yesterday, flashed a GB rom, and going to use the ShootMe app it's saying I'm not rooted and won't connect. Does flashing unroot the phone?
Unless you flash a stock update then flashing will not unroot your phone. All custom ROMs are rooted unless otherwise noted.
The easiest way to see if your still rooted is by opening up terminal and typing "su" without the quotes. It should change to a pound sign - if it say access denied then something went awry.
Code:
$su [ENTER]
#
That's how it should look.
Says Terminal Emulater was grandted superuser permissions but shootme still says it's not rooted. Signs that during the restore of the app something went wrong?
Check superuser to see if the app is being granted permission
Sent from my HTC Vision using XDA App
^ that worked. Thanks. I have another small issue and dont want to make another thread so hopefully someone can help with this as well... How do I take apps that are installed on the sd card and move them back to the phone itself?
settings>applications>manage applications
go to the app you wanna move, tap on it and then tap on move to phone

[Q] I dont have full root aces. Can you help me?

I have LG optimus one and Iam try new rom Omnirom beta 7 and beta 7.1. Iam saw ther isnt any superuser app and Iam try flash SuperSU (chainfire) and SuperUser (CloakWorkMod) with cwm recowery 6.4.0.6 and twrp 2.7.0.0.
Now I can run some apps like a total commander with superuser aces, Rom manager, but Iam style not can run titanium backup and lot of more. Sorry my English. Thanks for all reply.
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
thanks
chuSmu said:
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks Iam try it.
I am found error
chuwork54049883 said:
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This dont work
Iam dont saw a easy think. My result app hawe root aces but adb no.
How to repair. Settings -> for developers ( If you dont see it, you must go to settings -> About phone and seven times touch build number)
In setings you mustvote apps & adb in defoult only apps.

Gsam on Nougat - how to grant permissions to see all battery usage on all processes

I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Click to expand...
Click to collapse
That's it. No root necessary.
hachamacha said:
I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
That's it. No root necessary.
Click to expand...
Click to collapse
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?
droid27 said:
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?
Click to expand...
Click to collapse
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.
hachamacha said:
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.
Click to expand...
Click to collapse
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?
droid27 said:
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?
Click to expand...
Click to collapse
I've done it once when upgrading to b360 Nougat and it has held and worked fine through a few reboots and a number of system changes. So, .. once should do it, but I'd never expect it to outlast an upgrade of OS.
I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.
F1Fanatic27 said:
I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.
Click to expand...
Click to collapse
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.
hachamacha said:
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.
Click to expand...
Click to collapse
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
Did you "force-close" the app after you enabled storage and reenabled the android.permission.BATTERY_STATS? If so, other than uninstall/reinstall and try again, I'm not sure. Are you running stock OS? There can always be something quirky in anyone's install that I'll never figure out. Good luck.
The only thing I recall is that the command doesn't do anything until after you've executed it, force closed and re-started the app. If it doesn't work then, then something else is going on.
F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.
StewMaker said:
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.
Click to expand...
Click to collapse
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs
ayush rao said:
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.
StewMaker said:
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.
Click to expand...
Click to collapse
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs
ayush rao said:
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.
StewMaker said:
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.
Click to expand...
Click to collapse
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs
Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Mine worked until I rooted at which point root takes care of that problem without the shell command.
The one thing I can think of is that the command differs (I read this somewhere) if you have GSAMPRO rather than GSAM (by just a word) and you'd have to google the correct word and substitute it. I got this the first time I started GSAM in an unrooted environment and just noted it. It showed up in a dialogue box on GSAM.
What iam doing wrong? :
adb>adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
Edit: problem solved: I have the Pro version and so the item was: 'com.gsamlabs.bbm.pro'
ayush rao said:
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
That's no problem. Hey, a response is better than no response.
I wrote the actual application name, not the goes here. Just a placeholder.
Sorry, but what is there a way to run this command locally in the Android Terminal Emulator?

Categories

Resources