Hi, apologies at first if this was posted before. I tried searching a lot.
Acer Iconia A500.
I have been using FLEXREAPER custom rom for the last 6 months. installed any updated rom i can find.
Few days ago I found FLEXREAPER released FLEXREAPER-RELIX_rev5 ANDROID 4.0.3, downloaded the rom on my 2GB SD card, wiped everything, tried installing.
Installation showed successfully finished. reboot.
Stuck on the first ACER LOGO screen.
Wiped everything off. installed again. reboot.
Stuck on the first ACER LOGO screen.
Downloaded a few other ROM, such as, RE-FLEXxx ANDROID 4.0.4 ROM, Evil-Alex-Unleashed, JELLYTIME_AOSP_BUILD_5.
Installed. Stuck on the first ACER LOGO screen.
tried finding the ROM that I was using last. could not remember the name, so I found an older ROM, FLEXSTRIKER-FINAL-BASE-2-R8-3GusbIntegrated.
installed. Perfectly booting. no issue whats so ever. That means I did not brick the device.
updated CWM to CWM-based Recovery v5.5.0.x(thor2002ro rev1.7), the touch screen one.
went the whole process of trying to install with all the new roms I have downloaded. Same exact issue.
Stuck on the first ACER LOGO screen.
tired installed the OLD (FLEXSTRIKER-FINAL-BASE-2-R8-3GusbIntegrated.) rom, works FINE.
tried Fix Permissions from CWM advanced menu. tried the whole process again. same issue.
I am loosing my mind. any HELP?
btw, please be patient with me as I do not understand the Android terminology that good.
I always followed tutorial instructions as it is.
just half an hour ago, I tried to install RE-FLEXxx ANDROID 4.0.4 ROM from a different SD card( thinking maybe the sd card has something to do it) , Same issue.
#1. You must be on the unlocked ICS boot loader. Instrustions in the dev section.
#2. Upgrade your recovery to version 1.7.3.
Do those two things and you should be good to go.
Rippster said:
#1. You must be on the unlocked ICS boot loader. Instrustions in the dev section.
#2. Upgrade your recovery to version 1.7.3.
Do those two things and you should be good to go.
Click to expand...
Click to collapse
guide for unlocking ICS boot loder
[GUIDE]A500/501/G100W-Installing ICS V8 UNL-BL & CWM Or back to HC BL(24-6-2012)
Should i follow this guide? or is there a less scary guide? would you kindly point out if there is any?
I am assuming you have been running honeycomb based ROM, you can't upgrade android versions without upgrading boot loader.
Yes follow that guide, that's what pretty much everyone has done to upgrade the boot loader, you have to have ICS unlocked boot loader to run almost all ICS ROMs, and jellybean ROMs, unless they provide an alternative kernel for honeycomb boot loader.. which developers have stopped supporting, so if you want to be able to keep up to date, and install the latest ROMs, you need to upgrade boot loader, the directions seems overwhelming at first, but trust me its very easy takes like 5min.
Sent from my A500 using xda app-developers app
iamtapu said:
guide for unlocking ICS boot loder
[GUIDE]A500/501/G100W-Installing ICS V8 UNL-BL & CWM Or back to HC BL(24-6-2012)
Should i follow this guide? or is there a less scary guide? would you kindly point out if there is any?
Click to expand...
Click to collapse
You have a good guide to go by. And trust me, if you have any issues, I am confident we can help you.
The issue, is the Bootloader. To run any ICS based rom, including my own (Evil Alex), you have to have an ICS Bootloader. That's just how it is.
The bootloader is included with every "stock" rom. Call it the security measure and OS launcher. With HC based roms, everything was more or less in order., When ICS came, Acer changed the rules. As they usually do.
A new bootloader was introduced, and it communicated more with the Android Kernel. So, after some hacked kernels, which was ok, it was decided the bootloader needed to be hacked, And so, the unlocked ICS bootloader came about, But, this meant some rules.
1. ICS roms run on ICS bootloader (unless they have a hacked kernel, which is really not so good)
2. Honeycomb based roms will not run on an ICS Unlocked Bootloader. So don't even think about it.
So, you have to upgrade your bootloader to the unlocked V8. Don't worry. These days, the 500/501 are pretty much "bulletproof", so you don't have to worry about bricking your tab.
Just remember. Your UID number before you do anything. So write it down somewhere. After your ICS upgrade, get your UID and write it again. Call it your golden key to life.
MD
Moscow Desire said:
You have a good guide to go by. And trust me, if you have any issues, I am confident we can help you.
Just remember. Your UID number before you do anything. So write it down somewhere. After your ICS upgrade, get your UID and write it again. Call it your golden key to life.
MD
Click to expand...
Click to collapse
Thanks a lot mate for you reply.
I am on a 8 night in a row shift and do not have a Windows laptop so that I can follow the instruction at work.
Will get a windows lappy tomorrow at work and will start doing it.
Will buzz you guys back if I hit a wall.
iamtapu said:
Thanks a lot mate for you reply.
I am on a 8 night in a row shift and do not have a Windows laptop so that I can follow the instruction at work.
Will get a windows lappy tomorrow at work and will start doing it.
Will buzz you guys back if I hit a wall.
Click to expand...
Click to collapse
thanks a lot guys.
I guess it worked.
I installed the Evil-Alex-Unleashed.
I guess that's it. right?
I can list any number of things that I've done/tried, but there have been so many! I'm not a noob when it comes to flashing ROMs, but I'm a new to the Acer Iconia Tab A500 and that's the problem, I think.
Anyway, I got the A500 with Honeycomb and I let it do the ICS OTA. No problem. Then I rooted it. No problem. I got to here: http://forum.xda-developers.com/showthread.php?p=31546261#post31546261
Then I decided to change the bootloader and that's when I borked something up. It would still boot into ICS just fine, but I couldn't get into recovery. I decided to try downgrading to Honeycomb 3.0.1 using the "unstable" update.zip, but that just ruined everything as now I'm completely stuck. I can't boot at all, it just hangs at the black screen with white Acer letters and red "boot verification failed" in the top left corner. Recovery gets me the dead Android image with the black exclamation point in a red triangle.
I have looked all over and I've read dozens of XDA threads...and I'm sure I'm missing the one thing I need to do to fix this, but heck if I know what it is. I have the Acer drivers installed on my computer, I have a variety of tools (nvflash, blackthund3r's apxflash, etc) waiting to be used if necessary.
So, please, I implore you...treat me like I'm dumb and walk me step-by-step through whatever it is I need to do to get my A500 back up and running! Thanks for your help!
UPDATE: Many hours later, I fixed it! I did another update using the full, stock image of Acer_A500_7.006.01_COM_GEN2 (just guessing about whether it would work or not) and it seems to have done it. Sure, I'm back on Honeycomb 3.2, but it worked. And then I was able to use AfterOTA to root and get the CWM bootloader on there.
So my next question: what do I need to do in order to get ICS? Can I just flash an ICS ROM from CWM, or do I need to update the bootloader in some way?
Thanks!
moonlightinwhite said:
I can list any number of things that I've done/tried, but there have been so many! I'm not a noob when it comes to flashing ROMs, but I'm a new to the Acer Iconia Tab A500 and that's the problem, I think.
Anyway, I got the A500 with Honeycomb and I let it do the ICS OTA. No problem. Then I rooted it. No problem. I got to here: http://forum.xda-developers.com/showthread.php?p=31546261#post31546261
Then I decided to change the bootloader and that's when I borked something up. It would still boot into ICS just fine, but I couldn't get into recovery. I decided to try downgrading to Honeycomb 3.0.1 using the "unstable" update.zip, but that just ruined everything as now I'm completely stuck. I can't boot at all, it just hangs at the black screen with white Acer letters and red "boot verification failed" in the top left corner. Recovery gets me the dead Android image with the black exclamation point in a red triangle.
I have looked all over and I've read dozens of XDA threads...and I'm sure I'm missing the one thing I need to do to fix this, but heck if I know what it is. I have the Acer drivers installed on my computer, I have a variety of tools (nvflash, blackthund3r's apxflash, etc) waiting to be used if necessary.
So, please, I implore you...treat me like I'm dumb and walk me step-by-step through whatever it is I need to do to get my A500 back up and running! Thanks for your help!
UPDATE: Many hours later, I fixed it! I did another update using the full, stock image of Acer_A500_7.006.01_COM_GEN2 (just guessing about whether it would work or not) and it seems to have done it. Sure, I'm back on Honeycomb 3.2, but it worked. And then I was able to use AfterOTA to root and get the CWM bootloader on there.
So my next question: what do I need to do in order to get ICS? Can I just flash an ICS ROM from CWM, or do I need to update the bootloader in some way?
Thanks!
Click to expand...
Click to collapse
Yes and No.
Now that you are on HC 3.2, you're going to need to do the process again.
IE: Unlocked Bootloader and CWM
The problem you had at first, is that when you flashed the UNL bootloader and CWM, you missed 1 tiny step. (lot of people forget to do this) And that is to delete the boot-recovery.p file from the /System. If you do not, you can install CWM, however, when you boot into stock ICS, your CWM gets overwritten. Another little trick from Acer
In the Dev Section, in the stickies part, Civato posted a link to a full ICS Stock Root Rom, With all the nasty stuff removed. (bootloader, recovery files). Download it, put it on your Ext Sd card.
http://forum.xda-developers.com/showpost.php?p=31572588&postcount=6
Then do the unlocked bootloader + Cwm again. Only THIS TIME, when it finishes, boot the tab immediately to CWM (vol- and PWR). And install the modified stock rom, or one of the custom roms.
Don;t forget to get your HC UID number written down before starting the process. Also it's good after ICS to get your ICS UID number also written down.
MD
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.
Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!
Pareeeee said:
Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!
Click to expand...
Click to collapse
Wow I thought I was the only one who had this issue. My A501 was working fine on Evil-A V2 (4.1.2) for many months and decided one night to crash and now stuck on V8 boot screen. Ive tried everything however I can get it to boot up on a 3.2 update.zip file.
The only recoveries I can get to work are TWRP 2.5.0.0 (on secboot)
Now I cant get it to flash anything other than 3.2.
It is formatted with ext4 partitions
whenever I try to flash it reboots to ACER download screen but the flashers wont get any further than that. (loads Acer boot recovery driver ok)
Any ideas?
Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:
Pareeeee said:
Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:
Click to expand...
Click to collapse
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here
LPMatt said:
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here
Click to expand...
Click to collapse
I think my MB is failing/has failed. Either that or something I flashed to it was badly corrupted.
Now my tab has stuck itself in apx mode, bootloader won't load, recovery won't load, every program I have (nvflash, TDv4, EUUs, Babsector, etc) fails. Babsector gives me the fatal error "command 12 NvError 0x120002" and "setting device: 2 3" which I've read means that the tab is shot. Adb.exe tells me the device is not detected, even though all the drivers are installed correctly.
I'm pretty bummed because I don't have the money to buy another tab at the moment, and I used it ALL the time, took it everywhere with me.
On the up-side, I've done some research and it seems if you disassemble your tab and sell the working parts (things like the screen, metal back panel, internal speakers - obviously NOT the MB though!) individually on eBay you can make a bit of your money back.
Can anyone direct me to some good links/video tutorials for dis-assembly?
whoops... I just started a new thread with a very similar issue... My tab also just involuntarily bricked itself... I've made some progress but it's still in bad shape... I don't know about you guys but I had been running at a steady 50% overclock; do you think that could have led to this?
Sorry Man
No @rwilpstra....my a500 is overclocked to 1504 ghz and it runs just fine......as for you pareeeee....Sorry man.....your device is gone....no apx...no fastboot....no recovery.....it's beyond minor corruption....it's like you somehow managed to corrupt every single part of the memory and every partition that there was on your device....you're better off disassembling it.:crying::crying: