DirtyCow Test - LG G5 Guides, News, & Discussion
Someone please test this. I can't right now (at work, don't have G5) so please update me. It works on my HTC 10 but I do not know if it will work on the G5...
CODE:
adb push arm64-v8a/dirtycow /data/local/tmp
adb push arm64-v8a/run-as /data/local/tmp
adb shell 'chmod 777 /data/local/tmp/run-as'
adb shell 'chmod 777 /data/local/tmp/dirtycow'
adb shell '/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as'
adb shell /system/bin/run-as
Honestly Annoying said:
Someone please test this. I can't right now (at work, don't have G5) so please update me. It works on my HTC 10 but I do not know if it will work on the G5...
CODE:
adb push arm64-v8a/dirtycow /data/local/tmp
adb push arm64-v8a/run-as /data/local/tmp
adb shell 'chmod 777 /data/local/tmp/run-as'
adb shell '/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as'
Click to expand...
Click to collapse
I tested those commands but what result are you waiting for ?
YassGo said:
I tested those commands but what result are you waiting for ?
Click to expand...
Click to collapse
Well, what happened?
Also, try and open an adb shell with "adb shell"
EDIT Goddamnit I forgot the last command. My bad! Please try again.
Honestly Annoying said:
Well, what happened?
Also, try and open an adb shell with "adb shell"
Click to expand...
Click to collapse
That's what I've did for the last two commands :
C:\>adb push arm64-v8a/dirtycow /data/local/tmp
[100%] /data/local/tmp/dirtycow
C:\>adb push arm64-v8a/run-as /data/local/tmp
[100%] /data/local/tmp/run-as
C:\>adb shell
[email protected]:/ $ chmod 777 /data/local/tmp/run-as
tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as
/system/bin/sh: /data/local/tmp/dirtycow: can't execute: Permission denied
YassGo said:
That's what I've did for the last two commands :
C:\>adb push arm64-v8a/dirtycow /data/local/tmp
[100%] /data/local/tmp/dirtycow
C:\>adb push arm64-v8a/run-as /data/local/tmp
[100%] /data/local/tmp/run-as
C:\>adb shell
[email protected]:/ $ chmod 777 /data/local/tmp/run-as
tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as
/system/bin/sh: /data/local/tmp/dirtycow: can't execute: Permission denied
Click to expand...
Click to collapse
You aren't running my commands. Just copy and post exactly what I posted
C:\>adb push arm64-v8a/dirtycow /data/local/tmp
[100%] /data/local/tmp/dirtycow
C:\>adb push arm64-v8a/run-as /data/local/tmp
[100%] /data/local/tmp/run-as
C:\>adb shell 'chmod 777 /data/local/tmp/run-as'
/system/bin/sh: chmod 777 /data/local/tmp/run-as: not found
C:\>adb shell '/data/local/tmp/dirtycow /system/bin/run-as /da
s'
/system/bin/sh: /data/local/tmp/dirtycow /system/bin/run-as /d
as: not found
C:\>adb shell /system/bin/run-as
run-as: Usage:
run-as <package-name> [--user <uid>] <command> [<args>]
YassGo said:
C:\>adb push arm64-v8a/dirtycow /data/local/tmp
[100%] /data/local/tmp/dirtycow
C:\>adb push arm64-v8a/run-as /data/local/tmp
[100%] /data/local/tmp/run-as
C:\>adb shell 'chmod 777 /data/local/tmp/run-as'
/system/bin/sh: chmod 777 /data/local/tmp/run-as: not found
C:\>adb shell '/data/local/tmp/dirtycow /system/bin/run-as /da
s'
/system/bin/sh: /data/local/tmp/dirtycow /system/bin/run-as /d
as: not found
C:\>adb shell /system/bin/run-as
run-as: Usage:
run-as <package-name> [--user <uid>] <command> [<args>]
Click to expand...
Click to collapse
It sounds like there's a problem with your /tmp/ directory. Try running "adb shell 'chmod 777 /data/local/tmp/' "
C:\>adb shell 'chmod 777 /data/local/tmp/'
/system/bin/sh: chmod 777 /data/local/tmp/: not found
I can't even ls local directory....but I see your two files in tmp
255|[email protected]:/data/local $ cd tmp
[email protected]:/data/local/tmp $ ls
dirtycow
run-as
[email protected]:/data/local/tmp $
YassGo said:
C:\>adb shell 'chmod 777 /data/local/tmp/'
/system/bin/sh: chmod 777 /data/local/tmp/: not found
I can't even ls local or tmp directory....
Click to expand...
Click to collapse
What the heck dude?? I've never heard of that error... it seems like you just don't have a tmp directory.
Honestly Annoying said:
What the heck dude?? I've never heard of that error... it seems like you just don't have a tmp directory.
Click to expand...
Click to collapse
Sorry dude I edited my message.
adb push arm64-v8a/dirtycow /data/local/tmp
adb push arm64-v8a/run-as /data/local/tmp
adb shell 'chmod 777 /data/local/tmp/run-as'
adb shell 'chmod 777 /data/local/tmp/dirtycow'
adb shell '/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as'
--> warning: new file size (5960) and file old size (14192) diffe
size 14192
[*] mmap 0x7f7eb44000
[*] exploit (patch)
[*] currently 0x7f7eb44000=10102464c457f
[*] madvise = 0x7f7eb44000 14192
[*] madvise = 0 1048576
[*] /proc/self/mem 1996488704 1048576
[*] exploited 0x7f7eb44000=10102464c457f
adb shell /system/bin/run-as
--> running as uid 2000
uid 0
YassGo said:
Sorry dude I edited my message.
Click to expand...
Click to collapse
Ah okay see that now. Do this
adb shell
/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as
/system/bin/run-as
Basically, this adds the "run-as" to the /system/bin directory, which is only accessible by root
Honestly Annoying said:
Ah okay see that now. Do this
adb shell
/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as
/system/bin/run-as
Basically, this adds the "run-as" to the /system/bin directory, which is only accessible by root
Click to expand...
Click to collapse
Okay you forgot chmod 777 on the dirtycow file. Here's what I get now with the last two commands :
adb push arm64-v8a/dirtycow /data/local/tmp
adb push arm64-v8a/run-as /data/local/tmp
adb shell 'chmod 777 /data/local/tmp/run-as'
adb shell 'chmod 777 /data/local/tmp/dirtycow'
adb shell '/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as'
--> warning: new file size (5960) and file old size (14192) diffe
size 14192
[*] mmap 0x7f7eb44000[*] exploit (patch)[*] currently 0x7f7eb44000=10102464c457f[*] madvise = 0x7f7eb44000 14192[*] madvise = 0 1048576[*] /proc/self/mem 1996488704 1048576[*] exploited 0x7f7eb44000=10102464c457f
adb shell /system/bin/run-as
--> running as uid 2000
uid 0
YassGo said:
Okay you forgot chmod 777 on the dirtycow file. Here's what I get now with the last two commands :
adb push arm64-v8a/dirtycow /data/local/tmp
adb push arm64-v8a/run-as /data/local/tmp
adb shell 'chmod 777 /data/local/tmp/run-as'
adb shell 'chmod 777 /data/local/tmp/dirtycow'
adb shell '/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/run-as'
--> warning: new file size (5960) and file old size (14192) diffe
size 14192
[*] mmap 0x7f7eb44000[*] exploit (patch)[*] currently 0x7f7eb44000=10102464c457f[*] madvise = 0x7f7eb44000 14192[*] madvise = 0 1048576[*] /proc/self/mem 1996488704 1048576[*] exploited 0x7f7eb44000=10102464c457f
adb shell /system/bin/run-as
--> running as uid 2000
uid 0
Click to expand...
Click to collapse
Oh crap so sorry! Now run
adb shell
whoami
cd /data
ls
Please post results of that!
[email protected]:/data/local/tmp $ whoami
shell
[email protected]:/data/local/tmp $ cd /data
[email protected]:/data $ ls
opendir failed, Permission denied
YassGo said:
[email protected]:/data/local/tmp $ whoami
shell
[email protected]:/data/local/tmp $ cd /data
[email protected]:/data $ ls
opendir failed, Permission denied
Click to expand...
Click to collapse
Okay, so here's what I can see of this then. This DOES open a root shell, but it closes the shell right after placing "run-as" into /system/bin. If we can keep the shell open then bam root!
YassGo said:
[email protected]:/data/local/tmp $ whoami
shell
[email protected]:/data/local/tmp $ cd /data
[email protected]:/data $ ls
opendir failed, Permission denied
Click to expand...
Click to collapse
WAIT actually try running
SEE NEXT POST
[email protected]:/data $ cd /data/local/tmp
[email protected]:/data/local/tmp $ run-as cat /init.flo.diag.rc
running as uid 2000
uid 0
YassGo said:
[email protected]:/data $ cd /data/local/tmp
[email protected]:/data/local/tmp $ run-as cat /init.flo.diag.rc
running as uid 2000
uid 0
Click to expand...
Click to collapse
Oops, close that root shell and just do
adb shell
run-as cat /init.flo.diag.rc
C:\>adb shell
[email protected]:/ $ run-as cat /init.flo.diag.rc
running as uid 2000
uid 0
YassGo said:
C:\>adb shell
[email protected]:/ $ run-as cat /init.flo.diag.rc
running as uid 2000
uid 0
Click to expand...
Click to collapse
wtf it should be working.
Here's some to try, tell me if any of these work
adb shell
run-as id
run-as ls -lZ /sbin/
run-as ls -lZ /data/
Related
adb push su - Why doesnt this work on the Eris?
This doesnt work on the Eris but I was just wondering if anyone knows why. I am not a linux expect so the answer is probably obvious. I was wondering if we could just adb push the "su" command to the phone, execute and get root. Then I found this link to a tutorial on how to root the Magic by using adb to push a modified su command to the phone: http://android-dls.com/wiki/index.php?title=Magic_Root_Access Code: C:\>adb push su /data/local 952 KB/s (76232 bytes in 0.078s) C:\>adb shell $ cd /data/local cd /data/local $ ls -l ls -l -rw-rw-rw- shell shell 76232 2009-07-31 19:08 su drwxrwxrwx shell shell 2010-03-01 04:19 dmdata drwxrwx--x shell shell 2010-03-26 10:29 tmp drwxrwxrwx shell shell 2010-03-26 10:29 rights -rw-rw-rw- shell shell 399435 2010-03-26 13:51 bootanimation.zip $ chmod 777 su chmod 777 su $ ls -l ls -l -rwxrwxrwx shell shell 76232 2009-07-31 19:08 su drwxrwxrwx shell shell 2010-03-01 04:19 dmdata drwxrwx--x shell shell 2010-03-26 10:29 tmp drwxrwxrwx shell shell 2010-03-26 10:29 rights -rw-rw-rw- shell shell 399435 2010-03-26 13:51 bootanimation.zip $ ./su ./su su: access granted, courtesy of www.magicandroidapps.com su: permission denied
You can push it, but you will be unable to set the right permissions.
I am able to "chmod 777 su" successfully. Or are you talking about some other permissions?
DarthMowzy said: I am able to "chmod 777 su" successfully. Or are you talking about some other permissions? Click to expand... Click to collapse He's talking about super user permissions (chmod 4777)
-rwxrwxrwx shell shell 76232 2009-07-31 19:08 su Click to expand... Click to collapse Owner - shell. "chmod 4777" will not work =( mb you can change owner...
that would mean I could hack any computer or server i wanted if i just had a copy of su lol
Root Froyo 318
I have upgraded from 309 to 318.......wanting to root it using z4root and universal androot but both apps dont work for this 318 version..... does anyone have any clues to what i can do? please advise, thanks
Please Do Not Post the Same Question in 2 Forums i will Lock this one as i have answered the other one
Quoted from fards' thread: http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage Been rooting this way since day 1 -- if you aren't the type in command prompt, you can also just copy and paste the command lines exactly~ GET ECLAIR/FROYO version of Superuser.apk and su from http://forum.xda-developers.com/showthread.php?t=682828 extract the two files to the directory you're working from.. GET rageagainstthecage from http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz extract the rageagainstthecage-arm5.bin to the same directory you're working from open a terminal/command line adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage adb push Superuser.apk /data/local/tmp/Superuser.apk adb push su /data/local/tmp/su adb push busybox /data/local/tmp/busybox adb shell chmod 700 /data/local/tmp/rageagainstthecage adb shell chmod 700 /data/local/tmp/busybox adb shell cd /data/local/tmp ./rageagainstthecage ******this will kill adb server but manually kill it anyway and restart it ****** adb kill-server adb start-server * daemon not running. starting it now * * daemon started successfully * adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system **********Follow the following steps to install Superuser.apk, busybox,su **************** cd /data/local/tmp ./busybox cp busybox /system/bin/ chmod 4755 /system/bin/busybox busybox cp Superuser.apk /system/app/ busybox cp su /system/bin/ chmod 4755 /system/bin/su exit exit then reboot streak ************to remount filesystem as readonly,************* adb shell # su su #mount -o remount,ro -t yaffs2 /dev/block/mtdblock6 /system # exit exit Click to expand... Click to collapse
[Q] Htc desire HDHelp! Cmd failure when downgrading from 1.72 (Rooting)
Android SDK installed in programfiles ADB in this folder : C:\Program Files\Android\android-sdk-windows\platform-tools written in cmd, with USB debugging activated and charge only. C:\Users\any\adb devices. my device shows! Is this the right thing to insert to cmd or the one below 1. Answers! adb push psneuter /data/local/tmp : A bunch adb commands shows adb push misc_version /data/local/tmp : A bunch adb commands shows adb shell chmod 777 /data/local/tmp/psneuter :unable to chmod, no such file adb shell chmod 777 /data/local/tmp/misc_version :unable to chmod no such file adb shell /data/local/tmp/psneuter : Not found adb shell :$ or this 2. adb push psneuter C:\Program Files\Android\android-sdk-windows\platform-tools adb push misc_version C:\Program Files\Android\android-sdk-windows\platform-tools adb shell chmod 777 C:\Program Files\Android\android-sdk-windows\platform-tools/psneuter adb shell chmod 777 C:\Program Files\Android\android-sdk-windows\platform-toolsmisc_version adb shell C:\Program Files\Android\android-sdk-windows\platform-toolspsneuter adb shell Have I installed the Android SDK in the wrong folder or what is thats going wrong?
Official update to 1.82.405.1 stock ROM (from 1.72..) and root
Hi there, I tried if it is possible root on stock ROM 1.82.405.1 on HTC Desire Z. YES, we can! This is a little "how to" with all previous roots and updates from "1.34.." to actual 1.82.405.1 stock ROM: Permanent root on HTC ESIRE Z using linux Software No. 1.34... Necessary files: adb (Android SDK) gfree_02 psneuter Terminal emulator (Android) Optional files: gfree_verify Settings on Phone: Menu-Settings-Applications-Development-USB debugging [yop] USB connected to PC – only charge (card not mounted to PC) Procedure on PC: Check your device is properly conneted: $ ./adb devices It has to be like this : SH0BFRT00451 device Than continue: $ ./adb push su /sdcard/su $ ./adb push Superuser.apk /sdcard/Superuser.apk $ ./adb push rage /data/local/tmp/rage $ ./adb push busybox /data/local/tmp/busybox $ ./adb push root /data/local/tmp/root $ ./adb shell chmod 0755 /data/local/tmp/* On Android: Launch Terminal Emulator $ /data/local/tmp/rage Wait for the message: "Forked #### childs." Menu > Reset Term - Terminal Emulator will exit. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell Procedure on PC: $ ./adb push gfree /data/local On Android: # cd /data/local # chmod 777 gfree # ./gfree -f # sync # /data/local/tmp/root # sync there can be some errors with directory create – it is ok. update to 1.72 via system and do following again: ./adb push su /sdcard/su ./adb push Superuser.apk /sdcard/Superuser.apk ./adb push busybox /data/local/tmp/busybox ./adb push root /data/local/tmp/root ./adb shell chmod 0755 /data/local/tmp/* ./adb push psneuter /data/local/tmp/psneuter ./adb shell chmod 777 /data/local/tmp/psneuter ./adb shell /data/local/tmp/psneuter ./adb shell Finally execute this inside the shell you opened with the previous command >adb shell<: /data/local/tmp/root restart mobile and you have root.... update from 1.72 to 1.82 via system and again root: ./adb push su /sdcard/su ./adb push Superuser.apk /sdcard/Superuser.apk ./adb push busybox /data/local/tmp/busybox ./adb push root /data/local/tmp/root ./adb shell chmod 0755 /data/local/tmp/* ./adb push psneuter /data/local/tmp/psneuter ./adb shell chmod 777 /data/local/tmp/psneuter ./adb shell /data/local/tmp/psneuter ./adb shell Finally execute this inside the shell you opened with the previous command >adb shell<: /data/local/tmp/root restart mobile and you have root.... Superusere error is patchable by this: http://forum.xda-developers.com/showthread.php?t=886999 check /sys/devices/system/cpu/cpu0/cpufreq/current_scaling_freq
But do we need to be already on 1.82++ or do we need to downgrade to 1.34++ because I don't really understand what we have to do! PS: really really thank you!!!!! (all other root methods failed for me, so fingers crossed that this one will work!)
You need to have S-OFF; if you don't you need to go to 1.34 to get it, then upgrade back up the chain...
oh, thanks... I guess I'll have to downgrade then, wouldn't I
I guess so, but should only have to do it once... Sent from my HTC Vision using XDA App
I rooted my 1.72 device a while ago with this tut: http://forum.xda-developers.com/showthread.php?t=905261 Should I be fine by just executing the latest part off this tut? Code: update from 1.72 to 1.82 via system and again root: ./adb push su /sdcard/su ./adb push Superuser.apk /sdcard/Superuser.apk ./adb push busybox /data/local/tmp/busybox ./adb push root /data/local/tmp/root ./adb shell chmod 0755 /data/local/tmp/* ./adb push psneuter /data/local/tmp/psneuter ./adb shell chmod 777 /data/local/tmp/psneuter ./adb shell /data/local/tmp/psneuter ./adb shell Finally execute this inside the shell you opened with the previous command >adb shell<: /data/local/tmp/root restart mobile and you have root....
I got error: E:signature verification failed I'm using clockwork recovery 2.5.1.3. I think that's the reason, anyone got a fix for this?
hi, I have desire Z with bootloader 1.82.405.1 , from which stage should I start the rooting process?
[Q] twrp d80010o....SOLVED.....
Have anyone figured out how to put twrp on version ATT D80010o
If you pull the aboot.img I'll patch twrp for the device [email protected]:~$ adb shell [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s)
datechnerd said: If you pull the aboot.img I'll patch twrp for the device [email protected]:~$ adb shell [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s) Click to expand... Click to collapse how do i do this
ralphie1267 said: how do i do this Click to expand... Click to collapse enable usb debugging, plug phone into pc, and you'll need adb in attachments open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post
datechnerd said: enable usb debugging, plug phone into pc, and you'll need adb in attachments open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post Click to expand... Click to collapse i have minumal adb and fastboot can i use this
datechnerd said: If you pull the aboot.img I'll patch twrp for the device [email protected]:~$ adb shell [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s) Click to expand... Click to collapse sorry for the late response I was at work....
datechnerd said: If you pull the aboot.img I'll patch twrp for the device [email protected]:~$ adb shell [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]roid:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s) Click to expand... Click to collapse for some reason I cant run command I downloaded it to the desktop
antawnm26 said: for some reason I cant run command I downloaded it to the desktop Click to expand... Click to collapse put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window
datechnerd said: put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window Click to expand... Click to collapse sweet it came up...Im not that great at it so Im going to need you to walk me through it [email protected]:~$ adb shell- this should be my user name? [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s)
antawnm26 said: sweet it came up...Im not that great at it so Im going to need you to walk me through it [email protected]:~$ adb shell- this should be my user name? [email protected]:/ $ su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img [email protected]:/ # chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit [email protected]:/ $ exit [email protected]:~$ adb pull /data/local/tmp/aboot.img 3293 KB/s (2097152 bytes in 0.621s) Click to expand... Click to collapse the username is just from an example
datechnerd said: the username is just from an example Click to expand... Click to collapse ok im getting errors when I copy ~$ adb shell C:\Users\Bull\Desktop\adb>~$ adb shell '~$' is not recognized as an internal or external command, operable program or batch file.
antawnm26 said: ok im getting errors when I copy ~$ adb shell C:\Users\Bull\Desktop\adb>~$ adb shell '~$' is not recognized as an internal or external command, operable program or batch file. Click to expand... Click to collapse just type Code: adb shell don't type $ or #
C:\Users\Bull\Desktop\adb>:/ $ su C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo t of=/data/local/tmp/aboot.img C:\Users\Bull\Desktop\adb>adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * [email protected]:/ $ su su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc al/tmp/aboot.img dcc.1/by-name/aboot of=/data/local/tmp/aboot.img < 2048+0 records in 2048+0 records out 1048576 bytes transferred in 0.100 secs (10485760 bytes/sec) [email protected]:/ # chmod 644 /data/local/tmp/aboot.img chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit exit [email protected]:/ $ exit exit C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img 'pull' is not recognized as an internal or external command, operable program or batch file. C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img '~$' is not recognized as an internal or external command, operable program or batch file. C:\Users\Bull\Desktop\adb>
d80010o Any success guys?
datechnerd said: just type Code: adb shell don't type $ or # Click to expand... Click to collapse i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks
ralphie1267 said: i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks Click to expand... Click to collapse think i got it i had to use esfile explorer to get it from the data/local because i suck at adb, but i got all the way with but started getting errors..hold on let me put it in drive
Code: [CODE] [/CODE] antawnm26 said: C:\Users\Bull\Desktop\adb>:/ $ su C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo t of=/data/local/tmp/aboot.img C:\Users\Bull\Desktop\adb>adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * [email protected]:/ $ su su [email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc al/tmp/aboot.img dcc.1/by-name/aboot of=/data/local/tmp/aboot.img < 2048+0 records in 2048+0 records out 1048576 bytes transferred in 0.100 secs (10485760 bytes/sec) [email protected]:/ # chmod 644 /data/local/tmp/aboot.img chmod 644 /data/local/tmp/aboot.img [email protected]:/ # exit exit [email protected]:/ $ exit exit C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img 'pull' is not recognized as an internal or external command, operable program or batch file. C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img '~$' is not recognized as an internal or external command, operable program or batch file. C:\Users\Bull\Desktop\adb> Click to expand... Click to collapse Code: adb pull /data/local/tmp/aboot.img
datechnerd said: Code: [CODE] [/CODE] Code: adb pull /data/local/tmp/aboot.img Click to expand... Click to collapse https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9
antawnm26 said: https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9 Click to expand... Click to collapse NON-flashablezips flash with loki if you don't know how rename the .lok to .img and put it on your phone and flash it with flashify instead
datechnerd said: flash with loki if you don't know how take the .img put it on your phone and flash it with flashify instead Click to expand... Click to collapse I know its asking a lot but is there a guide on flashing with loki? also, do i just copy the image without the other files to my sdcard and flash with flashify?