Guys,
While I was trying to replace boot,system and recovery images with NVFlash using Modaco's tool for O2X, I forgot to replace the partitions and flashed O2X partitions stated below(Taken from android_fastboot_emmc_full.cfg). Is there anyway that I can find the sizes, id's and types of G2X's partitions so I can set a table like this and flash it to fix my partitions.
Ps. I did try Casper's way( using adb) but I can't go into recovery, and using KDZ flasher but since my phone stucked at LG icon bootloop my computer doesn't recognize the device. Is there anyway to recover the phone completely( Partitions, recovery, boot, and system images) using NVFlash?
[device]
type=hsmmc
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PT
id=3
type=partition_table
allocation_policy=absolute
filesystem_type=basic
start_location=4194304
size=2048
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=1572864
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=fastboot.bin
[partition]
name=MBR
id=5
type=master_boot_record
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=APP
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=367001600
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
[partition]
name=CAC
id=7
type=data
allocation_policy=sequential
filesystem_type=ext3
size=67108864
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=MSC
id=8
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
# extended partition
[partition]
name=EB1
id=9
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=113976
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=LNX
id=10
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=boot.img
[partition]
name=EB2
id=11
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=DRM
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2306560
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EB3
id=13
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=SOS
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=20971520
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=recovery.img
[partition]
name=EB4
id=15
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDA
id=16
type=data
allocation_policy=sequential
filesystem_type=ext3
size=1610612736
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EB5
id=17
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDB
id=18
type=data
allocation_policy=sequential
filesystem_type=ext3
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
i am also looking for this.
raar said:
Guys,
While I was trying to replace boot,system and recovery images with NVFlash using Modaco's tool for O2X, I forgot to replace the partitions and flashed O2X partitions stated below(Taken from android_fastboot_emmc_full.cfg). Is there anyway that I can find the sizes, id's and types of G2X's partitions so I can set a table like this and flash it to fix my partitions.
Ps. I did try Casper's way( using adb) but I can't go into recovery, and using KDZ flasher but since my phone stucked at LG icon bootloop my computer doesn't recognize the device. Is there anyway to recover the phone completely( Partitions, recovery, boot, and system images) using NVFlash?
[device]
type=hsmmc
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PT
id=3
type=partition_table
allocation_policy=absolute
filesystem_type=basic
start_location=4194304
size=2048
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=1572864
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=fastboot.bin
[partition]
name=MBR
id=5
type=master_boot_record
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=APP
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=367001600
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
[partition]
name=CAC
id=7
type=data
allocation_policy=sequential
filesystem_type=ext3
size=67108864
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=MSC
id=8
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
# extended partition
[partition]
name=EB1
id=9
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=113976
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=LNX
id=10
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=boot.img
[partition]
name=EB2
id=11
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=DRM
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2306560
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EB3
id=13
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=SOS
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=20971520
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=recovery.img
[partition]
name=EB4
id=15
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDA
id=16
type=data
allocation_policy=sequential
filesystem_type=ext3
size=1610612736
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EB5
id=17
type=extended_boot_record
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDB
id=18
type=data
allocation_policy=sequential
filesystem_type=ext3
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
Click to expand...
Click to collapse
Have you tried one click nvflash to flash recovery try this steps first
1. Get one click nvflash
2 Pull your battery out
3. Plug usb to pc
4.Hold volume up/volume down
5.flash recovery and then you will get spw screen
I tried to flash the stock recovery but NVFlash is giving me this error
" Partition download failed "
I'll take a look at how the O2x table is written and try to get y'all something to work with on the g2x
Sent from my LG-P999 using XDA Premium App
What you might want to try is using "recovery phone" from the lgmobile updater. Before you start get your serial# and IMEI from under the battery, you will need both. I'm unsure if this method works though.
Sent from my LG-P999 using XDA Premium App
casper200519 said:
What you might want to try is using "recovery phone" from the lgmobile updater. Before you start get your serial# and IMEI from under the battery, you will need both. I'm unsure if this method works though.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
I also tried that but the computer only recognizes my device as a APX driver because I can't go into recovery or S/W upgrade or normal boot mode, and when I'm at the APX driver LG's software doesn't recognize it
I've got about 3 hours before I have a chance to take a look at it.
Sent from my LG-P999 using XDA Premium App
raar said:
I also tried that but the computer only recognizes my device as a APX driver because I can't go into recovery or S/W upgrade or normal boot mode, and when I'm at the APX driver LG's software doesn't recognize it
Click to expand...
Click to collapse
Since you can get it to go into download mode try to flash CWR on external
Sent from my LG-P999 using XDA Premium App
raar said:
I also tried that but the computer only recognizes my device as a APX driver because I can't go into recovery or S/W upgrade or normal boot mode, and when I'm at the APX driver LG's software doesn't recognize it
Click to expand...
Click to collapse
Dude I'm just curious were you trying to port something or so you thought cause how do you flash o2x rom ,
and looks like you had fake recovery prior to flashing.
doniqcc said:
Dude I'm just curious were you trying to port something or so you thought cause how do you flash o2x rom ,
and looks like you had fake recovery prior to flashing.
Click to expand...
Click to collapse
I do know how stupid it sounds but I didn't flash O2X rom. His tool flashes the system boot and recovery images with NVFlash, I got G2X's images from the 2.3.3 images thread, the recovery image from TGA_Gunmann's thread and replace the images that tool has with them.Assuming that it will push those images to my phone, but I didn't foresee the partition change. Now it sounds less stupid
raar said:
Guys,
While I was trying to replace boot,system and recovery images with NVFlash using Modaco's tool for O2X, I forgot to replace the partitions and flashed O2X partitions stated below(Taken from android_fastboot_emmc_full.cfg). Is there anyway that I can find the sizes, id's and types of G2X's partitions so I can set a table like this and flash it to fix my partitions.
Ps. I did try Casper's way( using adb) but I can't go into recovery, and using KDZ flasher but since my phone stucked at LG icon bootloop my computer doesn't recognize the device. Is there anyway to recover the phone completely( Partitions, recovery, boot, and system images) using NVFlash?
Click to expand...
Click to collapse
Yes. You can restore the original partitions using SmartFlashTool_P990. I don't know how to do it using nvflash.
Get SmartFlashTool_P990.exe and the drivers from this post (Windows req'd)
Get LGP999AT-01-V10f-310-260-MAR-27-2011+0_CP.bin from the zip in this post.
Install the drivers.
Remove the battery AND usb cable.
While holding Volume Down, plug in the usb cable. Nothing will come up on the phone's screen, but you'll hear that Windows sound of a usb device being discovered.
Run the tool, go to the second tab, and flash the "CP" file by itself.
You'll be back to stock firmware, including having the original partition setup.
raar said:
I do know how stupid it sounds but I didn't flash O2X rom. His tool flashes the system boot and recovery images with NVFlash, I got G2X's images from the 2.3.3 images thread, the recovery image from TGA_Gunmann's thread and replace the images that tool has with them.Assuming that it will push those images to my phone, but I didn't foresee the partition change. Now it sounds less stupid
Click to expand...
Click to collapse
So then why don't you try to switch recovery with the same tool ?
It might work
Sent from my Nexus S using XDA Premium App
doniqcc said:
So then why don't you try to switch recovery with the same tool ?
It might work
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I did replace the recovery image but since the tool flashes to images according to the partitions table of O2X, my phone doesn't go into recovery mode
I'm trying the Smartflash tool right now.
Shmoopty said:
Yes. You can restore the original partitions using SmartFlashTool_P990. I don't know how to do it using nvflash.
Get SmartFlashTool_P990.exe and the drivers from this post (Windows req'd)
Get LGP999AT-01-V10f-310-260-MAR-27-2011+0_CP.bin from the zip in this post.
Install the drivers.
Remove the battery AND usb cable.
While holding Volume Down, plug in the usb cable. Nothing will come up on the phone's screen, but you'll hear that Windows sound of a usb device being discovered.
Run the tool, go to the second tab, and flash the "CP" file by itself.
You'll be back to stock firmware, including having the original partition setup.
Click to expand...
Click to collapse
SmartFlash came up with this error
00:00.0 Sec ownload Start...
00:02.0 Sec :RomBinary Download start
00:02.0 Sec :We can't read magic number
After 30 minutes I flashed AP file and everything worked perfect thank you
raar said:
SmartFlash came up with this error
00:00.0 Sec ownload Start...
00:02.0 Sec :RomBinary Download start
00:02.0 Sec :We can't read magic number
After 30 minutes I flashed AP file and everything worked perfect thank you
Click to expand...
Click to collapse
I get the same error but if I try the AP file it gives me another type of error, NVflash connects but doesn't seem to write to it.
meoshe said:
I get the same error but if I try the AP file it gives me another type of error, NVflash connects but doesn't seem to write to it.
Click to expand...
Click to collapse
Ditto - plus I cannot seem to get past "can't read magic number" with the CP.bin - the one I need the most.
I am currently sitting here with a 999 that thinks it is a 990 (cured my S/W Updater lock screen issue, but now looking for a way back from 990.
I someone had a partition layout like early in this tread, i would try to put it in Pau'ls 990 disaster recovery tool and with a few other tweaks - see if it would restore a 999 to stock including partition.
gaww said:
Ditto - plus I cannot seem to get past "can't read magic number" with the CP.bin - the one I need the most.
I am currently sitting here with a 999 that thinks it is a 990 (cured my S/W Updater lock screen issue, but now looking for a way back from 990.
I someone had a partition layout like early in this tread, i would try to put it in Pau'ls 990 disaster recovery tool and with a few other tweaks - see if it would restore a 999 to stock including partition.
Click to expand...
Click to collapse
Update (I did it this way to get this visible as a recent post):
Never found the partition info, but for those that accidently flashed O2X with Paul;s tool - there is hope.
I was finally able to do it with SmartFlash.
I had been trying flashing the CP,bin and AP.bin together - got the "cannot read magic number...". Tried only the CP.bin and same error message. Tried it a number of time - same error message, But after doing that, and then tid the AP.bin only and it starred up loading 7 partitions.
It quit once, so tried again. This time it finished. Leave the device alone until it blacks out. Then disconnect, put the batter in, hold you breath and press power button.
any one having the baseband fls only of p999? because the links are not working.
Story: tf300tg with 9.4.4.40 WW -> 1 click root -> bootloader unlock -> cwm installed -> stock firmware backed up -> cm 9.1.0 installed
Now I'm trying to restore stock firmware back. I've tried to restore backup, wifi not working. I've managed to found this thread (second post here), but also no luck. Here's the log file from cwm:
Code:
Starting recovery on Thu Sep 20 17:52:13 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /staging ext3 /dev/block/mmcblk0p4 (null) 0
5 /boot emmc /dev/block/mmcblk0p5 (null) 0
6 /recovery emmc /dev/block/mmcblk0p7 (null) 0
7 /data ext4 /dev/block/mmcblk0p8 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76I
ro.build.display.id=cm_tf300t-userdebug 4.0.4 IMM76I eng.xplodwild.20120523.001506 test-keys
ro.build.version.incremental=eng.xplodwild.20120523.001506
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed May 23 00:15:38 CEST 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=xplodwild
ro.build.host=barbecue
ro.build.tags=test-keys
ro.product.model=Transformer Prime TF300T
ro.product.brand=asus
ro.product.name=EeePad
ro.product.device=tf300t
ro.product.board=cardhu
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=tf300t
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.2.21-20120323 release-keys
ro.build.fingerprint=asus/US_epad/TF201:4.0.3/IML74K/US_epad-9.4.2.21-20120323:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=tf300t
ro.carrier=wifi-only
ro.com.android.dateformat=MM-dd-yyyy
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
persist.tegra.nvmmlite=1
ro.epad.model=TF300T
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-tf300t-UNOFFICIAL
ro.modversion=9.0.0-RC0-tf300t-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=015d2d426963f60b
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.mischelp=restarting
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media, no /sdcard found.
-- Installing: /sdcard/WW_epad-user-9.4.4.40.zip
Finding update package...
I:Update location: /sdcard/WW_epad-user-9.4.4.40.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
start to download IMC modem
Start to Downloading
count 5
add file 0 5 1
add file 1 5 2
add file 2 5 4
add file 3 5 4
add file 4 5 4
mknod /dev/ttyACMX0
run command: /system/bin/insmod /system/lib/modules/baseband_usb_chr.ko
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Set Com Port
SetComPort m_channel1 com:/dev/ttyACMX0 921600
SetComPort success
Reset modem
cannot open /sys/devices/platform/baseband_xmm_power/xmm_dwd_reset
ErrorText
Synchronized boot fail
Retry too many times!
script aborted (no error message)
script aborted (no error message)E:Error in /sdcard/WW_epad-user-9.4.4.40.zip
(Status 7)
Installation aborted.
I:using /data/media, no /sdcard found.
Signature Check: Enabled
Signature Check: Disabled
Script Asserts: Enabled
Script Asserts: Disabled
Sorry for being such a noob. Can someone tell me what am I doing wrong?
what happens if you try to flash original asus fw via fastboot?
this should work for sure...
Yes, I've finally manage to do this via fastboot, but only from second try, which is confusing..
Maybe it will help someone (blob is file twice extracted from original asus update zip):
Code:
E:\android_sdk\platform-tools>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [136.662s]
writing 'system'...
FAILED (remote: ()
finished. total time: 137.107s
E:\android_sdk\platform-tools>fastboot -i 0x0b05 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
E:\android_sdk\platform-tools>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [136.584s]
writing 'system'...
OKAY [184.836s]
finished. total time: 321.419s
kykc said:
Yes, I've finally manage to do this via fastboot, but only from second try, which is confusing..
Maybe it will help someone (blob is file twice extracted from original asus update zip):
Code:
E:\android_sdk\platform-tools>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [136.662s]
writing 'system'...
FAILED (remote: ()
finished. total time: 137.107s
E:\android_sdk\platform-tools>fastboot -i 0x0b05 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
E:\android_sdk\platform-tools>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [136.584s]
writing 'system'...
OKAY [184.836s]
finished. total time: 321.419s
Click to expand...
Click to collapse
when i try this
this error comes
C:\Users\VaHiD\AppData\Local\Android\android-sdk\platforms\fastboot>fastboot -i
0x0b05 flash system blob
sending 'system' (799748 KB)...
OKAY [138.170s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 214.335s
what i did wrong?
So, I've been searching around but haven't found any vital information. Nothing is explained in detail.
I've found out I've 16 partitions on my TF101 (I've installed linux on it). I got the partition information via nvflash i.e.:
$ sudo ./nvflash --getpartitiontable partition_table.txt
The question is, I don't know what all this partitions are for:
Code:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048
PartitionId=3
Name=PT
DeviceId=18
StartSector=1536
NumSectors=256
BytesPerSector=2048
PartitionId=4
Name=EBT
DeviceId=18
StartSector=1792
NumSectors=2048
BytesPerSector=2048
PartitionId=5
Name=SOS
DeviceId=18
StartSector=3840
NumSectors=2560
BytesPerSector=2048
PartitionId=6
Name=LNX
DeviceId=18
StartSector=6400
NumSectors=4096
BytesPerSector=2048
PartitionId=7
Name=BAK
DeviceId=18
StartSector=10496
NumSectors=2560
BytesPerSector=2048
PartitionId=8
Name=GP1
DeviceId=18
StartSector=13056
NumSectors=512
BytesPerSector=2048
PartitionId=9
Name=APP
DeviceId=18
StartSector=13568
NumSectors=262144
BytesPerSector=2048
PartitionId=10
Name=CAC
DeviceId=18
StartSector=275712
NumSectors=271104
BytesPerSector=2048
PartitionId=11
Name=MSC
DeviceId=18
StartSector=546816
NumSectors=1024
BytesPerSector=2048
PartitionId=12
Name=USP
DeviceId=18
StartSector=547840
NumSectors=271104
BytesPerSector=2048
PartitionId=13
Name=PER
DeviceId=18
StartSector=818944
NumSectors=2560
BytesPerSector=2048
PartitionId=14
Name=YTU
DeviceId=18
StartSector=821504
NumSectors=256
BytesPerSector=2048
PartitionId=15
Name=UDA
DeviceId=18
StartSector=821760
NumSectors=14281984
BytesPerSector=2048
PartitionId=16
Name=GPT
DeviceId=18
StartSector=15103744
NumSectors=256
BytesPerSector=2048
So here is scaled down overview:
----[PARTITION NAME] (comment/explanation)----
2 BCT
3 PT
4 EBT
5 SOS (recovery)
6 LNX (Ubuntu?)
7 BAK
8 GP1
9 APP (ROM operative system?)
10 CAC
11 MSC
12 USP
13 PER
14 YTU
15 UDA
16 GPT
Can anyone explain every partition?
My goal is to understand how to use nvflash to:
* Factory-reset
* Clear cache
* Clear data
* Flash linux
* Flash rom
* Flash recovery
and so on.
Is every above option possible via the nvflash utility? If not, which one and why?
Vantskruv said:
Can anyone explain every partition?
Click to expand...
Click to collapse
Try the table at http://forum.xda-developers.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu#Development for starters. Feel free to flesh that out if you can.
Here are a few I know off top of my head
----[PARTITION NAME] (comment/explanation)----
2 BCT
3 PT
4 EBT Bootloader Partition
5 SOS (recovery) correct
6 LNX (Ubuntu?) The main ROM of the system
7 BAK Backup I believe
8 GP1
9 APP (ROM operative system?) LNX is the ROM, APP is the userdata stored in the rom I believe
I don't recognize the rest of these, as I havn't had to use them.
10 CAC
11 MSC
12 USP
13 PER
14 YTU
15 UDA
16 GPT
More research into NvFlash could turn up their uses.
Hello,
I've recompiled the CyanogenMod 10.2 kernel for my TF300T with NFSv3 and CIFS support built into it. I have also a working ramdisk that i've unpacked from my own build of the CyanogenMod 10.2 ROM from CyanogenMod sources.
I've packed my zImage and the ramdisk using the following command line :
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel my-zImage --ramdisk my-ramdisk-archive -o my-boot-image
And then i created a blob file from it :
Code:
blobpack my-blob LNX my-boot-image
Finally i've tried to flash it to my TF300T with fastboot :
Code:
fastboot flash staging my-blob
...the flash procedure output is as usual :
Code:
sending 'staging' (5550 KB)...
OKAY [ 2.370s]
writing 'staging'...
OKAY [ 1.964s]
finished. total time: 4.335s
... but the :
Code:
fasboot reboot
command just hangs !
I must then press the power button for some time to restart the device and when it's back alive, i'm still with the old kernel !
Please correct me if i am wrong but i think after searching over here and there over the Internet that i've inputed wrong parameters to the mkbootimg executable in order to generate my boot.img file ...
After reading carrefully with a 'not perfect' english this article : Unpack/repack boot.img/ramdisk for Android ... i've not understood how to get the correct parameters for mkbootimg ...
Any help will be greatly appreciated,
Thank You
ne0zone75 said:
...the flash procedure output is as usual :
Code:
sending 'staging' (5550 KB)...
OKAY [ 2.370s]
writing 'staging'...
OKAY [ 1.964s]
finished. total time: 4.335s
... but the :
Code:
fasboot reboot
command just hangs !
I must then press the power button for some time to restart the device and when it's back alive, i'm still with the old kernel !
...
Click to expand...
Click to collapse
I'm pretty sure problem is not in command line arguments. I use androidroot blobtools + boottools for making blob and have same result before I read this. So You just need to put signature in the beginning of blob file:
Code:
echo -n "-SIGNED-BY-SIGNBLOB-" > blobtmp
dd if=/dev/zero bs=1 count=8 >> blobtmp
cat blob >> blobtmp
Graiden05 said:
I'm pretty sure problem is not in command line arguments ...
Click to expand...
Click to collapse
You were right : IT WORKED ! :good:
Thanks a lot for your fast answer !
I would like to enlarge the data partition of my Samsung S2 I9100, and there is a good thread about it here.
It has the command to flash the PIT as
Code:
$ heimdall flash --repartition --pit newpit.pit
But heimdall is refusing to flash, I guess because I have to specify all partitions with the same command:
Code:
$ heimdall flash --repartition --pit I9100_16GB_6GBdata.pit
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
It's heimdall 1.4.0. Is it not possible anymore to flash just the PIT?
P.s.: Of course it is dangerous, I know, I diffed old and new PIT file and only the data and ums partitions seem to change.