Database Users

Flash recovery image Droid Eris How To

First of all thanks to Amon_RA for this. I had no part in creating this. I am just providing a how to flash it. There may be an eaiser way but this is what worked for me.
First let me say I am on a Mac. If you are on windows the adb commands should work fine but I can't say how to get adb working for you.
1. download flash_image Here Link updated 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download Amon_AR's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
I made an automator script the help all of you having problems getting adb working. Make sure you have the android sdk downloaded and named android-sdk Put it in your home folder and then run this script. Let me know how it works for you.
Disclaimer: I am not responsible for any damage you may do to your phone. I am only providing instructions on what worked for me. This is very beta. Good luck. Enjoy the nandroid goodness.

First link is Dead...........
ooopps Srry my bad, Its up.

You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
adb push flash_image to /system/bin
Click to expand...
Click to collapse
I don't think there's a "to" in that command either. lol

testing567 said:
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
I don't think there's a "to" in that command either. lol
Click to expand...
Click to collapse
Thanks. I don't think the "to" is going to work either. I made the corrections.

Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.

Will this put the regular android on it or keep it the same, sorry just kinda getting started with android

coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
For testing567:
Do all the adb shell commands run as root against the 2.1_root install ... or maybe the above could be simplified even more by just running "adb root" first?
For Austinjs0102 (not a question)
This process only applies (at the moment) to phones with "2.1_root" - there isn't a path at present to go from "2.1_leak" to a rooted phone. Assuming that a way to roll back (or get root) for "2.1_leak" eventually is found, then the answer to your question is this: it is a process to apply a custom recovery partition to the phone that include tools that will allow you to perform complete phone backups and restore operations. This can be critical for devs who are experimenting with writing boot or system partitions to their phones - if something goes wrong with their experiments, they can "boot" their phone into recovery mode and restore back to a working configuration. To reiterate, though: this only applies to phones that are already rooted.
bftb0

Thanks a bunch that helps clear up info.
hopefully the hard working dev's here find a 2.1 leaked fix for us early people, if not then i may need to lose the phone lol.

Austinjs0102 said:
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Click to expand...
Click to collapse
I am in same boat as you...

Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc

DocTauri said:
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
Click to expand...
Click to collapse
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Doc,
I understand exactly what you are getting at... and also think I can explain why it's not easy.
First - what has been discovered so far was not a "root break-in", but rather an engineering ROM with root "built in". It is cryptographically signed so that a production phone will recognize the .zip file as a valid ROM. That first validation step has nothing to do with version numbers.
If the "SPL" on an unrooted phone was doing something as simple as looking at a couple of bytes in the initial file downloaded to the phone, then yes - doing what you suggest would work... just patch a few bytes using a hex editor. Unfortunately, the phone SPL is quite sophisiticated: it verifies the crypto signature on the entire zip file first, unpacks that zip, and then examines the contents of an individual file within the zip archive (and possibly even unpacks one of the YAFFS image files and then looks in a file within the YAFFS image) to read version numbers.
That means that the fundamental issue is the cryptographic signature on the .zip file. If you do anything which breaks step #1, step #2 (version # checks) are never reached. Certainly an individual file could be byte-patched, and then images and zip files could be re-assembled... but you would have no way to sign the zip with HTC's private key. Or you could even attempt to byte-patch the zip file - but then that would break the crypto signature. Either way, the crypto signature on the zip file is no longer valid.
If you have HTC's private RSA key, let us know!
bftb0

bftb0 said:
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
Click to expand...
Click to collapse
I added the reboot because. All I would get is out of memory errors. The reboot fixed that.
e.g.
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)

northmendo -
That first link (that you corrected) now points to the recovery image, not "flash_image".
Note that the "flash_image" executable which Amon_RA originally included with his first recovery (.zip) is identical to the /system/bin/flash_image binary which ships on the Eris with 1.5 (1.17.605.1); the md5sum signature (of both of those files) is:
16559f2c27d08ff1ddfcaca05fbf10fb flash_image
That's also the same md5 signature as the "flash_image" file which was posted to dl.dropbox.
I don't have 2.1_root installed on my phone, but if the same binary is already on the phone after installing the 2.1_root ROM, there's no need to include those steps in your instructions. It is also possible that even if the "2.1_root" version of /system/bin/flash_image is different, it would also work.
Note that the only reason I bring it up is that your instructions might be (a) unnecessary, and (b) are encouraging folks to overwrite a binary that is already on the phone. No harm (but unneeded) if it is the same, and unknown harm if it is different.
Also (while I'm at it)
901167f6b5541b488c8e0404bceb0631 recovery-RA-eris-v1.6.2.img ***
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
[Edit]***Wow, my post was obsolete the moment I posted it - don't know how I missed Amon_RA's announcement post. Note that there appears to be several versions of "v1.6.2" floating around now - make sure to check his post if you want the most recent.

bftb0 said:
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
Click to expand...
Click to collapse
I will keep the link updated to the newest version here. Also I tried the quicker method without success. I will try it again when I get home from work.
Thanks

bftb0 said:
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Click to expand...
Click to collapse
Sorry, didn't mean to. Understood on the explaination. I didn't realize it was a different rom image, I thought the key had been broken, allowing someone to resign a modified image.
Thanks!
Doc

I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?

sdk issues for flashing recovery...
Hey guys,
Im a noob but here's whats going on, Ive downloaded sdk extracted it to my c drive, ive downloaded all the required packages reccomended in the forum, Ive up dated my driver and still my machine doesnt recognize my phone...
Ive also extracted the recovery image to my tools directory and added the the path in enviromentals...
So at this point Im stuck as to how to get my pc (xp) phone and sdk in sync in order to get this recovery image working...So any advice would be highly appreciated. Thanks in advance.
Chris

Spencer_Moore said:
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
Click to expand...
Click to collapse
You could try this.
If you have your phone pluged in and type in to the terminal
adb reboot recovery [hit enter]
After you phone reboots it should come up with text options to do back-ups and restores. Do you get any of that?

Anyone know the key combo to get into recovery without adb?

having issues getting adb
got the command prompts working in xp, however while trying the methods here in the forum i am getting adb not foud errors. Any suggestions?

[Q] Stock AU A500

I figured since getting a replacement A500 and updating to Acer_A500_1.139.04_COM_GEN1 I would update this post with the images.
System.img - http://www.fileserve.com/file/gvemmYd
Flexrom.img - http://www.fileserve.com/file/Suq5yBG
Boot.img - http://www.fileserve.com/file/sSjqpME
Hope this helps anyone.
Kernel Information: Linux localhost 2.6.36.3 #1 SMP PREEMPT Wed May 11 22:11:55 CST 2011 armv7l GNU/Linux

103 views and no-one is able to do it? I am sure there are quite a few Aussies on this forum. :-(

i would if i knew how

splinter6 said:
i would if i knew how
Click to expand...
Click to collapse
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje

I got a replacement A500 from JB HiFi. I will update to Acer_A500_1.139.04_COM_GEN1 then create a system.img.

This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.

koprofile said:
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
Click to expand...
Click to collapse
I'm at work today. Will hopefully get the system.img uploaded this evening, should take ~2 hours being 600MB and all. :-(
I'm not sure if the flexrom.img is needed though.

that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP

eliousneo said:
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
Click to expand...
Click to collapse
Here is the untouched Acer_A500_1.139.04_COM_GEN1 system.img.
http://www.fileserve.com/file/gvemmYd

thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
I only rooted my a500 to be able to install apps to sd and that was a dissapointing move otherwise i think i may keep it stock from now on
thanking you in advance

eliousneo said:
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
Click to expand...
Click to collapse
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk

so that means use command line and copy image onto SD card?
Sounds simple enough just gotta wait for 8 hours for download
Than again juzman very helpfull

Juzman said:
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading

UnicornKaz said:
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
Click to expand...
Click to collapse
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6

Will we need the flexrom as well when flashing this system image?
Also, this thread contains some original kernel modules: http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
Will the modules linked there be compatible with this current AU system image in the event of gps/wifi issues?
Thanks again!

Juzman said:
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Click to expand...
Click to collapse
Is that definitely the correct md5 checksum? I've downloaded the file twice and both times I get an md5 of 850d68aac56169b211a4913de7e4e8e9
Can anyone else confirm?

mapaz04 said:
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
Click to expand...
Click to collapse
Can you say what terminal emulator to use or which is the best one to use?

urdaddi said:
Can you say what terminal emulator to use or which is the best one to use?
Click to expand...
Click to collapse
I used Better Terminal Emulator (with the extensions installed). Make sure after installing the extensions (after the prompt) to go into options, select root by default, then type exit (or CTRL-D) to close the terminal so it reinitializes with all the extensions (the icon on the taskbar must be gone). Afterwards do your stuff. After flashing the system.img the tablet might reboot (show the android boot logo) and cycle. Just power down holding the button long enough, and power back on, then flash the other img.

Hi Me again
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
I did the above thingy and it just extracted mmcblk0p3 into sdcard
How do i install it ??
i cant just run it so i presume there is some kind of command or something in terminal?

Is it possible to get the flexrom too?
Thanks

[REQUEST] Acer_A500_1.139.05_COM_GEN1

Can someone dump system and flexrom from ACER_A500_1.139.05_COM_GEN1, so that those that do not get the OTA or have previously flashed the chineese ROM can update manually their devices?
Commands are:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
Thanks!!!!

Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...

spades said:
Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...
Click to expand...
Click to collapse
Thanks! What modifications does this have?

huxflux2003 said:
Thanks! What modifications does this have?
Click to expand...
Click to collapse
Originally Posted by lord_voldemort666 View Post
do you guys know how to use google? A simple search led me to this...
"Below are the most important product improvements listed being covered by this update, which will further enrich the overall user experience;
1. Bluetooth Keyboard support added (currently for English language mapping only)
1. Touch panel performance improvement
1. G-sensor calibration
1. Fix for A500 turning off and on in sleep mode (Screen turning off and on when asleep?)
Firmware version change after FOTA update: 1.016.05_EMEA_GEN1 --> 1.139.05_EMEA_GEN1
Countries covered by EMEA_GEN1: UK / France / Italy / Spain
This update will also become available for the other countries soon, but as the exact release schedule is not fully available yet we are not able to provide you with any reliable release date at this moment."

i meant the uploaded system.img...like root modules and stuff...

huxflux2003 said:
Thanks! What modifications does this have?
Click to expand...
Click to collapse
I installed a few apps and that's it.
http://dl.dropbox.com/u/14023365/system.7z.001
http://dl.dropbox.com/u/14023365/system.7z.002
My 2 wifi files in the system/lib/module folder if needed..
http://dl.dropbox.com/u/14023365/wifi.zip

spades said:
I installed a few apps and that's it.
http://dl.dropbox.com/u/14023365/system.7z.001
http://dl.dropbox.com/u/14023365/system.7z.002
Click to expand...
Click to collapse
Hmmmmmm, unable to extract when renaming to a .7z extention. Is this an image file, or what should the extention of these files be?????
Thanks

bonzer2u said:
Hmmmmmm, unable to extract when renaming to a .7z extention. Is this an image file, or what should the extention of these files be?????
Thanks
Click to expand...
Click to collapse
It's actually a multi-part 7z. Don't rename, just extract.

spades said:
It's actually a multi-part 7z. Don't rename, just extract.
Click to expand...
Click to collapse
DOH..... works like a charm.

spades said:
Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...
Click to expand...
Click to collapse
I am in Ontario and only have v1.016.05_COM_GEN1
there are no update when hitting the system update button
unrooted ... got it few days ago.

I just flashed the Acer_A500_1.139.05_COM_GEN1 system image and flexrom to my system and I just noticed my version still shows Acer_A500_1.104.05_COM_GEN1
Hrm, is this normal?

Something may have gone wrong during the flash. I just flashed the flexrom and system images and mine reports as 1.139.05_COM_GEN1 now. There seems to be an issue with the wifi and GPS on mine now, though. I ran logcat while trying to enable wifi, and it looks like there's a driver missing.
Code:
E/WifiService( 115): Invoking mWifiStateMachine.setWifiEnabled
E/WifiStateMachine( 115): Failed to load driver!
E/WifiStateMachine( 115): DriverFailedState

kudakeru said:
Something may have gone wrong during the flash. I just flashed the flexrom and system images and mine reports as 1.139.05_COM_GEN1 now. There seems to be an issue with the wifi and GPS on mine now, though. I ran logcat while trying to enable wifi, and it looks like there's a driver missing.
Code:
E/WifiService( 115): Invoking mWifiStateMachine.setWifiEnabled
E/WifiStateMachine( 115): Failed to load driver!
E/WifiStateMachine( 115): DriverFailedState
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
and download the appropriate modules for your new kernel (the old modules don't load because they don't match with the kernel version). The correct ones are those at the bottom, with 991.
Decompress, copy to /system/lib/modules. Use insmod /system/lib/modules/bcm..... and insmod /system/lib/modules/scsi..... (not sure if necessary). Reboot.
BTW - Can anyone tell me where the option to calibrate the g-sensor is after the update? I cannot find it in settings, and the change log claims it's new.
Unfortunately the screen on issue persists after the update.

heyoh said:
I just flashed the Acer_A500_1.139.05_COM_GEN1 system image and flexrom to my system and I just noticed my version still shows Acer_A500_1.104.05_COM_GEN1
Hrm, is this normal?
Click to expand...
Click to collapse
Did you use the commands in the first post by any chance?
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
If yes, you've just overwritten the system.img and flexrom.img on the root of your sdcard. Those commands were for making the images from the actual partitions.
You will need to copy back system.img and flexrom.img to /sdcard. Afterwards do:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
Might be a good idea to reboot in between (at least I had to, but I was using the terminal on the A500 to flash the images).
After you're done you will notice you don't have WiFi anymore (it will say Error). See post above about how to get it back.

Odd thing, I still have root after the update (update shows in About correctly). Am wondering if I have missed anything. I had lots of frozen apps, but theoretically they shouldn't have been in the way. I cannot find the G-Sensor Calibration tool either (any idea where it is?)

adancau said:
Look here:
http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
and download the appropriate modules for your new kernel (the old modules don't load because they don't match with the kernel version). The correct ones are those at the bottom, with 991.
Decompress, copy to /system/lib/modules. Use insmod /system/lib/modules/bcm..... and insmod /system/lib/modules/scsi..... (not sure if necessary). Reboot.
BTW - Can anyone tell me where the option to calibrate the g-sensor is after the update? I cannot find it in settings, and the change log claims it's new.
Unfortunately the screen on issue persists after the update.
Click to expand...
Click to collapse
Aha, thanks! I tried with the kernel version you suggested, but insmod threw an exec failure. I looked at the kernel version again in device info, and it was 2.6.36.3-00001-g9b3ce2b, so I grabbed that archive (the middle of the three in the post you linked) and everything is working great now. I haven't had any luck finding the g-sensor calibration yet, though.

GPS status (https://market.android.com/details?id=app-com.eclipsim.gpsstatus2) I believe has a calibration feature in its new version.

adancau said:
Did you use the commands in the first post by any chance?
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
If yes, you've just overwritten the system.img and flexrom.img on the root of your sdcard. Those commands were for making the images from the actual partitions.
You will need to copy back system.img and flexrom.img to /sdcard. Afterwards do:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
Might be a good idea to reboot in between (at least I had to, but I was using the terminal on the A500 to flash the images).
After you're done you will notice you don't have WiFi anymore (it will say Error). See post above about how to get it back.
Click to expand...
Click to collapse
Can you please details how to use these dd commands, I got confused Thank you

lpachuong said:
Can you please details how to use these dd commands, I got confused Thank you
Click to expand...
Click to collapse
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
input file (if) is the image from the sdcard, output file (of) is the destination partition

where and how do i run these script? Thank you

[DEV] itsmagic

USE AT YOUR OWN RISK! YOU MAY BRICK YOUR DEVICE!
This is just a proof of concept. It will allow you to start any custom recovery. Sadly no completely working custom recovery is available. You can either try seraph's or vache's.
NOTE: Do not flash your kernel from recovery without calling itsmagic! Otherwise you will not be able to boot your device anymore.
How it works:
Checksums for all partitions are stored on mmcblk0p7. During boot, the actual checksums for boot.img and recovery.img are calculated and compared to the values stored in p7.
If a special pattern is applied to p7, the bootloader is triggered to recalculate the checksums and store them to p7. This pattern is also written when using normal recovery after installation of update.zip was succesful.
itsmagic does the same. It just applies the pattern, bootloader does the rest.
Backup:
Automatic method:
1. Download backup_tool
2. Extract somewhere on your PC.
3. Connect Iconia to your PC and ensure that USB debugging is enabled on your Iconia.
4. Execute 01_backup.bat and follow the instructions. The tool will take some time (~10 min), so be patient.
5. As soon as the batch file finished, check the backup folder for the following files:
Code:
p1, p2, p3, p5, p6, p7, mmcblk0_start, md5sums, uid.txt
6. Check if uid.txt contains a number like:
Code:
0x123456789abcdef0
If UID is empty then obtain your USB serial number as described at the end of this post.
Manual method:
1. Get your UID (= USB Serial number, has up to 16 chars) (see at the end of this post how to get). If you brick your device and do not know the UID, you are lost.
2. Backup all partitions (except cache + data) with dd:
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/dumps/p1
dd if=/dev/block/mmcblk0p2 of=/mnt/external_sd/dumps/p2
dd if=/dev/block/mmcblk0p3 of=/mnt/external_sd/dumps/p3
dd if=/dev/block/mmcblk0p5 of=/mnt/external_sd/dumps/p5
dd if=/dev/block/mmcblk0p6 of=/mnt/external_sd/dumps/p6
dd if=/dev/block/mmcblk0p7 of=/mnt/external_sd/dumps/p7
3. Backup the first 0x680000 bytes of mmcblk0:
Code:
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/mnt/external_sd/dumps/mmcblk0_start
4. Store them somewhere outside of your device.
Install itsmagic:
1. Copy itsmagic somewhere to /data or /cache, and set chmod 755 to it.
Flash a custom recovery:
1. dd the new recovery to mmcblk0p1:
e.g.
Code:
dd if=/mnt/external_sd/cwm.bin of=/dev/block/mmcblk0p1
2. Call itsmagic
3. Reboot. Bootloader will do the rest
4. Boot into recovery and see if it works
5. Every time you change mmcblk0p1 or mmcblk0p2, itsmagic must be called again.
Restore stock recovery:
Same as flashing a custom recovery but flash "p1" of you backup to mmcblk0p1 and call itsmagic.
Note:
Some devices seem to have a /system/etc/install-recovery.sh script. This will reflash the stock recovery every time you boot into normal kernel.
How to get the USB serial number:
1. Connect Iconia to your PC
2. Simple method (Window/Linux/Max), thx @daveid
Call:
Code:
adb devices
It will output something like this:
Code:
List of devices attached
370014740c00594 device
The number is the UID. Save it somewhere. You will need it if you ever brick your device.
Alternative methods (complicated):
2.b Linux
- call lsusb -v
- read the value of iSerial for Iconia
2.c Windows
- Open Device manager
- Goto Properties of Android USB Devices->Acer Composite ADB Interface
- Goto "Details" Tab
- Select "Parent" from the property selection.
- Read the value. It looks like this:
USB\VID_0502&PID_3325\370014740c00594
- The number after the last "/" is the UID.
2.d Windows (alternative method)
Download this tool (download link is nearly at the end of the page):
http://www.nirsoft.net/utils/usb_devices_view.html
- Open the tool
- Sort after VendorID
- Check all devices with VendorID = 0502 and ProductID = 3325 . There is also a "Serial Number" column.
Thanks
Thanks @vache + @rayman for their help.
Thanks to all testers of this tool.
What next
We need a working custom recovery. Sadly I'm quite busy the next few days so I don't have enough time to work on it. But there are enough experienced devs around.
Video
Here's the "faked" video again
http://www.youtube.com/watch?v=6IOayJUvvQI

... somehow the tools got lost
Edit: Added source

i think this is still not ready for user ..
but cant believe in last 3 days development of iconia can reach this far...
great guys...
sure next month we will have custom rom 3.1 for iconia

Finally!!
I am closing in with the 3.1 port of prime 1.4 .. so i needed this release..
so now we can figure out how to flash a working recovery next..

sc2k said:
Flash a custom recovery:
1. dd the new recovery to mmcblk0p1:
e.g.
Code:
dd if=/mnt/external_sd/cwm.bin of=/dev/block/mmcblk0p1
2. Call itsmagic
3. Reboot. Bootloader will do the rest
4. Boot into recovery and see if it works
5. Every time you change mmcblk0p1 or mmcblk0p2, itsmagic must be called again.
Click to expand...
Click to collapse
Does the cwm.bin file you mention actually exist?

eBug said:
Does the cwm.bin file you mention actually exist?
Click to expand...
Click to collapse
No Someone as to develop it.
There are some alpha Recoveries:
vache's recovery:
http://forum.xda-developers.com/showpost.php?p=14655235&postcount=395
seraphimserapis' recovery:
http://forum.xda-developers.com/showpost.php?p=14624515&postcount=326
But note:
YOU MUST CALL itsmagic from within update.zip! Otherwise your device will not boot anymore.
BTW: itsmagic needs libc.so to work

Spectacular, I now understand how this works. Thank you for supplying this to the community.
EDIT: When people begin putting custom roms together, might it be wise to edit the shutdown script to call itsmagic on every shutdown, just to be safe? Or does it introduce a performance penalty on next boot?

Is the backup_tool working?
And you all got your UID?

Has anyone contacted the rom manager guys? This seems like something they might be interested in...

Thanks sc2k! It is amazing!
Basically, I understand the logic, and I have 2 questions:
1) What is the use of UID in the whole process? What I see is getting it and backing it up, but why you say if we brick our device and don't know the UID, we are lost?
2)
sc2k said:
But note:
YOU MUST CALL itsmagic from within update.zip! Otherwise your device will not boot anymore.
Click to expand...
Click to collapse
What update.zip you are describing? You mean custom ROM/kernel? If flashing custom ROM without touching recovery, that means we do not need to call itsmagic again? Thanks.

sc2k said:
Is the backup_tool working?
And you all got your UID?
Click to expand...
Click to collapse
possible to use this on mac?
and is there any risk of brick by trting backup toll ?

ardatdat said:
Thanks sc2k! It is amazing!
Basically, I understand the logic, and I have 2 questions:
1) What is the use of UID in the whole process? What I see is getting it and backing it up, but why you say if we brick our device and don't know the UID, we are lost?
2)
What update.zip you are describing? You mean custom ROM/kernel? If flashing custom ROM without touching recovery, that means we do not need to call itsmagic again? Thanks.
Click to expand...
Click to collapse
1. UID hast some special meaning during unbricking process. I will provide details some days later. But if you do not have the UID, you will not be able to unbrick your device.
2. Yes, i mean any custom kernel. As boot.img is also verified against the checksum, a new kernel requires a new checksum. To recalculate a new checksum, itsmagic has to be used.

sc2k said:
1. UID hast some special meaning during unbricking process. I will provide details some days later. But if you do not have the UID, you will not be able to unbrick your device.
2. Yes, i mean any custom kernel. As boot.img is also verified against the checksum, a new kernel requires a new checksum. To recalculate a new checksum, itsmagic has to be used.
Click to expand...
Click to collapse
Wow! Thanks.
1. Now, I know that it is important. And I will remember it!
2. In theory, after flashing the custom kernel, in the updater-script, I should run the itsmagic. If I forget to embed it in the script, I can make another update.zip that 'only' runs itsmagic and flash it in the recovery. Right? (of coz, I cannot reboot in between...)
Arr.... btw, has acer released the kernel source? in some form of zip or github? I think under the GPL license, acer should have released it if 'someone' is asking for it.

interqd said:
possible to use this on mac?
and is there any risk of brick by trting backup toll ?
Click to expand...
Click to collapse
You will know the answer if you know what the backup script is doing

ardatdat said:
You will know the answer if you know what the backup script is doing
Click to expand...
Click to collapse
i dont understand script actually.. just a user here
but back up meant for backing up for future brickage right? so, it should not have brick possiblity..

I will put an APP together tomorrow, which should be able to install the recovery + run itsmagic all by a single press in the APP .
Let me see if i can have it ready for today or tomorrow..
but im sure it will make it all alot easier for all regular users.

In the nicest possible way, if you don't understand the script then at this point I wouldn't run it!
Give things a few more days to settle down.
EDIT: And Dexter beats me to it

themono said:
In the nicest possible way, if you don't understand the script then at this point I wouldn't run it!
Give things a few more days to settle down.
EDIT: And Dexter beats me to it
Click to expand...
Click to collapse
^ This. A thousand times this! If you don't know what the script is doing, you have zero business using it. Don't risk your device, wait until these smart guys have a chance to make it simpler to use, and hopefully safer for everybody!
Oh, and don't forget to, at the very least, pile thanks on these guys.

Thanks all the efforts up to now. I will try out the magic when I back home.
One question to ask: What is the worst situation? What I mean is that, if I forget to run itsmagic after flashing kernel, will I brick the device forever? And that I can no longer boot to recovery again?
Or, can I still go into recovery and restore from backup?
Thanks.

wow you guys are great!!! im just a regular user so i guess i just wait until all the smart guys make it simpler and safer. thanks for the great job.
anyway where did you guys learn all this thing??

Need help saving my phone

Can someone with rooted stock OK3 (and OK3 bootloaders) please do the following for me?
-busybox dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=1024 count=81920
-alternatively you can run this file in recovery which will dump the necessary files to /sdcard/Unbrick_files/: https://androidfilehost.com/?fid= 23578570567721355
-Upload the unbrick.img and send it to me
here are the guides that I am following (which have some precedent for working with SGS5):
http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419
I recently bricked my phone by accidentally flashing a BOD5 bootloader over a rooted OK3 (and OK3 bootloader) system. This obviously led to a hard brick, and I'm trying to see if I can fix it. Thanks.

I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.

CVertigo1 said:
I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.
Click to expand...
Click to collapse
jrkruse helped me out a lot and I was able to get my hands on an OK3 unbrick.img. IT WORKS. You're right about me posting the wrong code. The file that he used to get me the unbrick.img included the following code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000;
busybox gzip /external_sd/Unbrick_Files/*;
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258

Hariiiii said:
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258
Click to expand...
Click to collapse
you have linked the unbrick-creator.zip rather than the BOK3 unbrick.img

I am almost in the same situation as you. Can you please write the steps and the link for the BOK3.img ?

I think this is the correct link to the BOK3 unbrick img. You'll have to scroll down to the mediafire link
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/page11
Flash the file using win32diskimager.exe onto a microSD and boot into download mode.
Hope that works.
Also, if anyone has a rooted OG5, I would really appreciate an OG5 debrick.img!

Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.

CVertigo1 said:
Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.
Click to expand...
Click to collapse
Yes it does work, I can personally confirm it.

That's great!!! I'm assuming you were on the BOE1 bootloader, right?

CVertigo1 said:
That's great!!! I'm assuming you were on the BOE1 bootloader, right?
Click to expand...
Click to collapse
Yeah, that one is still used for the OK3 firmware, yeah?

Thanks for confirming that I did that right guys

jjdavis699 said:
Thanks for confirming that I did that right guys
Click to expand...
Click to collapse
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...

Hariiiii said:
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...
Click to expand...
Click to collapse
It's fine mate. Just enjoy your reinvigorated phone. I just did the file as something to waste a little time. Glad to see its working fine.