Develop Bugs

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

Help backing up stock JB kernel

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

[TOOL] == Secret Menu Exploit ==

YOU MUST BE ROOTED AND HAVE A ROOTED KERNEL INSTALLED FOR THIS TO WORK! NON-AOSP ROMS ONLY!
T-Mobile rooted insecure kernel HERE
AT&T rooted insecure kernel HERE
INTRODUCTION:
I originally was building a rom that enabled serial port in an attempt to repair IMEI but decided to make a universal tool to enable the exploit instead.
You can use this new menu to access a lot of new internal settings and you can enable DIag mode (serial port) for reading and writing settings via PST.
Should work on all sgs3 phones.
DOWNLOAD:
GALAXY S III EXPLOIT TOOL
INSTRUCTIONS:
-Simply run the tool with you phone connected and follow the instructions, its a one click tool. Enjoy.
If you appreciate this and would like to make a donation you can do so here:
DONATION LINK
UPDATE:
Simple no-root solution finished for backup/restore of IMEI finished!
Thread: HERE

This video will show you the exploit being ran and a serial port being established.
Click here to watch video!
This is a big step as this enables reading the IMEI (among many other settings) via PST. Normally we can simply 'write' back whatever IMEI we want at this point; but that is not the case with this phone. When we find how to write back the IMEI, the IMEI issue will be resolved.
So,
Q: Is this a full IMEI solution?
A: No, this is me posting my work in progress along with a one click tool so that the community can help finish it up.

Thanx in advance I did bricked 2 already with no imei
Sent from my SGH-T999 using xda premium

kajam said:
Thanx in advance I did bricked 2 already with no imei
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Please submit your information HERE. It is an IMEI track/spreadsheet.

Just to clarify the special note in op, is there a difference between rooted and having a rooted kernel? I am rooted by means of Odin flashing root injected stock Rom.
Sent from my SGH-T999

Thanks for your contribution .

rakeshchn said:
Just to clarify the special note in op, is there a difference between rooted and having a rooted kernel? I am rooted by means of Odin flashing root injected stock Rom.
Sent from my SGH-T999
Click to expand...
Click to collapse
I believe so. Is this correct op?
Sent from my SGH-T999 using xda app-developers app

rakeshchn said:
Just to clarify the special note in op, is there a difference between rooted and having a rooted kernel? I am rooted by means of Odin flashing root injected stock Rom.
Sent from my SGH-T999
Click to expand...
Click to collapse
jjlean said:
I believe so. Is this correct op?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You can be rooted without an insecure kernel. Think he's saying you need an insecure kernel that will allow you to "adb remount" and get SU in adb shell.

Mi|enko said:
You can be rooted without an insecure kernel. Think he's saying you need an insecure kernel that will allow you to "adb remount" and get SU in adb shell.
Click to expand...
Click to collapse
Correct, the first command ran is (adb -d shell su -c "mount -o remount rw /system") It installs adw and then pushes a few things to system and a few thing to data, sets permissions and reboots phone. For the sake of a simple one click tool this will require the insecure kernel.

This looks cool can't wait to try it!!
Sent from my SGH-T999 using xda premium

thanx op, looks easy enough.

I ran the tool and when the phone comes back I try the Geek MOD but nothing happens. Have installed the kernel and am rooted. I'm stock GS3 other than that. Any ideas of what it doesn't work?

Anyone who's tried it yet, what exactly does this do? I'm curious....

uoY_redruM said:
Anyone who's tried it yet, what exactly does this do? I'm curious....
Click to expand...
Click to collapse
Agree. A little more info added to the OP would be appreciated.
Screenshots, maybe?

overground said:
Agree. A little more info added to the OP would be appreciated.
Screenshots, maybe?
Click to expand...
Click to collapse
haha, yeah. I'm a little reluctant to flash something in which I have NO idea what it does

Mi|enko said:
You can be rooted without an insecure kernel. Think he's saying you need an insecure kernel that will allow you to "adb remount" and get SU in adb shell.
Click to expand...
Click to collapse
you can download adbd insecure from chainfire also just sayn https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS5hZGJkIl0.
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
swehes said:
I ran the tool and when the phone comes back I try the Geek MOD but nothing happens. Have installed the kernel and am rooted. I'm stock GS3 other than that. Any ideas of what it doesn't work?
Click to expand...
Click to collapse
Same with me

Would this work on VZW? I have a "lost" IMEI, in my about device menu, my IMEI is 0. I am running on vzw right now, but it's roaming.

Cvballa3g0 said:
Would this work on VZW? I have a "lost" IMEI, in my about device menu, my IMEI is 0. I am running on vzw right now, but it's roaming.
Click to expand...
Click to collapse
Is your MEID 0's too or just the imei?

<:GeeK:> said:
Is your MEID 0's too or just the imei?
Click to expand...
Click to collapse
my meid is 11 numbers long for Dec, and Hex is 10 numbers + letters long.
I added myself to the spreadsheet.

uoY_redruM said:
Anyone who's tried it yet, what exactly does this do? I'm curious....
Click to expand...
Click to collapse
Ditto........
sent from my iPhone killer SGS3

How to flash a newer version of CWM safely

I initially rooted with http://downloadandroidrom.com/file/GalaxyS3ATT/rooting/GalaxyS3RootATT.zip that I got from here yesterday but feel like it has been al ittle glitcht.y http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
the newer version is recovery-clockwork-5.8.4.5-d2att sI don't want it to conflict with the old version of CWM or anything it leaves behind. hould I just do it through odin?

the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery

hapticxchaos said:
the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery
Click to expand...
Click to collapse
Should I use the CWM that I already installed or install the CWM that comes with rom manager (in the drop down menu it only offers galaxy s2...fyi I've always flashed with CWM without ROM manager)?

zetsui said:
I initially rooted with http://downloadandroidrom.com/file/GalaxyS3ATT/rooting/GalaxyS3RootATT.zip that I got from here yesterday but feel like it has been al ittle glitcht.y http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
the newer version is recovery-clockwork-5.8.4.5-d2att sI don't want it to conflict with the old version of CWM or anything it leaves behind. hould I just do it through odin?
Click to expand...
Click to collapse
I just updated CWM through Rom Manager. The latest version is 6.xxxx, and it now reads exSd.
Sent from my SGH-I747 using xda premium

geomax45 said:
I just updated CWM through Rom Manager. The latest version is 6.xxxx, and it now reads exSd.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
what do you mean "through" rom manager. Did you flash an image through it? Could you provide the link for that image?
OR
Rom Mangaer has an install CWM recovery option...but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?

zetsui said:
what do you mean "through" rom manager. Did you flash an image through it? Could you provide the link for that image?
OR
Rom Mangaer has an install CWM recovery option...but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?
Click to expand...
Click to collapse
The first option in RM is to flash a recovery. Upon pressing that you are given a list of phones. Scroll down to the Samsung GS3 and choose it. It will then flash the recovery within RM.
Sent from my SGH-I747 using xda premium

zetsui said:
.but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?
Click to expand...
Click to collapse
zetsui said:
Should I use the CWM that I already installed or install the CWM that comes with rom manager (in the drop down menu it only offers galaxy s2...fyi I've always flashed with CWM without ROM manager)?
Click to expand...
Click to collapse
Sent from my SGH-I747 using xda premium[/QUOTE]
AhAh! I knew i wasn't crazy... I have the same problem with Rom Manager , it won't show the S3 in the Menu. I tried uninstalling, wiping app data, reinstalling, Nothing, Nada, Niet ...... Let me know if you find a solution to this

I've had issues getting ROM manager to recognize me as a gs3 as well that's why I learned the terminal commands lol

hapticxchaos said:
I've had issues getting ROM manager to recognize me as a gs3 as well that's why I learned the terminal commands lol
Click to expand...
Click to collapse
Anyone find an easier way? And how would you do this through terminal commands? What are the commands

zetsui said:
Anyone find an easier way? And how would you do this through terminal commands? What are the commands
Click to expand...
Click to collapse
Terminal is as easy as the rest. I posted the commands up top, I see you didn't read the whole thread ;p ****, terminal is easier BC you can pick any recovery you want. Besides, it makes u feel like a true dev ;p

cool

I do not have any SG3 as an option to flash. How do i fix this?
geomax45 said:
The first option in RM is to flash a recovery. Upon pressing that you are given a list of phones. Scroll down to the Samsung GS3 and choose it. It will then flash the recovery within RM.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

hapticxchaos said:
the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery
Click to expand...
Click to collapse
Hey my md5 checksum has a mismatch, but I know the files are fine. is there a terminal command to recompile the md5 for a given image?
Also I noticed the new version of CWM has teh option to backup files as TAR, wouldn't that be better since Odin flashes Tar? If you couldn't get into CWM for some reason you can just flash for Odin?
Forgive me if I'm being newb here had my phone for three days after a motorola bravo

CM10.1 RC4 bootloader assert failed

My dad's GS3 has CM10.1 RC2 running on it, and he tried to update it to RC4 yesterday, but it gave him an error about the bootloader not matching. I ran
Code:
getprop ro.bootloader
to check what his was, and it's I747UCALEM. Now, I've found lots of different stuff on here about bootloaders, but what I want to know, is whether it's necessary to update the bootloader just to upgrade to RC4? And one more thing, what's the best method, using ODIN or something else?
Thanks!
BTW, it's running ClockworkMod. Not sure what version, but it's fairly new.

Yes. It is required.
Check out the first section of the link attached. Thanks to Task, mrhaley & jiangyi
http://forum.xda-developers.com/showpost.php?p=38880428&postcount=2

I_Cornholio said:
My dad's GS3 has CM10.1 RC2 running on it, and he tried to update it to RC4 yesterday, but it gave him an error about the bootloader not matching. I ran
Code:
getprop ro.bootloader
to check what his was, and it's I747UCALEM. Now, I've found lots of different stuff on here about bootloaders, but what I want to know, is whether it's necessary to update the bootloader just to upgrade to RC4? And one more thing, what's the best method, using ODIN or something else?
Thanks!
BTW, it's running ClockworkMod. Not sure what version, but it's fairly new.
Click to expand...
Click to collapse
The bootloader update is mandatory for upgrading to any new version of cm10 or AOKP from now on.
There are several pages dedicated to doing this. It can only be done through odin
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
xBeerdroiDx said:
Yes. It is required.
Check out the first section of the link attached. Thanks to Task, mrhaley & jiangyi
http://forum.xda-developers.com/showpost.php?p=38880428&postcount=2
Click to expand...
Click to collapse
Missed it by that much. You are quick... !
Sent from my SGH-T999 using xda app-developers app

KorGuy123 said:
Missed it by that much. You are quick...
Click to expand...
Click to collapse
Ha! Ninja-like, perhaps...