Database Info

[Q] Rooting Parrot Car Stereo - rageagainstthecage exploit works, but how to proceed?

Hey guys,
I'm proud owner of a Parrot Asteroid car stereo, which is based on Android 1.5
My attemps to gain full root, had no success yet but I hope to find some help here on the forums.
This is what I've done yet:
As I don't have any ADB access (no LAN/WLAN and only USB-Hosts), I've installed a terminal emulator on the device and attached a usb keyboard.
This way, I was able to copy the rageagainstthecage-arm5.bin exploit file on the device (/tmp) and run it. Restarting the terminal emulator brings up the root access.
So the next step would be a modified su binary and a superuser.apk app.
I could remount /system without problems and copy the superuser.apk onto it, giving it the proper rights to run.
But what to do with the su binary?
Problem: the car stereo is using a busybox which includes su and sulogin.
- Where should I copy the su file to? (I assumed /system/xbin/su)
- What else do I need to do? (I tried already symlinking the file to /system/bin/su)
- Any other rhoughts?
Thanks for any help on this!
-gforums

OMG I can´t Root!!!

Hello guys,
So, I am extremely frustrated with LG. Besides linger for a lifetime upgrade their phones, yet it seems to create some blocking to simple process root.
I've been researching on the web about the root of Optimus Black (the unit is good, what is bad is the LG) and all processes seem to be complicated.
I need help from you guys to see if I can finally give this blessed root to my device. He is with version 2.3.4 (just the model is P970h),the firmware is the V20a. I Want to apply a custom rom and play with it a bit, since LG has not given up any indicative of whether or not to launch the ICS on it (maybe who knows when Google launched Android 12.1, or the man get to Mars. ..)
I have faced some problems and I will report here to see if they can help me.
Problem # 1:
I can not under any circumstances recognize the phone on my pc (win vista home basic ¬ ¬).
I've tried everything. I downloaded the drivers directly with LG and nothing ... I downloaded the personnel that provided the xda forum and nothing ...The windows is insistently asking such a CDC serial driver (something of the sort ...) and the phone just not recognized.
Already installed, reinstalled the drivers and nothing! I have installed the LG PC sync and nothing to .. (Seems that my phone and my pc just does not want to share the same connection!)
I don´t have another pc (unfortunately) so I can´t install the drivers.
Simply for this reason I can´t install Clockworkmod, or do any procedure that requires root install drivers on pc (root unlock, blackjack, oneclick...)
2nd Problem:
I've been reading that there is a apk root tools for the phone, the Gingerbreak. But apparently this not works on my phone. It is infinitely loading and does not reboot.
I installed the 1.1 and 1.2 versions and nothing!
I run the Root Checker Pro App and get the log:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x shell shell 0 2012-08-29 23:49 su
Analysis: Setuid attribute present BUT root user ownership NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your LG-P970h device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market
Click to expand...
Click to collapse
So can anybody help me to root my phone??

Don't have an LG, i have an Samsung and rooted with this app SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682), and searching through the forum i saw this thread ( http://forum.xda-developers.com/showthread.php?p=22495442&highlight=optimus+black#post22495442 ), a user that succeeded root of an Lg Optimus Black.
But I only have an Samsung so I can't guarantee that will work.
Hope to have helped.
Best regards!

Wo retusou
pjm_9 said:
Don't have an LG, i have an Samsung and rooted with this app SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682), and searching through the forum i saw this thread ( http://forum.xda-developers.com/showthread.php?p=22495442&highlight=optimus+black#post22495442 ), a user that succeeded root of an Lg Optimus Black.
But I only have an Samsung so I can't guarantee that will work.
Hope to have helped.
Best regards!
Click to expand...
Click to collapse
So,
I can´t connect my phone to my pc... I don´t know why!!

Anyone can help me?
Sent from my GT-P6800 using xda app-developers app

Here's what I did.
I was having the same problem, seemingly. I went to Android Central and learned about an app called kingo root.
First, I went to LG and downloaded the drivers for USB connection to my Win7 64 PC. After they loaded, I made sure the E980 was configured to install programs from PC via USB, instead of charge only. Also, I set debugging on. Then, I hooked up the USB cable. Then, a window came up asking if I wanted to use LG Programs, which I replied OK. Then it said I was connected successfully. Went to the PC, installed kingo root (google it) and it ran a program or two that rooted the device. Piece o' cake!
Since then, I downloaded freegee and twrp, rebooted into recovery and installed CM11. KitKat goodness!
Ken

SSHFS on Android - Extend Android features with Debian KIT

HI,
I would like to share the way how I mounted my NAS folders with SSHFS based on Debian KIT.
SSH-FS is ssh based mountable file system. If you have SSH account you can mount and access that server like a windows share.
Forewords:
Debian KIT is free! and it is _NOT_ yet another chroot debian!
This method is an alternative and FREE way to have SSHFS vs to the unique native Android SSHFS app (which is unfortunately paid. )
It is fully integrated with Androitd! Less ram resources and faster than chroot. Debian libraries are binded to Android.
So you enjoy Android and Debian advantages all together.
Steps to have SSHFS:
Set up Debian on your Android! Go to Debian Kit page and set up Debian!
Run Debian. Open Terminal Emulator and type
Code:
$deb
$sudo su
Set up SSHFS
Code:
#apt-get update
#apt-get install sshfs
Mount SSHFS
Code:
#mkdir /mnt/nas
#sshfs [email protected]:/ /mnt/nas/ -o allow_other
Checking mount:
Code:
#mount
[email protected]:/ on /mnt/nas type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=65536)
Then SSHFS will ask your root password and that all!
If no error then its ok, You Mounted!!
You done! :laugh:
Go back to Android and use your mounted share with any Android file manager under /mnt/nas (or where ever you mounted.)
Finishing all, just
Code:
#deb u
(It will umount and close debian session.)
For more comfort, set up password-less login to ssh server with authorized_keys.
#ssh-keygen
#cat ~/.ssh/id_rsa.pub >> /mnt/nas/root/.ssh/authorized_keys
#chmod 600 /mnt/nas/root/.ssh/authorized_keys
After above steps your ssh server wont ask root password from this site to that site logging in with root user.
Press "Thanks" button if its helps for you.
Regards
Robert

Convert docs to pdf with Openoffice within Debian Kit
Another great usage example of Debian kit:
Use your installed Open/Libre/Star/Office to convert your document to pdf:
#!/bin/bash
time soffice --headless --convert-to pdf $1
exit
Check your doc converted to pdf after a minute.

Thanks for the awesome guide. Any idea about mounting virtual drives from my Ubuntu?

whu007 said:
Thanks for the awesome guide. Any idea about mounting virtual drives from my Ubuntu?
Click to expand...
Click to collapse
Hi,
thanks.
>mounting virtual drive...
Can you please describe a little, what is the scenario?
Regards Robert

SSHFS problems @ Android 4.2.2 Nexus 10 - apps cannot see mounted content
Hi,
Robert, thanks for the guide to sshfs with debian-kit. I've been longing to get sshfs on my Android for three years
My problem is that Android Apps cannot see the mounted content, which is what I desire.
I have managed to get debian-kit + sshfs installed, and my nas mounted using sshfs. I can browse the files on the nas from the mounted directory in the ConnectBot Shell, but I cannot see the mounted directory through android apps (or adb shell), eg TotalCommander, OI FileManager, MX video player. I have tried the TotalCommander Android app, and tried telling TotalCommander to always use root (in case user made a difference).
I mounted the nas using ConnectBot local shell with the command:
> sshfs [email protected]:/mnt/user/ /mnt/tower/ -o allow_other
I can see the /mnt/tower content both with the ConnectBot shell as normal user ([email protected]), as root, and with the shell I get after running 'deb' from a ConnectBot shell.
If I remote login from PC to an SSHDroid server on the Android, then I cannot see the mounted content of /mnt/tower (even as root). Neither can Android apps. If I install the openssh-server in debian and stop the SSHDroid server, then I can see the /mnt/tower content from my ssh login from PC.
Best Alex

I've an issue, after mounting the nas folder I try to add it into the Poweramp library, it recognizes it (I've mounted into /sdcard/nas) but none of the mp3 is added to library
thank you

Thanks for the great guide!
Now how can you unmount the SSHFS directory?
The normal way is with:
Code:
fusermount -u /mnt/share
However this causes an error:
Code:
fusermount: failed to bind parent to /: Invalid argument
Does that happen for everyone or is it just me?
Restarting the Debian system with
Code:
deb -u
also did not cause the SSHFS directory to unmount.
Sent from my Nexus 4 using xda app-developers app

Hi
Just try umount /mnt/mountpoint.
Robert
Sent from my GT-N8013 using xda app-developers app

Thank you for this guide! Unfortunately this solution isn't quite what I'm looking for. I found that in order to get my apps to recognize the mounted share I have to first run the app, then mount the share. Also, if the app gets killed I have to unmount the share and then remount it in order for the share to become visible again from within the android app. However, the share remains mounted when viewed from within the debian shell or adb.
Anyone have an idea why this might be happening?

Debian kit not working on S4
Hey, there. I have a rooted Samsung Galaxy S4 (VZW) running stock.
I get this error after all MD5 sums pass:
ash: id: Permission denied
Can someone please assist me or point me in the right direction?

aikeru said:
Hey, there. I have a rooted Samsung Galaxy S4 (VZW) running stock.
I get this error after all MD5 sums pass:
ash: id: Permission denied
Can someone please assist me or point me in the right direction?
Click to expand...
Click to collapse
did you get this right after you started installing? after you used the 'sh' command?
Sounds to me like you might not have root in android, or you didn't click the accept button when the app asked for root permissions.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
m2xtreme said:
Thank you for this guide! Unfortunately this solution isn't quite what I'm looking for. I found that in order to get my apps to recognize the mounted share I have to first run the app, then mount the share. Also, if the app gets killed I have to unmount the share and then remount it in order for the share to become visible again from within the android app. However, the share remains mounted when viewed from within the debian shell or adb.
Anyone have an idea why this might be happening?
Click to expand...
Click to collapse
I don't think there is much you can do to get around always having to have deb environment open. One way you might be able to kill a few steps is use the 'autofs' package in debian to automatically mount the sshfs share when you login to the debian envorinment.
I haven't tried autofs yet, but it's on my todo list, i'll report back with my findings.
---------- Post added at 11:19 AM ---------- Previous post was at 10:46 AM ----------
chrisonline1991 said:
I haven't tried autofs yet, but it's on my todo list, i'll report back with my findings.
Click to expand...
Click to collapse
So i had some problems running autofs and i can't seem to find the problem, maybe someone more knowledgeable can help. When i install autofs the output is below, but it looks like it did install fine.
Code:
Starting automount: Error: failed to load autofs4 module.
invoke-rc.d: initscript autofs, action "start" failed.
dpkg: error processing autofs5 (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
nfs-common
autofs5
E: Sub-process /usr/bin/dpkg returned an error code (1)
When i run
Code:
$ sudo dpkg --configure -a
it returns
Code:
Setting up nfs-common (1:1.2.2-4squeeze2) ...
insserv: warning: script '99CleanTWEAKS' missing LSB tags and overrides
Starting NFS common utilities: statd failed!
invoke-rc.d: initscript nfs-common, action "start" failed.
dpkg: error processing nfs-common (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up autofs5 (5.0.4-3.2) ...
insserv: warning: script '99CleanTWEAKS' missing LSB tags and overrides
Starting automount: Error: failed to load autofs4 module.
invoke-rc.d: initscript autofs, action "start" failed.
dpkg: error processing autofs5 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
nfs-common
autofs5
I found this bug report which points to this bug report that says something about the newest autofs using a new upstart feature called 'wait-for-state' and something is going wrong with it. Looks like they added the bugfix to Ubuntu Precise. And looks like that fix might now have solved the problem as another bug was opened, but i'm not sure if it's related to this. I'm a little burnt out on this at the moment.
Hope this helps someone. If anyone else has some suggestions let me know and i'll try them out.

Hi
I have been trying to get something like this working for awhile...
Any chance by using debian kit this can automatically run at startup and mount my PC to my Android device?

my android apps just see an empty dir. In my terminal the sshfs command works as expected. When I cd into the mounted directory I can see its contents, android apps just see an empty dir.
Has any one managed to solve this?

late-2017 update
bisbal said:
my android apps just see an empty dir. In my terminal the sshfs command works as expected. When I cd into the mounted directory I can see its contents, android apps just see an empty dir.
Has any one managed to solve this?
Click to expand...
Click to collapse
I ran into a thread on stack exchange that says to mount the sshfs-accessed shares to subdirectories of /data/media/0/. I've yet to try it myself, but it sounds plausible.
(https://android.stackexchange[dot]com/questions/50246/mount-inside-subdir-of-storage-emulated-0)
I was initially reluctant to raise an old topic, but I think this is important; being able to mount a remote data store to your local filesystem is crucial to the mobile environment as the tendency of well-known phone companies like Samsung and Apple in removing the external sd card feature (even my OnePlus 3 doesn't have it). I did consider the Nextbit Robin as my next phone for the smart data storage design, but opted out because of the aging hardware.

how to copy over busybox config file? (completelinuxinstaller)

Hello everyone.
I have been wanting to get to grips with linux for a while now and decided linux decided to try completelinuxinstaller as i was having some problems with linux deploy.
i set up everything as the app asked. Downloaded .img files, extract, rename file and launch.. but in the android terminal i get a error which said:
chroot: can't execute '/root/init.sh': Permission denied
After days of searching and trying minor fixes i got no where until i found a list of instructions on how to fix this error.
(This error is becoming common on Samsung devices running android version 4.4.2, and can be expected to happen with some other devices, or newer versions of android. Although I haven't yet found the exact cause of the error, an effective workaround has been found:
The error seems to be coming from something in the busybox executable installed by the Complete Linux Installer app; many have reported that using other versions of busybox removed this problem, and the following version (free download on Google Play) has been confirmed to work: BusyBox
After using that app to install an updated busybox binary, simply copy the new binary over the existing busybox binary at /data/data/com.zpwebsites.linuxonandroid/files/busybox
Finally, in a rooted terminal window, type chmod 0755 /data/data/com.zpwebsites.linuxonandroid/files/busybox (see the more detailed instructions in the How do I install the most up-to-date version of bootscript.sh on my device? section of this FAQ)
Now you should be able to start linux using your Complete Linux Installer app on your device.)
But the problem is no matter what explorer i use i am not able to find the busybox config file. Where they said it would be doesnt exist. Even if i go to android/data its not there. Just the .com for all other apps. do you know where the busybox might be ?. On the busybox installer it says it is in /system/xbin but again i cant find it on my device.
And if i may chew your ear off for one more moment. How can i change the .config file ?
Thank you for your time

X88 Pro 10 full access issues

Okay let me start by saying I have been modifying android boxes for several years so the question that I ask is not because I've never done it before. I recently purchased the X88 Pro 10 media box. It has Android 11 as the O/S, and the firmware for the device is from Oct. 2021. I turn on the developer options and try to access the device using ADBlink via the Ip address without success. I then connect the device to my laptop via a usb cable connection and I'm able to install an APK though my ability to go in and access or modify files and folders is limited. Has anyone else had this issue and what were you able to do to overcome the issue?

I just picked one of these up to use as an Android 11 test kit. Unfortunately, the developers who built the Android disabled wireless adb debugging! Luckily, the box is rooted at the factory so I was able to add it in. Connect via USB, su to root, mount / as rw (mount -o rw,remount / ) and add this line to the end of /system/build.prop
Code:
service.adb.tcp.port = 5555
This change to build.prop is persistent after resets so you only have to do it once.

I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.

ThirdStarr said:
I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.
Click to expand...
Click to collapse
Looking at your screenshot, it appears that you have successfully gained root access (the # prompt). Your next steps :
mount the / partition as rw:
Code:
mount -o rw,remount /
Add code to the end of /system/build.prop
Code:
echo "service.adb.tcp.port = 5555" >> /system/build.prop
mount the / partition as ro:
Code:
mount -o ro,remount /
This worked for me. YMMV

Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences

ThirdStarr said:
Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences
Click to expand...
Click to collapse
In the device record, check the "disable root" checkbox, save the record, then disconnect the device. When you reconnect the file manager should work.

I did as you suggested and rebooted the device.
I was only able to access this far in file manager

ThirdStarr said:
I did as you suggested and rebooted the device.
I was only able to access this far in file manager
Click to expand...
Click to collapse
For Android 11, Google has implemented scoped storage which removes the ability for external applications (or the normal shell) to read/write in /sdcard/Android/data/. You can still access this area via the shell as the root user. File manager won't work as root on this device, sorry.

Ok I understand. Thank you very much

Hello i'm on android 11, how i can use the root access? Doesn't work for me

I no longer have this device. Good luck!

hi i am kumar, regarding my x88 pro 10 android 11 i am facing a issue that i can connect to other hotspot or wifi network. i can't connect to my home wife that at the below of thw wifi name (check password and try again). i change my password in router page and try back with the new password still it shows like that. may i know why?