Related
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.
edit: Would some money to help find answers?
If i try to install any fw with cwm, it doesnt change. Smartflash, same thing.
So next to try is fastboot method for getting to original ics(and get imei back).
If that doesnt work, next is adb push and flashing.
As some guested my phone is having Groundhog day, everytime it starts from clean table.
All settings all gone, apps etc.
If that thing was something else than 3D, i would throw it out of window.
And same thing with recovery, 5.8 stays there.
Parted doesnt remove partitions, format is missing.
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB x-loader
2 262kB 393kB 131kB nv1
3 393kB 524kB 131kB nv2
4 524kB 1049kB 524kB u-boot
5 1049kB 11.5MB 10.5MB kernel
6 11.5MB 22.0MB 10.5MB recovery
7 22.0MB 651MB 629MB ext4 system
8 651MB 1725MB 1074MB ext3 userdata
9 1725MB 1859MB 134MB fsswap
10 1859MB 1926MB 67.1MB ext3 cache
11 1926MB 1928MB 2097kB lgdrm
12 1928MB 1929MB 1049kB divxkey
13 1929MB 1950MB 21.0MB fota
14 1950MB 1955MB 4194kB misc
15 1955MB 7942MB 5987MB fat
(parted)
G:\lg 3d\flashing\omap4boot-for_optimus-v1.21>bin\fastboot flash recovery recove
ry-clockwork-touch-6.0.1.9-p920.img
sending 'recovery' (5355 KB)...
OKAY [ 2.783s]
writing 'recovery'...
OKAY [ 0.504s]
finished. total time: 3.287s
G:\lg 3d\flashing\omap4boot-for_optimus-v1.21>pause
Press any key to continue . . .
Is 5€ enough?
I have heard of this problem before. When you install any app, turn off your phone, take out a battery for 10min and get it back in, turn it back on, do you still have that app installed or not?
If you don't have that app installed after the restart... I think it's a hardware problem, the flash chip went bad. :/
Is there any way fix if flash chip is dead?
kalamake said:
edit: Would some money to help find answers?
If i try to install any fw with cwm, it doesnt change. Smartflash, same thing.
So next to try is fastboot method for getting to original ics(and get imei back).
If that doesnt work, next is adb push and flashing.
As some guested my phone is having Groundhog day, everytime it starts from clean table.
All settings all gone, apps etc.
If that thing was something else than 3D, i would throw it out of window.
And same thing with recovery, 5.8 stays there.
Parted doesnt remove partitions, format is missing.
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB x-loader
2 262kB 393kB 131kB nv1
3 393kB 524kB 131kB nv2
4 524kB 1049kB 524kB u-boot
5 1049kB 11.5MB 10.5MB kernel
6 11.5MB 22.0MB 10.5MB recovery
7 22.0MB 651MB 629MB ext4 system
8 651MB 1725MB 1074MB ext3 userdata
9 1725MB 1859MB 134MB fsswap
10 1859MB 1926MB 67.1MB ext3 cache
11 1926MB 1928MB 2097kB lgdrm
12 1928MB 1929MB 1049kB divxkey
13 1929MB 1950MB 21.0MB fota
14 1950MB 1955MB 4194kB misc
15 1955MB 7942MB 5987MB fat
(parted)
G:\lg 3d\flashing\omap4boot-for_optimus-v1.21>bin\fastboot flash recovery recove
ry-clockwork-touch-6.0.1.9-p920.img
sending 'recovery' (5355 KB)...
OKAY [ 2.783s]
writing 'recovery'...
OKAY [ 0.504s]
finished. total time: 3.287s
G:\lg 3d\flashing\omap4boot-for_optimus-v1.21>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Try making a system.img and flashing it
Sent from my R800i using xda app-developers app
Hi there everyone
Yes, unfortunately , as it is said in the movie when I was registering, a NOOB here. I was looking for a solution all over there forum and still nothing, it may be also some skills lack in installing or flashing etc.
But as in topic. Can it be fixed?
Today I received a message about new firmware update to Jelly Bean 4.2. I was over the moon when I saw it!!
When everything downloaded and I taped to start the update. TF turned off, started , the green android showed up with tha blue ball and the he fell with red triangle... [email protected]/#!!!
So i restarted it and now the message doesn't show up.
Here is what i tried:
- forcing to shut down and clearing data of DMClinet , CMClient, Google service framework - result nothing
- Multiple hard resets - result nothing
- downgrade to ICS - result nothing
- updating to JB 4.1.1 from ICS with dlpkgfile - result nothing
As far as I know there is one option that worked for me and it is sending to ASUS - result they made it and when I got my TF back Automatic updates were back ( I didn't send it just because of updates . there was problem with a mobile dock )
I don't want to do manual updates all the time, because as far as I know there are much more automatic updates and it is much simpler and quicker than flashing everything again and again.
Some more info about my TF700:
Rom: 4.1.1.
Rooted on ICS and kept the root even with manual flashing.
This may be helpful i use Pimp my rom, Seeder and automatic task killer
So people please:
Short answers do I have to sand it back to Asus again so they can fix it or anyone can show me the way step by step to repair this and get back automatic updates?
Thanks
benihussan said:
Hi there everyone
Yes, unfortunately , as it is said in the movie when I was registering, a NOOB here. I was looking for a solution all over there forum and still nothing, it may be also some skills lack in installing or flashing etc.
But as in topic. Can it be fixed?
Today I received a message about new firmware update to Jelly Bean 4.2. I was over the moon when I saw it!!
When everything downloaded and I taped to start the update. TF turned off, started , the green android showed up with tha blue ball and the he fell with red triangle... [email protected]/#!!!
So i restarted it and now the message doesn't show up.
Here is what i tried:
- forcing to shut down and clearing data of DMClinet , CMClient, Google service framework - result nothing
- Multiple hard resets - result nothing
- downgrade to ICS - result nothing
- updating to JB 4.1.1 from ICS with dlpkgfile - result nothing
As far as I know there is one option that worked for me and it is sending to ASUS - result they made it and when I got my TF back Automatic updates were back ( I didn't send it just because of updates . there was problem with a mobile dock )
I don't want to do manual updates all the time, because as far as I know there are much more automatic updates and it is much simpler and quicker than flashing everything again and again.
Some more info about my TF700:
Rom: 4.1.1.
Rooted on ICS and kept the root even with manual flashing.
This may be helpful i use Pimp my rom, Seeder and automatic task killer
So people please:
Short answers do I have to sand it back to Asus again so they can fix it or anyone can show me the way step by step to repair this and get back automatic updates?
Thanks
Click to expand...
Click to collapse
Can you check the "last_install" file located in /cache/recovery? is there anything in that file or empty? also the "last_log", please post the files here.
So as I tried to repair it by downgrading few minutes ago now I'm on ICS
last _install :
/sdcard/EP201_768_SDUPDATE.zip
1
and Last_log :
Starting recovery on Thu Apr 4 19:55:49 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
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 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d2ea06d400607
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.25-20121228
ro.build.version.incremental=WW_epad-10.4.4.25-20121228
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Dec 28 18:53:10 CST 2012
ro.build.date.utc=1356691990
ro.build.type=user
ro.build.user=android
ro.build.host=Uranus
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
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=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.25-20121228 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.25-20121228:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.65
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus-rev
ro.com.google.clientidbase.ms=android-asus-rev
ro.com.google.clientidbase.am=android-asus-rev
ro.com.google.clientidbase.gmm=android-asus-rev
ro.com.google.clientidbase.yt=android-asus-rev
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.dns2
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C8OKASO29554
ro.boot_reason=normal
ro.epad.model_id=04
ro.epad.model=TF700T
wifi.supplicant_scan_interval=98
persist.wifi_scan_interval=98
ro.mot.eri.losalert.delay=900
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.FOREGROUND_APP_MEM=6400
ro.VISIBLE_APP_MEM=8960
ro.SECONDARY_SERVER_MEM=19200
ro.BACKUP_APP_MEM=23040
ro.HOME_APP_MEM=3200
ro.HIDDEN_APP_MEM=23040
ro.EMPTY_APP_MEM=64000
ro.PERCEPTIBLE_APP_MEM=3200
ro.HEAVY_WEIGHT_APP_MEM=19200
ro.CONTENT_PROVIDER_MEM=38400
ro.FOREGROUND_APP_ADJ=25
ro.VISIBLE_APP_ADJ=35
ro.SECONDARY_SERVER_ADJ=75
ro.BACKUP_APP_ADJ=76
ro.HOME_APP_ADJ=26
ro.EMPTY_APP_ADJ=89
ro.HIDDEN_APP_MIN_ADJ=250
ro.PERCEPTIBLE_APP_ADJ=27
ro.HEAVY_WEIGHT_APP_ADJ=36
ro.CONTENT_PROVIDER_ADJ=90
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=false
MIN_HIDDEN_APPS=false
MAX_HIDDEN_APPS=false
CONTENT_APP_IDLE_OFFSET=false
EMPTY_APP_IDLE_OFFSET=false
MAX_ACTIVITIES=false
ACTIVITY_INACTIVE_RESET_TIME=false
MAX_RECENT_TASKS=false
MIN_RECENT_TASKS=false
APP_SWITCH_DELAY_TIME=false
MAX_PROCESSES=false
PROC_START_TIMEOUT=false
CPU_MIN_CHECK_DURATION=false
GC_TIMEOUT=false
SERVICE_TIMEOUT=false
MIN_CRASH_INTERVAL=false
video.accelerate.hw=1
debug.sf.hw=0
debug.egl.profiler=0
debug.egl.hw=0
debug.composition.type=cpu
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
persist.sys.use_16bpp_alpha=1
ro.gsm.2nd_data_retries=null
ro.ril.enable.amr.wideband=0
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.maxres=8m
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.media.enc.hprof.vid.fps=65
ro.media.enc.jpeg.quality=100
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=65
ro.media.capture.flashIntensity=70
ro.config.hw_quickpoweron=true
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.language=pl
persist.sys.country=PL
persist.sys.localevar=
persist.sys.timezone=Europe/Brussels
init.svc.recovery=running
init.svc.adbd=running
Finding update package...
I:Update location: /sdcard/ASUS_BUNDLE.zip
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory); trying /dev/block/mmcblk1
Opening update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
I:No factory bundle package.
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /sdcard/EP201_768_SDUPDATE.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
I:SKU token:WW_epad
Iroperty get:WW_epad
I:token f:n
I:ro.build.version.incremental:WW_epad-10.4.4.25-20121228
I:device version: 10.4.4.25
I:rule version: 9.4.5.30
I:i:2 token:4
I:i:3 token:4
I:i:4 token:25
I:rule i:2 token:4
I:rule i:3 token:5
I:rule i:4 token:30
I:dec_rule: 9 4 5 30 0
I:dec_version: 10 4 4 25 0
I:downgrade version.
I:check downgrade version pass
Installing update...
Check : blob size = 817556103
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /system ext4 /dev/block/mmcblk0p1 (null)
2 /cache ext4 /dev/block/mmcblk0p2 (null)
3 /misc emmc /dev/block/mmcblk0p3 (null)
4 /boot emmc boot (null)
5 /recovery emmc recovery (null)
6 /staging emmc /dev/block/mmcblk0p4 (null)
7 /btmac vfat /dev/block/mmcblk0p5 (null)
8 /data ext4 /dev/block/mmcblk0p8 length=-32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
10 /cra emmc /dev/block/mmcblk0p7 (null)
volume path for /staging:/dev/block/mmcblk0p4
wrote staging partition from staging
script result was []
Check and format /storage to vfat if needed...
Done.
Formatting /data...
Creating filesystem with parameters:
Size: 61415587840
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994040
Block groups: 458
Reserved block group size: 1024
Created filesystem with 11/3751936 inodes and 281560/14994040 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
Here you are
As I need my Tf to work I'm back on JB 4.1.1 rooted . Flashed manually from asus website.
Ohh! I almost forgot.
there is also a useful thing to mention, when i make the combination of keys on start-up Power up and Vol down, and it gets to kernel or recovery( I'm not sure how it's called) I can;t do nothing or choose to wipe data etc. the only thing that work is Vol up in 5/10 seconds to flash an update.
I hope this is valuable. Maybe I just do something wrong.
Exactly same problem and attempted solutions here.
So as I can't wait too long i decided to send my TF700 to Asus service center so they can solve this problem.
Nevertheless I think this problem is worth solving, so everybody can do it on their own. So i really encourage everyone who got any ideas to get involved. The same problem was on Nexus 7 as i have read somewhere. And there is some solution with special program, maybe that will help a bit.
Please type in google : "Nexus 7 OTA fix", I can't post outside links so far.
benihussan said:
So as I can't wait too long i decided to send my TF700 to Asus service center so they can solve this problem.
Nevertheless I think this problem is worth solving, so everybody can do it on their own. So i really encourage everyone who got any ideas to get involved. The same problem was on Nexus 7 as i have read somewhere. And there is some solution with special program, maybe that will help a bit.
Please type in google : "Nexus 7 OTA fix", I can't post outside links so far.
Click to expand...
Click to collapse
I had the same problem with my tf700. Did you manage to find a solution or Asus fixed your problem?
Sent from my GT-I9300 using xda app-developers app
Yes, they fixed it somehow. I tried to ask them how to solve it by my own , but I didnt get any answer so the best solution is to have luck and dont have this problem or send it to Asus with some bigger problem also mentioing it.
benihussan said:
Yes, they fixed it somehow. I tried to ask them how to solve it by my own , but I didnt get any answer so the best solution is to have luck and dont have this problem or send it to Asus with some bigger problem also mentioing it.
Click to expand...
Click to collapse
I had my fixed last night via dlpkgfile. It turned out I'd previously had a wrong version of dlpkgfile.
Just need a quick answer from a dev.
Situation: Got this TF300T last year, flashed stuff, wouldn't boot, got busy.
I made an nvflash backup at some point using ICS setup.
- Fastboot Accessible
- APX/NVFlash works
- Tried restoring bricksafe.img and in cmd prompt it appeared to be loading... for an hour.
I've since flashed ICS twrp 2.6.3, boot, no recovery option. Oh, at some point I wiped the data.
Big factors:
- I need to get something working prior to a trip next month
- I don't have time to do trial and error one step a day, for the next year
- I have a 3yr extended warranty through BB but thinking that'll be voided when they see "mobiroot 9.4.30etc..."
- I don't really wanna deal with this **** unless I can get it done in like an hour with someone on IRC or something. Happy to pay you a reasonable amount to avoid dealing w bb.
If the answer is, "you're an idiot, didn't you read all the threads", yes, yes I did. But I'm stubborn, so instead of reading me the riot act or telling me about the search function I'm like... SO good at using, tell me how best to ****ing destroy this heap of **** so BB just gives me a new one. Happy to make a video of outlined fraud commital providing it's creative, and actually gets me a new tablet.
DoUevenRoot said:
Just need a quick answer from a dev.
- Fastboot Accessible
Click to expand...
Click to collapse
If fastboot works as you say, try flashing the ICS blob using fastboot and you should be good.
If that doesn't work, this thread might help you out.
k1chy said:
If fastboot works as you say, try flashing the ICS blob using fastboot and you should be good.
If that doesn't work, this thread might help you out.
Click to expand...
Click to collapse
I should also point out that
Code:
fastboot getvars all
yields no results
DoUevenRoot said:
I should also point out that
Code:
fastboot getvars all
yields no results
Click to expand...
Click to collapse
and honestly, I have no clue if I flashed a JB recovery or not. My thought was that I *should* be able to flash the "bricksafe.img" and all would be right with the world, however, as I stated above, it just sits there saying it's transferring the 11 gig file. Not sure if I'm just being impatient or what but my thought was that it shouldn't take more than an hour to transfer so I just ctrl+c'd to stop it and tried other ****.
Personally, I'm wondering if the partitions are all ****ed up and I'm absolutely amazed nobody has worked out the partitions by now and that it's not as simple as recreating the file structure manually. Incidently, how can I pull the file structure to see if that's the case?
here's what I've got. It appears ADB is broken, but fastboot works. I can flash pretty much everything, except the bricksafe for whatever reason, but nothing gets reflected on reboot.
Code:
C:\Users\Owner\Downloads\BACKUPS\ANDROID BACKUPS>adb get-state
unknown
C:\Users\Owner\Downloads\BACKUPS\ANDROID BACKUPS>fastboot -i 0x0B05 flash recovery twrp263.blob
sending 'recovery' (6368 KB)...
OKAY [ 1.805s]
writing 'recovery'...
OKAY [ 2.086s]
finished. total time: 3.896s
C:\Users\Owner\Downloads\BACKUPS\ANDROID BACKUPS>fastboot -i 0x0B05 flash boot boot.blob
sending 'boot' (5212 KB)...
OKAY [ 2.319s]
writing 'boot'...
OKAY [ 2.023s]
finished. total time: 4.345s
C:\Users\Owner\Downloads\BACKUPS\ANDROID BACKUPS>fastboot devices
00000 fastboot
Pulled the partition table in fastboot, this is what I have:
pulled the partition table, this is what I have
.
Code:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=768
BytesPerSector=4096
PartitionId=3
Name=PT
DeviceId=18
StartSector=768
NumSectors=128
BytesPerSector=4096
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=2048
BytesPerSector=4096
PartitionId=5
Name=SOS
DeviceId=18
StartSector=2944
NumSectors=2048
BytesPerSector=4096
PartitionId=6
Name=LNX
DeviceId=18
StartSector=4992
NumSectors=2048
BytesPerSector=4096
PartitionId=7
Name=CER
DeviceId=18
StartSector=7040
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=IMG
DeviceId=18
StartSector=9088
NumSectors=2048
BytesPerSector=4096
PartitionId=9
Name=GP1
DeviceId=18
StartSector=11136
NumSectors=256
BytesPerSector=4096
PartitionId=10
Name=APP
DeviceId=18
StartSector=11392
NumSectors=196608
BytesPerSector=4096
PartitionId=11
Name=CAC
DeviceId=18
StartSector=208000
NumSectors=109568
BytesPerSector=4096
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
PartitionId=13
Name=USP
DeviceId=18
StartSector=318080
NumSectors=208896
BytesPerSector=4096
PartitionId=14
Name=PER
DeviceId=18
StartSector=526976
NumSectors=1280
BytesPerSector=4096
PartitionId=15
Name=YTU
DeviceId=18
StartSector=528256
NumSectors=128
BytesPerSector=4096
PartitionId=16
Name=CRA
DeviceId=18
StartSector=528384
NumSectors=1280
BytesPerSector=4096
PartitionId=17
Name=UDA
DeviceId=18
StartSector=529664
NumSectors=7231104
BytesPerSector=4096
PartitionId=18
Name=GPT
DeviceId=18
StartSector=7760768
NumSectors=128
BytesPerSector=4096
So... Now it claims to have flashed bricksafe. Will reboot and report back
Code:
C:\Users\Owner\Downloads\BACKUPS\ANDROID BACKUPS>nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
Nvflash started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully
No dice
Hi to all
First of all, thansk a lot for all hard job done for the all entire XDA Team. You helped us so much!
Well, I 'm starting into the world of TWRP, Custom ROM, CM, etc. All because I have a Tablet Genesis GT1440 that after a Update, (gt1440_update.img, 392MB) my tablet get two data partitions: One with 0.99GB and another with 2,09GB (no SDCard installed, just the Internal Memory).
And reading how to fix it, I got the page about the Unpacking/Repacking tool imgRepacker.exe
With that, I unpacking the rom I mentioned above and found a lot of files, but one called sys_partition.fex maybe solve my problem.
So I need some help to find out if is possible to edit this and solve the problem if the data partition. This is the file:
;---------------------------------------------------------------------------------------------------------
; 说明： 脚本中的字符串区分大小写，用户可以修改"="后面的数值，但是不要修改前面的字符串
;---------------------------------------------------------------------------------------------------------
;--------------------------------------------------------------------------------------------------
; 固件下载参数配置
;--------------------------------------------------------------------------------------------------
;****************************************************
; mbr的大小, 以Kbyte为单位
;****************************************************
[mbr]
size = 16384
;********************************************************************************************************
; 分区配置
;
;
; partition 定义范例:
; [partition] ; //表示是一个分区
; name = USERFS2 ; //分区名称
; size = 16384 ; //分区大小 单位: 扇区.分区表示个数最多2^31 * 512 = 2T
; downloadfile = "123.fex" ; //下载文件的路径和名称，可以使用相对路径，相对是指相对于image.cfg文件所在分区。也可以使用绝对路径
; keydata = 1 ; //私有数据分区，重新量产数据将不丢失
; encrypt = 1 ; //采用加密方式烧录，将提供数据加密，但损失烧录速度
; user_type = ? ; //私有用法
; verify = 1 ; //要求量产完成后校验是否正确
;
; 注：1、name唯一, 不允许同名
; 2、name最大12个字符
; 3、size = 0, 将创建一个无大小的空分区
; 4、为了安全和效率考虑，分区大小最好保证为16M字节的整数倍
;********************************************************************************************************
[partition_start]
;------------------------------>mmcblk0p2/nanda
[partition]
name = bootloader
size = 32768
downloadfile = "bootloader.fex"
;------------------------------>mmcblk0p5/nandb
[partition]
name = env
size = 32768
downloadfile = "env.fex"
;------------------------------>mmcblk0p6/nandc
[partition]
name = boot
size = 32768
downloadfile = "boot.fex"
;------------------------------>mmcblk0p7/nandd
[partition]
name = system
size = 1572864
downloadfile = "system.fex"
user_type = 0x2
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 2097152
user_type = 0x2
;------------------------------>mmcblk0p9/nandf
[partition]
name = misc
size = 32768
;------------------------------>mmcblk0p10/nandg
[partition]
name = recovery
size = 65536
downloadfile = "recovery.fex"
;------------------------------>mmcblk0p11/nandh
[partition]
name = cache
size = 1048576
user_type = 0x2
;------------------------------>nandi, data image backup
[partition]
name = databk
size = 262144
;------------------------------>nandj, private data
[partition]
name = private
size = 32768
keydata = 1
;------------------------------>nandk, UDISK
[partition]
name = UDISK
downloadfile = "diskfs.fex"
verify = 0
So, I think if I correct this file with the corretcs values for data partition, may solve the problem.... or maybe the case is not so simple as I think.... But I am here to try it.
The Tablet is a Genesis GT-1440, with a Allwinner A31 chipset
Regards and thanks a lot for any help
Hello and thank you for using XDA Assist,
please create an account and ask in our Android Q&A section. The expert's there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist