• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root need halp with dd comands after copy files to lg g2

root@Microknoppix:/home/knoppix/Desktop# dd if=/dev/null of=/dev/sdd5
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.7821e-05 s, 0.0 kB/s
root@Microknoppix:/home/knoppix/Desktop# dd if=/dev/null of=/dev/sdd23
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.3581e-05 s, 0.0 kB/s
root@Microknoppix:/home/knoppix/Desktop# dd if=/dev/zero of=/dev/ssd23
dd: writing to `/dev/ssd23': No space left on device
31745+0 records in
31744+0 records out
16252928 bytes (16 MB) copied, 0.08904 s, 183 MB/s
root@Microknoppix:/home/knoppix/Desktop#
what i need to do please??????
 
bender_007 said:
Try sbl1 first, then aboot
And type correctly m8. Sdd is not same as ssd. Linux is also case sensitive and doesn't forgive
Click to expand...

thats what i get
root@Microknoppix:/home/knoppix/Desktop# dd if=/dev/null of=/dev/sdd2
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.1382e-05 s, 0.0 kB/s
 
You don't need to reformat partitions. You do need to be careful as you type though. There's a reason dd is nicknamed "data destroy". Please be mindful of each character you type...post #51 in this thread has an error which is being noted by previous posters.
 
iowabowtech said:
You don't need to reformat partitions. You do need to be careful as you type though. There's a reason dd is nicknamed "data destroy". Please be mindful of each character you type...post #51 in this thread has an error which is being noted by previous posters.
Click to expand...

what do i miss???? it stell written no space laft on device in aboot/boot/sbl1/laf

root@Microknoppix:/home/knoppix/Downloads# dd if=aboot.img of=/dev/sdd5
dd: writing to `/dev/sdd5': No space left on device
1025+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.0068872 s, 76.1 MB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=dbi.img of=/dev/sdd15
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.00624214 s, 84.0 MB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=boot.img of=/dev/sdd7
dd: writing to `/dev/sdd7': No space left on device
6145+0 records in
6144+0 records out
3145728 bytes (3.1 MB) copied, 0.0332832 s, 94.5 MB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=sbl1.img of=/dev/sdd2
dd: writing to `/dev/sdd2': No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000472261 s, 0.0 kB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=rpm.img of=/dev/sdd6
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.00496202 s, 106 MB/s
root@Microknoppix:/home/knoppix/Downloads# gdisk -l /dev/sdd
GPT fdisk (gdisk) version 0.8.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/sdd: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 36 entries
First usable sector is 11, last usable sector is 61071349
Partitions will be aligned on 2-sector boundaries
Total free space is 30552054 sectors (14.6 GiB)

Number Start (sector) End (sector) Size Code Name
1 32768 163839 64.0 MiB 0700 modem
2 163840 165887 1024.0 KiB FFFF sbl1
3 165888 166911 512.0 KiB FFFF dbi
4 196608 197631 512.0 KiB FFFF DDR
5 229376 231423 1024.0 KiB FFFF aboot
6 231424 233471 1024.0 KiB FFFF rpm
7 262144 294911 16.0 MiB FFFF boot
8 294912 296959 1024.0 KiB FFFF tz
9 296960 296961 1024 bytes 0700 pad
10 327680 333823 3.0 MiB FFFF modemst1
11 333824 339967 3.0 MiB FFFF modemst2
12 339968 339969 1024 bytes FFFF pad1
13 360448 393215 16.0 MiB FFFF misc
14 393216 458751 32.0 MiB 0700 persist
15 458752 491519 16.0 MiB FFFF recovery
16 491520 497663 3.0 MiB FFFF fsg
17 524288 525311 512.0 KiB FFFF fsc
18 525312 526335 512.0 KiB FFFF ssd
19 526336 526337 1024 bytes FFFF pad2
20 526338 527361 512.0 KiB FFFF encrypt
21 557056 573439 8.0 MiB 0700 drm
22 573440 589823 8.0 MiB 0700 sns
23 589824 655359 32.0 MiB FFFF laf
24 655360 720895 32.0 MiB FFFF fota
25 720896 786431 32.0 MiB 0700 mpt
26 786432 787455 512.0 KiB FFFF dbibak
27 787456 789503 1024.0 KiB FFFF rpmbak
28 789504 791551 1024.0 KiB FFFF tzbak
29 791552 791567 8.0 KiB FFFF rct
30 819200 6488063 2.7 GiB 0700 system
31 6488064 7733247 608.0 MiB 0700 cache
32 7733248 7897087 80.0 MiB 0700 tombstones
33 7897088 7929855 16.0 MiB 0700 spare
34 7929856 8028159 48.0 MiB 0700 cust
35 8028160 30703615 10.8 GiB 0700 userdata
36 30703616 30777310 36.0 MiB 0700 grow
root@Microknoppix:/home/knoppix/Downloads# dd if=laf.img of=/dev/sdd23
dd: writing to `/dev/sdd23': No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00016824 s, 0.0 kB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=tz.img of=/dev/sdd8
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.138197 s, 3.8 MB/s
root@Microknoppix:/home/knoppix/Downloads# ^C
root@Microknoppix:/home/knoppix/Downloads# dd if=tz.img of=/dev/sdd8
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.144175 s, 3.6 MB/s
root@Microknoppix:/home/knoppix/Downloads# dd if=laf.img of=/dev/sdd23
dd: writing to `/dev/sdd23': No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000157593 s, 0.0 kB/s
 
What firmware was on this phone prior to all the problems. I'm not asking about a rom, but rather the firmware...kitkat or lollipop. Partition sizes changed on lollipop and appear to be the source of your gpt errors.
 
bender_007 said:
It has space. Earlymon noticed your typos. You typed ssd instead of sdd. Just flash the 10files as iowabowtech stated
Click to expand...
Yeah, that and I must either be dense or the G2 attaches to a Linux pc in ways I've never seen.

None of the above commands are happening on the phone via an adb shell.

The only evidence of a Mini-SDK install is for Windows, not Linux.

When you guys are done helping this guy, I'd like to know how dd'ing boot images to a local /dev works ok. :)

Unless that's the mounted storage partition on the phone... in which case I'd expect the storage partition to be obliterated.
 
Last edited:
iowabowtech said:
What firmware was on this phone prior to all the problems. I'm not asking about a rom, but rather the firmware...kitkat or lollipop. Partition sizes changed on lollipop and appear to be the source of your gpt errors.
Click to expand...
i dont know.
i bought the phone like this.
no os....
so i cant flash lolipop 7 files?
 
Hm /dev/sdd is his phone actually. He could also mount to other "directories".
-there is also another way, using partition manager. Search somboons tutorial on xda. Refurbished phones are so shitty for anything twrp related
 
bender_007 said:
Hm /dev/sdd is his phone actually. He could also mount to other "directories".
-there is also another way, using partition manager. Search somboons tutorial on xda. Refurbished phones are so shitty for anything twrp related
Click to expand...
can u please explain me what did u ment i didnt understand.?
there is any way of flashing any rom to this device i dont care wich rom
but i want a working phone and not some experimental projact
 
EarlyMon said:
Yeah, that and I must either be dense or the G2 attaches to a Linux pc in ways I've never seen.

None of the above commands are happening on the phone via an adb shell.

The only evidence of a Mini-SDK install is for Windows, not Linux.

When you guys are done helping this guy, I'd like to know how dd'ing boot images to a local /dev works ok. :)

Unless that's the mounted storage partition on the phone... in which case I'd expect the storage partition to be obliterated.
Click to expand...

The g2, g3 and likely other LG's with Qualcomms are blessed with a "bulk" mode which only presents itself in the event of a fully broken boot chain...boot fail, recovery fail, download mode fail, fastboot mode (1st bailout) fail, qhsusb_bulk mode (9006) = positive in most cases. In this state, the phone's partitions show up as "drives" to windows and write is possible. He's writing the partitions from Knoppix Linux currently.
 
tsharon81 said:
tell me something please i cant install cm rom without all the partition i dont care about kit kat or lolipop stock fw
im still cant dd del the 4 partition that says no space
Click to expand...

aboot is the one that's most troubling as it should be sized identically on both KK and LP. There should be no space error there.

kitkat: aboot = 1024kb, boot = 10.5 mb, laf = 15.5 mb, sbl1 = 512 kb
lollipop: aboot = 1024kb, boot = 16 mb, laf = 32 mb, sbl1 = 1024 kb

So regardless of which partitions were used here, aboot should not receive the no space error as you're writing a 1024 kb partition to a 1024 kb space. Currently, the partitions are showing sizes indicative of lollipop, but I'm beginning to believe LP partitions were flashed to a GPT designated for KK partition table/sizing.
 
You must log in or register to reply here.
Back
Top Bottom