We use different apps to view our logged on wifi password.
Some of those sometimes don't work or sometimes you just don't want to install an app for solution.
Rooted and Non-rooted
Do you know where's your password get stored?
Here
Code:
root/data/misc/wifi/wpa_supplicant.conf
So,If u already rooted your phone,u simply can navigate to there using a file explorer.
(Example : Root Xplorer,Mixplorer etc)
And open wpa_supplicant.conf.
If you are not rooted than you can use this ADB commands.
Code:
adb pull/data/misc/wifi/wpa_supplicant.conf
C>:wpa_supplicant.conf
In most case,
OEMs don't give access to data folder without root.
For these people, I didn't see a solution.
Bye and Thanks for reading....
bump
Related
I followed the instructions posted in and successfully Rooted and updated the Kernel on my WiFi Xoom. but today when showing it to a co worker we found out the google books app wasn't functioning.
I tried replacing it from the market by logging into the web page after the market app would not find it and it will not let me put it on the Xoom. I then downloaded the WiFi dump that was made hoping to sideload the app and it says it's already installed. i tried uninstalling and it says it failed to uninstall.
So would anyone have any other ideas in getting the app reinstalled?
get root explorer, delete books from system/apps
Then use root explorer to place books from the dump zip into system/app
Once placed, check the permissions and make sure they are the same as the rest of the apps. Reboot
Didn't see your post in time i ended up doing a wipe and reinstall.
I have this problem also...is there another way to do it without root explorer? sftp or ssh?
bigworm50 said:
I have this problem also...is there another way to do it without root explorer? sftp or ssh?
Click to expand...
Click to collapse
Yes bigworm, there are other apps out there that allow you to drill down into the system partition (not sftp) as long as you have you root you can use most types of terminal or files system tools.
Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help
one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed
See the attached
appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.
keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.
Hello everyone, I don't want to root my device just yet due to the fact that it's still under warranty... So since I only want to remove ads, can you tell me if there's a way to block ads on an unroot device, like pushing the file on adb shell or something like that ? I don't want to use adblock plus it simply doesn't work.
Thanks in advance !
leomon32 said:
Hello everyone, I don't want to root my device just yet due to the fact that it's still under warranty... So since I only want to remove ads, can you tell me if there's a way to block ads on an unroot device, like pushing the file on adb shell or something like that ? I don't want to use adblock plus it simply doesn't work.
Thanks in advance !
Click to expand...
Click to collapse
There are only so many ways to replace a system (hosts in this case) file within Android and almost all of them require rooting the device or tripping Knox with TWRP. You might be able to do it with adb push/pull commands but that is quite an advanced technique. Even then, I've had it request root access in CM to run the adb commands on the system apps. In reality the easy ways to do it requires root and my advice would be to try using the adblock browser or another custom browser that blocks ads until you are ready to root it.
AlkaliV2 said:
There are only so many ways to replace a system (hosts in this case) file within Android and almost all of them require rooting the device or tripping Knox with TWRP. You might be able to do it with adb push/pull commands but that is quite an advanced technique. Even then, I've had it request root access in CM to run the adb commands on the system apps. In reality the easy ways to do it requires root and my advice would be to try using the adblock browser or another custom browser that blocks ads until you are ready to root it.
Click to expand...
Click to collapse
Thanks, that's actually just what I thought. It's weird because you can change the density and the resolution of that tablet with the adb push on the fly without root or knox tripping but I guess the whole file is read only and that's why root is needed (the hosts).
There is a proxy ad blocker on market. Works just fine and does not require root . search market and you find a few.
use hosts without root
I know a simple way to use hosts without root:
enter playstore
search: "virtual hosts"
you will see a green icon of the apk
download it
open it and then you will see a big switch button.
click on it and then choose the host that you want to use
(if you want to make the host to be on startup, just click the plus icon in the corner and then you will see an android icon. just click on it).
I have a big problem. I put a password in an application, which I unfortunately forgot, and the information in that application is very important to me.
I heard that by accessing the root of the phone and a specific file, that password can be deleted. Do you have information about this. Please help me.
Simorg11 said:
I have a big problem. I put a password in an application, which I unfortunately forgot, and the information in that application is very important to me.
I heard that by accessing the root of the phone and a specific file, that password can be deleted. Do you have information about this. Please help me.
Click to expand...
Click to collapse
If the password is stored on the device itself, it "should" be in data/data/"name of app".
Yes, it requires either rooting the device or installing TWRP custom recovery. If you root the device, you won't need TWRP, you can simply use a file manager with root permissions to delete the file containing the password. If you install TWRP, you will not need to root the device, you can use the file manager that is built into TWRP to delete the file containing the password. Although you don't necessarily "have to" have both TWRP and root, most devices have to use TWRP to root the device, they require using TWRP to root the device but do not require root in order to install TWRP recovery. I hope that isn't confusing.
As for how to root your device or install TWRP, that depends on your specific device model. You will have to unlock your bootloader if it is not already unlocked or you will not be able to install TWRP or root. To find known methods to root your device or install TWRP on your device, do some Google searches for:
"How to root (your specific model number"
And
"TWRP for (your specific model number)"
If there are known methods for your device, those searches will find guides with instructions. If those searches don't find anything, you will have to try using the "Magisk root" method. There is a thread here at XDA for Magisk root and instructions.
Droidriven said:
If the password is stored on the device itself, it "should" be in data/data/"name of app".
Yes, it requires either rooting the device or installing TWRP custom recovery. If you root the device, you won't need TWRP, you can simply use a file manager with root permissions to delete the file containing the password. If you install TWRP, you will not need to root the device, you can use the file manager that is built into TWRP to delete the file containing the password. Although you don't necessarily "have to" have both TWRP and root, most devices have to use TWRP to root the device, they require using TWRP to root the device but do not require root in order to install TWRP recovery. I hope that isn't confusing.
As for how to root your device or install TWRP, that depends on your specific device model. You will have to unlock your bootloader if it is not already unlocked or you will not be able to install TWRP or root. To find known methods to root your device or install TWRP on your device, do some Google searches for:
"How to root (your specific model number"
And
"TWRP for (your specific model number)"
If there are known methods for your device, those searches will find guides with instructions. If those searches don't find anything, you will have to try using the "Magisk root" method. There is a thread here at XDA for Magisk root and instructions.
Click to expand...
Click to collapse
Thank you very much for your guidance. How do I identify a password file?
Simorg11 said:
Thank you very much for your guidance. How do I identify a password file?
Click to expand...
Click to collapse
I don't have any idea what file name the app used when it created the password file. You will have to figure that out for yourself. I'm not going to do ALL the work and ALL the thinking for you.
Simorg11 said:
Thank you very much for your guidance. How do I identify a password file?
Click to expand...
Click to collapse
Is the app itself password protected with a default feature that is built into the app? Or did you use a feature that is built into your device's stock firmware or by using a 3rd party app?
Where the password is stored depends on which of these methods you used.
If you mean a password that the app requires you to input in order to sign in to an account or profile inside the app, then the password is probably not stored on your device, it is more likely stored in a server associated to the app.
Droidriven said:
Is the app itself password protected with a default feature that is built into the app? Or did you use a feature that is built into your device's stock firmware or by using a 3rd party app?
Where the password is stored depends on which of these methods you used.
If you mean a password that the app requires you to input in order to sign in to an account or profile inside the app, then the password is probably not stored on your device, it is more likely stored in a server associated to the app.
Click to expand...
Click to collapse
No, this app is a cryptocurrency wallet that does not have a centralized server, and I think the password is embedded in the app itself. Someone who can delete the file containing the password by a special program requested a large amount for its delivery, which I could not
Hi, I use root in all my devices from a lot of time but now I'm 41yo and no more interested in this.
I use root "now only" for
1) call recording (BCR);
2) SwifthBackup;
3) Revanced.
So, call recorder seems to be installed also without root: just put apk in system app directory!
... but, how I can move an apk in system directory without root or twrp, and with locked bootloader?
SwifthBackup can work without root? I don't remember but I can search.
Revanced isn't a problem, I can use with microG.
----
Any help about my doubts?
I want try also because VPN not work, and after a months of email with support "seems" can be related to unlocked/rooted device.
I want just try.
Ty.
Without root, Swift Backup can backup app APK files, but not the app data. It does allow you to grant adb permissions through Shizuku, but I never figured out what [if anything] that allows it to do. I wasn't able to backup app data with ADB privelages.
I don't know the answer to the Call Recording issue.
lupastro82 said:
Hi, I use root in all my devices from a lot of time but now I'm 41yo and no more interested in this.
I use root "now only" for
1) call recording (BCR);
2) SwifthBackup;
3) Revanced.
So, call recorder seems to be installed also without root: just put apk in system app directory!
... but, how I can move an apk in system directory without root or twrp, and with locked bootloader?
SwifthBackup can work without root? I don't remember but I can search.
Revanced isn't a problem, I can use with microG.
----
Any help about my doubts?
I want try also because VPN not work, and after a months of email with support "seems" can be related to unlocked/rooted device.
I want just try.
Ty.
Click to expand...
Click to collapse
I imagine that, once you move that .apk to the system app directory (while rooted), once you unroot, it should still stay there and probably be accessible; but I'm unsure whether successfully running it will be possible -- it depends on the call recording app and if the app requires root to run. If it doesn't and it simply needs root just to be inserted, then I imagine it would probably work if you unroot.
But I have never heard of this method of getting a mod or add-on to work by inserting it in the system app directory...it's fascinating...
Like you said, ReVanced doesn't necessarily need root to work; it just works better with it. Swift Backup will only in a basic way be able to back your device up without root access.
But if you are simply just trying to get a certain VPN to work -- and in the end you don't want to lose root -- you could try doing the numerous root-hiding methods. There are many games, banking apps, and streaming apps that won't work with root (without even giving you a warning that it's because of root detection sometimes) that, once you hide root successfully, are able to run it. It sounds like that could possibly be the case for your VPN.
There are these you can try (if you haven't yet); Zygisk Deny List, UniversalSafetyNetFix (Displax mod works best with P7P), Shamiko, HideMyApp, Magisk Delta, etc.
Also, please be aware (or reminded if you know already) that while unrooting will not wipe and reset your device, locking your bootloader requires wiping the device and you losing everything! You'll be able to get some stuff restored through Google One Backup/Sync, but most everything will need to be set back up and/or lost. And if all you are seeking is to get a VPN to work, I really highly doubt that the app/service goes so far as to detect if you have an unlocked bootloader; it seems there are some banking apps that go that far, but most apps out there don't go that far, and hearing a VPN does would be a first...
Good luck!
Just Google VPN. Do not work anymore from about two months and seems can be a root/unlocked issue.
Anyway, u're right. Ty so much.