Related
I had to do a lot of hunting around to do this so thought I would write it all down.
Before you do this I would recommend reading these threads so you have an idea of what you are about to do:
http://forum.xda-developers.com/showthread.php?t=1136261
http://forum.xda-developers.com/showthread.php?t=1196747
You will need sbf_flash (attached to thread), fastboot-mac (attached to thread), the SBF file (attached to thread) and adb from the android SDK. Easiest thing is to download the Android SDK and copy sbf_flash.sh, fastboot-mac and the sbf file to platform-tools in the Android SDK.
1. Root your device with Gingerbreak.apk (v1.20) available here:
http://forum.xda-developers.com/showthread.php?t=1044765
2. Backup with Titanium backup (BATCH -> backup apps & system data)
3. Power down your device
4. Power it back up holding the volume up button
5. Connect your device to your Mac
6. Open a Terminal and 'cd' to where all your tools are ie type 'cd PATH TO platform-tools'. You'll need to change the permissions on 'sbf_flash.sh' and 'fastboot-mac' so type these in the terminal:
chmod +x sbf_flash.sh
then
chmod +x fastboot-mac
7. Run this 'sudo ./sbf_flash.sh intl-fix-try1.sbf' and you should get something like this:
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== intl-fix-try1.sbf ===
Index[5]: Unexpected chip 16
Index[6]: Unexpected chip 16
00: RDL03 0x00000000-0x002FFFFF 7F75 AP
01: RDL01 0x00800000-0x008407FF 3556 BP
02: CG02 0x00000010-0x0000580F 4615 AP
03: CG03 0x000000A0-0x0008009F 2135 AP
04: CG42 0x00000020-0x0030001F F03C AP
05: CG44 0x00000050-0x0030004F 0C66 AP
06: CG47 0x00000070-0x0008006F E7CB AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG02: 100.0%
-- OK
>> uploading CG03: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG44: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> rebooting
8. Let the device reboot
9. Power the device back off
10. Power it up with the volume down button, then press up
11. In your terminal run this './fastboot-mac -i 0x22b8 oem unlock'
... INFOUnlocking your device can permanently VOID your warranty.
INFOThis process cannot be reversed. If you wish to proceed,
INFOreissue the unlock OEM command containing the unique ID
INFOof your device: XXXXXXXX
OKAY
12. Enter it again with your device ID ie './fastboot-mac -i 0x22b8 oem unlock XXXXXXXXX' and this should happen:
... INFODevice is now unlocked
OKAY
13. Enter this in Terminal './fastboot-mac -i 0x22b8 reboot'
14. Success you've unlocked your bootloader!
15. Install Titanium Backup and restore your applications 'BATCH -> restore missing apps and all system data)
HOW TO FLASH GINGERBREAD ON OS X
Download moto-fastboot mac from here:
http://forum.xda-developers.com/showthread.php?t=1138092
Download Gingerbread and RAM fix from here (intsructions there for which Tegra version you need):
http://forum.xda-developers.com/showthread.php?t=1169409
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
Hurray you have Gingerbread!
INCREDIBLY USEFUL LINKS
FIX FINGERPRINT READER BROKEN AFTER TITANIUM BACKUP RESTORE
http://forum.xda-developers.com/showpost.php?p=12567301&postcount=8
SQLITE3 SO YOU CAN ACTUALLY DO THE FINGERPRINT FIX (COPY IT TO SYSTEM/BIN AND CHANGE PERMISSIONS TO 777 WITH ROOT EXPLORER)
http://forum.xda-developers.com/showpost.php?p=9848889&postcount=1
ROMRACERS RECOVERY
http://forum.xda-developers.com/showthread.php?t=1204500
Flash like this:
1. Put phone in fastboot mode
2. Open a terminal and cd to where fastboot-mac-osx64 is
3. Erase your recovery
./moto-fastboot-osx64 erase recovery
4. Flash romracers recovery
./moto-fastboot-osx64 flash recovery /PATH/TO/recovery-atrix4.1.img
5. Reboot
./moto-fastboot-osx64 reboot
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
I come to me a tablet lenovothink type 1838-22g wich rebooting...logo (lenovo) reboot ..lenovo reboot...
I use nvflash
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x043c704444012157
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: 0
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
After this I created partion OK this is tutorial : http://forum.xda-developers.com/showthread.php?t=1745450
And my tabletet respond OK
I write partion 6 with cwm OK (see in pictures)
The tablet now starts and remains stuck in logo LENOVO (not rebooting - this is a step : ) )
If I go into CWM says: cant mount sdcard (see in pictures)
What are these commands to solve this problem?
I saw (nvflash for asus transformes) as it would be a commands to reflash tablet.
Does anyone have these commands (nvflash) tailored for Lenovo tablet thingpad?
I took several firmwares on the net but do not know if they are correct for this model , and I would not want to spoil it worse than it is now.
Best regardes
Mihnea
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.
berbecverde said:
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.
Click to expand...
Click to collapse
Thanx for answer...
but from whare I cand download the good firmware because i see ...A300 , A310, A400 - sorry but i secod tablet lenovo and Iam not familiarized with this.?
a link pls.
Ai have recovery from tablet before to put cwm. I read with nvflash.
many thx
Mihnea
you can not flash a firmware using nvflash.
You can use it to backup your partitions, or restore your partitions from your backup.
that is about it.
so in order to make your tablet work again you have to restore your partitions from your backup(if you have one).
If you do not then you can use my backup.
I will upload my partitions later today when i got some time.
In your case i think that one of your partitions got corrupted.
You can fix that by flashing the rigth backup to the right partition.
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.
berbecverde said:
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.
Click to expand...
Click to collapse
Thank you
I hope to works...
BR
Mihnea
mihnea_gsm said:
Thank you
I hope to works...
BR
Mihnea
Click to expand...
Click to collapse
only if you do it right.:good:
berbecverde said:
only if you do it right.:good:
Click to expand...
Click to collapse
tehnical problem...
c:\nvflash>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: 0x043c704444012157
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: 0
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
in this moment tablet is in nvflash recovery mode / Nv3p Server
In archive I found 16 img... and I want to write first: 2.bct.img after this 3.pt.img... etc
c:\nvflash>nvflash -r --download 2 2.bct.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
c:\nvflash>nvflash -r --download 2 2.bct.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
c:\nvflash>nvflash -r --download 3 3.pt.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
what is wrong ???
I dont know if comands is ok.... because in tutorial said that first comand is:
nvflash -w --bl /space/android/_tpt/device/04.EBT.img --go - but to me not work
At me work this: nvflash -w --bl 04.EBT.img --go see in log up.
BR
mihnea
mihnea_gsm said:
tehnical problem...
c:\nvflash>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: 0x043c704444012157
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: 0
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
in this moment tablet is in nvflash recovery mode / Nv3p Server
In archive I found 16 img... and I want to write first: 2.bct.img after this 3.pt.img... etc
c:\nvflash>nvflash -r --download 2 2.bct.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
c:\nvflash>nvflash -r --download 2 2.bct.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
c:\nvflash>nvflash -r --download 3 3.pt.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
what is wrong ???
I dont know if comands is ok.... because in tutorial said that first comand is:
nvflash -w --bl /space/android/_tpt/device/04.EBT.img --go - but to me not work
At me work this: nvflash -w --bl 04.EBT.img --go see in log up.
BR
mihnea
Click to expand...
Click to collapse
In the tutorial the nvflash file and 04.ebt.img were not in the same folder so they had to specify the path were the img file was.
If they are in the same folder lie you case you do not have to specify the path.
The command seems fine.The bootloader it is unlocked as far as i can tell.
You should try to see if you can flash partitions 6 or 7.
nvflash and the partitions are in the same folder right?
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
Ameisentaetowierer said:
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
Click to expand...
Click to collapse
The partitions are ok cause i made them.
The only thing that might be a problem if not all the TPT have the same partitions.
These partitions are from a ROW TPT.
I'm not talking about your images!
Again: you can not write to a partition, if the partition table (on the target system) is corrupt
And even if the partition sizes of your devices may differ, you could verify this by comparing your partition tables.
nvflash itself doesn't know about position and size of partitions - it has to query the device for this
http://en.m.wikipedia.org/wiki/Partition_table
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Well, clearly i am no expert on this matter
So you should try to help him if you can.
If i understand correctly the partition table holds the information on where the partitions are located and The size of each partition.
If this information is corrupted then nvflash, does not know where to Write The image file.
If this is correct then how do you restore the partition table?
Sent from my HTC EVO 3D X515m using xda premium
Ameisentaetowierer said:
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
Click to expand...
Click to collapse
thx for answers
this is in ptable.txt :
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1024
BytesPerSector=4096
PartitionId=3
Name=PT
DeviceId=18
StartSector=1024
NumSectors=512
BytesPerSector=4096
PartitionId=4
Name=EBT
DeviceId=18
StartSector=1536
NumSectors=1536
BytesPerSector=4096
PartitionId=5
Name=GP1
DeviceId=18
StartSector=3072
NumSectors=512
BytesPerSector=4096
PartitionId=6
Name=SOS
DeviceId=18
StartSector=3584
NumSectors=1536
BytesPerSector=4096
PartitionId=7
Name=LNX
DeviceId=18
StartSector=5120
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=APP
DeviceId=18
StartSector=7168
NumSectors=196608
BytesPerSector=4096
PartitionId=9
Name=CAC
DeviceId=18
StartSector=203776
NumSectors=230400
BytesPerSector=4096
PartitionId=10
Name=MSC
DeviceId=18
StartSector=434176
NumSectors=512
BytesPerSector=4096
PartitionId=11
Name=PIA
DeviceId=18
StartSector=434688
NumSectors=131072
BytesPerSector=4096
PartitionId=12
Name=SEC
DeviceId=18
StartSector=565760
NumSectors=5120
BytesPerSector=4096
PartitionId=13
Name=USP
DeviceId=18
StartSector=570880
NumSectors=35840
BytesPerSector=4096
PartitionId=14
Name=PDA
DeviceId=18
StartSector=606720
NumSectors=5120
BytesPerSector=4096
PartitionId=15
Name=UDA
DeviceId=18
StartSector=611840
NumSectors=3234816
BytesPerSector=4096
PartitionId=16
Name=GPT
DeviceId=18
StartSector=3846656
NumSectors=512
BytesPerSector=4096
berbecverde said:
In the tutorial the nvflash file and 04.ebt.img were not in the same folder so they had to specify the path were the img file was.
If they are in the same folder lie you case you do not have to specify the path.
The command seems fine.The bootloader it is unlocked as far as i can tell.
You should try to see if you can flash partitions 6 or 7.
nvflash and the partitions are in the same folder right?
Click to expand...
Click to collapse
Yes all files (img + nvflash files) is in same folder c:/nvflash
I before I try and I suceed to write partition 6 - recovery and I put in tablet cwm (as you see in pictures)
I will try to write all pration not ony 2, 3
BR
Partitiontable looks OK (compared it to post #2)
So it's maybe a problem in one of the partitions itself...don't know.
But you can also write an image to a specific sector with the parameter "--rawdevicewrite"
Have a look here: http://forum.xda-developers.com/wiki/Talk:Nvflash
--rawdevicewrite
command usage: nvflash --rawdevicewrite S N <filename> --bl <bootloader> --go
used to write filename into N sectors of media starting from sector S to already flashed device
The startsectors and sizes can be taken from the output of "--getpartitiontable"
Good luck
Micky
Ameisentaetowierer said:
Partitiontable looks OK (compared it to post #2)
So it's maybe a problem in one of the partitions itself...don't know.
But you can also write an image to a specific sector with the parameter "--rawdevicewrite"
Have a look here: http://forum.xda-developers.com/wiki/Talk:Nvflash
--rawdevicewrite
command usage: nvflash --rawdevicewrite S N <filename> --bl <bootloader> --go
used to write filename into N sectors of media starting from sector S to already flashed device
The startsectors and sizes can be taken from the output of "--getpartitiontable"
Good luck
Micky
Click to expand...
Click to collapse
Honestly I'm not very good at this ... write commands and if someone does not give me orders clearly better do not jump ... than to destroy it worse so better let him ...
Mihnea
berbecverde said:
In the tutorial the nvflash file and 04.ebt.img were not in the same folder so they had to specify the path were the img file was.
If they are in the same folder lie you case you do not have to specify the path.
The command seems fine.The bootloader it is unlocked as far as i can tell.
You should try to see if you can flash partitions 6 or 7.
nvflash and the partitions are in the same folder right?
Click to expand...
Click to collapse
c:\nvflash>
c:\nvflash>nvflash -r --download 5 5.gp1.img
Nvflash started
[resume mode]
sending file: 5.gp1.img
/ 2097152/2097152 bytes sent
5.gp1.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 (0x60420
08) flags: 0
c:\nvflash>nvflash -r --download 7 7.lnx.img
Nvflash started
[resume mode]
sending file: 7.lnx.img
/ 8388608/8388608 bytes sent
7.lnx.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 (0x60420
08) flags: 0
c:\nvflash>nvflash -r --download 8 8.app.img
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
mihnea_gsm said:
Honestly I'm not very good at this ... write commands and if someone does not give me orders clearly better do not jump ... than to destroy it worse so better let him ...
Mihnea
Click to expand...
Click to collapse
Right!
If my car is broken, I would bring it to a car mechanic instead of fooling around with it.
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Ameisentaetowierer said:
Partitiontable looks OK (compared it to post #2)
So it's maybe a problem in one of the partitions itself...don't know.
But you can also write an image to a specific sector with the parameter "--rawdevicewrite"
Have a look here: http://forum.xda-developers.com/wiki/Talk:Nvflash
--rawdevicewrite
command usage: nvflash --rawdevicewrite S N <filename> --bl <bootloader> --go
used to write filename into N sectors of media starting from sector S to already flashed device
The startsectors and sizes can be taken from the output of "--getpartitiontable"
Good luck
Micky
Click to expand...
Click to collapse
if you know how to compose these commands pls write me 1 or 2 then I can handle it.
Thx
mihnea
Since the gapps for 4.4 need very much space wee need bigger system partitions.
I've created a script which automates this process and increases them both to 840MB.
the space is taken from the userdata partition.
You should backup your whole phone before doing this(storage will not be touched but you shouldn't take the risk)
I tested it with 32GB version only so if you want to know if it will work for 16gb, too give me the output of this command:
parted -s /dev/block/mmcblk0 print
Download:
http://d-h.st/FWz
Instructions:
1) boot into CWM
2) adb push repartition.sh /tmp
3) adb shell chmod 0777 /tmp/repartition.sh
4) adb shell /tmp/repartition.sh
5) adb reboot recovery
6) now you can do all the usual stuff like enabling TDB and installing ROM's
Sounds great but I cannot test it, since I dont have any parted binaries (at least in my 4.1.1 Wajk Wiui ROM) ? Can you please tell me where I can get them.
Second Question:
Im currently running TDB:
System 1 latest WIUI 4.1.1 v5 ROM
System 2 MIUI v6 1.9.19
Both system partitions are completely full (usage 98 %) and the same with the data partitions ( usage 97 % )!
Would it be possible to decrease /sdcard space and repartition it like the following with TDB enabled:
system 800 mb
system1 800 mb
data 1500 mb
data1 1500 mb
sdcard *the rest*
thanks in advance
sounds like you tried to repartition from Android
You need to boot to CWM - you have parted there.
Sorry I hate people who just ask stupid questions before reading the instructions carefully ...silly me sorry for that...
What about the second question, is it possible to either increase the data partitions for less space on /sdcard ?
there isn't sth. like a data1 partition. we have one data partition only that's why we need the TDB hack.
other than that it's possible but you should backup all your data and restore it afterwards.
m11kkaa said:
there isn't sth. like a data1 partition. we have one data partition only that's why we need the TDB hack.
other than that it's possible but you should backup all your data and restore it afterwards.
Click to expand...
Click to collapse
Ok got it.
So following your instructions and editing script like the following should work ?
Code:
change_table() {
ui_print "parted: delete"
parted -s /dev/block/mmcblk0 rm 23 || return 1 # system
parted -s /dev/block/mmcblk0 rm 24 || return 1 # system1
parted -s /dev/block/mmcblk0 rm 25 || return 1 # cache
parted -s /dev/block/mmcblk0 rm 26 || return 1 # userdata
parted -s /dev/block/mmcblk0 rm 27 || return 1 # storage
ui_print "parted: create"
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 336MB 1176MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 1176MB 2016MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 2016MB 2419MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 2419MB 6515MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 6515MB 31.3GB || return 1
ui_print "parted: name"
parted -s /dev/block/mmcblk0 name 23 system || return 1
parted -s /dev/block/mmcblk0 name 24 system1 || return 1
parted -s /dev/block/mmcblk0 name 25 cache || return 1
parted -s /dev/block/mmcblk0 name 26 userdata || return 1
parted -s /dev/block/mmcblk0 name 27 storage || return 1
return 0
}
Code:
ui_print "format partitions"
for NUM in 23 24 25 26 27
do
if ! format_partition "$NUM"; then
ui_print "Failed format partition $NUM"
exit 1
fi
done
already did full backup of sdcard, i just dont know if i should disable TDB before i stat repartitioning ... I dont know how TDB works to split the data partition thats my problem :/
yes that should work.
You don't need to disable TDB because your whole data partition will be wiped and it stores the TDB configuration(that means that TDB automatically gets disabled).
Had some errors but now its working fine ..thanks
unmount sdcard in CWM. It's a bug of this script.
Nice to hear it works now.
7 days ago Phone not start because partition corrupt
Hello
First do not panic is not the fault of your script but for you experience with mi2s and partitions are the few people in the world that can save my phone.
I'm playing a game phone(Xiaomi m2s 16GB) hang and one or more partitions are corrupt (I think this is the problem). But all de documentation than i find to delete o edit partition not work. Fastboot rom installation all ok but always only start with white logo. Mirecovery works perfectly and CWM by ivan works but temporally with this command sudo fastboot boot recovery.img
This is the result of your script
check environment
/sbin/mount
/sbin/umount
/sbin/parted
/sbin/tune2fs
/sbin/e2fsck
dump old table
unmount partitions
umount: can't umount /system: Invalid argument
umount: can't umount /system1: No such file or directory
umount: can't umount /data: Invalid argument
umount: can't umount /data_root: Invalid argument
umount: can't umount /sdcard: Invalid argument
change partition table
parted: delete
parted: create
Error: Unable to satisfy all constraints on the partition.
Failed changing table
OTHER TEST
/dev/block # e2fsck -fDp /dev/block/mmcblk0p24
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
/dev/block/mmcblk0p24:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/block # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p24
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
Couldn't find valid filesystem superblock.
I try to delete partition and create a new one but fail.
(parted) rm 24
rm 24
(parted) mkpartfs primary ext2 872 1409
mkpartfs primary ext2 872 1409
Error: Unable to satisfy all constraints on the partition.
I FOUND THIS IN XDA FORUM BUT I HAVEN'T IMAGE TO TEST
adb push mmcblk0p19_repaired.img /tmp/
adb shell dd if=/tmp/mmcblk0p19_repaired.img of=/dev/block/mmcblk0p19
adb reboot bootloader
MY PARTITION TABLE SYSTEM1 NOT HAVE FILESYSTEM EXT4
[email protected]:~/Escritorio/recovery$ sudo adb shell parted -s /dev/block/mmcblk0 print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 89.1MB 89.1MB fat16 modem
2 89.1MB 178MB 89.1MB fat16 modem1
3 178MB 179MB 524kB sbl1
4 179MB 179MB 524kB sbl2
5 179MB 180MB 1049kB sbl3
6 180MB 181MB 1049kB rpm
7 181MB 182MB 1049kB tz
8 182MB 183MB 524kB DDR
9 183MB 187MB 4194kB aboot
10 187MB 188MB 1049kB misc
11 188MB 191MB 2990kB logo
12 191MB 192MB 799kB m9kefs1
13 192MB 193MB 799kB m9kefs2
14 193MB 193MB 1024B m9kefsc
15 193MB 201MB 8501kB bk1
16 201MB 202MB 799kB m9kefs3
17 202MB 268MB 66.3MB bk2
18 268MB 284MB 15.7MB boot
19 284MB 300MB 15.7MB boot1
20 300MB 316MB 15.7MB recovery
21 316MB 327MB 11.5MB bk3
22 327MB 336MB 8389kB ext4 persist
23 336MB 872MB 537MB ext4 system
24 872MB 1409MB 537MB system1
25 1409MB 1812MB 403MB ext4 cache
26 1812MB 5570MB 3758MB ext4 userdata
27 5570MB 15.8GB 10.2GB ext4 storage
Xiaomi Mi2 32GB
XIAOMI MI2 32GB ONLY
For those using a single MIUI ROM I've made a partition table with system1 set to 1024Mb.
Run the attached from CWM (in /tmp).
Aternus said:
XIAOMI MI2 32GB ONLY
For those using a single MIUI ROM I've made a partition table with system1 set to 1024Mb.
Run the attached from CWM (in /tmp).
Click to expand...
Click to collapse
Can you explain a little more? Does it only leave 1 system partition? Can I flash it like a regular zip?
Enviado desde mi MI 2S mediante Tapatalk
any step by step manual how to change partition? with all necessary downloads etc...
or.... is it possible to delete system2 with all its parts? - for me I'd to use system1 only
Why can not I change the size of the system partition?
Already tried several times, with disabled TDB and with enabled TDB.
Full wipe did and still no result.
P.S. I have already been able to do any repartitioning.
Code:
PS C:\Android> adb push repartition.sh /tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
21 KB/s (3797 bytes in 0.169s)
PS C:\Android> adb shell chmod 0777 /tmp/repartition.sh
PS C:\Android> adb shell /tmp/repartition.sh
check environment
/sbin/mount
/sbin/umount
/sbin/parted
/sbin/tune2fs
/sbin/e2fsck
dump old table
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
unmount partitions
umount: can't umount /system: Invalid argument
umount: can't umount /system1: No such file or directory
umount: can't umount /data: Invalid argument
umount: can't umount /sdcard: Invalid argument
change partition table
parted: delete
parted: create
parted: name
format partitions
format: /dev/block/mmcblk0p23
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p23
Couldn't find valid filesystem superblock.
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p23
Possibly non-existent device?
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p23: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p23: 11/500856 files (0.0% non-contiguous), 62917/1000445 blocks
format: /dev/block/mmcblk0p24
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p24: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p24: 11/262144 files (0.0% non-contiguous), 49386/524289 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p24: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p24: 11/262144 files (0.0% non-contiguous), 49386/524289 blocks
format: /dev/block/mmcblk0p25
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p25: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p25: 11/196608 files (0.0% non-contiguous), 32935/393217 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p25: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p25: 11/196608 files (0.0% non-contiguous), 32935/393217 blocks
format: /dev/block/mmcblk0p26
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p26: 11/399200 files (9.1% non-contiguous), 28951/798348 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p26: 11/399200 files (9.1% non-contiguous), 28951/798348 blocks
Done.
PS C:\Android> adb reboot recovery
PS C:\Android>
UPD. The problem was that I was using Windows Povershell
Run the script from the command line and everything turned out.
Thanks!
I have to format first system and system1 in recovery to apply this script, because I have and error :
tmp/repartition.sh lin 115 can´t create /sdcard/parted_12_06_2014_FDFD6F4CB043F4956D9CAD053C3738AA.
DO MOUNT your SDCARD
then Follow the instruction
duhh...
I modified the script a little bit for 1 ROM usage. System1 is 840MB as in the original and System2 is 5MB. The rest goes into userdata. This is for the 16GB version.
Ok! I did again and umount the sdcard abd it worked fine.
Thanks
I found a better way
If u reboot into dload mode, u can change the partition table from your computer
The problem is that most partition managers don't support changing the GPT Partition names and that's why I added support for that to GParted.
GParted supports booting from Live CD/USB so Windows/Mac users aren't left out.
http://i.imgur.com/3SwSXs2.png
I pushed the patch to GParted repo's and I'll inform u once there're any news.
from my point of view the best way for use is:
- system (system1) - let 1024 MB
- system1 (system2) - let 10 MB
- userdata (apps) - let 4096 MB (take it from sdcard) - but maybe more
emmcdl is a command line utility allowing all sorts of manipulations in EDL mode using Sahara/Firehose protocol and a device-specific "programmer" file :
Code:
$ emmcdl
Version 2.10
Usage: emmcdl <option> <value>
Options:
-l List available mass storage devices
-info List HW information about device attached to COM (eg -p COM8 -info)
-MaxPayloadSizeToTargetInBytes The max bytes in firehose mode (DDR or large IMEM use 16384, default=8192)
-SkipWrite Do not write actual data to disk (use this for UFS provisioning)
-SkipStorageInit Do not initialize storage device (use this for UFS provisioning)
-MemoryName <ufs/emmc> Memory type default to emmc if none is specified
-SetActivePartition <num> Set the specified partition active for booting
-disk_sector_size <int> Dump from start sector to end sector to file
-d <start> <end> Dump from start sector to end sector to file
-d <PartName> Dump entire partition based on partition name
-d [email protected]<start> <size> Dump size of logbuf to the console
-e <start> <num> Erase disk from start sector for number of sectors
-e <PartName> Erase the entire partition specified
-s <sectors> Number of sectors in disk image
-p <port or disk> Port or disk to program to (eg COM8, for PhysicalDrive1 use 1)
-o <filename> Output filename
[<-x <*.xml> [-xd <imgdir>]>...] Program XML file to output type -o (output) -p (port or disk)
-f <flash programmer> Flash programmer to load to IMEM eg MPRG8960.hex
-i <singleimage> Single image to load at offset 0 eg 8960_msimage.mbn
-t Run performance tests
-b <prtname> <binfile> Write <binfile> to GPT <prtname>
-g GPP1 GPP2 GPP3 GPP4 Create GPP partitions with sizes in MB
-gq Do not prompt when creating GPP (quiet)
-r Reset device
-ffu <*.ffu> Download FFU image to device in emergency download need -o and -p
-splitffu <*.ffu> -o <xmlfile> Split FFU into binary chunks and create rawprogram0.xml to output location
-protocol <s|f> Can be <s>(STREAMING), default is <f>(FIREHOSE)
-gpt Dump the GPT from the connected device
-raw Send and receive RAW data to serial port 0x75 0x25 0x10
-wimei <imei> Write IMEI <imei>
-v Enable verbose output
Examples: emmcdl -p ttyUSB0 -info
emmcdl -p ttyUSB0 -gpt
emmcdl -p ttyUSB0 -SkipWrite -SkipStorageInit -MemoryName ufs -f prog_emmc_firehose_8994_lite.mbn -x memory_configure.xml
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -x rawprogram0.xml -SetActivePartition 0
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -x rawprogram0.xml -xd imagedir -SetActivePartition 0
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -ffu wp8.ffu
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -d 0 1000 -o dump_1_1000.bin
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -d SVRawDump -o svrawdump.bin
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -b SBL1 c:\temp\sbl1.mbn
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -e 0 100
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -e MODEM_FSG
emmcdl -p ttyUSB0 -f prog_emmc_firehose_8994_lite.mbn -raw 0x75 0x25 0x10
Checking in tools/ subdirectory Sugar QCT_SP v11.1.2 (after installation), there are Idol35_5_NPRG7627.bin and Idol34_7_NPRG7627.bin files (among many other models). Trying :
Code:
emmcdl -p ttyUSB0 -f Idol35_5_NPRG7627.bin -b recovery twrp-3.2.1-0-idol3.img
indeed installed TWRP 3.2.1
It also works for dumping partitions (didn't try restore) :
Code:
emmcdl -p ttyUSB0 -f Idol35_5_NPRG7627.bin -d recovery -o backup-recovery.img
I guess it should be possible to even replace MobileUpgradeQ if we can catch the files and write an Sahara XML file.
The OTUUpgrade log made by MUQ could help a lot for this...
GNU+Linux :
The latest revision from the linked Git repo above won't build (missing files) I had to use previous revision :
Code:
git checkout 05a9615a5b70334d14f95fd194b0f34d482d3803
and correct symlinks for newer automake and probably running "autoreconf".
Windows :
I don't know what the primary download site would be, there are emmcdl.exe around the Net...
And there's this Sahara GUI tool, but seems to require writing a XML file just for writing a partition...
By the way, one can use adb to switch the phone to EDL (no more crushing volume buttons while inserting USB cable) :
Code:
sudo adb reboot edl
after flashing recovery i want the phone to boot to system again. i get Status: 6 then handle is invalid when i add -r.
my vivo v9 bootloader is lock and until now, no one manage to unlock it. i have even send to repair shop to unlock bootloader. they using mrt dongle, but unsuccessful
if i obtained firehose for my phone and dump the boot.image using emmcdl,
can i modify the boot.img using magisk and flash back using emmcdl.
will it work?
i have tried to dump devinfo.img successfully.
ahhl said:
my vivo v9 bootloader is lock and until now, no one manage to unlock it. i have even send to repair shop to unlock bootloader. they using mrt dongle, but unsuccessful
if i obtained firehose for my phone and dump the boot.image using emmcdl,
can i modify the boot.img using magisk and flash back using emmcdl.
will it work?
i have tried to dump devinfo.img successfully.
Click to expand...
Click to collapse
If the bootloader accepts the modified boot.img I guess it could work.
Switching between SailfishOS and LineageOS works here by writing their respective boot.img without requiring fastboot, rooting or unlocking OEM in Android.
Difficult to say in advance what will work on each specific device...
Make sure you backup first, and have a way to reset/reinstall the phone if things go wrong.
Could i read and write any qualcomm phone with emmcdl..??
emmcdl (or more modern and maintained edl tool) should be able to flash any qcom device for which you have a suitable "flash programmer" file.
"Suitable" meaning that the device recognizes it as correctly signed by the OEM/vendor, or that signature verification is disabled in which case you can use a generic programmer file adapted to the SoC of the device.
Hi all, I wrote a 2022 update on how to put the phone into a fastboot state using the edl tool mentioned by vknecht above (btw, thank you so much for all your hard work over the years!)
You can find it here:
[TOOL] Sahara & Firehose Test (Alcatel Flasher oncoming ...)
Let me introduce some new tool for you. This is my first practice in learning and understanding "How to work with Sahara & Firehose?" and as an owner of Alcatel Idol 3 4.7" firsts test of this app were made on my Idol 3 6039Y. What is this...
forum.xda-developers.com