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
Related
I just rooted the phone (I know this because I installed a screen shot app and it works) and I'm trying to copy a private app that is free off of my phone onto my computer. But, I cannot figure it out. Could someone please give me step-by-step instructions. I would really appreciate this.
It sounds like you have completed this process:
http://forum.xda-developers.com/showthread.php?t=581577
But read it and make sure you complete the last step to flash the recovery rom.
www.androidspin.com/downloads...roc-v1.2.3.img
He kind of botched the last command instead of:
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
it should be:
adb shell
cd /sdcard/
su
flash_image recovery recovery-RA-heroc-v1.2.3.img
Once you make sure this is done, turn of your phone and then hold Home button and press end button. This should load the recovery, choose Nandroid Backup once you are done backing up you will want to flash Modaco's 1.1 rom. More information can be found here:
http://forum.xda-developers.com/showthread.php?t=581846
Once this is done connect your phone to your pc, and open command prompt.
type in:
cd "the directory where the sdk is" \tools
then type:
If you are using appstosd with ext2 and fat32 partitioned sdcard:
adb pull /system/sd/app app
If you are using just fat32, no appstosd:
adb pull /data/app app
this will put all your apps into a directory named app in your \tools folder on your pc.
for private apps just replace app with app-private
alternatively, you can move apps one at a time with the command:
leave out " ".
adb pull /system/sd/app/"appname" "appname"
This will place the file directly into your tools directory. Hope this helps.
Yep, thats what I did. But I didn't flash the recovery rom. If I do that will it erase all my applicastion that I have installed? I didn't want to do that because the app I want to backup was free when I downloaded it but now it's not.
Ok, so I followed all the instructions above and go the in MoDaCo rom flashed. Then, when I tried to pull the apps off the sdcard I get a permissions denied error.
{
"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"
}
Thanks.
Now I have a new problem. It says "adb: not found". Now what?
Thanks for being so helpful everyone.
adb is a command that is run outside of the shell
for example your prompt would still be at
c:\android-sdk-windows\tools>adb pull /data/app-private (location)
you can't use adb inside of adb shell
Ah, I didn't know adb had to be run outside of the shell.
Now it says there aren't any files in app-private but I know there are two in there.
CyanogenMod BootAnimation
How to install
adb shell mount -o rw,remount /dev/block/mtdblock3/system
adb push bootanimation.zip /system/media
{
"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"
}
CyanogenMod BootAnimation
http://me-projects.googlecode.com/files/bootanimation.zip
http://www.youtube.com/user/mrjtz100#p/a/u/0/TuUYX8mmE7c
Where's the boot animation link?
all fix now
Looking at the images, it looks like the matrix style text works down properly; however, the cyan logo just sort of bounces around. Haven't installed it, so I might be wrong.
matrix style text works down and the cygen logo is jumping up and down but can fix that
Video for said boot animation incoming, I hopes?
the video is uploading now
pretty damn awesome
you can also push this to: /data/local/bootanimation.zip allowing it to persist after updating or reflashing
instead of pushing it to /system/media/bootanimation.zip
and btw, this one freaking rocks!
rikupw said:
you can also push this to: /data/local/bootanimation.zip allowing it to persist after updating or reflashing
instead of pushing it to /system/media/bootanimation.zip
and btw, this one freaking rocks!
Click to expand...
Click to collapse
Hi mate,
Is that what I think? Patching up the custom boot logo premanently that it won't effect only until a data wipe takes palce?
first step in process failed...please advise
Code:
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdblock3/system
* daemon not running. starting it now *
* daemon started successfully *
mount: can't find /dev/block/mtdblock3/system in /proc/mounts
nonmindo said:
first step in process failed...please advise
Code:
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdblock3/system
* daemon not running. starting it now *
* daemon started successfully *
mount: can't find /dev/block/mtdblock3/system in /proc/mounts
Click to expand...
Click to collapse
just type:
adb remount
nice, thanks
I tossed it in /data/local for obvious reasons and it works as advertised.
Very nice.
Is there a backup copy of the original boot animation, so we can revert it back?
deprecate said:
nice, thanks
I tossed it in /data/local for obvious reasons and it works as advertised.
Click to expand...
Click to collapse
Can you please explain the command in terminal?
Thanks ...
//
adb push for it to work
adb remount works just as well and is easier to remember and type.
edit: sorry didn't see it already provided.
Love this boot animation!! Pushed a couple around tonight and this one is my favorite and I will be sticking with it for some time!! Thanks a million!!
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?
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