Hey guys and gals,
I have an Iconia a500 that has been rooted since I got it last December. It has run various 3.2 and 3.2.1 HC roms, then the ICS leaks, and most recently Skrillax's V* bootloader, with Civato's Re-Flexx roms. Just yesterday, I had a random reboot, and then another, but on the second one it wouldn't get past the "loading kernel image" screen. I've tried to EEU back to Vache's 3.0.1 then flash an official rom to get it back on to the official upgrade path, and have been successful, except when going to ICS. Once the official ICS install completes, it hangs on the Acer logo, requiring another EUU. I've also tried Blacktundr's APX tool at that point to go to V8+thor recovery, then flashing an ICS rom. same result.."loading kernel image".
The tablet is fine, as long as I stick with HC roms, and the HC bootloader. It will upgrade-path sucessfully thru 3.2.1, and even run Timmydean's rooted3.2.1, then an old HC rom of my choice. Just NO ICS .
Ideas? Maybe a partition error?
I believe there is a .zip or .rar file called Babsector with 2 .bat files in it that will help me if anyone has them?
ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?
AtariDroid said:
ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?
Click to expand...
Click to collapse
where does it fail on the bl flash, what error do u get?
failing to ota to ics from HC - go to thread how to revert to stock the easy way by jdgM3NT4L - there's a non-US update.zip i posted that worked for me. but until we figure out why u u can't flash the bl, you're stuck with stock.
Sent from my GT-I9300 using Tapatalk 2
Thanks for responding! it is good to hear from a voice of experience on the subject. I will copy/paste my results of various tries asap. I was able to flash the V8 bootloader a couple days ago. But since then i've tried a few methods to get to ics.. Including the Babsector .bats, maunually trying timmydean's and vache's EUUs, all fail at formatting BCT. The APX tools hang at uploading image(bootloader). I'm thinking i may have to do the Rawread technique to map out bad sectors, and place an FCK partition where they reside.... BUT i've not found exact instructions on how to get that to work yet. so for it seems to just hang, but iim sure i'm doing the rawread command wrong. win7x64 by the way.
I have of course uninstalled/ reinstalled and tried both driver versions out there also.
Any tips are greatly appreciated.
Here is a try with babsector's first .bat:
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
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
| 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: 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
Next try.. same .bat:
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
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
| 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: 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
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:0x5 (0x1000005) flags: 0
As i mentioned earlier, I'm guessing I have the failed EEMC memory problem. hoping to remap the partitions. Going to try to put an FCK first and see what happens.
After trying an FCK partition of 1000000 sectors in size..
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
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
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: FCK
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
Formatting partition 15 FCK please wait.. done!
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader_v8_green.bin
| 1191932/1191932 bytes sent
bootloader_v8_green.bin sent successfully
sending file: recovery.img
/ 5242880/5242880 bytes sent
recovery.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
Well.. this is definitely uncool.. I made a .bat that loads the bootloader from any upgrade package and runs the flash.cfg from it.. I've tried timmydean's V4, vache's 3.0.1, the babsector cfg's, and even the CES picasso version with it's huge bootloader. ALL are a no-go. My only chance seems to be to map out bad sectors with the Rawread command and try to put a dummy partition on top of them.. IF said partition doesn't fail on format.
Can someone explain the process on how to figure out what sectors are bad with the rawread comand?
I did get an error 12 a couple times before it even tried formatting on a few of my over 50 attempts.
Also.. if i am really screwed here.. anyone know of any broken a500's around that I may be able to buy a motherboard from?
Thanks everyone for your help so far. Without the countless threads I have gone through to learn what I have, I would still be sitting here scratching my head even more lol.
I'm not much help sorry, i guess you've read what there is regarding this.
there is a few posts from user 'yaworski' who managed to fix this in one of the old bootloader threads, thats all i can offer at this point. you might wanna pm him? or maybe blackthund3r or eppeP. wish u all the luck in getting fixed.
rgds dibb
Sent from my GT-I9300 using Tapatalk 2
Actually you have been a great help, as you have been a large part of many of the threads I have read on the subject
I see this post: http://forum.xda-developers.com/showpost.php?p=27456113&postcount=22... but I did not succeed in finding where they actually went through the process.
I've tried running the rawdeviceread command to find the bad sector/s, but I think i am loading the RAM bootloader(Timmydean's) wrong. I have been using the a501 A.bat to load the bootloader, then killing it where it waits for the bootloader to initilize. From there I open another command prompt window, but nvflash hangs at every command. I'm not very well versed in Nvflash, as I only know what I have seen here and at Tegraowners.
Can someone tell me how to load the bootloader without having it execute any commands? That way I can run the rawdeviceread command and maybe figure out how to go from there. I also need to know if there is a way to create a partition without formatting it(I think that is automatic?). That way I can create the dummy FCK partition over the bad sector/s and skip it so the others can create/format successfully.
Re: [INFO/DEV] A500 ICS Bootloader (plus unlocked patched version)
oops just annihilated my post...and links to couple early bootloader threads, useful info really bct error....
apxflash tool allows you to dump your bct so you can nvflash - as long as your tab enters download mode and the apx usb device is showing up, go ahead and flash it -
Theres lots of info in some of the older bootloader threads http://forum.xda-developers.com/showthread.php?t=1514951)??? well worth a read
sp3dev said:
I have uploaded the archive with nvflash and some instructions on using it with A500. This is only intended for hardcore geeks who know how ARM boots. Be careful - while you can't really brick tegra2 (since it has a minimal usb-capable bootloader in the OTP area), you can screw up things and it will be quite hard to force the tablet to boot in some cases due to stupid security checks.
You can use this to download any bootloader/recovery/linux you want. That will help us with porting uboot. Someone may even write an automated tool for reflashing bootloaders and unbricking tablets..
http://www.mediafire.com/?pp97x9aahs58hzp
Let me just copy-paste the README from the archive here.
1. First, generate your sbk with http://vache-android.com/v1/index.php?site=sbk
2. Then, get a hold of mmcblk0 start sectors (at least 4KB) and copy it to mmcblk0_start
3. run the ./rip_bct.sh script and supply it with your SBK to rip BCT (boot config table. contains ram timings among other things)
4. run ./download.sh to connect nvflash to iconia (do it in APX mode). Note that you also need to supply your SBK here, but not as a long single number, but as it is displayed on the website
5. You can now play with nvflash - for example, read partitions, partition table and write your own flash_ic.cfg with partition layout
6. If you flash linux/recovery, make sure to update the magic values (like itsmagic does).
To do it, first download the 12th partition (AKB)
then, in the akb.bin, at address 0x84, replace 4 16-byte entries with the same pattern
"00 FB 30 94 99 01 4F 97 2E 4C 2B A5 18 6B DD 06"
ok, you need to patch the file once and can use it in further flashing. Just upload it to the device (like sign.sh does)
POTENTIAL PITFALLS. Listen up, I ain't gonna help you if you eff up here.
1. You must use BCT from your device Otherwise, the bootloader will not boot.
You will still be able to use NVFLASH, but until you dump your own BCT and use it
with NVFLASH, the device will not be booting again
2. If you use the ./iconia_boot.bin that differs from the bootloader on your
device, the device will get stuck in the APX mode after a reboot. If you do it,
flash the new ./iconia_boot.bin to the device (to the partition 4).
.
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk 2
Ok hoping to try again tonight. thanks for your help!
Hi i was looking for help on my iconia tab a500 everywhere, i've tried everything and don't get it to work, i try afterota, the blackthund3r, the timmy's help i try flashin bootloader, recovery, with babsector i ran the a502A Bat and give me this:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x7AAB1E00 0xB8CCE601 0x57850203 0x59042103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c6243416121d7
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
Presione una tecla para continuar . . .
then I ran the a501B and get this at the end
Formatting partition 2 BTC please wait.. FAILED¿
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7)
message: nverror:0x42008 (0x6042008) flags: 0
Presiones una tecla para continuar...
If someone can help me I appreciate it very much.
Thank you
I have reached the exact same point...for what I could found the issue is the internal SD damaged... only a MB change would be the solution...
sucks
hello i have an A500 stock rom and recovery,never flash it anything and one day it just died after puting it on stand by, i can put in in apx mode but i never turn the debugg on, so when i try to flash it ..nothing happens, the sd method dont work i hace the cpuid and the sbk witht the linux method, but thats as far as i can get.
im on ics, my bootloader is v0.03.12-ics and when i press vol +, power and rotation lock i got this
Bootloader v0.03.12-ics: starting fastobbot USB download protocol.
its was bricked so i run the a501 A.bat and after it i just came with an APX mode only
This is the result of the a501.bat
Nvflash started
rcm version 0X200001
System Information:
chip name: t20
chio id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380624440e10417
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
opertating 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: 0x1080000 entry point: 0x1080000
ending file: bootloader.bin
: 714409/714409 bytes sent
bootloader.bin sent 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
formating partition 2 BCT please wait ... FAILED
command failure: create failed (bad data)
bootloader status: specified partiton is invalid or does not exist (code: 7) message: nverror: 0x42008 (0x6040008) flags: 0
press any key . . .
Any ideas . I think i have lost my partitions, is there a way to create them?
by the way im very noob here so a step by step procedure is what i need....
Thank for the help you can provide me .
(I already tried a lot of searching, no success)
I am trying to recover an Acer Iconia A500, which seemed to have a bad sector in the first 4MB of flash. So after Babsector and manual rawwrite/rawread tests, I created a modified flash.cfg which inserted an FCK partition for the bad sectors between the BCT and PT partitions. However when I run nvflash --create, it hangs trying to format that FCK partition (which is just there to prevent use of the bad sectors).
Is there a workaround, e.g. some way of telling nvflash not to format the FCK partition while still creating the proper contents of the BCT and PT partitions (so I can move on to flashing the desired bootloader, kernel and recovery)?
Update: By simply trying again and again, it randomly succeeded (once) in getting past the FCK formatting. No change in config or command, just repeated tries (which cannot be good for the flash chip).
I am using the old nvflash.exe (dated 2011-11-23, size 152064, no --version option) with the following command line:
Code:
nvflash --bct flash.bct --setbct --configfile flash.cfg --create --odmdata 0x100c0105 --bl dlmodebl.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX
dlmodebl.bin (like nvflash.exe and flash.bct) is from timmydean's root-3.2.1-V4.7z
The output (from failed attampts) is this:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: dlmodebl.bin
| 714385/714385 bytes sent
dlmodebl.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: FCK
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.. done!
Formatting partition 15 FCK please wait.. done!
(and it just hangs after that). The one time I was successful, it swiftly did all the partitions then flashed the various .bin and .img files as specified in flash.cfg. Output was this:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
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: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: dlmodebl.bin
| 714385/714385 bytes sent
dlmodebl.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: FCK
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.. done!
Formatting partition 15 FCK please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader.bin
| 1191932/1191932 bytes sent
bootloader.bin sent successfully
sending file: recoveryThor.img
\ 4810752/4810752 bytes sent
recoveryThor.img sent successfully
sending file: boot.img
- 3450880/3450880 bytes sent
boot.img sent successfully
sending file: system.img
/ 629145600/629145600 bytes sent
system.img sent successfully
sending file: flexrom.img
/ 104857600/104857600 bytes sent
flexrom.img sent successfully
sending file: checksum.img
/ 10485760/10485760 bytes sent
checksum.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
However, the result is still not bootable (to recovery, system.img doesn't match the other parts).
The modified flash.cfg differs from timmydean's only in a smaller BCT and the extra FCK partition at the beginning, here is the new beginning:
Code:
[device]
type=hsmmc
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=FCK
id=15
type=data
allocation_policy=sequential
filesystem_type=basic
size=3141632
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
Wow that's some nice investigative work there...
These things are way above my skill level, but I can offer some thoughts from being around the Acer forums here for a while now.
You are correct regarding the chip. It is faulty (or the solder is.) Which is why formatting 'worked' after multiple attempts.
It's still failing on the bct write error. What I can tell you is, each tabs bct is 'different'. For nvflash to operate correctly, you must use your tabs own bct. Once flashed successfully with skrilax_cz bootloader, it doesn't appear to matter which bct you use...
Blackthund3r's apxFlash tool has an option to dump (and save) your tabs bct, which can then be used to successfully nvflash.
If you could somehow retrieve the original bct you may be able to resolve the problem....in saying that though, you will still be left with a faulty emmc, so any success you have with the flash, at some point it will fail completely....attempts at Reflowing the solder has worked in some but not all cases, so that's at least worth a try.
I wish you all the best with your endeavours, the bct error has never been resolved and thei conclusion has always been "it's a faulty chip" not much comfort for those with the issue, especially being through no fault of their own....
One other thing, through many, many flashing attempts of my own, I did get this error once...thankfully between the auto tools and babsector/tdv4 etc, I managed to get it up and running again. I've never had any trouble with it over the 2-3 years since...there maybe a small sliver of hope for you there...
Good luck with it !!
dibb
Sent from my HTC_PN071 using Tapatalk
Unfortunately, Blackthunder's utility just kept getting in the way, as it kept assuming I was starting from a working tablet in ADB mode, not a broken tablet that could only be put in APX mode with the reset button. I managed to find an XDA thread with a tool to extract the CPUID from APX mode and another thread with a tool for creating the Iconia specific SBKv1 from the CPUID.
Blackthunder's tool seems to be mostly a wrapper around the base tools (adb.exe, fastboot.exe and nvflash.exe), and at least the nvflash from the timmyDean ROM bundle fails when asked to read back the old BCT, while the nvflash from the wheelie bundle simply doesn't accept an SBK argument. Anyway since I have by now repeated reformatted the flash, I doubt the old BCT is still there.
From what I have read however, the (unencrypted) BCT depends only on the following:
1. How the RAM and FLASH is wired to the Tegra chip in a specific tablet model (and which RAM and FLASH chip models they are, for instance do they run on 1.8V or 3V).
2. Parts of the partitioning.
3. Parts of the bootloader configuration (the --odmdata argument).
So using the BCT from timmyDean's bundle should be fine for the A500 it was written for.
Another thing is that during flashing, the BCT and other early boot parts need to be encrypted with the device specific SBK. For the A500 and A501 we know the SBK and can do so directly (via the --sbk option to the old nvflash.exe or the BlackThunder GUI), while for some later tablets we don't know the SBK but can use the the wheelie trick to make the tablet encrypt it for us (this is what the wheelie preparation procedure essentially does).
I still haven't found a detailed nvflash manual, the documentation for the RCM preboot protocol or the documentation for Tegra's AES engine.
My Ideapad K1 is bricked, I assume.
I tried flashing multple ROMS and I keep getting below error..
flash-win
Flashing ICS Stock Rom for Lenovo Ideapad K1
build 120607
Nvflash v1.8.90246 started
Using blob v1.1.57813\AppDap☺│ß½W
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428018142a05597
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: 1
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x300c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
\ 1393296/1393296 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: USP
creating partition: UDA
creating partition: TMP
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
Click to expand...
Click to collapse
Note- My SDCARD slot is corrupted and it does not work.
Is there a way to recover the tab?
Update - I tried flashing 'K1_A301_11_11_111108_US' and it worked like a charm. Any other ROM that I try to flash using nvflash does not work thou'