Not new to root, new to iconia - Acer Iconia A500

Ok, here is what i have , I have a IConia a500 rooted with, link for forum and files, using ICS Root
(came with 3.1, ran all the iconia updates, to 4.0)
everything went fine, now... i am familiar with flashing roms, i have had a few android phones and have rooted them, and flashed custom roms on them. that is what i want to do with this, after doing over 4 hrs of reading, I have confused the crap out of myself. there is a lot of talk about things that i dont know much about..
-CPUID's
-ICS recoverys (bootloaders?)
Basically, all i want to do is add the CM Jelly time mod, but im not 100% on how i go abouts that? what do i need? i have the files and gapps, etc., i know i need a full wipe, but what recovery do i use? CWM? do i temp flash it or, pernament? after watching a few videos, i still dont think im ready, i diont want to brick this thing. i just want it to work with that rom. thanks any help and clarity is severly appriciated!
j

1. get yr cpuid and save it multiple places open a file explorer and go to /sys/firmware/fuse/acer_cpuid
2. then go to /system and rename/delete recovery-from-boot.p file - this will prevent your custom recovery being overwritten with the stock recovery.
3. have your custom rom on yr ext SD card, ready to flash ONCE you've flashed the unlocked bootloader
4.To flash the v8 bootloader you need to use nvFlash and there are a couple ways if going about that...
a) manually by using the guide in the OP of civato's BL thread
b) using one of the auto tools like afterOTA or apxFlash - links also in that same post...
c) you'll also get to pick a custom recovery and it will be flashed at the same time - cwm 1.7.3 is recommended until you're running stable
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
5) once flashed, boot straight to recovery
6) Do a nandroid backup then the wipes
7) Flash the rom
8) Reboot to recovery and wipe again
9) Job Done!
notes:
Everything you need to do this is in civato's BL OP - sorry can't post the link but its stickied in the Dev Forum
the afterOTA tool,
- saves all yr uid details etc in a txt file
- flashes v3 bootloader -
- it also installs the needed drivers too
- its pretty good at what it does...
seems some are having wifi issues with jellytime but the dev is working on this
you've done the right thing by asking questions before attempting anything, wish everyone was like you...if my post isn't clear then please let me know....for those of us used to the way things work with our Acer, its hard to remember how difficult it seemed when we were new!!
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2

dibb_nz said:
1. get yr cpuid and save it multiple places open a file explorer and go to /sys/firmware/fuse/acer_cpuid
2. then go to /system and rename/delete recovery-from-boot.p file - this will prevent your custom recovery being overwritten with the stock recovery.
3. have your custom rom on yr ext SD card, ready to flash ONCE you've flashed the unlocked bootloader
4.To flash the v8 bootloader you need to use nvFlash and there are a couple ways if going about that...
a) manually by using the guide in the OP of civato's BL thread
b) using one of the auto tools like afterOTA or apxFlash - links also in that same post...
c) you'll also get to pick a custom recovery and it will be flashed at the same time - cwm 1.7.3 is recommended until you're running stable
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
5) once flashed, boot straight to recovery
6) Do a nandroid backup then the wipes
7) Flash the rom
8) Reboot to recovery and wipe again
9) Job Done!
notes:
Everything you need to do this is in civato's BL OP - sorry can't post the link but its stickied in the Dev Forum
the afterOTA tool,
- saves all yr uid details etc in a txt file
- flashes v3 bootloader -
- it also installs the needed drivers too
- its pretty good at what it does...
seems some are having wifi issues with jellytime but the dev is working on this
you've done the right thing by asking questions before attempting anything, wish everyone was like you...if my post isn't clear then please let me know....for those of us used to the way things work with our Acer, its hard to remember how difficult it seemed when we were new!!
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks !
i have used the afterOTA and it would let me select the recovery i wanted to boot, is this permanent or temp? right now on my phone its the cwm, but i remember on my Nexus S, they recomended just pushing it, that way it was super hard to brick.. basically i just need to know if i need to run the afterOTA tool everytime i wanna boot into recovery? thats why i like my CM 10 for my Galaxy Nexus, i can choose to boot into it,
I think the hardest part of these simple tasks, is that there a 20 steps to something totally new, I used to unlock iphones for a living, I never knew what i was doing exactly, i had a rough idea, but i did know how to cut and paste. even going from my NS to GN its always been a few hrs to root/unlock, Being familiar with a lot of the steps, theres more with this tablet! EI, CPUID, APX? tons of warnings! the other things are the abriviations, they can be confusing.. soo
this is the only thing i didnt understand, does the OP dumb it down, or can you??
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
what is sbk, and why do i need it?
thanks again, i really appriciate it!
also, what is a LEAK? leaked rom?

jerkwagon said:
ok, thanks !
i have used the afterOTA and it would let me select the recovery i wanted to boot, is this permanent or temp? right now on my phone its the cwm, but i remember on my Nexus S, they recomended just pushing it, that way it was super hard to brick.. basically i just need to know if i need to run the afterOTA tool everytime i wanna boot into recovery? thats why i like my CM 10 for my Galaxy Nexus, i can choose to boot into it,
Click to expand...
Click to collapse
no m8, once you've 'flashed' via the tools its permanent -
there are flashable zips around (for recovery) but again, you need the unlocked bootloader first....once you have it then you can flash anything, anyhow you like. Even Acer Recovery Installer will work fine and you can flash a rom from there too, though that may require the paid version from memory.
the only time you will 'lose' the unlocked bootloader/recovery is if you need to rollback to HC - specifically 3.2 -
I think the hardest part of these simple tasks, is that there a 20 steps to something totally new, I used to unlock iphones for a living, I never knew what i was doing exactly, i had a rough idea, but i did know how to cut and paste. even going from my NS to GN its always been a few hrs to root/unlock, Being familiar with a lot of the steps, theres more with this tablet! EI, CPUID, APX? tons of warnings! the other things are the abriviations, they can be confusing.. soo
Click to expand...
Click to collapse
yeh I'm hearing you - this thread is a perfect example!!! I'd love to be able to say...root it, then flash cwm and the unlocked bootloader IF you want it, lol
Acer locked this baby down tight as - and if it werent for the work done by alot of the devs here, we'd still be stuck on factory stock.....The success these devs had is proved by the fact that there are still so many new folks coming here looking for info and help
this is the only thing i didnt understand, does the OP dumb it down, or can you??
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
what is sbk, and why do i need it?
Click to expand...
Click to collapse
sbk = secure boot key....as you've discovered 'root' just isnt enough to flash anything...to flash anything you need nvididas nvFlash program PLUS the key to unlock the encryption which is hardwired into the ROM of the memory chip itself -(haahhhaa I think thats right) - The CPUID is unique to every tab (and this too may be hardwired into the chip as well) the sbk is a hex number based on the uid. there are a couple of generators around to do this for you, blackthund3er has one and so does vache....you've used afterOTA so this does the genration for you automatically - you can see it in the text file you saved
thanks again, i really appriciate it!
also, what is a LEAK? leaked rom?
Click to expand...
Click to collapse
yeh back in the day before acer released ics, 'someone' got hold of a leaked ics version, and this is where alot of the work was done on unlocking the bootloader...by the time acer got round to releasing ics - we had a more stable version than they ever had
So now you're unlocked and rooted, have all your ID's backed up and done a nandroid you can quite happily flash to your hearts content!!!!:good::good::good:
rgds dibb

dibb_nz said:
no m8, once you've 'flashed' via the tools its permanent -
there are flashable zips around (for recovery) but again, you need the unlocked bootloader first....once you have it then you can flash anything, anyhow you like. Even Acer Recovery Installer will work fine and you can flash a rom from there too, though that may require the paid version from memory.
the only time you will 'lose' the unlocked bootloader/recovery is if you need to rollback to HC - specifically 3.2 -
yeh I'm hearing you - this thread is a perfect example!!! I'd love to be able to say...root it, then flash cwm and the unlocked bootloader IF you want it, lol
Acer locked this baby down tight as - and if it werent for the work done by alot of the devs here, we'd still be stuck on factory stock.....The success these devs had is proved by the fact that there are still so many new folks coming here looking for info and help
sbk = secure boot key....as you've discovered 'root' just isnt enough to flash anything...to flash anything you need nvididas nvFlash program PLUS the key to unlock the encryption which is hardwired into the ROM of the memory chip itself -(haahhhaa I think thats right) - The CPUID is unique to every tab (and this too may be hardwired into the chip as well) the sbk is a hex number based on the uid. there are a couple of generators around to do this for you, blackthund3er has one and so does vache....you've used afterOTA so this does the genration for you automatically - you can see it in the text file you saved
yeh back in the day before acer released ics, 'someone' got hold of a leaked ics version, and this is where alot of the work was done on unlocking the bootloader...by the time acer got round to releasing ics - we had a more stable version than they ever had
So now you're unlocked and rooted, have all your ID's backed up and done a nandroid you can quite happily flash to your hearts content!!!!:good::good::good:
rgds dibb
Click to expand...
Click to collapse
ok after OTA generated my sbk and all that info, saved it to my computer... how do i unlock the bootloader? i want to install CWM, do i just need to download a file then use the advanced tab?, from cwm im sure i can get around, also, i dont know what apx mode is, ill do some more searching, thanks again.
ok this is really hard to do with windows8, my god, i have to do a lot of running around, i think im just going to give up, now, APX drivers are nto working, fml
had to manualy add the drivers, it was a pain the ass, now its all donw, hopefully i can get it going now!

s**t. use the last option ics v3.14.8 standard tab
jerkwagon said:
ok after OTA generated my sbk and all that info, saved it to my computer... how do i unlock the bootloader? i want to install CWM, do i just need to download a file then use the advanced tab?, from cwm im sure i can get around, also, i dont know what apx mode is, ill do some more searching, thanks again.
Click to expand...
Click to collapse
standard tab choose first option...keep an eye on the status bar while its flashing..should not take longer than 10mins.
You must then boot straight to recovery and flash yr rom from yr USB key
don't have to worry bout apx mode but yr tab should display.either Acer apx mode.or Acer download.mode at stage 3 of 4 in tool status bar.
if u.muck.up you'll learn all u ever wanted.to know about apx.mode
Sent from my GT-I9300 using Tapatalk 2
EDIT: the last option on the Standard Tab
DON'T FLASH THE FIRST ONE!!!!!!!

Related

[Q] A little help needed upgrading to ICS

Hi all, I'm running a rooted A500 (Android 3.1 build number Acer_A500_4.010.13_COM_GEN2) using the 2.6.36 Honeyvillian 1.0 kernel (so I could OC) and would like to upgrade to a rooted ICS. But since I changed from the stock kernel I get a little confused trying to follow other threads on what to do. The threads seem to start out on topic but tend to drift and for somebody like me, that can make it very hard to understand. I'd like to stay away from a custom ROM, no insult to the hard working dev's intended. You guys have saved alot of my devices from ending up on the top shelf of the closet. I'd like to upgrade to a "stock" rooted ICS with proper bootloader, kernel, etc. If I decide later to try a dev's ROM then I'll always have that option, but since I've never messed with ICS...stock may do all I need. I'd like to root for OC because some of the things I do seem to run better if the device is OC'd. So, what I need are a clear set of instructions on what to do. OTA's dont work, I'm guessing thats because of the root and kernel. Any help would be appreciated. Thanks.
There are 2 threads with Stock rooted ICS roms in the developer section. Read each and choose the one that suits you. Also, you may need to separately update the bootloader. To do this there is a new tool in the developer section called afterota 1.02. This will help automate the process for you.
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
realityrat said:
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
Click to expand...
Click to collapse
If you want to go completely stock (stock kernel, non-rooted), then you need only to install one of the Stock ICS Roms. This set's your bootloader back to a stock condition. So that's simple enough. You can do this through CWM
You said you're on Honeyomb right now. So my suggestion, is to follow these steps to upgrade your a500 to ICS.Go Here and read the steps;
http://forum.xda-developers.com/showthread.php?t=1622425
Pay attention to step 4. You have a choice. Stock Rom with Full Root, or (in small print (stock rom no root).
If you decide to install Stock Rom No Root, then skip steps 5 and 6. Just copy the file to your EXT SD Card, boot to your recovery (pwr & Vol-) and install Zip From SD. It'll be a done deal. Recovery gone, ICS Stock bootloader and rom.
I have you do steps 1-3 because I want you to write down your UID!!!!!! It's the only thing that will save you if something messes up.
Then you can decide if you want to root and install some custom stuff later.
MD
MD, can you run setCPU w/o Root? I didn't think so. Since this OP requests the ability to OC specifically I think that the steps listed would all need to be followed in Civato's post.
RR, Here are the steps I recommend, it's an opinion, and I think the best route to take as a fairly novice rooter, I've done my A500 many times and BN Nooks, but nothing else and am not a DEV, but have professionally been in IT for 20 years...so I use novice loosely here...
First, know why you're getting your CPUID:
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
Don't forget to BACKUP!!
Second, select which ROM you want on your tab, I recommend putting a couple on the MicroSD card so that you can test them. DON'T INSTALL ANYTHING, JUST PICK A COUPLE OF ROMS AND PUT THE ZIPS ON THE SD.
Don't forget to BACKUP!!
Third, follow the steps in the post that MD listed, read twice, run once...
http://forum.xda-developers.com/showthread.php?t=1622425
Don't forget to BACKUP!!
Fourth, flash one of the ROMs you chose previously while in recovery. Can't give you steps on this because they are all different unless you're just using the option in step 4 of the above post (stock w/ root)
Don't forget to BACKUP!!
Fifth, not sure if you can OC the stock w/ root or not, but if not pick a custom ROM and test several, they're all great, and see what fits your needs best. I use Flexreaper Extreme and love it, posted below, but look at ALL of them and find the one you like best, they're all GREAT! We have great DEVs here.
http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1
Don't forget to BACKUP!!
Good Luck, Have fun, and did I mention to make sure you Backup before each step so that you can get back to that point if you run into issues, and make sure you write down or put in a text file on a different device your CPUID...both very important.
Good luck again!
-DB
Thanks everybody for the info but I think I'll be staying on HC for now. The linked threads are the problem I mentioned in the OP. If you look at those threads with novice eyes they are incredibly hard to follow. Not sure why I cant find simple instructions but I do appreciate everyone's help. Maybe somebody will come up with a guide for dummies. Until then I guess I'm stuck with HC. Thanks again for the info.
Mate, it can be daunting even to experienced flashers...
My advice, go to this thread - http://forum.xda-developers.com/showthread.php?t=1622425
This has been cleaned up to make it easy to understand...
I use the manual method to go to apx mode but each to their own...
Now, follow each step. Make sure each step has been followed EXACTLY. Don't skip ahead or you will regret it, sooner than later...
If you have a doubt, go back a step.
Good idea to read through to the end first, especially the bit about checking you sdk...
Good luck....
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
realityrat said:
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
Click to expand...
Click to collapse
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Moscow Desire said:
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Click to expand...
Click to collapse
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
realityrat said:
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
Click to expand...
Click to collapse
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Moscow Desire said:
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Click to expand...
Click to collapse
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
realityrat said:
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
Click to expand...
Click to collapse
I zipped 4 apx packages for your 500. They have the ICS Booltoader and different recoveries. Unzip them to the same folder as your installation package.
http://www.4shared.com/zip/9TE6rTH-/500Bootloader_package.html
Yes, after you finish the bootloader/recovery installation process, turn tablet off. Press and hold Vol- and PWR till you see 2 lines of text in upper left corner, then release both. This will be your recovery menu. From here, you need to follow the instructions from the Rom page where you got your new Rom for the installation. Pretty simple really.
Also, I can't advise you on which recovery to use. I haven't tried the public recovery or TWRP yet.
MD
Thanks MD. Got the files downloaded. I'm gonna read over the threads a few times and make sure I havent missed anything and I also want to research some of the ROM's available. I'll probably give it a try in the next few days. Thanks again for all your help.
**UPDATE**
After reading the threads multiple times and following the instructions carefully I am now running ICS 4.0.3 with updated bootloader!! Everything went fine with only a couple problems that I was easily able to overcome. I'd like to address those problems so if anybody else has problems, 1: when entering the sbk its important to note that the spaces between the sets of numbers ARE needed, and the 0x at the beginning of each set has to be typed with a lowercase "x". 2: I used ezterry ICS 1.031.00stock- full root with busybox, and more tweaks and a500 public recovery. Following the instructions for this ROM I used the "clean up tablet" option in recovery. This DOES NOT do a full data wipe. So first boot had my custom boot animation and all my other apps and settings still there. ICS didnt like this and kept forcing reboots. I had to do a full data wipe and all is good now. I'm on ICS rooted stock and OC'd and loving it. Thank you all for your help, without your input I dont know if I would've tried this but I'm glad I did and I really appreciate everyone taking time out of their busy schedules to help some guy in NY get some ICS love. Thank you all again!

Bricked A500 in Houston area will pay you to fix

I live in the Houston area. Bricked my A500 will pay you to fix email me . I went from CWM v5 1.3.4 to 1.7 and now I can only go into boot loader but nothing can be applied , tried different ROMS wipe everything still nothing
[email protected]
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
twistedknickers said:
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
Click to expand...
Click to collapse
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Quandary unsolved
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
graphdarnell said:
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
Click to expand...
Click to collapse
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Danny2 said:
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Click to expand...
Click to collapse
This is my guess: I was able to get someone with the right equipment to probe into the NAND and scan. The result shows random bad sectors all over the place. The scan lasted for more than a day without finishing, so eventually remapping could not be executed. If the capability of the NAND to remap is exhausted then depending on your luck, if the ROM data fits into good sectors, you get to use the unit. If the cache partition has black holes in it, you'll get errors and operational aberrations. If I'm right, then this is purely a hardware issue which will come back to haunt sooner or later. Makes sense?
Since the NAND is soldered onto the Main Board, there is little chance of replacing the NAND, if you can find one, that is. Darn it!
graphdarnell said:
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Click to expand...
Click to collapse
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Danke schoen dibb nz
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Thanks MD
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Click to expand...
Click to collapse
Can't thank you enough MD, and dibb_nz too. Can't wait to get back to the tablet. Hopefully things will work out. When they do, I'll post the results for the perusal of similarly situated members.
graphdarnell said:
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Click to expand...
Click to collapse
Well after u fix permissions u boot straight back into cwmand flash the v8 and civatos cm 10 flex, which is exactly what I did after getting it up n running again. edit: no, u need the latest tdv4 - ...I'll post the link for it shortly....
I'd definitely uninstall the Acer drivers and reinstall them. When u connect to yr PC , windows will try to install the drivers....don't let it search windows updates, u have to be quick to cancel it....then it should install the drivers from the acer folder on yr PC which u just reinstalled....is that clear as mud, lol???
One more thought, u could get round all this driver business if u know linux at all....
But will w8 till u get a chance to spend some quality 'tab time'
Sent from my A500 using Tapatalk 2
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
MD
Click to expand...
Click to collapse
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Danny2 said:
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Click to expand...
Click to collapse
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Moscow Desire said:
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Click to expand...
Click to collapse
OK, Thanks
Progress report
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
graphdarnell said:
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
Click to expand...
Click to collapse
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Possibly corrupt V4?
dibb_nz said:
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out. Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
graphdarnell said:
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out.
Click to expand...
Click to collapse
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
Click to expand...
Click to collapse
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
dibb_nz said:
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
Click to expand...
Click to collapse
I was initially on 3.1 stock. I went to stock recovery which proceeded to erase whatever, then showed the android belly up with the triangle exclamation mark and so forth (The sd card contained no ROM at this point). I rebooted, then flashed V4 directly from inside 3.1 with debugging on. It "PASS" uneventfully, rebooted on its own to the setup wizard. Things function normally within that capsule (it showed HC 3.2 I believe). I turned it off after setup was done, then on again to experience the black SOD. I then went to Recovery 1.5, erase everything a few times, then rebooted. Same result. Eerily dead.
Then came the V8 Bootloader and Thor V20, and the tablet was resuscitated. Works fine now.

How to install custom rom/recovery for Acer a500?

I just rooted my Acer iconia tab a500. I am on the official ics 4.0.3. Can anyone provide step by step guide how to install custom rom for this tablet? Also which custom rom that you recommended? I thanks
Sent from my SGH-T989 using xda premium
Please, me too. I just bought mine too and is rooted, but my cell phones were much easier than the tablets. Either that or I just don't have the patients anymore. Maybe a dummies way to install custom rooms on a500? Lol.
Sent from my A500 using xda app-developers app
fe1ixs said:
I just rooted my Acer iconia tab a500. I am on the official ics 4.0.3. Can anyone provide step by step guide how to install custom rom for this tablet? Also which custom rom that you recommended? I thanks
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
slayinu said:
Please, me too. I just bought mine too and is rooted, but my cell phones were much easier than the tablets. Either that or I just don't have the patients anymore. Maybe a dummies way to install custom rooms on a500? Lol.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Hi guys welcome to the weird and wonderful world of the acer tab!!!!
Things are very different with this device, whats 'normal' for other android devices is not 'normal' for our tab!!!!
So first of all, dont try installing cwm or a rom the 'normal-this-is-the-way-I-did--it-on-myphone', you will end up with a brick!!!
2nd, you both have working systems at present, so we'll try to keep it that way.
Open up a file explorer and navigate to this:
/sys/firmware/fuse/acer_cpuid
One of the first things that are different is this: acer_cpuid
It should look something like this:
288424344009597 - now u need to add a 'zero' to the front:
0288424344009597 - this is your cpuid, back it up in multiple places if need be, just dont ever lose it - IF anything 'goes wrong' at any time you will NEED this number to save your tab from eternal brickdom!!
3rd once you do get your 'cpuid' go to the 'sbk generator' here.
This generates your 'sbk' or secure boot key and will give you something like this:
0x93588800 0x33CE8901 0x0BED6D03 0x30737899.....
OK then, now you have your cpuid/sbk you can start thinkning about what rom you want to install on your tab.......
Read the OP(Original Post) of your desired rom. This will tell you EVERYTHING you need in order to flash it - remembering always that 'Acer' does not do things the 'normal' way!!!!!!
Most of the custom ICS/JB roms on here all require the 'patched / unlocked bootloader'... In fact, even installing a custom recovery, cwm, twrp or public recovery, for the first time....will require the BL to be 'patched' first....and yes, even flashing this is not done the 'normal' way....tho the process can be complicated there are PLENTY of guides and auto tools to make it easier for you....
The 'patched bootloader flash' will also include a 'custom recovery' too, and you can choose from 3-4 options....amazing but i'd advise to use cwm 1.7.3, until u get up and running, after that you can go crazy flashing anything you like!!
So basically there are 5 main steps to getting a custom rom installed.
1. Install the Acer Drivers and the android_sdk drivers
2. Get your cpuid and generate your 'sbk'
3. Your desired rom is on your external sd card
4. Put your tab in 'apx mode' which allows u access to download mode
5. Install the patched v8 bootloader/recovery - either manually using nvFlash or using the auto tools.
Personally I prefer the manual nvFlash method, if you get an error it will at least give you an error message...the auto tools will just get 'stuck'
Check the 'bootloader' thread OP for a guide to manual nvFlash and the patched bootloader package here
There is also a step-by-step in my sig!!!
If you want to use the auto tools then apxFlash tool, or afterOTA tool you can find both in the 'bootloader' thread. And a step by step for apxflash tool also in my sig....or this excellent one here by user jdgM3NT4L here...
please be sure to read these posts very carefully and if there is something you do not understand then please dont hesitate to ask , there are plenty on here who will help you thru the process....AND its easier to offer help at this point rather than trying to do so when you've bricked it.....
As far as roms are concerned, you cant go past 'civato's FLEX roms' very stable and no issues i'm on cm10 and havent had a problem with it.....Of course it depends on what you require but I'd start with one of the flex ones.
Most peeps here have no trouble with this process, those that do, usually try things the 'normal' way, then find out they need their cpuid/sbk to get out of trouble and of course they dont have it....this makes things most difficult.... there are a few tabs with motherboard issues that have needed to be sent to acer....other than that, he only other issue you may have are driver related, check out the cpuid thread for anything driver related and lots of other background info too....theres also a zip file there that has a mini-sdk kit, to save u downloading the full android-sdk....
i think thats all i can think of at the moment, sorry for the long post and all the caps and bold text - just trying to save you alot of unnecessary grief...
Good luck with it all and remember....in this forum things are not 'normal' :laugh::laugh:
Wow, a lot of stuff to do just to flash a from huh. Lol
Sent from my A500 using xda app-developers app
Lol, as always preparation determines the success of the final outcome....and yeah with the tab 95% of yr time and energy is spent preparing!!! The actual flashing process takes only a few minutes...
Of course u could revert to hc 3.1 where everything is 'normal' i.e. one click root, flash cwm, flash rom, done....
Gosh, even hc 3.2 was locked down and unrootable....
So in the grand scheme for us to even be able to have stable ICS roms, let alone cm10 on the a50x.is.purely down to those wonderfully clever devs we have here..who were never gonna let a.locked bl, get in their way..
OK its complex I'll admit, but stock ICS is c**p and the lives of our tabs extended past wot Acer ever thought....and guys like gersma and.blackthund3r have built auto tools to make things easier
Anyways, its.well worth the
effort and is actually alot simpler to do than it is to describe how to do it...think of.trying to explain how to ride a bike and writing all those steps out....much easier to help them thru it by just getting them on the darn thing and doing it....dontcha think??
Sent from my GT-I9300 using Tapatalk 2
Yeah, I hear ya loud and clear. I wouldn't mind goin back to stock 3.1 , I kinda liked the hc. Ohwell
Sent from my A500 using xda app-developers app
---------- Post added at 07:27 PM ---------- Previous post was at 07:21 PM ----------
But as soon as I get home on my PC I'll start trying out this method. Hopefully I don't end up with a paper weight. Lol. Thank you very much for your response on this subject.
Sent from my A500 using xda app-developers app
Well, I could give u a a d/l link for 3.1 if u really do wanna go back....but I think gersma's afterOTA tool can do it too, tho I've Neva used it for that so can't really comment....
Oh, one other thing, you'll wanna back up all yr personal stuff, music, photo's and wot not especially going from one build to another, and most of the custom ROMs require a complete wipe and format of yr data partition too before install, just so u know!!
Sent from my A500 using Tapatalk 2
Yeah ,I'll take the link, I liked it better than 4.0.3 is it an original , or a rooted
Sent from my A500 using xda app-developers app
slayinu said:
Yeah ,I'll take the link, I liked it better than 4.0.3 is it an original , or a rooted
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
its factory stock but easy to root and get cwm installed, will have to w8 till i get home 2nyt to upload....
oh there myt be one in blackthund3rs stock rom thread in dev forum...i think
Sent from my GT-I9300 using Tapatalk 2
wow dibb, thank you so much for a helpful response!! Really enlightened me about how far off I was about the update process (compared to updating phones) and yet close enough to what I had to go thru for the Viewsonic GTab.
I'm currently on stock 4.0.3 rooted for A500. I have obtained my cpuid and SBK. When I go to recovery mode, I see a droid with triangle and exclamation mark. I tried flashing twrp but I still saw the same droid. I now know that I need to flash a different bootloader with recovery included.
My question is that if I flash the new bootloader which will allow me to put a custom recovery, during that process will my current ROM be removed or wiped out? If so, what do you recommend for backing up the app in the current stock ROM? Titanium Backup? BTW, I don't have an external SD card; all I'm using is the internal 8GB
Thank you for your help!!
def need external SD , it will help out alot
Sent from my A500 using xda app-developers app
artbybart said:
wow data, thank you so much for a helpful response!! Really enlightened me about how far off I was about the update process (compared to updating phones) and yet close enough to what I had to go thru for the Viewsonic GTab.
I'm currently on stock 4.0.3 rooted for A500. I have obtained my cpuid and SBK. When I go to recovery mode, I see a droid with triangle and exclamation mark. I tried flashing twrp but I still saw the same droid. I now know that I need to flash a different bootloader with recovery included.
My question is that if I flash the new bootloader which will allow me to put a custom recovery, during that process will my current ROM be removed or wiped out? If so, what do you recommend for backing up the app in the current stock ROM? Titanium Backup? BTW, I don't have an external SD card; all I'm using is the internal 8GB
Thank you for your help!!
Click to expand...
Click to collapse
Yes u need the v8 bootloader to get a recovery installed...
Always check the original post of the rom you install for special instructions regarding bootloaders.....this applies to all custom Roms even stock pre rooted ones.
Yup TB to back up yr apps and data - dont restore immediately...make sure everything is stable first.
If u dont have an ext. SD card, the EUU method doesn't require one, and as slayinu said, it would make it easier if u had one especially for the update.zip methid
Im sorry...
I have the a500 running ota 4.0.3....well from the official app. I have it rooted and running superuser yet I downloaded the Acer recovery installer app from the market and get the recovery verified failed message when booting into any custom recovery and the dead android with the exclamation mark....I know I need a patched or an unlocked boot loader but I cannot find one I downloaded the afterota but it doesn't do anything on my computer...idk what to do the frustration is gonna make me break this thing and just go buy a newer tab running jb ....help please!
famousnerd1 said:
I have the a500 running ota 4.0.3....well from the official app. I have it rooted and running superuser yet I downloaded the Acer recovery installer app from the market and get the recovery verified failed message when booting into any custom recovery and the dead android with the exclamation mark....I know I need a patched or an unlocked boot loader but I cannot find one I downloaded the afterota but it doesn't do anything on my computer...idk what to do the frustration is gonna make me break this thing and just go buy a newer tab running job....help please!
Click to expand...
Click to collapse
Seems weird afterota "doesn't do anything"...did you install the drivers?? Did it give u yr cpuid/sbk you cannot do anything without this AND if u muck things up its the only thing that will get u unbricked? Are u using a micro USB cable? Do u have USB debug enabled?
If u go to the root guide in my sig you'll find d.load links and all the guides to help u install the v8....take special note of the boot.p file u need to rename or delete in /system....
For more info on getting yr cpuid/sbk see the cpuid guide in my SIG or the sticky in dev forum...
Sent from my GT-I9300 using Tapatalk 2
obviously..
I'm too dumb to figure this out...idk how to get my cpuid none of the ways in your "where's my cpuid"guide worked.I don't want to stay stuck on ota 4.0.3 but apparently I have to..thanks for your time and your advice,unfortunately I wasn't able to use it properly.
Well, it seems it's not just you being dumb ...
I tried the same - original OTA 4.0.3 and rooted my A500. Now tried to use the 'AfterOTA'-Tools, but getting stuck in step 3 of 4 (maybe i just need to insert a SD-Card in the Tab?).
Just got no idea, what to do now - the only thing i know is: before flashing, i need a open bootloader, but i've got no idea how to do that. The Guide linked in this posts: http://forum.xda-developers.com/showthread.php?t=1622425 is just confusing me more and more
After a reading a few times, it seems to me, that MY next step should be:
"Automated flashing tool" (STEP 5= Going into APX mode see Q&A or use A500 manager)
-1-Reboot your tablet and make sure on your tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
[...]
-It will ask if you are ready (click yes if you are)
Click to expand...
Click to collapse
Is it correct, that THIS will help me to patch/open the bootloader?
Or do i just have to follow this as a next step to create a patched bootloader:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44 ?
voodoo441 said:
Well, it seems it's not just you being dumb ...
I tried the same - original OTA 4.0.3 and rooted my A500. Now tried to use the 'AfterOTA'-Tools, but getting stuck in step 3 of 4 (maybe i just need to insert a SD-Card in the Tab?).
Just got no idea, what to do now - the only thing i know is: before flashing, i need a open bootloader, but i've got no idea how to do that. The Guide linked in this posts: http://forum.xda-developers.com/showthread.php?t=1622425 is just confusing me more and more
After a reading a few times, it seems to me, that MY next step should be:
"Automated flashing tool" (STEP 5= Going into APX mode see Q&A or use A500 manager)
Is it correct, that THIS will help me to patch/open the bootloader?
Or do i just have to follow this as a next step to create a patched bootloader:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44 ?
Click to expand...
Click to collapse
Hi voodoo, no, neither of you are being dumb!!! It CAN be a complicated procedure, we try to make our guides 'simple' but theres ALOT that can go wrong
Yes the last link you posted will flash the patched bootloader!!!
- but basically this is what SHOULD happen
Note: The only way to get a custom ICS rom on your tab is with the v8 bootloader by skrilx_cz. This must be flashed via nvFlash/apx mode.
Note:The only way to install a custom recovery like cwm or twrp etc is with v8 bootloader.
Note: You cannot use Acer Recovery Installer unless you have the v8 installed.
Note: Rom Manager does not support our Acer Tabs...please don't use it to flash 'anything'!!
OK heres an overall view of the process:
1. Install Acer and adb/fastboot drivers
2. Retrieve your CPUID...
3. ...and use it to generate your SBK
4. Download your ICS or JB rom and copy to your sd card (internal or external)
5. Enter apx mode to begin the flash!!! or use apxFlash tool
5. Use balckthund3rs apxFlash tool and follow the instructions: hint: dump and save your bct!!!
5. If using civato's manual nvFlash method - Put your tab in apx mode and run the .bat file
5. AfterOTA Tool is only for those tabs which have OTA'ed to ICS!!!
The main issues you will have with the actual flashing process itself is a partitioning error or a bct error - and both of these are easily fixed...UNLESS your tab in one of the few with a hardware fault which only a new motherboard can remedy
Once you get the big white "PASS" on your tab, boot straight to your new custom recovery, do the FULL WIPES and flash your new rom....DONE!!!
Well ... i now used AfterOTA - but not in a virtual machine - now just natively installed on my macbook via bootcamp (windows). Worked. I now have a V8-Bootloader (the tab shows me this when iam booting it up).
Whats the next step to flash a new ROM? Iam ready to do that? Or is there any other step needed by now?
Regards, Tom
Edit:
I now just tried flashing a custom rom - so i copied the *.zip to my USB-Stick (FAT32) - because i read, i can use an USB-Stick as an micro-sd card.
Tried booting into recovery-kernel - worked for me, but the only thing i can see: a lying android with an red sign ("!").
Did i something wrong?
Oh dear....if u had a stock rom on there then its overwritten
your newly flashed recovery....you need to delete or rename
the "boot.p file" in /system..then reflash the v8...
The very next step should be to enter recovery and flash your
desired rom....
So, it now just works everything.
Used Acer Recovery-Manager to re-flash the recovery - worked fine for me.
But: i tried several 4.1 and 4.2-ROMS ... is it correct, that there's no Google Marketplace anymore on 4.1 and 4.2?

[Q] unbricking selfbricked stock A500

My colleague brought his stock A500 to me in a bricked condition last week.
I need a way to restore it. If I try to do a wipe it will say bootloader error if i try the recovery the droid falls down with the red sign with the exclamation mark.
This tablet has never been rooted, my colleague is not in to such things, it's lived its life with ordinary acer otas and the occational very young human (5 year old) trial wich it has survived.
He has installed all the OTAs he ever got on the tablet and this is in Sweden so it would probably be a 4.0.3 acer stock on it now.
I'm guessing it has died during a OTA or something. if i turn it on it will sit at the acer logo indefinitly.
I Bricked my A500 during a rooting atempt resulting in me needed to flash a stock rom to get it working again, but i cant find the thread i read to un-brick my A500.
Please Help!
try this http://forum.xda-developers.com/showthread.php?t=1839313
dibb_nz wrote:
try this http://forum.xda-developers.com/showthread.php?t=1839313
Click to expand...
Click to collapse
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Hogbola said:
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Click to expand...
Click to collapse
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
I am in a similar situation. Push the power button and it goes to a screen with white acer on black and stays there. Totally stock ICS, no root. I tried the update.zip thing and after automatically rebooting it says "Boot verified failed...". I don't have my cpuid, or have installed previously CWM or anything like that. I can get into APX mode. This guy here: http://forum.xda-developers.com/showthread.php?t=1751978 could only get into APX with no cpuid as well, but i don't understand all of the ubuntuu and command line stuff. I would love for someone to be able to walk a dummy like me through this mess. Thanks for any help.
if u got boot verified fail error you need nvFlash to repair that....as u know, with nvflash you need yr cpuid....wot about usbdeview? if you've never plugged yr tab into yr PC - then it won't work and the ONLY other way is Linux....
might be best to start yr own thread with a descriptive title, not just a help I'm bricked no uid, thread there are hundreds of those....the more effort u put into the title the more likely you will attract the attention of someone who can actually help...and remember you just don't need a bit of help but a blow by blow description of what to do and how....this will be very time consuming....at the very least get ubuntu installed, maybe just try a few things, anything to show you are capable of at least giving it a go yourself..
there are others who would like 2 know how to do this as well...having a specific thread of its own would be great
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
Actually, I have connected it to my PC before. Only for transferring media though. If I've done that, is the some way to retrieve my cpuid from the PC?
yup...usbdeview.zip see the bottom of the OP in the cpuid guide in my sig
Thanks alot for your help. I used usbdeview and got my cpuid. Now I should use nvflash? Know where a good step by step is for that one?
you could try the one in my sig??
dibb_nz said:
you could try the one in my sig??
Click to expand...
Click to collapse
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
NvigR8 said:
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
Click to expand...
Click to collapse
The .rar EUU is for an A500, the .exe is for the A501, which do you have?
I've got the a500. However, I decided to go with a custom ICS rom after all. I managed to put a new bootloader and custom recovery on using the a500apx flash tool. That part went fine. I flashed this rom:
Acer_AV041_A500_1.054.00_WW_GEN1-FULL-ROOT (original odex)
and that appeared to go well according to twrp, but after rebooting, it just shows the bootloader again and stops there. Not sure what i did wrong.
I renamed the rom update.zip. Should i not have done that?
well congrats for getting thru the flash process with no probs!!!
as far as renaming to update.zip that was not such a good move...hopefully things havent been screwed up too much
just go back into recovery and do a FULL wipe/format
then to flash use the option "install from zip file" not sure where that is in TWRP but it will have one
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
NvigR8 said:
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Click to expand...
Click to collapse
The stock ICS BL is encrypted - more or less - the only way to 'flash' a recovery or rom is to have the "key" that "unlocks" - it more or less - if you dont use the right key then the OS will not boot - the 'key' is based on your cpuid which is why everyone is forever telling you to save it somewhere safe....
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
Click to expand...
Click to collapse
I enjoy the big screen, took awhile to get used to it in my hand, kept dropping it....then I ran it over with my 44tonne truck after 3 days and munted it!!!!
I have a case for it now, and its gr8 - I havent installed a rom on it yet...the forums over there are jampacked and I have no idea what I'm doing, lol - its the first android device I've had that I've left stock for so long...but it does what I want...the camera is awesome -burst mode is the bomb - BUT do I think it was worth the money???? Still on the fence about that one.....
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
NvigR8 said:
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
Click to expand...
Click to collapse
yeh sometimes happens with the tab for some reason - thank your lucky stars it didn't get stuck in apx mode...if that happens its normally a hardware fault so theres not alot u can do...I'm just pleased you got sorted without too much drama and it was as easy as reflashing the zip....so now you have the v8 BL - you're gold!!!
dibb_nz said:
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
Click to expand...
Click to collapse
When i do the wipe it says
Code:
Erasing userdata...
Code:
Unrecoverable bootloader error (0x19000008)
Unrecoverable bootloader error (0x19000008)
Hogbola said:
When i do the wipe it says
Code:
Erasing userdata...
Code:
Click to expand...
Click to collapse
I googled your error - the consensus from what I read is a corrupt OS due to running OTA updates...
Some had luck with rebooting. Others had to send it to Acer.
Did you run the update.zip? so what happens when you run the update.zip
Are you able to get into "apx mode"? If you can, hook up to your PC and see if your tab is recognised as an "apx device" - check "Hardware, Printers in win7"
Thats all I can suggest atm - if your tab does get into apx mode OK then you can find your cpuid by running Linux -
Maybe ask the guy if he's ever had the tab hooked up to his PC like to transfer files and stuff - get him to download "USBdeview" to his PC -
this will show every single device thats ever been connected to the PC and it will show the "cpuid"...
Even if we do get the uid theres no guarantee it will fix the bootloader error - but we may as well explore all the options we can....
dibb_nz said:
USBDeview will only work when you have previously plugged your tab into the PC WHILE you were running HC Rom and BL
1. If you haven't plugged your tab into this pc before, do so now, before you run the program. HC ROM/BL ONLY
1a. Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2. Click on "VendorID" column along the top to sort them
3. Look for the number "0502" under Vendor ID AND "3325" Product ID
4. In the serial number column will be a 15-digit number this is your device ID.
5. Write the number down and put a 0 in front of it and now you have your CPU ID!!!
Click to expand...
Click to collapse

HELP

while trying to root and unlock bootloader on acer a500, somehow i screwed things up and had to finally flash a euu file to get it working again, now im rooted unlocked, i guess, im able to flash roms but my storage has been reduced to 128mb. , no matter what i flash or try no change, not enuff room to restore any apps.. question is any chance or anything i can do to recover that space? thank you...
athack said:
while trying to root and unlock bootloader on acer a500, somehow i screwed things up and had to finally flash a euu file to get it working again, now im rooted unlocked, i guess, im able to flash roms but my storage has been reduced to 128mb. , no matter what i flash or try no change, not enuff room to restore any apps.. question is any chance or anything i can do to recover that space? thank you...
Click to expand...
Click to collapse
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
ok let me say ive been rooting my ohones since the OG droid, its been 5 or 6 diff since then but this tablet has me stumped... can you please tell me how i can find which version bootloader? the euu file i got off of tegra forum owners, ive got cwm based recovery v5.5.0.x 9thor2002ro rev 1.7) and as far as operating system ive flashed 3 diff roms so far the 1 im on now is flex resurection rev1...4.0.4 android version, ive tried 4.0.3, and jb... i have cpuid if thats the same as uid#...? if you could help in any way its much appreciated...
Moscow Desire said:
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
Click to expand...
Click to collapse
when i run recovery bootlader version says 03.11 custom mode????
athack said:
ok let me say ive been rooting my ohones since the OG droid, its been 5 or 6 diff since then but this tablet has me stumped... can you please tell me how i can find which version bootloader? the euu file i got off of tegra forum owners, ive got cwm based recovery v5.5.0.x 9thor2002ro rev 1.7) and as far as operating system ive flashed 3 diff roms so far the 1 im on now is flex resurection rev1...4.0.4 android version, ive tried 4.0.3, and jb... i have cpuid if thats the same as uid#...? if you could help in any way its much appreciated...
Click to expand...
Click to collapse
Ha ha, no mate. No doubt you are a bit familiar. Phones is different than tabs though.
Ok,, when you start your tab normally, you should see the bootloader version. Upper left corner.
There's only a couple EUU files, and I believe both are Honeycomb.
CWM ver is ok.
But if you are running ICS or JB roms, on a HC bootloader, than that's not OK.
So, I need current ROM and version, and current bootloader version. Civato has several roms.
Just wanna see where exactly you are at right now.
MD
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 Bundle (Stock 3.0.1 if I remember correctly) ...... FLEX-Resurrection_Rev1-Aroma-Public....0.03.11 ICS bootloader custom mods...
Moscow Desire said:
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
Click to expand...
Click to collapse
athack said:
when i run recovery bootlader version says 03.11 custom mode????
Click to expand...
Click to collapse
3.11 sounds like an HC bootloader, or one of Skrilax_cz's initial bootloader. If you try running ICS or JB based roms, you're gonna get a lot of screwy stuff going on, Like display glitches and stuff.
You need to goto Civato's Bootloader thread in the Dev forum, and try running the apps listed there to get you to Skirlax_cz's unlocked bootloader for ICS. Works for CM JB.
@dibb_nz also has a thread there, explaining things about UID and stuff.
Then, after you get the unlocked bootloader NV flashed, throw CWM on there. I use 1.7.3 I believe. In mounts and storage, there is an option to format your internal SD. Select the option, then do your wipes and formats. Then flash the rom.
Think you'll be okay then.
recovery also says thor kernal v1.16mini running itsmagic that is on the screen when i run a backup....
athack said:
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 Bundle (Stock 3.0.1 if I remember correctly) ...... FLEX-Resurrection_Rev1-Aroma-Public....0.03.11 ICS bootloader custom mods...
Click to expand...
Click to collapse
athack said:
recovery also says thor kernal v1.16mini running itsmagic that is on the screen when i run a backup....
Click to expand...
Click to collapse
It's magic is no longer needed for unlocked bootloader and ICS/JB.
If you boot holding PWR and Vol -, you should boot into the V8 bootloader menu. If you don't, there's an issue.
ok i got that set up right now, its magic is no longer needed it says... everything is working fine but still only 128 mb of storage wiped mounted unmounted formatted everything, nothing is changing it....
Moscow Desire said:
It's magic is no longer needed for unlocked bootloader and ICS/JB.
If you boot holding PWR and Vol -, you should boot into the V8 bootloader menu. If you don't, there's an issue.
Click to expand...
Click to collapse
Well, sounds like the emmc memory is hosed. As you read in the threads, it happens sometimes.
However, as a last chance, there is a thing called "bab sector". I've never used it before. Supposedly helps recover bad memory blocks. I've tried searching for it here in the forums, but must not be using the right search parameters . Found discussions on it in @Skrilax_CZ bootloader thread. It's labeled for the a501 but doesn't matter as partitions are the same I believe. He knows more about the memory partitions, so may want to post the issue in his bootloader thread.
But, I do happen to have one of the zips on my Dev Host server.
http://d-h.st/iQX
If I remember correctly, there are 2 variants of this repair file. @dibb_nz might know more about it.
Also on my server. is an HC roll back tool. If not mistaken, it may have a different variant of EUU. Might wanna run it and see if it resets partitions. As it seems like things screwed up when you ran an EUU.
http://d-h.st/0x7
At any case, I would run the EUU again. Can't hurt, and maybe will reset partitions.
thank you that bab sector file how would i go about installing that? flash with the a500 apx flash tool ? and the euu i believe get done that way also?
Moscow Desire said:
Well, sounds like the emmc memory is hosed. As you read in the threads, it happens sometimes.
However, as a last chance, there is a thing called "bab sector". I've never used it before. Supposedly helps recover bad memory blocks. I've tried searching for it here in the forums, but must not be using the right search parameters . Found discussions on it in @Skrilax_CZ bootloader thread. It's labeled for the a501 but doesn't matter as partitions are the same I believe. He knows more about the memory partitions, so may want to post the issue in his bootloader thread.
But, I do happen to have one of the zips on my Dev Host server.
http://d-h.st/iQX
If I remember correctly, there are 2 variants of this repair file. @dibb_nz might know more about it.
Also on my server. is an HC roll back tool. If not mistaken, it may have a different variant of EUU. Might wanna run it and see if it resets partitions. As it seems like things screwed up when you ran an EUU.
http://d-h.st/0x7
At any case, I would run the EUU again. Can't hurt, and maybe will reset partitions.
Click to expand...
Click to collapse
athack said:
thank you that bab sector file how would i go about installing that? flash with the a500 apx flash tool ? and the euu i believe get done that way also?
Click to expand...
Click to collapse
Ok, never run the Bab tool before. But looking at it, you have to be in APX mode just as you would to run NVFlash, as it operates the same way.
With the Bab tool, if it errors out writing any of the partitions, it should at least generate an error message. Now, you'll have to search to find out how to manually get into APX mode. But if I'm not mistaken, it's tab off. Hold PWR and Reset button. Then count to 3 or 5, release reset, then 2 counts later release PWR. But please do not quote me on this. Been some time, and primarily I work on the A701 now. But it's pretty close.
Then, run the bat file in the zip via a command window. Note I have never had to use this before.
The rollback/EUU works just like any other EUU. Has an exe file in it to run (make sure USB debugging is on, and remember to get your UID.
I also have an ATT EUU handy. Not sure which version it installs, but will be HC.
I still say to post a note in the Bootloader thread. Skrilax_cz knows more about the 50x partitions than even Acer.
flashed the bab file thru cmd promots device said pass reboot... rebooted to booloade mode saying error invalid primary lnx kernal image.. wont d...o anything but reboot to this same screen... also the other file euu is a rar file wont let me do anything with it when i flashed the other file euu i used the a500 tool and it found the euu file, how do i extract the euu from the roll back rom?
Moscow Desire said:
Ok, never run the Bab tool before. But looking at it, you have to be in APX mode just as you would to run NVFlash, as it operates the same way.
With the Bab tool, if it errors out writing any of the partitions, it should at least generate an error message. Now, you'll have to search to find out how to manually get into APX mode. But if I'm not mistaken, it's tab off. Hold PWR and Reset button. Then count to 3 or 5, release reset, then 2 counts later release PWR. But please do not quote me on this. Been some time, and primarily I work on the A701 now. But it's pretty close.
Then, run the bat file in the zip via a command window. Note I have never had to use this before.
The rollback/EUU works just like any other EUU. Has an exe file in it to run (make sure USB debugging is on, and remember to get your UID.
I also have an ATT EUU handy. Not sure which version it installs, but will be HC.
I still say to post a note in the Bootloader thread. Skrilax_cz knows more about the 50x partitions than even Acer.
Click to expand...
Click to collapse
thanks i found the tool in the rollback rom to redo my tab it restored my tab to full storage your a genius... thank u for all your help truly appreciate it...
athack said:
thanks i found the tool in the rollback rom to redo my tab it restored my tab to full storage your a genius... thank u for all your help truly appreciate it...
Click to expand...
Click to collapse
Ehhhh.... sometimes MD is just lucky I guess
CCR... I Put a Spell on You.... (what I'm listening to now) on a Viper4Android tricked out A701 running Evil Alex Purgatory V2 for the 701 :good:
Damn glad you got it going Mate!
Rock On!
MD

Resources