Database Info

[GUIDE][ROOT] Root almost any china android phone

Use any 1 of the following methods.
I have personally tried these on 2 of my china android phones.
1. Using linux {Recommended}Install Ubuntu or DebianEither
Install the android-sdk.
dl.google.com/android/adt/adt-bundle-linux-x86-20130717.zip <==x86
dl.google.com/android/adt/adt-bundle-linux-x86_64-20130717.zip <==x86_64
or
Just get the standalone adb and fastboot executables
texasice-cream-sandwich-mirror.googlecode.com/files/adb_fastboot.zip​Install ia32-libsRun this in a terminal
Code:
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
Now download the files required for root and put it in the same folder as adbmir.cr/GDEPZT4V​After you finish installing the files,
Connect your device with debugging mode enabled
Run
Code:
cd path/to/adb
where "path/to/adb" is the directory of your adb file
Now run
Code:
sudo chmod a+x adb
sudo chmod a+x fastboot
>>Root
Code:
./adb devices
./adb push psneuter /data/local/tmp/
./adb push busybox /data/local/tmp/
./adb push su /data/local/tmp/
./adb push Superuser.apk /data/local/tmp/
./adb shell
Chmod and run the exploit under adb shell
Code:
cd /data/local/tmp/
chmod 755 psneuter
./psneuter
Now re-engage an adb shell to check if the exploit worked.
Code:
./adb kill-server
./adb devices
./adb shell
If you see a # sign, the exploit was was successful. Otherwise repeat from >>Root
Now run these on the same adb shell
Code:
cd /data/local/tmp
./busybox ash
mount -o remount,rw /dev/block/mtdblock0 /system
cp /data/local/tmp/su /system/xbin/su
chmod 6755 /system/xbin/su
chown 0.0 /system/xbin/su
cp /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 777 /system/app/Superuser.apk
cp /data/local/tmp/busybox /system/xbin/busybox
chmod 6755 /system/xbin/busybox
Now reboot your device and open up SuperSU. Let it update the binary.
Your device should be rooted. ​2. Use Windows + MoboroboMethod 1 {Recommended but hard}
Download Moborobo from
Code:
moborobo.com
This software can Install drivers for many china phones and other branded phones.
After installing Moborobo download the files required for root
Code:
mir.cr/GDEPZT4V
Extract the files to the installation directory of Moborobo.
Code:
C:\Program Files (x86)\Moborobo
Run a CMD window under that directory and type
Code:
xcopy AndroidInterface.exe adb.exe
Connect your device in debugging mode & Open up Moborobo, It will install the drivers.
Keep Moborobo open & Follow the instructions mentioned in >>Root
P.S- the linux commands begin with a "./" remove this in windows or else it won't work. Note: Wherever I mentioned a terminal, the windows equivalent to this would be cmd​Method 2 {Easier}
Download and Install Moborobo just like above and run this under a cmd on that folder
Code:
xcopy AndroidInterface.exe adb.exe
Also download UnlockRoot or SuperOneClick
To make sure the adb files are of the same version, Copy over
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
to UnlockRoot's tools directory or SOC's ADB directory
Connect your device in debugging mode and open up moborobo.
Now keep Moborobo open and Run UnlockRoot or SOC. ​Good Luck :good:
---Smo0thK, team BL4CKF1R3---
Click thanks if I helped you.
[/COLOR]

Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....

>>Root
arena1 said:
Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....
Click to expand...
Click to collapse
I said follow the instructions mentioned in ">>Root".
I named a step in Method one as ">>Root". So I meant you should repeat those steps.

Now download the files required for root and put it in the same folder as adb
mir.cr/GDEPZT4V
Click to expand...
Click to collapse
What files?
EDIT: managed to do all the steps using method 1 in windows but got this message with executing ./psneuter :
mnmap() failed. Invalid argument

I used windows to root
failed at adb shell psneuter command...
/system/bin/sh: psneuter: not found
how to proceed ?

[Q] Firewater: Can't execute: permission denied [NEVERMIND PLEASE DELETE]

I can't seem to get s-off on this htc one m8 on verizon. This is the second one I've attempted to get s-off on. With the first one everything went smoothly and I had s-off within minutes. Weaksauce roots it, the terminal successfully pushes firewater, but when I go to execute firewater I get an error message.
List of devices attached
FA44NSF01498 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push C:\User
s\Andrey\Desktop\firewater /data/local/tmp
3715 KB/s (4519496 bytes in 1.187s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
tmp-mksh: /data/local/tmp/firewater: can't execute: Permission denied
126|[email protected]_m8wl:/ #
Click to expand...
Click to collapse
Am I doing something wrong?
Nevermind... I really need more sleep... I forgot to chmod

if everyone that got their question answered deleted their post, we'd have the same questions being asked every day lol the archives have saved me multiple times so even when you fix your own problem, its good to post how you did it so others can use it for reference (like you did)

[resolved] Help for thread [6039y] **GUIDE** Repartitioning of the internal memory

Problem solved, by using an other usb adb driver, instead of universal adb driver ; thx petrov.0
Hi, sorry for my bad english,
I've trouble to understand what's wrong or I miss : want to run the 1st command umount /cache at the 4th step (unmount all partitions of the internal memory )
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ umount /cache
umount /cache
failed: Operation not permitted
1|[email protected]:/ $​
Actually the phone are root, TWRP v2.8.6.0 by decker. I've also swap with twrp-2.8.7.0-idol3-6039y-with-gdisk instead of just run it one time : same trouble, Operation not permitted
Any idea ?
Just to be sure, when it writing go to device, we are under the TWRP -> Reboot -> System ... and we go to android ? And at this point I run adb shell, that ok ?
I would also say, that my first smartphone / 1st root / 1st trying

Ok I've discover what's wrong
Need writing on the commande line : adb shell su
SuperSu on the phone ask me an authorization about "adb shell", of course I say yes
Now i can see :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su
[email protected]:/ #​
Symbol and "user" have change
shell --> root
$ --> #​
Hope now all clear for the next step.
Unfortunaly, it's not to seem that, now I can't writing any caractere in command line
Have try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # gdisk
gdisk
tmp-mksh: gdisk: not found
127|[email protected]:/ #​
umount /and-sec directory not found
gdisk not works
...help !

You shouldn't reboot the device. Everything must be done while the phone is in the recovery.

Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.

bykarat said:
Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.
Click to expand...
Click to collapse
You do this from Windows, so you need drivers which recognize your device when is in the recovery. I'm not sure which drivers work with the phone. The vendor and the product IDs for the recovery are
Code:
idVendor=18d1, idProduct=4ee2

Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.png​When I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:

bykarat said:
Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.png​When I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:
Click to expand...
Click to collapse
Glad to see that you made it. There is a thanks button by the way . I will include the link to the drivers in the guide.

How to root Lava 46 ?

I have new phone lava but Root not support please help ?

An Android device's OS is rooted when SU binary ( AKA superuser, childish called root ) is present in Android's filesystem. Hence push a matching SU binary to Android OS, what can be done by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SUITABLE-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"

Easiest way to temporarily get root on Android

Hi
I have a new Android device, it's not any of the ones that have their own forum.
More specifically it runs Android 11 on top of a 4.19.193 Rockchip BSP kernel.
I need to read one or two specific files but these files are only readable by root.
I have ADB shell access.
What I do want to acheive:-
Temporarily have an ability to copy a file that's readable only by root, this could be by some GUI app that copies files, as long as the copy is readable by normal user, running commands as root, copy a partition to an image file, export to a desktop machine and read it there. Any one of these would get me that file.
What I don't want to do:-
I don't want to permanently modify the device, unlock the bootloader, put su into /system or anything like that.
Does anyone know of a rooting app that can give me temporary root access but then doesn't actually change the system?
thanks

To get temporary super-user ( AKA root ) rights on an Android's device shell all you have to do is to find a suitable su binary and copy it onto Android's filesystem.
A: To run Android shell commands with super-user right from within the shell on desktop computer ( AKA Command Prompt ) you have to run within desktop computer shell
Code:
adb devices
adb push <LOCATION-OF-SUITABLE-SU-BINARY-ON-PC-HERE> /data/local/tmp/
what will 1. connect the Android device to your desktop computer and 2. upload the su binary in the Android device temporary directory always available for the user.
B: Then, in desktop computer shell type
Code:
adb shell "cd /data/local/tmp & chmod 776 su"
what makes the su binary executable: its ownership by default is set to shell.
C: Then in desktop computer shell type
Code:
adb shell "ls -l"
what will show you content and permissions on recently uploaded files.
D:
To apply a series of Android shell commands what require super-user rights you now would run
Code:
adb shell
export PATH=/data/local/tmp:$PATH"
su -c "<SHELL-CMD-HERE>"
....
su -c "<SHELL-CMD-HERE">
exit
BTW:
When in an Android shell another process like su gets started then this spawned process runs as a child process means it inherits most of the parent process attributes.

adb push allowed me to send the file
Code:
adb push su /data/local/tmp/
su: 1 file pushed. 1.2 MB/s (11640 bytes in 0.009s)
but the adb shell command is failing
Code:
adb shell "cd /data/local/tmp & chmod 776 su"
chmod: su: No such file or directory
if I then log in over adb I don't seem to have permissions to do anything in data
Code:
adb shell
ls -al
drwxrwx--x 47 system system 4096 2022-09-02 16:31 data
cd data
ls -al
ls: .: Permission denied

additionally, I thought that su would need the suid bit set
Does chmod 766 acheive that?

oh this works
Code:
adb shell
cd /data/local/tmp
ls -al
total 18
drwxrwx--x 2 shell shell 3452 2022-09-02 16:32 .
drwxr-x--x 4 root root 3452 2022-07-27 03:04 ..
-rw-rw-rw- 1 shell shell 11640 2022-09-02 16:29 su

Code:
chmod 776 su
ls -al
total 18
drwxrwx--x 2 shell shell 3452 2022-09-02 16:32 .
drwxr-x--x 4 root root 3452 2022-07-27 03:04 ..
-rwxrwxrw- 1 shell shell 11640 2022-09-02 16:29 su

Code:
adb shell
export PATH=$PATH:/data/local/tmp
su
su: setgid failed: Operation not permitted

The device has separate boot_a, boot_b, dtbo_a, dtbo_b partitions.
If I could be reasonably sure that booting a boot partition from a similar device (I have one) would pick up the dtb from this device then I think I could be reasonably confident of not frying anything, I might try and boot it from fastboot.