Related
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!
*** SOLVED ***
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Psychlone said:
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Click to expand...
Click to collapse
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
gears177 said:
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
Click to expand...
Click to collapse
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
if your on the honeycomb bootloader simply flash a honeycomb rom and kernel no need to use afterOTA or anything else if i remember correctly
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
dibb_nz said:
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
Click to expand...
Click to collapse
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
gears177 said:
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
Click to expand...
Click to collapse
Yeh 2nd line of my post hc bootloader ics rom, and u correct use 3.01 buggy update,zip or stock update.zip I shoulda been clearer - thanks gears
Thanks guys, I really do appreciate the help, but I'm still having serious issues reverting back to HC.
I feel like an idiot, but I have to say that even though it seems so, I'm actually the owner of a computer repair business, have 28 years experience in PC/Mac repair, and have rooted and modded every android device I've owned (including some for friends as well) - all the way back to the very beginning with the D1. This, however, has thrown me for a loop. NOTHING with this A500 has been this complicated! Everything up to this point has literally been stupid-proof and I've actually been quite impressed at just how easy modding is on the A500...
Anyway...
Here's what's going on and what I've tried today:
I've tried unsuccessfully several times to get ANYTHING working on my laptop, but to no avail. Same story as last night, no progress whatsoever - however, I did note that with CWM 134, I was able to restore an earlier version of ICS 4.03 (Flexreaper R10 I believe) - but it wasn't easy... I ended up restoring the main image and then using parts and pieces (using Advanced Restore) from other saves to finally even get it to boot.
This clearly wasn't getting me anywhere, so I moved the entire operation to another computer - my main rig (also a Win7 x64 - in fact, I don't own a computer that's not Win7 x64)
Now I've got USB driver issues! I can't even install the standard USB drivers from Acer's website because the installer errors out saying that there's no version of Acer Iconia 3G Driver Install is installed. wtF? That's what I'm TRYING to do!
I did get a different USB driver installed - the USB Driver_Acer_1.06.1500_A30H_A500, but nothing wants to use it and Blackthund3r's APX Flash Util won't see it, AfterOTA won't use it, and it's basically useless anyway. AND I can't install the Acer_1.00.0524_A30H_A31H_A32H_A500_A501 drivers no matter if I've got any others installed or not.
In my device mangler, there is no device with an exclamation, and in fact, sees my Acer Iconia A500 under USB Serial Bus Controllers as "Acer Picasso USB Boot-Recovery Driver", only when it's plugged in. NO other instance shows up at all.
I'm actually at the point of trying to follow through with the EUU (dibb_nz's "last resort"), but vache's website is down and I can't download anything for it. In fact, there's nothing from that guide that has a valid link...
(http://forum.xda-developers.com/showthread.php?t=1632392)
So now where do I go? I understand IT really well, so you don't need to talk to me like a complete noob, but dang if I can't figure this one out!
If I can get valid links to all the downloads from the link above, I'd be more than happy to give it a go and see if that works, but I can't piece together all those things from random places. If either of you (or anyone else for that matter) has valid links for everything needed to follow the EUU guide, I'd be very grateful!
Any other advice would certainly be appreciated as well! I don't have to use either of these computers, but as mentioned, ALL of my computers have Windows 7 x64 on them. I suppose I could try one of my customer's computers for all this, but that's not morally right and probably something that I would prefer not to explore.
I feel as if I could get the USB drivers installed properly on EITHER machine, that I'd likely be in good shape. I think that's what my problem actually is on the laptop as well, even though they're all installed and shows as installed until I boot into any recovery - then I get the MTP Device Driver Fail. There's likely other Acer driver issues there though, since Blackthund3r's utils don't follow through for anything... everything just hangs. AfterOTA just hangs.
Advice please?
And thanks again for your knowledge!
Psychlone
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
dibb_nz said:
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
Click to expand...
Click to collapse
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
EDIT::
OK, so I'm really in bad shape here - now the EUU (PBJ20upgrade) comes back with the error:
Please download the newer image for the upgrade.
Current image version: Acer_AV041_A500_1,054.Acer_AV041_A500
New image version: Acer_A500_1.016.05_Com_GEN1
What now????
Psychlone said:
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
Click to expand...
Click to collapse
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
dibb_nz said:
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
Click to expand...
Click to collapse
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Psychlone said:
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Click to expand...
Click to collapse
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
THANK YOU!
dibb_nz said:
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
Click to expand...
Click to collapse
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Thanks again,
Psychlone
With what I went thru use Civs nvflash and rom and I'd stick with third cement until your safely patched and on ics.do all the wipes and follow instructions to the letter ...I'll check back in shortly
EDIT wtf "third cement" dang auto correct ... should read thors recovery
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
excellent news glad it worked for ya
Psychlone said:
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
Click to expand...
Click to collapse
if its referring to newer image then the data cable is connected!
and it will spit this error at you....
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
Click to expand...
Click to collapse
yup now you're cookin
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Click to expand...
Click to collapse
oh yeahhhhh!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Click to expand...
Click to collapse
nps glad to be of assistance -
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Click to expand...
Click to collapse
becoz then you'd have thousands of posts to look thru and no-one would bother reading it all....i try to keep my cpuid thread updated with things 'unbricking' but its too hard to put 'everything' in one post unfortunately
---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------
Psychlone said:
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
Click to expand...
Click to collapse
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
dibb_nz said:
excellent news glad it worked for ya
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
Click to expand...
Click to collapse
CM10 is SLICK. Think CM9 on graphics steroids and you're close!
I appreciate your position more than most. I get a lot of enjoyment out of helping others as well - I've written overclocking guides for AMD systems that was written years ago, revised a couple/three years ago and is still used to this day, even though I've long since moved over to Intel's "dark side". I also participate pretty deeply in helping others at a couple PC hardware forums pretty much daily, even though that's my actual job - I own 2 computer repair businesses in my hometown, and with well over 20,000 computers to fix, I'm ALWAYS busy but still always find time to help others in need.
As for adding ***SOLVED*** to the title, I'd love to...but it won't let me. Perhaps it's because I don't have a high enough post count, or because it's reserved for Mods, but I can't do it.
Thanks for everything once again - it's quite refreshing to be on the receiving end!
Psychlone
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
The problem is that, I couldn't find a tested (official/unofficial) ClockworkMod recovery for use with Defy XT. I could do with installing some Chinese release of ICS for Defy XT (SBF), but, I wanted to try CM10; it appeared more fascinating. So, anyway, I thought I could use Koushik's custom recovery build script on his website (builder.clockworkmod.com). So, I did the process of obtaining the stock "recovery.img", plugging it in that script, and obtained a new custom-built CWM. The real problem which I am not able to come out of is now - After flashing it, on the next reboot, it is going into the "MBM-flash mode", and it throws out an "error 0301", and doesn't go further than that. In this mode, I gathered that it will be able to communicate to a computer (RSD lite) over USB, and so, I installed it and was able to detect the device, but I'm not able to find out, what to do next to get it back to normal working condition.
Since that error screen I see now is basically a flashing tool, I was thinking, reflashing the recovery partition with the stock "recovery.img" (have a back up) should solve the problem. But, I'm not able to find out how to do it...
If there is anyone else who has faced a similar problem and found a solution, it would be really good of you to share it. Or, if there is anyone who knows how to work with RSD lite, could you suggest a method to flash the "recovery" section only through this software? (I'm guessing an XML file should be enough, but I don't know how to write it; format).
Hopefully I'll get speedy replies .
QuaziRandom said:
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
I tried...
Srika said:
QuaziRandom said:
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
QuaziRandom said:
Srika said:
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
Srika said:
QuaziRandom said:
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
any other way to backup my stock rom b4 flashing the new ics rom?
Click to expand...
Click to collapse
Please ask all questions in the Q&A section. Thread moved there.
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.
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