adb shell, dd, and basebands - Galaxy S 5 Q&A, Help & Troubleshooting

Greets.
Working with an SM-G900T that's still on a KitKat baseband. I'm attempting to use `adb shell` and `dd` to update my baseband firmware. I've backed up both modem.bin and NON-HLOS.bin before attempting this. Here's what the commands and output looks like:
Code:
→ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/mnt/sdcard/Download/NON-HLOS.bin of=/dev/block/mmcblk0p1
dd: /dev/block/mmcblk0p1: Operation not permitted
1+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
1|[email protected]:/ #
I'm stuck on the 'Operation not permitted' bit, and I can't find any information on that on the web. Any ideas?
(I've exhausted all of the other roads to accomplish this; OSX JOdin, Mobile Odin, and heimdall. I've spent a lot of time trying to get each to work with no success, so please leave those out as suggestions.)

Related

[Q] Help please, can't seem to reach Clockwork. Logs included, thanks!

Hi there. I got an Epic 4G not too long ago, and I've been attempting to root and install Clockwork to get some custom ROMs on it.
Installed Samsung drivers, phone connects fine. I'm not mounting the SD card, and I've tried it in Charge Only and USB Mass Storage modes.
I ran the sticky'd root method (2.2.6) from the Development subforum under the Epic 4G. Here is my log from that:
Code:
C:\Users\___>CD C:\Users\___\Desktop\Root
C:\Users\___\Desktop\root>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\root>run.bat
exploit and busybox made by joeykrim and one click installer made by noobnl and
firon
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
128 KB/s (5392 bytes in 0.041s)
3 KB/s (88 bytes in 0.026s)
[*] 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 2208
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 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.
make it RW and move files
30 KB/s (687 bytes in 0.022s)
246 KB/s (26264 bytes in 0.104s)
355 KB/s (196521 bytes in 0.540s)
327 KB/s (14428 bytes in 0.043s)
9 KB/s (201 bytes in 0.020s)
413 KB/s (511436 bytes in 1.207s)
8 KB/s (203 bytes in 0.024s)
24 KB/s (479 bytes in 0.019s)
set permission
install busybox
push any key to reboot the phone
Press any key to continue . . .
Alright, so it rebooted. I can see SuperUser, and I can run apps that require root work perfectly (that screenshot one, etc).
So, I go to install Clockwork from the SDX forum (crossposted [link to noobnl's post spliced]). I ran "run-try-first.bat"
Code:
C:\Users\___>CD C:\Users\Media\Desktop\clockwork
C:\Users\___\Desktop\clockwork>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\clockwork>adb shell
$ su
su
# exit
exit
$ exit
exit
C:\Users\___\Desktop\clockwork>run-try-first.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeeters
lint, and koush
Press any key to continue . . .
remove stock recovery patcher
mount: Operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
copy kernel and flasher
432 KB/s (313888 bytes in 0.708s)
462 KB/s (5820868 bytes in 12.299s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>
So, that seems like it didn't really work. I rebooted and went to recovery with ADB on the computer, with the volume + camera + power method, and got the stock recovery each time.
I went back in and installed ROM Manager, and flashed the newest build for the Epic, didn't work, stock recovery with the E: verification failed error.
I returned to my PC to try "run-try-last.bat"
Code:
C:\Users\___\Desktop\clockwork>run-try-last.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeetersl
int, and koush
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
146 KB/s (5392 bytes in 0.036s)
4 KB/s (88 bytes in 0.020s)
[*] 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 2209
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 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.
remove stock recovery patcher
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
copy kernel and flasher
459 KB/s (313888 bytes in 0.667s)
343 KB/s (5820868 bytes in 16.535s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 53700 bytes
read finished
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>adb reboot recovery
Same thing, didn't work. I am currently guessing that the:
Code:
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
is the problem, since I can't seem to remove these files? I don't know.
Help is appreciated! Thanks much!
EDIT
Code:
C:\Users\Media>CD C:\Users\Media\Desktop\Root
C:\Users\Media\Desktop\root>adb shell mount -t rfs -o remount,rw /dev/block/stl9
/system
mount: Operation not permitted
C:\Users\Media\Desktop\root>adb shell
$ su
su
# mount -t rfs -o remount,rw /dev/block/stl9 /system
mount -t rfs -o remount,rw /dev/block/stl9 /system
# rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
# rm /system/recovery/recovery-from-boot.p
rm /system/recovery/recovery-from-boot.p
rm failed for /system/recovery/recovery-from-boot.p, No such file or directory
#
These files actually don't exist or something
I am having this exact same problem. When I try to use clockwork it goes to the stock android recovery mode and I receive the signature error.
are you rooted first?
nevermind sorry
I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps
jimmyz said:
I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps
Click to expand...
Click to collapse
I tried to do this and here is what I got. I may have messed up since I am new to this.
c:\samsung>adb shell
$ su
su
remount rw
remount rw
Permission denied
$ Remounting /system </dev/st19> in read/write mode
mount: Operation not permitted
$
Does anyone think it could be caused by the system update that has been rolling out? I downloaded that before I rooted.
I am having the same problem while trying to get Clockwork to work correctly on my Epic.
I also think that the problem is related to the install-recovery.sh and recovery-from-boot.p files. If I run a batch file (run.bat or run-try-first.bat or run-try-last.bat) the first problem is always when it tries to remove these files.
First I tried to just remove the install-recover.sh file
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
The system reported that the file system was read-only.
Next I changed the file system to be writable.
>adb shell
$ su
su
# remount rw
remount rw
Remounting /system (/dev/stl9) in read/write mode
# exit
exit
$ exit
exit
This seemed to work ok and no errors were reported
Last I tried to delete the file again.
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
This time the system reported that the file (or directory) was not found.
All of the updates have been applied to this phone.
I'm just getting into the Android world so I'm pretty lost right now. I am able to get into the clockwork recovery if I hold the volume-down, camera button and the power button down until the phone is fully turned on. I am not able to update the phone's rom and this problem seems to be tied back to that the phone is not "really" rooted (this is pretty much just a guess...)
Thank you in advance for any help or suggestions you may offer!
Scott
Hi there.
I've redone the entire phone a few times now with Odin. Each time I try a new method of root/flashing clockwork. I've tried in every combination:
-Using Noobl's stuff, including 2.2.7, 2.2.6, and I guess 2.2.5 or whatever he published before that
-Using Koush's clockwork and noobl's clockwork things, both -first and -last
-Pulling the battery during the clockwork reboot and using the camera + volume + power
-Using ADB rebooting and quick rebooting
-Remounting the system RW between root and clockwork, before both, etc
Nothing has worked, tried with no updates applied and with all 3, and with the first one. I guess this android stuff just isn't my cup of tea after all. Time to wait for WP7, I suppose (can't stand this 5 hour battery crap, was hoping to fix it). Tried it on 3 computers, done it every conceivable way.
Thanks to the modding community, rooting community, and everybody who writes the guides. I guess I'm just unlucky or something.
EDIT: Disregard that, randomly worked after pulling the battery during the reboot following Noobl's clockwork install...... well then
If you want to try one last time I would try to manually root etc by entering one line at a time via adb
Sent from my SPH-D700 using XDA App
Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...
juchmis said:
Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...
Click to expand...
Click to collapse
This is expected behavior if you just used noobnl one click- it installs to bml8. IF you want to reach clockwork through Rom Manager you need to have a modified kernel (on bml7) which many of the custom Roms have built in. After you you do that adb reboot will work but only if you keep the appropriate clockworkwod mod update.zip in the root of your sdcard and select it through the "stock" recovery- this is "fakeflash"

[Request] Oppo Find 5 'boot.img' extract from device

Hey Folks,
Is there anyone who wants to extract the basic stock kernel from the Oppo Find 5.
I don't have the Oppo Find 5 yet, but I want to make a custom kernel for it.
Instructions:
- Make sure you have ADB set up
- Make sure your device is in USB debugging
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
exit
adb pull /sdcard/boot.img
Thanks in advance!
Ps: A big thanks to the one that wants to do this!
brakke97 said:
Hey Folks,
Is there anyone who wants to extract the basic stock kernel from the Oppo Find 5.
I don't have the Oppo Find 5 yet, but I want to make a custom kernel for it.
Instructions:
- Make sure you have ADB set up
- Make sure your device is in USB debugging
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
exit
adb pull /sdcard/boot.img
Thanks in advance!
Ps: A big thanks to the one wants to do this!
Click to expand...
Click to collapse
you probably want the ramdisk.gz ?
http://files.ngvincent.com/android/oppo-find-5/kernel/ramdisk.gz
if you want a walk through of building the kernel source
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki
@paperWastage Thanks for the help!
paperWastage said:
you probably want the ramdisk.gz ?
http://files.ngvincent.com/android/oppo-find-5/ramdisk.gz
if you want a walk through of building the kernel source
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki
Click to expand...
Click to collapse
The link from the ramdisk.gz is dead.
Do you have a mirror site?
brakke97 said:
Hey Folks,
Is there anyone who wants to extract the basic stock kernel from the Oppo Find 5.
I don't have the Oppo Find 5 yet, but I want to make a custom kernel for it.
Instructions:
- Make sure you have ADB set up
- Make sure your device is in USB debugging
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
exit
adb pull /sdcard/boot.img
Thanks in advance!
Ps: A big thanks to the one that wants to do this!
Click to expand...
Click to collapse
Code:
c:\AndroidSDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.552 secs (18995942 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull /sdcard/boot.img
adb pull /sdcard/boot.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
However found the boot.img on the root of sdcard but failed to open it, maybe you have a better luck
Hello everyone,
I was wondering if there is any support for the T-Mobile LG Optimus F6? I was able to pull the aboot.img from the device, but I am not sure if this is even compatible or not? Here is the aboot.img attached to this post. Is it possible for someone to take a look at this? Thanks!
KaminoReal said:
Code:
c:\AndroidSDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/boot.img
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.552 secs (18995942 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull /sdcard/boot.img
adb pull /sdcard/boot.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
However found the boot.img on the root of sdcard but failed to open it, maybe you have a better luck
Click to expand...
Click to collapse
thats because you need to split it first! with

[Q] Loki flash??

ok here's the lowdown.
Verizon lg g2
rooted = yes
downloaded or a update in December = yes
installed twrp using the freegee app in the app market. not sure if their method implies the Loki boot loader bypass.
my question is is their a way to imply Loki bypass no. twrp does work but I can't successfully flash any roms and I believe it's the lack of Loki being implemented.
Here's loki patched twrp and loki patched boot
extract and flash
datechnerd said:
Here's loki patched twrp and loki patched boot
extract and flash
Click to expand...
Click to collapse
Still kinda new to the whole flash game.. I'm using flashify and it has three flash options
boot image
recovery image
and zip file..
which option do I use to flash.
sorry if the question seems obscene.
joewaz said:
Still kinda new to the whole flash game.. I'm using flashify and it has three flash options
boot image
recovery image
and zip file..
which option do I use to flash.
sorry if the question seems obscene.
Click to expand...
Click to collapse
Those are great questions..
I am having a issue close to yours..
I am going to use the boot as boot and the recovery as recovery.
These phone are quite a bit different than htc
http://forum.xda-developers.com/showthread.php?t=2449670 here's a guide
example for twrp
[email protected]:~$ adb push twrp.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
example for boot
[email protected]:~$ adb push boot.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
datechnerd said:
http://forum.xda-developers.com/showthread.php?t=2449670 here's a guide
example for twrp
[email protected]:~$ adb push twrp.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
example for boot
[email protected]:~$ adb push boot.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Click to expand...
Click to collapse
is this something you have to use adb or can you use flashify
joewaz said:
is this something you have to use adb or can you use flashify
Click to expand...
Click to collapse
Looks like adb to me.
i read a post were someone said you could change .lok to ,img and use flashify, you could give it a shot, they said it the same thing
I am getting errors
C:\max\loki-master>adb devices
List of devices attached
LG-LS980-03a89c4cdf4ce82c device
C:\max\loki-master>adb push loki_flash /data/local/tmp/loki_flash
cannot stat 'loki_flash': No such file or directory
C:\max\loki-master>adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/
openrecovery-twrp-2.6.3.2
cannot stat 'openrecovery-twrp-2.6.3.2-g2vzw.img': No such file or directory
C:\max\loki-master>adb push loki_flash /data/local/tmp
797 KB/s (3271 bytes in 0.004s)
C:\max\loki-master>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /data/local/tmp/loki_flash
/data/local/tmp/loki_flash
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
126|[email protected]:/ $ su
su
# /data/local/tmp/loki_flash
# /data/local/tmp/loki_flash
1|[email protected]:/ $ # /data/local/tmp/loki_flash
1|[email protected]:/ $ /data/local/tmp/loki_flash [boot|recovery] [in.lok]
/data/local/tmp/loki_flash [boot|recovery] [in.lok]
/system/bin/sh: recovery]: not found
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
127|[email protected]:/ $ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp
.lok
recovery /data/local/tmp/twrp.lok <
127|[email protected]:/ $ adb push boot.lok /data/local/tmp
adb push boot.lok /data/local/tmp
error: device not found
1|[email protected]:/ $ exit
exit
C:\max\loki-master>adb push boot.lok /data/local/tmp
4553 KB/s (9848832 bytes in 2.112s)
C:\max\loki-master>adb push loki_flash /data/local/tmp
1595 KB/s (3271 bytes in 0.002s)
C:\max\loki-master>adb shell
[email protected]:/ $ su
su
# /data/local/tmp/loki_flash
# /data/local/tmp/loki_flash
1|[email protected]:/ $ # /data/local/tmp/loki_flash
1|[email protected]:/ $ /data/local/tmp/loki_flash [boot|recovery] [in.lok]
/data/local/tmp/loki_flash [boot|recovery] [in.lok]
/system/bin/sh: recovery]: not found
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
127|[email protected]:/ $ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
boot /data/local/tmp/boot.lok <
127|[email protected]:/ $
Try renaming boot.lok to boot.img and twrp.lok to twrp.img and using flashify. If you still can't get it to work let me know
12B?
If yes, you're out of luck.
If no, what datechnerd said.
Steamer86 said:
12B?
If yes, you're out of luck.
If no, what datechnerd said.
Click to expand...
Click to collapse
I patched twrp for 12b I also patched cwm for 12b
@datechnerd I just saw that. Nice. I used the flashify method for CWM ( loki version) on 11A, loki errors. Never got around to pushing loki. Is your CWM pre loki and flashable after extraction? Thinking about flashing and doing the OTA dirty flash of 12B.
Steamer86 said:
@datechnerd I just saw that. Nice. I used the flashify method for CWM ( loki version) on 11A, loki errors. Never got around to pushing loki. Is your CWM pre loki and flashable after extraction? Thinking about flashing and doing the OTA dirty flash of 12B.
Click to expand...
Click to collapse
when i updated, i did temp unroot(ended up being permanent), plugged phone into pc and used lg tool to update. then used ioroot to root again
the cwm is lokied and i believe only works with 12b
datechnerd said:
when i updated, i did temp unroot(ended up being permanent), plugged phone into pc and used lg tool to update. then used ioroot to root again
the cwm is lokied and i believe only works with 12b
Click to expand...
Click to collapse
I had so much trouble trying to modd my phone after the update.. I pushed lg stock ROM on here and am leaving it that way lol.. Now I have cyan mod 11 on here and its working beautifully.. I'm leaving it on as my daily os

[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?

Rooting LG V20 and installing TWRP

Question for everyone,
So I have followed the steps to root my LG V20 before I installed TWRP, however I am stuck at the moment. Here is a copy of my log. It keeps coming up with an error saying no file or directory when I try to put this in " dd if=/sdcard/twrp-3.0.2-0-beta4-h918.img of=/dev/block/bootdevice/by-name/recovery.
Here is a copy of the log:
--------
Updating boot image hash
Writing modified boot image to block device '/dev/block/bootdevice/by-name/boot'...
Done!
------------
Permissive boot has been has been flashed to /dev/block/bootdevice/by-name/boot successfully!
You may use 'reboot' now to enter a permissive system.
***********************************************
* give jcadduono a hug, will ya? *
***********************************************
elsa:/data/local/tmp $ run-as su
Welcome to recowvery! (run-as)
------------
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
We have root access!
------------
Starting root shell
elsa:/data/local/tmp # dd if=/sdcard/twrp-3.0.2-0-beta4-h918.img of=/dev/block/bootdevice/by-name/recovery
dd: /sdcard/twrp-3.0.2-0-beta4-h918.img: No such file or directory
1|elsa:/data/local/tmp # dd if=/sdcard/twrp-3.0.2-1-h918.img of=/dev/block/bootdevice/by-name/recovery
dd: /sdcard/twrp-3.0.2-1-h918.img: No such file or directory
1|elsa:/data/local/tmp #
---------------------------------------------------------------------
Thanks

Categories

Resources