Quote:
these are my backup partitions.ROW tablet stock ICS.
Partitions from 02 to 10
partitions from 11 to 16
the files will be available for 8 days, after that they are deleted.
Thank you
I hope to works...
Dear Mihnea
If you still have the partitions from Berbecverde, please send it again .
Thank you
Hi All,
After having bricked my tablet recently with the "booting recovery kernel image" boot loop error and subsequently surfing these threads to figure out how to fix it, I realized a much more streamlined solution was necessary.
My roommate compiled all the files from the various threads (APX drivers, recover images, etc.) and compiled them in to one executable script.
If anyone is interested, I can start a new thread and upload a script.
My Thinkpad lives again. No more flashing or modding for me!
Hi All,
After having bricked my tablet recently with the "booting recovery kernel image" boot loop error and subsequently surfing these threads to figure out how to fix it, I realized a much more streamlined solution was necessary.
My roommate compiled all the files from the various threads (APX drivers, recover images, etc.) and compiled them in to one executable script.
If anyone is interested, I can start a new thread and upload a script.
My Thinkpad lives again. No more flashing or modding for me!
Hi All,
After having bricked my tablet recently with the "booting recovery kernel image" boot loop error and subsequently surfing these threads to figure out how to fix it, I realized a much more streamlined solution was necessary.
My roommate compiled all the files from the various threads (APX drivers, recover images, etc.) and compiled them in to one executable script.
If anyone is interested, I can start a new thread and upload a script.
My Thinkpad lives again. No more flashing or modding for me!
Mine is still bricked. I will very appreciate it if you can provide the scripts.:good:
I am very interested in the offer - I have a bricked thinkpad - you are my last hope.
Thanks in advance.
I would also be greatful, if you would do such a thing. Mine is a nice cup holder since it got bricked. Keep us posted if u create a new thread.
Thank you in advance
Send me a PM please and I will send you the file directly!
---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------
If you send me a personal message I can supply the file directly; may not be worth creating a new thread here seeing as Thinkpad dialogue is pretty much a ghost town by this point
Hi All,
After having bricked my tablet recently with the "booting recovery kernel image" boot loop error and subsequently surfing these threads to figure out how to fix it, I realized a much more streamlined solution was necessary.
My roommate compiled all the files from the various threads (APX drivers, recover images, etc.) and compiled them in to one executable script.
If anyone is interested, I can start a new thread and upload a script.
My Thinkpad lives again. No more flashing or modding for me!
Please I have TPT bricked but NVflash is still working. I will very appreciate if you can to help me with this issue.
Thanks in Advance.
Hi guys,
there's an option "getpartitiontable" in nvflash to download the partition table from the tablet.
To me it looks like the partition table is crap.
If it is crap, you can't write an image to a partition, because there is no partition
So maybe you have to create a new partition table.
Both of you: Pls try the following and look, if the file "partitiontable.txt" is created. Then post it here, so you can compare it.
nvflash --getpartitiontable partitiontable.txt --bl 04.EBT.img --go
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
root@jandsBox:~/tpt# ./nvflash -w --bl ./04.EBT.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0a80518544805557
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 1
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: ./04.EBT.img
/ 6291456/6291456 bytes sent
./04.EBT.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
root@jandsBox:~/tpt# ./nvflash -r --read 4 04.EBT.img.orig
Nvflash started
[resume mode]
receiving file: 04.EBT.img.orig, expected size: 6291456 bytes
/ 6291456/6291456 bytes received
file received successfully
root@jandsBox:~/tpt# ./nvflash -r --read 2 02.BCT.img.orig
Nvflash started
[resume mode]
receiving file: 02.BCT.img.orig, expected size: 4194304 bytes
/ 4194304/4194304 bytes received
file received successfully
root@jandsBox:~/tpt# ./nvflash -r --read 3 03.PT.img.orig
Nvflash started
[resume mode]
receiving file: 03.PT.img.orig, expected size: 2097152 bytes
/ 2097152/2097152 bytes received
file received successfully
root@jandsBox:~/tpt# ./nvflash -r --read 7 07.Kernel.img.orig
Nvflash started
[resume mode]
receiving file: 07.Kernel.img.orig, expected size: 8388608 bytes
/ 8388608/8388608 bytes received
file received successfully
root@jandsBox:~/tpt# ./nvflash -r --read 8 08.App.img.orig
Nvflash started
[resume mode]
receiving file: 08.App.img.orig, expected size: 805306368 bytes
/ 805306368/805306368 bytes received
file received successfully
root@jandsBox:~/tpt# ./nvflash -r --download 6 ./recovery.img
Nvflash started
[resume mode]
sending file: ./recovery.img
/ 5462016/5462016 bytes sent
./recovery.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
root@jandsBox:~/tpt#
Hi.
you do not need a firmware.
all you need is the right partition backup, nvflash, and a computer.
1.You have to enter nvflash mode(described in the nvflash thread)
2.If you want to flash a partition you have to use the download command.
It is a slow process because you have to flash the partitions one at a time(maybe you can flash them all at once but you need some batch file, and i did not find one for the TPT, and i con not create one).
so like this:
Writing an image to device partition:
The recovery partition:
$ nvflash -r --download 6 recovery.img
this flashes the recovery to the recovery partition (number 6).
The Kernel Partition:
$ nvflash -r --download 7 kernel.img
this flashes the kernel to the kernel partition (number 7).
and the same goes for the rest of the partitions.
note that the name of the image may differ:
my backup for the recovery image for example is named 6.sos.img
the command in this case will be:
$ nvflash -r --download 6 06.sos.img
these are the TPT partitions:
2. BCT StartSector=0 NumSectors=1024 Boot Configuration Table
3. PT StartSector=1024 NumSectors=512 Partition Table
4. EBT StartSector=1536 NumSectors=1536 Bootloader Table
5. GP1 StartSector=3072 NumSectors=512 ?
6. SOS StartSector=3584 NumSectors=1536 Recovery
7. LNX StartSector=5120 NumSectors=2048 Kernel
8. APP StartSector=7168 NumSectors=196608 Applications in System/ROM
9. CAC StartSector=203776 NumSectors=230400 CAChe
10. MSC StartSector=434176 NumSectors=512 ?
11. PIA StartSector=434688 NumSectors=131072 Pre-Install APK
12. SEC StartSector=565760 NumSectors=5120 ?
13. USP StartSector=570880 NumSectors=35840 ?
14. PDA StartSector=606720 NumSectors=5120 ?
15. UDA StartSector=611840 NumSectors=3234816 User Data (/sdcard)
16. GPT StartSector=3846656 NumSectors=512 ?
You should try to flash my recovery image then restore a CWM backup.