Database Users

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.

Broke my recovery

Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?

mrkkk said:
Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?
Click to expand...
Click to collapse
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Make yourself a bootable CWM card by following the directions HERE
Then download the attached file that goes with your stock OS version, and put it into the root of the CWM card.
Boot the device with that card, and flash the file. Remove the SD card when done, and reboot. You should now be back into your CM7. At this point to can flash CWM back onto the NC, or leave it off.

GMPOWER said:
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Click to expand...
Click to collapse
Any way to determine that now?

mrkkk said:
Any way to determine that now?
Click to expand...
Click to collapse
Not really, the version 1.1.0 update came out at the end of January, and the guide that you linked to was made in February, so I would say that there is good chance that you were not on version 1.1.0. I would start with the 1.2.0 package, and work my way down.

No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?

mrkkk said:
No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?
Click to expand...
Click to collapse
The NC does NOT need CWM installed on the device to install or run CM7. A lot of people don't install it because of problems like this. I just did a restore of my CM7 image, and took the same steps as you. When it reboots and says install failed, I just shut it down and restarted right back into CM7.
The problem with the package that you had started with was the fact that besides the recovery files it installed a version of u-boot.bin that does not seem to be compatible with your device. The packages that I put up include each version specific u-boot.bin and recovery files.
I would flash the 1.2.0 file again, this time when it restarts and says install failed, just reboot the device, and it should go into CM7. At the very least, at this point you could do a full factory restore.

Update
before seeing your last message I built cwm 3.2.0.1 card using http://www.techerrata.com/dl.php?path=15&file=1gb_clockwork-3.2.0.1-eyeballer.zip
downloaded cm7 latest nightly
flashed it
applied titanium backup
was up in about an hour
BTW I do like CWM recovery, I can take nandroid backups time to time
Thanks for helping

[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] Some help for a nub and ICS + Flashing ROM

Got ICS, OTA (download) installed that no problem, downloaded the acer usb drivers and used ICS Root (blackthund3r). Now i want to install LightSpeed 4.4 (i know theres a newer version) I renamed it update.zip and did the power button + V- button but it says invalid image.
Now im a bit confused cause all this android stuff is new to me, I have the acer recovery installed but im not sure what to do with it. Tried renaming it to recovery.img it says it is flashing but nothing happens.
Kinda lost at what to do or how to get this rom working.... if someone could point me in the right direction it would be sweet
Fox

foxorroxors said:
I renamed it update.zip and did the power button + V- button but it says invalid image.
Fox
Click to expand...
Click to collapse
Yep. That was pretty n00b of ya (that little trick only works on signed official roms, and even then, only ify-ify)
Check this thread. It has the tools you need.
http://forum.xda-developers.com/showthread.php?t=1622425
You can skip the part about installing an ICS rom and rooting. You already did that. You need to do steps 1, 2, (partial 4) 5 or 6 basically.
Note after you rooted. Look at step 4 and delete the required file like it says, before going to steps 5 or 6. You have an option on which package to use. Personally, I like the exe package. But your choice.
This installs patched b-loader and CWM recovery so you can flash ICS only Roms.

Easy
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.

urbie47 said:
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
Click to expand...
Click to collapse
Acer recovery is fine if it'll install the patched Bootloader.
However, it doesn't make a user get his UID number, which is essential in case something happens in the future. Without your UID, you're basically toasted Or you're in for the long haul in figuring out how to unbrick a tab.

help
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...

ores992 said:
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).

Moscow Desire said:
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Click to expand...
Click to collapse
Thanks, but that link is dead

ores992 said:
Thanks, but that link is dead
Click to expand...
Click to collapse
Yeah, XDA did some cleaning up overnight. Try it now;
http://forum.xda-developers.com/showthread.php?t=1622425
MD

[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