Database Users

[Q] Downgrading 3.1 to 3.0.1

i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.

brewmaster said:
i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.
Click to expand...
Click to collapse
see this: http://forum.xda-developers.com/showthread.php?t=1113878
i dont see why you wouldn't be able to.

brewmaster said:
i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.
Click to expand...
Click to collapse
If you made a nandroid backup using clockworkmod (you should have), just do a full restore. ba-da-bing.
The acer recovery tool you mention is just for installing clockworkmod, it won't install a rom itself. clockwork mod does that.

i didn't create a backup so i guess i'm out of luck.

brewmaster said:
i didn't create a backup so i guess i'm out of luck.
Click to expand...
Click to collapse
Maybe you are not... Dexter provided a stock rom on his first post here:
http://forum.xda-developers.com/showthread.php?t=1121790

Check this post. flashing those 4 files (don't forget itsmagic), will put you at version 1.104.02_GEN1_COM (U.S. Stock).
Skip flashing the recovery if you don't want to lose ClockworkMod.
http://forum.xda-developers.com/showpost.php?p=14967064&postcount=206
If you want a specific version, ask someone to uplaod a ClockworkMod backup of boot, system and flexrom and use ClockworkMod to restore it.

thanks euclid. I might try this later but i can't figure out itsmagic. I installed the clockworkmod recovery with acer recovery installer. Can i just boot into recovery after that and have itsmagic work?
edit: i got its magic running then did the steps in the post minus the recovery. when it was done the device rebooted and got stuck on the acer logo. after that i booted into clockwork and installed the 3.1 update.zip and now my tablet is working fine again.

prep for OTA

hi guys. I was running us update 1.147.07 before installing cwr and then switched to 3.1 leaked. When I ran my restore it took me back to 1.147.04? I then used Acer recovery tool to install stock recovery 1.147.07 . But system build still sits at 1.147.04. Tried a factory reset and still at 1.147.04? Will I get the OTA too 3.1? I'm worried I need to somehow reinstall the 1.147.07 that was pushed to the tablet but can't pull from settings. Any help?

Any suggestions? I can restore to 3.1 leak rooted cwr or my stock 1.147.04

Sounds like a mismatched flexrom to me. Did you backup the flexrom partition?
Sent from my A500 using Tapatalk

You seems trying to use Acer recovery tool to return to 1.147.07 but it should be impossible! Acer recovery tool can help you to restore the stock RECOVERY but not your system so you can't go back to 1.147.07. You will need to find a 1.147.07 package(>300MB) and flash it. Hope this help you!

Let me know what you need to check my flexrom version. i wanna get this straightnend out

lamchei said:
You seems trying to use Acer recovery tool to return to 1.147.07 but it should be impossible! Acer recovery tool can help you to restore the stock RECOVERY but not your system so you can't go back to 1.147.07. You will need to find a 1.147.07 package(>300MB) and flash it. Hope this help you!
Click to expand...
Click to collapse
I used acer recovery to flash CWR. i then used CWR to flash 3.1 leak. I used CWR to then recover the stock backup I had. and then used acer recover to reflash stock recovery

Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.

[Q] K1 CM9 - CWM/will not boot after update

Can't post reply to DEV section yet.
I installed the updated CWM zip to my K1. Rebooted, got:
"Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002)."
Any ideas? installed so I could backup my current 3.2...guess it's gone

I met the same problem, we need nvflash again, just fellow the nvflash method.

Yes, a clean nvflash of the rooted stock image, and then a flash of CM9 should get it to work.
Are you still having issues?

Fixed
I didn't find any way to recover my 3.2. I went ahead and flashed to CM9 via nvflash. Install went well, was able to reboot into recovery, backup, ect.
I like the effort put into the port, thanks. I need to be able to play video and use bluetooth.
I had hoped to use my backup of 3.2 to switch back and forth, testing out the new builds, but lost my setup. No big deal.
I ended up putting the recovery.img into the Alpha3 3.2 nvflash package. I now have a working CWM and a nandroid of my 3.2 setup and the CM9 setup.
I'm not sure what the problem was with the CWM update zip package. I used the same recovery.img file...

[Q] Help, solving this mystery? Bootloader/partitions?

Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.

lowsum said:
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
Click to expand...
Click to collapse
Sounds like you have data leftover (either not a good enough wipe, or corrupted data)
Try this. Note that this will reformat your entire internal memory, but will ensure all remaining data is cleaned up and removed.
Before installing your rom;
1. Wipe User Data
2. Wipe Cache
3. Wipe DalviK
4. Wipe Battery Stats
go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This WILL format your entire internal memory, so if you have something important, you need to copy it out. Note that this should not effect things on the Ext SD Card.

Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!

lowsum said:
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
Click to expand...
Click to collapse
Well, more than likely it is indeed a bootloader issue. But you must understand, all these "leaked" ICS roms are what they are... BETA. And with each new leak, there's a different bootloader. So you have to pay attention to the instructions for the specific leak. Usually involves flashing a newer or older bootloader to match the rom.
Until Acer releases an "official" ICS Rom and source code for the 500/501, these issues are going to be around for awhile.
My choice, would be to run a 3.2.1 rom. Very few issues with some of the mildly modded ones. Then wait awhile, till the official ICS updates come out.
One good thing out of this, you learned some tricks on how to recovery from some "semi-bricks"

I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!

lowsum said:
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
Click to expand...
Click to collapse
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.

Moscow Desire said:
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Click to expand...
Click to collapse
It is possible to rebuild your partition structure from scratch (using SBK + bootloader + nvflash create command + bct + flash.cfg + system image + recovery image + boot image + probably some other things) but I'm not sure of anyone that has done this and I can't say I have myself. Using timmydean's method (with a, what looks like, leaked Acer A500 Flash Tool) should, in theory, wipe it clean and start again.
I created a flash bundle to reset back to version EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 (it's on the forum I use which I got tempbanned for mentioning publicly ) but it's untested. I see no reason it shouldn't work, however.

I tried another way to restore my tab, this time flashing a leak based rom with RA recovery instead. This time i had a little different behavior, during flash process, formating flexrom froze for a while outputing this error: Random Offset : 0x188 ...the rest flashed normally. At first boot it froze after 2sec during bootanimation, before it froze at the black & white lines.
I think I may have a corrupted flexrom partition, so Im wondering, does the recovery*doing a quick format erasing only the first sectors? If so, is there any way to do a deep format?

[Q] Error while restoring /data!

I got this error when I restore a full backup in CWM.
I explain better:
I made a full nandroid backup & a full titanium backup on my old PB G100W, then I received a brand new tablet from Acer.. Now I would restore back all my apps & data, so I made downgrade from HC 3.2.1 to HC 3.0.1 unstable, root, recovery 1.3.4, updated recovery to 1.7.3 touch and flashed Tegraowners v169.
I restored apps by Titanium and everything was ok, but 2 apps (Opera and a game weren't work properly). Tried something to solve it, but nothing.
I decided to restore my last nandroid backup from cwm 1.7.3, but nothing, restoring boot ok, restoring system ok, restoring data works for a while, almost at the end stops and give me back "Error while restoring /data!".
Maybe my backup could be corrupted or maybe it's a internal storage issue.
So I made a real format (data/media enabled) -> /format system.
Retried, nothing, get back the same error.
Flashed back recovery 1.3.4 by thor and retried restoring, works for a while, then stops again.
I tried another nandroid backup, different from the first one (of 1 week before), same procedure, and stops and the same point.
So, I got two corrupted backup or I'm missing something?
EDIT:
Solved!
I tried so much methods that I bricked the tab, but solved with TimmyDean's method, unbricked, reflashed and then (I don't know how) all Titanium backup were working and no issues.
Maybe the solution on titanium back is reboot a few times.
SOLVED!

3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.

Moscow Desire said:
3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.
Click to expand...
Click to collapse
I got some freezes on 1.7.3, a few in flashing/wiping time.. Then, I restored 1.3.4 recovery, and it worked fine.
I had to update the old version to 1.7.3 for tegraowners v169 flashing, so I made it. On reboot, it wasn't work anymore.. In recovery mode the screen was blinking, no way to get out. In normal boot the tab got stuck on Acer logo, in recovery mode blinked.
Used the unbricking method with new recovery image (the same 1.7.3 touch) and all went fine.
Rebooted, flashed, restored by titanium and no issues.
Faith mistery!
Thanks for answering master Moscow
Sent from my Packard Bell [email protected]_rv3 using Tapatalk