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).
Related
Has anyone successfully installed clockwork recovery on the continuum? I was tempted to try the fascinate instructions
Sent from my SCH-I400 using XDA App
I have used Titanium Back up with success
Okay, I can officially say that the Fascinate Clockwork Recovery does not work... Fails on "updating from Verizon" or something similar.... Then reboots... Is that Clockwork or the standard recovery?
Okay, I did not backup my stock recovery (stupid stupid stupid stupid), so can anyone get me that file and tell me which directory I need to shove it in?
Sent from my SCH-I400 using XDA App
I cannot remember the process to backup the recovery. What do you need me to do?
ThePravus said:
I cannot remember the process to backup the recovery. What do you need me to do?
Click to expand...
Click to collapse
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Or let me know... Somehow Swype changed that to injure...
Sent from my SCH-I400 using XDA App
I believe its more than just a file, you have to flash it.
Weudel said:
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
If you know why the directory is I can post the files. Man, we really need some devs...
Also, you can might not need to flash it, but you would probably need to use ABD then.
Sent from my SCH-I400 using XDA App
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
ThePravus said:
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
Click to expand...
Click to collapse
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
dfgged said:
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
If you can pull the stock recovery and post it, that would be great...
Otherwise, could one of you try booting into the stock recovery and see what it does... I tried to load the Fascinate Clockwork using ROM Manager and I'm not sure if it actually did anything or not... I don't think Clockwork would check with Verizon for updates.... All I have experience with is Amon Ra on my Eris..... Would be great if it just failed to change it.....
ThePravus said:
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
Click to expand...
Click to collapse
Awesome, thanks...
Looks like it worked... I guess I might not know for sure until the 2.2 OTA comes out.... Fingers crossed...
I've been working on porting clockwork. After running
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
with the path substitution, I get
Code:
unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Does anyone have any suggestions?
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
trailblazer101 said:
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
Click to expand...
Click to collapse
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
dfgged said:
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
There currently is not a Clockwork Recovery for the Continuum, but it is in the works...
Has anyone other than Weudel tried using this supposed stock recovery?
Sent from my SCH-I400 using XDA App
I'm using a Terminal Emulator on my phone trying to run the command to backup my current boot image. I'm typing "su" first for root privileges then typing "dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096" but I'm getting an error saying uknown operand if. Help?
Nevermind, I've discovered the problem. The code to backup your current boot image is "dd if=/dev/block/bml1 of=/sdcard/boot.bak bs=4096". There was an equal sign missing in the post above.
So I've completed the steps listed above and was under the impression this would restore my phone to stock. However, I still don't have the Verizon bloatware I deleted. Did I not understand what this process was meant to accomplish?
No longer supporting
How to install/
creepinm3 said:
How to install/
Click to expand...
Click to collapse
If you have gone through as many phones in your sig as you claim to you should be able to figure out by process of elimination how to install it, not trying to be mean but people round here just need to think more, its a recovery you install it the same way you install any recovery like when you first rooted your phone. Check the stickies prolly something in there to answer your question too.
I usually did rom manager. Too lazy for all the extraness. Thanks anyway.
burger1987 said:
If you have gone through as many phones in your sig as you claim to you should be able to figure out by process of elimination how to install it, not trying to be mean but people round here just need to think more, its a recovery you install it the same way you install any recovery like when you first rooted your phone. Check the stickies prolly something in there to answer your question too.
Click to expand...
Click to collapse
Like
* I'm just sayin......
Not every knows the other methods. But seems people in this community can't be nice enough to just explain a simple thing. With rom manager you don't have to do it. It does it for you. Just tossing up my 2 cents.
Good looking out oon this. Flashed it and worked like a charm.
Sent from my HTC Vision using XDA Premium App
Before you guys keep on flaming, rename to recovery.img, put it on the root of your sdcard, open terminal, and type:
Su
Flash_image recovery /sdcard/recovery.img
I swear to god this knowledge should be a prerequisite before being allowed to post in the dev forums..
mejorguille said:
Before you guys keep on flaming, rename to recovery.img, put it on the root of your sdcard, open terminal, and type:
Su
Flash_image recovery /sdcard/recovery.img
I swear to god this knowledge should be a prerequisite before being allowed to post in the dev forums..
Click to expand...
Click to collapse
You don't get it do you?
This is FLASHABLE!
Without going into terminal, you flash it like a rom
Exactly. I didn't have to go through all the renaming nonsense for this. Just drop it on the root of your SD, boot into recovery and then flash. Simple.
Sent from my HTC Vision using XDA Premium App
Are.Two said:
Exactly. I didn't have to go through all the renaming nonsense for this. Just drop it on the root of your SD, boot into recovery and then flash. Simple.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
He didn't try looking inside the zip. IF there's a meta folder it's flashable via recovery
LOL it's assumed when a recovery image is posted it is in the .img form, coz for a person first flashing stuff on their phone, they have to either flash a custom recovery thru Rom Manager, or the flash_image binary in terminal. It's impossible to flash a .zip without a custom recovery in the first place.
Just sayin...
Is there an overview of the changes in this version compared to the last?
I suggest people who want to know what the changes are learn to read github...
https://github.com/CyanogenMod/android_bootable_recovery
Sent from my PG06100 using XDA Premium App
mejorguille said:
Before you guys keep on flaming, rename to recovery.img, put it on the root of your sdcard, open terminal, and type:
Su
Flash_image recovery /sdcard/recovery.img
I swear to god this knowledge should be a prerequisite before being allowed to post in the dev forums..
Click to expand...
Click to collapse
::facepalm::
djfoo000 said:
LOL it's assumed when a recovery image is posted it is in the .img form, coz for a person first flashing stuff on their phone, they have to either flash a custom recovery thru Rom Manager, or the flash_image binary in terminal. It's impossible to flash a .zip without a custom recovery in the first place.
Just sayin...
Click to expand...
Click to collapse
it's also probably assumed that any noob isn't going to be attempting an update of something they have no idea what it even is, or how to do so... for those that have a clue, they would know that all they need to do is extract the .img and place it on root of sdcard or whatever... just sayin...
Thanx for the Recovery & The laughs!!
Excellent work.
burger1987 said:
If you have gone through as many phones in your sig as you claim to you should be able to figure out by process of elimination how to install it, not trying to be mean but people round here just need to think more, its a recovery you install it the same way you install any recovery like when you first rooted your phone. Check the stickies prolly something in there to answer your question too.
Click to expand...
Click to collapse
LMFAO
No problem at all guys. When theres an update I'll release that as well
Sent from my SGH-T959 using Tapatalk
What do you mean by "for those of you who missed wiping from recovery"? I wipe from recovery just fine on the latest Clockwork Recovery.
Why would you not take the short amount of time to list the specific changes in the OP for everyone?
Why would you not take the time to list simple step by step instructions for those who need them in the OP? (At least you added that its a flashable zip...prior to that there was no information whatsoever)
And I thought I was lazy...
G1ForFun said:
What do you mean by "for those of you who missed wiping from recovery"? I wipe from recovery just fine on the latest Clockwork Recovery.
Why would you not take the short amount of time to list the specific changes in the OP for everyone?
Why would you not take the time to list simple step by step instructions for those who need them in the OP? (At least you added that its a flashable zip...prior to that there was no information whatsoever)
And I thought I was lazy...
Click to expand...
Click to collapse
all that has changed from koush's github is the ext support. So you want us to copy everything from his github and put it here with all the dates when and what he changed?
lol i gotta say.... whats new in this recovery? i looked at github and it dont seem too have much of a difference usage wise.... for basic users like me it isnt a "must update" right?
and, ROFL at all the people who dint get "flashable" xD
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.
I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
mtmjr90 said:
I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
Click to expand...
Click to collapse
Here's the stock kernel for you
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Edit: Oh, also is that zip flashable via CWM?
Sent from my Galaxy Nexus using Tapatalk 2
I got it from one of the Jellybean threads, but with the sheer volume of JB threads today, I can't remember which. I think it's the main JB thread in General.
The only thing I did was rename it from StockKernel.zip and added the JB prefix so as not to lose it in my mess of files
Ah, sounds good. Thanks again!
Sent from my Galaxy Nexus using Tapatalk 2
mtmjr90 said:
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Click to expand...
Click to collapse
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
Click to expand...
Click to collapse
Is that via a terminal emulator on the device then?
efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Click to expand...
Click to collapse
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
mtmjr90 said:
Is that via a terminal emulator on the device then?
Click to expand...
Click to collapse
Either or.
---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------
drewcam888 said:
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
Click to expand...
Click to collapse
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
efrant said:
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
Click to expand...
Click to collapse
I don't see any option to restore only the kernel. Where is this option?
drewcam888 said:
I don't see any option to restore only the kernel. Where is this option?
Click to expand...
Click to collapse
Under "backup and restore" under "advanced restore", select boot image.
Sent from my Galaxy Nexus using Tapatalk 2
Only a little bug for me:
From settings-->storage (memoria in italian) It can't see all the files in the sdcard, also doesn't see a lot of music (but I can see those music files with play music app)...
Any other thing is working fine, good battery life, much faster on homescreen and on the appdrawer, maybe a little laggier on temple run...
Waiting for the official release...
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
jenda.69 said:
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
Click to expand...
Click to collapse
Yes, you are right.
jenda.69 said:
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
Click to expand...
Click to collapse
If harveydent used dd to dump the image, it will be padded with a bunch of zeros at the end. Both will work fine, although you cannot flash the untrimmed one using fastboot, you need to use recovery or dd.
Sent from my Galaxy Nexus using Tapatalk 2
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