[BACKUP] .IMG files for Acer_A100_1.018.05_COM_GEN2 - Acer Iconia Tab A100

I've been out of the scene for a while so here is a contribution to the A100 community...​
Now that the A100 has been ROOTED, we can begin tinkering with the devices. As of now, I have not seen where we have Custom Recovery for the A100 available yet (THIS STATEMENT IS INCORRECT. SEE SECOND POST FOR RECOVERY. THANKS Theonew)so... I have made backups of the blocks 1-7 for OUR convenience... jejeje
THESE BACKUPS ARE STOCK, THEY ARE TO BE USED IN CASE YOU BRICK YOUR DEVICE OR IN OTHER CASES, TO INSTALL CUSTOM ROMS...​
Find a link to my Android Dropbox with the .IMG files, they are in .RAR format and will need to be extracted (They took too much space as .IMG files so had to compress... )
Anyway, if I'm correct, most of you will only need the mmcblk0p2 (BOOT) and mmcblk0p3 (SYSTEM) images. The others were uploaded in case you need them...
NOTE: The mmcblk0p3 (SYSTEM image) is divided into 2 parts, you MUST download both parts to extract the file. DropBox gave an error when uploading the whole file...
The information of the tablet this came from (ENSURE YOUR A100 MATCHES)
MODEL #: A100
ANDROID VERSION: 3.2
KERNEL VERSION: 2.6.36.3
BUILD NUMBER: Acer_A100_1.018.05_COM_GEN2
***If your tablet is different OR you prefer to do your own backups then follow this steps from a Terminal Emulator on your tablet (You MUST be rooted for this to work)***​
At the Terminal Emulator prompt type whats in GREEN:
su (Give SuperUser permissions if you have not done so...)
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2.img (BOOT img)
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img (SYSTEM img)
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7.img
HOPE THIS HELP... AND ENJOY...
DROPBOX LINKS:
mmcblk0p1: http://dl.dropbox.com/u/27178906/Acer%20A100/IMG%20Files/mmcblk0p1.rar
mmcblk0p2: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/BOOT_mmcblk0p2.rar
mmcblk0p3a: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/SYSTEM_mmcblk0p3.part1.rar
mmcblk0p3b: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/SYSTEM_mmcblk0p3.part2.rar
mmcblk0p4: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/mmcblk0p4.rar
mmcblk0p5: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/mmcblk0p5.rar
mmcblk0p6: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/mmcblk0p6.rar
mmcblk0p7: http://dl.dropbox.com/u/27178906/Acer A100/IMG Files/mmcblk0p7.rar
EDIT: WOW, I STAND CORRECTED BY THEONEW... I DID NOT REALIZE WE HAVE CUSTOM RECOVERY... JEJEJE, as stated, I have been out of the scene for a bit so... My apologies... I am still leaving the backups available in case they are nessesary for anyone. Thanks Theonew... jejeje

mapaz04 said:
As of now, I have not seen where we have Custom Recovery for the A100 available yet
Click to expand...
Click to collapse
We do have a custom recovery: http://forum.xda-developers.com/showthread.php?t=1558595.

Ohh man... Didnt even notice...
Thanks man... I didnt even notice that... I am still leaving the backups available for those that need it but I stand corrected on the Custom Recovery... jejeje

good to have those files because that recovery is not for the a100. its an a200 recovery.
but proper a100 cwm is under testing right now and should be released soon.
Sent from my SGH-I897 using xda premium

ptesmoke said:
good to have those files because that recovery is not for the a100. its an a200 recovery.
but proper a100 cwm is under testing right now and should be released soon.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Nice...can't wait for the release

mapaz...chk pm plz :-D
Sent from my SGH-I897 using xda premium

how could i use these files to recover if i happened to brick my tablet?

luthifer said:
how could i use these files to recover if i happened to brick my tablet?
Click to expand...
Click to collapse
Depends on the brick but as long as you have some form of adb you can push the partition image to the device to restore the partition to a working state. If you're bricked past adb then they won't help that I know of outside of maybe nvflash.
Tapatalked from my Galaxy S II.

pio_masaki said:
Depends on the brick but as long as you have some form of adb you can push the partition image to the device to restore the partition to a working state. If you're bricked past adb then they won't help that I know of outside of maybe nvflash.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Couldn't have said it better myself... thanks... jejeje

pio_masaki said:
Depends on the brick but as long as you have some form of adb you can push the partition image to the device to restore the partition to a working state.
Click to expand...
Click to collapse
What command could I run for that?

conorkickass said:
What command could I run for that?
Click to expand...
Click to collapse
To put a partition image? Something like this
abd shell dd if=partitionimage.img of=/dev/block/mmcblk0p#
Where # is the block ID of the partition you want to do.
It doesn't usually work on a brick because the partitions are "missing".
Tapatalked from my A100 - CM10 Build 4

Dying to figure out if I can use these with nvflash. Got a bricked (out of warranty, stock, unrooted, unmodified) A100 that shows up in APX mode. I've got APX drivers installed and I have nvflash command line utility. nvflash --getbct does...something. It spits out text at least. Now I just need to figure out the commands to flash back to Honeycomb. If that works, then I can get it back to ICS.
If it bricked because the NAND is dead, then so be it, I'll just get a cheap Chinese replacement or maybe a "old" 2011 Kindle Fire for Jelly Bean.

DeerSteak said:
Dying to figure out if I can use these with nvflash. Got a bricked (out of warranty, stock, unrooted, unmodified) A100 that shows up in APX mode. I've got APX drivers installed and I have nvflash command line utility. nvflash --getbct does...something. It spits out text at least. Now I just need to figure out the commands to flash back to Honeycomb. If that works, then I can get it back to ICS.
If it bricked because the NAND is dead, then so be it, I'll just get a cheap Chinese replacement or maybe a "old" 2011 Kindle Fire for Jelly Bean.
Click to expand...
Click to collapse
Nvflash can't be used on these devices, its covered in the brick thread. Acer locked us out so only they can repair it, and they don't flash it they replace the whole board. We could use it if someone figures out the sbk for it.
Sent from my Galaxy Nexus using Tapatalk 2

Bah, oh well. I always hated the screen on this thing anyway. :lol: My wife and daughter are both just sad because it croaked, and I can't even pinpoint it to something they did. It just...didn't wake up yesterday.

DeerSteak said:
Bah, oh well. I always hated the screen on this thing anyway. :lol: My wife and daughter are both just sad because it croaked, and I can't even pinpoint it to something they did. It just...didn't wake up yesterday.
Click to expand...
Click to collapse
If it makes you feel better its Acer using a known faulty emmc chip, likely nothing you did caused it.
Sent from my Galaxy Nexus using Tapatalk 2

We need the sbk...
Sent from my A100 using Tapatalk 2

das_webos_transformer said:
We need the sbk...
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
See post 13
Sent from my Galaxy Nexus using Tapatalk 2

would there be any reason as to why fast boot works but not adb? my situation is that my a100 is bricked... i can fastboot recoveries to try to install a new rom however i beleive the system is corrupt or missing and will not allow the recovery to see the SD card (i hope that makes sense to you). ive tried to flash roms via fastboot but i end up with the error reading
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
i figured i could try to adb push this backup and start fresh however adb isnt working for me but fast boot is... doesnt make sense to me... any suggestions?

ramontomzer said:
would there be any reason as to why fast boot works but not adb? my situation is that my a100 is bricked... i can fastboot recoveries to try to install a new rom however i beleive the system is corrupt or missing and will not allow the recovery to see the SD card (i hope that makes sense to you). ive tried to flash roms via fastboot but i end up with the error reading
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
i figured i could try to adb push this backup and start fresh however adb isnt working for me but fast boot is... doesnt make sense to me... any suggestions?
Click to expand...
Click to collapse
Fast boot doesn't flash recovery zips which is why you get that error. Fastboot and adb are totally different tools used at different times. Fastboot is used only for images, do some googling on how to use it vs adb for certain things.
Adb is only available in android or recovery, not bootloader. Fastboot is only available in boot loader not recovery or android.
These images would be used in fastboot on a HC system, not ICS.
If you're getting the mount errors there's not much you can do, its the emmc bug. Needs to go to acer for repair.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Fast boot doesn't flash recovery zips which is why you get that error. Fastboot and adb are totally different tools used at different times. Fastboot is used only for images, do some googling on how to use it vs adb for certain things.
Adb is only available in android or recovery, not bootloader. Fastboot is only available in boot loader not recovery or android.
These images would be used in fastboot on a HC system, not ICS.
If you're getting the mount errors there's not much you can do, its the emmc bug. Needs to go to acer for repair.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the clarification! might just be time for a new tablet since I bought this one second hand and im not sure if it would still be covered for warranty.

Related

Superwiped without rom

Hi!
I think I may have bricked my phone. I superwiped but I forgot to put a ROM
so now I have nothing on my phone.
Can I flash a ROM from my computer to my phone?
Thx in advance!
Flash a stock image using the Google images, then you can re-flash a custom one
If you still have cwr, mount USB in cwr, put a rom on there, flash from. If you don't have a recovery, you should be able to adb push the recovery file and flash through boot loader, then mount USB in recovery, copy rom to phone, flash.
Sent from my Galaxy Nexus using XDA App
Fastboot and download mode are your friends ;-)
Sent from my Galaxy Nexus using xda premium
EddyOS said:
Flash a stock image using the Google images, then you can re-flash a custom one
Click to expand...
Click to collapse
Where do I find them? I am sorry im a n00b :S
Cutting-TM said:
Fastboot and download mode are your friends ;-)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1 What he said! /\
look at thread that has the odin stock rom
If you're a n00b then why on earth did you unlock the phone in the first place? Surely you should've researched what you were doing in case something like this happened?
Kotd424 said:
Hi!
I think I may have bricked my phone. I superwiped but I forgot to put a ROM
so now I have nothing on my phone.
Can I flash a ROM from my computer to my phone?
Thx in advance!
Click to expand...
Click to collapse
all is very easy to fix
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.
Its all in here
http://groups.google.com/group/android-building/msg/43c3a418144fc6c5
This has helped me out twice already, and its where the factory images will be when the OTAs start, so of you're impatient and want them as soon as you can get them here
Sent from my Galaxy Nexus using Tapatalk
I think we need to put up a sticky again explaining what "brick" means.
mike1986. said:
all is very easy to fix
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.
Click to expand...
Click to collapse
Hi, when I write adb shell, it says device not found.
i have install usb drivers but it dosent work
spences10 said:
Its all in here
http://groups.google.com/group/android-building/msg/43c3a418144fc6c5
This has helped me out twice already, and its where the factory images will be when the OTAs start, so of you're impatient and want them as soon as you can get them here
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
thx!
nbdysreal said:
If you still have cwr, mount USB in cwr, put a rom on there, flash from. If you don't have a recovery, you should be able to adb push the recovery file and flash through boot loader, then mount USB in recovery, copy rom to phone, flash.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Mount usb isn't working yet on Galaxy Nexus CWM 5.5.0.2 recovery you need to have a working rom to put your files in the phone
ok, nobody knows why I get error: device not found when i type adb shell?
I cant make it work... :S would really appreciate it
Kotd424 said:
ok, nobody knows why I get error: device not found when i type adb shell?
I cant make it work... :S would really appreciate it
Click to expand...
Click to collapse
Did adb work before? Sounds like the drivers aren't installed properly
And if you are trying to use the images from what I linked earlier you need to be in fastboot not adb
Sent from my Galaxy Nexus using Tapatalk
spences10 said:
Did adb work before? Sounds like the drivers aren't installed properly
And if you are trying to use the images from what I linked earlier you need to be in fastboot not adb
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
ok i also have the fastboot but what do I write?
fastboot boot <image name> ? that didnt work for me
Got it working now.
Thx everybody for the help. I didnt know that you should use adb in recovery mode.

[REQ] flash_image for ICS

Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)
nxt said:
Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
I want to flash images on my device. It looks like the version of the file that has been out for years is not ICS compatible.
Sent from my Galaxy Nexus using Tapatalk
Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)
I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU
nxt said:
Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
Exactly.
josteink said:
I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU
Click to expand...
Click to collapse
flash_image is a utilty that will allow you to flash images to partitions on your device using a terminal emulater on your device or via adb. There is no need to have an unlocked bootloader, and no need to plug your device into a computer.
CWM uses this utility to flash images. It looks like Koush made some changes to it to make it work on ICS, as the original version no longers works properly on ICS (worked fine on Gingerbread and earlier).
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.
efrant said:
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.
Click to expand...
Click to collapse
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk
josteink said:
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks very much. I'll pm you if no one helps out.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
Anyone?... Bueller?... Anyone?...
efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Thanks for spending time on this, but, unfortunately it does not work on ICS. If it was from a build pre-December 18, it likely won't have the modifications in it.
I'm a noob as well, and I probably know less than you, so I don't think I'd be able to write a good step-by-step...
Hopefully someone will be able to help out. Thanks again.
josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Correction.
Using some cyanogen magic perl scripts, I managed to unpack the official 5.5.0.2 recovery (which works fine on my ICS gnex) and from that one I could extract KOush's build of flash_image, which you will find attached to this post.
It is significantly larger than the plain ICS flash_image, which I guess means it is statically built/linked and probably supports more devices, but I can't really say anything for sure.
Have a good one.
Now... I'm still looking into building fastboot FOR arm (so that I can run it from my asus transformer).
Anyone care to help me out getting gcc to build stuff for me?
Hmmm. I can't figure this out. None of the versions of flash_image seem to work in a terminal, yet CWM and ROM Manager obviously work using it.
If anyone can help shed some light on this, it would be more than welcome.
On older devices, you could use flash_image to flash radios, bootloaders, and recoveries, either through a terminal emulator on your device, or though an adb shell on your computer.
The syntax was: flash_image partition path-to-image-file.img
Trying to use this on my Galaxy Nexus produces an error:
can't find recovery partitionfailed with error: -1
Not sure what the problem is. It would be nice to get this working, as it would give users another on-device option to flash radios, bootloaders, and recoveries, without using ROM Manager.
Hey efrant, did u ever get anywhere with this?
danger-rat said:
Hey efrant, did u ever get anywhere with this?
Click to expand...
Click to collapse
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Sent from my Galaxy Nexus using Tapatalk
Trying flash_image from ROM Manager 5.0.0.1
efrant said:
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Click to expand...
Click to collapse
The apk for ROM Manager from ClockworkMod (Koush) contains a flash_image file in the assets folder. For ROM Manager 5.0.0.1, the file is 70.66K and has a MD5 checksum of a7291696dd4fc4208e397e31aa84bc9e.
I'm going to try copying it to /system/bin, setting ownership to root.root, and setting permissions to 750. I'll then see if it works on my Galaxy Nexus (LTE/CDMA) like the old CyanogenMod flash_image used to work.
I'll post back here once I'm done.
---------- Post added at 03:22 PM ---------- Previous post was at 03:16 PM ----------
chriv said:
I'll post back here once I'm done.
Click to expand...
Click to collapse
No luck. I used the flash_image that was in ROM Manager 5.0.0.1, and I had the same problem:
Code:
[email protected]:/mnt/sdcard/Download # flash_image recovery recovery.img
flash_image recovery recovery.img
can't find recovery partitionfailed with error: -1
255|[email protected]:/mnt/sdcard/Download #
---------- Post added at 03:27 PM ---------- Previous post was at 03:22 PM ----------
I also tried:
Code:
[email protected]:/mnt/sdcard/Download # flash_image --help
flash_image --help
usage: flash_image partition file.img
2|[email protected]:/mnt/sdcard/Download #
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?
chriv said:
[snip]
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?
Click to expand...
Click to collapse
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
But I haven't had the chance to work through it yes.
Sent from my Galaxy Nexus using Tapatalk
flash_image not the solution
efrant said:
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
Click to expand...
Click to collapse
I tried that. The error is the same. I also checked out the android source. The source for flash_image is bootable/recovery/mtdutils/flash_image.c .
flash_image enumerates all of the mtd partitions on the device from /proc/mtd, and compares their names with the first argument passed to it. If it doesn't find a match, it bails with the error "can't find %s partition" where %s is the first argument passed to flash_image.
You can enumerate the mtd partitions yourself. I did, and this is what I got:
Code:
[email protected]:/ $ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
[email protected]:/ $
As you can see, the only mtd partition on my Samsung Galaxy Nexus is w25q80. I could use flash_image with it, but I'm not that brave. For all I know, I could be overwriting the system partition, or the userdata partition.
The bottom line:
It is not likely that flash_image is being used by ROM Manager on the Galaxy Nexus, as flash_image is only capable of writing to the w25q80 mtd partition, and I don't know what it is! Koush must be using some other way to flash the recovery from the phone.
I'd be interested to know if other Galaxy Nexus users have something different for /proc/mtd.
I'd contact Koush and ask him how he writes the recovery on the Galaxy Nexus, but he never responds to my tweets! ;-)
I hope this helps some users, even if it just prevents other users from going on a wild goose chase with flash_image.
@chriv I get the same as you when I list the partitions.
Sent from my Galaxy Nexus using Tapatalk
Sorry to bump an old thread, but I found an alternative way to flash recovery images to my CDMA Galaxy Nexus without using flash_image (and without unlocking the bootloader/using fastboot). I found a post over on RootzWiki and the command is:
Code:
cat name-of-the-recovery.img > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
I did this and successfully reflashed the stock Google recovery image. I currently have a CM9 nightly running on the phone, the bootloader relocked and the stock recovery loaded (since leaving ClockworkMod Recovery installed would allow a thief to extract data via adb).
There are other things in the /by-name directory such as boot and radio so I'm guessing that it'd be possible to write those images as well (although I haven't tried it myself).
The only weird bug I've encountered is that ROM Manager still says that ClockworkMod Recovery is still installed for some reason (but it's not).

Sprint Restore To Stock! (Nandroids CWM+TWRP & Recovery IMG) Radios VIA ODIN!

Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint? NOW WITH RADIOS + FACTORY IMAGES!
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
RADIO FIX IN THE FORM OF AN ODIN FACTORY IMAGE!!!
THANK YOU SHABBYPENGUIN!!!!! WE LOVE YOU!
If this helped Donate To Me
This should be stickied too
Can someone post the stock zimage?
Wordlywisewiz said:
Need MoComing Soon:
Radio Fix (if you flashed a verizon radio)
Click to expand...
Click to collapse
I am desperate to have anyone dd the basebands & post them.
poontab said:
I am desperate to have anyone dd the basebands & post them.
Click to expand...
Click to collapse
We are working on them....
They appear to be combined into one radio image but it needs to be one for CD a one for lte
Sent from my Galaxy Nexus using xda premium
Thanks - always nice to have insurance - I think I know the answer but just to be sure - is the TWRP nandroid rooted or will I loose root when I run this?
mocsab said:
Thanks - always nice to have insurance - I think I know the answer but just to be sure - is the TWRP nandroid rooted or will I loose root when I run this?
Click to expand...
Click to collapse
All are unrooted but its easy to re root
Sent from my Galaxy Nexus using xda premium
Wordlywisewiz said:
All are unrooted but its easy to re root
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
WHat would I do - simply reflash the SU zip or would I have to re-push that to the phone ? (I know I sound like a noob here - but still learning the differnces between this phone and my old Epic4g - I recall seeing how sometimes everything on the SD card get's over written - but I wasn't sure if that happened in this case?)
mocsab said:
WHat would I do - simply reflash the SU zip or would I have to re-push that to the phone ? (I know I sound like a noob here - but still learning the differnces between this phone and my old Epic4g - I recall seeing how sometimes everything on the SD card get's over written - but I wasn't sure if that happened in this case?)
Click to expand...
Click to collapse
You sould just have to reflash
Unless you wiped your SD card
Sent from my Galaxy Nexus using xda premium
Update:
No new updates XD
Hows the radios coming along, i just borked mine and restored with the verizon img by mistake
joetemp75 said:
Hows the radios coming along, i just borked mine and restored with the verizon img by mistake
Click to expand...
Click to collapse
We are doing our best
Thanks I know you are and I appreciate all that you're doing.
Sent from my Transformer Prime TF201 using XDA Premium HD app
LTE Fixed.
C:\Galaxy Nexus ToolKit>adb-toolkit.exe shell
~ # ls
ls
boot etc sd-ext
cache init sdcard
data init.rc sys
datadata proc system
default.prop res tmp
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd sdcard
cd sdcard
/data/media # ls
ls
radio.img radio1.img
/data/media # dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
24576+1 records in
24576+1 records out
12583168 bytes (12.0MB) copied, 3.677856 seconds, 3.3MB/s
/data/media # dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 4.613159 seconds, 3.5MB/s
/data/media #
C:\Galaxy Nexus ToolKit>
Click to expand...
Click to collapse
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Tilton53 said:
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Click to expand...
Click to collapse
That's good
Hopefully when u figure out how to fix the radio and get mms working on aosp then the roms should be up and we will have a recovery radio in case something goes bad
Sent from my SPH-D700 using xda premium
Theoretically we basically have a factory image at this point we just need that cdma radio
Sent from my Galaxy Nexus using xda premium
Tilton53 said:
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Click to expand...
Click to collapse
Awesome we will get them... then hopefully we can make some sort of factory restore tool
Restore stock nandroid
Flash stock radios
Flash stock recovery
Then relock boot loader..
Sent from my Galaxy Nexus using xda premium
i think that this download for cwm recovery is wrong or something because everytime i go to flash it after putting it on my internal storage like i would with a custom rom it fails right off the bat.
please help me im lost on what to do now.
jsonger121 said:
i think that this download for cwm recovery is wrong or something because everytime i go to flash it after putting it on my internal storage like i would with a custom rom it fails right off the bat.
please help me im lost on what to do now.
Click to expand...
Click to collapse
Reread the first post. It is not a flashable ROM, it's a backup of the stock ROM. So you'll need to unzip it then place it on your internal storage under CWM/backup (or somewhere similar, not using CWM myself so unsure of the exact folder names) then boot into recovery and select Restore and then restore the backup you downloaded.
Sent from my Galaxy Nexus using Tapatalk 2
@Worldly: You still getting Error 927? I just got that issue and just cleared Market (Play Store) cache and it was fine.
Sent from my Galaxy Nexus using Tapatalk 2

[HOWTO]Recover From a Bad Flash - Now automated

Ok so you accidentally tried to Odin or CWM the wrong file to your phone. Well the good news is that if you can get into CWM with access to the sdcard(s) or access ADB we can fix it. If the phone won't power on at all, you can't access cwm with sdcard(s), ADB or Odin you are unfortunately out of luck. You will need to get it repaired by Sprint or send it off for a jtag repair.
Disclaimer: I am not responsible for anything that happens to your phone. You do this at your own risk.
If you don't own the E4GT do not use this guide because if your partitions are not the same as ours you will brick your phone.
If by chance you can get into Odin mode and your computer can see the phone go buy a lottery ticket J/K. All you have to do is download a full tar and Odin it back on. I won't go into details for that as it is well documented. Or you can still use this zip if you prefer.
I have automated the process of the restore. What this zip will do is flash the Agat 0.5.4 source kernel so you have cwm. It will flash the FH13 boot.bin, hidden.img, param.lfs and Sbl.bin. It will wipe Cache and Dalvik also.
This will not flash the modem, wipe data or replace system. So after you use this zip if your modem is also hosed flash a modem zip from CWM. Once you have recovered the phone you can flash whatever you want back on the phone.
Download CWM Odin Restore To FH13: http://d-h.st/3yZ
Copy the zip file to your phone and flash in custom recovery.
If you don't have access to the sdcard(s) but do have access to ADB proceed to the second post.
If you need some direct assistance you can PM me and I will work with you when possible.
You only have ADB access
For this method you will need CWM, ADB, Root and the image files to restore.
If you don't have ADB installed I have attached it to this post. I have also provided a link to the FH13 image files.
If you don't have ADB, extract the ADB directory to the root of C:. So you should see C:\ADB
You need to know where your ADB directory is located. If you used step 1 ADB it is C:\ADB. If you installed it on your own you should know where to find it.
Extract the images.zip into the ADB directory. You should now have the Images folder in the ADB folder.
Boot into CWM and attach your phone to the computer.
Open a command prompt and change directory to the ADB directory cd C:\ADB (or wherever your directory is).
Type adb push Images /tmp and hit enter.
You should see something like 6 files pushed. 0 files skipped.8465 KB/s (19271020 bytes in 2.223s).
Type adb shell and hit enter.
This part is critical. Make sure it is typed exactly or you can/will destroy your phone.
Copy and paste or type the following commands. If you copy and paste make sure you don't copy any leading or trailing spaces. Hit enter after each command.
You can skip any of the following commands if you know you don't need them. For example, if you know you only installed the Sbl.bin then you only need to enter that command. I have provided them all to cover all of the needs. If you are not sure just do them all.
dd if=/tmp/boot.bin of=/dev/block/mmcblk0p0
dd if=/tmp/hidden.img of=/dev/block/mmcblk0p12
dd if=/tmp/param.lfs of=/dev/block/mmcblk0p4
dd if=/tmp/Sbl.bin of=/dev/block/mmcblk0p2
dd if=/tmp/zImage of=/dev/block/mmcblk0p5
dd if=/tmp/zImage of=/dev/block/mmcblk0p6
You should see something like 2560+0 records in, 2560+0 records out, 1310720 bytes (1.3MB) copied, 0.265521 seconds, 4.7MB/s after each command.
Reboot your phone and it should boot up.
If it still doesn't boot something didn't take and we will need to work one on one.
Download the Images.zip: http://d-h.st/8gY
The bootloader restore has been proven to work on one phone so far. Thanks to pjkingphd for testing and confirming that it works.
great share!thanks for the tutorial.
crawrj said:
Please sticky this thread.
Click to expand...
Click to collapse
Hopefully this will be done.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
Crawrj my man.
Tappin' Typin'
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But then we wouldn't have anyone to test this... would we..
Great tutorial crawrj
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
Very nice. Thank you.
times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If the md5 is not right it will say so when you try to restore in cwm. It won't restore if they don't match. But I can throw up md5 for the sbl.
Sent from my SPH-D710 using xda premium
MD5 added. Sticky this please.
I have now automated the restore process in a zip file. You must be able to copy the zip file to the phone for it to work. I have flashed it about a dozen times but I would like to get a few brave testers to try it on your phone for me. Make sure you do a backup first! I have moved the manual commands to post two and revamped the instructions.
+1
Sticky or move to original development.
Sent from my piece of crap Zio until i get my E4GT back from Samsung, using XDA Premium app
Thread stuck. Thank you for helping out the community. :highfive:
jayharper08 said:
Thread stuck. Thank you for helping out the community. :highfive:
Click to expand...
Click to collapse
Thank you sir :highfive:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
PhAkEer said:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
Click to expand...
Click to collapse
Yeah this will fix you up. Once you get recovered you can flash whatever you want back on. Since you are an advanced user if you have a particular setup that you want to restore, just pull those files from the tar and place them in the Images folder of the zip.
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
PhAkEer said:
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
Click to expand...
Click to collapse
LOL nice. Let me know how it turns out.
crawrj said:
LOL nice. Let me know how it turns out.
Click to expand...
Click to collapse
Good as gold, as expected. I did end up only using the param.lfs but Im sure the rest will work great when I need it =)
Thanks again.... Itd been a long time since I last saw that sweet , sweeet gaudi_bootimage.jpg
Sent from my SPH-D710 using xda premium

Ubuntu Galaxy Nexus Image

I believe that ubuntu team will be posting there galaxy nexus image rom here at this link
http://cdimage.ubuntu.com/
please dont yell at me if im wrong..
nullbesign said:
I believe that ubuntu team will be posting there galaxy nexus image rom here at this link
http://cdimage.ubuntu.com/
please dont yell at me if im wrong..
Click to expand...
Click to collapse
Also check: https://wiki.ubuntu.com/TouchInstallProcess
I haven't seen anyone link to this yet, what's this about?
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
SkuzFoz said:
I haven't seen anyone link to this yet, what's this about?
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
Click to expand...
Click to collapse
I wondered there too and was wondering myself. it has the codenames for all the nexus devices, Galaxy Nexus (GSM), Nexus 4, Nexus 7 ect
i wlii try to flash the maguro file size 48mb....report at once....hope not to brick my gnex...lol
adambala said:
i wlii try to flash the maguro file size 48mb....report at once....hope not to brick my gnex...lol
Click to expand...
Click to collapse
I would have gone ahead but I'm not sure why there are different versions. Totally confused on boot and recovery images, but I've been out of the ROM loop for a long time.
nothing.....no boot.....just restoring my xenon rom...
The zip is flashable, contains a boot.img and has scripts to install stuff. the others are .IMG files, and the main phablet one is the biggest file at over 400megs.
edit: the one that is almost 500megs is a flashable zip too, has updater script. since that is the only one of that size, i bet that is the main ubuntu, and the others are the drivers, boot images, ect, specific to different devices.
yeap...i am downloading the img file now but i am not sure if i want to enter fastboot to flash it...
adambala said:
yeap...i am downloading the img file now but i am not sure if i want to enter fastboot to flash it...
Click to expand...
Click to collapse
We can flash it via fastboot like google images???????
Sent from my GT-I9001 using xda app-developers app
kagouro said:
We can flash it via fastboot like google images???????
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
No one knows yet. but you can try, but you risk bricking your phone. My galaxy nexus is dead now, charging the battery. Not going to experiment with my nexus 4, since it's my daily phone. by the time my gnex charges someone will figure it out or they'll be instructions posted on the ubuntu site.
I think we should fastboot flash all the img boot recovery system and then flash the zip. So start from the bottom of the page
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
Page offline ! They took it down.
j3r3myp said:
I think we should fastboot flash all the img boot recovery system and then flash the zip. So start from the bottom of the page
Click to expand...
Click to collapse
I'm going to guess you might need their recovery to flash it. Otherwise why bother making one.
So nice I hope to use it soon~~
The files are still there, they just put up a blank index.html file so you can't see the directory I have all the files for nexus 4 and Gnex
Here's the links to Gnex
http://cdimage.ubuntu.com/ubuntu-to...wc-demo/quantal-preinstalled-armel+maguro.zip
http://cdimage.ubuntu.com/ubuntu-to...mo/quantal-preinstalled-boot-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...uantal-preinstalled-recovery-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to.../quantal-preinstalled-system-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip
the last one is the ~500 meg file.
Luxferro said:
No one knows yet. but you can try, but you risk bricking your phone. My galaxy nexus is dead now, charging the battery. Not going to experiment with my nexus 4, since it's my daily phone. by the time my gnex charges someone will figure it out or they'll be instructions posted on the ubuntu site.
Click to expand...
Click to collapse
Brick it? Really?
As long as you dont flash a new bootloader, there's really no risk of bricking your phone, because, via your old bootloader you can always boot back into fastboot mode.
I'm not sure you know what the word "brick" means: Dead as a brick. Unrecoverable. Useless.
If it's recoverable, it's not a brick. Being in a state where you have to reflash some things in fastboot hardly constitutes a brick.
Sorry about the nitpick, but as a owner of much less open devices, where the risk of bricking $1k worth of equipment was a real risk when rooting/flashing, I find myself offended every time I see people whine about Nexus'es being "bricked".
Is the 500MB img for GNex, to your opinion?
Luxferro said:
The files are still there, they just put up a blank index.html file so you can't see the directory I have all the files for nexus 4 and Gnex
Here's the links to Gnex
http://cdimage.ubuntu.com/ubuntu-to...wc-demo/quantal-preinstalled-armel+maguro.zip
http://cdimage.ubuntu.com/ubuntu-to...mo/quantal-preinstalled-boot-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...uantal-preinstalled-recovery-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to.../quantal-preinstalled-system-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip
the last one is the ~500 meg file.
Click to expand...
Click to collapse
From a shell, just type the following:
Code:
# wget http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-ubuntu_stamp
Guys why new thread when v have already one Ubuntu discussion.. This makes people search more... close this thread
Sent from my Galaxy Nexus using Tapatalk 2
josteink said:
From a shell, just type the following:
Code:
# wget http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-ubuntu_stamp
Click to expand...
Click to collapse
I also mirrored the original page with all download links:
http://invalid.ed.ntnu.no/~jostein/ubuntu_images.html

Categories

Resources