Database Users

[solved] Flash CWM despite green android bot in recovery?

Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.

First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )

adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?

Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798

Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.

something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!

[Q] Bricked a500- stuck on boot menu.

Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!

boxyJ said:
Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!
Click to expand...
Click to collapse
Sounds like the A500 manager didn't do something right. Happens sometimes.
Here is what I would do. I assume you don't have the Android SDK installed. No need to, as some of the bootloader/CWM packages have the necessary files needed.
1. Boot to the bootloader, select the option "Fastboot Mode"
2. Make sure you have downloaded to PC a CWM package for ICS/JB. Usually the manual packages have the necessary files, such as the CWM image, fastboot.exe, adb, and some dll files. Unzip them to your PC. (Also helps to download a custom ICS or CM10 rom to your sd card first)
3. Open a command window in the same folder you have the files.
4. type "fastboot flash recovery xxxxxxxx.img" (xxxxxxxx is name of cwm recovery img file, do not put the " in) then hit enter.
5. After completion, immediately boot tablet into recovery. I believe holding Vol- and PWR does this. Or, Vol+ and PWR boots to the bootloader menu. Either way.
In recovery, do your wipes and or formats as per ROM installation instructions.
Install ROM
Enjoy. If you have problems locating one of those packages, give a shout back.
MD

Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks

boxyJ said:
Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks
Click to expand...
Click to collapse
No problem. I'll post a link in awhile.
MD

Files
Ok, so here are your files.
Unzip the contents of the zip file to a folder on your PC
Boot your tab to the bootloader menu, select Fastboot.
Connect tab to PC, then wait 30 seconds or so (windows has to recognize it)
Then, go to that folder. Hold "Shift" + "Right Mouse Click".
Select "Open Command Window"
Type in the following;
fastboot flash recovery recovery_thor17_403.img
and hit enter. Should transfer good.
When finished, boot tablet to recovery like I mentioned earlier. DO NOT boot to the system. Or you'll be doing this all over again.
Install ICS or CM10 rom following the instructions on the ROM post. I suggest starting out with Civato's ICS Flex****** rom first, or one of the stock rooted ones.
Should be good...... I hope.
MD

Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?

boxyJ said:
Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?
Click to expand...
Click to collapse
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.

If not, your partitions are probably hosed.
Then it's Timmy Deans Rollback tool time. Will have to turn you over to dibs_nz for that one.
MD

Moscow Desire said:
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.
Click to expand...
Click to collapse
That brings me to the screen "Skrilax_Cz's bootloader V8: Booting recovery kernel image." But it doesn't go any further?

Well crap.
Sounds like some partitions are messed.
Try this NVFlash package;
http://d-h.st/32X
It's a version 3 bootloader using NVFlash. Might work.
Put your tab in APX mode (I believe you press and hold the pinhole reset, then PWR. After 3 seconds, release PWR, 2 seconds later release pinhole. Might have to reverse it, don't remember)
Plug tab in. PC should recognize.
Unzip to a folder, open a command window, and run the batch file (type it into the command window, xxxxxxxx.bat then hit enter)
If there's an error, it should show in the command window.
Here is a link to Timmy Deans roll back package;
http://d-h.st/0x7
The issue here, is you need a UID number, which I HOPE you wrote down when you did the V8 bootloader!
MD

Well I cant manually put it into APX mode, tried a few times. Also there is no bat file in that download... as for Timmy Deans roll back package, is it a simple method taht should work? At this point I just want to get my tab working again . And yes I do have my UID number.

Ok,ok.
So this morning I tried to fix it again. And I think i managed to put it in APX mode. Also, I started up APX flash tool and all, did that. Suddenly a cmd window opened and started doing stuff. And now the tablet says in the top right corner "Acer Iconia APX mode", and a yellow glowing 'acer' title in the middle (which is different from what I've been seeing). Another cmd window opened by itself saying "Nvflash started [resume mode]. Where do i go from here??
Thanks!

So I think I've gotten a better understanding of how this all works today. I've tried multiple ways of flashing recovery imgs ect, flashing the bootloader and all that stuff. And all the times I've done this, it always stops at "Nvflash started [resume mode]" and doesn't go any further.
So I'm not really sure what else there is to do.
Please, I need guidance. (below is my last attempt, and what It said in the cmd window).
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]

Please let us know if/how you fixed this problem! Some of us are in the same boat.

timmytutone said:
Please let us know if/how you fixed this problem! Some of us are in the same boat.
Click to expand...
Click to collapse
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589

dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
Thank you so much for the reply. I gave up this afternoon and just flashed the ota 4.0.3 version from Acer and it seems to be running really good. The only reason I was looking to flash something new is because the update from honeycomb to ics didn't take very well and I've always been dealing with problems from it. If the flashed version is still running well I might not try a different Rom again. I'll be putting your tip in my notes in case I do. Thanks again.

dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.

timmytutone said:
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.
Click to expand...
Click to collapse
Dude I know it's been 4 years since you wrote that but I just wanted to say you really saved my life, THANK YOU!!!
About 2 months ago I tried to unlock my tablet's bootloader but I gave up after reading different articles and obviously ended up with a really bad headache. Last night I realized Android 3 is really old and I almost can't install anything on it. So basically I gave it another shot and been reading and downloading different files for almost 3 hours. Today I managed to unlock bootloader and use your short instruction (more likely a walk-thru that how you fixed your problem) and it worked!!! I owe you man... I owe you
I even took it to so many different mobile centers about 3 weeks ago but they said its files are not anywhere/we can't do it/it's too risky/it's not possible deal with it

Happy to help!

[Q] soft-bricked? my acer iconia a500 please help!

Ok, I seem to be making things worse and worse, so I've come here to beg for help.
TLDR:
my acer iconia a500 was running skrilax_CZ's bootloader V8, I screwed it up (I think) by trying to install ClockworkRecovery.
I was still able to boot into Tegraowners_JB-MR1_ROM_v11t4
I messed a BUNCH more stuff up. a bunch!
Now, I can still see the internal and external SD but when i try to use blackthund3r's tools to root/recovery/custom-mod
it gets stuck when trying to enter APX mode. "No APX devices detected"
I do have the CPUID and the SBK
Longer explanation and details:
I installed Acer's USB drivers: USB_Acer_1.06.1500_A30H_A
I rooted the device using: ICS_rooting_A10x_A5xx --> runit-win.bat
I used blackthund3r's tools: A500APXFlash.exe and A500Manager.exe
I installed a custom bootloader rom: V8-Thor_1.7.3_recovery.a500apx
I installed Tegraowners_JB-MR1_ROM_v11t4 and gapps-jb-20130301-a500-v2
I was happy as a clam for 2 days playing with my fancy tablet.
I installed Superuser App
I made a nandroid backup at least once from the v8 bootloader.
I made a batch Titanium backup
I then tried installing clockwork recovery mod, and I think that's when i screwed myself.
Suddenly the power on + down_volume switch just led to a screen that said "Skrillax_CZ's bootloader V8"
"Booting recovery kernel image" and then it would hang there forever.
I could still boot into Tegraowners_JB-MR1_ROM_v11t4 so I tried to run a restore from Titanium Backup,
it froze halfway through with the message "superuser access denied"
I rebooted, and suddenly most of the widgets/apps are gone, and the back/home/and application navigation
button that are usually on the bottom left corner are also gone!
then I did a bunch of crazy/desperate stuff with blackthund3r's tools, (something involving trebuchet?)
and I finally blacked out amidst tears and despair around 5 am this morning.
so
now, when I use A500APXFlash.exe and A500Manager.exe it tries to put the tablet into APX mode, and the
tablet goes to a blackscreen, with a white LED on the power button, but I get the error "No APX devices detected"
I also tried inserting a paper clip then turning the power on, same result.
I do have the CPUID and the SBK
Please help if you can, and please dumb down your explanations if possible, this is my first tablet and
i'm totally new to android, etc.
Thanks for your time
-Joel
couple more details, it boots to the point where you swipe to unlock it, but when i do, i get a popup that says Trebuchet has stopped,
and when i click ok, it just comes back infinitum
oh, and when i use A500 Manager.exe it says that it's connected and usb debugging is ON, but I have no way of getting into the settings
to confirm that?
I don't want to come across as lazy, I literally have 8 tabs open from xda-developers and 3 from tegraowners. I also just tried afterotav_109 but that didn't do anything.
I found
the following files in
Computer\Acer Iconia Tab A500\Internal Storage\0\.AcerRecoveryInstaller
(see attached picture)
I'm guessing I can't rename recovery.old to recovery, or something easy like that?

small update, installed android SDK and adb shell
when I launch adb shell I can see the various directories on the tablet internal and external SD. I'm in the process of scouring the forums for info about how to use the adb tool to fix my problem, am I even on the right track?
thanks for any feedback y'all can provide
-Joel

j8ner said:
Ok, I seem to be making things worse and worse, so I've come here to beg for help.
Click to expand...
Click to collapse
I'm going to reply to each part of your post, just in case someone else is having the same probs...
Longer explanation and details:
I installed Acer's USB drivers: USB_Acer_1.06.1500_A30H_A
I rooted the device using: ICS_rooting_A10x_A5xx --> runit-win.bat
I used blackthund3r's tools: A500APXFlash.exe and A500Manager.exe
I installed a custom bootloader rom: V8-Thor_1.7.3_recovery.a500apx
I installed Tegraowners_JB-MR1_ROM_v11t4 and gapps-jb-20130301-a500-v2
Click to expand...
Click to collapse
TBH installing T/O's rom you should really be asking on their forum - their roms are a little different to the ones on xda - like, you don't need the v8 unlocked bootloader you can run it on HC or ICS Bootloaders.
android adb/usb drivers?? you dont mention them are they on your PC?
I then tried installing clockwork recovery mod
Click to expand...
Click to collapse
Didnt you already have cwm 1.7.3?
How did you try to install it? and yeh this is probably where you went wrong.
You must install custom recoverys using either fastboot or an appropriate flashable zip
Suddenly the power on + down_volume switch just led to a screen that said "Skrillax_CZ's bootloader V8"
"Booting recovery kernel image" and then it would hang there forever.
Click to expand...
Click to collapse
For future reference what you should have done here is run the 1.7.3.apx with apxflash tool.
I could still boot into Tegraowners_JB-MR1_ROM_v11t4 so I tried to run a restore from Titanium Backup,
it froze halfway through with the message "superuser access denied"
I rebooted, and suddenly most of the widgets/apps are gone, and the back/home/and application navigation
button that are usually on the bottom left corner are also gone!
then I did a bunch of crazy/desperate stuff with blackthund3r's tools, (something involving trebuchet?)
and I finally blacked out amidst tears and despair around 5 am this morning.
Click to expand...
Click to collapse
Yes it gets like that sometimes dont panic its fixable!
so
now, when I use A500APXFlash.exe and A500Manager.exe it tries to put the tablet into APX mode, and the
tablet goes to a blackscreen, with a white LED on the power button, but I get the error "No APX devices detected"
I also tried inserting a paper clip then turning the power on, same result.
I do have the CPUID and the SBK
Click to expand...
Click to collapse
If thats the error it means the drivers are screwed up. Completely uninstall the acer drivers, reboot and reinstall. But w8 theres more....
Make sure you got the adb/fastboot drivers here
Please help if you can, and please dumb down your explanations if possible, this is my first tablet and
i'm totally new to android, etc.
Thanks for your time
-Joel
couple more details, it boots to the point where you swipe to unlock it, but when i do, i get a popup that says Trebuchet has stopped,
and when i click ok, it just comes back infinitum
oh, and when i use A500 Manager.exe it says that it's connected and usb debugging is ON, but I have no way of getting into the settings
to confirm that?
I don't want to come across as lazy, I literally have 8 tabs open from xda-developers and 3 from tegraowners. I also just tried afterotav_109 but that didn't do anything.
I found the following files in Computer\Acer Iconia Tab A500\Internal Storage\0\.AcerRecoveryInstaller
(see attached picture)
Click to expand...
Click to collapse
Acer recovery installer? OK so I assume you used that to try and flash a recovery? This app works best on HC Bootloader - the only way to use it with ICS is IF you already have the v8.
Also, you must make sure you run the correct recovery for whatever version of ROM you are wanting to flash. So check the OP of your chosen rom for which recovery you need. Most of the ics/jb custom roms here on xda work with cwm 1.7.3, TWRP or public recovery. BUT these wont work on HC
I'm guessing I can't rename recovery.old to recovery, or something easy like that?
Click to expand...
Click to collapse
You can use an appropriate recovery.img and flash via fastboot
-------------------------------------------------------------------------------------------
OK so lhow do we get you fixed???
You need to do a complete FORMAT (factory data reset) of your system to get it back to a state where you can use the tools.
Install the adb drivers first!
Lets see if fastboot mode is available.
As long as you see skrilax_cz v8 bootloader on your screen connect yr micro usb cable - power down and boot up holding VOLUME UP button...you should see the fastboot menu now follow the instructions here on using the fastboot commands to WIPE userdata and cache
THEN if you have the correct recovery.img you can flash this too (see that post) if not run the apxflash tool again using cwm 1,7,3.apx file.
Now, once you have run it BOOT DIRECTLY to recovery and flash your rom. (Doesnt matter which one as long as its ICS or JB...)
This is important...if you try and boot yr tabs OS, you'll get either booting primary kernel error or be stuck on the acer logo -
IF fastboot is not available then run the apxflash tool to install recovery instead then using that same post it shows you how to do a full format wipe, with cwm.
I hope this isnt too over the top for you...I've tried to explain things so you can understand a bit better - but I may have to 'dumb' things down a bit more, let me know
good luck with it
dibb

thank you so much for replying, i'll get right on this
Dibb thank you very much, as soon as I get back I'm going to go through your directions step by step.
I really appreciate your help, and I'll post an update later tonight.

in fastboot, please advise
dibb_nz said:
Acer recovery installer? OK so I assume you used that to try and flash a recovery? This app works best on HC Bootloader - the only way to use it with ICS is IF you already have the v8.
Also, you must make sure you run the correct recovery for whatever version of ROM you are wanting to flash. So check the OP of your chosen rom for which recovery you need. Most of the ics/jb custom roms here on xda work with cwm 1.7.3, TWRP or public recovery. BUT these wont work on HC
You can use an appropriate recovery.img and flash via fastboot
-------------------------------------------------------------------------------------------
OK so lhow do we get you fixed???
You need to do a complete FORMAT (factory data reset) of your system to get it back to a state where you can use the tools.
Install the adb drivers first!
Lets see if fastboot mode is available.
As long as you see skrilax_cz v8 bootloader on your screen connect yr micro usb cable - power down and boot up holding VOLUME UP button...you should see the fastboot menu now follow the instructions here on using the fastboot commands to WIPE userdata and cache
THEN if you have the correct recovery.img you can flash this too (see that post) if not run the apxflash tool again using cwm 1,7,3.apx file.
Now, once you have run it BOOT DIRECTLY to recovery and flash your rom. (Doesnt matter which one as long as its ICS or JB...)
This is important...if you try and boot yr tabs OS, you'll get either booting primary kernel error or be stuck on the acer logo -
IF fastboot is not available then run the apxflash tool to install recovery instead then using that same post it shows you how to do a full format wipe, with cwm.
I hope this isnt too over the top for you...I've tried to explain things so you can understand a bit better - but I may have to 'dumb' things down a bit more, let me know
good luck with it
dibb
Click to expand...
Click to collapse
DIBB IS TEH AWSEOMEMEMEST!!!!!!!
fastoot mode worked!
one thing that threw me off is that I had to figure out that I needed to type
Code:
fastboot.exe flash [B]recovery[/B] recovery_thor17_403.img
the guide here
doesn't specify which partition to use so I got an error message until I guesstimated I wanted the boot partition.
Anyway, once you fixed my bootloader, I restored the full system from a backup I had made on the first of the month.
thank you thank you for your awesome help!
now I can break it again and again!
made a minor edit, changed boot --> recovery in the "code" section above

j8ner said:
DIBB IS TEH AWSEOMEMEMEST!!!!!!!
fastoot mode worked!
one thing that threw me off is that I had to figure out that I needed to type
Code:
fastboot.exe flash [B]recovery[/B] recovery_thor17_403.img
the guide here
doesn't specify which partition to use so I got an error message until I guesstimated I wanted the boot partition.
Anyway, once you fixed my bootloader, I restored the full system from a backup I had made on the first of the month.
thank you thank you for your awesome help!
now I can break it again and again!
made a minor edit, changed boot --> recovery in the "code" section above
Click to expand...
Click to collapse
Glad u got it
Not sure why you had to use fastboot.exe as the command tho? but as long as it worked and you're up and running, that's the main thing!
happy flashing
dibb
Edit: have edited guide to show recovery partition - thank for picking that up
Sent from my GT-I9300 using Tapatalk 4 Beta

Windows A500 NVfash Bootloader Script

Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: A500-Bootloader-V9_Babsector
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM: Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji

Omg! Thank you!
Thank you, thank you, thank you. I've been trying for two days to get a custom recovery to install. I too used Blackthund3r's tools, but nothing was working. I think my partition table was screwed. It took me forever just to get the drivers to recognize APX mode. Google's generic driver's > Acers! Again thank you so much.

KaijiKun said:
Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Code:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: http://www.4shared.com/zip/dbt1DsjT/A500-Bootloader-V9-Nvflash.html
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM
Code:
Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
http://www.4shared.com/zip/R6Wn2rFJ/A500-Stock.html
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Nice guide Kaiji...a quick question. Do u know why babsector requires u to run both bat files. A few folks have just run the first one, done the formats then flashed their rom. Seems no one had any problems. Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
Nice guide Kaiji...a quick question. Do u know why babsector requires u to run both bat files. A few folks have just run the first one, done the formats then flashed their rom. Seems no one had any problems. Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thanks
Actually both of those batch files are identical, I believe that the original writer wanted to be sure that any corrupted data, and or partitions were repaired. And that is exactly what they do.What happens is after the tab is in apx mode a temporary rw bootloader image is uploaded, and then the file correctly maps out and create the partitions needed for you tablet, then it uploads the bootloader, and recovery images. now with your new patched bootloader you can boot to custom recovery, install custom ROM's, and you could even install a second OS and set up a dual boot scenario, Skrilax_CZ has some really great tutorials on this here. You will also find that Blackthund3r's tools will also work now too.
- Kaiji

dibb_nz said:
; Nice guide Kaiji...a quick question....... Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you
I am very happy that you, a senior member, actually thinks the guide is good. It really does mean a lot ( to a noob like me
I have actually just been poking around, and learning alI I can. I have always been a big fan of the Linux system, and the fact that it is now, in its Android form so huge world wide, on smartphones, and tablets everywhere is awesome!!
Any way I do really love that Android is based on the open source Linux code, and since it is, it's 100% customizable, hackable, & rewritable, sweet!!.
Oh yeah, To continue on a bit more about babsector, from my last post. The way that babsector actually works is this, while the tablet is is the NVidia APX download mode, the program NVFlash can then upload the special temporary APX mode bootloader image with rw abilities so that NVFlash can then set the partitions, and upload you patched bootloader. At least I believe that is how it all works. As I said I am just poking around, hehehe, an old linux user trying to learn all I can and then pass it on so everyone can enjoy the full potential of their devices.
- Kaiji

Not Working
KaijiKun said:
Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: A500-Bootloader-V9_Babsector
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM: Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks

jd4r said:
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks
Click to expand...
Click to collapse
Hmm, I wonder what the problem could be.... I would say for starters, try reinstalling the drivers, reboot, and try the script again. making sure to runit as Administrator. Also do you have AfterOTA? send me a PM after you try reinstalling your drivers, and if you are still having trouble tomorow, I will PM you my phone # and I will do my best to help you solve this over the phone.
I will be online tomorow around 12:00 noon EDT and will look for your PM and/or a reply
- Kaiji

Thanks.
KaijiKun said:
Hmm, I wonder what the problem could be.... I would say for starters, try reinstalling the drivers, reboot, and try the script again. making sure to runit as Administrator. Also do you have AfterOTA? send me a PM after you try reinstalling your drivers, and if you are still having trouble tomorow, I will PM you my phone # and I will do my best to help you solve this over the phone.
I will be online tomorow around 12:00 noon EDT and will look for your PM and/or a reply
- Kaiji
Click to expand...
Click to collapse
Thanks for your response. I appreciate it. My problem got resolved after running Acera500 flash tool.
Thanks again for your help.

jd4r said:
Thanks for your response. I appreciate it. My problem got resolved after running Acera500 flash tool.
Thanks again for your help.
Click to expand...
Click to collapse
No problem , I am very glad your problems were resolved. And, if you don't mind, I have a few questions for you.
1. What exactly went wrong in your situation?
2. Which tablet are you using?
3. And, how did you solve your problems exactly?
The reason I ask is that each tablet/software combination may each be a little unique, and the details of your experience can be very helpful to others as they encounter their own situation, and most of all we can always learn more from everyones different case, and apply that knowledge to improving the ability to help in the next case. Also, please try to be as detailed as possible, if you decide to answer the questionsI asked.
Thank you very much for your input
- Kaiji

KaijiKun said:
Hi Everyone
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Well it got me from only booting to APX mode to having a bootloader, but I'm still having problems. I ran the script and got the PASS screen. Now it boots to the bootloader but I'm no longer able to use the reset button to get to the APX mode. Even when I hold the reset button while powering on, it just goes to the bootloader. It also does this just powering on without press the -vol button. I'm assuming this was because I was also getting an error message say the Lnx kernel was invalid.
So I went ahead and flashed the A500-stock.zip and no longer get the invalid kernel message but it still boots to the loader menu with the options Primary (LNX), Recovery and Fastboot. But when I choose the first option it hangs on the first screen saying "Booting Android Image from LNX partition..." Revovery takes me to the recovery menu and Fastboot connect me to my PC in ADB mode.
Any suggestion about where I go from here?

4929york said:
Well it got me from only booting to APX mode to having a bootloader, but I'm still having problems. I ran the script and got the PASS screen. Now it boots to the bootloader but I'm no longer able to use the reset button to get to the APX mode. Even when I hold the reset button while powering on, it just goes to the bootloader. It also does this just powering on without press the -vol button. I'm assuming this was because I was also getting an error message say the Lnx kernel was invalid.
So I went ahead and flashed the A500-stock.zip and no longer get the invalid kernel message but it still boots to the loader menu with the options Primary (LNX), Recovery and Fastboot. But when I choose the first option it hangs on the first screen saying "Booting Android Image from LNX partition..." Revovery takes me to the recovery menu and Fastboot connect me to my PC in ADB mode.
Any suggestion about where I go from here?
Click to expand...
Click to collapse
I got APX mode working again. I had to fall back to Win 7. In Win 8 it couldn't find tthe APX driver.
So, I started from scratch and ran the A501.A bat, then formatted the /system twice. Then rebooted into APX and ran the a501.B script and got this error. "Formatting partition 2 BCT please wait... FAILED!" What now????? PLEASE HELP!!!!!

jd4r said:
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks
Click to expand...
Click to collapse
im having the same problem as u were having with the attachments on the error codes u got can u share some light to me on the solution u was told to use

Im about at my wits end and gonna make a paper weight out of this thing I guess. I had recovered it with the Timmy Dean tool once already, and was on HC for about a week. I wanted to upgrade to ICS. So I tried to flash to bootloader but somehow got to where I can only boot into APX mode. I keep hanging on every tool I use. Here is a screen shot of the error when using the babsector in this thread. As far as I know I have the correct drivers from Acers site, but not sure about the adb drivers. I have them, but they don't "install" like the acer drivers did. How do I know they are correct? See my error attached photo. Is it possible to have something so messed up that even though apx mode works, it still wont flash itself out of the problem?

Need help with running A501 A.bat
Hi there. I put my tablet into APX mode by following the instructions above. However, when I run the A501 A.bat script, it reports that "USB device not found"
I have my tablet connected to my desktop via a USB-miniUSB cable. The connection works fine when the tablet is on, but it doesn't register it when the tablet is in APX mode
Any suggestions? Thanks!

romUser1365 said:
Hi there. I put my tablet into APX mode by following the instructions above. However, when I run the A501 A.bat script, it reports that "USB device not found"
I have my tablet connected to my desktop via a USB-miniUSB cable. The connection works fine when the tablet is on, but it doesn't register it when the tablet is in APX mode
Any suggestions? Thanks!
Click to expand...
Click to collapse
Just a couple suggestions, I would start by making sure you have a known good micro USB cable, make sure it's plugged into a USB 2.0 port directly connected to you motherboard and not a USB hub or a USB 3.0 port as those can cause problems. The last thing I would recommend is to use Windows 7. Windows 10 may or may not work with this method as this tablet is pretty old. You can use a virtual machine to run Windows 7 and it should work fine. Hopefully this helps a bit.

turnert said:
Just a couple suggestions, I would start by making sure you have a known good micro USB cable, make sure it's plugged into a USB 2.0 port directly connected to you motherboard and not a USB hub or a USB 3.0 port as those can cause problems. The last thing I would recommend is to use Windows 7. Windows 10 may or may not work with this method as this tablet is pretty old. You can use a virtual machine to run Windows 7 and it should work fine. Hopefully this helps a bit.
Click to expand...
Click to collapse
I am unable to connect directly to the motherboard, as my PC is actually a laptop, and I don't really want to try and open it up. I did manage to use a vm and try this on Windows 7 with no luck . If anyone has any other suggestions I'm all ears. The only thing that I think might be causing these issues is that I'm using a USB 3.0 port (My laptop doesn't have 2.0 ports), so I'll update this reply once I find a computer that has usb 2.0 ports.
Also, do I need to install a custom recovery before running the A500 A and A500 B scripts? Are there tutorials on how to do that? I think I ran into issues last time I tried because I hadn't unlocked my bootloader (tablet wouldn't enter recovery mode). But, if I understand it correctly, the instructions for this thread tell you how to unlock the bootloader, but it also requires the custom recovery or else you lose your stock rom. It's quite a catch 22

romUser1365 said:
I am unable to connect directly to the motherboard, as my PC is actually a laptop, and I don't really want to try and open it up. I did manage to use a vm and try this on Windows 7 with no luck . If anyone has any other suggestions I'm all ears. The only thing that I think might be causing these issues is that I'm using a USB 3.0 port (My laptop doesn't have 2.0 ports), so I'll update this reply once I find a computer that has usb 2.0 ports.
Also, do I need to install a custom recovery before running the A500 A and A500 B scripts? Are there tutorials on how to do that? I think I ran into issues last time I tried because I hadn't unlocked my bootloader (tablet wouldn't enter recovery mode). But, if I understand it correctly, the instructions for this thread tell you how to unlock the bootloader, but it also requires the custom recovery or else you lose your stock rom. It's quite a catch 22
Click to expand...
Click to collapse
Yes you need to unlock your bootloader before you can get a custom rom or a custom recovery. But to do that you need root first. Also when I said connect your USB cable directly to your mother board I meant just any USB port on your motherboard.

turnert said:
Yes you need to unlock your bootloader before you can get a custom rom or a custom recovery. But to do that you need root first. Also when I said connect your USB cable directly to your mother board I meant just any USB port on your motherboard.
Click to expand...
Click to collapse
That would still involve opening up my laptop, no? Also, I don't think that the USB cable is the issue, as I am able to connect just fine when the tablet is powered on, but not in APX mode. Also, I have tried rooting it before with a couple methods, both of which failed in one way or another. I'm open to trying out some other method(s) if you have a suggestion

Hi!
I have a similar problem like other users. Ive try many metods and I cant unbrik my A500. I dont know witch BL etc it has. Ive tried many update.zips but always without result. I can enter in apx mode but no more...
When I run A501A the I have this problem.
* Reboot your tablet into APX mode *
Generate your SBK with your CPUID from here :
Enter your SBK:0x58244C00 0x6309C006 0x2B432404 0xB0512103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x038892484340e057
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) message: nverror:0x8 (0x19000008) flags: 0
Presione una tecla para continuar . . .
-------------------------------------------------------
I cant solve it. Can you help me please.

[GUIDE] Install NvFlash Flatline (become unbrickable!!)

This Optimized Guide is for NvFlash Flatline only! That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.5.
According to this post and this post, it works with the tf300tg as well. Bootloader: 10.6.2.11
Original Thread: http://forum.xda-developers.com/showthread.php?t=2455922
Why install NvFlash?
rayman said:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF300T Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
Click to expand...
Click to collapse
You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
Guide:
1) Download files
NvFlash for windows.
and the TF300 image, which is a custom recovery for the purpose of flashing the AndroidRoot Bootloader.
Place image in ADB folder, and rename it to: flatline_device.img
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power and vol down button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6) Reboot into recovery which should be CWM at this point. Go Advanced -> Wheelie. Accept the warning.
step 1) Flash AndroidRoot BL
The device will shut down, reboot into Android. Then reboot back into recovery.
step 2) Once back in recovery select go to Advanced ->:”Generate wheelie blobs” Be patient here too.
They can be found in the device at /data/media/AndroidRoot" or /tmp/AndroidRoot
You can use ADB to get them:
Code:
adb pull /data/media/AndroidRoot
or
Code:
adb pull /tmp/AndroidRoot
Alternatively, you can use a root file explorer such as ES File Manager. Be sure to copy all of the files out of the directory. Make sure you have root access before you try to search for the files.
Keep this file safe in multiple places.
7)The next section (Accessing NVFlash) is for creating more essential backups with NVFlash.
step 1) Hold down the volume up key while rebooting and the tablet is plugged in via USB. (This may take a few tries to get into APX mode). If you are successful, the screen will be blank and the device name on the computer will be something along the lines of "NVIDIA APX"
step 2) Take the NvFlash tools zip and extract them to a folder. Shift right click in that folder and select "Open Command window here".
step 3) Copy the blob.bin from the Step # 7 above into the NvFlash folder.
step 4) run the command:
Code:
wheelie --blob blob.bin
8) Next we run some commands to get even more backup files. These should all be run from the same command window in the previous step.
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Code:
nvflash --resume --read 14 factory-config.img
Code:
nvflash --resume --read 7 unlock-token.img
These files will be stored in C:\User\AppData\Local\VirtualStore (on the computer)
If they are not there, run a search on your computer for
Code:
*img
9.) Flash any other recovery you want, including TWRP. Be sure it is the correct version for your bootloader.
10.) Store ALL of the img files AND the blob.bin AND all other files in the folder in multiple safe places (email, dropbox, HDD, flash drive, SD card, tape backup, or your favorite plant etc.)
11.) Enjoy the peace of mind that you can now restore your device if you brick it
Hit that thanks button if I helped and also thanks to @bucket81 and of course AndroidRoot.mobi devs @rayman

Recovery
For recovery from a brick when you have already made your NvFlash backups, look here:
As @ebildude123 pointed out, first try
Code:
nvflash -r --download 5 twrp.blob
where the output should be:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
ebildude123 said:
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
If that does not work, try using the method here:
http://forum.xda-developers.com/showthread.php?t=2590450
Thanks to @lj50036 and @bucket81

Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.

nadorf said:
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
Click to expand...
Click to collapse
If you can flash a Tf300t version of CWM recovery to your ME301 then it could work. I dont have a 301, so i cant test it but i dont think it will because this is bootloader specific and the me301 does not have the same bootloader.

Does this work with TF300TG\L?

spider623 said:
Does this work with TF300TG\L?
Click to expand...
Click to collapse
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.

cmendonc2 said:
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
adb devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
Click to expand...
Click to collapse
Think you mean fastboot devices not adb devices

cmendonc2 said:
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
Click to expand...
Click to collapse
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk

spider623 said:
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,

cmendonc2 said:
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
Click to expand...
Click to collapse
No need, they are the same, only difference is one file that you can put in any rom before flashing to her the radio to work, same for the TL
Sent from my Nexus 4 using Tapatalk

Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?

cravinRiboflavin said:
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
Click to expand...
Click to collapse
Well, when you restore, you restore back to ICS bootloader so you will have to reflash the stock JB zips first. I don't think its worth the hassle if you already have them.

Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot

BrakeZ said:
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
Click to expand...
Click to collapse
Since it is also the latest 4.2 bootloader, it should work fine.

cmendonc2 said:
Since it is also the latest 4.2 bootloader, it should work fine.
Click to expand...
Click to collapse
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.

Matatusku said:
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
Installing CM does not change your bootloader, so if you were running the latest Asus firmware before, you should be fine.
To make sure, you can check the bootloader version on the top-left of the bootloader screen.
Sent from my TF300T using Tapatalk

Matatusku said:
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.

cmendonc2 said:
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
Click to expand...
Click to collapse
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)

aminpro715 said:
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
Click to expand...
Click to collapse
Well I'm not experienced with tf700t bootloaders, but it says that it is compatible with bootloader version 10.6.1.14.4. That may be the same as 10.6.1.14.10 but you will have to check in the tf700 forum.

Does not work for me in step 4!
hello
I have followed your tutorial on my Asus TF300T Android 4.2.1 build 10.6.1.27.5.
I installed ADB Fastboot, placed flatline_device.img file in the ADB folder.
When I get to step 4 the fastboot devices command displays the serial number of my tablet but the command to flash the image file does nothing !...
My question is: Should the tablet be rooted for this manipulation? or it could be something else?
Thank you for your help