Database Users

Acer_A500_1.105.01_EMEA_GEN3 boot.img, flexrom.img, system.img and update.zip

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).

[Q] can't change CWM from 5.8.3.4

I'm stuck with only the ability to go into recovery while the rom doesn't boot and backups are stored on the uSD.
It's the Clockworkmod Recovery 5.8.3.4, and it looks like it doens't read from my uSD. I am able to connect via adb and push an other recovery.zip, that does work with the uSD, but it looks like the flashing goes ok, but when i reboot, i just end up in clockworkmod recovery 5.8.3.4 again.
adb push works to push multiple recovery.zip, but when i try with some rom.zip, i get, maybe because of the filesize, a 'protocol failure'.
I tried easyflasher 0.8.3, but it also doesn't have any effect.
Is there anyone who can help me guiding what else i can try or what the problem could be?

Try these steps
1: use adb to push a new recovery file (which you already did)
2: flash the zip
3: use the adb shell to execute the following command
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

[Q] Push /System to internal

Anyway to push this to internal memory?
I got /system damaged and phone is stuck in bootloop.
odin doesn't work as I am on MF3.
-----
SGH-I337
-----
Windows 7
OSX 10.9

pandaturtle64 said:
Anyway to push this to internal memory?
I got /system damaged and phone is stuck in bootloop.
odin doesn't work as I am on MF3.
-----
SGH-I337
-----
Windows 7
OSX 10.9
Click to expand...
Click to collapse
"Originally Posted by toastido View Post
I actually just did it and it did work. I used goo manager to try to write TWRP not thinking about MF3. Got a buddy who has a stock phone running MF3 (also an i337), temp pwnd it, pulled a dd of his recovery and dd'd it back to mine (rooted). I have a recovery again!
Here's the MF3 recovery image I used (attached and zipped to save space)
MD5 (recovery.img) = 8bb35b1bfbf01dfb83b30ffdbb243d87
On a stock device, enabled developer mode, adb, put in my sdcard with pwn on it, got root. Then did:
adb shell
$ /mnt/extSdCard/pwn
...
# dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
# exit
$ exit
adb pull /sdcard/recovery.img
*disconnected the donor phone*
adb push recovery.img /sdcard/
adb shell
$ su
# dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# exit
$ exit
Rebooted phone with vol+/home/power and it booted into recovery mode, whereas before this would get it stuck in the ODIN download screen.
YMMV of course, but it DOES work!.
-toast"
You can try to use ADB only problem is idk if works in download mode or not.

[q] help help help

My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..

umm
you said TWRP 2.3.4 did you mean 2.6.3.4? i know TWRP 2.6.3.4 supports OTG cables. If you have an OTG cable you could put a rom on a flash drive and it and try to flash it.

jarhead0231 said:
My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..
Click to expand...
Click to collapse
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696

Saving LG G2 after unwanted OTA caused boot loop
doktor buknasty said:
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.

Franketo said:
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.
Click to expand...
Click to collapse
DOES NOT WORK says adb not found.

jarhead0231 said:
DOES NOT WORK says adb not found.
Click to expand...
Click to collapse
Are you even on Linux? And have adb / Android sdk
Sent from my LG-D802

Manual upgrading Nexus 6 without wiping data.

A little how-to on upgrading your nexus phone without having to wipe your data if you rooted and installed some stuff onto system partition.
WARNING!
DO NOT USE THIS METHOD IF YOU ARE NOT GOOD AT USING COMMAND LINE! THIS HAS A POSSIBILITY OF BRICKING YOUR PHONE TO WHERE IT WONT BOOT.
Note:
You will loose the following when using this method:
-Custom Recovery
-Custom Kernel
-ANYTHING that is installed on the system partition including but not limited to: SU (root), Busybox, Xposed, etc.
What is needed:
-ADB (1.0.32+) and Fastboot
-Factory Image of Nexus 6 (https://developers.google.com/android/nexus/images?hl=en)
-- MUST BE THE SAME BUILD VERSION AS YOUR CURRENT VERSION!
--- Check under System > About Phone > Build Number
Step 1 (Catch the update url):
Open up command prompt/terminal and type in
Code:
adb logcat
.
From here you will get a lot of debug lines, dont worry about any of it.
What we are looking for is the url to the update file.
When adb logcat is ready, start the update for your phone. (Dont worry about restarting or whatnot, you wont be using the file it's downloaded anyway).
From the url, use that to download the update file to your computer.
Step 2 (Backup):
This is important as a just in case **** happens thing.
BACK UP YOUR PHONE if you have a custom recovery.
Don't think that this update method is foolproof.
Don't even think.
BACK IT UP!
Step 3 (Restore to "Factory"):
This is where it gets hairy.
Using the factory image you downloaded open up the "image-shamu-<build>.zip" file and extract "boot.img", "recovery.img", and
"system.img".
Restart your phone to bootloader either with adb or pressing and holding power + vol down.
From here, in a command prompt/terminal, type:
Code:
fastboot flash boot <boot.img path>
Code:
fastboot flash recovery <recovery.img path>
Code:
fastboot flash system <system.img path>
System image will take the longest and will be streamed to the phone so just wait until it's finished.
Step 4 (Upgrade):
ok, now that we are in "Factory" settings, start up your phone in recovery mode.
From the recovery screen you should see the little android with the red exclamation point icon thing.
Press and hold power and click the volume up button. Release power button.
From here, select
Code:
apply update from ADB
now in command prompt type:
Code:
adb sideload <update.zip path>
Step 5: ???
Step 6: Profit!
I have done this method twice and haven't experienced any problems myself. As stated above, this does have the possibility of mucking something up so be sure to have backups.
After everything is done, you are using your phone in stock mode.
flash your custom recovery and custom kernel if you'd like. Also reinstall root via custom recovery (twrp will let you know) and busybox.
Troubleshooting:
- Update says system partition has unexpected contents.
-- Reflash system.img.
- Get adb sideload error (xxx)
-- Make sure you have the latest version of adb and that your drivers for your phone are installed. Sometimes you have to manually install the adb drivers when in sideload mode.