Thought that I had figured this out, but not quite I guess. I'm trying to flash a custom ROM. Running stock a500 with the ICS OTA update. Running Ubuntu 12.10 on my laptop. Didn't realize how difficult this would be. Despite a bunch of reading, I'm still confused as to what I should be doing. I think that my mixing and matching files is hurting me here...
It appears that the only way to do this is manually with NVFlash. I had a difficult time finding the appropriate file. For those wondering, it's an official nvidia file, and there is a linux specific version. Here's the link I used.
I followed a couple of different guides, none of which worked.
Started here. Couldn't get past the first nvflash command after realizing that I didn't have any of the bin files. OK, found this guide, which appears to have the most up to date bootloader, and I think all the other files I need--none of the other guides included bct.bct, and flash.cfg, which I think are necessary (someone please correct meif I'm wrong). The "V8-UNL-ICS-HC-bootloader-MULTI-cwm" package on the first page is what I used.
So this thread is windows-centric, but looking at the v8.bat file I think pointed me in the rightish direction.
I first ran this command:
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_v8.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x59DBC201 0xDB60F601 0xDB0F1203 0xAE0A2103 --sync
and got this error:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0428000741ff3357
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_v8.bin
| 1191932/1191932 bytes sent
bootloader_1_v8.bin sent successfully
waiting for bootloader to initialize
bootloader status: success (code: 0) message: flags: 1073848316
bootloader failed NvError 0x0
command failure: bootloader download failed
Ok, an aside: what exactly am I doing in this step? I initially thought that I was flashing the bootloader, but that doesn't appear to be the case (looks like that's later). Tried finding out what the arguments meant for the nvflash command, but couldn't figure it out. Anyway, noticed another bootloader.bin file in the directory. Tried the above command using "bootloader_apx.bin" (Edit: Rereading the .bat file, looks like I was supposed to use the apx file initially anyway) Success, I think.
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x59DBC201 0xDB60F601 0xDB0F1203 0xAE0A2103 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0428000741ff3357
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Next step:
Code:
sudo ./nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
So formatting partition 4, which is where the bootloader lives I guess.
Code:
sudo ./nvflash -r --download 4 ./bootloader_v8.bin
Nvflash started
[resume mode]
sending file: ./bootloader_v8.bin
| 1191932/1191932 bytes sent
./bootloader_v8.bin sent successfully
OK.
Code:
[CODE]sudo ./nvflash -r --format_partition 6
Nvflash started
[resume mode]
Formatting partition 6 please wait.. done!
OK again.
sudo ./nvflash -r --download 6 recovery_thor17_403.img
Nvflash started
[resume mode]
sending file: recovery_thor17_403.img
\ 5074944/5074944 bytes sent
recovery_thor17_403.img sent successfully[/CODE]
And,
Code:
sudo ./nvflash -r --go
Nvflash started
[resume mode]
At this point, I rebooted...and ended up stuck in apx mode.
So I d/l'd the package from Moscow Desire in this thread, repeated the steps, and my tab came back.
I don't remember if I tried getting directly into the bootloader, but I had the "rom manager" program on my desktop. I was able to boot into recovery and backup my ROM.
Next time I tried using vol down + power to get into bootloader (or using rom manager to get back into recovery) I ended up with a dead android image.
So while typing up this post, I redid the steps using v8. Everything appears to have went well. I get a "Skrilaz bootloader v8/booting primary kernel image" message, and it boots normally. I can enter recovery using vol + + power. Bootloader still gives me a dead android though.
I didn't do:
Erase boot.p file. Wasn't sure if this was necessary or not. Since I see the v8 bootloader message, I'm guessing not.
If nothing jumps out at anyone, could this be a hardware problem? Of note, before I started messing with this, I tried getting into the bootloader via vol -/pwr, and got the dead android there too.
EDIT: Oops, looks like I'm entering the bootloader menu after all by using vol +/pwr. So recovery is my problem now. Getting closer...
nola mike said:
I didn't do:
Erase boot.p file. Wasn't sure if this was necessary or not. Since I see the v8 bootloader message, I'm guessing not.
If nothing jumps out at anyone, could this be a hardware problem? Of note, before I started messing with this, I tried getting into the bootloader via vol -/pwr, and got the dead android there too.
EDIT: Oops, looks like I'm entering the bootloader menu after all by using vol +/pwr. So recovery is my problem now. Getting closer...
Click to expand...
Click to collapse
Wot rom did u start off with?
The boot.p file. If it's there u must rename or delete it, else it will just keep
Overwriting yr newly flashed custom cwm with the stock Acer recovery, this
is the dead android you mentioned.
No, u have no errors which point to the h/w fault.
The process is this...
Check boot.p file and rename - need root
1. Flash v8 and cwm
2. Boot directly to cwm
3. Flash rom
4. Full data wipe recommended
5. Reboot
So re flash cwm with nvflash again and flash yr rom...that should be it!!
Also, rom manager does not support our tab, would recommend not using it.
Once u have the v8 you can use Acer recovery installer instead.
Finally got it working.
I ended up getting the "acer recovery" program from the play store, which worked fine. My backup plan was to try to install one of the recovery zip files through the bootloader rather than through apx. I tried all 4 of the bootloaders through apx without success.
Another note: I ended up stuck in apx mode again, but was able to get out of it just by re-starting the process--I was able to just flash v8 rather than reverting back to the v3 packages. Hopefully this will help some of you linux folks. I guess I can summerize what actually worked for me (all the links are in the above post):
1. Download nvflash (linux version)--I don't remember if I needed to change permissions for this, but make sure it's executable
2. Find your CPUID and SBK (instructions for this are elsewhere; basically go to a terminal emulator, type dmesg | grep androidboot.serialno. On mine, grep wasnt recognized as a command, so I did dmesg>dmesg.txt, opened dmesg.txt with an editor and searched for androidboot.serialno)
3. Download V8-UNL-ICS-HC-bootloader-MULTI-cwm and unpack. Copy nvflash to this folder.
4. Place your tab in apx mode: Turn off, plug microusb port to computer, hold in reset button, press power x 3 sec, release power button, wait 1/2 sec, release reset button. dmesg on your computer should show something like this:
Code:
[146408.156075] usb 1-4: new high-speed USB device number 42 using ehci_hcd
[146408.288787] usb 1-4: New USB device found, idVendor=0955, idProduct=7820
[146408.288797] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[146408.288803] usb 1-4: Product: APX
[146408.288808] usb 1-4: Manufacturer: NVIDIA Corp.
5. Replace your sbk where indicated
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk YOURSBK --sync
6.
Code:
sudo ./nvflash -r --format_partition 4
7.
Code:
sudo ./nvflash -r --download 4 ./bootloader_v8.bin
YMMV on steps 8 and 9. Although everything said it worked on mine, it didn't. I'm thinking at this point that it's because I didn't delete the boot.p file, though I didn't think that was necessary using a patched bootloader.
8.
Code:
sudo ./nvflash -r --format_partition 6
9.
Code:
sudo ./nvflash -r --download 6 recovery_thor17_403.img
10.
Code:
sudo ./nvflash -r --go
Again, at this point I bailed somewhat and installed acer recovery from the play store, and it was able to install a recovery without me doing anything else. I'm now running CM 10.1/Jelly bean 4.2.1.
I actually forgot to do a system wipe (wiped dalvik though) before installing that ROM, but it's running great so far, and kept all my data. Sweet. Hopefully this will save somebody some time...
dibb_nz said:
Wot rom did u start off with?
The boot.p file. If it's there u must rename or delete it, else it will just keep
Overwriting yr newly flashed custom cwm with the stock Acer recovery, this
is the dead android you mentioned.
No, u have no errors which point to the h/w fault.
The process is this...
Check boot.p file and rename - need root
1. Flash v8 and cwm
2. Boot directly to cwm
3. Flash rom
4. Full data wipe recommended
5. Reboot
So re flash cwm with nvflash again and flash yr rom...that should be it!!
Also, rom manager does not support our tab, would recommend not using it.
Once u have the v8 you can use Acer recovery installer instead.
Click to expand...
Click to collapse
Thanks, the boot.p file was the conclusion that I eventually reached, but since I got it working through acer recovery I didn't try deleting/reflashing again. I don't remember which recovery loaded rom manager. Through acer recovery I flashed TWRP 2.1.3, which is a pretty slick program. BTW, I started with a completely stock tab running the ICS OTA update.
Related
Summary: I tried to install the ROM that shouldn't be named over FLEXREAPER extreme, and now the tablet is bricked.
Previous state: A500, unlocked ICS bootloader v7, Thor recovery 1.7.3, FLEXREAPER RF1 EXTREME revision 2.
What I did:
I entered CWM recovery
I wiped data, cache, dalvik cache, and battery status
I installed Tegraowners ICS ROM v169
I installed gapps-ics-20120429 (without rebooting)
I rebooted the tablet.
In retrospect, I suppose things went wrong when I didn't reboot before installing gapps, but it's too late to change that now.
Current state: the tablet won't boot, and pressing vol-up / vol-down doesn't help.
Connecting an USB cable from Linux, I get the USB ID 0955:7820, so the tablet seems to be in APX mode. I tried flushing the boot loader from scratch, but the operation fails:
Code:
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0xXXXXXXXXXXXXXXXX
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0
The above bootloader_apx.bin is ICS v7.
Edit: I do have a CWM backup taken just before installing the new ROM. So I suppose what I'm asking here is, how can I get to a bootable state with CPUID, SBK, the beginning of mmcblk0, and a working nvram. Help please?
lcd047 said:
Summary: I tried to install the ROM that shouldn't be named over FLEXREAPER extreme, and now the tablet is bricked.
Previous state: A500, unlocked ICS bootloader v7, Thor recovery 1.7.3, FLEXREAPER RF1 EXTREME revision 2.
What I did:
I entered CWM recovery
I wiped data, cache, dalvik cache, and battery status
I installed Tegraowners ICS ROM v169
I installed gapps-ics-20120429 (without rebooting)
I rebooted the tablet.
In retrospect, I suppose things went wrong when I didn't reboot before installing gapps, but it's too late to change that now.
Current state: the tablet won't boot, and pressing vol-up / vol-down doesn't help.
Connecting an USB cable from Linux, I get the USB ID 0955:7820, so the tablet seems to be in APX mode. I tried flushing the boot loader from scratch, but the operation fails:
Code:
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0xXXXXXXXXXXXXXXXX
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0
The above bootloader_apx.bin is ICS v7.
Edit: I do have a CWM backup taken just before installing the new ROM. So I suppose what I'm asking here is, how can I get to a bootable state with CPUID, SBK, the beginning of mmcblk0, and a working nvram. Help please?
Click to expand...
Click to collapse
If u cannot get to fastboot volume up/power to flash a recovery
and cannot boot to the OS or recovery
U will need to downgrade back to HC. See jazzyjames rollback thread on how to do that.
Yr cpuid is listed above as 'chip uid'
Ok, solved
Thanks for the answer. I got it working with TimmyDean's tool in a roundabout way: I re-created the partitions with TimmyDean's bootloader, and that allowed me to flash the unlocked ICS bootloader and recovery. Then I rebooted into recovery and I was back in business.
I should note however that I lost all the data from the internal sdcard in this process. I'm not sure if that was the result of me futzing with nvflash, or if re-creating the partitions did that; the end result is all files are gone. That's a pain, but survivable. At least my tablet is back, which is good, because with that rounded shape it would have made a lousy door stop.
i have this acer iconia i recently update facebook via playstore,its getting bootloop then suddenly when i press the power button on the power led indicator will lights but no display could someone can help me?:crying:
katz1328 said:
i have this acer iconia i recently update facebook via playstore,its getting bootloop then suddenly when i press the power button on the power led indicator will lights but no display could someone can help me?:crying:
Click to expand...
Click to collapse
Sounds like you are stuck in APX mode. A little reading will straighten things out.
badly needed help
could someone give some links to fix this problem i dont have my cpu id and sbk, EUU stop working in my laptop, apx tools are not working could someone help me im badly needed some help w/ this matter tnx for thos who help me
I have the exact same issue.
Power button turns white - screen is black - no vibration from power button - seems dead.
The tablet was untouched and stock - I have never rooted anything or messed with any ROMs.
It had updated to ICS a while back and was working great until yesterday when it just wouldn't turn on besides the power button.
I have tried holding down the volume up and power button reset. I have tried the reset button. I have tried unhooking the battery.
After checking this forum I have installed the ACER drivers and plugged the tablet into my PC. It is showing up as APX.
I believe I am stuck in APX mode so from what I'm reading there is hope I can somehow salvage the tablet even though I didn't try flashing
anything and haven't screwed with it before.
Since I have never messed with flashing android stuff I really have no idea where to start as the guides seem to be for people who have experience. Where do I start? From what I'm reading I'll need a CPUID but how do I get that from a "dead" machine.
I am a quick learner if someone has the time to point in the right direction. Maybe I'll get hooked on flashing ROMs and can contribute something here.
Thanks for any help you can give.
If yr tab is stuck in apx mode, you're gonna need yr cpuid to recover it, there is no other way....see cpuid guide in my SIG and checkout srbeens method using Linux to retrieve it or usbdeview....
If getting stuck happened spontaneously it points to the faulty chip issue requiring replacement from Acer... check post #3 of the root guide in my SIG for ways to recover from apex mode, you might get lucky but be aware that if its happened once it will happen again...
EDIT see this post http://forum.xda-developers.com/showthread.php?p=37421071 regarding new motherboards on eBay
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
If yr tab is stuck in apx mode, you're gonna need yr cpuid to recover it, there is no other way....see cpuid guide in my SIG and checkout srbeens method using Linux to retrieve it or usbdeview....
If getting stuck happened spontaneously it points to the faulty chip issue requiring replacement from Acer... check post #3 of the root guide in my SIG for ways to recover from apex mode, you might get lucky but be aware that if its happened once it will happen again...
EDIT see this post http://forum.xda-developers.com/showthread.php?p=37421071 regarding new motherboards on eBay
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the info. I was able to get my cpuid and sbk last night following the guide that used Ubuntu live cd. It was fun to play with Linux again.
I want to try and recover and if it continues to be a problem I will replace the board.
Looking at post 3 from your guide it appears my next step will be to use nvflash.
I am a little lost on what I will be flashing since I don't have anything backed up (flash a recovery?) and don't have a custom ROM to flash.
I just a need a push in the right direction.
Thanks for the help.
sixstring774 said:
Thank you for the info. I was able to get my cpuid and sbk last night following the guide that used Ubuntu live cd. It was fun to play with Linux again.
I want to try and recover and if it continues to be a problem I will replace the board.
Looking at post 3 from your guide it appears my next step will be to use nvflash.
I am a little lost on what I will be flashing since I don't have anything backed up (flash a recovery?) and don't have a custom ROM to flash.
I just a need a push in the right direction.
Thanks for the help.
Click to expand...
Click to collapse
Well done getting yr cpuid!!
If you want stock, your best bet is an Acer EUU. There's one in the guide which will take u back to HC 3.0.1. Blackthund3r has one in his acer OTA update thread too I think in dev forum....
Next step is getting out of apx mode...use lcd047's method in the cpuid guide....just use the image folder from your EUU ...and no need to do the boot loader part....Also use Linux again to run nvflash commands, no driver issues with that, unlike windows....
See how u go with that for a start. You should be able to OTA all the way to ICS with that EUU, if u want.
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
Well done getting yr cpuid!!
If you want stock, your best bet is an Acer EUU. There's one in the guide which will take u back to HC 3.0.1. Blackthund3r has one in his acer OTA update thread too I think in dev forum....
Next step is getting out of apx mode...use lcd047's method in the cpuid guide....just use the image folder from your EUU ...and no need to do the boot loader part....Also use Linux again to run nvflash commands, no driver issues with that, unlike windows....
See how u go with that for a start. You should be able to OTA all the way to ICS with that EUU, if u want.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Well we are getting somewhere but I hit a snag.
After running nvflash command the tablet instantly vibrated and I now have the ACER logo on the screen and the words Entering Acer Download Mode in the corner. I'm not sure if the command ran correctly as there was an error at the end in regards to partitions
[email protected]:~/Desktop/nvflash/Image$ sudo ./nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x6C886F00 0xA4A2F106 0x4BEB1504 0xD8292103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c70044220d657
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x5 (0x1000005) flags: 0
What to do next? Thanks for guiding me in the right direction.
sixstring774 said:
Well we are getting somewhere but I hit a snag.
After running nvflash command the tablet instantly vibrated and I now have the ACER logo on the screen and the words Entering Acer Download Mode in the corner. I'm not sure if the command ran correctly as there was an error at the end in regards to partitions
[email protected]:~/Desktop/nvflash/Image$ sudo ./nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x6C886F00 0xA4A2F106 0x4BEB1504 0xD8292103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c70044220d657
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x5 (0x1000005) flags: 0
What to do next? Thanks for guiding me in the right direction.
Click to expand...
Click to collapse
OK bad data and partition error too...
Which EUU did u end up using?
tdv4 is known to reset partitions but in some instances fails. The babsector.rar file can be more successful... link in the root guide with some instructions how to use.
You're gonna need a ROM to flash and At this stage I'd suggest a custom ICS one...
babsector will/should also flash up the skrilax_cz v8 unlocked bootloader.
If u get still get a bad data error then yr tab is toast...BUT keep trying it 8, 10, 15 times you may get lucky
PS:
Oh check the euu image folder for the .bat file and see if the odm data values match with what u are using manually.
There are 2 values used in different euu's and no-one as ever explained why this is....the one u used and this one 0x300d8011
To leave download/apx mode the windows command is nvflash -r --go
See vaches post bottom of post 3 in root guide, for more nvflash commands. You might just get lucky
good luck!!
dibb
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
OK bad data and partition error too...
Which EUU did u end up using?
tdv4 is known to reset partitions but in some instances fails. The babsector.rar file can be more successful... link in the root guide with some instructions how to use.
You're gonna need a ROM to flash and At this stage I'd suggest a custom ICS one...
babsector will/should also flash up the skrilax_cz v8 unlocked bootloader.
If u get still get a bad data error then yr tab is toast...BUT keep trying it 8, 10, 15 times you may get lucky
PS:
Oh check the euu image folder for the .bat file and see if the odm data values match with what u are using manually.
There are 2 values used in different euu's and no-one as ever explained why this is....the one u used and this one 0x300d8011
To leave download/apx mode the windows command is nvflash -r --go
See vaches post bottom of post 3 in root guide, for more nvflash commands. You might just get lucky
good luck!!
dibb
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I used this EUU
Official Acer EUU 3.0.1
WHOA!! Something happened overnight. When I went to bed last night I was stuck in APX.
I was going to try a new EUU or babsector like you suggested. As I was getting ready to do that I powered on the tablet. It vibrated and the ACER logo came up on the screen. First time it has done that since I started trying to fix it. It does not say it is download mode like it did before.
Looking at the guide there is a section that says
Use this update.zip for any of the following:
- You do not have your cpuid
- You are stuck on the "Acer" Logo
- Your tab boots past the Acer Logo but then boot loops at the boot animation
- You are on the old HC bootloader /ICS Rom combination
- You wish to return to factory stock, and OTA all the way to Stock ICS
Should I be trying that now?
---------- Post added at 06:25 PM ---------- Previous post was at 05:48 PM ----------
sixstring774 said:
I used this EUU
Official Acer EUU 3.0.1
WHOA!! Something happened overnight. When I went to bed last night I was stuck in APX.
I was going to try a new EUU or babsector like you suggested. As I was getting ready to do that I powered on the tablet. It vibrated and the ACER logo came up on the screen. First time it has done that since I started trying to fix it. It does not say it is download mode like it did before.
Looking at the guide there is a section that says
Use this update.zip for any of the following:
- You do not have your cpuid
- You are stuck on the "Acer" Logo
- Your tab boots past the Acer Logo but then boot loops at the boot animation
- You are on the old HC bootloader /ICS Rom combination
- You wish to return to factory stock, and OTA all the way to Stock ICS
Should I be trying that now?
Click to expand...
Click to collapse
I ended up trying the tdv4 EUU. I put the tablet back into APX mode.
This was the result.
[email protected]:~/Desktop/root-3.2.1/Image$ sudo ./nvflash --bt --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x6C886F00 0xA4A2F106 0x4BEB1504 0xD8292103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c70044220d657
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 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: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x4 (0x4) flags: 0
I just tried babsector on my PC. It also had an error
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c70044220d657
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 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: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Ideas?
Its not looking good m8
Someone else posted ebay have new m/b's listed for $50, you may want to look into that??
Couple of things to note though:
maybe just a copy/paste error but
you wrote: [email protected]:~/Desktop/root-3.2.1/Image$ sudo ./nvflash --bt --odmdata 0x100c0105
should be nvflash --bct flash.bct --setbct --configfile flash.cfg --create --odmdata 0xb00d8011 --bl bootloader.bin --go
the BCT error - if you d/l apxflash tool and run it....you MUST dump, save then use your tabs BCT when u get to the "bct window" - carry on with the tool and then put your tab in apx mode manually - just before the flash you'll see a window with a couple of check boxes "show nvflash commands'" check that to show any flash errors....flash it and see what happens
failure to write to mass storage - just another symptom of the "bad sector fault"
you might try a factory hard reset via rotation switch - this should wipe all userdata and cache and has been known to fix a few problems
With all the tools and some persistence (otherwise known as banging one's head against a brick wall. lol) something may end up working....thats all I can offer you at the moment...others who have been in this same situation will post something like you did...whoa all of a sudden it worked!!!! Be aware though it will happen again sometime in the future unfortunately...as I said before, your best bet is gonna be ebay
Well I tried for a few more hours to get something flashed and finally gave up and ordered a new board. Since this thing bricked itself without me ever screwing around with the file system I've got to believe it's a hardware issue. Hopefully the new board will last longer than 14 months like this one. Thanks for the tips on trying to revive it. After installing the new board I might get into some of this custom ROM stuff. What do you suggest for a ROM?
a500 USB DRIVER VANISHES
I need a little help my device is stuck in apx mode (blank screen with power led on) i have uid (cpuid) and sbk i have read a lot fom this forum and have all the tool to root, flash, load.. But my main problem is that when i reset my acer a500 and the usb is attached the windows 7 recognizes the driver and (sound pops up) and the driver (acer picasso usb boot recovery driver) is there but no tool e.g apxtool or fastflash or ics rooting nothing works or regocznies the device coz when i press any option or press the key to continue the drive drops and vanishes from the window usb list in device manager and i have to manually reset acer again to get the driver back but still no use as command prompt tells me that no device is attached or found. Please help as this acer is my wifes gift to me and im trying hard to get it back its totally dead
I am not sure of the best place to post this. I am having trouble installing loader/ROM on an Acer A500 tablet. I have read many of the posts here and in other forums and have tried several of the suggestions/guides. I think I am just digging the hole deeper and need some guidance on the path I should follow at this point.
The tablet is running Android 4.0.3 (Acer_AV041_A500_1.033.00_PA_CUS1), which has been completely stock and not rooted up to now. I followed directions on several postings (mainly by dibb_nz) on this forum, but have not been successful.
Here's how far I got and where I went off the rails.
I rooted it using SuperUser.
I collected the CPUID and got the SBK number.
I downloaded/installed Acer drivers and Andriod SDK.
I downloaded APX_v0.4A-flashTool-500Manager1.0.2_(1) and ran A500Manager and found that it could get info from the tablet.
I ran A500APXFlash, downloaded bundle 17, entered the SBK.
I manually put the table in APX mode, confirmed it is the Windows system tray (APX Device) and A500APXFlash reported it in that mode.
I proceeded to flash (in A500APXFlash). Here is where it went off the rails.
It hung at some point, but I can't recall exactly where (I've done many things since), but it was it was something like formatting the flash. I let it go for an hour and finally killed everything and rebooted the tablet.
I tried many more things, but always ended in failure. One was manual flashing with nvFlash. Below are the highlights of the batch file output to show how far it got:
Code:
Enter your SBK: <removed for security reasons?
* Make your choise: *
*(4) ICS bootloader V8 with Thor-1.7.3 NEW cwm(touch cwm)*
* with its compatible recoveries. *
(1 2 3 4):4
Loading bootloader...
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xA88B1E00 0x9726AB01 0xD76C4F03 0x00022103 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: <removed for security>
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0
During the above, the tablet said "Acer Iconia APX mode."
At one point I tried installing the CWM loader (I think it was that one). I also ran the Android adb program and was able to talk to the tablet through a command prompt.
Somewhere along the line, the Windows system tray driver report began saying "Acer USB Boot Recovery Driver" instead of "APX Device." I'm not sure when or what I did to cause it.
Another change in behavior is that the recovery mode boot (Power+VolDn) used to result in a dead robot icon. Now it looks like it is doing "SD update cmd: recovery" which fails (I put no SD card in it).
It appears that somewhere along the line (early in my trials) the BCT might have gotten wiped out and I cannot find a copy of it. I have seen various places where flashing hangs during a format or a download operation.
I have tried as much as I dare without help (maybe too much). At this point, by tablet is not bricked -- it still boots to Android 4.0.3. But I would like to restore it to where it was and then try the process again.
I have been trying to do the Timmy Dean EUU recovery to stock, but I have not been able to get the files. It seems that most of the links are either broken, or go to what lools like some pretty shady places. I'm not sure I should even be trying this route and, if I do, which EUU I should attempt.
I am fluent in Linux and have a Ubuntu 12.04 (VM) I can run if that's the best approach. I am also somewhat familiar with ARM Linux and the Marvell and TI-OMAP boot processes if any of this is useful. I am a complete noob on Android and the various ROMS, Loaders and mods. In fact, at this point, I'm not even sure what state tablet is in -- what loader is there, what has happened the flash ... -- or how to find out.
Thanks for whatever help/guidance you can give me.
Hello there, so it would appear that I've screwed up a big time. It's better if I tell you the whole story, so someone can help me.
I have this Vega clone with Froyo on it and I actually managed to delete the stock launcher with Titanium Backup. I though I wouldn't need it anymore (I know, I know) since I had GoLauncher installed. It worked well until I decided to flash a different ROM. So I formated the phone, erasing all the data, GoLauncher included. And of course I ran into a problem. I can't get past the Froyo setup wizard (probably because of the deleted stock Launcher), it just crashes everytime I try to finish the setup and returns back to the start.
After many tries I've decided to flash a Stock Vega ROM seeing as it should be compatible with my tablet. I put the device into APX mode, installed necesarry Nvidia drivers and tried to flash it with the exe downloaded from Vega homepage. And this is the main problem, the program works for a while and then it stops at creating BCT partition, showing this error:
C:\Users\LUK~1\AppData\Local\Temp>nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct
--setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x0b0c0075 --crea
te --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0370014741a04217
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: H5PS1G83EFR-S6C_V24_0625.bct
- 4080/4080 bytes sent
H5PS1G83EFR-S6C_V24_0625.bct sent successfully
odm data: 0xb0c0075
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 941512/941512 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:
Click to expand...
Click to collapse
I've been trying to fix this for two days now and I'm getting desperate. I found several posts on other forums where some users had the same problem, but there was no solution posted anywhere.
Does anyone know, what may be the cause of this error and how can I fix this?
Alternatively, is there another solution to the problem I've created?
Does it happen with all nvflash roms ?
if yes see below, if no try one of Scannos roms first before proceeding below.
Can you unzip the nvflash.exe, any zip prgram should do this, even if you rename it to nvflash.zip.
Then edit the command to flash and exclude flashing the bct cause this looks like this is where it's falling down. Just use the other commands. For an example see below. The full command is first. So edit out the bct bit.
nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x000c0075 --create --go
Try something like
nvflash.exe --bl bootloader.bin --configfile flash.cfg --odmdata 0x000c0075 --create --go
See how you get on with that. And as usual I'm not responsible if your tablet blows up, goes on fire or whatever. You could try asking over on modaco or tabletroms forum, look for Scanno or EJTagle.
You could also try this.
Actually reading around I don't think you need to extract the nvflash.exe/zip but it's worth a shot.
Sorry about the long post.
Thank you for your reply Stephen.
StephenC82 said:
Does it happen with all nvflash roms ?
if yes see below, if no try one of Scannos roms first before proceeding below.
Click to expand...
Click to collapse
Forgot to mention this, yes it happens with all roms.
StephenC82 said:
Can you unzip the nvflash.exe, any zip prgram should do this, even if you rename it to nvflash.zip.
Then edit the command to flash and exclude flashing the bct cause this looks like this is where it's falling down. Just use the other commands. For an example see below. The full command is first. So edit out the bct bit.
nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x000c0075 --create --go
Click to expand...
Click to collapse
Ok, so the full command for the stock nvflash is:
nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x0b0c0075 --create --go
Click to expand...
Click to collapse
I've tried to get rid of all the BCT parts, but it doesn't seem to work even if I delete a single argument. Always ends up like this:
command failure: --setbct required for --create
or
command failure: bootloader download failed
Click to expand...
Click to collapse
So I don't think I can affor skipping any of these.
StephenC82 said:
See how you get on with that. And as usual I'm not responsible if your tablet blows up, goes on fire or whatever. You could try asking over on modaco or tabletroms forum, look for Scanno or EJTagle.
Click to expand...
Click to collapse
Already posted my problem on both forums, got no replies so far.
StephenC82 said:
You could also try this...
Click to expand...
Click to collapse
Tried, unfortunately it didn't work.
StephenC82 said:
Sorry about the long post.
Click to expand...
Click to collapse
No problem, you're the only one who has tried to help me so far.
When you unzip the nvflash rom can you send the config file please. Flash.cfg I think it's called.
This looks weird to me.
load address: 0x108000 entry point: 0x108000
failed executing command 16 NvError 0x120002
Looks like it's pointing in teh wrong direction.
I could be totally way off but figure it's worth a go.
There you go, hopefully you can find out what's wrong.
What kind of clone is it ? Is it a Gtab ?
Couple of things to try/read over at your leisure.
http://forum.xda-developers.com/showthread.php?t=978791
http://forum.xda-developers.com/showthread.php?t=848272
After this not sure what else to try to be honest. Either it's a bad block on the nand or a clone of the vega and the Roms aren't taking to it.
Is it a P10AN01 ?
take a look here
hez, i had in the past the same problem. I think, i can help you. Take a look in the topic below
forum.xda-developers.com/showpost.php?p=36124362&postcount=4
in one of the -edits- is the solution.
i linked on a ohter webpage ...
Hello.
Since I dont have 10 posts, I am forced to post here. I hope this is ok.
I already asked in a german forum, but I didnt get an answer there.
I have an Acer A501 Tablet.
Bootloader is HC 3.01.
Recovery is Touch Recovery 1.8.1 by Thor
ROM is 4.2.2 by TegraOwners
Since I want to try out the new 4.3 ROMs my bootloader must be upgraded to ICS Bootloader.
I am using Linux. And I want to use nvflash to replace the HC 3.01 bootloader with ICS v9.
I download the "Patched ICS bootloader V9" bootloader which contains 3 files:
bootloader_apx.bin
bootloader_v9.bin
bootloader_v9.blob
After studying the tutorials
for flashing:
http://forum.xda-developers.com/showthread.php?t=1622425
and linux:
http://forum.xda-developers.com/showpost.php?p=26372919&postcount=460
I still have a question. So forgive me to post here.
I have written an sh script which should do the flashing.
Code:
#!/bin/sh
./nvflash --bl bootloader_apx.bin --sbk 0x12345678 0x12345678 0x12345678 0x12345678
./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
bootloader_apx.bin should load the bootloader.
bootloader_v9.bin is the bootloader itself.
bootloader_v9.blob I dont know what this file is good for.
So my question. Is this script right? I only want to replace the bootloader. Recovery and ROM is already installed.
I really need to know this exactly, since I dont want to brick my tablet.
Oberkellner said:
Hello.
Since I dont have 10 posts, I am forced to post here. I hope this is ok.
I already asked in a german forum, but I didnt get an answer there.
I have an Acer A501 Tablet.
Bootloader is HC 3.01.
Recovery is Touch Recovery 1.8.1 by Thor
ROM is 4.2.2 by TegraOwners
Since I want to try out the new 4.3 ROMs my bootloader must be upgraded to ICS Bootloader.
I am using Linux. And I want to use nvflash to replace the HC 3.01 bootloader with ICS v9.
I download the "Patched ICS bootloader V9" bootloader which contains 3 files:
bootloader_apx.bin
bootloader_v9.bin
bootloader_v9.blob
After studying the tutorials
for flashing:
http://forum.xda-developers.com/showthread.php?t=1622425
and linux:
http://forum.xda-developers.com/showpost.php?p=26372919&postcount=460
I still have a question. So forgive me to post here.
I have written an sh script which should do the flashing.
Code:
#!/bin/sh
./nvflash --bl bootloader_apx.bin --sbk 0x12345678 0x12345678 0x12345678 0x12345678
./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
bootloader_apx.bin should load the bootloader.
bootloader_v9.bin is the bootloader itself.
bootloader_v9.blob I dont know what this file is good for.
So my question. Is this script right? I only want to replace the bootloader. Recovery and ROM is already installed.
I really need to know this exactly, since I dont want to brick my tablet.
Click to expand...
Click to collapse
Judging by the post u linked the script looks like this:
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXX 0xXXXXX 0xXXXXX 0xXXXXXX --sync
./nvflash -r --format_partition 4
./nvflash -r --download 4 ics_boot_unlk_V3.bin
./nvflash -r --format_partition 6
./nvflash -r --download 6 recovery_thor17_403.img
./nvflash -r --go
Yr script is missing:
--sync command after the sbk and
./nvflash -r--go command after the v9.bin seeing as you aren't flashing a recovery.img. ...
I am linux illiterate! ! So cannot help you much, if at all but I think you'd be best to follow the post you linked to....hopefully someone else, (like @Moscow Desire, lol) can help you out a bit more!
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
Thread can be closed.
I figured it out myself.
I have written a German tutorial. If there is interest I will translate it to English.
:fingers-crossed:
Oberkellner said:
Thread can be closed.
I figured it out myself.
I have written a German tutorial. If there is interest I will translate it to English.
:fingers-crossed:
Click to expand...
Click to collapse
Sorry am late to the party, but happy you figured it out. Am on vacation this month.
If you want to write a guide for linux, then you can create a new thread in general forum.
@Oberkellner - a guide would be great, as Moscow suggested start a new thread for it and I will add a link to it in the root guide, thanks
@Moscow Desire - good to see you M, have a gr8 vacation
dibb_nz said:
@Oberkellner - a guide would be great, as Moscow suggested start a new thread for it and I will add a link to it in the root guide, thanks
Click to expand...
Click to collapse
I have written to tutorial and saved it, but I cant post it.
Error:
After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
My tutorial needs outside links which contain the files.
Correct me if I'm wrong but u should be able to upload the files via attachments here on xda, unless the 10 post rule applies to attachments as well...
Sent from my GT-I9300 using Tapatalk 4
Oberkellner said:
I have written to tutorial and saved it, but I cant post it.
Error:
After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
My tutorial needs outside links which contain the files.
Click to expand...
Click to collapse
I am pretty desperate for a linux nvflash tutorial, as I'm getting write errors in Windows and there's some evidence linux may be the answer. If there's any way for you to PM me the tutorial with links, etc. I'd be hugely appreciative. Thanks.
mylacuna said:
I am pretty desperate for a linux nvflash tutorial, as I'm getting write errors in Windows and there's some evidence linux may be the answer. If there's any way for you to PM me the tutorial with links, etc. I'd be hugely appreciative. Thanks.
Click to expand...
Click to collapse
Wot sort of write errors? If you've run babsector pls post output.
As far as linux is concerned u just need to pop yr tab in apx mode and run the command, see the 3rd post in the root guide in my sig
Sent from my GT-I9300 using Tapatalk
The errors always involve an inability to write to or partition the BCT partition. I've seen a few others users stuck in that dead end and a handful of them found success with this operation in linux.
(I'm such a newb I don't know how to properly post the output (in the gray box), but here it is)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
---------- Post added at 01:06 PM ---------- Previous post was at 12:38 PM ----------
@Oberkellner, I'm very sorry to threadjack. Just haven't received much help in my own thread and I know dibb_nz is very knowledgeable about this particular issue.
@dibb_nz, running nvflash from command line, using the code in the post you mentioned returns this
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
Click to expand...
Click to collapse
mylacuna said:
The errors always involve an inability to write to or partition the BCT partition. I've seen a few others users stuck in that dead end and a handful of them found success with this operation in linux.
(I'm such a newb I don't know how to properly post the output (in the gray box), but here it is)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
---------- Post added at 01:06 PM ---------- Previous post was at 12:38 PM ----------
@Oberkellner, I'm very sorry to threadjack. Just haven't received much help in my own thread and I know dibb_nz is very knowledgeable about this particular issue.
@dibb_nz, running nvflash from command line, using the code in the post you mentioned returns this
Click to expand...
Click to collapse
The code you ran, can be run with linux.
can you try it again please but replace the following:
odmdata 0x300d8011
with this:
odmdata 0xb00d8011
at the very end of the code replace --sync with --go
I've never tried doing it this way so you can play guinea pig, lol...don't worry it won't break anything thats not already broken
If that doesn't do it, then you will need to run the babsector.rar file, this will reset your partitions, if you get the bct error head over to this thread http://forum.xda-developers.com/showthread.php?p=47871344#post47871344from post#27. these guys are having issues too, u may be able to help each other
Pls post the outcome of the change in code here though, cheers dibb
Thank you kindly for your continued attempt to help. Your new code returned this:
c:\nvflash>nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash
.cfg --odmdata 0xb00d8011 --sbk 0x417D4C00 0x932F1700 0xDB65F302 0xA4082103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
Click to expand...
Click to collapse
FWIW, I was able to muddle my way through an attempt to use NvFlash in Linux (Ubuntu). Took a while to get everything set up correctly, but once I did, even trying to get the partition table failed :crying:
I think I'm screwed
Lol no u not m8...babsector.rar file will repartition download in post 2 in the root guide....
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Lol no u not m8...babsector.rar file will repartition download in post 2 in the root guide....
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
While I greatly appreciate the ray of hope you're giving me, I've run BabSector dozens of times and it always fails at creating the BCT partition (or anything after that).
Edit: here's the result of the A.bat file:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
Click to expand...
Click to collapse
dibb_nz said:
Judging by the post u linked the script looks like this:
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXX 0xXXXXX 0xXXXXX 0xXXXXXX --sync
./nvflash -r --format_partition 4
./nvflash -r --download 4 ics_boot_unlk_V3.bin
./nvflash -r --format_partition 6
./nvflash -r --download 6 recovery_thor17_403.img
./nvflash -r --go
Yr script is missing:
--sync command after the sbk and
./nvflash -r--go command after the v9.bin seeing as you aren't flashing a recovery.img. ...
I am linux illiterate! ! So cannot help you much, if at all but I think you'd be best to follow the post you linked to....hopefully someone else, (like @Moscow Desire, lol) can help you out a bit more!
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
mylacuna said:
While I greatly appreciate the ray of hope you're giving me, I've run BabSector dozens of times and it always fails at creating the BCT partition (or anything after that).
Edit: here's the result of the A.bat file:
Click to expand...
Click to collapse
Well thankx for posting that...bct errors are difficult to fix, not impossible, just difficult. .
Blackthund3rs apxflash tool is the only tool I know of that can fix and sometimes even that tool can have probs too...
I dont know why this happens, but it does seem strange alot of peeps lately have struck this error.
As I stated in the other thread...nvflash requires the bct from your own tab...apxflash tool uses a default bct which in most cases works...but if it does not then you must dump yr tabs bct and use that. The tool provides an option to do this...as long as u are on Ics, rooted, have busybox installed and usb debugging enabled!!!
So, can u still boot?
Which rom were u running?
Can u boot to recovery?
Sent from my GT-I9300 using Tapatalk
Can't boot, to Android or Recovery, was running a custom HC 3.1 ROM called Minimalist because anything after 3.1 broke the app needed to stream from Hava Monsoon (slingbox-like device). Was rooted, had CWM installed, and I do have a backup with a mmcblk0_start.img, which supposedly can be used to decrypt and recreate a .bct file but I'm not sure how that can help seeing as how my partition table is fubar'd and I can't write to partition 2. Needless to say, I wasn't on ICS, don't have busybox installed (not even sure what it is) but I do (or at least did) have USB debugging enabled.
Was the first part of your last reply directed at me? The part about stuff missing from the script?
At this point, I'm back to working in Windows. Tried linux and it didn't help or change the errors.
---------- Post added at 09:55 PM ---------- Previous post was at 09:41 PM ----------
Hmmm... just contacted ACER for an out-of-warranty repair and they created an RMA and sent me a pre-paid FedEx label. I have my fingers crossed that they are getting a lot of bad memory/motherboard repairs and are willing to do it for free, as suggested in this post:
http://forum.tegraowners.com/viewtopic.php?f=8&t=1249#p39164
Was the first part of your last reply directed at me? The part about stuff missing from the script?
Click to expand...
Click to collapse
sorry no it wasn't posting from my ph so not sure wot happened there lol
mylacuna said:
Can't boot, to Android or Recovery, was running a custom HC 3.1 ROM
Click to expand...
Click to collapse
ahhhh ok you're on the HC bootloader, different kettle of fish!!!
Its a shame the OP never posted his tutorial or told us how he got round the problem...ggrrrr
You have 2 choices from here:
1) run an update.zip from your ext sd card, altho with all the mucking about we've done I'm not sure how that will go...theres a link for a HC3.1 here. Put it on yr ext sd. Then power/vol down and it should boot into stock recovery and flash.
If all is well, you should be able to OTA all the way to ICS
2) The other way is to use timmydeans v4 - its nvflash EUU which will upgrade you to HC 3.2.1 pre-rooted and cwm installed. You say that anything above 3.1 breaks an app you want, but gosh, 3.1 is Gingerbread, its ancient Surely there must be another way to stream???
Anyway the main thing is to get you up and running, see how you go with these 2 methods.
If the upate.zip works and you intend staying on 3.1, you will need root again, see the root guide for the iconiaroot file, then Acer Recovery Installer file to flash a custom recovery.
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
@mylacuna OMG True....Good on Acer, I can see them getting a few more requests too...pls let us know how you get on with it
Thanks again. Think I'm going to go with the RMA.
FWIW, neither update.zip on ext. sd card, nor timmy dean's method would work, unfortunately. Stock recovery never boots (not sure if it's because something's cooked, or because I had CWM installed) and Timmy Dean's never shows a connection using the test.cmd script. I think that's because it's requires an ICS bootloader or something.
In any case, have a nice one, mate. You went above and beyond :good:
FWIW, as outlined in the previous posts, my Iconia was fully bricked... absolutely none of the tools available were able to re-format a corrupted BCT partition, whether due to hardware/memory error or what, I can't say, but I initiated a repair ticket and Acer repaired my out-of-warranty A500 for free, including shipping both ways.
So that might be an option for anyone who's having no luck with these other methods.
Kewlies good on Acer
Sent from my GT-I9300 using Tapatalk