Results 1 to 2 of 2

Thread: AC100-10T Restore Android 2.2

  1. #1
    Member
    Join Date
    Jan 2014
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    AC100-10T Restore Android 2.2

    Hello,

    I am new to flashing AC100, I flashed only my HTC wildfire S with custom roms so far (using adb and CWMrecovery)... So I don't know what to do exactly (nvidia), I am sorry if I ask simple/stupid question.

    I got a Toshiba AC100-10T, per label info this ac100 have configuration: T250/512/8GB/10.1WSVT/B/W/3G (owner also mentioned that it have gsm modem). The owner of ac100 wanted me to restore back Android - someone for him some time ago installed ubuntu but he want now back android so...

    I did some digging...
    I know AC100 is based on Tegra 2 Harmony (harmony fastboot), also I found information about partition table and sizes. I managed manually dump partitions (ID=2..14).

    Image files sizes that I dumped:
    Code:
    total 7815200
    -rw-r--r-- 1 saper saper    3145728 Jan 18 15:25 part-02.img
    -rw-r--r-- 1 saper saper     524288 Jan 18 15:25 part-03.img
    -rw-r--r-- 1 saper saper    2097152 Jan 18 15:26 part-04.img
    -rw-r--r-- 1 saper saper    5242880 Jan 18 15:26 part-05.img
    -rw-r--r-- 1 saper saper    8388608 Jan 18 15:26 part-06.img
    -rw-r--r-- 1 root  root     1048576 Jan 18 15:29 part-07.img
    -rw-r--r-- 1 root  root   314572800 Jan 18 15:30 part-08.img
    -rw-r--r-- 1 root  root   419430400 Jan 18 15:31 part-09.img
    -rw-r--r-- 1 root  root     2097152 Jan 18 15:34 part-10.img
    -rw-r--r-- 1 root  root      524288 Jan 18 15:34 part-11.img
    -rw-r--r-- 1 root  root  1294991360 Jan 18 15:38 part-12.img
    -rw-r--r-- 1 root  root      524288 Jan 18 15:38 part-13.img
    -rw-r--r-- 1 root  root  5950144512 Jan 18 15:55 part-14.img
    Dumped images sha1 sums:
    Code:
    d5a08985b10b33c17e76bbfcb7937e49  part-02.img
    90b289a35b2e9c084009a06f9ce393c1  part-03.img
    d9641221f30d02e489c2e96eb1624f63  part-04.img
    68e78020d24724c12f3118595ee04a4c  part-05.img
    74a3aec55cab695a84745617d9edc87e  part-06.img
    67caee2aab1a3fecc5748dc2fb6c0b98  part-07.img
    550f8aa14dc4a96ca4db2bcfef4e9920  part-08.img
    535fca32ef0b56868bac516f81aab7fc  part-09.img
    26d642736b0c3703bf58f8e438d38074  part-10.img
    75def5a388c98b4b2afd02360722e876  part-11.img
    4d778ae4539635086f63b5c5bf6d36d2  part-12.img
    89f0536128ce6a9c0ad575c4bdcfeebc  part-13.img
    3e7009e7990e7d4b623875a95a6d3caf  part-14.img
    Partition table:
    Code:
    ~$ sudo ./nvflash -r --getpartitiontable parttbl.txt
    Nvflash started
    [resume mode]
    Succesfully updated partition table information to parttbl.txt
    ~$ cat parttbl.txt
    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=1024
    BytesPerSector=2048
    
    
    PartitionId=5
    Name=SOS
    DeviceId=18
    StartSector=2816
    NumSectors=2560
    BytesPerSector=2048
    
    
    PartitionId=6
    Name=LNX
    DeviceId=18
    StartSector=5376
    NumSectors=4096
    BytesPerSector=2048
    
    
    PartitionId=7
    Name=MBR
    DeviceId=18
    StartSector=9472
    NumSectors=512
    BytesPerSector=2048
    
    
    PartitionId=8
    Name=APP
    DeviceId=18
    StartSector=9984
    NumSectors=153600
    BytesPerSector=2048
    
    
    PartitionId=9
    Name=CAC
    DeviceId=18
    StartSector=163584
    NumSectors=204800
    BytesPerSector=2048
    
    
    PartitionId=10
    Name=MSC
    DeviceId=18
    StartSector=368384
    NumSectors=1024
    BytesPerSector=2048
    
    
    PartitionId=11
    Name=EM1
    DeviceId=18
    StartSector=369408
    NumSectors=256
    BytesPerSector=2048
    
    
    PartitionId=12
    Name=UDA
    DeviceId=18
    StartSector=369664
    NumSectors=632320
    BytesPerSector=2048
    
    
    PartitionId=13
    Name=EM2
    DeviceId=18
    StartSector=1001984
    NumSectors=256
    BytesPerSector=2048
    
    
    PartitionId=14
    Name=UDB
    DeviceId=18
    StartSector=1002240
    NumSectors=2905344
    BytesPerSector=2048
    I have compared this layout with partition layout on non-existing any more web site http://tosh-ac100.wetpaint.com/page/Partition+Layout (can be still found via web.archive.org ).

    Partition layout from page: tosh-ac100.wetpaint.com - for 8GB AC100:
    Code:
    http://web.archive.org/web/20120608030734/http://tosh-ac100.wetpaint.com/page/Partition+Layout
    -----------------------------
    Partition Layout
    The original partition layout on a 10V device (read out by nvflash --getpartitiontable) looks like this:
    
    part #    name          size                description remarks
         2    BCT         3 145 728 (3 MB)        boot config table    
         3    PT            524 288 (512 kB)      partition table    
         4    EBT         2 097 152 (2 MB)        bootloader    
         5    SOS         5 242 880 (5 MB)        recovery partition    
         6    LNX         8 388 608 (8 MB)        linux kernel and initrd    kernel starts at 0x800 initrd starts at 0x20E800
         7    MBR         1 048 576 (1 MB)        master boot record    
         8    APP       314 572 800 (300 MB)      applications (/system)    
         9    CAC       419 430 400 (400 MB)      cache (/cache)    
        10    MSC         2 097 152 (2 MB)        misc (/misc)    
        11    EM1           524 288 (512 kB)    
        12    UBA     1 294 991 360 (1235 MB)     user data (/data)    
        13    EM2           524 288 (512 kB)    
        14    UDB     5 950 144 512 (5674.5 MB)   user data (/storage)
    This is for lazy bums (like me )

    So after I have created partition images, next I started looking for original android 2.2 images... I found page/ftp: Index of /firmware/2.2 (2.2.5.029) , and download all files:

    Code:
    ~$ ls
    total 71616
    -rwxr--r-- 1 saper saper 42270720 Feb  3 19:51 AC100_Froyo_2.2.5.029_root_8.zip
    -rwxr--r-- 1 saper saper   524288 Feb  3 19:50 AC100_Froyo_2.2.5.029_root_8.zip.1
    -rwxr--r-- 1 saper saper   393216 Feb  3 19:50 AC100_Froyo_2.2.5.029_root_8.zip.2
    -rwxr--r-- 1 saper saper  2097152 Feb  3 19:47 froyo_10.img
    -rwxr--r-- 1 saper saper   524288 Feb  3 19:47 froyo_11.img
    -rwxr--r-- 1 saper saper   524288 Feb  3 19:47 froyo_13.img
    -rwxr--r-- 1 saper saper  3145728 Feb  3 19:47 froyo_2.img
    -rwxr--r-- 1 saper saper   524288 Feb  3 19:47 froyo_3.img
    -rwxr--r-- 1 saper saper  2097152 Feb  3 19:48 froyo_4.img
    -rwxr--r-- 1 saper saper  5242880 Feb  3 19:49 froyo_5.img
    -rwxr--r-- 1 saper saper  8388608 Feb  3 19:49 froyo_6.img
    -rwxr--r-- 1 saper saper  1048576 Feb  3 19:49 froyo_7.img
    -rwxr--r-- 1 saper saper  6553600 Feb  3 19:49 froyo_8.img
    Now what to do with them?
    Q1: Files froyo 2..7,10,11,13 - flash them with matching partition data (startSector, numsectors - from partition table) - right?
    Q2: froyo_8 have different size: 6,5MiB on FTP, my - 300MiB - what to do ? (flash -> but NumSectors won't match )
    Q3: What to do with missing partition images (9,12,14) - or what to do with partitions? I think I need them to format but how? (nvflash -r --format_partition [PartitionId] ; will be ok? Android will rebuild file structure on it's own?)
    Q4: What about files AC100_Froyo_2.2.5.029_root_8.zip , AC100_Froyo_2.2.5.029_root_8.zip.1 , AC100_Froyo_2.2.5.029_root_8.zip.2 ?

    Sorry for my stupid questions but I don't want to brick this AC100 because it's not my own, so I would be grateful for help. And I am sorry for my English.
    I found a pieces of info on this forum but I can't get whole picture how to flash back android to ac100, and there is no answers for my questions too...

    If I success then I will write guide (step-by-step) how to do it for future reference

  2. #2
    Member
    Join Date
    Jan 2014
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    [SOLVED] [GUIDE] Flash Android 2.2 after Linux (Ubuntu)

    Hello,

    I have managed to restore on that AC100 Android 2.2.

    First: those files I download at beginning - I not used them, there is missing partition 9 and 12.

    I downloaded images from Index of /from_torrents/images/2.2
    Those works but there is no Play Store (Android Market).

    Anyway what I do:

    1. Boot AC100 into recovery: Ctrl+Esc + Power
    2. Load to RAM bootloader:
    Code:
    ac100/nvflash# nvflash --bl harmony/fastboot.bin --sync
    3. Go to where you have downloaded images and for partition form 5 to 13 run command ( [num] replace with partition number 5..13):
    Code:
    ac100/flash-images/froyo# nvflash -r --download [num] tac100-part-[num].img
    4. If you had linux on 14th partition then you have like in my case different file system on that partition. So after AC100 boot into android, connect it to PC running with windows and format drive (windows detects AC100 as removable drive) to FAT32 that will show up.
    5. Hookup AC100 on wifi and download update via Toshiba Service station.

    So that's all - now this is extremely simple for me

    Also I wanted to write some thanks for stuw_ from irc channel #ac100 @ chat.freenode.net for help and giving me confidence in flashing
    THANKS stuw_!!!!!!!!!!!

    For installing Android Market/Play Store I found this topic on xda-developer: [Q] Toshiba AC100 and Android Market - xda-developers from what I saw on few first pages, looks like you need to root your AC100 then install manually files from gapps (google apps) package.


    [!close]

Remove Ads

Similar Threads

  1. Replies: 325
    Last Post: 04-25-2016, 04:30 AM
  2. Replies: 100
    Last Post: 11-19-2013, 05:19 AM
  3. Replies: 104
    Last Post: 02-20-2012, 03:42 AM
  4. Replies: 12
    Last Post: 02-08-2012, 09:17 AM
  5. Replies: 223
    Last Post: 02-01-2012, 12:12 PM

Search tags for this page

ac-100 nvflash windows
,
ac100 toshiba play store
,

android 2.2 update toshiba ac100

,
download android 2.2 toshiba ac100
,
flash ac100 bootloader
,
googleplay in toshiba android ac100
,
installer google play store android2,2 pour toshiba ac100
,
sos-uboot ac100
,

toshiba ac100 android 4.0 download

,
toshiba ac100 cwm sos uboot recovery
Click on a term to search for related topics.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •