Related
Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!
ldeijkva said:
Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!
Click to expand...
Click to collapse
Well, the big question...Which version of android do you currently run?
Which version of CWM did you try to flash?
Second question, which bootloader are you currently on? To find out, just run the acer recovery app and it will tell you when it starts.
And finally, which rom are you trying to install.
Then we can give you a more precise answer.
MD
Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.
ldeijkva said:
Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.
Click to expand...
Click to collapse
Glad you made some steps.
You still didn't answer my questions about bootloader.
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
This is why I asked which bootloader you were currently running. Because it makes a big difference since the release of ICS. Acer changed the playing rules.
Once again I ask you, to run AcerRecovery, and just get the version bootloader you are currently running. Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD
Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
ldeijkva said:
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
Moscow Desire said:
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD
Click to expand...
Click to collapse
nuff' said,.
ldeijkva said:
Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
If you plan on running ICS correctly now, and in the future, it is highly advisable to upgrade your bootloader to an ICS Unlocked version.
Civato posted a guide for doing just that (dev forums). It has all the info you need.
The reason SOD happens, is that in order to get a good root, and have an unlocked bootloader, certain things have to be done (hacks). With them. Remember, ICS kernel and bootloader communicate with each other. The hack to the kernel, resulted in the screwy display on boot. Also, SOD's can happen also (power management issue with wake loks). But at the time, in the beginning, it was a good method for getting ICS to run on a HC bootloader.
The unlocked ICS bootloader is the way to go. Every Dev's rom (made for ICS BL) has the kernel modified so that you not only get full root with no issues, you rarely get SOD anymore. Also some other enhancements have been added such as GPS tweaks for example.
If you get SOD, as I said, it happens so rarely now days that most can't remember that maybe they shut their tab off!
Most of the dev's (myself included) have quit support for HC BL based ICS roms. No reason for it.
Also remember, Acer is just starting to push ICS to the tabs a little. So builds will change on a regular basis. And the early builds will not be 100% stable. 95% probably. The rom you install today, may have a new version in a week. Who knows.
MD
or nightly versions ,sometimes its hard to keep up , I think ICS not only changed the rules but the "skys the limit" now and Devs see stuff and change it quickly!
Stuck on "ACER" logo at boot...won't boot & pc can't see it.
If I go into recovery I get: Android Guy & Box with arrow then a triangle with explanation point.
I was running ICS Rooted OTA.
I was trying to return the tablet to stock ICS & Boot Loader, when I messed things up.
(Sold Tablet--Need to restore it to factory look & feel.)
If someone could please advise I'd GREATLY appreciate it.
Thanks,
Rob
rgenins said:
Stuck on "ACER" logo at boot...won't boot & pc can't see it.
If I go into recovery I get: Android Guy & Box with arrow then a triangle with explanation point.
I was running ICS Rooted OTA.
I was trying to return the tablet to stock ICS & Boot Loader, when I messed things up.
(Sold Tablet--Need to restore it to factory look & feel.)
If someone could please advise I'd GREATLY appreciate it.
Thanks,
Rob
Click to expand...
Click to collapse
Have you tried to restore HC boot loader on an ICS rom. Don't worry just download one of the update package from the following link. As you mentioned you were on ICS rom then try ICS update only as it will update boot loader back to ics. Decrypt the file using Acer decrypter on the same link. Place the update.zip on your externel SD and then boot in recovery. Let other recovery install the update file.
http://forum.xda-developers.com/showthread.php?t=1113878
Only Acer logo
Hi all,
i have the problem that the A500 does nothing else but show the Acer logo.
The only thing i can do is use TWRP.
What did i try:
I tried flashing some roms using TWRP, also some older ones but no luck.
I tried using an empty SD-card and then start with Volume - and Power but no luck
What can i do...i am stuck...
Anyone? Still have a non-working Iconia 500...boohoo
Is it an option to flash it with Clockworkmod / CWM, reboot, flash it with an Acer ROM ?
jan99 said:
Anyone? Still have a non-working Iconia 500...boohoo
Is it an option to flash it with Clockworkmod / CWM, reboot, flash it with an Acer ROM ?
Click to expand...
Click to collapse
Well, telling us you've "tried some other ROMs" and have had "no luck" is pretty much telling us nothing at all.
What ROMs -exactly-?
What -exactly- do you do in TWRP?
What version of TWRP?
-Exactly- what error messages do you get?
What bootloader do you have? Sounds to me like you might have the HC bootloader when trying to install a stock ICS ROM. This is not going to work, period.
If you want help, you've got to provide enough info to help you.
Hi FloatingFatMan,
thanx for your answer.
I tried TWRP v2.1.0 with following roms:
Acer_A500_4.010.42_7.006.01_COM_GEN1
Acer_A500_7.014.14_041.203.01_COM_GEN1
cm-9-20120708-UNOFFICIAL-a500
recovery-ra-iconia-3.17-
gnm
Today i updated TWRP to v2.2.0 using openrecovery-twrp-2.2.0-picasso-signed and tried the cm-10-20120730-UNOFFICIAL-a500.zip rom. Same problem, after system reboot i only see the acer icon (permanent).
Also tried cm-9-20120708-UNOFFICIAL-a500.zip but same problem.
What can i do?
There are three main ingredients when customizing a device:
1) BOOTLOADER
2) RECOVERY
3) ROM/KERNEL
You provided answers to #2 and #3....what about #1??? What BOOTLOADER are you on?
Thanks for your reply.
I never changed my bootloader so that will be stock i think.
Finally i managed to get it going again. The trikck was to use a 3.0 stock rom. That worked.
From there i now use ICS (stock) which is fine at first. I had not seen anything but the Acer logo the past 2 weeks, so the Acer ICS will do perfectly now.
But for later on: can i use CM9 or CM10 with default bootloader + TWRP 2.2.0?
Rippster said:
There are three main ingredients when customizing a device:
1) BOOTLOADER
2) RECOVERY
3) ROM/KERNEL
You provided answers to #2 and #3....what about #1??? What BOOTLOADER are you on?
Click to expand...
Click to collapse
You'll need the unlocked ICS bootloader. Civato made a great guide over in the DEV section.
jan99 said:
Thanks for your reply.
I never changed my bootloader so that will be stock i think.
Finally i managed to get it going again. The trikck was to use a 3.0 stock rom. That worked.
From there i now use ICS (stock) which is fine at first. I had not seen anything but the Acer logo the past 2 weeks, so the Acer ICS will do perfectly now.
But for later on: can i use CM9 or CM10 with default bootloader + TWRP 2.2.0?
Click to expand...
Click to collapse
OK to explain for you.
ICS and JB require the ICS bootloader to run. They will not run on the HC bootloader unless specifically modified to do so. Also, no HC ROM will run on the ICS bootloader. This is why none of those ROMs were working for you.
Flashing stock ICS has updated your bootloader with the locked ICS one, so you probably won't be able to downgrade to any HC ROMs, or use any custom ROMs anymore. You can, however, use APX mode to install the unlocked ICS bootloader which will enable custom ROMs again.
I don't recommend trying to install ANY custom ROMs now until you'd flashed the unlocked bootloader. Instructions for this are in the Development section. Read VERY carefully before proceeding and if in doubt, don't proceed.
Hi FloatingFatMan,
thanks for the explanation.
I think i will stick to the stock rom at first. The APX way is not without risk...but maybe in the near future...
jan99 said:
Thanks for your reply.
I never changed my bootloader so that will be stock i think.
Finally i managed to get it going again. The trikck was to use a 3.0 stock rom. That worked.
From there i now use ICS (stock) which is fine at first. I had not seen anything but the Acer logo the past 2 weeks, so the Acer ICS will do perfectly now.
But for later on: can i use CM9 or CM10 with default bootloader + TWRP 2.2.0?
Click to expand...
Click to collapse
I am having the same "stuck on acer logo" issue. I am totally novice when talking about how to flash to ROM and stuff. Can you please direct to me a simple "dummy guide" on how to flash back to factory rom and fix my tablet. I tried the hard reset by holding down volume up and pwr button and on/off button, where i see the 'erasing..." but it still goes back to logo screen.
Please help me with my situation. Thanks in advance.
Have a look at this video
That is an example on how to do it.
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
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: