SuperSU breaks ADB - SuperSU

Hey.
I'm trying to root my brand new BQ Aquaris U to use it as my new development platform, since the Samsung Galaxy Nexus (i9250), which has served as my development device for the last five years, is rapidly breaking down on the hardware side.
The Aquaris runs on the latest firmware, Android 6.0.1, Kernel 3.18.24, Build 1.5.0_20170217-1219.
My host computer is running on Fedora 25 with the lastest Android SDK.
As long as the device is stock, I can connect to it via ADB, but of course, I cannot obtain root.
Code:
$ ./adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
$ ./adb shell
[email protected]:/ $ exit
$
I then boot the device into Fastboot mode and install TWRP.
Code:
$ ./adb reboot bootloader
$ ./fastboot flash recovery ../../BQ/twrp-3.1.0-0-chaozu.img
target reported max download size of 535822336 bytes
sending 'recovery' (16676 KB)...
OKAY [ 0.528s]
writing 'recovery'...
OKAY [ 0.416s]
finished. total time: 0.944s
$ ./fastboot reboot
rebooting...
finished. total time: 0.203s
$ ./adb reboot recovery
$
Then I back up the "boot" and "system" partitions and transfer the backup over to my computer via MTP.
I then transfer "SuperSU-v2.79-201612041815.zip" to my phone and install it via TWRP.
After I boot into Android again, ADB is no longer working.
Code:
$ ./adb shell
error: no devices/emulators found
$
There seems to be nothing I can do to get ADB access when the device is rooted. The device will show that "USB debugging is connected", but will not be recognized by ADB. Resetting debugging permissions on the device does not help. Neither does changing the USB connection mode (e. g. from "File transfer (MTP)" to "Charging only") on the device or adding the device's USB ID (2a47:901b) to "~/.android/adb_usb.ini". When the device is returned to stock via an OTA update, ADB will start working again. Restoring the backup via TWRP will probably make it functional as well. However, of course both will un-root the device.
Is there any way to get ADB working on this device while it's rooted? Since it's pretty obvious that SuperSU breaks ADB on this device, can I somehow contact the developers of SuperSU to help them track the issue down? Or is there a known workaround?
Any help is appreciated.

Related

Superboot for Tattoo test

Feeling brave? Help me test / develop my superboot!
http://android.modaco.com/content/h...9976/13-jan-1-0-superboot-rooting-the-tattoo/
P
sorry, but your batch makes problemm...
and when i make it manual:
C:\Android\superboot>fastboot-windows boot tattoo.superboot.img
downloading 'boot.img'... OKAY
booting...
then nothing
for me doesn't work... i've got mac and the message in terminal is:
./install-superboot-mac.sh: line 3: unexpected EOF while looking for matching `''
./install-superboot-mac.sh: line 14: syntax error: unexpected end of file
and if i try to do the steps inside the script terminal says:
bash-3.2# chmod +x fastboot-mac
bash-3.2# chmod +x adb-mac
bash-3.2# ./adb-mac shell reboot oem-78
error: device not found
bash-3.2# ./fastboot-mac oem-78
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
bash-3.2# ./fastboot-mac boot tattoo.superboot.img
downloading 'boot.img'... FAILED (remote: not allow)
bash-3.2# ./fastboot-mac reboot
rebooting... (here with no reboot)
i hope this could help you...
You could try fastboot oem boot superboot.img allthough I don't think it will work, we have tried this on the Eris but who knows maybe yours will be different
Any advance on this guys?
If you need my help, just tell me, I'm newbie but I love to take risks!
I tried this method on my HTC.
downloading 'boot.img'... OKAY
booting.....
Click to expand...
Click to collapse
I waited for few min nothing happen.so un plug the cable it goes to RUU.
And then i insert the cable it rebooted.
What about this?
i'm New
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
I have a feeling there stuck on it same as we are, the tattoo and eris are more alike than either to the hero
binny1007 said:
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
Click to expand...
Click to collapse
Yup, tried that. It just boots the phone to it's current (flashed) rom
I tried using the boot command and, while it's hanging at "booting...", I sent a oem boot, but no luck
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
FireSokar said:
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
Click to expand...
Click to collapse
Interesting. When I get mine (tattoo), I'll try it out. Superboot just allows us superuser access, doesn't it? If we boot with this, then run a Terminal emulator, type 'su', we'll be able to get root (temporarily)?
Im pretty sure thats how it works, im not 100% sure im following this thread closely as we are stuck @ the exact same point on getting the droid eris rooted, better side of 2 months working on it.
The wait for my HTC Tattoo is killing me. I really want to try this out before I go back to school...
I ordered it last week sometime and it's supposedly coming next week... If it all comes to the worse, I'll just try this at school.... Hehe
Alright, I did this, and I think it may get me somewhere.
I did this while on the home screen, with USB debugging enabled. I ran the mac fastboot script, and it booted into the HTC logo screen. It said "Booting..." and got stuck.
After a minute, I yanked the USB cord out, and it dumped me at the RUU screen with text like this in my Terminal:
Terminal said:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./install-superboot-mac.sh
Superboot for HTC Tattoo by Paul O'Brien @ http://www.MoDaCo.com
----------------------------------------------------------------
Rebooting device...
* daemon not running. starting it now *
* daemon started successfully *
0
Waiting 10 seconds for reboot...
Booting superboot...
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
ERROR: could not get pipe properties
< waiting for device >
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
Click to expand...
Click to collapse
I then reinserted the USB cable and got this:
rebooting...
Done!
Click to expand...
Click to collapse
After that, I did some exploring with adb-mac:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./adb-mac shell
$ ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ su
su: permission denied
Click to expand...
Click to collapse
And so, I got the dreaded permission denied error! Oh well, at least I tried...
Any suggestions?
EDIT: I can do 'cat /proc/cpuinfo' and get:
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 244.94
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2
Hardware : bahamas
Revision : 0080
Serial : 0000000000000000
Click to expand...
Click to collapse
Interesting...

[Q] how can I open adb shell on Nexus One on Ginger bread

I have updated my nexus one to Ginger bread image GRI40 from http: //android.clients.google.com/pa...8.656099b1.zip
following this thread http: //forum.xda-developers.com/showthread.php?t=966939&page=4
But when I tried to open adb shell and want to list the content of '/data/data' directory. I get the following error:
Code:
$ adb shell
$ cd /data/data
$ su
su: permission denied
$ ls
opendir failed, Permission denied
$
and when i do 'adb remount' i get
Code:
$ adb remount
remount failed: Operation not permitted
Can you please tell me how can I open 'adb shell' to Nexus one
Thank you.
You're not rooted. That's your problem.
If you have rooted earlier, then most probably you need to re-root.
Sent from my Nexus One using XDA App
I did
$ fastboot oem unlock
...
(bootloader) Erasing userdata...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 15.000s
Click to expand...
Click to collapse
And then the phone reboots.
But I still can't get to /data/data
$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ cd /data/data
$ ls
opendir failed, Permission denied
$
Click to expand...
Click to collapse
No.
10chars...
Unlocking the bootloader disables security on the bootloader.
Rooting a phone effectively disables security on the system.
They are not the same thing...
With an unlocked bootloader you can use fastboot to flash a custom recovery, rooted system, or any other image you wish (provided it it's for your phone).
Sent from my Nexus One using XDA App
So i have installed GRI40 myself and then have done 'fastboot oem unlock'. What else do I need to do in order to root my phone?
Install custom recovery and flash su.zip through recovery...
It's all in the wiki, and many threads...
Sent from my Nexus One using XDA App
Thanks.
I have installed recovery rom recovery-RA-passion-v2.2.1.img by following this http://forum.xda-developers.com/showthread.php?t=611829
$ fastboot flash recovery recovery-RA-passion-v2.2.1.img
sending 'recovery' (3366 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 1.261s]
finished. total time: 1.754s
Click to expand...
Click to collapse
But it still does not let me see the content of /data/data
$ adb shell
$ cd /data/data
$ ls
opendir failed, Permission denied
$ su
su: permission denied
$ exit
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Again, I am using the GingerBread build on Nexus One. Ginger bread image GRI40 from http: //android.clients.google.com/pa...8.656099b1.zip
Read post 8 again.
I have gotten the su.zip file from
http://forum.xda-developers.com/showthread.php?t=968396
put it to my sd card. 292KB
And I have booted my nexus one (installed it with ginger bread with a 0.35 HBoot loader).
And when i try to 'apply sdcard:update.zip', I selected the zip file I put in my sd card.
It sid
'Verifying update package...' E:signature verification failed. Installation aborted'.
He did say you have to flash su though...
from here http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images it said i need to also execute 'fastboot reboot recovery' after I fastboot flash install the recovery rom.
But when i execute 'fastboot reboot recovery' i get
$ fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
I think the 'fastboot ' command only takes 'fastboot reboot'?
You don't need to rename to update, but it doesn't matter either way. In your custom recovery, select the option to flash any zip and select the su file. If you get a verification error, turn off signature verification in your custom recovery...
The command to boot into recovery is:
fastboot boot recovery.img
(where recovery.img is the name of your recovery file)
Sent from my Nexus One using XDA App
OK, you seriously don't know what you are doing.
Follow this to the letter:
Flash your recovery.
Pick the bootloader option.
Pick the recovery option.
Download su files from: http://forum.xda-developers.com/showthread.php?t=682828
Mount the USB storage
Copy the zip file over.
Unmount USB storage.
Flash the zip you just downloaded.
You might want to flash this file, also, while you are in recovery. It will make sure your recovery doesn't disappear the next time you boot your phone...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
I have updated my nexus one to gingerbread 2.3.3. Is there any possible way to root without unlocking my bootloader. Thanks I'm advance.
Sent from my Nexus One using Tapatalk
If you can roll back to 2.2, yes. Not everyone can for some reason though. If you're one that can't, then you have to unlock.
Rusty! said:
If you can roll back to 2.2, yes. Not everyone can for some reason though. If you're one that can't, then you have to unlock.
Click to expand...
Click to collapse
Hmmmmm thanks rusty but I think I will wait for a possible way to root rather than unlocking my bootloader. Thanks again.
Sent from my Nexus One using Tapatalk
Most people seem to be able to roll back. You might as well try, since it won't do any harm...?
Sent from my Nexus One using XDA Premium App

[Q] Bootloop forever after KitKat install

So i decided to give insertcoin 4.4 rom a go yesterday. flashed twrp 2.6.3.3 via adb flash recovery which worked great.
Clean installed insertcoin kept to instructions no odex etc.... phone rebooted as required got to setup screen an just reboots itself and repeats the same procedure.
I cannot push anything via adb now all sdk is up to date and in correct folders etc.
would try sideload but i cant get any sense out of that. any help on this oh yeah.
hboot 1.54, htc dev unlocked and thought i had s-off but its showing s-on. tried rumrunner with the hope i can fix situation but no joy but the program just ends.
so whats i should route to take follow some tutorials and get back to stock or try a few more times to get it sorted?
edit: I have a backup but its on my laptop and i cannot push it through
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exitYes
This is the message I get when trying rumrunner. but there is no way i can enable/disable usb debugging as i cannot boot into the phone
I have tried many different ways to restore the phone but i keep getting remote not allowed error
iamsloany said:
I have tried many different ways to restore the phone but i keep getting remote not allowed error
Click to expand...
Click to collapse
I thought TWRP 2.6.3.3 was pulled due to some bugs, maybe best to go back to 2.6.3.0
then use adb push or sideload to get a Guru Reset ROM (same or close to your firmware) onto your phone (with ROOT, and without "stock recovery")
and use rumrunner to get s-off.
nkk71 said:
I thought TWRP 2.6.3.3 was pulled due to some bugs, maybe best to go back to 2.6.3.0
then use adb push or sideload to get a Guru Reset ROM (same or close to your firmware) onto your phone (with ROOT, and without "stock recovery")
and use rumrunner to get s-off.
Click to expand...
Click to collapse
thought i was being clever installed latest CWM made fatal mistake and delted user data phone still doing same thing booting and rebooting. cant get s-off as i cannot boot into phone and anything being sideloaded or pushed through adb other than a recovery img wont flash.
im majorly stuck help
iamsloany said:
thought i was being clever installed latest CWM made fatal mistake and delted user data phone still doing same thing booting and rebooting. cant get s-off as i cannot boot into phone and anything being sideloaded or pushed through adb other than a recovery img wont flash.
im majorly stuck help
Click to expand...
Click to collapse
what's the output of the adb push command? can you copy/paste your command prompt output please
example:
Code:
C:\ADB2>[B]adb push Guru_Reset_M7_3.62.401.1.zip /data/media/[/B]
2922 KB/s (1102709591 bytes in 368.450s) [I][B]<- just an example, and yes it takes 5 to 10 minutes without reporting any progress until finished[/B][/I]
C:\ADB2>[B]adb shell[/B]
~ # [B]cd /data/media[/B]
cd /data/media
/data/media #[B] ls -l[/B]
ls -l
-rw-rw-rw- 1 root root 1102709591 Oct 3 03:56 Guru_Reset_M7_2.24.707.1.zip [I]<- just an example[/I]
/data/media # [B]md5sum Guru_Reset_M7_3.62.401.1.zip[/B]
md5sum Guru_Reset_M7_3.62.401.1.zip
6444b41a1f332f31345d5ead674382d7 Guru_Reset_M7_3.62.401.1.zip [B][I]<- confirm MD5 sum is correct[/I][/B]
/data/media #[B] exit[/B]
exit
C:\ADB2>
nkk71 said:
what's the output of the adb push command? can you copy/paste your command prompt output please
example:
Code:
C:\ADB2>[B]adb push Guru_Reset_M7_3.62.401.1.zip /data/media/[/B]
2922 KB/s (1102709591 bytes in 368.450s) [I][B]<- just an example, and yes it takes 5 to 10 minutes without reporting any progress until finished[/B][/I]
C:\ADB2>[B]adb shell[/B]
~ # [B]cd /data/media[/B]
cd /data/media
/data/media #[B] ls -l[/B]
ls -l
-rw-rw-rw- 1 root root 1102709591 Oct 3 03:56 Guru_Reset_M7_2.24.707.1.zip [I]<- just an example[/I]
/data/media # [B]md5sum Guru_Reset_M7_3.62.401.1.zip[/B]
md5sum Guru_Reset_M7_3.62.401.1.zip
6444b41a1f332f31345d5ead674382d7 Guru_Reset_M7_3.62.401.1.zip [B][I]<- confirm MD5 sum is correct[/I][/B]
/data/media #[B] exit[/B]
exit
C:\ADB2>
Click to expand...
Click to collapse
going out for an hour will post when I get back
there you go its all i get
C:\Fastboot>fastboot flash zip C:\Fastboot\ViperOne_3.1.0_RC2.zip
sending 'zip' (982337 KB)...
OKAY [ 42.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 42.812s
C:\Fastboot>adb push "C:\Fastboot\HTC One Toolkit 2.0 - Squabbi.zip"
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Fastboot>
You didn't read nkk71's example properly.
Assuming this file is good: HTC One Toolkit 2.0 - Squabbi.zip, rename to Squabbi.zip only
try:
C:\Fastboot>adb push Squabbi.zip /data/media/
How does it go?
iamsloany said:
there you go its all i get
C:\Fastboot>fastboot flash zip C:\Fastboot\ViperOne_3.1.0_RC2.zip
sending 'zip' (982337 KB)...
OKAY [ 42.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 42.812s
Click to expand...
Click to collapse
you cant fastboot flash a ROM. you have to, be in custom recovery, then:
adb push C:\Fastboot\ViperOne_3.1.0_RC2.zip /data/media/ <- this will take 5 to 10 min
then in recovery INSTALL ZIP -> choose zip -> ViperOne
and you should be good.
All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app
iamsloany said:
All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
all done? if yes, please add [SOLVED] to your main thread title. thanks
iamsloany said:
All fixed now using revone to s-off and sideloaded zip I'm back in the game.
Thanks for you help guys really appreciate it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I was having the same issue, but can't seem to get past it.
I have HBOOT 1.55 and CWM installed. S-ON.
I've tried Revone and Rumrunner but can't get S-OFF.
If I go back to Cyanogen Mod rom it works but I would like to try this ROM, no joy! http://forum.xda-developers.com/showthread.php?t=2544119&page=4

[Q] KFHD 7 Gen3 11.3.2.1 root

Hello,
I've tried to root my KFHD Gen 3 SW 11.3.2.1.
I've installed ADB interface and windows recognizes the KFHD as "Android Composite ADB Interface" in the hardware- manager.
First attemp to root: "Restore_by_Bin4ry_v31" an original "stock" cable. Batchfile runs, device is making backup, restarts 2 time - no root access
Second attemp: Selfmade fastboot cable. KFHD boots in fastboot mode und I've tried "11.3.2.1_root_script.zip" from xda forum - no root access.
Step- by step:
- connect with factory cable
- start runme.bat:
sending 'boot' (5846 KB)... OKAY [ 0.691s]
writing 'boot'... OKAY [ 0.437s]
finished. total time: 1.129s
...
Device detected: KFSOWI (JDQ39)
Attempt acdb exploit...
KFSOWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
ioctl: Bad address
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt perf_swevent exploit...
Root complete. Rebooting to fastboot...
Upgrade complete. Deactivating updates...
resuming boot... OKAY [ 0.001s]
finished. total time: 0.001s
[email protected]:/ $
KFHD reboots. Nothing happens. In the runme.bat are a lot more commands, but the command window isn't executing anything? Is the In the runme.bat are the next commands:
adb wait-for-device
echo Device connected. Pushing files...
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
echo Changing permissions...
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
echo Executing Exploit (could take some time, be patient!)
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
echo.
echo.
adb reboot
echo Root complete. Rebooting to fastboot...
fastboot -i 0x1949 wait-for-device
fastboot -i 0x1949 flash boot new-boot-prod.img
echo.
echo.
echo Upgrade complete. Deactivating updates...
fastboot -i 0x1949 continue
adb wait-for-device
adb shell
when i enter the commands by myself, it is not working. "Device not found"?
When i open another cmd window and enter the commands, it tells me, after executing
"adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"":
Error No such file or directory
Failed to obtain root privilege.
....
What can I do?

Unable to Root MRA58N

I have been going at it for a week straight and unable to find help. I am using Nexus Root Tool Kit 2.1.0. My Device is unlocked and OEM unlocked. However when i try to root the phone restarts into AP Fastboot Mode and nothing happens but the program seems like its trying but just unable to finish.
Log File:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3099
- AndroidDeviceListFull.ini 3099
- AndroidDeviceListFlash.ini 3099
SHAMU-SHAMU: Android 6.0.0 - Build: MRA58N
Live log initiated [2015-11-28]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Flashing Root Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_shamu_mra58n.img"
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Rebooting your device...
Waiting for your device...
I have also tried to flash a custom boot.img but NRT stops at rebooting device.
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Flashing boot.img to BOOT partition...
fastboot flash boot "C:\Users\Dave\Desktop\volantis-mra58n-boot-system\boot.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
my screen just never does anything i remember last time i rooted on Android L it went with no problems.
just stays at
AP Fast boot Flash Mode (Secure)
BL: moto-apq8084-71.15 (sha-96f7faf, 2015-08-04 11:36:17)
Base Band : D4.01-9625-05.27+fsg-9625-02.104
just installed ADB and tried from command prompt to flash TWRP and i got failed (data transfer failure (unknown error) )
well, you are doing it wrong for a nexus owner, you dont need a root toolkit. to root m you need to flash any custom kernel for m as well as the latest supersu(as well as the latest twrp recovery so you can flash a custom kernel and supersu).
Don't use Root kits and follow these steps. Start from step 1 if you already have your bootloader unlocked and if you have SDK tools installed (adb and fastboot). And you should be fine...
yes wont let me install recovery TWRP
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
thats because you dont use adb for this. you have to use fastboot while you are in your recovery. read that again, FASTBOOT instead of ADB. you always use fastboot to flash the factory image or any part of it, or twrp recovery.
simms, the command he posted that failed WAS fastboot.
HOWEVER, if adb is reporting devices, you are likely either booted to android or recovery... reboot to the bootloader
(turn off device, then hold volume down and while holding vol down press and hold power until the device boots to the bootloader mode.
Make sure that you have twrp in the same folder, and that you have renamed it to recovery.img (not .img.img as a lot of people accidently do) That last part isn't completely necessary, as its really just "fastboot flash recovery <file name>", and you can replace <file name> with the name of the recovery image it doesn't HAVE to be recovey.img, and it doesn't have to be in the same folder if you include path... but people find it easier to just rename it to recovery.img, copy it to their platform tools folder and use the command you ran.
ahh.. yea @scryan i didnt see that fastboot was used(later in the post). now i see hes uding adb devices instead of fastboot devices.
As far as I can see, you are trying to flash recovery using fastboot flash recovery recovery.img while not in bootloader (or you didn't copy everything you did).
You should:
1. adb reboot bootloader (your phone will reboot into bootloader)
2. now you can write "fastboot devices" to see if your phone is recognized
2. then if it's there: "fastboot flash recovery recovery.img"
EDIT: If you still did everything correctly, quick google search said it could be problem with computer's USB port. Try another port...
I have tried every port on my pc some give unrecognized USB error while others work. If I am able to charge and transfer files along with send adb commands (restart phone,adb sees my phone) does that rule out the USB cable? I bought a pack of four on ebayhttp://m.ebay.com/itm/4x-6Ft-Micro-USB-Charger-Sync-Data-Cable-Nylon-Braided-for-Samsung-Galaxy-HTC-/221891441910?txnId=1650092351012
I no longer have the cable I used to flash marshmallow but I did use this to unlock the device.

Categories

Resources