Database Info

Karbonn A9 adb root (FINAL HOPE)

​
Requirements and rooting process
1 > Your pitiable unrooted Karbonn A9 Android device
2 > ADB drivers for your device installed on your pc (I used WinXP. You may use Win 7/Vista or the Linux distro of your choice)
3 > su , busybox , Superuser.apk
4 > A working linux distro with Nautilus (use a live usb stick of Ubuntu 11.04)
5 > Strength, courage and whatever makes you a man !!!!!
Rooting Process
To start, you must have adb installed on the OS of your choice.
I used my trusty WinXP system .
To confirm your device is properly detected, in the command prompt , run -
CODE -
adb devices
Now copy busybox, su, superuser.apk to /data/local/tmp/ using adb.
CODE -
adb push busybox /data/local/tmp
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
Now run adb shell .
CODE -
adb shell
Note that you see a "$" sign in the command prompt. That means you are not rooted . Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
CODE -
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
Note that the names of the files are case sensitive.
Done?
Turn off your Android device using the power button.
Now you need to reboot your system into a Linux distro which has Nautilus.
Android and Linux, having a similar heritage, makes it possible for us to get root access over the Android phone if you are running with root privileges within Linux. I used an Ubuntu 11.04 Live USB disk to save the hassle of installing another os.
When you have booted into Linux, open up terminal and type:
CODE -
sudo nautilus
This would open up the Nautilus file browser with root privileges.
Now put your Android device into Download mode . for the karbonn A9 the method is to hold down the Volume up button and simultaneously turn on the phone using the power on switch.
Once in download mode, connect the Android device using the microusb cable to the computer.
Now using the open Nautilus window, navigate to /UserData/local/tmp/ folder and verify that you have the files you sent to the device viz. su, busybox and Superuser.apk
Move/cut-paste su and busybox to /system/bin/ using Nautilus.
Move/cut-paste Superuser.apk to /system/app/ using Nautilus.
Now pull out the battery from your Android device.
Now simply turn on your device.
You must now have root.
Verify by running:
CODE -
adb shell
su
You'll note that the "$" prompt will turn into a "#" and you'll be prompted by a Superuser permission notification on your
device
WOOHOO !!!! YOU NOW HAVE ROOT ON YOUR PHONE !!!!
​

Important -
​1 > For all purposes, consider that your warranty will be void if you follow these steps
2 > I am not responsible for any loss, monetary or otherwise arising as a result of this article.
If you don't feel up to it, quit now and close this web page .
3 > I must assert that although I am aware of no reason why this should not work on *any* Android device, phone or tablet, I have only tested this on my GALAXY s3 .
4 > I have tried to explain it in the easiest way I can, but I must state here that this is by no means an easy task and you must persevere. If you can't follow the steps to the letter, its better you don't follow them at all and wait for a single click app for this or a custom rooted firmware.
​

RESERVED
reserved .......................

RESERVED
reserved .......................

Doesnt work,Already tried it a week ago.
THis technique doesnt work.I have already tried it a week ago.
here's the original link:
http://www.erodov.com/forums/how-root-any-android-device-manually/43325-page2.html
The problem is that nautilus just wont list our device's folders.
And download mode is opened by pressing Vol down + power for A9,
Vol up + Power opens fastboot.

Useful one touch pixi 4007E rooting and shell commands

+ Alcatel one touch pixi 4007E
+ Firmware Version: 2.3.6
+ Baseband Version: 6575M
+ Kernel Version: 2.6.35.7
+ Build number: GINGERBREAD
Useful shell commands
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod -R 755 <dir>
{ :;}; su
rm custpack/app/withlibs/Gmail.apk
rm custpack/app/withlibs/UNO3_20130613_100_gl_global.apk
rm custpack/app/withlibs/OnetouchLive_PIXO_20130723_V2.7_AMERICAS.apk
cd /data/data/com.bcmon.bcmon/files/tools
svc wifi enable
svc wifi disable
uname -a
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
I hope these links are still valid, all is good and working October 5th, 2014, if any links die, please contact me and i'll see if i still have a copy of the files in a backup.
Device was rooted using the following software, from tutorial with these listed steps (below, cannot post links yet sorry) :
Software: Vroot App – VRoot_1.4.2.3195_Setup_95.exe @ a TinyURL
Tutorial: the root-alcatel-one-touch-pixi from ninjaromeo
Steps:
Make sure you have downloaded the above file.
Install it on your PC or Laptop.
Make sure that you have installed USB Drivers on your PC.
Then Open the installed program.
Now connect the phone to Computer using Original USB data cable that you got it when you bought the phone. Because using other kind of cables may not be detected by the computer. So only we are recommending to use the original.
Make sure that USB debugging is enabled on your phone.
Then wait for the Vroot to detect the device.
After that click the green button.
Then in a few seconds your mobile will be rebooted.
When it reboots your device must be rooted.
Then go to the Google Play store and download the SuperUser app or update it.
Now your mobile has been rooted successfully.
Then you can remove the phone from the Computer.
Normally first boot take some long time to complete. It will install the updates on the first boot. So, wait un till it finishes the booting process.
If your phone has stuck on the welcome screen or boot screen, just remove the battery and re insert it and do the above steps again.
Additional (important) software installed:
Terminal Emulator for Android
Jack Palevich
- June 20, 2014
Phone is rooted without issue all software installed fine but bcmon.apk (for wireless monitor mode) is not functioning by out of box root but i am working on it, arghum... aircrack-ng also does not function out of the box, titanium backup functions correctly and phone appears to operate perfect after Gmail.apk (bloatware) was removed (after many super stressful hours of directory scanning and OS information gathering but not bad for $99 and some mind numbing research lol!).
Argh... will keep posted on bcmon
Current issue (October 06th, 2014 12:48AM EST +10) = <message>command: 'cp' failed with exitValue = 127</message>
so...
install the following BusyBox to help get bcmon to work on this device:
BusyBox X
Robert Nediyakalaparambil [root]
- August 8, 2014
and now bcmon records are as follows:
"<record>
<date>Oct 6, 2014 2:16:47 AM</date>
<millis>1412522207853</millis>
<sequence>9</sequence>
<logger>com.bcmon.bcmon.chipsets.BCM4330B2</logger>
<level>FINE</level>
<class>com.bcmon.bcmon.chipsets.Chipset</class>
<method>detect</method>
<thread>0</thread>
<message>return false</message>
</record>"
then... now... i have arghum... downloaded the entire bcm4330/ directory from bcmon googlecode /svn/trunk/ and simply copied to the phone's sdcard via usb mode.
opened terminal (on phone) in su mode, navigated to bcm4330/driver/src/bcmdhd/ and attempted to launch sh build.sh but now have the following error:
"can't cd to /data/data/jackpal.androidterm/app_HOME/android/system/kernel/samsung/smdk4210
make: command not found"
More of a note really, a side bit of information
... installed Android SDK (Eclipse) and prerequisites (Java 64bit, in Windows), with phone connected via usb, and sdcard usb mode disabled (card mounted on phone and not windows).
Simply extraced archive to desktop (C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702).
Within the extracted folder you will find the following directory (providing the same versions) "\sdk\platform-tools" and within there resides the adb.exe windows command line tool.
I have now opened a command-line window (cmd.exe) at this directory ("\sdk\platform-tools", held shift and right-clicked on folder, windows 7) and issued the following commands:
adb reboot
adb /proc
things appear to have executed perfect, so i CUT all files and folders from the directory "C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools" and pasted them into a new folder called "backup", i am now left with three files "adb.exe", "AdbWinApi.dll", "AdbWinUsbApi.dll" and one folder "\backup" in this directory...
i now re-execute the following command:
adb /proc
it would appear as though all the files that i CUT from this directory are in fact being rebuilt...
the adb.exe windows process finished with the result:
"31308 files pulled. 0 files skipped."
Click to expand...
Click to collapse
must say...
i dig this QR --> http://forum.xda-developers.com/member.php?u=1164149
and have concluded the following results.
bcmon is useless!, wifilog does not work on Alcatel one touch pixi 4007e but does on ZTE Telstra UNO T12, WiFiReaver, Wifi Analyzer and Wi-Fi Direct are all that is needed, in fact i have uninstalled bcmon and BusyBox.
Use mobiles to locate networks and normal means for wireless traversal, why else do people buy mobile phones?.
For an extra note on this model phone (and this will be posted in a separate thread) and help on removing apps manually (i had to do this as android would not allow me to uninstall and it was no longer listed as an installed app in Google Play )
I used the following commands (In Terminal Emulator) in this order to remove Wi-Fi Direct (in this case but same process should work for other apps) manually (remember this is only a backup of the app and not a complete removal in the phone system, bricks are not to be made but found, this merely removes the app from the android dashboard/desktop/app list)...
su
ls
cd system/app
ls
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
mv WifiWsdsrv.odex backupwifi/WifiWsdsrv.odex
mv WifiContactSync.odex backupwifi/WifiContactSync.odex
mv WifiContactSync.apk backupwifi/WifiContactSync.apk
mv WifiP2PWizardy.odex backupwifi/WifiP2PWizardy.odex
mv WifiP2PWizardy.apk backupwifi/WifiP2PWizardy.apk
And to actually remove the backupwifi folder (completely remove everything from system) issue the following command...
rm -r backupwifi
Click to expand...
Click to collapse

How do I adb pull root directories (like "/system"?) to my Windows PC??

Hi there, I'm trying to pull root directories like /system and /data without any luck. My purpose it to have them on my PC as a backup, and be able to browse them to pull out apps and pieces of data as necessary if it ever becomes necessary.
Device: Nexus 6P (North American version)
ROM: Stock 6.0.1 Rooted, using Wugfresh Nexus Root Toolkit and SuperSU
PC OS: Windows 7 PC (64 bit)
Adb is working properly and I can easily pull non-root directories like "/sdcard" and so on. I'd like to be able to backup the entire root directory ("/") or at least the child directories (like "/system" and "/data", etc.) Unfortunately, when I try
Code:
adb pull -p "/system" "C:\somewhere"
it skips a bunch of files, so I need to come up with a better method.
I've tried
Code:
adb root
and it tells me it's already running in root mode.
I try
Code:
adb remount
and it does this properly, but doesn't change the effects of all the commands I've tried.
When I run
Code:
adb shell
it enters shell and gives me # by default, so seemingly it is giving me su permission by default?
*** Oddly, when I enter "su" while in shell, it tells me "/sbin/sh: su: not found" which seems odd to me. I think it's possibly that SuperSU is installed as systemless root, or there's something else screwy here, so I guess I'm not sure how to proceed. Still, if that were case, why would adb already be running as root, and why would shell automatically give me the #?
Any help is appreciated!!
Thanks!

How to root Samsung S7 [SM-G930A]?

at&t phone, running android 8.0, i have odin and unlocked oem, also enabled usb debugging. i just need a root file for it or some other way

Android can be considered to be rooted if SU-binary is present. Hence
unlock bootloader if not done yet. Then by utilizing a mix of ADB and/or Fastboot commands
1. Disable VB 1.0 & VB 2.0 ( AKA AVB) and re-boot device
2. Copy a matching SU-binary ( either 32-bit or 64-bit ) to Android's directory data/local/tmp
3. Make the copied SU-binary executable & set its owner to 'root:shell'
4. By means of copied SU-binary mount Android's partition /system as RW
5. Copy copied SU-binary to Android's directory /system/bin & set its owner to 'root:shell'
At least I would do it this way.
SU-binaries can be downloaded from here:
SU
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

[Q] How to edit camera features file

I want to edit camera_features.xml file but it needs root access, I don't want to root device but I think there is a way through ADB or using some third party apps that uses super user permission to edit root files
Please I'm sure there is way to edit it without rooting device by using special third party apps but I need someone who know how to

Temporarily root Android by putting a suitable su binary into Android's filesystem - preferably /data/loca/temp - and making it executable.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/

I don't find the directory data/local
And does it require root to put the su file there

Noticed that I made a spelling mistake:
The directory recommended to copy su binary into is
/data/local/tmp
what exists on all Android versions since beginning and by default is mounted as RW

How can I reach the folder, which app can reach and copy files to root data/local/tmp without rooting device

You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.

I tried to use adb push su data/local/tmp but it doesn't work

xXx yYy said:
You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.
Click to expand...
Click to collapse
I know but I think there is another way using apps that uses system apps permissions
Such as editing root file of the device as official device updater