Database Info

Bricked gtab?

I think its done for but I want to be sure. I've used nvflash many times to revert to stock but this time I tried the format rom (http://forum.xda-developers.com/showthread.php?t=974422) just before I tried to revert.
So far I've tried flashing with nvflash following the directions here (http://forum.xda-developers.com/showthread.php?t=861950) using the 1105 and the 1126 images. The format rom still completes but the stock rom gives the following output.
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714400940ffc357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 3407872/33554432 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Press enter to continue:
I've tried to use nvflash to get CM .8 back but nothing seems to work. I hope someone has an idea on how to recover from this.
Thanks in advance

ok, I fixed my issue and found a new one.
1. I re-downloaded the format
and the 1126 rom files.
2. I re-ran the format rom.
3. I copied the files from "nvflash_gtablet_46_2010112600.zip" into the same directory as the format rom files and ran the new nvflash_gtablet.bat file.
For some reason this time it worked. I tried this before but for some reason it worked this time.
Once I got in I updated to 3588 using the OTA updater and now it only boots in to APX. Seems others are having the same issue. I'll keep trying to get this resolved but if anyone has some insight into this problem I'd love to hear it.

Well, you probably already know, but for the sake of beginning a new, clean thread-
Using nvflash.exe, you can simply
nvflash.exe --bl bootloader.bin --format_partition 2 --go
And it will reboot your tablet without erasing anything important.
Holding down the volume key will get you into recovery mode as well, if you hold it before you press enter.
Hope we can fix this. Im tired of explaining how i fried something and it wont boot with a computer.

So after many hours of searching the forums and web for different possible solutions, and trying them all, I think I'm going to throw in the towel. Mine is still in the 30 days for a return so I think I'll just return it and get another.
All my issues started when I tried the format rom, so that's one I'll not do again.
Good luck to everyone still fighting to get their gtab to boot out of APX mode.

You might have better luck with the 1105 image. I would give that one more try before you give up. You might also need to reinstall ClockworkMod and repartition your internal sdcard.

When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?

notwen said:
When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?
Click to expand...
Click to collapse
APX mode is like fastboot mode in other devices.
On the gtablet, it is a blank, unlit screen.
It waits for a command from a host device, and once it gets one, the screen lits up black with a single line of text.
Its as if the unit doesnt power up, but it really does. The only way to tell is to have it plugged up to a computer.
I mean, you can use nvflash to boot it.
And i will try the 1105 image in the next 24 hours and report if it got the device to boot independently.

[Q] nvflash_gtablet, cannot start

After running sh ./nvflash_gtablet.sh I get this message
Flashing G Tablet with base images...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188423f3217
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. /usb read error (71): Protocol error
done!
failed executing command 14 NvError 0x8
command failure: create failed
Done!
Please help, what do I do next!
Thanks
hguled

hguled said:
After running sh ./nvflash_gtablet.sh I get this message
Flashing G Tablet with base images...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188423f3217
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. /usb read error (71): Protocol error
done!
failed executing command 14 NvError 0x8
command failure: create failed
Done!
Please help, what do I do next!
Thanks
hguled
Click to expand...
Click to collapse
try using the other recovery , the one named nvflash_gtablet_2010110500

nvflash_gtablet_2010110500 Failing
I downloaded nvflash_gtablet_2010110500.zip from dropbox , after unzip all I get is 'nvflash_gtablet.sh'. I Am downloading a wrong version.
I Appreciate your reply

hguled,
What operating system are you using?
The nvflash_gtablet_2010110500.zip is for Windows.
The file nvflash_linux_2010110500.tar.gz is for Linux.
If you have questions, check out the "NVFlash" STICKY thread near the
start of the Developer forum.

Bricked After NVFlash

Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
F:\nvflashtf>download.bat
F:\nvflashtf>cd F:\Chrome DL\nvflash\nvflashtf\
F:\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --co
nfigfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x168
2CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c6208417fd657
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 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
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
\ 5085184/5085184 bytes sent
recovery.img sent successfully
file not found: boot.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks

I don't think you're supposed to update after you've rooted
I bricked one that way

Hmm, well things seemed to be fine after doing so. It was just the nvflash which finished me off. I'm new to all this.
Any suggestions on getting it back? I have the whole weekend to try now.

Try redownloading the nvflash files? Maybe the checksum failed.
It seems boot.img was not found, but your download.sh script tries to install it.

it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again

lilstevie said:
it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again
Click to expand...
Click to collapse
Thanks! This made a lot of sense after I read it. I downloaded the nvflash edition and ran the download.bat. It found the missing files and copied them to the transformer successfully. I then rebooted the device and was back in action with prime. Appreciate it!

compywiz said:
Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks
Click to expand...
Click to collapse
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.

goodintentions said:
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.
Click to expand...
Click to collapse
Definitely glad. The funny thing is I ran the nvflash because I wanted to see if it worked for getting a clean install, little did I know I would make it cleaner than I wanted :x. I had an idea that I needed to supply the files, but really had no idea where to get them. Luckily lilstevie pointed me in the right direction. I've since updated to Prime HC3.2 and loving it so far.
Glad it's back and working now though!

[Help] Broke Eee Pad Transformer :(

Hi all.
I tried to install rom on my Eee Pad but i failed and my device is broke now
please help me.
that what i did..
- i installed Windows nvflash with APX drivers successfuly
- then i installed SU using Razorclaw_1.0.1.apk successfuly
- then start my device with APX mode with windows 7 on my kaptop
- then i start download.bat from nvflash folder, everything done
but the device just show me .. black screen with message
entering nvflash recvery mode / nv3p server
chip uid : .... some numbers i don't remember
my device info ..
kernal
2.6.36.3
build
HTK75.CN_epad-8.6.5.19-20111107
android
3.2.1
Please any help .. its first day with my Eee Pad Transformer
Thanks

You got an apx bootloop going on there. You need to nvflash your way out of there.

goodintentions said:
You got an apx bootloop going on there. You need to nvflash your way out of there.
Click to expand...
Click to collapse
How?
i know nothing about android at all, some details will help
please

First of all, what's your seriel number?

goodintentions said:
first of all, what's your seriel number?
Click to expand...
Click to collapse
s/n : B70kas151295

This is the log when run download.bat
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 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
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed

Hang on, I'm confused about something. Why did you nvflash after you rooted?

goodintentions said:
Hang on, I'm confused about something. Why did you nvflash after you rooted?
Click to expand...
Click to collapse
i don't have any experiance with that, i did that to access the recovery options
i just tried to install rom from here http://forum.xda-developers.com/showthread.php?t=1245892

Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.

goodintentions said:
Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.
Click to expand...
Click to collapse
sorry i don't know about cwm
i did it, nothing happened
not turned on

CWM/ClockWorkMod is a common recovery tool. It is somewhat like booting into a recovery partiton that allows you to backup/restore using a MicroSD. Also whiping data.
Sent from my Transformer TF101 using Tapatalk

yes.
what should i do to get my device work again?

What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
fadiodeh said:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
What files did you download and from where?

brando56894 said:
What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
What files did you download and from where?
Click to expand...
Click to collapse
Hi,
thanks to reply,
i download this .. http://ff06d07.filefactory.com/dl/f...822c5b18bdf8d2e664f2b163ae76fff/n/nvflash.zip
then i tried to set Prime 1.4 files but i can't find boot.img and recovery.img on it, its just contain one file system.img, i download it from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
i want to install Android Revolution HD from this link http://forum.xda-developers.com/showthread.php?t=1245892
or back to stock os at least .
Thanks

how can i get the correct recovery.img and boot.img files for my device ?

IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
Here's a guide to read: Guide
I'm uploading the stock images for you.
You really should have read some more before you tried this.

brando56894 said:
IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
You really should have read some more before you tried this.
Click to expand...
Click to collapse
i did, but the files in Prime 1.4 is just one file system.img, i can't find recovery.img and boot.img
i got prime 1.4 from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
what should i do ?

I got this ..
ICS Themed Vanilla Release
Prime! v2.1.0
files .. system.img, boot.img and recovery.img
the issue is when start NVflash its disconnected USB automatically,
see the log please ..
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
and
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 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
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed
its not disconnected in specific step, its randomly

its working now with ICS Themed Vanilla Release
after a lot with tries using Brks_rootkit_v7
Thanks a lot for all there
have a great day

You're welcome and glad you got it fixed!

[Q] Problem flashing Elocity A7

Wanted to post this in the elocity section but not taking new threads. I have an elocity A7 (not plus). had it for a few years, always worked great, used
sparingly. from day one had it flashed to dexter's 1.41 rom. never had a problem. it has been sitting for a while
and I decided to break it out. charged it up and booted. nothing but force close errors. nothing really works.
tried to reflash with dexter and also with original rom. both go through the motions but after it reboots it's
exactly the same, no changes made. have gone into privacy menu and did a factory reset. same thing, goes through
the motions but after it reboots it's exactly the same. tried to uninstall programs using app manager. they
apprear to be gone but after a reboot they magically re-appear!! tried to use file manager to delete and same
thing. it's like it write protected or something. I used the elocty "restore from PC" batch file/imager and here
is what I get:
C:\Users\Snake\Documents\A7-restore-from-pc\A7 restore from PC\nvflash_windows_2
.2\image>..\nvflash.exe --bct flash.bct --setbct --configfile android_froyo_fas
tboot_emmc.cfg --create --odmdata 0xC0075 --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x02804145445fa517
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
| 937544/937544 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
creating partition: NVC
creating partition: SOS
creating partition: LNX
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: ER1
creating partition: UDA
creating partition: ER2
creating partition: SDC
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x2 (0x2) flags: 0
so I'm guessing that the "failed" part is the main problem, lol. anyone have ideas? I want get this going in a
big way. My thought after seeing that was the flash ram had gone bad, but it was literally just sitting unused...I
don't see how it could have gone bad from sitting. if it does have bad sectors say, is there any utility like they
have fro hard drives that can map those areas? looking for serious help here from real experts, I think I have
gone though all the basics. Help MUCH appreciated. Thanks in advance