giefroot - rooting tool (CVE-2014-4322) - Sony Cross-Device General

giefroot
A tool to root your device using CVE-2014-7911 (by Keen Team) and CVE-2014-4322 (by zxz0O0).
System rw access & SuperSU installation.​
Requirements
USB debugging enabled
Settings => About phone => Click 7 times on Android Build to unlock developer options
Allow mock locations
Settings => Developer Settings
adb drivers installed
Firmware < October 2014 (kernel and system)
How to use
Download the tool (latest version) and extract it
Start your device and plug it to your computer
Put your device in air plane mode
Run install.bat and follow the instructions on screen
Congratulations! You should now be rooted. If you get an error "Device not rooted", try running the tool a second time.
Don't forget to make a donation
If you are not rooted, see post #3 for possible solutions!
What can you do next
Make a donation to the people involved
Backup TA partition / DRM keys
http://forum.xda-developers.com/showthread.php?t=2292598
Install dualrecovery by [NUT]
Download Z??-lockeddualrecovery2.X.XXX-BETA.installer.zip from http://nut.xperia-files.com/, run install.bat and select Option #1
Note if you have problems after installing recovery, this thread is not the place to ask for help!
Download v3.1
Thanks to
Big thanks to Keen Team for developing the CVE-2014-7911 exploit.
Original thread: http://forum.xda-developers.com/mate-7/general/wip-mate-7-root-bl-unlock-t2995086/post57991147
Code:
88 a8P 88888888888 88888888888 888b 88
88 ,88' 88 88 8888b 88
88 ,88" 88 88 88 `8b 88
88,d88' 88aaaaa 88aaaaa 88 `8b 88
8888"88, 88""""" 88""""" 88 `8b 88
88P Y8b 88 88 88 `8b 88
88 "88, 88 88 88 `8888
88 Y8b 88888888888 88888888888 88 `888
Huawei Ascend Mate 7 root utility
Present by Keen Team:
Liang Chen, flanker017 - CVE-2014-7911 exploit
idl3r - Kernel vulnerability and exploit
Special thanks to:
Yaron Lavi and Nadav Markus from Palo Alto Networks for "Mock Location" trick
Chainfire for SuperSU
KingRoot (www.kingroot.net) for testing devices
Tested on MT7-TL10 and MT7-CL00 China Domestic edition with B122 SP06 (2014/12/30)
May or may not work on international editions
Additionally, thanks to:
Chainfire: SuperSU developer
MohammadAG: Disable RIC kernel module (Link)
idler1984: Trick for stopping system_server
RHBH, squabbi, minijaws, Desperanto86: Testing & debugging
Changelog
v3.1
Add new device D6643 and D6616 (see here)
Small fixes
.
v3
Fixed a few bugs allocating memory
Add some new devices / firmwares for compatibility
.
v2
Fix phone rebooting before exploit completed (thanks idler1984!)
Fix error allocating memory for exploit code
.
v1
Initial release
XDA:DevDB Information
giefroot - rooting tool, Tool/Utility for the OEM Cross Device Development
Contributors
zxz0O0
Version Information
Status: Beta
Created 2015-01-24
Last Updated 2015-05-03

Reserved
Help: My device is not supported
The tool uses static kernel addresses. To support a device, I need the following information from someone with stock kernel (supported firmware) and root:
Code:
cat /proc/version
su
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /data/local/tmp/kallsyms
chmod 777 /data/local/tmp/kallsyms
Upload kallsyms and show output of version command.
Currently as in v1 only Z3 Compact and Z3 is supported.

Reserved
I have supported firmware / kernel but still not rooted!
Solution 1:
Run the tool a few times
Solution 2:
Put your phone into safe mode and run the tool. To get the device into safe mode:
pkobier said:
Hold power button and than hold "Turn off". You will see prompt message to reboot phone in safe mode.
Click to expand...
Click to collapse
Solution 3:
Try running the tool on another computer
No solution works:
To speed up the support process you can provide the following output / information:
Device model / firmware version
Kernel version (cat /proc/version)
adb shell "ls -l /data/local/tmp/"
adb shell "cat /data/local/tmp/giefrootlog"
adb shell "cat /proc/last_kmsg"

The wait worth a lot... Thanks man, you are awesome!

can i use it on D6603?

@zxz0O0 : I have done everything but at the end, it's say "Error: device not rooted"?

thienbrand said:
@zxz0O0 : I have done everything but at the end, it's say "Error: device not rooted"?
Click to expand...
Click to collapse
Post this information: http://forum.xda-developers.com/showpost.php?p=58391697&postcount=3
and output of install.bat

Nice

zxz0O0 said:
I have supported firmware / kernel but still not rooted!
To speed up the support process you can provide the following output / information:
Device model / firmware version
Kernel version (cat /proc/version)
adb shell "ls -l /data/local/tmp/"
adb shell "cat /data/local/tmp/giefrootlog"
Click to expand...
Click to collapse
Device model / firmware version : D6603 / 23.0.A.2.93 Generic Global
Kernel version (cat /proc/version): 3.4.0-perf-g0961 cdf [email protected] #1 Tue-Aug 19 19:48:36 2014
adb shell "ls -l /data/local/tmp/":
C:\adb>adb shell "ls -l /data/local/tmp/"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-rw-rw-rw- shell shell 4016989 2015-01-24 06:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 17:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 06:39 busybox
-rw-r--r-- root root 30184 2014-07-15 15:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 20:13 getroot
-rwxrwxrwx shell shell 143 2015-01-24 05:06 giefroot
-rwxrwxrwx system system 181 2015-01-24 20:31 giefrootlog
-rw------- u0_a33 u0_a33 3774 2015-01-24 20:39 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 09:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 12:40 main
-rwxrwxrwx shell shell 0 2015-01-24 20:38 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 23:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 10:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 05:02 wp_mod.ko
adb shell "cat /data/local/tmp/giefrootlog":
C:\adb>adb shell "cat /data/local/tmp/giefrootlog"
giefroot (c) zxz0O0
query failed. trying another app...
getting ptr
getting offset
Error: Could not allocate memory for exploit code
getting root...
getuid: 1000
Error getting root
output of bat:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1118 KB/s (17892 bytes in 0.015s)
25 KB/s (143 bytes in 0.005s)
1899 KB/s (60799 bytes in 0.031s)
13 KB/s (13592 bytes in 1.000s)
1 KB/s (1544 bytes in 1.000s)
2144 KB/s (34473 bytes in 0.015s)
2666 KB/s (4016989 bytes in 1.471s)
2417 KB/s (657704 bytes in 0.265s)
0 KB/s (752 bytes in 1.000s)
2766 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .

Hey, after root, can i update my device to latest firmware?

Thank so much my friend...
My small contribution: 8TJ698456J713772F

No success on my device:
Edit: after second attempt it did work
D5803
23.0.A.2.93
Kernel
3.4.0-perf-g0961cdf
[email protected] #1
Tue Aug 19 19:48:36 2014
Output of install.bat:
Code:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1109 KB/s (17892 bytes in 0.015s)
0 KB/s (143 bytes in 1.000s)
3799 KB/s (60799 bytes in 0.015s)
13 KB/s (13592 bytes in 1.000s)
96 KB/s (1544 bytes in 0.015s)
2154 KB/s (34473 bytes in 0.015s)
3985 KB/s (4016989 bytes in 0.984s)
4567 KB/s (657704 bytes in 0.140s)
0 KB/s (752 bytes in 1.000s)
2767 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .
Output of
adb shell "ls -l /data/local/tmp/"
Code:
-rw-rw-rw- shell shell 4016989 2015-01-24 00:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 11:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 00:39 busybox
-rwxrwxrwx shell shell 17892 2015-01-24 14:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 23:06 giefroot
-rwxrwxrwx shell shell 752 2015-01-24 03:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 06:40 main
-rwxrwxrwx shell shell 0 2015-01-24 14:37 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 17:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 04:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-09 23:02 wp_mod.ko
Output of
adb shell "cat /data/local/tmp/giefrootlog"
Code:
/system/bin/sh: cat: /data/local/tmp/giefrootlog: No such file or directory
Edit:
After the second time, it did work.
Here is the output of the install.bat after second attempt:
Code:
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .

It didn't worked with my device.
Device model / firmware version:
Code:
D6643 / 23.0.A.2.93
Kernel version (cat /proc/version):
Code:
[email protected]:/ $ cat /proc/version
cat /proc/version
Linux version 3.4.0-perf-g18c6f85 ([email protected]) (gcc version 4.7 (GCC) )
#1 SMP PREEMPT Thu Sep 11 12:05:53 2014
[email protected]:/ $
adb shell "ls -l /data/local/tmp/":
Code:
[email protected]:/ $ ls -l /data/local/tmp
ls -l /data/local/tmp
-rw-rw-rw- shell shell 4016989 2015-01-23 21:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 08:50 a
-rwxrwxrwx shell shell 657704 2014-02-06 21:39 busybox
-rw-r--r-- root root 30184 2014-07-15 06:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 11:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 20:06 giefroot
-rwxrwxrwx system system 0 2015-01-24 11:44 giefrootlog
-rw------- system graphics 2654 2015-01-24 11:45 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 00:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 03:40 main
-rwxrwxrwx shell shell 0 2015-01-24 11:43 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 15:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 01:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-09 21:02 wp_mod.ko
[email protected]:/ $
adb shell "cat /data/local/tmp/giefrootlog":
Code:
[email protected]:/ $ cat /data/local/tmp/giefrootlog
cat /data/local/tmp/giefrootlog
[email protected]:/ $
As far I saw the system escalation was successful, so the 1st exploit worked, the problem was achieving root with system user.

At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.

I'm also getting the "device not rooted" error.
Model: D6603
Firmware: 23.0.A.2.93 (1282-2729_23.0.A.2.93 GENERIC - user)
Kernel: Linux version 3.4.0-perf-g0961cdf ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Aug 19 19:48:36 2014
/data/local/tmp/
Code:
-rw-rw-rw- shell shell 4016989 2015-01-24 00:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 11:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 00:39 busybox
-rwxrwxrwx shell shell 17892 2015-01-24 14:13 getroot
-rwxrwxrwx shell shell 143 2015-01-23 23:06 giefroot
-rw------- system graphics 11058 2015-01-24 14:53 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 03:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 06:40 main
-rwxrwxrwx shell shell 0 2015-01-24 14:52 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 18:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 04:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 00:02 wp_mod.ko
giefrootlog is not there.
install.bat output:
Code:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
0 KB/s (152 bytes in 1.000s)
1118 KB/s (17892 bytes in 0.015s)
0 KB/s (143 bytes in 1.000s)
3799 KB/s (60799 bytes in 0.015s)
13 KB/s (13592 bytes in 1.000s)
96 KB/s (1544 bytes in 0.015s)
2156 KB/s (34473 bytes in 0.015s)
3528 KB/s (4016989 bytes in 1.111s)
3957 KB/s (657704 bytes in 0.162s)
0 KB/s (752 bytes in 1.000s)
2770 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .

RHBH said:
It didn't worked with my device.
[..]
Click to expand...
Click to collapse
Please pm me your gmail address for google hangout.
H117 said:
At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.
Click to expand...
Click to collapse
Thanks for confirming. What is your device / version? So we can collect which are working.

H117 said:
At first it didn't work, the batch would report "Error: device not rooted", but I suspect that's because I declined the Google pop up to perform app checks. After I rebooted and accepted, it worked just fine.
So thank you very much. I will be making a small contribution shortly.
Click to expand...
Click to collapse
Also had problem at first to get root , didnt even see the popup but on my 5th try i did see it and all went fine . So people give it a few tries .
D5803 running 23.0.A.2.93

zxz0O0 said:
Please pm me your gmail address for google hangout.
Thanks for confirming. What is your device / version? So we can collect which are working.
Click to expand...
Click to collapse
Sure.
Device model / firmware version - D5803/23.0.A.2.93
Kernel version - 3.4.0-perf-g0961cdf

zxz0O0 said:
Please pm me your gmail address for google hangout.
Thanks for confirming. What is your device / version? So we can collect which are working.
Click to expand...
Click to collapse
D5803
23.0.A.2.93
Kernel
3.4.0-perf-g0961cdf
First time: exact same output as @darwusch, did not get the SU prompt after reboot
Second time: This time i waited for the command window to connect my phone, and i waited a bit after reboot before touching the phone. After unluck i got SU prompt , confirmed it and i got root.
Thanks for all!!

thienbrand said:
Device model / firmware version : D6603 / 23.0.A.2.93 Generic Global
Kernel version (cat /proc/version): 3.4.0-perf-g0961 cdf [email protected] #1 Tue-Aug 19 19:48:36 2014
adb shell "ls -l /data/local/tmp/":
C:\adb>adb shell "ls -l /data/local/tmp/"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-rw-rw-rw- shell shell 4016989 2015-01-24 06:00 SuperSU.zip
-rwxrwxrwx shell shell 152 2015-01-24 17:50 a
-rwxrwxrwx shell shell 657704 2014-02-07 06:39 busybox
-rw-r--r-- root root 30184 2014-07-15 15:10 flatland
-rwxrwxrwx shell shell 17892 2015-01-24 20:13 getroot
-rwxrwxrwx shell shell 143 2015-01-24 05:06 giefroot
-rwxrwxrwx system system 181 2015-01-24 20:31 giefrootlog
-rw------- u0_a33 u0_a33 3774 2015-01-24 20:39 glsl_shader_log.txt
-rwxrwxrwx shell shell 752 2015-01-24 09:08 installsupersu.sh
-rwxrwxrwx shell shell 60799 2015-01-07 12:40 main
-rwxrwxrwx shell shell 0 2015-01-24 20:38 memfile
-rwxrwxrwx shell shell 13592 2014-07-20 23:10 modulecrcpatch
-rwxrwxrwx shell shell 1544 2015-01-24 10:13 systemrw.sh
-rwxrwxrwx shell shell 34473 2014-07-10 05:02 wp_mod.ko
adb shell "cat /data/local/tmp/giefrootlog":
C:\adb>adb shell "cat /data/local/tmp/giefrootlog"
giefroot (c) zxz0O0
query failed. trying another app...
getting ptr
getting offset
Error: Could not allocate memory for exploit code
getting root...
getuid: 1000
Error getting root
output of bat:
==============================================
= =
= giefroot v1 =
= created by zxz0O0 =
= =
= Many thanks to: =
= - [NUT] =
= - MohammadAG =
= - Keen Team =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Sending files
=============================================
9 KB/s (152 bytes in 0.015s)
1118 KB/s (17892 bytes in 0.015s)
25 KB/s (143 bytes in 0.005s)
1899 KB/s (60799 bytes in 0.031s)
13 KB/s (13592 bytes in 1.000s)
1 KB/s (1544 bytes in 1.000s)
2144 KB/s (34473 bytes in 0.015s)
2666 KB/s (4016989 bytes in 1.471s)
2417 KB/s (657704 bytes in 0.265s)
0 KB/s (752 bytes in 1.000s)
2766 KB/s (44259 bytes in 0.015s)
pkg: /data/local/tmp/exploitServiceApp.apk
Success
=============================================
Running exploit
=============================================
Please wait 70 seconds to let the device reboot
Error: device not rooted
Press any key to continue . . .
Click to expand...
Click to collapse
Have EXACTLY the same, except i'm on .98 fw. Will try in about 30 minutes.
atm: Z, Z3, Arc S, Play, S3, S3 Mini

Related

[Q] i need help again

trying too root.. and im looking at this
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
65 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
395 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 19393
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ adb shell
adb shell
adb: not found
$
what do i do now????
The $ means you are still in the shell. You have to wait till it goes back to the Command prompt (c
Sent from my SCH-I500 using XDA App
ace5198 said:
trying too root.. and im looking at this
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
65 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
395 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 19393
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ adb shell
adb shell
adb: not found
$
what do i do now????
Click to expand...
Click to collapse
You haven't waited long enough. That last step should kick you out of the shell, and back into the command prompt, where your 'adb shell' command will work.
adb is used on the windows command prompt, not the phone's shell.
To exit the shell, and get back to the windows command prompt, you can always type "exit" and hit enter at the $ or # prompt.
just wait?
ace5198 said:
just wait?
Click to expand...
Click to collapse
Ideally yes. Many people report having to wait up to 2 minutes. I don't know what you've done since then, best to just start over. To be safe, just reboot the phone, then start again.
ok i rebooted and got past that point now im at this line and stuck
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
87 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
410 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2200
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\androidsdk\Tools>adb shell
error: device not found
C:\androidsdk\Tools>
help please.. im totally lost and cant find anything about this anywhere
hahahahah wooohoooo.. i did it... benchmark 2155 =) thank your so much to everyone that helped me... you are all awesome.. tanks dirrk for the step by step instructions..and a huuuuuggggeee shoutout to poulosjr couldnt have done it without you.. thank you all sooo much
Hello ace5198,
How did u do it? I am facing exactly the same issue...
$ chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
$ cd /data/local/tmp
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3341, 3341}
[*] Searching for adb ...
[+] Found adb as PID 1941
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
[email protected]:~/android-sdk-linux_86/platform-tools$ ./adb shell
error: device not found
There is a new root method by dirrk on one of the stickies in android development... I would link you directly, but I can't from my phone. look for the one that says roll up

[SOLVED] Kindle fire rooting error

I rooted it yesterday then I reset the phone
I want to root now the same method doesn't work
when I write
adb root
command it gives me
adbd cannot run as root in the production builds
why??
what is the error is this in files or what
how you try to root your kf?
did you use burrito root3?
*********************
skip to the next replay
yes I tried it with those steps
http://www.androidpolice.com/2012/0...r-6-2-2-update/comment-page-1/#comment-169037
this is my try plz help me
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb devices
List of devices attached
2A9C002600000001 device
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
13 KB/s (0 bytes in 13317.001s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[COLOR="Blue"][1] Killed am broadcast -a ...
[/COLOR]Please run "adb root" and enjoy
C:\kindleADB>adb root
[COLOR="blue"]adbd cannot run as root in production builds
[/COLOR]
C:\kindleADB>
with this method others had also troubles - would try to use burritoroot3:
http://forum.xda-developers.com/showthread.php?t=1410223
Where I will find
BurritoRoot3.bin
look here
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \
C:\>cd android/platform-tools
C:\android\platform-tools>adb kill-server
C:\android\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb push BurritoRoot2.bin /data/local/
13 KB/s (13317 bytes in 1.000s)
C:\android\platform-tools>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>
C:\android\platform-tools>as
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>adb devices
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell chmod 777 /data/local/tmp
C:\android\platform-tools>adb install BurritoRoot3.apk
3307 KB/s (1164225 bytes in 0.343s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
C:\android\platform-tools>adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
[COLOR="Blue"]Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
[1] Killed am broadcast -a ...
Installing Superuser APP, if it errors as already exists, please ignore the erro
r.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[/COLOR]
C:\android\platform-tools>
the blue means no any result
no bin - it's a completly new method - please read the op (1st post) of the above linked in thread
wait - still reading your updated post
okay look to my previous post i tried it and the result is above
everything seems to be fine as in your previous post:
Code:
Installing Superuser APP, if it errors as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
it says you should ignore the error cause you have allready installed the superuser app
yeah it installed
should I continue??AND Ignore this error
YES - it says to ignore the error
Not working!!
what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so
I don't know what happened but someone told me to reset the kf
then when I tried the order that was the output
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
2273 KB/s (0 bytes in 1164225.000s)
[1] Killed pm install /data...
C:\kindleADB>
to restart was probably not the best idea - anyway:
the error message looks like he uninstalled it now
retry:
adb install BurritoRoot3.apk
what's the output ?
b63 said:
what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so
Click to expand...
Click to collapse
thank you so much, i was having a problem with this, i used 2 lines above and everything went smooth
respect
okay I will try now
look
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd \kindleADB
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
216 KB/s (0 bytes in 13317.000s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\kindleADB>adb root
adbd cannot run as root in production builds
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
can't find 'BurritoRoot3.apk' to install
C:\kindleADB>adb install BurritoRoot3.apk
573 KB/s (0 bytes in 1164225.001s)
[1] Killed pm install /data...
C:\kindleADB>

[HELP] Root

Hi!
I need help with root Acre Iconia tab a500... I use this guide for root on linux (ubuntu 12.10).
I follow all instructions. All is fine but I stucked on last step.
Here is my error (bold font) in terminal:
Thanks for help!
Code:
[email protected]:~/root$ chmod +x ./root.sh
[email protected]:~/root$ ./root.sh -d
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
DEBUG MODE
FOR TESTING ADB CONNECTION. DOES NOT MODIFY THE TABLET
Press any key to continue...
[+] Killing any adb processes
[+] Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Listing devices
List of devices attached
14902506315 device
Is your device listed? (y/n) y
[+] Your ADB connection is fine. Proceed to root your device!
[email protected]:~/root$ ./root.sh -h
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
USAGE:
-h | --help: Shows this usage message
-r | --root: root the device (Installs busybox, su, Superuser.apk & remount app)
-t | --trebuchet: Install Trebuchet (CM9 launcher)
-f | --facelock: Install FaceLock (Experimental and only partially working at the moment
-a | --RemoveAcerNidus: Remove AcerNidus Crash Report App
-s | --RemoveStockRecoveryReflash: Remove auto-reflash of stock recovery in preparation to flash CWM in APX mode
-u1 | --AcerRing1: Install Acer Ring on 0.019.00
-u2 | --AcerRing2: Install Acer Ring on 0.022.00
-u3 | --AcerRing3: Install Acer Ring on 1.031.00
-b | --bash: Install bash on the tablet
-c | --complete: Does the whole lot!
-d | --debug: Debug mode. Tests the ADB connection
[email protected]:~/root$ ./root.sh -r
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
Press any key to run!
Running in 5 seconds
5
4
Ready...
Set...
Go!
Running!!
[+] Killing all old adb processes
[+] Starting ADB Server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Listing Devices
List of devices attached
14902506315 device
Is your device listed? (y/n) y
[+] Uploading exploit
1088 KB/s (37273 bytes in 0.033s)
[+] Uploading busybox
1293 KB/s (821340 bytes in 0.620s)
[+] Setting permissions
[+] Creating directories
[+] Uploading files...
[B]./root.sh: řádek 161: [: ==: očekáván unární operátor
547 KB/s (22364 bytes in 0.039s)
1126 KB/s (843503 bytes in 0.731s)
0 KB/s (40 bytes in 0.040s)
537 KB/s (21584 bytes in 0.039s)
12 KB/s (519 bytes in 0.040s)
./root.sh: řádek 282: chyba syntaxe: nenadálý konec souboru[/B]
[email protected]:~/root$

[Q:SOLVED] su : not found; rooted without root access

Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery (after rooting with motochopper). I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
gr4v1ty said:
Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery. I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
Click to expand...
Click to collapse
What methods have you tried? Did you try the Chainfire Auto Root?
DeadlySin9 said:
What methods have you tried? Did you try the Chainfire Auto Root?
Click to expand...
Click to collapse
It was motochopper. Sorry forgot to mention. Also here the output of the root checker pro app
Code:
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
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 /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
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.
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 SGH-I337M device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
EDIT : Solved by using CF-Auto-root : http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my SGH-I337M using Tapatalk

Logcat/Recowvery issue

I've done it before but it seems like it's just not giving in this time. I had the phone rooted before and had to unroot for what I thought was going to be an insurance claim through my work (T-Mobile) and ended up just having some friends replace the screen for me. I went back to root the device again and still had all the same original files that I used to originally root and even locked and unlocked the bootloader again hoping that would fix my issue but I'm still getting hung at the logcat -s recowvery command. It shows <------- Beginning of system> <-------- Beginning of main> and just hangs and does nothing else.
text posted of every command I used to the exact instructions on @jcadduono post on how to root the h918
can't post screenshots because of new member.
Code:
C:\Users\Mike\Desktop\mini tools>adb devices
List of devices attached
LGH9185c391d6e device
C:\Users\Mike\Desktop\mini tools>adb push dirtycow /data/local/tmp
dirtycow: 1 file pushed. 0.3 MB/s (9984 bytes in 0.030s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-applypatch /data/local/tmp
recowvery-applypatch: 1 file pushed. 1.7 MB/s (18472 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-app_process64 /data/local/tmp
recowvery-app_process64: 1 file pushed. 1.0 MB/s (10200 bytes in 0.010s)
C:\Users\Mike\Desktop\mini tools>adbpush recowvery-run-as /data/local/tmp
'adbpush' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Mike\Desktop\mini tools>adb push recowvery-run-as /data/local/tmp
recowvery-run-as: 1 file pushed. 0.9 MB/s (10192 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb shell
elsa:/ $ cd /data/local/tmp
elsa:/data/local/tmp $ chmod 0777 *
/dirtycow /system/bin/applypatch recowvery-applypatch <
warning: new file size (18472) and file old size (165144) differ
size 165144
[*] mmap 0x7e70077000
[*] exploit (patch)
[*] currently 0x7e70077000=10102464c457f
[*] madvise = 0x7e70077000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x7e70077000=10102464c457f
./dirtycow /system/bin/app_process64 recowvery-app_process64 <
warning: new file size (10200) and file old size (18600) differ
size 18600
[*] mmap 0x7ddae0d000
[*] exploit (patch)
[*] currently 0x7ddae0d000=10102464c457f
[*] madvise = 0x7ddae0d000 18600
[*] madvise = 0 1048576
[*] /proc/self/mem -1971322880 1048576
[*] exploited 0x7ddae0d000=10102464c457f
elsa:/data/local/tmp $ exit
C:\Users\Mike\Desktop\mini tools>adb logcat -s recowvery
--------- beginning of system
--------- beginning of main
how to fix lgh918 recowvery issue
OfficialVillager said:
I've done it before but it seems like it's just not giving in this time. I had the phone rooted before and had to unroot for what I thought was going to be an insurance claim through my work (T-Mobile) and ended up just having some friends replace the screen for me. I went back to root the device again and still had all the same original files that I used to originally root and even locked and unlocked the bootloader again hoping that would fix my issue but I'm still getting hung at the logcat -s recowvery command. It shows <------- Beginning of system> <-------- Beginning of main> and just hangs and does nothing else.
text posted of every command I used to the exact instructions on @jcadduono post on how to root the h918
can't post screenshots because of new member.
Code:
C:\Users\Mike\Desktop\mini tools>adb devices
List of devices attached
LGH9185c391d6e device
C:\Users\Mike\Desktop\mini tools>adb push dirtycow /data/local/tmp
dirtycow: 1 file pushed. 0.3 MB/s (9984 bytes in 0.030s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-applypatch /data/local/tmp
recowvery-applypatch: 1 file pushed. 1.7 MB/s (18472 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb push recowvery-app_process64 /data/local/tmp
recowvery-app_process64: 1 file pushed. 1.0 MB/s (10200 bytes in 0.010s)
C:\Users\Mike\Desktop\mini tools>adbpush recowvery-run-as /data/local/tmp
'adbpush' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Mike\Desktop\mini tools>adb push recowvery-run-as /data/local/tmp
recowvery-run-as: 1 file pushed. 0.9 MB/s (10192 bytes in 0.011s)
C:\Users\Mike\Desktop\mini tools>adb shell
elsa:/ $ cd /data/local/tmp
elsa:/data/local/tmp $ chmod 0777 *
/dirtycow /system/bin/applypatch recowvery-applypatch <
warning: new file size (18472) and file old size (165144) differ
size 165144
[*] mmap 0x7e70077000
[*] exploit (patch)
[*] currently 0x7e70077000=10102464c457f
[*] madvise = 0x7e70077000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x7e70077000=10102464c457f
./dirtycow /system/bin/app_process64 recowvery-app_process64 <
warning: new file size (10200) and file old size (18600) differ
size 18600
[*] mmap 0x7ddae0d000
[*] exploit (patch)
[*] currently 0x7ddae0d000=10102464c457f
[*] madvise = 0x7ddae0d000 18600
[*] madvise = 0 1048576
[*] /proc/self/mem -1971322880 1048576
[*] exploited 0x7ddae0d000=10102464c457f
elsa:/data/local/tmp $ exit
C:\Users\Mike\Desktop\mini tools>adb logcat -s recowvery
--------- beginning of system
--------- beginning of main
Click to expand...
Click to collapse
this is exzactly what happened to me any ideas how to correct it?
I recommend getting the stock kdz and flashing it to get you back to a true stock state. Don't use any kdz after 10j.
Who knows what was left behind when you unrooted. Unrooting doesn't return you to stock. It just unrooted you.
Once on a true stock system, recowvey should work.
androiddiego said:
I recommend getting the stock kdz and flashing it to get you back to a true stock state. Don't use any kdz after 10j.
Who knows what was left behind when you unrooted. Unrooting doesn't return you to stock. It just unrooted you.
Once on a true stock system, recowvey should work.
Click to expand...
Click to collapse
Unfortunately, that won't be the case on 10q or 10r. According to @runningnak3d, they've not only locked down qualcomm processors, but have also basically removed fastboot. There isn't any way to root beyond that update. not yet at least. and with antirollback being enabled now, no way to downgrade. We're stuck in a rut.
OfficialVillager said:
Unfortunately, that won't be the case on 10q or 10r. According to @runningnak3d, they've not only locked down qualcomm processors, but have also basically removed fastboot. There isn't any way to root beyond that update. not yet at least. and with antirollback being enabled now, no way to downgrade. We're stuck in a rut.
Click to expand...
Click to collapse
What firmware is the phone currently on?
androiddiego said:
What firmware is the phone currently on?
Click to expand...
Click to collapse
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.
OfficialVillager said:
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.
Click to expand...
Click to collapse
You're on 10q. That's why recowvery won't work. It work on 10j and below.
OfficialVillager said:
You'd have to check the about settings of your phone to know what you're on. The most recent is 10r. Im on 10q.
Click to expand...
Click to collapse
Sorry bud you can't root and if you try to go back to a rootable version you'll brick. This is even if you got there through a TWRP flashable zip, since they still update everything except recovery.
Try running logcat -s recowvery directly in an adb shell on the target device.

Categories

Resources