Be warned: Your Warranty will become void by using this method
Last week, my brand new Xiaomi Mi-Pad arrived via Flipkart and no sooner did I have it in my hands, I started installing useful apps like Greenify, ES File Explorer, etc. Two days went by and I was disappointed to learn that it doesn’t support a USB Dongle (Data Card) which is a very common method of Internet access in India. The only way I could have it was to root the tablet. And it was while rooting using SuperSU app that I foolishly selected a wrong click and ended up bricking my brand new tablet.
The Problem
It was a hard brick, meaning my tablet showed no signs of life when switched on or connected to a PC through a USB cable. Had it been a soft brick, meaning that I were able to boot to MIUI Recovery by pressing Power+UpVolume or to FastBoot Recovery by pressing Power+DnVolume button, it would have been easy to recover. But my tablet was totally dead. Even after charging for next 6 hours, all it did was light up a black LED screen for a second or two and then vanished for any combination of those buttons.
The problem was that the wrong click that I made had caused the tablet bootloader to be corrupted. And in the android world, if the bootloader is lost, then your device is literally as useful as a brick! Unlike 8086 PCs, android tablets don’t have a hard-wired BIOS to recover things from, the bootloader is as good as the BIOS.
The Research
Now obviously, I was disappointed and annoyed. After spending ₹10,999 on a brand new tablet, this was not what I was hoping for. Getting service from a Xiaomi service center was not an option as they are very rare in India. Besides, OEMs hardly provide warranty/support to people who try and root their devices, do they? So naturally, I had to myself find a way out of this. My research finally led me to a post by a Russian hacker who had successfully revived the tablet from this very situation. In this article, I’ll note down exactly what steps I had taken to revive it and hope that someone might find it useful.
The Solution
Though the solution is easy and straight-forward, there are some tricky areas where you might run into trouble. If you don’t have the confidence to open up an electronic device using a screwdriver or flash a stock ROM, just say quits and if possible, ask help from someone you know who is used to do it. Basically, the process involves this:
Open the back-cover by separating it from the screen (fingernails or a sharp object will do) and unscrew the plastic panel that covers the top area of the motherboard.
Disconnect the battery by slowly pulling the power belt (using a flat-head screwdriver or any sharp object).
Connect the USB cable to Mi-Pad end (but not the PC end yet).
Create a short circuit between the two tiny pads inside the MicroSD card slot using a metal object or wire.
Connect the USB cable to the PC end.
If done properly, the PC will detect a Nvidia Boot Recovery for Mobile USB device and then you can flash your stock ROM using Xiaomi’s flashing software, Mi Flash Tool, thus putting the life back into your tablet.
The Magic
The most tricky and magical aspect of this whole process is the short-circuiting in step four. Firstly, it is not easily diagnosable. The Nvidia USB driver is in fact detected by the PC even if you don’t create the short-circuit (but the battery needs to be disconnected of course), but then it will disappear instantly and you won’t get the time to flash your stock ROM. For some unknown laws of electricity (or maybe the laws coded inside this Nvidia driver), the short-circuit may not work instantly the first time. You’ll create the short-circuit, connect to the USB port and hear the Windows beep sound for USB connection, but moments later you will hear another beep of disconnection. If that happens, you’ll have to disconnect the USB cable and repeat from step-4: Create the short-circuit again and reconnect to the USB port - I had to do this about 50 times before the connection was stable enough for me to flash the ROM.
Some forum posts advice you to plug in the power belt at exactly the same time as the USB connection is detected in the PC. However, I’ve found that its not true. Not once did I put the power belt back in the whole process until the ROM had been flashed completely.
The Weapon
You can use any metallic object to create the short circuit, even a tiny wire could be used. The important thing is that those two minuscule pads inside the MicroSD slot are connected by a metal. Personally, I used this tiny pin that came with the booklet along with the Mi-Pad itself!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All I did was place that pin inside the MicroSD slot, so it created a bridge on top of those two pads, and supported the pin using any available object (in this case a screwdriver).
You’ll also need a 2.0mm screwdriver to open the back-panel above the motherboard. Please remember that opening those screws are going to void your warranty (which is going to happen in any case since you either tried to root or used the dd command to rewrite partitions in order to reach this stage!).
On your Windows PC, you need the following installed:
Latest version of Mi Flash Tool (Can be downloaded here).
Latest version of Mi Phone Manager PC Suite for the Nvidia drivers (Can be downloaded here).
Alternatively, you can download the whole bundled software from here that comes with Mi Flash Tool, NVidia Drivers and ADB Drivers too.
You’ll also need to download the latest MIUI stock ROM for Mi-Pad from here and extract somewhere on your PC to flash it later.
Once your short-circuit works and the connection stays stable, waste no more time. Just fire up the Mi Flash tool and select the path to the ROM image you just extracted and click the flash button. Once the flash is successful, assemble back your Mi-Pad and on pressing the power button, you should see this:
Summary
Keep a cool mind and do it, it can be done! If you can’t do it, try and find a mobile repair shop nearby or catch a tech enthusiast in your circle who can do it.
References
Post by original Russian Hacker (BogNik) who did it first
Latest Mi Flash Tool
Latest Mi Phone Manager PC Suite
Latest Bundled Software - Flash Tool with Nvidia and ADB Drivers
Latest MIUI stock ROM
Original post on my blog
Edit
As noted elsewhere, this is not a sure-shot or guaranteed way to recovery. Depending on other factors like what you originally did to cause the hard-brick and whether or not you were flashing the correct ROM, you may or may not be able to resuscitate this device. Apparently, based on the observations and discussions on the Xiaomi support forums, Xiaomi motherboards (and especially the eMMC) are known to get damaged under the following situations:
1. You tried to alter existing partitions using the parted tool.
2. You tried to flash an incorrect ROM.
So, if you had done such a thing and caused yourself a hard-brick, the better idea is to hand it over to a Xiaomi service center directly (or hand it to your local service center and they will send it to China). However, this seems to be specific to Xiaomi and Nvidia - I've altered partitions and flashed ROMs with several MediaTek SoC based phones before and never had such an issue, so Nvidia might be having answers to lots of our woes here.
Thank you for the instructions. Will try them out over the weekend.
I am in the same boat... an incorrect recovery flash bricked my device.
However, can you please point out which one is the power belt to be pulled out?
can you please point out which one is the power belt to be pulled out?
Click to expand...
Click to collapse
Have a look at this original post. There is an green arrow above the battery area where the power-belt is marked. However, I hope you didn't try to flash the ROM of an entirely different device? If that happens, hope of recovery is little as Xiomi devices are known to get their motherboards damaged in that case.
Tried all the steps after shorting the two pins (stable)... MiFlash said operation completed successfully in 93s. But, the battery had completely died so the device didn't boot... charging it now...
However, I think the MiPad is now resuscitated. Many thanks for your post. Saved a great device.
chetzrao said:
Tried all the steps after shorting the two pins (stable)... MiFlash said operation completed successfully in 93s. But, the battery had completely died so the device didn't boot... charging it now...
However, I think the MiPad is now resuscitated. Many thanks for your post. Saved a great device.
Click to expand...
Click to collapse
Great! Let us know whether you were able to start the device and what had caused the brick originally? (Will be useful for documentation).
prahladyeri said:
Great! Let us know whether you were able to start the device and what had caused the brick originally? (Will be useful for documentation).
Click to expand...
Click to collapse
Which is the power belt -1,2,3
Pranz... said:
Which is the power belt -1,2,3
Click to expand...
Click to collapse
Its 2. But you need to carefully pull that out by inserting a flat-head screwdriver or something at the hollow below the base of that metallic belt. Do it carefully, if you don't feel comfortable, then I recommend enlisting the help of someone who is used to opening electronics.
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
I have a problem , when I connect power belt then Nvidia drivers connect
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
If NVIDIA drivers are connected and the USB connection is stable, you should just flash the latest ROM for MiPAD and be done.
If the connection is not stable, check whether you are doing the short-circuit properly? Refer to the original diagram I've attached for creating the short circuit.
prahladyeri said:
Great! Let us know whether you were able to start the device and what had caused the brick originally? (Will be useful for documentation).
Click to expand...
Click to collapse
Sorry for the delayed response.
YES. The device is now fully back to normal... thank you once gain for the instructions... getting the short between the pins is the tricky bit... I managed it by twisting the ends of a safety pin and wedging them under the MicroSD frame.
The original cause of the brick was flashing a wrong version of CWM.
chetzrao said:
Sorry for the delayed response.
YES. The device is now fully back to normal... thank you once gain for the instructions... getting the short between the pins is the tricky bit... I managed it by twisting the ends of a safety pin and wedging them under the MicroSD frame.
The original cause of the brick was flashing a wrong version of CWM.
Click to expand...
Click to collapse
Great! Glad to know that.
Code:
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[00001308]0 0.00 execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[00001308]0 0.03
[00001308]0 0.03 $pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images
[00001308]0 0.03
[00001308]0 0.03 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
[00001308]0 1.80 Nvflash 4.13.0000 started
[00001308]0 1.80 chip uid from BR is: 0x34001001740d01480800000001ff0080
[00001308]0 1.80 rcm version 0X400001
[00001308]0 1.80 Skipping BoardID read at miniloader level
[00001308]0 1.80 System Information:
[00001308]0 1.80 chip name: unknown
[00001308]0 1.80 chip id: 0x40 major: 1 minor: 1
[00001308]0 1.80 chip sku: 0x0
[00001308]0 1.80 chip uid: 0x00000000000000000000000000000000
[00001308]0 1.80 macrovision: disabled
[00001308]0 1.80 hdcp: disabled
[00001308]0 1.80 jtag: disabled
[00001308]0 1.80 sbk burned: false
[00001308]0 1.80 board id: 0
[00001308]0 1.80 warranty fuse: 0
[00001308]0 1.80 dk burned: false
[00001308]0 1.80 boot device: emmc
[00001308]0 1.80 operating mode: 3
[00001308]0 1.80 device config strap: 0
[00001308]0 1.80 device config fuse: 0
[00001308]0 1.80 sdram config strap: 0
[00001308]0 1.80
[00001308]0 1.80 RCM communication completed
[00001308]0 1.80 BCT sent successfully
[00001308]0 1.80 odm data: 0x49c000
[00001308]0 1.80 downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001308]0 1.80 sending file: bootloader.bin
[00001308]0 1.80
[00001308]0 1.80 - 1048576/4194304 bytes sent
[00001308]0 1.80 \ 2097152/4194304 bytes sent
[00001308]0 1.80 | 3145728/4194304 bytes sent
[00001308]0 1.80 / 4194304/4194304 bytes sent
[00001308]0 1.80 bootloader.bin sent successfully
[00001308]0 1.80 waiting for bootloader to initialize
[00001308]0 1.80 bootloader downloaded successfully
[00001308]0 1.80 ML execution and Cpu Handover took 1 Secs
[00001308]0 1.80 setting device: 2 3
[00001308]0 1.80 creating partition: BCT
[00001308]0 1.80 failed executing command 17 NvError 0x120002
[00001308]CScriptReport::DoWork(413): Unspecified error(0x80004005)
[00001308]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00001308]SaveFlashResult(1347): The specified service does not exist.(0x800704db)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[000004BC]0 0.00 execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[000004BC]0 0.03
[000004BC]0 0.03 $pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images
[000004BC]0 0.05
[000004BC]0 0.05 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
Please help!
Thank you!! It worked!
Finally after 4 hours of effort, got my Mi Pad working! The process does work! Had to log in and post and reply. Thank you @prahladyeri. :good:
What had happened:
Wrong click during SuperSU update. After that no boot. Screen lights up, but stays blank. No MI logo. No Fastboot. No Recovery. No battery charging/LED indication.
What worked for me
Here's the step by step of what worked for me after a lot of trial and error.
Downloaded all necessary files. Downloaded MiFlashTool from Xiaomi Tips (v20160830) - did not install. Downloaded Fastboot ROM (MiPad Global). Had already installed Mi PC Suite.
Uninstalled everything installed earlier (excluding MI PC Suite).
Restarted Windows 10 and disabled driver signature verification. Just hold shift when clicking restart in the windows power menu.
Installed MiFlash. Checked log in <the drive you installed Mi Flash in>:\XiaoMi\XiaoMiFlash\Log. Verified whether the result for all driver installation is 'true'.
Removed back cover and panel. Disconnected battery belt. Took a regular paper clip and created a small 'v' shaped object. Bent the ends to look like the paws of a dog's front legs when standing on its hind legs (sorry, not really a great description, but there it is ). Created a short circuit using the clip.
Connected to PC. PC beeps for connection. Thankfully connection remains stable (I did not connect the power belt; let the clip stay).
Dev Manager shows 'APX'. Update driver by pointing to MiFlash folder. Driver installs successfully.
Open MiFlash. Select ROM.
Refresh MiFlash. Device shows '0'. I say what the heck and click Flash. Starts flashing but shows device busy and pauses. At this point I am about to give up again. But suddenly the Gods of Android smile on me, and it flashes.
73s later I see a successful message and a sigh of relief escapes my lips.
Remove clip. Connect battery. Reassemble pad.
Turn on Pad and Voila! MI logo!
Hope this helps or at least encourages ('coz I know how frustrating it was to get it to work).
Thanks very much, I fixed my MiPad 1 year later !
I succeed to using aluminum foil (easiest way) and when I connected my MiPad to the PC I directly reconnected the battery and flash without disconnect device and it's worked !
I used MiFlash 20151028 instead of 20160830 and download ROM like this mocha_images_4.11.21_4.4_cn_7352dcd481.tgz
Just a small point for clarity, my MI pad got bricked with the wrong click in supersu. I did not unlock my MI pad ever since I bought it with MI unlocked tool provided by MI. But did root the tab with kingroot desktop app which showed fastboot logo in between the rooting process. Sould I be worried because I'm planning to do the same procedure. Waiting for your approva
Thanks
Try all the "soft-unbrick" methods first before trying this out
jobinslmn said:
Just a small point for clarity, my MI pad got bricked with the wrong click in supersu. I did not unlock my MI pad ever since I bought it with MI unlocked tool provided by MI. But did root the tab with kingroot desktop app which showed fastboot logo in between the rooting process. Sould I be worried because I'm planning to do the same procedure. Waiting for your approva
Thanks
Click to expand...
Click to collapse
Make sure you try the usual "soft-unbrick" methods first (like recharging it overnight and various power button combinations(power+up, power+dn, etc)). This method has to be the last resort. Though there isn't anything specific you need to worry about and usually it works, the short-circuit is tricky and needs to be done very correctly so that the USB connection stays stable which is essential to flash the MiPad.
l0stb0t said:
Code:
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]CreateManagedObject(1261): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1305): Unspecified error(0x80131604)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[00001308]0 0.00 execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[00001308]0 0.03
[00001308]0 0.03 $pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images
[00001308]0 0.03
[00001308]0 0.03 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
[00001308]0 1.80 Nvflash 4.13.0000 started
[00001308]0 1.80 chip uid from BR is: 0x34001001740d01480800000001ff0080
[00001308]0 1.80 rcm version 0X400001
[00001308]0 1.80 Skipping BoardID read at miniloader level
[00001308]0 1.80 System Information:
[00001308]0 1.80 chip name: unknown
[00001308]0 1.80 chip id: 0x40 major: 1 minor: 1
[00001308]0 1.80 chip sku: 0x0
[00001308]0 1.80 chip uid: 0x00000000000000000000000000000000
[00001308]0 1.80 macrovision: disabled
[00001308]0 1.80 hdcp: disabled
[00001308]0 1.80 jtag: disabled
[00001308]0 1.80 sbk burned: false
[00001308]0 1.80 board id: 0
[00001308]0 1.80 warranty fuse: 0
[00001308]0 1.80 dk burned: false
[00001308]0 1.80 boot device: emmc
[00001308]0 1.80 operating mode: 3
[00001308]0 1.80 device config strap: 0
[00001308]0 1.80 device config fuse: 0
[00001308]0 1.80 sdram config strap: 0
[00001308]0 1.80
[00001308]0 1.80 RCM communication completed
[00001308]0 1.80 BCT sent successfully
[00001308]0 1.80 odm data: 0x49c000
[00001308]0 1.80 downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001308]0 1.80 sending file: bootloader.bin
[00001308]0 1.80
[00001308]0 1.80 - 1048576/4194304 bytes sent
[00001308]0 1.80 \ 2097152/4194304 bytes sent
[00001308]0 1.80 | 3145728/4194304 bytes sent
[00001308]0 1.80 / 4194304/4194304 bytes sent
[00001308]0 1.80 bootloader.bin sent successfully
[00001308]0 1.80 waiting for bootloader to initialize
[00001308]0 1.80 bootloader downloaded successfully
[00001308]0 1.80 ML execution and Cpu Handover took 1 Secs
[00001308]0 1.80 setting device: 2 3
[00001308]0 1.80 creating partition: BCT
[00001308]0 1.80 failed executing command 17 NvError 0x120002
[00001308]CScriptReport::DoWork(413): Unspecified error(0x80004005)
[00001308]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00001308]SaveFlashResult(1347): The specified service does not exist.(0x800704db)
[00000468]GetFactoryObject(1326): The specified service does not exist.(0x800704db)
[00000468]GetSearchPath(1381): The specified service does not exist.(0x800704db)
[000004BC]0 0.00 execute C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\nvflash_all.bat
[000004BC]0 0.03
[000004BC]0 0.03 $pushd C:\Xiaomi\mocha_images_KXFCNBH11.0_4.4\images
[000004BC]0 0.05
[000004BC]0 0.05 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
Please help!
Click to expand...
Click to collapse
Did you ever try to re-partition the MiPad any time? If that happens or you tried to flash a wrong version of the ROM, there is the danger of MiPad mother-board getting damaged. Better take it to your nearest Xiaomi service center or send it to China.
Hi, please help. I managed to get to the part my PC can detect the APX device with Nvidia driver installed. The connection is stable, but I am unable to detect the device on my MIFlash tool version 2016.08.30.0 (I spam Refresh/Flash button but it's not helping). I have disabled driver signature enforcement too.
Do I need to manually enter fastboot mode by pressing the power and volumn down button? I find it very difficult to do that with the casing off.
Let me know if there is anything else I could be missing. Thanks!
You can try an older version of the MiFlash tool from here and see if it detects anything:
https://androidmtk.com/download-xiaomi-mi-flash-tool
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
Hey guys for the past 5 months I`ve been trying to unstuck my A500 from teh APX mode, and still no luck.
I have my CPUID/SDK, I`ve used every methodthat I know to unstuck it but I never managed it.
Can anyone share me a light? And in the case of sending it for Acer, can anyone say if is an firmware or hardware problem?
*Notes:
It all happened after I tried to intall a custom ics rom (based on stock ics rom) because that acer was delaying the launch on my country.
On the nvflash program , I get the following error
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
On the A500APXFlash program freezes on Step 2 uploading image.
thx in advance
caio492 said:
Hey guys for the past 5 months I`ve been trying to unstuck my A500 from teh APX mode, and still no luck.
I have my CPUID/SDK, I`ve used every methodthat I know to unstuck it but I never managed it.
Can anyone share me a light? And in the case of sending it for Acer, can anyone say if is an firmware or hardware problem?
*Notes:
It all happened after I tried to intall a custom ics rom (based on stock ics rom) because that acer was delaying the launch on my country.
On the nvflash program , I get the following error
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
On the A500APXFlash program freezes on Step 2 uploading image.
thx in advance
Click to expand...
Click to collapse
Do a search for "babsector", you will find exact references to the same error messages you are getting. It seems your partition table got corrupted, and now you can't write to it because it is corrupted, so babsector (misspelled badsector?) rewrites the partition table in a different location, and a different size, then re-creates it back in the correct location, thus fixing your problem. (Or something along those lines, but it will def fix your problem)
Don't forget to click "Thanks" if this fixes you up. (Tip, maybe, a lot of noobs at flashing, forget to root their tablet before flashing, thinking the flash will give them root. This is the cause for many of these first time flashers ending up in APX.)
badsector or babsector, can be found at:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
Danny2 said:
Do a search for "babsector", you will find exact references to the same error messages you are getting. It seems your partition table got corrupted, and now you can't write to it because it is corrupted, so babsector (misspelled badsector?) rewrites the partition table in a different location, and a different size, then re-creates it back in the correct location, thus fixing your problem. (Or something along those lines, but it will def fix your problem)
Don't forget to click "Thanks" if this fixes you up. (Tip, maybe, a lot of noobs at flashing, forget to root their tablet before flashing, thinking the flash will give them root. This is the cause for many of these first time flashers ending up in APX.)
badsector or babsector, can be found at:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
Click to expand...
Click to collapse
Thx for the response, I ran both .bat files on the folder, still I get error messages (listed below).
I`ve tried to run the nvflash.exe, but it opens and closes instantly.
Sorry if I done something wrong, I dont have much exp. on these subjects and the folder didnt present instructions how to proceed.
Error messages:
A501 A.bat:
Tablet enters in Acer download mode (Acer logo on the middle)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x03806248436154d7
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
A501 B.bat:
Tablet enters in Acer download mode (Acer logo on the middle)
Same message as above.
caio492 said:
Thx for the response, I ran both .bat files on the folder, still I get error messages (listed below).
I`ve tried to run the nvflash.exe, but it opens and closes instantly.
Sorry if I done something wrong, I dont have much exp. on these subjects and the folder didnt present instructions how to proceed.
Error messages:
A501 A.bat:
Tablet enters in Acer download mode (Acer logo on the middle)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x03806248436154d7
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
A501 B.bat:
Tablet enters in Acer download mode (Acer logo on the middle)
Same message as above.
Click to expand...
Click to collapse
Sorry, I am by no means an expert, but babsector has always fixed the problem for me when the error was " Command Execution failed cmd 13, error 0x12 0002"
I have not seen anyone that had the error "failed executing command 16 NvError 0x120002" come away without having to change out the Motherboard. Can't hurt to try again, sometimes it takes a couple tries to make it go. If it doesn't go, maybe you might need a new motherboard.
Danny2 said:
Sorry, I am by no means an expert, but babsector has always fixed the problem for me when the error was " Command Execution failed cmd 13, error 0x12 0002"
I have not seen anyone that had the error "failed executing command 16 NvError 0x120002" come away without having to change out the Motherboard. Can't hurt to try again, sometimes it takes a couple tries to make it go. If it doesn't go, maybe you might need a new motherboard.
Click to expand...
Click to collapse
Then its a dead tablet because the technical assistance on my country doesn`t have motherboards, bad luck then
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.
****************************************************************
* 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 :
]
Enter your SBK:0x9180C201 0x7B22F106 0x7B4D1504 0x62512103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x04280003433fd217
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 . . .
Sorry chap u got faulty memory chip error. Can try acer support, someone else had tab out of warranty last week. Acer repairing for free. Worth a shot!
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Sorry chap u got faulty memory chip error. Can try acer support, someone else had tab out of warranty last week. Acer repairing for free. Worth a shot!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Could you give a link or something?
In germany there is a warranty of 24 months if the producer have given a faulty device.
But I've only time until tommorow xD, so some stuff would help me to get a functionally device .
Fiedler5895 said:
Could you give a link or something?
In germany there is a warranty of 24 months if the producer have given a faulty device.
But I've only time until tommorow xD, so some stuff would help me to get a functionally device .
Click to expand...
Click to collapse
As far as I know you just go to the acer website. Choose "support" from the menu. I've never had to do it myself, so can't help much. The other thing is that it doesn't matter if your tab is out of warranty or not, acer seems to honour it anyway, according to the last few users who've done this.
babsector download no longer available Russian site
Please help can somebody provide me with the babsector.rar (Needed for my Acer Iconia a500) seem like Russian site is no longer available, please somebody help me. Thanks in advance!:cyclops:
Root guide in my Sig 2nd post
Sent from my HTC_PN071 using Tapatalk
BCT create error... Help!!!
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
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
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Same problem
Hello, I have the same problem. can anyone help?
[email protected] said:
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
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
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Click to expand...
Click to collapse
TRY THIS!!!
Worked for me. try this
http://forum.xda-developers.com/showthread.php?t=2617196
[email protected] said:
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
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
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Click to expand...
Click to collapse
TechShui said:
****************************************************************
...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 . . .
Click to expand...
Click to collapse
Sound like a EMMC/ROM problem...Just send it to RMA if you could.
But what if it's out of warranty?
I took out the Mother Board to a local electronics repairman, he blew heat gun over the sandiskNAND memory chip. I put it back together and turned on. To my surprise it worked.
You can find a thread link in my post above for further help.
androidvillage said:
Sound like a EMMC/ROM problem...Just send it to RMA if you could.
Click to expand...
Click to collapse
farhanalisyed said:
But what if it's out of warranty?
I took out the Mother Board to a local electronics repairman, he blew heat gun over the sandiskNAND memory chip. I put it back together and turned on. To my surprise it worked.
You can find a thread link in my post above for further help.
Click to expand...
Click to collapse
Pretty much all 500 and 501 tablets are out of warranty. I believe maybe some few places may have them new, and sell them. But I wouldnt buy one. (hence the RMA post). But technically, if you buy it, it starts the warranty, so indeed you should be able to RMA the purchase.