all the exploits are just a bunch of c code and idk how to compile code
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting is the act of unlocking the Android OS to gain complete control over the device through which you can access hidden files, change the ROM or install certain special apps. Rooting Android OS simply means to add Superuser AKA Root functionality to it.
This Superuser functionality is part of every Linux OS distribution. Because Android OS is based on a Linux OS kernel, so all you what have to do is to add the SU binary to Android OS.
The most primitive method to achieve this is to run this command sequence on PC - what requires USB Debug option got enabled in Android OS:
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When it's needed to apply a shell command what requires elevated rights ( read: root rights ) then you in Android OS terminal app run
Code:
/data/local/tmp/su -c "SHELL-COMMAND-HERE>"
jwoegerbauer said:
Rooting is the act of unlocking the Android OS to gain complete control over the device through which you can access hidden files, change the ROM or install certain special apps. Rooting Android OS simply means to add Superuser AKA Root functionality to it.
This Superuser functionality is part of every Linux OS distribution. Because Android OS is based on a Linux OS kernel, so all you what have to do is to add the SU binary to Android OS.
The most primitive method to achieve this is to run this command sequence on PC - what requires USB Debug option got enabled in Android OS:
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When it's needed to apply a shell command what requires elevated rights ( read: root rights ) then you in Android OS terminal app run
Code:
/data/local/tmp/su -c "SHELL-COMMAND-HERE>"
Click to expand...
Click to collapse
it doesn't work like that
The most primitive method to achieve this is to run this command sequence on PC
snaptube vidmate
Related
Not sure if anyone has gotten one of these yet but I have been given one for some work so thought I would share my progress with it.
About
http://www.ippea.com/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Table of Contents
How to Root
How to Root
The iPPea comes with busybox built-in into the image. So unlike other devices we don’t have to compile/download busybox and deploy it - full access to all the busybox tools is available by default.
But what makes rooting really easy the iPPea has ro.secure off. This means that a simple adb connection is enough to grant root access - all that we have to do is install a su binary.
Unfortunately, the busybox su requires too much baggage of the traditional Linux system - notably /etc/passwd, /etc/groups and friends to work. Since this is a MIPS system and Superuser.apk is contains an ARM binary, that approach cannot work either. In addition, compiling su-binary from Superuser.apk requires the entire AOSP tree, which is too much work and network bandwidth for us. So, we will use a portable C implementation of su instead.
This step does require you to plug in the iPPea into a computer with ADB, so be prepared to do so. You will also need this prebuilt portable MIPS Android su binary.
Now that you have the ‘su’ binary handy as well as your iPPea detected in adb (adb devices, you may need to chown it to make it visible), here we go:
Code:
adb push su /dev/
adb shell
# now we are on the iPPea
busybox mount -o remount,rw /system
busybox mv /dev/su /system/bin/su
busybox chmod 4755 /system/bin/su
busybox mount -o remount,ro /system
exit
# now we are back to our computer
adb reboot # to reboot
Credits to: Compdigitec
Useful Links + more Info
Here you will find useful links for the ippea and places to find more information
Change log
09/02/2012
Started thread
Added how to root
The following procedure has been tested by me only on ZP950 + 16GB model. Although the procedure is created generally for the MTK6589 processor and it has been already tested on other devices, could / should also work for other devices based on MTK quad-core processor.
!! Important !!
Success with this application void warranty on your device.
The procedure is based on exploits found by motochopper and the necessary files can be downloaded from here
The procedure works on both linux (run.sh) and Windows (run.bat).
Here are the steps to follow:
Download and unzip the package into a folder
Enable USB debugging on your device. Check that using the command adb devices your device is seen.
Open a DOS window (or in case of linux the unix shell) on the new extracted folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disconnect the device from the PC, run the run.bat command and press enter.
The program will wait for the device. Then connect your device to the PC
The program will upload the necessary programs, install the exploit and SuperSU.apk and after will launch the exploit to enable root permissions.
When the process is finished, press a button and the program will restart the phone
When the phone is rebooted you will have the root permission and SuperSU application installed.
At first launch of the program will ask you to perform an upgrade to a newer version.
To test whether the procedure for root works, connect the terminal to the PC and type the commands
Code:
adb shell
at the shell prompt given command
Code:
su
The SuperSU app will ask you whether to grant root permissions or not, and once accepted, the shell prompt will change from $ to #.
Tested on my zp950+ Build number 20130427-162946
Reserved for future use
Recovery
The recovery partition is only 6 mb so, some latest recovery don't fit in partition and cant'be installed.
(To be honest, there is a procedure that allow you to increase the recovery partition but you must shift all other partitions and reflash all, but is very dangerous and i am not sure about it).
Here there is an adapted version of CWM (6.0.3.0) that works with the default partion size.
PS: Your device must be rooted, and i am not resposabile of damage to your phone.
The steps are:
Downloa the recovery from here
Conncet the device to pc, open a shell (or dos) where you have downloaded the recovery and run this commands:
Code:
adb push cwm-6.0.3.0-zp950.img /sdcard/
adb shell
su
dd if=/sdcard/cwm-6.0.3.0-zp950.img of=/dev/recovery
This will copy the new recovery on your sdcard,
open a shell on your phone and get the root grants
flash (manually) the new recovery into recovery partition
After the operation ends, you can type
Code:
adb reboot recovery
to reboot the phone in recovery mode, on power off it and restart it pressing POWER_ON and VOLUME_UP together.
PS: here there is the default (stock) recovery for who wants to restore it.
I was working in Android Studio and accidentally locked my Android Folder containing the Sdk, I re gave myself the permissions and unlocked it but when I try to reopen my android project it stays stuck on loading project.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried restarting my computer(linux) and running ./studio.sh but it is still not loading.
I am also seeing in the terminal:
2021-03-19 12:48:57,346 [ 56749] WARN - Container.ComponentManagerImpl - Do not use constructor injection (requestorClass=com.android.tools.idea.apk.issues.SetupIssueReporter)
first, glad to see you use programming on linux, i encourage you continue using it and learn it
that "WARN", is normal when starting studio from command line.
check in ~/HOME/AndroidStudioProjects directory, (if you allowed android studio to install location for projects in ~/HOME/AndroidStudioProjects, and in ~/HOME directory check if you have "Android" directory, there is located Sdk tools.
check permissions for directories, just check this website , cd (open directory, terminal command) to ~/HOME/AndroidStudioProjects;
Code:
~/HOME/AndroidStudioProjects
, and check permissions via
Code:
ls -l
, or
Code:
cd AndroidStudioProjects
to get deeper into, to list project directories you have, and check their permissions, they need to have write, and read permissions for owner at least
And replace ~/HOME, with your name you use in linux, if command don't work, so not to get confused there
indestructible master said:
first, glad to see you use programming on linux, i encourage you continue using it and learn it
that "WARN", is normal when starting studio from command line.
check in ~/HOME/AndroidStudioProjects directory, (if you allowed android studio to install location for projects in ~/HOME/AndroidStudioProjects, and in ~/HOME directory check if you have "Android" directory, there is located Sdk tools.
check permissions for directories, just check this website , cd (open directory, terminal command) to ~/HOME/AndroidStudioProjects;
Code:
~/HOME/AndroidStudioProjects
, and check permissions via
Code:
ls -l
, or
Code:
cd AndroidStudioProjects
to get deeper into, to list project directories you have, and check their permissions, they need to have write, and read permissions for owner at least
And replace ~/HOME, with your name you use in linux, if command don't work, so not to get confused there
Click to expand...
Click to collapse
Thanks so much for you help and encouragement for programming with linux!
I checked the permissions of the folder and am seeing:
Code:
drwxrwxr-x
Which I think means that I have permissions for this folder.
yjay18 said:
I was working in Android Studio and accidentally locked my Android Folder containing the Sdk, I re gave myself the permissions and unlocked it but when I try to reopen my android project it stays stuck on loading project.
View attachment 5254367
I have tried restarting my computer(linux) and running ./studio.sh but it is still not loading.
I am also seeing in the terminal:
2021-03-19 12:48:57,346 [ 56749] WARN - Container.ComponentManagerImpl - Do not use constructor injection (requestorClass=com.android.tools.idea.apk.issues.SetupIssueReporter)
Click to expand...
Click to collapse
I keep reading a lot of posts when I first get into trouble. This is how I once reached this website ( https://kodlogs.net/329/android-studio-stuck-on-installing-apk ) and got the desired solution. You can read this post as well as visit here. I think it will be very useful for you
I am ultra noob, so can anyone take a look at the following link for me.
And post a detailed guide.
https://www.pentestpartners.com/security-blog/cracking-android-passwords-a-how-to/
Thanks
P.S. I need this for my own phone and not for illegal stuff.
If your phone's Android is rooted
&
If your phone can get accessed by means of ADB
then
you can open Android's SQLite database named /data/system/locksettings.db via ADB
Code:
adb devices
adb shell
mount -t auto -o rw,remount /data/system
sqlite3 /data/system/locksettings.db
and do the database query as mentioned in the article linked to.
@jwoegerbauer this is what it shows
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some things to mention.
1.My phone is locked.
2.By default it goes to USB tethering mode upon connecting to my PC(I changed the setting in DEV mode)
3. It is rooted
4. It has orange fox recovery installed
5. Again I am a noob right now (won't remain that way for too long) and need a tutorial of some kind to do this successfully.
6. I do not know SQL and so how to use it either, and for that matter Hashcat too.
The blog still remains difficult for me.
Thanks again
Line
Code:
mount -t auto -o rw,remount /data/system
should read as
Code:
mount -t auto -o rw,remount /data
Nothing
I see today is not my best day.
This should work
Code:
adb devices
adb shell
su -c 'mount -t auto -o rw,remount /data'
sqlite3 /data/system/locksettings.db
Still not working @jwoegerbauer
Is there any other way such as doing all this in recovery mode or using terminal in orange fox
or adb sidelode or something.
sa1 said:
View attachment 5307221
Click to expand...
Click to collapse
My guess is that your phone 's Android isn't properly rooted.
@jwoegerbauer what does properly rooted mean. All apps that require root works properly.
SubwayChamp said : If you are in Android 10 system can't be mounted the suggested way, you also said that device is locked but is rooted (?). Orange Fox recovery has inbuilt an add-on feature that can do that.
Here : https://forum.xda-developers.com/t/help-thread-ask-any-question-noob-friendly.2257421/post-85003273
sa1 said:
@jwoegerbauer what does properly rooted mean. All apps that require root works properly.
Click to expand...
Click to collapse
It's not interesting here whether apps that require root work or not. In your case it is only important whether SU-binary can be found by the system.
Anyway:
Some newer Android builds require the following additional ADB commands to be run first to disable Android's AVB-lock
Code:
adb root
adb disable-verity
adb reboot
adb wait-for-device
Try this. Then run commands as listed above.
FYI: I no longer participate this thread. Have a nice day.
This is what it shows
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Grant Root Privileges to Regular Users Using Devices With Android 6 and up by Simply Upgrading Android's Multi-command Applet Toybox.
Preface:
THIS TOOL MAKES USE OF ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON AND ADB IS NOT INSTALLED ON YOUR WINDOWS COMPUTER, THEN IT WILL NOT BE OF ANY USE.
What does it do?
THIS TOOL MODIFIES ANDROID'S MULTI-COMMAND APPLET TOYBOX BY REPLACING IT BY ITS FULL VERSION - MEANS BY ITS VERSION THAT HAS SU COMMAND INCORPORATED.
Screenshot:
Download:
Usage:
Unpack the downloaded ZIP to any location on your Windows computer, run the script named Toybox-Updater.bat located therein.
Disclaimer:
This program is offered AS IS.
I do not warrant the functions in the program will meet your requirements or that the operation of the program will be uninterrupted or error-free.
In no event I am liable to you for any damages, including any lost data or other incidental or consequential damage.
Please don’t hesitate to report here any issues you may have with this tool! Thanks & enjoy!
In Linux, what Android is based on, the su (read: switch user) command is used to run a command as a different user, means the su command is used to run an OS function as a different user. It is the easiest way to switch or change to the administrative account in the current logged in session.
So using su to temporarily act as a root user - a root account is a master administrator account with full access and permissions in the system - allows you to bypass any default user-restrictions and perform different tasks with full permissions.
Because most Android versions by defaut use limited user accounts for normal use - making the system more secure - what restricts the user from running specific OS commands, the tool provided herewith adds su command to Android, what allows the currently logged in user to temporarily act as a root user - take note that a root account is a master administrator account with full access and permissions in the system.
su Command Syntax
To use the su command, enter it into a Windows command-line as follows:
Code:
adb shell "toybox su -c '[options] [username [arguments]]'"
Take note that if [username] is omitted su defaults to the superuser (in Linux term: root).
Hi, I came across this from another post where the user was trying to get su in his a022f. I have the same device and would like to achieve the same result. Unfortunately, I can't seem to find the zip file (there's no link to dl), or is it still being worked on, hence the absence of a link?