Related
Hi everyone. I'm totally new to Android. My relative have bought an a500 for me, and I should receive it in a couple of days. I'm very eager to join you guys .
I have read your forum vigorously for 2 months, since I started looking for a tablets. And I understand the risk of using Custom ROMs, since I used them on my Samsung i8910 (I know it's obsolete, but I will stick will it).
I have some questions about my coming a500:
1/ Look like it will definitely come with stock 3.2, so if I want to root it (in order to install ROMs), I will have to revert back to earlier version. I read the guide to revert to 3.0.1 carefully, and it seems that Method 2 is much easier. Can I use that method immediately when I got my hand on the a500?
2/ I read somewhere that I will need the UID if I happen to brick my a500. Do I really need it?
3/ Can I skip the step of backing up my device, since I don't have anything on it yet?
4/ If I follow the Method 2 above, after flashing the unstable 3.0.1, I will have to root it with Iconiaroot, and then install CWD? The CWD 1.6 from tegraowners site seem complicated for me to install . Can I install Acer Recovery Installer from Market, and then update CWD to 1.6 ? To update, just download 1.6, copy to micro sd and then boot into CWD, select update option? Can anyone please give me a short guide to do this .
5/ After having a rooted 3.0.1 with CWD installed, I can flash any ROMs I want? First, download the ROM, copy to micro sd, then boot into CWD, wipe everything (data, cache, dalvik cache), then select flash from zip file?
6/ I'm thinking of getting either Taboonay or Thor's. Which one is better? I heard that Thor's is faster, but no hardware screen rotation lock (still can use software lock), and no auto-brightness. I want everything work like champ (I can accept two above bugs), I don't need GPS, but stable Wifi and Bluetooth is must-have. I need recommendation, please.
7/ I don't have plan for 3G dongle right now, but maybe in future. So in that case, which ROMs is right for me? And is getting those dongles work hard to do? I read that patching the 3g patch in Thor's 14.2 cause battery rain fast (whether the dongle is in or out).
8/ There are also some news that ICS will be released by Acer in mid Jan, so is it worth install a custom ROMs now? Or I should wait?
Thanks a lot in advance.
redguardsoldier said:
1/ Look like it will definitely come with stock 3.2, so if I want to root it (in order to install ROMs), I will have to revert back to earlier version. I read the guide to revert to 3.0.1 carefully, and it seems that Method 2 is much easier. Can I use that method immediately when I got my hand on the a500?
Answer = Yes. But seriously, you may want to check it out for a couple of hours or so, to make sure there are no defects. No sense in creating headaches if you have to return it. Also, it may come with 3.1, so check it first.
2/ I read somewhere that I will need the UID if I happen to brick my a500. Do I really need it?
Answer = Depends on how bad you screw it up. But it's always good to have the number, just in case.
3/ Can I skip the step of backing up my device, since I don't have anything on it yet?
Answer = Yes. You can skip any step you wish. Just don't come crying when you fubar your device. Always do a recovery before flashing. Unless you just like to live on the edge.
4/ If I follow the Method 2 above, after flashing the unstable 3.0.1, I will have to root it with Iconiaroot, and then install CWD? The CWD 1.6 from tegraowners site seem complicated for me to install . Can I install Acer Recovery Installer from Market, and then update CWD to 1.6 ? To update, just download 1.6, copy to micro sd and then boot into CWD, select update option? Can anyone please give me a short guide to do this .
Answer = Root it and run the Acer Recovery tool. You wanna short guide? Ok. Run Acer Recovery. Install recovery. .
5/ After having a rooted 3.0.1 with CWD installed, I can flash any ROMs I want? First, download the ROM, copy to micro sd, then boot into CWD, wipe everything (data, cache, dalvik cache), then select flash from zip file?
Answer = Yes. Please do not do a n00b move and flash a kernel instead of a rom.
6/ I'm thinking of getting either Taboonay or Thor's. Which one is better? I heard that Thor's is faster, but no hardware screen rotation lock (still can use software lock), and no auto-brightness. I want everything work like champ (I can accept two above bugs), I don't need GPS, but stable Wifi and Bluetooth is must-have. I need recommendation, please.
Answer = Try them both and decide. Both are good.
7/ I don't have plan for 3G dongle right now, but maybe in future. So in that case, which ROMs is right for me? And is getting those dongles work hard to do? I read that patching the 3g patch in Thor's 14.2 cause battery rain fast (whether the dongle is in or out).
Answer = too many dongles out there. Get one first, then come back and ask.
8/ There are also some news that ICS will be released by Acer in mid Jan, so is it worth install a custom ROMs now? Or I should wait?
Answer = If you believe that, I have a bridge in the Mohave Desert to sell you. They will release it, "when" they release it. And it will probably have a different bootloader, so the root methods may not work, which could take some more time. And, it will probably be offered on their newer Tablets first.
QUOTE]
Click to expand...
Click to collapse
Moscow Desire said:
redguardsoldier said:
1/ Look like it will definitely come with stock 3.2, so if I want to root it (in order to install ROMs), I will have to revert back to earlier version. I read the guide to revert to 3.0.1 carefully, and it seems that Method 2 is much easier. Can I use that method immediately when I got my hand on the a500?
Answer = Yes. But seriously, you may want to check it out for a couple of hours or so, to make sure there are no defects. No sense in creating headaches if you have to return it. Also, it may come with 3.1, so check it first.
2/ I read somewhere that I will need the UID if I happen to brick my a500. Do I really need it?
Answer = Depends on how bad you screw it up. But it's always good to have the number, just in case.
3/ Can I skip the step of backing up my device, since I don't have anything on it yet?
Answer = Yes. You can skip any step you wish. Just don't come crying when you fubar your device. Always do a recovery before flashing. Unless you just like to live on the edge.
4/ If I follow the Method 2 above, after flashing the unstable 3.0.1, I will have to root it with Iconiaroot, and then install CWD? The CWD 1.6 from tegraowners site seem complicated for me to install . Can I install Acer Recovery Installer from Market, and then update CWD to 1.6 ? To update, just download 1.6, copy to micro sd and then boot into CWD, select update option? Can anyone please give me a short guide to do this .
Answer = Root it and run the Acer Recovery tool. You wanna short guide? Ok. Run Acer Recovery. Install recovery. .
5/ After having a rooted 3.0.1 with CWD installed, I can flash any ROMs I want? First, download the ROM, copy to micro sd, then boot into CWD, wipe everything (data, cache, dalvik cache), then select flash from zip file?
Answer = Yes. Please do not do a n00b move and flash a kernel instead of a rom.
6/ I'm thinking of getting either Taboonay or Thor's. Which one is better? I heard that Thor's is faster, but no hardware screen rotation lock (still can use software lock), and no auto-brightness. I want everything work like champ (I can accept two above bugs), I don't need GPS, but stable Wifi and Bluetooth is must-have. I need recommendation, please.
Answer = Try them both and decide. Both are good.
7/ I don't have plan for 3G dongle right now, but maybe in future. So in that case, which ROMs is right for me? And is getting those dongles work hard to do? I read that patching the 3g patch in Thor's 14.2 cause battery rain fast (whether the dongle is in or out).
Answer = too many dongles out there. Get one first, then come back and ask.
8/ There are also some news that ICS will be released by Acer in mid Jan, so is it worth install a custom ROMs now? Or I should wait?
Answer = If you believe that, I have a bridge in the Mohave Desert to sell you. They will release it, "when" they release it. And it will probably have a different bootloader, so the root methods may not work, which could take some more time. And, it will probably be offered on their newer Tablets first.
QUOTE]
Click to expand...
Click to collapse
Great answer, great sense of humor lol
Click to expand...
Click to collapse
Moscow Desire said:
redguardsoldier said:
1/ Look like it will definitely come with stock 3.2, so if I want to root it (in order to install ROMs), I will have to revert back to earlier version. I read the guide to revert to 3.0.1 carefully, and it seems that Method 2 is much easier. Can I use that method immediately when I got my hand on the a500?
Answer = Yes. But seriously, you may want to check it out for a couple of hours or so, to make sure there are no defects. No sense in creating headaches if you have to return it. Also, it may come with 3.1, so check it first.
2/ I read somewhere that I will need the UID if I happen to brick my a500. Do I really need it?
Answer = Depends on how bad you screw it up. But it's always good to have the number, just in case.
3/ Can I skip the step of backing up my device, since I don't have anything on it yet?
Answer = Yes. You can skip any step you wish. Just don't come crying when you fubar your device. Always do a recovery before flashing. Unless you just like to live on the edge.
4/ If I follow the Method 2 above, after flashing the unstable 3.0.1, I will have to root it with Iconiaroot, and then install CWD? The CWD 1.6 from tegraowners site seem complicated for me to install . Can I install Acer Recovery Installer from Market, and then update CWD to 1.6 ? To update, just download 1.6, copy to micro sd and then boot into CWD, select update option? Can anyone please give me a short guide to do this .
Answer = Root it and run the Acer Recovery tool. You wanna short guide? Ok. Run Acer Recovery. Install recovery. .
5/ After having a rooted 3.0.1 with CWD installed, I can flash any ROMs I want? First, download the ROM, copy to micro sd, then boot into CWD, wipe everything (data, cache, dalvik cache), then select flash from zip file?
Answer = Yes. Please do not do a n00b move and flash a kernel instead of a rom.
6/ I'm thinking of getting either Taboonay or Thor's. Which one is better? I heard that Thor's is faster, but no hardware screen rotation lock (still can use software lock), and no auto-brightness. I want everything work like champ (I can accept two above bugs), I don't need GPS, but stable Wifi and Bluetooth is must-have. I need recommendation, please.
Answer = Try them both and decide. Both are good.
7/ I don't have plan for 3G dongle right now, but maybe in future. So in that case, which ROMs is right for me? And is getting those dongles work hard to do? I read that patching the 3g patch in Thor's 14.2 cause battery rain fast (whether the dongle is in or out).
Answer = too many dongles out there. Get one first, then come back and ask.
8/ There are also some news that ICS will be released by Acer in mid Jan, so is it worth install a custom ROMs now? Or I should wait?
Answer = If you believe that, I have a bridge in the Mohave Desert to sell you. They will release it, "when" they release it. And it will probably have a different bootloader, so the root methods may not work, which could take some more time. And, it will probably be offered on their newer Tablets first.
QUOTE]
Click to expand...
Click to collapse
1/ My a500 is the BestBuy 229usd version, specs reviews said that it come with 3.2. I think my relative got enough time playing with it before hand it to me .
2/ Ok, I will get my UID, and store it somewhere, just in case .
3/ Did you mean backup the recovery image?
4/ Thks.
5/ I understand kernel vs ROM .
6&7/ Ok, look like I will go with Thor's. Since I know that Huawei dongles are working, I will exchange my gf's E173 for a new one. Anyway, haven't decide to go with 3g or not yet.
8/ Ok, stick to custom ROM .
Thanks a lot for your answers.
Click to expand...
Click to collapse
kjy2010 said:
Great answer, great sense of humor lol
Click to expand...
Click to collapse
Yeah, things have been way to serious around here lately
---------- Post added at 05:20 PM ---------- Previous post was at 05:08 PM ----------
redguardsoldier said:
Moscow Desire said:
3/ Did you mean backup the recovery image?
Answer = Not exactly. Before you make major changes like flash a rom/kernel, you should boot your tab to recovery, and make your recovery image from there. This generally creates the file on your sd card, where it's generally safe when you do your 3 wipes and flash.
6&7/ Ok, look like I will go with Thor's. Since I know that Huawei dongles are working, I will exchange my gf's E173 for a new one. Anyway, haven't decide to go with 3g or not yet.
Answer = Like I said, play with a couple of the roms out there. After you do this a couple times, you can flash 1 in about 10 minutes or less. Generally, you get a good feel for a rom within the first 30 minutes after flashing. Before loading it up with apps and customizing. Also, some kernels work better with some roms.
8/ Ok, stick to custom ROM .
Answer = Yeah, I think it's going to be awhile til a good solid usable version of ICS comes along. The devs are making good process and actually have something good enough for a daily driver... sort of, but, the real strides will be made after some of the newer devices are released. Best to wait for awhile, especially if your device is "mission critical", like mine. But it's ok to flash some of the stuff in work.
Thanks a lot for your answers.
Click to expand...
Click to collapse
No Problem. Welcome to the "Gang"
Click to expand...
Click to collapse
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
So, I'm not too tech savvy. I do get by though. About two months ago I was "computing" (haha) on my Acer a500 and the thing froze on me, when I restarted it, it when into a bootloop (I guess) of the ACER logo. I pretty much gave up and recently bought a Nexus 7. Anyways... when I tried entering in the recovery it really doesn't do much but show the lil green android guy trying to recover, but alas he falls over each time and a red triangle with an exclamation point appears. I've tried many a button combo to make it reset, recover... etc.. but still no luck. After reading some things, I saw it might be possible that its a hardware issue? Which made me wonder if I purchased a new or refurbished motherboard and plugged it all in, does anyone think it would work again? Or am I grossly underestimating whats going on here? I pretty much want to make it a mission to fix this damn thing, if only for bragging rights. Before I go test my luck and buy a motherboard, I want to know if I'm going to have to go through any other steps or processes so I don't get overly excited, then fail and throw this tablet against the side of my house.
Help me XDA users, you're my only hope.
Sincerely, Radnuh the pseudo tech-geek.
If you fall off your house, then I hope your tab falls my way.
One thing about the 50x, it's pretty bullet proof.
Were you rooted, with a CWM? Or was it stock?
And what OS was it running at the time it died? ICS or HC?
MD
Moscow Desire said:
If you fall off your house, then I hope your tab falls my way.
One thing about the 50x, it's pretty bullet proof.
Were you rooted, with a CWM? Or was it stock?
And what OS was it running at the time it died? ICS or HC?
MD
Click to expand...
Click to collapse
Hey! That's what I have gutters for! It was running ICS, stock not rooted. Oh and in the past I had a display problem. I had to open it up and reconnect the screen display connector, or whatever the technical term is! I've been reading quite a few stories of similar situations about this very same thing occuring, that's why I'm hoping its a software issue!
Sorry to bump this, but I'm just curious if it would be a simple plug n' play situation if I bought a new motherboard. Anyone? Bueller.... Bueller?
Radnuh said:
Sorry to bump this, but I'm just curious if it would be a simple plug n' play situation if I bought a new motherboard. Anyone? Bueller.... Bueller?
Click to expand...
Click to collapse
You don't need no stinking board. Don't sound like it the way you described. Try reflashing the darn thing using the techniques you can find all over this place. It's your chance not to be a chicken, to use Civato's expression, and to liberate yourself and your tablet. Above all, don't listen to your wife or girlfriend.
graphdarnell said:
You don't need no stinking board. Don't sound like it the way you described. Try reflashing the darn thing using the techniques you can find all over this place. It's your chance not to be a chicken, to use Civato's expression, and to liberate yourself and your tablet. Above all, don't listen to your wife or girlfriend.
Click to expand...
Click to collapse
Well I tried the whole putting stock ics as an update zip file on an sd then trying to recover, every time it starts then a few seconds later bam, red triangle. I also tried fastboot, but it would say waiting for device and that's it. I'm not really sure but I think I read something about having to unlock a bootloader, I definitely need to read some more into all this, lol. Is this normal though for this tablet to just freeze, and go into a bootloop?
Radnuh said:
Well I tried the whole putting stock ics as an update zip file on an sd then trying to recover, every time it starts then a few seconds later bam, red triangle. I also tried fastboot, but it would say waiting for device and that's it. I'm not really sure but I think I read something about having to unlock a bootloader, I definitely need to read some more into all this, lol. Is this normal though for this tablet to just freeze, and go into a bootloop?
Click to expand...
Click to collapse
I'm quoting MD for your information. Pay special heed to the 2 files on ICS stock. If you're in stock recovery, and it's corrupt, I doubt it it would let you flash anything. Start with TD's or EUUs found in Civato's stock Roms thread. Better yet, if you're game, get V8 and flash a newer custom ROM. Stock ROM ain't no fun.
"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"
graphdarnell said:
I'm quoting MD for your information. Pay special heed to the 2 files on ICS stock. If you're in stock recovery, and it's corrupt, I doubt it it would let you flash anything. Start with TD's or EUUs found in Civato's stock Roms thread. Better yet, if you're game, get V8 and flash a newer custom ROM. Stock ROM ain't no fun.
"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
I have much to learn, haha. Thank you for the info *starts researching*
Ok, here is what i have , I have a IConia a500 rooted with, link for forum and files, using ICS Root
(came with 3.1, ran all the iconia updates, to 4.0)
everything went fine, now... i am familiar with flashing roms, i have had a few android phones and have rooted them, and flashed custom roms on them. that is what i want to do with this, after doing over 4 hrs of reading, I have confused the crap out of myself. there is a lot of talk about things that i dont know much about..
-CPUID's
-ICS recoverys (bootloaders?)
Basically, all i want to do is add the CM Jelly time mod, but im not 100% on how i go abouts that? what do i need? i have the files and gapps, etc., i know i need a full wipe, but what recovery do i use? CWM? do i temp flash it or, pernament? after watching a few videos, i still dont think im ready, i diont want to brick this thing. i just want it to work with that rom. thanks any help and clarity is severly appriciated!
j
1. get yr cpuid and save it multiple places open a file explorer and go to /sys/firmware/fuse/acer_cpuid
2. then go to /system and rename/delete recovery-from-boot.p file - this will prevent your custom recovery being overwritten with the stock recovery.
3. have your custom rom on yr ext SD card, ready to flash ONCE you've flashed the unlocked bootloader
4.To flash the v8 bootloader you need to use nvFlash and there are a couple ways if going about that...
a) manually by using the guide in the OP of civato's BL thread
b) using one of the auto tools like afterOTA or apxFlash - links also in that same post...
c) you'll also get to pick a custom recovery and it will be flashed at the same time - cwm 1.7.3 is recommended until you're running stable
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
5) once flashed, boot straight to recovery
6) Do a nandroid backup then the wipes
7) Flash the rom
8) Reboot to recovery and wipe again
9) Job Done!
notes:
Everything you need to do this is in civato's BL OP - sorry can't post the link but its stickied in the Dev Forum
the afterOTA tool,
- saves all yr uid details etc in a txt file
- flashes v3 bootloader -
- it also installs the needed drivers too
- its pretty good at what it does...
seems some are having wifi issues with jellytime but the dev is working on this
you've done the right thing by asking questions before attempting anything, wish everyone was like you...if my post isn't clear then please let me know....for those of us used to the way things work with our Acer, its hard to remember how difficult it seemed when we were new!!
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
1. get yr cpuid and save it multiple places open a file explorer and go to /sys/firmware/fuse/acer_cpuid
2. then go to /system and rename/delete recovery-from-boot.p file - this will prevent your custom recovery being overwritten with the stock recovery.
3. have your custom rom on yr ext SD card, ready to flash ONCE you've flashed the unlocked bootloader
4.To flash the v8 bootloader you need to use nvFlash and there are a couple ways if going about that...
a) manually by using the guide in the OP of civato's BL thread
b) using one of the auto tools like afterOTA or apxFlash - links also in that same post...
c) you'll also get to pick a custom recovery and it will be flashed at the same time - cwm 1.7.3 is recommended until you're running stable
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
5) once flashed, boot straight to recovery
6) Do a nandroid backup then the wipes
7) Flash the rom
8) Reboot to recovery and wipe again
9) Job Done!
notes:
Everything you need to do this is in civato's BL OP - sorry can't post the link but its stickied in the Dev Forum
the afterOTA tool,
- saves all yr uid details etc in a txt file
- flashes v3 bootloader -
- it also installs the needed drivers too
- its pretty good at what it does...
seems some are having wifi issues with jellytime but the dev is working on this
you've done the right thing by asking questions before attempting anything, wish everyone was like you...if my post isn't clear then please let me know....for those of us used to the way things work with our Acer, its hard to remember how difficult it seemed when we were new!!
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks !
i have used the afterOTA and it would let me select the recovery i wanted to boot, is this permanent or temp? right now on my phone its the cwm, but i remember on my Nexus S, they recomended just pushing it, that way it was super hard to brick.. basically i just need to know if i need to run the afterOTA tool everytime i wanna boot into recovery? thats why i like my CM 10 for my Galaxy Nexus, i can choose to boot into it,
I think the hardest part of these simple tasks, is that there a 20 steps to something totally new, I used to unlock iphones for a living, I never knew what i was doing exactly, i had a rough idea, but i did know how to cut and paste. even going from my NS to GN its always been a few hrs to root/unlock, Being familiar with a lot of the steps, theres more with this tablet! EI, CPUID, APX? tons of warnings! the other things are the abriviations, they can be confusing.. soo
this is the only thing i didnt understand, does the OP dumb it down, or can you??
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
what is sbk, and why do i need it?
thanks again, i really appriciate it!
also, what is a LEAK? leaked rom?
jerkwagon said:
ok, thanks !
i have used the afterOTA and it would let me select the recovery i wanted to boot, is this permanent or temp? right now on my phone its the cwm, but i remember on my Nexus S, they recomended just pushing it, that way it was super hard to brick.. basically i just need to know if i need to run the afterOTA tool everytime i wanna boot into recovery? thats why i like my CM 10 for my Galaxy Nexus, i can choose to boot into it,
Click to expand...
Click to collapse
no m8, once you've 'flashed' via the tools its permanent -
there are flashable zips around (for recovery) but again, you need the unlocked bootloader first....once you have it then you can flash anything, anyhow you like. Even Acer Recovery Installer will work fine and you can flash a rom from there too, though that may require the paid version from memory.
the only time you will 'lose' the unlocked bootloader/recovery is if you need to rollback to HC - specifically 3.2 -
I think the hardest part of these simple tasks, is that there a 20 steps to something totally new, I used to unlock iphones for a living, I never knew what i was doing exactly, i had a rough idea, but i did know how to cut and paste. even going from my NS to GN its always been a few hrs to root/unlock, Being familiar with a lot of the steps, theres more with this tablet! EI, CPUID, APX? tons of warnings! the other things are the abriviations, they can be confusing.. soo
Click to expand...
Click to collapse
yeh I'm hearing you - this thread is a perfect example!!! I'd love to be able to say...root it, then flash cwm and the unlocked bootloader IF you want it, lol
Acer locked this baby down tight as - and if it werent for the work done by alot of the devs here, we'd still be stuck on factory stock.....The success these devs had is proved by the fact that there are still so many new folks coming here looking for info and help
this is the only thing i didnt understand, does the OP dumb it down, or can you??
d) From yr cpuid - generate yr sbk - how to do that is in the same OP
what is sbk, and why do i need it?
Click to expand...
Click to collapse
sbk = secure boot key....as you've discovered 'root' just isnt enough to flash anything...to flash anything you need nvididas nvFlash program PLUS the key to unlock the encryption which is hardwired into the ROM of the memory chip itself -(haahhhaa I think thats right) - The CPUID is unique to every tab (and this too may be hardwired into the chip as well) the sbk is a hex number based on the uid. there are a couple of generators around to do this for you, blackthund3er has one and so does vache....you've used afterOTA so this does the genration for you automatically - you can see it in the text file you saved
thanks again, i really appriciate it!
also, what is a LEAK? leaked rom?
Click to expand...
Click to collapse
yeh back in the day before acer released ics, 'someone' got hold of a leaked ics version, and this is where alot of the work was done on unlocking the bootloader...by the time acer got round to releasing ics - we had a more stable version than they ever had
So now you're unlocked and rooted, have all your ID's backed up and done a nandroid you can quite happily flash to your hearts content!!!!:good::good::good:
rgds dibb
dibb_nz said:
no m8, once you've 'flashed' via the tools its permanent -
there are flashable zips around (for recovery) but again, you need the unlocked bootloader first....once you have it then you can flash anything, anyhow you like. Even Acer Recovery Installer will work fine and you can flash a rom from there too, though that may require the paid version from memory.
the only time you will 'lose' the unlocked bootloader/recovery is if you need to rollback to HC - specifically 3.2 -
yeh I'm hearing you - this thread is a perfect example!!! I'd love to be able to say...root it, then flash cwm and the unlocked bootloader IF you want it, lol
Acer locked this baby down tight as - and if it werent for the work done by alot of the devs here, we'd still be stuck on factory stock.....The success these devs had is proved by the fact that there are still so many new folks coming here looking for info and help
sbk = secure boot key....as you've discovered 'root' just isnt enough to flash anything...to flash anything you need nvididas nvFlash program PLUS the key to unlock the encryption which is hardwired into the ROM of the memory chip itself -(haahhhaa I think thats right) - The CPUID is unique to every tab (and this too may be hardwired into the chip as well) the sbk is a hex number based on the uid. there are a couple of generators around to do this for you, blackthund3er has one and so does vache....you've used afterOTA so this does the genration for you automatically - you can see it in the text file you saved
yeh back in the day before acer released ics, 'someone' got hold of a leaked ics version, and this is where alot of the work was done on unlocking the bootloader...by the time acer got round to releasing ics - we had a more stable version than they ever had
So now you're unlocked and rooted, have all your ID's backed up and done a nandroid you can quite happily flash to your hearts content!!!!:good::good::good:
rgds dibb
Click to expand...
Click to collapse
ok after OTA generated my sbk and all that info, saved it to my computer... how do i unlock the bootloader? i want to install CWM, do i just need to download a file then use the advanced tab?, from cwm im sure i can get around, also, i dont know what apx mode is, ill do some more searching, thanks again.
ok this is really hard to do with windows8, my god, i have to do a lot of running around, i think im just going to give up, now, APX drivers are nto working, fml
had to manualy add the drivers, it was a pain the ass, now its all donw, hopefully i can get it going now!
s**t. use the last option ics v3.14.8 standard tab
jerkwagon said:
ok after OTA generated my sbk and all that info, saved it to my computer... how do i unlock the bootloader? i want to install CWM, do i just need to download a file then use the advanced tab?, from cwm im sure i can get around, also, i dont know what apx mode is, ill do some more searching, thanks again.
Click to expand...
Click to collapse
standard tab choose first option...keep an eye on the status bar while its flashing..should not take longer than 10mins.
You must then boot straight to recovery and flash yr rom from yr USB key
don't have to worry bout apx mode but yr tab should display.either Acer apx mode.or Acer download.mode at stage 3 of 4 in tool status bar.
if u.muck.up you'll learn all u ever wanted.to know about apx.mode
Sent from my GT-I9300 using Tapatalk 2
EDIT: the last option on the Standard Tab
DON'T FLASH THE FIRST ONE!!!!!!!