Database Info

[RECOVERY][MOD][Desire][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.

it works... thank you

suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.

bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?

sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.

zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days

sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.

well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?

sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk

yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!

sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.

Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?

Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.

Updated OP to version 4.0.0.0.

Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.

teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.

I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.

Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.

Md5 mismatch

Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium

hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Couple of things...
Your backup might be corrupt if the md5 doesn't match.
or you might want to try and make sure you have the latest version of CWM installed on your phone. I read in one of the other threads that someone had an md5 mismatch problem that was solved with a newer version of CWM. I hope this helps.

hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I had this happen to me once. Turned out the nand backup was bad....used the previous one I had made and was back in action. Had a few moments to sweat it out though. Just make sure to backup regularly and archives them.
Sent from my SAMSUNG-SGH-I727 using xda premium

same problem
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?

bshebib said:
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
Click to expand...
Click to collapse
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.

Presbycusis said:
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Click to expand...
Click to collapse
This is exactly how I do it. I've never needed it but have always had it for emergency. Now that ICS is out I've been going back and forth from the sandwich to gingerbread because the bugs are well.......bugging me. I odin'd the leak then I backed it up after I installed cwm so I could always go back to that after testing out these other roms, cwm flashes, and even the backups of ICS, then I root. I basically have started from scratch twice and both times I went back to my backup I got the mismatch ( 2 different backups of the leak). I know its me (possibly cwm) because the cwm ics backup that's out there restores fine.
Sent from my SAMSUNG-SGH-I727 using XDA

Are you extracting on your PC? There seems to be some problems with unzips on the phone causing a mismatch
I've been using 7-zip for mine, and it works great. Extract files on the desktop, place on the external SD using USB

Got this from another forum
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse

Toggle signature works for me alot
Sent from my SAMSUNG-SGH-I727 using XDA

Not totally sure that I'm correct but I had made two backups on one version of cwm and then upgraded my cwm to the touch version and the two backups from the previous version wouldn't restore because of md5 mismatch. Those same two backups had worked several times perfectly on the other version of cwm as well. So I just assumed that maybe the version change had something to do with it.
Sent from a payphone at the quick-e-mart down the street from you

hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium

Just flashed cwm touch from another recovery before trying to flash new rom zip and md5 mismatch accured...after darkwipe..dang..that was close call....think your correct with the change theory...
Sent from my SAMSUNG-SGH-I727 using XDA

Yes
yes that wass the problem. Tnk you NO spaces on backup folder name.
Tnk s
mindmajick said:
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse

hisham027 said:
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Worked perfect, thanks

adb Problem
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.

funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Isn't that for the international gs2?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Try using terminal emulator from your device

ADB Shell
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?

funatkill said:
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
Click to expand...
Click to collapse
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed

hisham027 said:
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
Click to expand...
Click to collapse
I fixed my md5 with the adb shell.. but I had to do this in one command . After reading this tut, I think there only has to be the MD5 of *.img, not of the .tar. Am I right?
Maybe its possible to script a zip-file for CWM which recalculates the MD5 of existing Backups?
The bash commands are simple. You only have to do this in a loop for all folders in /sdcard/clockworkmod/backup.

[GUIDE]How to load CM9 on GSIII

**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.

Very informative. Would read again.
Sent from my Transformer Prime TF201

dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html

I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.

Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium

dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.

is the data not working due to the ril??

suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out

I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.

Will these same instructions work for the CM10 build that is in the server list?

17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium

neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.

17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium

i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?

seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.

Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.

17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium

DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.

[ROM][SGH-S730M] Stock deodexed + rooted + overclocked

This is a DEV thread, this is not yet working
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked

problem
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

problem
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
[/URL]
Click to expand...
Click to collapse
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

E signature verification keeps failing

bil4554lel said:
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
Click to expand...
Click to collapse
Not sure, haven't tried to install this yet, BUT when in recovery, given you have a custom recovery installed, you shouldn't be trying to "apply update from zip" you should be selecting "install from zip". If you are using a stock recovery, you won't be able to flash a ROM. You need to flash a custom recovery such as twrp or cwm using Odin from a PC.
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
I have this old gem of a phone and have been looking forever for a custom ROM. Don't know where you pulled the stock from as I've been trying to dump it off the phone unsuccessfully to mod with Android kitchen. I'll flash this and update with my results

I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8

atmu5fear said:
I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8
Click to expand...
Click to collapse
Hi, i get too the same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?

Bibounet said:
Hi, i get it too, and same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?
Click to expand...
Click to collapse
I'm definitely interested in developing a custom ROM for this phone. I bought this phone nearly two years ago, and although I have since upgraded, I seem to always have use it as a back up when my t989 has issues. I know there is a ton of demand for a custom ROM for this phone. I was reading a bunch about META-INF folders and Android kitchen for developing a ROM without having a current base to work with. I'll look into it a bunch more throughout the week, this weekend etc. See if I can get a flashable zip after deodexing and overclocking using the thread the OP of this one used. I read on another forum, after googling "cwm status 255" that this has to do with the updated-binary file in the META-INF folder. The suggestion that worked for the op of that thread was to take the updated-binary file from another flashable zip (for the same phone) and use it to replace the updated-binary file in the zip giving the 255 error. So I took the file from the deodexing zip for this phone and replaced it, not expecting it work, but just to see. Cwm no longer gives the 255 code, but still aborts the installation, with no code given. So it seems this very well could be a start.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem

atmu5fear said:
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
Click to expand...
Click to collapse
That may very well be it, I'm gonna change it and reupload
Check back in a bit. Appreciate the help

I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role

I just threw together a flashable zip of this rom quickly on android kitchen. I used the META-INF folder from the thread I previously linked to. It's been deodexed and rooted, but I didn't bother with the overclock. Once we can get a flashable zip that works, i figure we'll go from there. I'm going to flash it to the phone now, and see if it will complete and boot.
I'm getting a status 0 error code. I'm going to rebuild without converting to edify. Will update

Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.

Bibounet said:
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.
Click to expand...
Click to collapse
The overclock is built into the kernel, clocks it from 800mhz to 1000mhz, any one who wants to run it without the higher clock, can just use any CPU control app and set the max to 800.
Without modding the kernel you actually can't overclock past 800mhz using any CPU control app.
---------- Post added at 03:28 AM ---------- Previous post was at 03:20 AM ----------
Restl3ss said:
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
Click to expand...
Click to collapse
The Tab 3 runs on intel and the discover runs on ARM.
From everything I can find this is definitely the problem. Although just replacing the binary itself, and rebuilding hasn't seemed to accomplish anything other than no longer giving the error code. Just aborts. I've read your updater-script and none of the ui messages show up or anything from within that script during install.

@Restl3ss I swapped out the binary from another flashable zip for the same phone, from within the kitchen using your flashable zip. Kept your updater script and other than that the only other change was I zipaligned. I rebuilt it, flashed it. The install doesn't abort, and completed. But none of your ui code from script appears during install, and nothing actually installed to the phone, it just boots straight into recovery. Since I have no idea how to decipher what I'm reading in the binary using notepad++, I'll leave it to your expertise to sort out the rest. I'm only just getting into this developing bit and so far have reached my limit of what I can help you with, as far as getting a base to flash and install successfully. I tried to get a report using adb logcat after it kept booting into recovery but the log remained empty.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."

Joel-Tang said:
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."
Click to expand...
Click to collapse
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz

Restl3ss said:
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz
Click to expand...
Click to collapse
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the more information you can get me the better, thanks a ton for the help

How to Install Gapps ? (/system and /data on sd-ext)

My mmc got fried while formatting my /system and /data partition using twrp, so I moved my /system and /data partition to sd-ext partitions which I made using 4EXT recovery using delta-roh Turbo-DATA mod.
Here is what my partitions look like
1st partition -> SD-card -> vfat
2nd partition -> sd-ext -> /system -> ext4
3rd partition -> sd-ext2 -> /data -> ext4
Currently I have cm-11 by Ivanich on my phone but cant install Gapps. I ve been editing the update-binary in the Gapps zip but it always returns me the error that
"This Gapps pkg is for android version 4.4.x ...... Your rom : 2.3.7"
But I have a kitkat installed. I am guessing that its not reading the build.prop correctly. So how do I install Gapps ?
Any help is appreciated ...
More info about my phone
S-off
Bootloader unlocked
Rooted
Recovery : 4EXT
Rom : CM-11 by Ivanich

A recovery with modified ramdisk might be necessary. Maybe @hinxnz can help you with that.

Ok. Can i use the android kitchen to unpack recovery.img and modify it ?
If yes what modifications do I need to make it work ?

Wahaj.47 said:
Ok. Can i use the android kitchen to unpack recovery.img and modify it ?
If yes what modifications do I need to make it work ?
Click to expand...
Click to collapse
Yes you can use AIK for recovery image, you'll need to modify fstab like you did with the boot image. I have never unpacked 4ext though and it's a bit outdated now but I've always used ivanich's twrp builds when modifying recovery.
Otherwise you could just modify the updater script in the gapps package to not mount data etc but this will have to be done every time.
Edit: I just read your first post and I'm not sure how you even flashed ROM if your system partition is bad, did you modify the ROMs updater script to flash it to your new system on sd-ext or something? If so gapps could be reading your old system, then I'm thinking is it actually bad or just your data partition is...

hinxnz said:
Yes you can use AIK for recovery image, you'll need to modify fstab like you did with the boot image. I have never unpacked 4ext though and it's a bit outdated now but I've always used ivanich's twrp builds when modifying recovery.
Otherwise you could just modify the updater script in the gapps package to not mount data etc but this will have to be done every time.
Edit: I just read your first post and I'm not sure how you even flashed ROM if your system partition is bad, did you modify the ROMs updater script to flash it to your new system on sd-ext or something? If so gapps could be reading your old system, then I'm thinking is it actually bad or just your data partition is...
Click to expand...
Click to collapse
Yep I modified the roms updater script to mount sd-ext as /system and sd-ext2 as /data.
I cant modify the gapps updater script because its just a dummy file and all the code is in update binary and it needs some experienced programming .
I ll try modifying the recovery's fstab and post the results.
"/etc/recovery.fstab" is that the file I need to modify ?
Edit:
I also tried adding the gapps to the rom zip itself and flashed it but that made the rom useless because it kept rebooting.

Wahaj.47 said:
Yep I modified the roms updater script to mount sd-ext as /system and sd-ext2 as /data.
I cant modify the gapps updater script because its just a dummy file and all the code is in update binary and it needs some experienced programming .
I ll try modifying the recovery's fstab and post the results.
"/etc/recovery.fstab" is that the file I need to modify ?
Edit:
I also tried adding the gapps to the rom zip itself and flashed it but that made the rom useless because it kept rebooting.
Click to expand...
Click to collapse
Just open update binary with a program like note++ if using windows.
I haven't modified recovery for a little while and haven't got the files in front of me but there are a couple to modify to get everything working, just have a peek round in the folders.

hinxnz said:
Just open update binary with a program like note++ if using windows.
I haven't modified recovery for a little while and haven't got the files in front of me but there are a couple to modify to get everything working, just have a peek round in the folders.
Click to expand...
Click to collapse
I have been messing around with the update binary but honestly man I ve got know idea, I am not even close to fixing the damn problem.
I haven't tried modifying the recovery fstab yet. I am gonna do it and see what happens.

Wahaj.47 said:
I have been messing around with the update binary but honestly man I ve got know idea, I am not even close to fixing the damn problem.
I haven't tried modifying the recovery fstab yet. I am gonna do it and see what happens.
Click to expand...
Click to collapse
If you want, upload your recovery image and I'll modify it for you.

hinxnz said:
If you want, upload your recovery image and I'll modify it for you.
Click to expand...
Click to collapse
First I tried using the google installer to install gapps but playstore kept crashing so I ruled that out.
Then I modified the recovery.img and flashed pa-gapps-4.4 and it worked . The playstore was still crashing but updating google play service has fixed it, but I am not sure about this, gonna keep testing for a while. Atleast now I have gapps
Thank you very much

I was getting random reboots on cm-11 so I ve moved on to cm-12.1. Can this be a battery fault ?

Wahaj.47 said:
I was getting random reboots on cm-11 so I ve moved on to cm-12.1. Can this be a battery fault ?
Click to expand...
Click to collapse
If you mean shutdowns then yes, otherwise if rebooting then it's something else.
If a full reboot happens, it will show in /proc/last_kmsg

hinxnz said:
If you mean shutdowns then yes, otherwise if rebooting then it's something else.
If a full reboot happens, it will show in /proc/last_kmsg
Click to expand...
Click to collapse
I am not experiencing any reboots on cm-12.1, but its lagging a bit. And phone turns off when taking picture with flash on.