Database Info

ntrw read error while backing from SD card to PC

I am getting 0 bytes when I run the ntrw read oldrom_gr.nb1 g: command..
It quits after this
NTRW v2.00
Removeable media
Cylinders: 0:0
TracksPerCylinder: 1
SectorsPerTrack: 16
BytesPerSector: 512
bufsize is 65536
0 bytes written Res: 0 bytes: 0
ReadFile(): german1.nb1 -- The parameter is incorrect.
Is this a normal thing..I have read posts which asks one to wait for a while ...waited for 10 mins but the file still shows 0 bytes...
Also the ntrw process is not showing up on the running proceses list.
Can anyone please shed light on this?

There's something not quite right here. It should look something like this:
NTRW v2.00
Removeable media
Cylinders: 0:31
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
255850496 bytes written bytes: 00484
ReadFile(): junk.nb1 -- The parameter is incorrect.
The parameter is incorrect thing is ok but it should show how many bytes were written.
Depending on the size of the SD card you're using, it could take a while. The above was a 256MB card. When a flash backup is done to an SD card on the pocketpc, it will always fill the entire size of the card no matter what it is. When ntrw finishes, your command prompt should come back.

There's something not quite right here. It should look something like this:
NTRW v2.00
Removeable media
Cylinders: 0:31
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
255850496 bytes written bytes: 00484
ReadFile(): junk.nb1 -- The parameter is incorrect.
The parameter is incorrect thing is ok but it should show how many bytes were written.
Depending on the size of the SD card you're using, it could take a while. The above was a 256MB card. When a flash backup is done to an SD card on the pocketpc, it will always fill the entire size of the card no matter what it is. When ntrw finishes, your command prompt should come back.

something about the nand boot of my raph (htc6850)

I've dealed with android nand boot for a week,but there is still a problem bothered me so much.the first time after android installed my phone can launch android system normally,but when I reboot,things become bad,it warming that there is noting in my nand .Can you tell me what happened to it with your knowledge and experience!thank you very much^^

nandmtd2_WriteChunkWithTagsToNAND chunk 7177 data c5663000 tags d4061da8
<4>[ 96.371551] packed tags obj 114 chunk 10 byte 2048 seq 33
<4>[ 96.379058] ext.tags eccres -1072003072 blkbad -737796660 chused 7173 obj 114 chunk10 byte 2048 del 0 ser 2048 seq 33
this is messeage, I face the same problem

Basic question about flashing nandroid backups

I want to know that when we flash specific partition images (say system.img, data.img, cache.img, etc.), then how does the software know where exactly to put those partition bytes? For example, if I flash system.img, which CHS/LBA sector will it consider as beginning of that block? If it is based on the MBR/EBR1 tables, what will happen if I'm flashing the MBR/EBR1 too?
The reason I'm asking is that I want to change the partitioning in EBR1 slightly, so that more space is allocated to `/data` partition instead of `/sdcard`. I've got an old but good conditioned MediaTek (MTK-6577) based smart-phone called Karbonn-A30 which is great in build quality and almost every other aspect, but it only has 500MB of Internal Storage (`/data` partition in Linux lingo) which is not good enough for apps. Presently, the MBR and EBR1 partitions are thus:
$disktype MBR
--- MBR
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1024)
Type 0x05 (Extended)
Partition 2: 10 MiB (10485760 bytes, 20480 sectors from 18432)
Type 0x83 (Linux)
Partition 3: 10 MiB (10485760 bytes, 20480 sectors from 38912)
Type 0x83 (Linux)
Partition 4: 650 MiB (681574400 bytes, 1331200 sectors from 113152)
Type 0x83 (Linux)
$disktype EBR1
--- EBR1
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 1.293 GiB (1388314624 bytes, 2711552 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2196501691904 bytes, 4290042367 sectors from 4924928)
Type 0x83 (Linux)
Why this last partition which corresponds to `/sdcard` is left so large (1.998 TiB) is beyond my understanding! Since there is a good 2.5GB of space available on my actual `/sdcard` partition, I was thinking if I can alter the EBS1 and change the LBA addressing so that the third partition starts from 2097152 additional sectors (which comes to 1024MB or 1GB which is good enough for me), will it automatically increase my `/data` partition by 1GB and decrease the `/sdcard` by 1GB correspondingly? On XDA and other forums, I've read that people have successfully done this mod and achieved the change in partition sizes, but I first want to understand how it happens.

Question about flashing nandroid backups

I want to know that when we flash specific partition images (say system.img, data.img, cache.img, etc.), then how does the software know where exactly to put those partition bytes? For example, if I flash system.img, which CHS/LBA sector will it consider as beginning of that block? If it is based on the MBR/EBR1 tables, what will happen if I'm flashing the MBR/EBR1 too?
The reason I'm asking is that I want to change the partitioning in EBR1 slightly, so that more space is allocated to /data partition instead of /sdcard. I've got an old but good conditioned MediaTek (MTK-6577) based smart-phone called Karbonn-A30 which is great in build quality and almost every other aspect, but it only has 500MB of Internal Storage (/data partition in Linux lingo) which is not good enough for apps. Presently, the MBR and EBR1 partitions are thus:
$disktype MBR
--- MBR
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1024)
Type 0x05 (Extended)
Partition 2: 10 MiB (10485760 bytes, 20480 sectors from 18432)
Type 0x83 (Linux)
Partition 3: 10 MiB (10485760 bytes, 20480 sectors from 38912)
Type 0x83 (Linux)
Partition 4: 650 MiB (681574400 bytes, 1331200 sectors from 113152)
Type 0x83 (Linux)
$disktype EBR1
--- EBR1
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 1.293 GiB (1388314624 bytes, 2711552 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2196501691904 bytes, 4290042367 sectors from 4924928)
Type 0x83 (Linux)
Click to expand...
Click to collapse
Why this last partition which corresponds to /sdcard is left so large (1.998 TiB) is beyond my understanding! Since there is a good 2.5GB of space available on my actual /sdcard partition, I was thinking if I can alter the EBS1 and change the LBA addressing so that the third partition starts from 2097152 additional sectors (which comes to 1024MB or 1GB which is good enough for me), will it automatically increase my /data partition by 1GB and decrease the /sdcard by 1GB correspondingly? On XDA and other forums, I've read that people have successfully done this mod and achieved the change in partition sizes, but I first want to understand how it happens.

Recover corrupt SD card partitions

Hi,
After a botched attempt to install LineageOS 17 on my Samsung Galaxy S5, I decided to revert to LOS16. the problem is that I had completely wiped my device in order to install LOS 17, and my only available 16.x ROM was gone, so I found another ROM on a backup site (October 2020 version).
Once installed, this version did not recognize my SD card where I had stored all my user data. Therefore I dumped the partitions on my Linux PC using dd, and let Android reformat the card.
I dumped 2 individual partitions (not the whole device with the partition table), one of 16Mb, and the other about 29Gb (it's a 32Gb SD card).
Now I want to browse my old data on the backup, but I cannot mount or fsck the partition dumps. the superblock is not recognized as ext*, fat, or even f2fs.
This is all the info I have on the 2 partitions:
Bash:
$ sudo fdisk -l klte-sdc1.img
Disk klte-sdc1.img: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
$ sudo fdisk -l klte-sdc2.img
Disk klte-sdc2.img: 29.71 GiB, 31897140736 bytes, 62299103 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Also, for comparison, I dumped the partition table of the currently working SD card:
Bash:
$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Disk model: MicroSD/M2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 35D0FC04-06BD-4578-87FB-D6ED991C03A5
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 62333918 62299103 29.7G unknown
As you see, the partition sizes are identical. I can chance it and dd the original partitions into the new ones, but I don't want to lose recent data on the current partition. I could also corrupt the partition headers if the ones in the backups are corrupt, and be back to square 1.
Can anybody help? Which kind of partition or specialized tools shall I look for?
Thanks,
gm