Related
Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.
What's new? Thanks for sharing
Nothing's new but this a way to restore your A500 back to Acer_A500_1.141.01_EMEA_GEN3 if you had to restore the tablet with an foreign update.zip.
i c. thank you.
Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure
spaanplaat said:
Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.
Click to expand...
Click to collapse
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.
Euclid's Brother said:
Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure
Click to expand...
Click to collapse
Thanks for sharing. I will make a backup just in case.
mrlonely78 said:
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.
Click to expand...
Click to collapse
First you flash the boot.img but do not reboot (if you manually reboot you will get the LNX checksum error). Then check for the update. Once the update is downloaded it will automatically reboot to install the update. This is no problem as it will first check if there is a proper boot.img and then flash the update (it goes into recovery instead of just booting).
Some of us used the flash-stock-then-flash-CWM method of installing the ICS leak, but were left without a working recovery. The method below allows you to unlock the bootloader and install a custom CWM.
This method may or may not work for you. I take NO CREDIT for making this happen, I'm just writing a quick howto. Thanks to strra for making it convenient.
Typically, attempting to boot into Recovery would generate an error that recovery image was not verified (something along those lines).
Thanks for all the devs who made this possible - you guys are amazing. Donate to them if you can, they deserve it.
I TAKE NO RESPONSIBILITY IF YOU TURN YOUR A500 INTO A PAPERWEIGHT.
If you don't feel comfortable with this possibility, stop here.
Install the A500 drivers from Acer on PC (from Acer's site).
Install and launch Android terminal app on tablet. Run the following command:
Code:
dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt and look for androidboot.serialno. That is your CPUID. In my case, the serial number reported by the OS, on the box, in the MicroSD slot was NOT my cpuid.
Use Vache's site to convert that number into your SBK (four long hex values).
Extract all of the required files (batch.rar and nvflash) from strra's post into c:\nvflash.
Open up a Windows command prompt (cmd.exe) and then `cd c:\nvflash`.
Launch `run.bat`, but don't enter your SBK yet.
Power down the tablet.
Use a paper clip and hold down the Reset button. Do not release it. Hold down power for 3 secs and then release it. After another second, remove the paper clip. Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
Go back to the Windows command prompt and enter your SBK. Once you enter it, the process should begin. If you receive a USB write error, your SBK is incorrect.
Once the process begins, the Windows command prompt will read "Press any key when your A500 is in bootloader mode". Do not continue until the tablet is in Download Mode.
Once the tablet reads "download mode" (something along those lines), you are in bootloader mode. You can proceed and it will begin formatting the various partitions and installing the recovery.
Once the process completes, it should say PASS. You can then power off the tablet and power it back on again.
Make sure your tablet boots.
Power the tablet down and attempt to launch CWM via Power+VolDown.
PROTIP
Remount /system rw:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
Worked perfectly! Thanks!
yaw
worker for me too... thanks to all for this work!
good write-up
also, another protip:
if you right click the title bar of the command prompt, you can go to edit>paste to copy/paste the SBK... should make things a little easier
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Problem with recovery
When it launches download mode, it says entering download mode in acer boot screen and it stays like that. How much time should I wait until it enters download mode? Or is that download mode? When it shows PASS message then under appears a red text saying LNX image not certified or something like that, why? Please help me. Thanks.
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Luescoff said:
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Click to expand...
Click to collapse
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Click to expand...
Click to collapse
You can also add social Jogger
Link to facebook .
and all the links to there so called book shelf apps like link to games link to media .there are 4 of them They Hog resources even if you NEVER use them.I forget all there names and im on Vachs rom he has removed them all.
@jm77: Maybe could you split the DL link (batch.rar) and add the link to the OP of the orig. thread for downloading the bootloader binary (so when I update it people get the updated version directly)?
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
.......
Click to expand...
Click to collapse
Acer hid them in flexrom/app this time around!
Thanks for the help.
yaworski said:
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
Click to expand...
Click to collapse
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
So should the odmdata in the bat file be 0x300d8011 or 0xb00d8011. It has 0x300d8011, but i saw another post where it should match was EUU uses as 0xb00d8011.
Thanks.
castafiore said:
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
Click to expand...
Click to collapse
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
I want to make a backup of my current EBT before I try flashing this new one. When I enter APX mode (reset button + power), I get "Acer Picasso USB Boot-recovery driver" listed in my device manager.
Then I issue the command (i blanked out most of my SBK here).
Code:
nvflash --read 4 myboot.img --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
I've tried different flags like --bct --odmdate --configuration but i always get:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Following that, the device dissappears from my windows device manager.
I've also tried the first command from run.bat with both odmdata values
Code:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xb00d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
Both of these give the error message same message.
Any ideas?
---------- Post added at 01:21 PM ---------- Previous post was at 01:11 PM ----------
Also, just tried the run.bat as is (well.. i removed the "cls" so the screen woudln't blank. Get the same error..
Code:
C:\Users\james\Downloads\bootloader>run
****************************************************************
* This will boot your A500 into bootloader mode, *
* flash patched bootloader V2, and flash Thor Recovery 1.7 *
****************************************************************
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here : http://vache-android.com/v1/index.
php?site=sbk
Enter your SBK:0x8E000006 0x9C000001 0x22000002 0xF0000002
Loading bootloader...
Nvflash started
rcm version 0X4
[COLOR="Red"]Command send failed (usb write failed)
[/COLOR] **********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .
strra said:
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
Click to expand...
Click to collapse
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
castafiore said:
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
Click to expand...
Click to collapse
While in Android you need to remount your /system partition as writable and just delete the file with rm command . If you didn't replaced your boot.img yet with patched one, just use
Code:
fastboot boot boot.img
command where boot.img is patched kernel, then wait until Android is started (it will run on patched kernel from ram like with recovery).
When you run on patched kernel and you use adb shell then you will have root from the beginning. Then just use
Code:
mount -o remount,rw /system
and you can remove the file.
Thanks for your quick and clear answer, yaworski
Booting on this patched boot.img is the trick.
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
querobolo said:
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
Click to expand...
Click to collapse
Did you flash the patched bootloader in APX mode using nvflash? Because all above instructions work only on unlocked and patched bootloader with "secure" flag off.
Is there a way to completely recover a ThinkPad Tablet as I can with my LePad A1 ?
Would really like to upgrade to ICS, but I am unable to perform a complete factory reset... since even after doing this the tablet takes 10 minutes to boot and start throwing launcher errors when booted.
ThinkPadTablet_A310 (SC)
Still running Android 3.1 as no updates ever came through
Have rooted the device with Thinkpwn @djrbliss
gbraad said:
Is there a way to completely recover a ThinkPad Tablet as I can with my LePad A1 ?
Would really like to upgrade to ICS, but I am unable to perform a complete factory reset... since even after doing this the tablet takes 10 minutes to boot and start throwing launcher errors when booted.
ThinkPadTablet_A310 (SC)
Still running Android 3.1 as no updates ever came through
Have rooted the device with Thinkpwn @djrbliss
Click to expand...
Click to collapse
I can offer a full nandroid backup of a WE Tablet, it this helps
ThinkPad Tablet stuck in reboot-loop after ICS update
emuandco said:
I can offer a full nandroid backup of a WE Tablet, it this helps
Click to expand...
Click to collapse
Always helpful... but seems my problem was related to a broken build.prop. Luckily I had a copy of this file...
Was able to update my tablet from:
ThinkPadTablet_A310_02_0024_0065_SC
to:
ThinkPadTablet_A310_03_0069_0121_SC
But after successfully applying this update the device is in a reboot loop (only shows a static lenovo logo) and turns off, vibrates and turns on.
Iirc, some boot loops can be ended by doing a complete power down, i.e. power off. Press battery-disconnect button next to the SDcard. Then try a regular boot.
Full power down did not help
pwstein said:
Iirc, some boot loops can be ended by doing a complete power down, i.e. power off. Press battery-disconnect button next to the SDcard. Then try a regular boot.
Click to expand...
Click to collapse
Tried this, but did not help. At one stage it stayed on the bootlogo without rebooting, but never progressed. Still same...
Restored a nandroid with CWR
Was able to restore a nandroid with CWR and nvflash:
$ ./nvflash -w --bl ./04.EBT.img --go
$ ./nvflash -r --download 6 ./cwr/cwr-myrecovery.img
Reboot into recovery... and restored the backup ThinkPadTablet_0089_ROW_Root_CWM
Tablet booted and currently at the setup screen.
Note1: when using the recovery from the backup file itself the device rebooted before restoring. had to use my own backup
Note2: essentially I also got rid of the Chinese firmware
ROW image: http://forum.xda-developers.com/showpost.php?p=27981255&postcount=9
nvflash: http://forum.xda-developers.com/showpost.php?p=28148282&postcount=1
CWR: http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1 might be the one I use
Tried to update to ICS and bootloop/stuck again
To apply to ICS update I needed to modify the update.zip a little. When the system is running you enable USB debugging. Connect the tablet
[[email protected] adk]$ adb push ~/TPTRecover/busybox /sdcard/busybox
[[email protected] adk]$ adb shell
$ su
# mount -o rw,remount /system
# cd /system/xbin
# mv busybox busybox.ext
# cp /sdcard/busybox ./busybox
# chown root.shell busybox
# chmod 755 busybox
# exit
$ exit
Removed the indigo assert lines from META-INF/com/google/android/updater-script (maybe even the version check). And applied the update from the recovery menu; in this case this was still CWR (although I had to install my own backup again). Wiped cache before the restore...
The update got applied correctly... but on reboot it was again stuck on the Lenovo logo (no green nvidia tegra logo appeared). I suspected the boot .img does not get applied or flashed correctly. Since restoring this is essential to make the device boot normally again. Can you only update ICS from the stock recovery? Any clue or assistance is appreciated.
Note1: for the moment I restored nandroid again and run Honeycomb 3.1 (ROW)... having a Google market on a Chinese tablet is already a lot better.
Note2: below you can find my partition table. made a dump of all these just in case. Partition 7 seems to be the trouble for me? If so, can anyone provide me with an image for it?
Note3: after updating using CWM I also notice it does NOT remove clockworkmod with the stock recovery... this confirms my suspicions about the boot.img
----
BytesPerSector=4096
2. BCT StartSector=0 NumSectors=1024 Boot Configuration Table
3. PT StartSector=1024 NumSectors=512 Partition Table
4. EBT StartSector=1536 NumSectors=1536 Bootloader Table
5. GP1 StartSector=3072 NumSectors=512 ?
6. SOS StartSector=3584 NumSectors=1536 Recovery
7. LNX StartSector=5120 NumSectors=2048 Kernel
8. APP StartSector=7168 NumSectors=196608 Applications in System/ROM
9. CAC StartSector=203776 NumSectors=230400 CAChe
10. MSC StartSector=434176 NumSectors=512 ?
11. PIA StartSector=434688 NumSectors=131072 Pre-Install APK
12. SEC StartSector=565760 NumSectors=5120 ?
13. USP StartSector=570880 NumSectors=35840 ?
14. PDA StartSector=606720 NumSectors=5120 ?
15. UDA StartSector=611840 NumSectors=3234816 User Data (/sdcard)
16. GPT StartSector=3846656 NumSectors=512 ?
This is my backup made using nvflash.
Hope it helps.
I am using a ROW ICS stock rooted rom.
berbecverde said:
This is my backup made using nvflash.
Hope it helps.
I am using a ROW ICS stock rooted rom.
Click to expand...
Click to collapse
Does not seem to work...
... applied the update (reboot, nothing), flashed 07.lnx.img (reboot, nothing)
Only rolling back the ROW nandroid seems to work at the moment. I have tried pwstein's US image of ICS: http://forum.xda-developers.com/showpost.php?p=30799431&postcount=7 but also to no avail. Same problem... a static lenovo power-up image is shown. Seems more is needed to get ICS running on the tablet than what the nandroid images provide.
Does anyone have the stock recovery image?
gbraad said:
Does not seem to work...
... applied the update (reboot, nothing), flashed 07.lnx.img (reboot, nothing)
Only rolling back the ROW nandroid seems to work at the moment. I have tried pwstein's US image of ICS: http://forum.xda-developers.com/showpost.php?p=30799431&postcount=7 but also to no avail. Same problem... a static lenovo power-up image is shown. Seems more is needed to get ICS running on the tablet than what the nandroid images provide.
Does anyone have the stock recovery image?
Click to expand...
Click to collapse
Maybe if you flash all partitions using nvflash if would be ok.
If you can tell me how to back up all my partitions i can give it a try.
Right now i have the following partitions backed up:
04.ebt.img
06.sos.img
07.lnx.img
08.app.img
berbecverde said:
Maybe if you flash all partitions using nvflash if would be ok.
04.ebt.img
Click to expand...
Click to collapse
Fixed. The solution was to also allow the EBT to update, partition 4. I included an attachment with the files and a small script...
Additional info: http://m.51nb.com/thread-1244385-1-1.html
I have an ancient stock HC 3.2 and decided it would be nice to update. Forgetting completely about the fact that I had the ancient honeycomb bootloader as well, I loaded up an ICS update.zip and flashed. Now I'm stuck with a broken tab that displays Boot verification failed on startup. I have access to APX mode, but my computer does not seem to be cooperating with the drivers.
What to do?
Same kind of Problem
I have an A500 with OTA 4.01 o it.
I rooted it successively
Added bootloader ICS - worked fine - could see loader on reboot - used afterOTA
Backuped rom onto SD
Went in to recovery mode and installed JellyBean X rom - I wiped every thing including cache's
Installed fine, went to reboot and nothing.
Power light goes on and that's it.
I have tried several utilties but most need the computer to see A500 as a device or say failed, or do nothing
The "ejectAPX" shows on the eject hardware ion, and ACER USB drivers show up in device manager
I have tried resets, volume buttons etc - no go
The A500 screen did come up with "Acer Download Mode", but that as far as I get.
Any detailed help would be appreciated!
Win7 computer
David
Update
I do have mu cpuid and SBK #
I tried Blackthund3r APX flash tool, using A500_A501_ICS_V7_bootloader
BThdr says APX detected
Tab enters in to download mode with ACER logo on screen,
stage one ok
stage 2 just hangs at 3 quaters the way - I waited over 5 minutes
I have tried the following command with theresults after:
nvflash --bct flash.bct --setbct --odm
data 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x04FF
1E00 0xABE0D706 0xEBAA3304 0x20502103 --go
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x5 (0x1000005) flags: 0
used babsector and it worked
got back into recovery mode
Been there
Been there (I think I have a messed up reset button actually), but the only thing I can get my tablet back to life on is timmyDean´s root-3.2.1-V4.7z find in the forums extract the files then in the image folder you will find nvflash run the flash.bat but it reformats your flash etc. and brings you back to HC 3.2.1.
I have been through all of the tools and this was the only one that boots to android when its finish, which I need since I think my reset is stuck.
I needed to create ubuntu usb stick and run eppe's code to get my CPUID might help with usb connection issues to use similar too.
Then I was working with nvflash --read and the v8 bootloader stuff (since before my tablet soft bricked I was OTA ICS full stock), and was able to read off my user data with nvflash partition before I did the flashing. That way I saved all of my tablet pictures and video etc. (loop mounted the image read from that partition in ubuntu and was able to pull out any of my user data).
To get my data I used V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip see more at http://forum.xda-developers.com/showthread.php?t=1622425
Then I did:
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata --sbk %MYSBK% --sync
nvflash --resume --read 2 mybct.bct
nvflash --resume --getbct
nvflash --resume --getpartitiontable mypartitiontable.txt
nvflash --resume --read 13 UDA_raw3.img
I wish I would have backed up all of my partitions that way but I think I will get the replacement part first and then rebuilt the tablet.
Hope that helps
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
The used A500 APXflash
Then installed Jellytime X
The Jellytime was not working properly so I used root-3.2.1 V4 to take it back to 3.21, then OTA to 4.0.1
Root it again and then I stopped.. think I will stay with this rom, until 4.2 is super stable.
I think I did this procedure about 4 times in 2 days, as every rom that I tried either trashed the partition or boot loader, or didn't run properly.
I was lucky as I used afterOTA as part of flash the bootloader, and it saved a txt file with all my cpu info...
David_h99 said:
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
Click to expand...
Click to collapse
What do you means by that? what is this babsector?
HOw do you creating and formatting partitions with Babsector?
I had try badsector and it doesn't work so if you have another way to do it i am very interested!
thanks
you can get babsector here
narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
Make sure your computer sees tablet in APX mode, and the driver in device manager is the ACER USB driver
Then read info on how to run babsector
Hi,
this is how I (finally) fixed my "SD fix" freezes/lags on my S3 running CM 10.1/10.2. More about the SuddenDeath Fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1993044
and
http://forum.xda-developers.com/showthread.php?t=2091045
1. Install "Heimdall" or "Odin"
Heimdall: http://www.glassechidna.com.au/products/heimdall/
Odin: http://forum.xda-developers.com/showthread.php?t=2189539
2. Flash stock ROM XXEMG4 (Germany!)
XXEMG4: http://netload.in/dateia4mNpIO0nw/I9300XXEMG4_I9300DBTEMG3_DBT.rar.htm
3. Keep this ROM up to 3 days (you should not get any freezes)
4. Switch back to CWM Recovery
Download:
Recovery: http://www.clockworkmod.com/rommanager
Optional:
Baseband/Modem: http://perka.zapto.org/ (I chose XXEMB6 Odin version)
Bootloader: http://forum.xda-developers.com/showthread.php?t=2189063 (I chose XXEMG5)
Boot phone into Download mode.
on Linux:
Code:
optional: tar xvf bootLoader_I9300XXEMG5.tar.md5
optional: tar xvf Modem_XXEMB6_I9300.PFS.Odin.tar
optional: sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.2-i9300.img --BOOTLOADER sboot.bin --MODEM
modem.bin
or just: sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.2-i9300.img
5. TRIM your SSD
Download and install ADT Bundle: http://developer.android.com/sdk/index.html
Boot into CWM Recovery.
Code:
./adb shell mount /system
./adb shell fstrim -v /system
./adb shell fstrim -v /data
./adb shell fstrim -v /cache
6. Install latest CM10.2 nightly
Download: http://get.cm/?device=i9300
Code:
./adb push cm-10.2-20130xxxx-NIGHTLY-i9300.zip /data/
Boot into CWM and flash cm-10.2-20130xxxx-NIGHTLY-i9300.zip + Factory reset / wipe data
Finished.
Please let me know if it worked for you.
Regards,
engel
*** UPDATE ***
My phone is still freezing. It worked about two days and than started freezing again. Still no solution found (((
engel75 said:
*** UPDATE ***
My phone is still freezing. It worked about two days and than started freezing again. Still no solution found (((
Click to expand...
Click to collapse
Then delete or change the title of your thread as its totally misleading .
Or at least report to a mod via report button .
jje
Today I decided to install the latest Stock FW: I9300XXEMG4/I9300DBTEMG3
I did a complete wipe/factory reset and a flash counter reset in case I have to send my phone to samsung. And right now - I dot get any freezes?!
At the moment I plugged my phone to my Linux PC and I am running:
for i in 1 2 3 4 5 6 7 8 9 10; do ./adb shell dd if=/dev/zero of=/storage/sdcard0/tempfile$i bs=1085000 count=1024; done
This does create 10 >1GB files on my internal SSD storage and fill it up to ~100%
I will repeat this a couple of times to cause a freeze - bt I had right now no success after 3 times of running that loop (~30GB written). It looks like the Stock FW does not have any freeze problem?
http://forum.xda-developers.com/showthread.php?t=2240291