Develop Bugs

[Q] how to install a boot.img file

Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?

mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?

Broken internal SD card

The partitioning of my internal SD card seems to be horribly broken, I haven't been able to find any solution that works.
When I run fdisk, and press p, this is what is shown:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 4097 32768 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 4097 4225 1024 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 4225 4353 1024 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4353 88064 669695+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 5121 5248 1024 47 Unknown
/dev/block/mmcblk0p6 6145 6784 5120 45 Unknown
/dev/block/mmcblk0p7 7169 7808 5120 4c Unknown
/dev/block/mmcblk0p8 8193 9472 10240 48 Unknown
/dev/block/mmcblk0p9 10241 10368 1024 46 Unknown
/dev/block/mmcblk0p10 11265 11648 3072 4a Unknown
/dev/block/mmcblk0p11 12289 12672 3072 4b Unknown
/dev/block/mmcblk0p12 13313 14336 8192 83 Linux
/dev/block/mmcblk0p13 14337 16384 16384 60 Unknown
/dev/block/mmcblk0p14 16385 20480 32768 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p15 20481 20864 3072 59 Unknown
/dev/block/mmcblk0p16 21505 21888 3072 5a Unknown
/dev/block/mmcblk0p17 22529 22912 3072 5b Unknown
/dev/block/mmcblk0p18 23553 23936 3072 58 Unknown
/dev/block/mmcblk0p19 24577 24704 1024 5d Unknown
/dev/block/mmcblk0p20 25601 26624 8192 83 Linux
/dev/block/mmcblk0p21 26625 28672 16384 83 Linux
/dev/block/mmcblk0p22 28673 37888 73728 83 Linux
/dev/block/mmcblk0p23 37889 38912 8192 83 Linux
/dev/block/mmcblk0p24 38913 41984 24576 76 Unknown
/dev/block/mmcblk0p25 41985 43008 8192 77 Unknown
/dev/block/mmcblk0p26 43009 43136 1024 78 Unknown
/dev/block/mmcblk0p27 44033 109568 524288 83 Linux
/dev/block/mmcblk0p28 109569 150528 327680 83 Linux
/dev/block/mmcblk0p29 150529 150912 3072 83 Linux
/dev/block/mmcblk0p30 151553 438272 2293760 83 Linux
/dev/block/mmcblk0p31 438273 440320 16384 83 Linux
/dev/block/mmcblk0p32 440321 440576 2048 83 Linux
when I try parted /dev/block/mmcblk10 and type print I get
Code:
Error: Unable to satisfy all constraints on the partition.
Any ideas, preferably a solution that doesn't cost money?

Wow.....if you were trying to format the 16 gb card that came with the phone first you need to Google SDFORMAT, it's a free download. Then pull the memory card it of your phone, put it in a micro sd to sd adapter, insert into a laptop and use the utility that you downloaded. However, those look like android partitions and under no circumstances are you to use Windows fdisk. Unless you want to brick your phone, hopefully you haven't already. If you have a custom recovery use the built in utility to handle the internal memory. Good luck.
Sent from my LG-D800 using XDA Free mobile app

How extract the Pit file ?

Can anybody confirm that the follow strings working on the T805?
Use Terminal Emulator and enter follow:
su (Enter)
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176 (Enter)
Click to expand...
Click to collapse
This Code is from the Galaxy S5 but i think that the mmcblk0 is the same or i wrong?
Here are the partition from the S10.5 and S8.4 Tab
Code:
Größe Device Name Kommentar Mountpoint
15388672 mmcblk0
4096 mmcblk0p1 BOTA0
4096 mmcblk0p2 BOTA1
20480 mmcblk0p3 EFS EFS Filesystem /efs
4096 mmcblk0p4 m9kefs1 EFS Filesystem
4096 mmcblk0p5 m9kefs2 EFS Filesystem
4096 mmcblk0p6 m9kefs3 EFS Filesystem
4096 mmcblk0p7 CARRIER Modemfirmware
8192 mmcblk0p8 PARAM Param
8192 mmcblk0p9 BOOT Kernel
10240 mmcblk0p10 RECOVERY Recovery
10240 mmcblk0p11 OTA FOTA Partition
4096 mmcblk0p12 CDMA-RADIO Modemfirmware
49152 mmcblk0p13 RADIO Modemfirmware
4096 mmcblk0p14 TOMBSTONES
4096 mmcblk0p15 TDATA
12288 mmcblk0p16 PERSDATA /persdata/absolute
4096 mmcblk0p17 RESERVED2
2447360 mmcblk0p18 SYSTEM System Partition /system
204800 mmcblk0p19 CACHE Cache /cache
235520 mmcblk0p20 HIDDEN Hidden Partition
12333056 mmcblk0p21 USERDATA Userdaten /data
4096 mmcblk0rpmb
4096 mmcblk0boot1
4096 mmcblk0boot0

Chrack said:
Can anybody confirm that the follow strings working on the T805?
Click to expand...
Click to collapse
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668

gggg said:
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668
Click to expand...
Click to collapse
Efs professional

ashyx said:
Efs professional
Click to expand...
Click to collapse
It cannot read PIT on A5 this is why I want to dd, but I need the right params ... please reply here:
http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668

[Q] d855 unbricking help :)

OK, I am no noob at rooting, but have drawn a blank with this one. Would very much appreciate some advice.
I have 2 x LG G3 D855s, both running Cloudy G3 ROM. Both have been successfully downgraded to Android 4.4.2 (10L), rooted with purple drake, and Cloudy Lollipop installed. Perfect.
BUT whilst doing a Titanium restore on an app, one of them rebooted this evening, and is now bricked.
- Normal boot - never does anything other than initial LG boot logo;
- TWRP takes about 5 minutes on the splash screen before reaching the main TWRP screen (but has errors, see later);
- LG download mode only shows the initial logo on the phone but the PC does not 'see' it upon cable connection, and the phone never kicks into full download mode. Connecting my other d855 fires up download mode correctly, so PC drivers are OK.
Because download mode never fully starts, I am unable to restore to stock using the kdz / LG flash.
When TWRP DOES start, it is unable to mount /data, /cache, and the log has the following errors:
E: Could not mount /data and unable to find crypto folder
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount /cache
E: Unable to mount storage
... etc.
Within TWRP Internal Storage is shown as (0MB), and /data and /cache are not mounted. My external_sd is mounted OK.
With TWRP running, a device is seen by my PC (Google Nexus ADB Interface) but 'adb devices' shows nothing. This is the same behaviour as the phone that works, so I assume that at least is normal.
I am unable to mount /data manually, or repair within TWRP.
With /data not mounted, I am unable to proceed any further...
So my question - how do I rebuild the screwed up partitions? Or am I barking up the wrong tree?

Some more troubleshooting.
Trying to mount manually in terminal in TWRP gives me a mount unknown error 150.
Running a non-invasive e2fsck gives me:
Code:
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inode 7, i_size is 3082895360, should be 3087097856. Fix? no
Inode 245415, i_blocks is 704, should be 712. Fix? no
Deleted inode 261925 has zero dtime. Fix? no
Pass 2: Checking directory structure
Entry 'net.dinglisch.android.taskerm' in /data (244801) references inode 342934 found in group 42's unused inodes area.
Fix? no
Entry 'net.dinglisch.android.taskerm' in /data (244801) has deleted/unused inode 342934. Clear? no
Entry 'base.apk' in /app/net.dinglisch.android.taskerm-1 (342899) references inode 342932 found in group 42's unused inodes area.
Fix? no
Entry 'base.apk' in /app/net.dinglisch.android.taskerm-1 (342899) has deleted/unused inode 342932. Clear? no
Entry 'lib' in /app/net.dinglisch.android.taskerm-1 (342899) references inode 342933 found in group 42's unused inodes area.
Fix? no
Entry 'lib' in /app/net.dinglisch.android.taskerm-1 (342899) has deleted/unused inode 342933. Clear? no
Entry 'net.dinglisch.android.taskerm' in /dalvik-cache/profiles (1020002) references inode 1020523 found in group 125's unused inodes area.
Fix? no
Entry 'net.dinglisch.android.taskerm' in /dalvik-cache/profiles (1020002) has deleted/unused inode 1020523. Clear? no
Entry '[email protected]@[email protected]@classes.dex' in /dalvik-cache/arm (1020003) references inode 1020522 found in group 125's unused inodes area.
Fix? no
Entry '[email protected]@[email protected]@classes.dex' in /dalvik-cache/arm (1020003) has deleted/unused inode 1020522. Clear? no
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 244801 ref count is 227, should be 226. Fix? no
Inode 342899 ref count is 3, should be 2. Fix? no
Pass 5: Checking group summary information
Block bitmap differences: -(1389467--1390267) -3348514
Fix? no
Free blocks count wrong for group #25 (293, counted=292).
Fix? no
Free blocks count wrong for group #37 (4806, counted=4853).
Fix? no
Free blocks count wrong for group #42 (20629, counted=19028).
Fix? no
Free blocks count wrong (5806109, counted=5471235).
Fix? no
Inode bitmap differences: -261925 -(342932--342935) -(1020522--1020523)
Fix? no
Free inodes count wrong for group #32 (7338, counted=7337).
Fix? no
Free inodes count wrong for group #42 (7950, counted=7945).
Fix? no
Directories count wrong for group #42 (57, counted=58).
Fix? no
Free inodes count wrong for group #125 (7639, counted=7637).
Fix? no
Free inodes count wrong (1692439, counted=1689847).
Fix? no
/dev/block/mmcblk0p43: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p43: 4841/1697280 files (8.7% non-contiguous), 988001/6794110 blocks
Parted gives me this:
Code:
Model: MMC SDW32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 85.5MB 86.0MB 524kB DDR
5 86.0MB 88.1MB 2097kB aboot
6 88.1MB 89.1MB 1049kB rpm
7 89.1MB 90.2MB 1049kB tz
8 90.2MB 90.2MB 4096B pad
9 90.2MB 91.2MB 1049kB sbl1b
10 91.2MB 91.8MB 524kB dbibak
11 91.8MB 92.8MB 1049kB rpmbak
12 92.8MB 93.9MB 1049kB tzbak
13 93.9MB 94.9MB 1049kB rpmf
14 94.9MB 95.9MB 1049kB tzf
15 95.9MB 96.5MB 524kB sdif
16 96.5MB 98.6MB 2097kB abootf
17 98.6MB 101MB 2093kB spare1
18 101MB 117MB 16.8MB boot
19 117MB 151MB 33.6MB ext4 persist
20 151MB 168MB 16.8MB recovery
21 168MB 171MB 3146kB modemst1
22 171MB 174MB 3146kB modemst2
23 174MB 174MB 4096B pad1
24 174MB 177MB 3146kB fsg
25 177MB 178MB 524kB fsc
26 178MB 178MB 524kB ssd
27 178MB 178MB 4096B pad2
28 178MB 179MB 524kB encrypt
29 179MB 179MB 524kB eksst
30 179MB 179MB 8192B rct
31 179MB 185MB 5226kB spare2
32 185MB 201MB 16.8MB misc
33 201MB 235MB 33.6MB laf
34 235MB 268MB 33.6MB fota
35 268MB 285MB 16.8MB spare3
36 285MB 294MB 8389kB ext4 drm
37 294MB 302MB 8389kB ext4 sns
38 302MB 336MB 33.6MB ext4 mpt
39 336MB 369MB 33.6MB factory
40 369MB 2533MB 2164MB ext4 system
41 2533MB 3171MB 638MB ext4 cache
42 3171MB 3439MB 268MB ext4 cust
43 3439MB 31.3GB 27.8GB ext4 userdata
44 31.3GB 31.3GB 513kB grow

Whenever I try and write, repair, or delete the partitions parted tells me:
Code:
Error: Input/output error during write on /dev/block/mmcblk0
I can read partitions. I have backed up EFS and /boot. For what it's worth
I can't delete partitions:
Code:
/ # dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512B) copied, 0.247840 seconds, 2.0KB/s
/ # parted /dev/block/mmcblk0 print
Model: MMC SDW32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 85.5MB 86.0MB 524kB DDR
5 86.0MB 88.1MB 2097kB aboot
6 88.1MB 89.1MB 1049kB rpm
7 89.1MB 90.2MB 1049kB tz
8 90.2MB 90.2MB 4096B pad
...
etc...
So it looks like the whole filesystem has gone read only??? Any way to force reset it? I'd have thought dd would have worked.

mmcblk 14 missing (data)

Hello,
Today i tried to put a custom rom on my Sony Xperia Acro S. After a lot of problems with the flashing(windows 10 blocks everything) i got it rooted and in fastboot.
After that i repartioned it, if followed this guide: https://forum.xda-developers.com/xperia-s/acro-s-development/guide-naosp-6-0-flashing-guide-ultimate-t3334055
I did everything it said and at the end I didn't got an error while the thread said it had to, so i waited a while and then rebooted it.
I don't know if the problem came from that but after that i couldn't format or change filesystems. The phone constantly says: Erimary block device '/dev/block/mmcblk0p14' for mount point '/data' is not present!
After that a few more lines follow with unable to mount and error change and so on. So basically it says that mmcblk0p14 is missing. After that i did some research in adb and i found out that the partitions look completely different from the start situation. After that i tried to just install the rom, this worked until at the end i got an error and with the reboot after that the phone got stuck in a bootloop, after removing the sd it worked normal again. My question now is, how can i recover the storage or place mmcblk0p14 back or can i just go back to my normal android or is this gone now?
Start
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
4 heads, 16 sectors/track, 477120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 477120 15243264 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 477120 11796480 c Win95 FAT32 (LBA)
~ #
Click to expand...
Click to collapse
End
~ # fdisk -l /dev/block/mmcblk0
Omitting empty partition (14)
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
4 heads, 16 sectors/track, 477120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 477120 15243264 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
~ #
Click to expand...
Click to collapse

Re open adb shell just like you did for partitioning then: (aafter every command press enter)
fdisk /dev/block/mmcblk0
n
42945
108480
t
14
83
write w
after this write: fdisk -l /dev/block/mmcblk0
the output at part 14 should be like this:
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux if yes ok, REBOOT, IF NOT OK:
reboot the phone, go to twrp again and restart adb shell, retype the command fdisk -l /dev/block/mmcblk0 and see if there is a 14 partition then,
again
n
108481
477120
t
15
NOW, I'M NOT SURE, when it asks for hex code type L and search for win32/fat32 code and write it.
and write w
after every w you should see smt like the partition table has been altered.
Restart the phone, and in twrp format data you should be ok, NOT FOR FLASHING NAOSP, IF YOU WANT TO FLASH NAOSP:
fdisk /dev/block/mmcblk0
n
42945
477120
t
14
83
write w

Thank you for your reply. I tried it but after i typed 42945 it asks for another letter while you instruct that i have to use 108480, it doesn't accept this number.
But anyway i gave up on repartitioning. I found out how to go back to stock android and i maybe will try later again but i need to be reachable right now.
Anyway thanks for your reply