[RECOVERY][CWM] Completely stock ClockworkMod 5.5.0.4 (7/5/12) - AT&T Samsung Galaxy S II Skyrocket SGH-I727

This is a clockworkmod recovery built completely from source. It has the latest cwm updates and the latest ics kernel (eMMC erase bug fixed). This should also have the hanging backup bug fixed. I havent had time to make a billion backups to test this but the few i did without the .hidenandroidprogress file worked like a charm If you do get a hanging backup that is all koush's fault as i just used his latest sync to cwm.
To get adb working on this:
add these lines to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
-add them in the section that says [Google.NTx86] and the section that says [Google.NTamd64]. just make it look like the ones that are already there but with this code:
Code:
;
; Samsung Skyrocket
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0231&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
- then right click "my computer" and go to device manager
- you will see a driver with a yellow exclamation point...right click it and click "update driver software"
- click "browse my computer"....then click "let me pick from a list of device drivers on my computer"
- then click all devices
- click "have disk..."
- go to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
- click to allow installation of driver
- presto
DOWNLOADS:
recovery.img / recovery.tar.md5​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CHANGES:
Changes here.​
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Nice job man!

Good Job! :good:
Will test it in a bit

so i guess we have to use adb, or can we use odin, if not do u think u will make it flashable through odin
thks for the new cwm

vincom said:
so i guess we have to use adb, or can we use odin, if not do u think u will make it flashable through odin
thks for the new cwm
Click to expand...
Click to collapse
there is a recovery.tar.md5 that is already there in the OP....thats made for odin. just flash in the pda tab. in the downloads......

sk8erwitskil said:
there is a recovery.tar.md5 that is already there in the OP....thats made for odin. just flash in the pda tab. in the downloads......
Click to expand...
Click to collapse
great, didnt c that, thks

just making sure that no ones getting bricks from this, and for sure that the emmc thing is fixed

Is this recovery just for ppl who is on ICS roms? Gingerbread roms? Either?

Does it work a 100% now? Was the problem with unable to read external sd card and to format fixed?
Sent from my SAMSUNG-SGH-I727 using xda premium

kinvid said:
Is this recovery just for ppl who is on ICS roms? Gingerbread roms? Either?
Click to expand...
Click to collapse
both
r3dp0is0n2012 said:
Does it work a 100% now? Was the problem with unable to read external sd card and to format fixed?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
i never knew about a "unable to read external sdcard" error. the emmc format brick bug is fixed.

Excuse my noobness , and thanks for all your work
What is the difference between all those recoveries ? this one , you're other modified recovery and this one from CWM website http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.3-skyrocket.img ? apart from being with touch or not ?
Thanks

SK8, now that this base has the bugs ironed out are you planning to theme it like your other recovery?

mahanddeem said:
Excuse my noobness , and thanks for all your work
What is the difference between all those recoveries ? this one , you're other modified recovery and this one from CWM website http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.3-skyrocket.img ? apart from being with touch or not ?
Thanks
Click to expand...
Click to collapse
mostly just the UI.
bluntman420 said:
SK8, now that this base has the bugs ironed out are you planning to theme it like your other recovery?
Click to expand...
Click to collapse
ill just make a tutorial that shows how to change the font and background and colors and stuff instead of making a million different versions. i think that would be easier.

updated links to have all the latest changes to clockworkmod

Can you add "format /boot" option ?

mahanddeem said:
Can you add "format /boot" option ?
Click to expand...
Click to collapse
No problem. It's on the road map. I've just been busy focusing on a backup issue atm. I'll add that today tho
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Hi, first of all thanks for the recovery, it has been part of all my development. I might play with this over the weekend. My questions are:
1) Will it restore backups created from older version. I have parked on 5.5.0.4 BL14 (I think)
2) Does this include usb mount external sdcard?
TIA

mohan_kr said:
Hi, first of all thanks for the recovery, it has been part of all my development. I might play with this over the weekend. My questions are:
1) Will it restore backups created from older version. I have parked on 5.5.0.4 BL14 (I think)
2) Does this include usb mount external sdcard?
TIA
Click to expand...
Click to collapse
yes it should restore any backups made with any version of cwm.
this version does mount the external sdcard and not the internal. right now its only one or the other. the stock option is the mount the external. i can make a version that mounts the internal and post that if you would like. but until the commits from twrp get picked over its just one or the other.

Flashing in odin failed. File coming up as recovery.tar.tar in odin. someone help please.
---------- Post added at 07:07 PM ---------- Previous post was at 07:01 PM ----------
r3a1ist said:
Flashing in odin failed. File coming up as recovery.tar.tar in odin. someone help please.
Click to expand...
Click to collapse
Figured it out, why the heck was internet explorer changing my filename? Firefox was the answer. Sry.

Any news for T989 (Hercules)? Thanks!

Related

[ROM](Working Update.zip) -> Defy Update.zip Cookie Cutter Rom

Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App

[RECOVERY] 100% working ClockworkMod Recovery for Infuse 4G

This is 100% working. All partitions are mapped correctly and the SD cards mount properly.
Instructions (Method 1):
1) Place the zip file on your INTERNAL SD card and rename it "update.zip".
2) Boot into modded 3e recovery and choose "Reinstall Packages". You may have to do this twice the first time.
Instructions (Method 2):
1) Install ROM Manager from the Market and select "Flash ClockworkMod Recovery"
2) Select "Galaxy S i9000" (The partitions are identical. I checked.)
Disclaimer: This is not an official CWM recovery from Koush.
GREAT ! ! !
thx
Updated! Thanks !
Nice work dude.
You win +1 internet. Thank you.
How is this different from the one before? SDCard compaitibility?
ROM Manager
Is there any way to tell ROM Manager that you have CWM installed and use it's functionality? Or do we have to wait for the official?
LabiaSlayer said:
Is there any way to tell ROM Manager that you have CWM installed and use it's functionality? Or do we have to wait for the official?
Click to expand...
Click to collapse
Hint: I compared our partition tables to those of the original Galaxy S and they are identical, so just select the "Galaxy S" recovery in ROM Manager.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
slider2828 said:
How is this different from the one before? SDCard compaitibility?
Click to expand...
Click to collapse
Not only SD card compatibility, but also the data and dbdata partitions were mapped wrong in the Captivate recovery.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
If I installed CWM already before this version (selected Captivate on the menu) and I have Infused 1.1.1 installed, what do I need to do?
First Android phone, have enough paperweights laying around, don't need another ...
gtg465x said:
This is 100% working. All partitions are mapped correctly and the SD cards mount properly.
Instructions (Method 1):
1) Place the zip file on your INTERNAL SD card and rename it "update.zip".
2) Boot into modded 3e recovery and choose "Reinstall Packages". You may have to do this twice the first time.
Instructions (Method 2):
1) Install ROM Manager from the Market and select "Flash ClockworkMod Recovery"
2) Select "Galaxy S i9000" (The partitions are identical. I checked.)
Disclaimer: This is not an official CWM recovery from Koush.
Click to expand...
Click to collapse
Really? this zip you provided is just the Galaxy S i9000 flash? Bravo sir, for finding this out
Good call! i'll decommission my other CWM thread to alleviate confusion.
hoofadoo said:
Really? this zip you provided is just the Galaxy S i9000 flash? Bravo sir, for finding this out
Click to expand...
Click to collapse
Hey... don't reinvent the wheel right? I synced Koush's CWM repo, pulled the mount data from my Infuse, and then realized it... exact same as the Galaxy S.
gtg465x said:
Hint: I compared our partition tables to those of the original Galaxy S and they are identical, so just select the "Galaxy S" recovery in ROM Manager.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I chose "Galaxy S Captivate", it seems to work. Would "Galaxy S i9000" be a better choice?
Thanks for the help and the ROM!
LabiaSlayer said:
I chose "Galaxy S Captivate", it seems to work. Would "Galaxy S i9000" be a better choice?
Thanks for the help and the ROM!
Click to expand...
Click to collapse
Yes. Do not choose Captivate. The Captivate recovery is not fully compatible with the Infuse and you will have problems.
Just a quick question, What are the (MTD) versions of the flashes? I dont use them, because it comes up with a warning before flashing, but im just curious
Good stuff! W
Why are we on an "old" version of CWM? (ie: with Inspire I was on 3.** with the orange text). Just different versions due to hardware or ?
hoofadoo said:
Just a quick question, What are the (MTD) versions of the flashes? I dont use them, because it comes up with a warning before flashing, but im just curious
Click to expand...
Click to collapse
MTD is for CM7 users on SGS. They completely changed the formatting that Samsung put down, so they needed a recovery that was modded to work with the different partition table and filesystem.
To do the second "method" do you need to have the modded 3e recovery installed? I tried it without and and it didn't work. If you don't need it any ideas on how to get it to work??
VtHondaGuy08 said:
To do the second "method" do you need to have the modded 3e recovery installed? I tried it without and and it didn't work. If you don't need it any ideas on how to get it to work??
Click to expand...
Click to collapse
Yes, you always need modded 3e recovery to get to CWM.

[RECOVERY][MOD][DesireHD][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 HD. 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. I haven't been able to test it on the HTC Desire HD, since I don't own one.
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-ace.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-ace.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.
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.
Thanks dude,
if i use sense roms, this will still work fine right?
DubelBoom said:
if i use sense roms, this will still work fine right?
Click to expand...
Click to collapse
I don't know of any issues when flashing Sense ROMs with ClockworkMod recoveries, but then I'm also not using Sense ROMs.
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Thanks..Flash it at once!
Sent from my HTC Sensation Z710e using XDA App
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Correct, because of a bug in the ClockworkMod 4.0.0.0 source code. Keep an older recovery handy if you're testing this.
You can get around the bug. Each time you get the error, you can "adb shell umount /sdcard" from your computer. It's annoying, and hopefully we can find a solution for it soon.
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
+1 on this Had to return to 3.2.0.0
I edited 4.0.0.2, adding j_r0dd's mods and compiled it. Works well on Nexus One and Nexus S. No more sdcard mounting bug, it's been fixed. Can't test it on any other models myself. Updated first post of this thread.
how do you install this?
Doo Doo said:
how do you install this?
Click to expand...
Click to collapse
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
dirk089 said:
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
Click to expand...
Click to collapse
thanks for the info
does this work & are you using it ?
Doo Doo said:
thanks for the info
does this work & are you using it ?
Click to expand...
Click to collapse
since few minutes
and it works great.
also the sd-card mount !
dirk089 said:
since few minutes
and it works great.
also the sd-card mount !
Click to expand...
Click to collapse
Glad to hear it!
Sent from my Nexus S using Tapatalk
will it work on EXT4 roms?
Doo Doo said:
will it work on EXT4 roms?
Click to expand...
Click to collapse
That's a good question.
I just tried flashing it through terminal on my ext4 ROM and I just get a "scanning partitions" error.
when i try to flash it says image not found why when its on my sdcard
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
p2pjack said:
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
That's the work of Koush, I think. Glad it works, though.
Sent from my Nexus S using Tapatalk
Doo Doo said:
when i try to flash it says image not found why when its on my sdcard
Click to expand...
Click to collapse
Try renaming it to something short like recovery.img.
Sent from my Nexus S using Tapatalk

Unofficial Guide To Installing K-exec and CM9 & CM10

Unofficial K-EXEC & CM9\10 Guide
cm9 Required Files / Downloads
CM9 ROM: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/cm-9-20120719-UNOFFICIAL-d2vzw.zip
K-Exec Clockwork Mod: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
ICS Gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
cm10 Required Files / Downloads
CM10 Rom: http://goo.im/devs/BeansTown106/SGS3vzw/CM10/cm-10-20120721-UNOFFICIAL-d2vzw.zip
JB Gapps: http://goo.im/devs/BeansTown106/SGS3vzw/CM10/gapps-4.1.1-Kejar31-20120711.zip
K-Exec Clockwork Mod: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
Click to expand...
Click to collapse
Setup Instructions
Step 1.- Transfer the CM9 or Cm10 Rom, ICS or JB Gapps, and d2vzw_recovery.img to the root of you emmc
Step 2.- push the kexec cwm to sdcard and install
Code:
adb push d2vzw_recovery.img /sdcard/
adb shell
su
dd if=/sdcard/d2vzw_recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
reboot recovery
Step 3.- reboot into recovery
Step 4.- wipe data factory reset
Step 5.- Install cm9 or Cm10 zip
Step 6.- Install ICS or JB Gapps
Step 7.- Profit You Should Be Booting into CM9 or Cm10
Click to expand...
Click to collapse
Credits
I take no credit for this.. its all cvpcs's work and the cyanogenmod team.. **the jb zip was also made by dhacker it is 100% stable i think better than ics ** i was just impatient and merged the data fix before it went live , Build now has kexec intergrated so all u need to do is flash this new recovery and the cm9 zip it will auto Kexec thanks to cvpcs
Click to expand...
Click to collapse
DISCLAIMER
Neither me or team cyanogenmod take any responsibility if u brick your phone doing this, make a backup and read over instructions 2-3x
Click to expand...
Click to collapse
Edit* just wanted to apologize for my previous post! I thought you were posting a guide in the oe development thread...when in reality your posting cm9/10 roms that you helped develop. I would suggest editing the title of the thread to reflect that its rom development and not just a guide. I do appreciate your work!!!
droidstyle said:
Sweet write up....but derp, what on earth made you determine this is original development?
Click to expand...
Click to collapse
This is meant for the newest roms ie: aosp, cm, aokp source builds. no?
I'm giving this a shot. Thank you for the write...I don't think even I scan even screw this up!
I know this is early stage so not a complaint here, just having data drops on 3G. Besides those I am in heaven! lol
Sent from my Galaxy Nexus using Tapatalk 2
So there's data now?
EM2_Rob said:
So there's data now?
Click to expand...
Click to collapse
Yeah I am as well curious, though it seems that if there are drops it would suggest that data is available... I assume this is the build that cvpcs posted about having shaky 4g? (And 3g it seems)
Please pardon the noobish question but is there a way to push these files with terminal emulator? I haven't been able to get ADB to work. I have it and the SDK installed but when i try to push something it says ADB is not a recognized command
Dcox28 said:
Please pardon the noobish question but is there a way to push these files with terminal emulator? I haven't been able to get ADB to work. I have it and the SDK installed but when i try to push something it says ADB is not a recognized command
Click to expand...
Click to collapse
Sure..just skip the first two ADB commands (make sure you have the files on your EMMC/internal storage). Start with the "su" command to get root and follow the rest of the directions.
Hello data is not dropping for me at all. Actually better signal then stock touchwiz. I recommend flashing this and trying.
Sent from my SCH-I535 using Tapatalk 2
papi92 said:
Hello data is not dropping for me at all. Actually better signal then stock touchwiz. I recommend flashing this and trying.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Nice... do you live in a 4g area? My experience has been this device is shaky on 4g, so I might hold out.... but I'm definitely tempted!
Marcismo55 said:
Sure..just skip the first two ADB commands (make sure you have the files on your EMMC/internal storage). Start with the "su" command to get root and follow the rest of the directions.
Click to expand...
Click to collapse
Thank you very much. I am almost scared to ask the next question but when plugging my phone in to the pc i get the window that pops up and lets me go to Card or Phone. Obviously emmc/internal storage would mean for me to copy these files to Phone but I also am rooted and have CWM installed. If I did a nandroid right now before installing CM9, would I be able to restore it if needed after installing the Kexec touch CWM?
Thanks again for all help.
Yeah, I would also like to know what the LTE situation is with this. Not really pressed, though, as it's early in development. Great to see work like this happening.
Any chance for a CM10 build?
edit*
My 4g is solid. I haven't dropped yet.
Sent from my SCH-I535 using Tapatalk 2
papi92 said:
My 4g is solid. I haven't dropped yet.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Whoa, really?! I didn't know CM9 for the S3 now had data! That's awesome, I'm so tempted to try it out now...
---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------
Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
My data shut off after about a half hour. Now I can't get it past No Service and Roaming (No SMS/MMS, Voice, nothing); just a heads up for those who want a preemptive taste of CM9.
Dcox28 said:
Thank you very much. I am almost scared to ask the next question but when plugging my phone in to the pc i get the window that pops up and lets me go to Card or Phone. Obviously emmc/internal storage would mean for me to copy these files to Phone but I also am rooted and have CWM installed. If I did a nandroid right now before installing CM9, would I be able to restore it if needed after installing the Kexec touch CWM?
Thanks again for all help.
Click to expand...
Click to collapse
I still have access to my backups using the included touch recovery so restoring nandroids should be fine.
minmongoblin said:
Whoa, really?! I didn't know CM9 for the S3 now had data! That's awesome, I'm so tempted to try it out now...
---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------
Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
Click to expand...
Click to collapse
The EMMC is the internal storage. Just place the files on the root of your internal storage (not in any folders)
minmongoblin said:
[/COLOR]Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
Click to expand...
Click to collapse
https://www.google.com/search?sugex....,cf.osb&fp=3a50ef9c1ec22192&biw=1280&bih=623

[Q&A] [ROM][4.4.4]Android-L Themed Omega ROM [Beta-9]

Q&A for [ROM][4.4.4]Android-L Themed Omega ROM [Beta-9]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4]Android-L Themed Omega ROM [Beta-9]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I can't flash my trimmed ROM, it shows "Installation aborted."
wcdaniel said:
I can't flash my trimmed ROM, it shows "Installation aborted."
Click to expand...
Click to collapse
Which recovery are you using? You need cwm6+ or TWRP2.7+ without TLS
And if possible, give a log of the error
Unfortunately, Google Play Store has stopped.
I've tried a lot.
Clear data "Play Store" -> not fix.
I'm sorry maybe I should abandon rom.
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
wcdaniel said:
I can't flash my trimmed ROM, it shows "Installation aborted."
Click to expand...
Click to collapse
Recovery : CWM v6.4.0.6 by mukulsoni or TWRP v2.7.0.0 by @HardLight
Root
Any PlayStore said:
Unfortunately, Google Play Store has stopped.
I've tried a lot.
Clear data "Play Store" -> not fix.
I'm sorry maybe I should abandon rom.
Click to expand...
Click to collapse
That's possibly because you haven't trimmed it enough or you didn't use gapps light.
How much space do you have in /system partition?
rhar**** said:
That's possibly because you haven't trimmed it enough or you didn't use gapps light.
How much space do you have in /system partition?
Click to expand...
Click to collapse
13MB GappsLight.
trim MB?
Add a problem I can not mount ext4 for link2sd
Setting is suddenly stopped -> when accessing the "Performance"
Any PlayStore said:
13MB GappsLight.
trim MB?
Add a problem I can not mount ext4 for link2sd
Setting is suddenly stopped -> when accessing the "Performance"
Click to expand...
Click to collapse
Those are the signs of low system space
rhar**** said:
Those are the signs of low system space
Click to expand...
Click to collapse
Rom after downloading 111MB
After the trim 90.9 MB
Ok I will try again. Thanks.
Any PlayStore said:
Rom after downloading 111MB
After the trim 90.9 MB
Ok I will try again. Thanks.
Click to expand...
Click to collapse
You need at least 17mb on /system partition
rom that supports linux swap?
rhar**** said:
Which recovery are you using? You need cwm6+ or TWRP2.7+ without TLS
And if possible, give a log of the error
Click to expand...
Click to collapse
I am using CWM 6.4.0.6 from
http://forum.xda-developers.com/showthread.php?t=2564767
My recovery log is in the attachment.
wcdaniel said:
I am using CWM 6.4.0.6 from
http://forum.xda-developers.com/showthread.php?t=2564767
My recovery log is in the attachment.
Click to expand...
Click to collapse
That recovery should work. Try January build, if you are on December one.
Secondly, the log you sent is of cm11 by mukulsoni's and not omega ROM
rhar**** said:
That recovery should work. Try January build, if you are on December one.
Secondly, the log you sent is of cm11 by mukulsoni's and not omega ROM
Click to expand...
Click to collapse
Well, so where the right log file is?
wcdaniel said:
Well, so where the right log file is?
Click to expand...
Click to collapse
After the error, go to advance> copy log to sdcard.
And then send me the file clockworkmod>recovery.log
Or better use this TWRP 2.7.0.0 recovery by @HardLight from his thread
rhar**** said:
After the error, go to advance> copy log to sdcard.
And then send me the file clockworkmod>recovery.log
Or better use this TWRP 2.7.0.0 recovery by @HardLight from his thread
Click to expand...
Click to collapse
OK, I changed my recovery into TWRP2.7.0.0
But I still can't flash my ROM.
This is the new log file.
wcdaniel said:
OK, I changed my recovery into TWRP2.7.0.0
But I still can't flash my ROM.
This is the new log file.
Click to expand...
Click to collapse
Weird, there's nothing to show the error. Just 'Error flashing zip '
Maybe you trimmed it wrong.
What did you do to trim?
rhar**** said:
Weird, there's nothing to show the error. Just 'Error flashing zip '
Maybe you trimmed it wrong.
What did you do to trim?
Click to expand...
Click to collapse
I use 7zip(version 9.20, 64bit) to pack/unpack the ROM file.
Remove in:
\system\app: Email, Browser, LiveWallpapers, Exchange2, LiveWallpapersPicker, PicoTts, VideoEditor
\system\fonts: DroidSansFallback
That's all.
Is any possible I made some mistake when I repack the ROM?
I attached the screenshot of my 7zip pack setting.
wcdaniel said:
I use 7zip(version 9.20, 64bit) to pack/unpack the ROM file.
Remove in:
\system\app: Email, Browser, LiveWallpapers, Exchange2, LiveWallpapersPicker, PicoTts, VideoEditor
\system\fonts: DroidSansFallback
That's all.
Is any possible I made some mistake when I repack the ROM?
I attached the screenshot of my 7zip pack setting.
Click to expand...
Click to collapse
Compression level to normal or none. And encryption to none.
If still doesn't work, try WinZip or default windows zip manager
rhar**** said:
Compression level to normal or none. And encryption to none.
If still doesn't work, try WinZip or default windows zip manager
Click to expand...
Click to collapse
I have tried all of them but no one works. Log attached.
I can flash the original beta9 zip, but I really need google play store.
Can you upload a new beta9 zip with trim? I have totally no idea to make my own trimmed-zip work. :crying:
wcdaniel said:
I have tried all of them but no one works. Log attached.
I can flash the original beta9 zip, but I really need google play store.
Can you upload a new beta9 zip with trim? I have totally no idea to make my own trimmed-zip work. :crying:
Click to expand...
Click to collapse
I have created a script to trim the ROM. Hope it helps.
Just flash the the script after flashing the ROM.
I recommend the super_trim.zip

Categories

Resources