yashsingh1/xdaforums huggingface dataset:
[Folio 100 General] pereiks:
Great, at least now my dead folio makes vibration after unsuccessfull update ;p

Something went wrong, i'm a little busy now, will try to fix it later.

nvflash.exe --bct folio.bct --setbct --bl bootloader.bin --configfi

le flash.cfg --odmdata 0x000c0075 --create --go

Nvflash started

rcm version 0X20001

System Information:

chip name: t20

chip id: 0x20 major: 1 minor: 2

chip sku: 0x8

chip uid: 0x161c10c742e0d2d7

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

sending file: folio.bct

- 4080/4080 bytes sent

folio.bct sent successfully

odm data: 0xc0075

downloading bootloader -- load address: 0x108000 entry point: 0x108000

sending file: bootloader.bin

/ 2097152/2097152 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize

bootloader downloaded successfully

setting device: 1 0

creating partition: BCT

failed executing command 16 NvError 0x120002

command failure: create failed (bad data)

bootloader status: specified device is not the boot device (code: 17) message: n

verror:0x4 (0x4) flags: 0

Press enter to continue:
[Folio 100 General] DerArtem:
Can you post your flash.cfg file?
[Folio 100 General] Dexter_nlb:
this part already looks better than the one i did.. you got at least it to start a bootloader.. the red part never appeared on mine :-)

im sure DerArtem might be able to deliver you the missing data, so you can rebuild, and the end result is we all get access to APX mode..

sad part is it deletes everything all the time, not sure i will go into APX often due to that..
[Folio 100 General] pereiks:
Looked at flash.cfg - looks like it is totally wrong...

I took all the files from the link that Dexter provided in his previous message.
[Folio 100 General] DerArtem:
Hi,

I have recreated the flash-configuration. Please try out the attached file. (Rename it to folio.cfg).

If this does not work try renaming the bootloader.bin to fastboot.bin as this name is referenced in the flash-config...

It may also be possible that we have to change the first three line in the config, as I don't know if the values are correct.

[device]

type=hsmmc

instance=3
[Folio 100 General] pereiks:
now the problem is that fastboot.bin cannot bee copied:

sending file: bootloader.bin

/ 2097152/2097152 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize

bootloader downloaded successfully

setting device: 2 3

creating partition: BCT

creating partition: PT

creating partition: EBT

failed executing command 16 NvError 0x120002

command failure: create failed (bad data)

bootloader status: BCT is full; no more bootloaders can be added (code: 16) mess

age: nverror:0x4 (0x4) flags: 0

Press enter to continue:

UPD: If i remove the EBT partition from the config file - everything finish successfully, but no more progress.

downloading bootloader -- load address: 0x108000 entry point: 0x108000

sending file: bootloader.bin

/ 2097152/2097152 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize

bootloader downloaded successfully

setting device: 2 3

creating partition: BCT

creating partition: PT

creating partition: MBR

creating partition: APP

creating partition: CAC

creating partition: MSC

creating partition: ER1

creating partition: LNX

creating partition: ER2

creating partition: UDA

creating partition: ER3

creating partition: SOS

creating partition: ER4

creating partition: DAT

Formatting partition 2 BCT please wait.. done!

Formatting partition 3 PT please wait.. done!

Formatting partition 5 MBR please wait.. done!

Formatting partition 6 APP please wait.. done!

Formatting partition 7 CAC please wait.. done!

Formatting partition 8 MSC please wait.. done!

Formatting partition 9 ER1 please wait.. done!

Formatting partition 10 LNX please wait.. done!

Formatting partition 11 ER2 please wait.. done!

Formatting partition 12 UDA please wait.. done!

Formatting partition 13 ER3 please wait.. done!

Formatting partition 14 SOS please wait.. done!

Formatting partition 15 ER4 please wait.. done!

Formatting partition 16 DAT please wait.. done!

done!

Press enter to continue:

Folio displays on its LCD this message: "Unrecoverable Bootloader error (0x00000004)"

UPD2:

wow, after changing the id's to 1,2,3 from 2,3,4 i managed to load everything. And after reboot it even showed up the toshiba logo ;p

But after it writes down Magic Value Mismatch error

UPD3:

Recovery menu is working but after i select system update - it shows up Magic value mismatch error. Looks like the problem is that the partitions is empty. NOw i need img's of other partitions, we can add them to cfg file and all will work fine. Looks like the solution is found at last.
[Folio 100 General] Dexter_nlb:
REAL NICE!!!

it sounds like we're getting close to have opened our folio just like all others has...

you just hit gold!!!

no more bricked folio's!! and maybe even fix stupid bootloader, so the keycombo goes away.

can it be you need to change partition order? once more?

below is the original factory setup of folio100 (i think is close to correct, DerArtem knows better)

bct....

loader:300:400:800

mbr:700:200:800

system:900:20000:800

userdata:a1f00:80000:800

misc:a0900:400:800

...4....

linux:a0e00:1000:800

cache:20900:80000:800

recovery:122000:a00:800

....8.... /storage partition
[Folio 100 General] pereiks:
No, i think it just a problem that recovery partition is empty. I need img's for partitions.

Also i think 16 partitions is too much - there are too many unused data partitions that should be removed.
[Folio 100 General] Dexter_nlb:
is it my recovery? then you can check partitions are ok with adb?
[Folio 100 General] Dexter_nlb:
download the foliomod there you got boot,recovery,system partitions

AC100 has guides on how to download partition from nvflash..

i guess you seen those..

in your list SOS is not at part7, which will make any update.zip fail, as the updates points to specific partitions i think.

not sure how the update-binary will see the SOS partition or APP, so maybe it works with recent updater's
[Folio 100 General] Dexter_nlb:
download this update for Advent Vega, they release their updates as complete nvflash images with all needed to do it on windows.

get it here

it contains all needed to do a full nvflash, so you just replace with folio files needed, and we got a full recovery solution for bricked devices..
[Folio 100 General] pereiks:
downloading now...
[Folio 100 General] DerArtem:
Yes, I think that you have to reflash the recovery.img using nvflash on partition 14.

I have build the partitions list based on the data I have found on the internal sdmmc. So all of them exist on the Folio. You, are right. Many of them are unused, but they still exists...

I have build the partitions list based on the data I have found on the internal sdmmc. What you are showing are the values of the kernel options. The kernel also can only see partition that are referenced in the MBR.

So the internal sdmmc has much more partitions on it that the kernel can see...
[Folio 100 General] Dexter_nlb:
i'm personally hoping for your success here :-)

so lets you can create a full functioning recovery from a bricked folio.. and it also makes it alot easier to redesign partition if needed :-)
[Folio 100 General] DerArtem:
If I understand everything correctly then the flashing out from recovery happends by partition names and not by ID's...
[Folio 100 General] Dexter_nlb:
sure, it was just meant as reference to which partition was used for what..

if he succeed , i think it can be designed in whatever manner we like except recovery and boot might need different pointers in init.rc..
[Folio 100 General] pereiks:
Artem, can you dump all the partitions for me, except user data of course.

And i had to increase the BCT partition size in your config, because bootloader failed to be uploaded.

Dexter, config file from your link is not works at all - seems they are using very different configuration
[Folio 100 General] Dexter_nlb:
yes, i know.. i just meant you could make a full image based on this release, when the exe file is unpacked, you put all files together, with the modified ones you make for our folio100 and we got a full recovery..

you should not flash it :-) just use a method to create a working recovery image, for those with a bricked folio, when you have a fully working setup.

so you can share your final image and the knowledge you gained and make folio even safer to use now..

so its just a reference, you takes files inside the zip'd (exe) and that was my idea.
[Folio 100 General] pereiks:
I misunderstood you , thought you are talking about taking cfg file from that release.

The current situation is that normal boot and recovery image isn't loading at all. No info is displayed on LCD. If i connect usb ot it - the folio is recognized as Toshiba storage USB device. Looks like i got expensive card reader now ;p
[Folio 100 General] Dexter_nlb:
well, if your paritions are not matching a normal stock , you dont have system at 1 and data,misc,cache in the right locations..

so it will not boot... if you write the recovery from foliomod, you get full adb working, so boot into recovery and use adb to check if all partition are there and that recovery mounted a system,data,cache folder..

you're close :-) don't give up..
[Folio 100 General] pereiks:
adb not detecting a device ;( I'll continue tomorrow, it's almost 2am, time for a rest...
[Folio 100 General] Dexter_nlb:
sounds like you got a wrong recovery partition loaded? (especially if you do see the menu? i guess ill modify the menu so it shows "foliomod")
[Folio 100 General] DerArtem:
Hi,

this is exactly the problem. Do NOT modify the partition sizes in the config! Otherwise all partitions will move to a wrong location.

I have attached a smaller version of the bootloader. Please try using this one.

The real bootloader is much smaller. I have just dumped the whole bootloader partition - which is filled with zeroes after the end of the bootloader....

Can you try flashing the recovery.iso from folio mod?

I will dump the partitions tomorrow again, if you can not flash the recovery.iso.
[Folio 100 General] DerArtem:
How did you get into recovery? Have you flashed the recovery.iso?
[Folio 100 General] Dexter_nlb:
good thing my recovery is 100% self contained, regular adb needs /system to work :-)

but anyways its progress, so at least something loads but again, i noticed too that partition table was wrong..it needs to be like stock image for anything to load.
[Folio 100 General] pereiks:
I thought maybe someone can make a full copy of entire mmc like dd if=/dev/block/mmcblk0 so i can write down full disk without need of creating partitions from nvflash.

Just to be sure that folio can be restored ;) After that we can experiment with nvflash
[Folio 100 General] Dexter_nlb:
if you got fastboot, bct/mbr , boot,recovery, system

misc is not used as i know, but yes its mounted, but not important.

you just need to be a WIPE in recovery to format data/cache partittions.

the img files in foliomod is exactly the same if dumped with nvflash.
[Folio 100 General] pereiks:
i mean full dump, not per partition, so i could write directly to /dev/mmcblk0

It will recreate the partition table and fill all the partitions with right data.

You can make it like this (from the adb shell):

dd bs=64k if=/dev/block/mmcblk0 of=/sdcard/full.img

It will also copy your private data, so better to do it on a clean folio.
[Folio 100 General] Dexter_nlb:
but there is no difference? you got the BCT/MBR from DerArtem, you got partitions to format, and you got the foliomod with needed partitions to boot?
[Folio 100 General] pereiks:
Tried to dd the beginning of SD dump (that DerArtem provided) - no chance, the partition table is still wrong.
[Folio 100 General] Dexter_nlb:
you should try and do a ls -l /dev/block/mmcblk0*

if you still got p0 -> p8 your right on track, but partitions need the proper data.. the errors you report is just defective filesystem not missing partitions.

the BCT file is equal to the MBR that some people used to repair their partition table. its available on the wiki page. when this is written to mmcblk0 you got a proper partition list from stock rom.. you will need to reboot for the changes to be seen. i think BCT part in nvflash needs to be 4080 bytes, but for the MBR part its only 1024 bytes..
[Folio 100 General] DerArtem:
On the Tohiba AC100 the MBR partition is generated on the fly on every boot.

I am stil wondering how you got into recovery mode? Have you flashed the recovery.iso, or did the recovery just worked?

When you turn on your folio, do you see the bootloader on the screen asking you for Press Vol + and Power and stuff like that?

Do you entering recovery by Vol + and Power and then following the menu to install an Update?
[Folio 100 General] pereiks:
Yes, i added system.img, boot.img and recovery.img to the nvflash config (img's from the foliomod update.zip).

On power-on i see toshiba standard bootloader, press power + vol+ , choose system update.

Of course it kicks me out to recovery menu, because it cannot find update.zip on sd card.

In that moment i can use adb shell.
[Folio 100 General] DerArtem:
Ok, I got it!

You can not write the full flash from the recovery. When booting the standard kernel with the standard kernel parameters (which you did, as you are in the recovery now) the kernel won't see anything on the internal sdmmc prior the MBR. (The mmcblk0 just starts at the MBR due to the kernel parameters.)

What you can do is repacking the recovery.iso:

You must remove the tegrapart= parameter from the kernel arguments list. Only then the kernel will see the full sdmmc and you can dd my dump over it.

I can repack the recovery.iso for you today afternoon, or you can do this by yourself :)

Here is how to repack system images:

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

You cat get the current boot-parameters by "cat /proc/cmdline". And don't forget to escape special characters when setting up the --cmdline parameter.
[Folio 100 General] pereiks:
Created new recovery image:

sh-4.1# cat /proc/cmdline

mem=192M@0M nvmem=320M@192M vmalloc=448M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc boardtype=PR

Then

sh-4.1# dd if=/tmp/sdmmc.dump of=/dev/block/mmcblk0

20480+0 records in

20480+0 records out

Now it prints me "Magic Value Mismatch"

I think i will need full img of the entire disk
[Folio 100 General] DerArtem:
Ok, I will crete a full dump today afternoon.
[Folio 100 General] DerArtem:
I have send you a PM with the download link.
[Folio 100 General] pereiks:
Found out that dd isn't compiled with large file support. I will try to trim your file to 500mb - that should be enough.

UPD: Still magic value mismatch
[Folio 100 General] DerArtem:
You can also try

cat image.dump > /dev/block...

Update:

Try to restore more. There still important filesystems till ~3 GB.... (see partition list in some posts before)
[Folio 100 General] Dexter_nlb:
is this helping?

seems the guys with viewsonic tab's also experience that issue sometimes, i found other hits in viewsonic threads on it.

so if the boot img partition is empty you get the "magic value" problem?

so the bootloader maybe points to specific partition and not using names? which problably not correct, but if so , it finds no boot.img partition and you get the error?
[Folio 100 General] pereiks:
Do you think cat is compiled with large file support? If not, then i won't be able to use it with file larger than 2Gb.

Uploading your dump to sdcard now....

UPD:

Ok, uploaded first 4gb's of your dump. Partition table is ok, but system haven't started(or i haven't waited long enough). Made an update with foliomod's update.zip, and at last android booted ok.

Thanx all - now we have a working solution. Now lets try to fix flash.cfg so there will be no need to cat the 4gb img to internal flash.
[Folio 100 General] Dexter_nlb:
for me it sounds like you changed the mmcblk structure data only after you recovery from a nvflash setup?

so somehow some data in the nvflash process is causing the issue.
[Folio 100 General] DerArtem:
This are really great news! Now we can repair bricked devices ;D
[Folio 100 General] pereiks:
Looks like some partition infformation is missing after nvflash. For example - we only filling up first 3 system partitions and boot, Recovery and system partitions. But there is also extended partition and we don't upload any information about it except creating its child partitions
[Folio 100 General] Dexter_nlb:
true, im think you could have used the wiki solution with the 1024 byte dump of mmcblk0 from my device, which would build the MBR and you should have all partitions back.. some ppl had the issue, with just 1 partition available, they used it and had all partitions back..

in your case, you would still need boot/recovery and a wipe in recovery and it should have been close to ready i think.
[Folio 100 General] kiemthanh:
HELP

i use the file for you by my folion but my folion dont power on .you have give me you file by start you folion . thank
[Folio 100 General] kiemthanh:
Help help help

My set the same your set when I downloaded your file(softwareImage_v1.02_Vega_Final.exe).But when i this run only stop here "waiting the bootloader to initialize". Please send your file that you run successfull for your toshiba folion !!!!!!!! Thank!!!!!!!!!!!
[Folio 100 General] Dexter_nlb:
this is files i got from DerArtem, hope it helps.
[Folio 100 General] kiemthanh:
Help me

i do not run this file. Can you guide details for me.

Thanks.
[Folio 100 General] kiemthanh:
Too long for wait processing !!! help me !

I have used this file but this process stopped at this command as follow :

C:\DOCUME~1\Admin\LOCALS~1\Temp>nvflash.exe --bct flash.bct --setbct --bl bootlo

ader.bin --configfile flash.cfg --odmdata 0x000c0075 --create --go

Nvflash started

rcm version 0X20001

System Information:

chip name: t20

chip id: 0x20 major: 1 minor: 2

chip sku: 0x8

chip uid: 0x161c10c941df9117

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

sending file: flash.bct

- 4080/4080 bytes sent

flash.bct sent successfully

odm data: 0xc0075

downloading bootloader -- load address: 0x108000 entry point: 0x108000

sending file: bootloader.bin

- 1091568/1091568 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize......

I have waited one hour but this still not continue.

How long hdid you wait this process ?

Pls confirm me ASAP , thank you .:)
[Folio 100 General] Dexter_nlb:
I dont know, sorry.. never tried this...
[Folio 100 General] Dexter_nlb:
instantly , no waiting then its wrong..
[Folio 100 General] Mr. Clown:
Hi, can you please stop posting the same thing. Help will come along hopefuly. You need to have some patience.

Cheers,
[Folio 100 General] kiemthanh:
please

help me step by step
[Folio 100 General] kiemthanh:
help me step by step

help me step by step
[Folio 100 General] vranikx:
Hi, could you please send me a link by PM? I can`t find it there :/
[Folio 100 General] Miraculix666:
Solution?!

Hi,

is there a Solution by now? could't find it.

Some help would be nice!!!

Greets...
[Folio 100 General] DerArtem:
Hi,

we have restored one folio, but we have no complete howto.

What problem do you have?
[Folio 100 General] Miraculix666:
nvram accidently deleted.

power on -> powerLED is white, softbuttons light up if they are touched. APX device on USB connection in Win.

I alredy have nvflash but I need the Instructions / Files

thx
[Folio 100 General] Miraculix666:
I tried some files / commands posted here, but no succes until now.

Which are the right ones?
[Folio 100 General] puppet13th:
this is working nvflash for Toshiba Folio 100

this will bring life for bricked Toshiba Folio 100(in APX mode)

may be this can be reference to create a working solution for full system recovery

!!! Warning !!!

this will not make your device back to usable state

Working :

- bootloader (toshiba logo)

- fastboot

- working boot and recovery if flashed from nvflash or fastboot

still confusing : partition table layout

we need manualy made parition table using fdisk command from cwm recovery

i have made script for creating partition on /dev/block/mmcblk0 using parameter found on part.txt

the partition table still need to be adjusted

files :

folio.bct	- downloaded from xda

new.bct	- downloaded form my folio 1000 (don't know if it's the right bct)

bootloader.bin	- downloaded from xda

folio100.xls	- my summary about partition table on folio 100 and ac100

env.cmd	- start command prompt with adb,fastboot and nvflash support

flash.cfg	- i created this config file based on my summary

part.txt	- fdisk partition parameter

part-table.txt	- partition table after created

NVFlash.txt	- nvflash documentation

cwm-fdisk.cmd	- make partition table using adb shell on CWM Recovery mode

need to download recovery.img for working nvflash script

http://xdaforums.com/showthread.php?t=923722

http://xdaforums.com/showthread.php?t=1065009

in flash.cfg i have place recovery.img as image for linux and recovery,after fresh flash from nvflash the device should booting to recovery

Hacking the Toshiba AC100

http://tosh-ac100.wetpaint.com/

download : nvflash-folio100.zip

APX recovery mode : on toshiba logo press power 4x + vol-

fastboot mode : on toshiba logo press power 3x + vol-
[Folio 100 General] puppet13th:
i have made fully working NVFlash solution check this thread

Folio 100 Fully working NVFlash
[HD2 Windows Mobile 6.5 Themes and Apps] kuzibri:
Hi,

I.ve used CHT now for many, many months, and I'm due/into to a change for my homescreen. Is there a good alternative for CHT at this very moment? If not, I will stay on CHT, no prob at all because it's functioning very well (that is to say the 1.8.5.1 vesion - CHT 2 beta gives too much problems at this moment in combination with Artemis ROM), just a question.

regards, Kuzibri
[HD2 Windows Mobile 6.5 Themes and Apps] Symondo:
I'd just hold on until CHT2 final is released - alongside CHTS its about as versatile as you could ever need it to be
[HD2 Windows Mobile 6.5 Themes and Apps] kuzibri:
Thanks Symondo, I will wait for the finale release of CHT2!!

regards, Kuzibri
[HD2 Windows Mobile 6.5 Themes and Apps] huismeester:
Yes but the question is when?
[HD2 Windows Mobile 6.5 Themes and Apps] kurt-willems:
Co0cie is back in town, and working hardly.

It's a small matter of time.
[HD2 Windows Mobile 6.5 Themes and Apps] Dic3ptor:
HI all

For me i can say CHT 2.0 Beta works great on Artemis V41. Some little bugs but i can live with!

But i hope that Cookie will release the Final version soon.
[HD2 Windows Mobile 6.5 Themes and Apps] conantroutman:
CHTS has been made final so I would guess that CHT wont be too far behind.....

:D

Saying that, Im not even sure I'll update because the beta has been SO stable for so long........

ahh who am I kidding of course I'll update......:p
[HD2 Android Q&A, Help & Troubleshooting and Genera] dwatson85:
I have installed android froyo onto my (TMOUS) HTC HD2 and I have little to NO 3G signal. It will switch from H to 3G to Egde constantly with no bars for signal.

Do I need to change the signal radio? PLEASE HELP!

Currently using...

RADIO - 2.12.50.02_2

MOD VERSION - darkstone HD2Froyo V3
[HD2 Android Q&A, Help & Troubleshooting and Genera] yksudha:
It's a known issue and I am afraid no has found a fix yet
[HD2 Android Q&A, Help & Troubleshooting and Genera] onelftstanding:
also having a problem with this build. no 3g service practically anywhere. it doesnt show the switching bars or signal type but i can not use opera facebook or any other app that is data intensive. other than this it is a very smooth very functioning build.
[Hero, G2 Touch Android Development] LlabTooFeR:
Here latest RUU for Hero TW

http://www.multiupload.com/VB6BK201BL

Enjoy!
[Hero, G2 Touch Android Development] Krizp0:
What's new here? It's still 2.1, right?