Database Users

Something Went Wrong w/ Rooting - Please Help!

I seem to be having a little problem here. I've been wanting to root an android device and after reading about how simple and fail proof the TF rooting experience is I decided to take the plunge.
I found a tutorial on another site (I'm not able to post the link because of forum rules) and decided to proceed. I followed the instructions to the letter and got confirmation that the “phone update was successful” but after rebooting the TF is stuck on the “Eee Pad” screen. I’ve tried rebooting into APX mode but the computer doesn’t find the device.
I’ve looked elsewhere regarding how to unbrick the device but every solution that I see requires booting into APX. Please help!
Edit: I'm sure that it's important that you know what exactly I did. The site that I got the tutorial was eeepadhacks dot net. I'm almost positive it's using the Nvflash method.

Posted this in the middle of the night and it's almost off the first page. Bumping it for an answer...hopefully.

You are in the wrong section. Look in the Android Development section. The first topic there is about unbricking your device.
http://forum.xda-developers.com/showthread.php?t=1123429

Not too experienced with the TF, but had the same bootloop type problem on Android phones straight after rooting.
Can you still get into recovery (power off, then hold the power button + volume down until the message shows up, then press volume up)? Try this if you haven't already. If you can get into the recovery you've installed (clockworkmod), you'll be able to flash a new ROM such as Prime and it should be working. If it's the same problem I've run into then it's not bricked, it's just somehow screwed up the original ROM during the rooting process.
Try to get into recovery and let me know. If it doesn't work, then hopefully someone else can help but I wouldn't worry much. It should be relatively easy to fix.

I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714

Thanks for the replies guys. I saw your thread last night Vert and that does seem to be the exact problem that I am having. The difference is that I can't get the TF to turn off.
If I hold the power button until the screen shuts off it just reboots. The only way that I can get the screen to turn off is by holding down the volume up button and the power button simultaneously but that doesn't appear to put it in APX mode. At least my computer doesn't seem to recognize it as such.
My plan is to redo it by following the link that you posted (I saw that last night too) but I don't think there's any way to do that until I can get the TF to show up on the PC. Anyone have any suggestions?

After playing with it for a couple of minutes I've noticed that when I put the TF into APX mode a new entry appears under the USB Controllers. It is called NVIDIA USB Boot - recovery driver for Mobile devices.
Hopefully that is helpful information....
Thanks again!!

Are you on windows 7? If so, open up device manager by going to start menu>right click on computer>manage>device manager. Then hold power/vol up on your transformer until the screen doesn't turn on. Device manager should then refresh. Look under Universal Serial Bus controllers and "Nvidia USB Boot-recovery driver for mobile devices" should show up. This means it is in APX mode. If that doesn't show up try reinstalling the drivers. From there you can run root.bat and it will boot up
Good luck
EDIT:Looks like you got it while I was typing lol

Thanks for your help guys!!
I'm back up and running. I'm not rooted but at least my TF is back alive.
I'll try again later today using that video that you posted Vert.
Thanks to all and enjoy the rest of your weekend!

At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.

poltak11 said:
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
Click to expand...
Click to collapse
Yup, got it all up and running and am happy to report that I am now sporting Prime 1.5 on my newly rooted TF. Thanks again to everyone that helped out!

I had this problem earlier, and I used nvflash to recover. I thought I was not in apx mode as well but I was. Win 7 64 did not show it but when I flashes it worked. Just try it.
Sent from my Transformer TF101 using XDA Premium App

Vertiginouz said:
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
The reason why you forgot may be because in the instructions it tells you to unzip the files higher in the thread before Step 1 begins.
"
extract the file inside the zip to directory root before running root.bat
for ww 8.4.4.11 version. thanks for the help from poet,paddy01,peacemaster,rebound821 provide me the boot file
for tw 8.4.4.11 version thanks for the help from butro for the boot file.
Thanks for the fone_fanatic to do the walkthru.
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.

[Solved] Mystery bricked tablet. Black "android systems" screen

I bought an Acer a500 tablet a few days ago not knowing how broken it is.
After loads of research and attempting different techniques I still haven't had any progress.
The software issue:
When booting up the tablet, it goes to the black screen with "android system" at the top and power off/ shutting down in the middle of the screen.
Fixes I've tried:
1.
Since I don't know anything about what operating system is on this tablet, I have been blindly flashing different "stock" (from Vache) versions of HC.
--The android logo with gears shows up, the green bar loads but freezes when it gets 1 cm away from finishing.
--After turning off the tablet and booting it up again, "updating bootloader shows up on the upper left hand corner of the screen. Then a message pops up saying "apk installer: all pre processes complete". Then it returns to the black screen.
2.
The tablet will not go into apx mode (using the reset botton at the bottom).---Fixed. I didn't execute the steps properly. Apx mode works fine.
3.
I plugged the tablet into an older windows laptop and the computer could not install the correct drivers to sync with the tablet. Again also my lack of knowledge. I installed drivers from Acer.com
4.
These two guides seem to be exactly what my problem is but I can't seem to make sense of them:
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
http://forum.xda-developers.com/showthread.php?t=1572622
This is as far as I've gotten.
Other complications:
--The battery is dead. I have to use it while plugged in by the charger.
--Most of the thread that I have looked at use Megaupload as the source of downloading their files.
--The original owner of the tablet will not help me out. As I stated before, I don't know what version android OS was on here before it was bricked and on top of that the original owner won't answer my questions. As far as I know though, this tablet is not rooted or has anything "non-OEM" installed in it. The story goes that this tablet was bricked when the owner tried to "update" it. Before that, it was functioning perfectly.
-----It looks like Darvis is having the same issue and frustrations I'm having but reading his threads makes me think that this tablet is a dead end.
http://forum.xda-developers.com/showthread.php?t=1427983&page=4
http://www.androidtablets.net/forum...32467-please-help-me-unbrick-my-iconia-5.html
If someone could point me in the right direction toward fixing this tablet, I would appreciate it very much.
Thank you for reading my Thread.

KiwiN said:
http://forum.xda-developers.com/showthread.php?t=1572622
Click to expand...
Click to collapse
First off......I hope u didn't pay much for the tablet.
Secondly the guide above looks pretty straight forward but maybe this is one of the ones that has files at megaupload?
I know that the ra recovery and timmydean's files are accessible as I have downloaded both of them.
Maybe someone who has done this previously will chime in and get you the other file if it is indeed unreachable.
Sent from my A500 using xda premium

I would suggest trying to connect the tab to a Windows 7 PC after installing the USB drivers from ACER. Then check if your device appears in the device manager. As long as you have its UID you can flash the tab from the PC with one of the EUU tools - check my signature on "how to revert to 3.0.1" or TimmyDean's thread which offers an EUU with rooted HC 3.2.1 (it's linked in my thread as well).
How exactly did you try to get into APX mode?
p.s. I have the EUU files if you can't access them from the threads links. I can send them to you.

getting into apx mode
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
I'm trying to follow the instructions from the root 3.2.1 v4 file.
I can't perform the first step where it instructs me to turn on Usb debugging. The problem is that I can't open the settings by clicking the clock. Nothing happens.
I realize that one complication of my tab is that it will not charge. The battery power is below 15% so none of these fixes might not be effective for me. That might be the ultimate problem?
CyaN1de-
I paid $100 for the tablet. As of this moment I feel like I paid too much.
Thank you both for you quick replies. I have to say that most of the problems that I'm having is because of my lack of experience but I'm learning. I hope I fix this tab soon.

if this dont fix it, i'll give you what you paid for it;0
someone posted a while back that a hard reset fixed the android systems screen error
not sure where you're at now but no harm in trying it
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock s to your left;
3) Press Vol+ (which is next to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and you
should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.

Thanks for the suggestion but I didn't accomplish anything by hard resetting it. I've done this many times and nothing has changed.
I haven't given up on unbricking this tablet yet and even though it's frustrating I'm learning from the process. If I decide to sell it, I'll contact you Dibb.

KiwiN said:
.....
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
Click to expand...
Click to collapse
i've seen the 2 methods u described but i've not seen anyone else have success with it apart from the OP'ers - seems OTT to me but hey if it works for ya...
I've used timmydeans method ALOT on HC it never failed to work and that includes reverting back to HC from ICS - if it doesnt work for your issue then id be tempted to use blackthund3rs APXFlash Tool and civato's HC_ICS_Bootloader zip to flash a new bootloader and rom package on yr tab - but for the moment we'll run with td'sv4 - if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
as i said this is worth a go,,,,how about the update.zip have u tried that.....
else the only other way i know is apx flash....ya still need to get into apx
mode and if u cant then ???? sometimes youll try something over and over
and then out of the blue it will work...you'll swear you never did anything different , it jsut worked this time.....
hope you find some joy

Thanks Dibb for your words of wisdom. I've put it aside for now but I'm going to pick it up in the morning.

As addition to what dibb_nz said - Windows 7 would do the trick - I'm almost 100% sure you'll be able to connect in APX mode with the drivers properly installed. Then use one of the EUUs.
Drained battery really looks like the ultimate problem now because as far as I know you cannot charge the tab in APX mode - haven't tried that. Eventually I would suggest to crack the tab open, remove the battery and charge it somewhere - I don't know alternative ways but...may be another tab or you own charger with proper connector ...
http://www.youtube.com/watch?v=xvXihNIdQ1M
p.s. 15% power ... seems enough to flash through the PC...but who knows - don't waste them and get everything you need before starting the procedure.

no probs m8 hope u have better luck tomorrow
if u wanted to try the EC method i have those files if you want them
good luck m8

dibb_nz said:
if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
hope you find some joy
Click to expand...
Click to collapse
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.

KiwiN said:
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
Click to expand...
Click to collapse
do u get on yr tab the big 'PASS' in white leetters or "entering download mode" at all???
think we're beyond update.zip if EUU failed but you can try it -
you can get to apx which is a start - getting a new boot/recovery image on there is the main priority I think...as i posted earlier i've only ever seen a fix for this problem work for 2 people, so on new ground here....
But anyway check out the APXFlash method/walkthru in my sig....all the info is in there and the links to the required files ....do we know if you're on HC or ICS B/L????

I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
dibb_nz said:
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????
Click to expand...
Click to collapse
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.

KiwiN said:
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen.
Click to expand...
Click to collapse
I could never get mine into apx mode with the usb cable plugged in. So try that if you haven't. And it is literally hold reset, then press power, without letting up on the reset, release the power button after 3 seconds (use a watch or timer!) then one more second before you release the reset... It does work, but the timing has to be close. It must have a tenth of seconds or less tolerance. Very picky... I've done it on 2 different a500s so far and I am heading to do another tonight. If it doesn't work I'll be right back!!!

KiwiN said:
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
Click to expand...
Click to collapse
Hi m8 Hwya goin - just got home - what's the lay of the land???
Holey motley we just had a good shake....thort was gonna carry on thank fk it stooped, phew, just been awhile since we had one like that, scary
Crikey just as I finished typing "....land"
Back to more important matters..... whr u at m8????

None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?

KiwiN said:
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
Click to expand...
Click to collapse
recovery mode???
u need a new boot and recovery image on that thing
the HC EUU based flash arent working even tho u got a PASS on screen after TDv4
So HC based methods arent up to it. You need nvflash/fastboot.
We need ICS with the unlocked bootloader it has access to another level below where HC worked because HC b/l is and always has been locked down.
If ICS cant fix it, I have no idea what will and my offer to buy is off the table!!!!
check out civatos guide and ready yourself for nvflash via zip files in that post or blackthund3rs APXflash tool, with a complete tutorial for using it, all links in my sig.
good luck

Just to chime in with a tip on getting google drivers to work.
When getting any device not recognized, or driver error, generally I go into windows device manager, select the unknown or offending device, update driver, only I choose which driver to use, and ignore the error message where it says "may not be compatible with your device", and use it anyhow.
I get that occassionally when swapping back and forth between devices.
Also, battery not charging and display errors, are usually a sign of EC Power control. So you were on the right track about that. Once you get a rom up and running, if the batt don't charge, then there are some EC flash's you can do from CWM.

Back at it again using BT's nvflash tool. And tablet is still bricked.
I've tried a few different bundles and none allow me to operate the tablet. Everything goes smoothly and I get "pass" at the end of the process. When I go to reboot the tablet, it gets stuck at the black start up screen.
Found another lead: http://forum.xda-developers.com/showthread.php?t=1579490
Sounds like he was in the same situation as I am but has a bit more skills and knowledge dealing with problem solving.

You say you were able to flash roms. So apparently recovery is working OK. Have you tried flashing civato's flexreaper? It has code that will detect whether you bootloader is HC or ICS. You may just be flashing a rom that doesn't match your bootloader... I know I'm jumping into the middle of this, but it's just a thought.
Also, when you did the hardware reset with the rotation lock switch did you get the confirmation that it was, in fact, being wiped?
Failing all that, I'd be willing to take it off your hands for spare parts...
Sent from my A500 using Tapatalk 2

SOD and no root and unable to connect to a pc!

Ok so I was running taboonay 3.0d and I thought I'd have a go at Thor's rom. Flashed it wasn't really into it few things missing that I like in taboonay. So I then restored my back up. All hunky dory.
I then flashed a zip for scrillax v8 bootloader. It seemed to work fine, tablet boots up and rom running fine. I then tried to get to recovery and it's just not happening. Acer recovery says it cannot get root access. When I reboot I can get into the bootloader menu but none of the commands work. I can't get into the recovery menu at all no matter what I do. So then I figured I'd give Blackthund3r's root tool a go. Got everything ready on the pc including latest acer drivers. Now the tab isn't showing up on the pc either. I know some others have had similar problems but no solution was found in the other threads and considering that I probably screwed up badly somewhere along the way I thought I'd start this thread where you can all point out my ignorance and stupidity without bothering anyone else :silly:
Any help?

Any advice at all would be great, I have reinstalled drivers for tab but still no go! I'm on a old xp pro laptop. Everything else connects to the usb port and the cable is working fine

If you can't get to Recovery, you will need to reflash that.
But first thing is first. And that's the driver issue.
With the tab plugged into the PC, go to Device Manager, and see if it reflects there. If not, you will probably have to reload the drivers. You have a choice, which is the Acer Driver installation, or you can try the Google USB Android drivers. Generally I have had not much luck letting windows search the PC, so I usually install them manually. You can either;
a. Direct device manager to look in a specific folder for the google drivers, or;
b. In Device Manager, when you choose update drive, use "select from list" and see if the acer drivers show up there.
Generally, when you install the acer drivers, you should "right" mouse click the install file and select "run as administrator".
MD

Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.

irishmoe said:
Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.
Click to expand...
Click to collapse
Ok, now I run Win 7. But XP should be similar.
Are you saying in device manager, you do not have a device with an exclamation mark when you plug the tab in???
If you do, then right click the exclamation mark, select properties. Then the Tab "driver". Next, select "update driver". Then, "browse my computer for drivers". You should get the option to "select from a list".
If your PC does not detect the tablet at all when you plug it in, then it';s a different issue. It's what we call a USB Brick. At first guess. Usually easy to fix on the 500.
Can you start your tablet in APX mode? hold the pin reset, press and hold pwr. Count to 3, and release pwr, then 1 second later, release the pin reset. You should have a black screen with the pwr lite on.
I'm thinking you might want to do the manual flashing of the bootloader + 1.7.3 recovery. Obviously the bootloader V8 flashed, or it wouldn't work at all. Civato has instructions for manual flashing of the bootloader and recovery. Note that I HOPE you wrote down your UID number somewhere. As you will need to convert it to the SBK.
MD
EDIT. One more note. When you boot to the bootloader menu, in your case, probably the only option that will work is "fastboot mode". When you select it, the menu should go away, and it should say "fastboot mode". Then plug into PC and see if windows detects it in device manager. If so, you can fastboot a recovery image to it. Note, that for fastboot to work, you must have the Android SDK installed on your PC. Because you will have to run the fastboot commands from a command window. But for now, check to see if you get to fastboot mode on the tablet.
Sorry I can't spend a lot of time, as it';s late in moscow. Job tomorrow. But Skirlaz_CZ can give you the commands to fastboot a recovery in his bootloader thread.

Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
Ouch! No UID numbers. That hurts. Look in your old CWM recovery backups (if you have) on your EXT SD Card. If you were at one time running a more recent version of CWM, You might have them in the recovery folders. The more recent recovery programs in the backup folders, it's called UID.txt. You have to have this if you use NVFlash. No way around that.
With Fastboot, you don't need it, as you will fastboot the recovery image. If successful, that should allow you to boot to recovery, and flash one of the custom roms. Make sure you do your wipes as in the Rom install instructions. I use CWM 1.7.3 (I've been too busy to try EZTerry's or the TWRP versions. But CWM works good so far.
If not, well, there;s always the update.zips to get a stock ICS on your tab.
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD

Moscow Desire said:
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD
Click to expand...
Click to collapse
You're not wrong there! I'm doing the whole ikea/home improvement thing with the family today. I'll try the fastboot later
Again I really appreciate the help.

Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl

irishmoe said:
Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl
Click to expand...
Click to collapse
HA HA! Yep, gotta have the SDK for ADB and Fastboot. I posted some instructions yesterday about flashing recovery via fastboot.
http://forum.xda-developers.com/showpost.php?p=29294671&postcount=6
You should be able to do it if you already have V8 Bootloader.
MD

Nice one MD going to try it out.

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388

irishmoe said:
Nice one MD going to try it out.
Click to expand...
Click to collapse
Waiting for an update

blackthund3r said:
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388
Click to expand...
Click to collapse
Ha ha cheers mate! Like I said I'm a simpleton but not quite that bad.
Thanks for all the good work. I was actually following another thread stupidly when I should have been following yours.
MD - was away for a few days, just back but have had a few beers so not doing anything stupid tonight. Got sdk installed.

MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device

irishmoe said:
MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device
Click to expand...
Click to collapse
Sorry I was away. Did everything work ok for you? All running? (been trying to chase down my rom issue)
If it says "waiting for device", then you need to check your device manager, and make sure the correct driver is recognized. (APX, Fastboot, Recovery, Download, etc). Usually, I can change drivers while this is happening, and the process will complete.
MD

ok I don't mind admitting that I'm totally lost here. Nothing resembling the tab is showing up device manager so how can I check the drivers?I've been playing around with device manager for a while now and I can't find any way to do what you suggested
I've uninstalled and reinstalled the drivers again and again. Nothing! Could it have anything to do with me having a gateway? I wouldn't think so because they're the same inside.

Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do

irishmoe said:
Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do
Click to expand...
Click to collapse
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.

dibb_nz said:
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.
Click to expand...
Click to collapse
Ok ok boot/recovery driver? You've lost me there chap! Xp device manager is showing nothing tab related. Tell me what to do and I'll give it a blast.
I'm using the regular usb slot as opposed to the mini cause I've no mini cable. That should be ok right?

[Q] Iconia500 shows white power light but no screen or vibrate

My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris

CKM80 said:
My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris
Click to expand...
Click to collapse
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb

Thanks for your reply and your advice! It is nice to have the confirmation about what the problem is, and a step by step guide to start tackling it. I feel a bit less lost now I'm going to try to follow your steps and will let you know if I get stuck anywhere.
- Chris

next steps?
Ok, so somehow (a miracle I guess) I managed to do your steps:
- installed ubuntu
- followed srbeen's steps upto the point where I got my CPUID
- got my SBK
- downloaded babsector.rar (luckily chrome offered to translate the russian site I found it at)
- unrarred it
- downloaded a ROM from http://forum.xda-developers.com/showthread.php?t=1935582 (is this an appropriate ROM?)
- unzipped the ROM and copied it to the external micro SD card
Can you point me in the right directions for the next steps?
Thanks,
Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse

Next steps?
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse

CKM80 said:
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
Click to expand...
Click to collapse
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.

I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Thanks,
Chris
ps. my tablet was never rooted, so I don't know if that complicates the matter... it does say that it needs to have been rooted to choose the dump option. Moreover, I never was able to turn USB debugging on, because I don't have access to the tablet. It does nothing besides black screen and occasionally the "Enter download mode" (but not with these steps)
dibb_nz said:
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.
Click to expand...
Click to collapse

CKM80 said:
I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
Click to expand...
Click to collapse
yep thats correct
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
Click to expand...
Click to collapse
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Click to expand...
Click to collapse
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80

Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
dibb_nz said:
yep thats correct
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80
Click to expand...
Click to collapse

CKM80 said:
Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
Click to expand...
Click to collapse
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb

Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
dibb_nz said:
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb
Click to expand...
Click to collapse

CKM80 said:
Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
Click to expand...
Click to collapse
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!

Yeah, I think I'll try a couple of times, but I am pretty much ready to give up.
Thanks for all your tips along the way.
- Chris
dibb_nz said:
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!
Click to expand...
Click to collapse

Cant Flash Custom Bootloader/Recovery on A500 (ICS OTA 4.0.3)

So ive been trying for almost a week now trying to put a custom ROM on my Acer Iconia A500, but my tablet doesnt want to do cooperate. I have tried EVERYTHING, from using blackthunders APXFlash tool to NvFlash and everything. My problem is my computer will pick up my tablet once its in APX mode. I go to my "Devices and Printers" and under everyting it has a picture of a object and under it, it says "APX". Also in the bottom right corner of laptop theres the "Usb" icon and if i click on it, it says "Eject APX", so i know my computer knows what it is. but no matter WHAT program i use, my A500 never gets any white text on it when its trying to go into the bootloader or anything. i can only get to the point where my device is in APX mode.Nothing seems to work AT ALL. And all the programs get to the point of trying to flash the bootloader and thats it. They just stop working or cant go any further for some reason. I also deleted my "boot.p" file in /system as well. I got my CPUID, i got my SBK, i got all of that using Afterota program. My tablet IS ROOTED. So im stuck right now. Tablet runs fine and good. Just dont wanna give up and really needing some help. Heres my tablet info:
Tablet Cpuid : 037C61C9408103D7
Tablet Sbk : 0xE4531F00 0x18070000 0xF74EE402 0x11DE2003
Android Build : Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
I also tried downloading the "babsector.rar" file from the russian website and it says the file was removed, id SO GREATLY appericate it if someone who has it could re-upload it somewhere else or gimme a good working downloading link for it. One again please help me out if you have ANY suggestions or know how to fix my issue. THANKS

RECKLESS PAIN said:
So ive been trying for almost a week now trying to put a custom ROM on my Acer Iconia A500, but my tablet doesnt want to do cooperate. I have tried EVERYTHING, from using blackthunders APXFlash tool to NvFlash and everything. My problem is my computer will pick up my tablet once its in APX mode. I go to my "Devices and Printers" and under everyting it has a picture of a object and under it, it says "APX". Also in the bottom right corner of laptop theres the "Usb" icon and if i click on it, it says "Eject APX", so i know my computer knows what it is. but no matter WHAT program i use, my A500 never gets any white text on it when its trying to go into the bootloader or anything. i can only get to the point where my device is in APX mode.Nothing seems to work AT ALL. And all the programs get to the point of trying to flash the bootloader and thats it. They just stop working or cant go any further for some reason. I also deleted my "boot.p" file in /system as well. I got my CPUID, i got my SBK, i got all of that using Afterota program. My tablet IS ROOTED. So im stuck right now. Tablet runs fine and good. Just dont wanna give up and really needing some help. Heres my tablet info:
Tablet Cpuid : 037C61C9408103D7
Tablet Sbk : 0xE4531F00 0x18070000 0xF74EE402 0x11DE2003
Android Build : Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
I also tried downloading the "babsector.rar" file from the russian website and it says the file was removed, id SO GREATLY appericate it if someone who has it could re-upload it somewhere else or gimme a good working downloading link for it. One again please help me out if you have ANY suggestions or know how to fix my issue. THANKS
Click to expand...
Click to collapse
First of all thanks for an informative post!! I wish everyone gave as much info as you One thing you didn't mention was which PC OS you are using - 32bit are best
My problem is my computer will pick up my tablet once its in APX mode. I go to my "Devices and Printers" and under everyting it has a picture of a object and under it, it says "APX". Also in the bottom right corner of laptop theres the "Usb" icon and if i click on it, it says "Eject APX", so i know my computer knows what it is.
Click to expand...
Click to collapse
Right, everything is in order here, you're seeing exactly what you are supposed to
So now we need to know "what" doesn't "work".
The babsector file is best for trouble shooting as it will always post some sort of output. Its in post2 of the root guide in my sig.
1. Put your tab in apx mode and connect your "micro usb cable" to your pc
2. Run the first .bat file of babsector.
Now what exactly happens next, can you post a screenshot?
Can't help much further until you do this!!
If the first .bat file runs ok, you need to boot directly to cwm which babsector has just flashed.
Do a nandroid backup and then
a complete wipe including /data/media - you need to go in and specifically enable this from the 'mounts' menu. Wipe davlik and cache too.
Now flash your custom rom and power down.
Back into apx mode and run the 2nd .bat file.
Reboot and voila! you should be all good - fingers crossed!!!

dibb_nz said:
First of all thanks for an informative post!! I wish everyone gave as much info as you One thing you didn't mention was which PC OS you are using - 32bit are best
Right, everything is in order here, you're seeing exactly what you are supposed to
So now we need to know "what" doesn't "work".
The babsector file is best for trouble shooting as it will always post some sort of output. Its in post2 of the root guide in my sig.
1. Put your tab in apx mode and connect your "micro usb cable" to your pc
2. Run the first .bat file of babsector.
Now what exactly happens next, can you post a screenshot?
Can't help much further until you do this!!
If the first .bat file runs ok, you need to boot directly to cwm which babsector has just flashed.
Do a nandroid backup and then
a complete wipe including /data/media - you need to go in and specifically enable this from the 'mounts' menu. Wipe davlik and cache too.
Now flash your custom rom and power down.
Back into apx mode and run the 2nd .bat file.
Reboot and voila! you should be all good - fingers crossed!!!
Click to expand...
Click to collapse
OK so when I put it in APX mode and connected to it, I ran the "A501 A" file and entered my SBK. But when I hit enter it will work just fine alllll the way up til it says something about sending file to bootloader, and then just fails. This is the SAME thing that happened when I use NvFlash and APXFlash! None of them can seem to access my boot loader and I never get anyway white text on my Acer saying it is! So idk what to do! I can't post any screenshots at the moment since I'm not home right now. I will once I get home. Also I can't even enter stock recovery on my tablet! I turn it off, and as its turning back on I hold the "Power" and "Volume Down" button, but just boots normally.....so Idk if this has to do with the problem or not....
Sent from my XT912 using Tapatalk

NEVER MIND GOT IT WORKING!!!!!! THANK GAWD. I just reinstalled the drivers and apx drivers and when i loaded up the a501 A file it sent everything correctly and smoothly! Now running a custom ROM! THANKS A MILLION!!!!!!!(;

Not for me =(
RECKLESS PAIN said:
NEVER MIND GOT IT WORKING!!!!!! THANK GAWD. I just reinstalled the drivers and apx drivers and when i loaded up the a501 A file it sent everything correctly and smoothly! Now running a custom ROM! THANKS A MILLION!!!!!!!(;
Click to expand...
Click to collapse
Well that sux because I thought we were on the same page, except you got it working. I get stuck on uploading the bootloader stage 2 in apx program.
Also when I try to load recovery.
It does a laying down android with a triangle and a exclamation point in it.
I found the cpuid from navigating to the android file folders.
0428004342e0e297 which converts to this
0xC7E2C201 0xDBFDC006 0xDB922404 0x44312103
Is there a way to verify that I do in fact have the correct one?
I really want to update my rom, but I don't know what I'm doing wrong.

vicviper74 said:
Well that sux because I thought we were on the same page, except you got it working. I get stuck on uploading the bootloader stage 2 in apx program.
Also when I try to load recovery.
It does a laying down android with a triangle and a exclamation point in it.
I found the cpuid from navigating to the android file folders.
0428004342e0e297 which converts to this
0xC7E2C201 0xDBFDC006 0xDB922404 0x44312103
Is there a way to verify that I do in fact have the correct one?
I really want to update my rom, but I don't know what I'm doing wrong.
Click to expand...
Click to collapse
What I did was went to the Acer website and found my tablet and installed the HoneyComb driver that was right under my ICS firmware. (Since they didn't have any drivers for the latest ICS OTA 4.0.3) which these drivers will work fine. Next after I reinstalled those drivers I put my tablet in APX mode, connected it to my laptop. Made sure in the bottom right hand corner it had installed the APX drivers successfully and made sure under the usb icon it.said "APX". I then flashed the a501a file first and it went through and worked! Them from there I went to wipe what I needed and installed my custom rom!
Sent from my XT912 using Tapatalk

vicviper74 said:
Well that sux because I thought we were on the same page, except you got it working. I get stuck on uploading the bootloader stage 2 in apx program.
Also when I try to load recovery.
It does a laying down android with a triangle and a exclamation point in it.
I found the cpuid from navigating to the android file folders.
0428004342e0e297 which converts to this
0xC7E2C201 0xDBFDC006 0xDB922404 0x44312103
Is there a way to verify that I do in fact have the correct one?
I really want to update my rom, but I don't know what I'm doing wrong.
Click to expand...
Click to collapse
two tools in my root guide for sbk check and while you're there read up about the boot.p file if you ever want to get past the dead android screen, everything is explained in the first post