Database Info

[Q] My CWM 3.x.x.x backup doesn't work : SGS2

Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.

download cwm 2.5.x.x its better

[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?

OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm

Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!

You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.

Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App

Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.

I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.

Can't install ClockworkMod Recovery

Hi:
Following gtg465x's instructions in http://forum.xda-developers.com/showthread.php?t=1107881, I updated my stock recovery to modded 3e recovery. However, continuing with the update for ClockworkMod Receovery, I see a failure.
Here's what I see when I try to "apply update from sdcard":
-- Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It appears the 3e recovery I have isn't modded, and hence is still trying to verify the signature. I've tried downloading the (modded) 3e recovery a couple of times, just to make sure I'm getting the right one.
Interestingly, I don't have a file called recovery in /system/bin, but I do have one in / and one in /sbin. What gives?
I am on GINGERBREAD.UCKL2.
Any suggestions?

Use his video on youtube.
http://www.youtube.com/watch?v=PkMo8rBehHg
Edit: Sorry didn't see the end of your post. I always install cwm right away before I flash another rom.

Hi:
Tried exactly that. Unfortunately, didn't do the trick for me. I wonder if it's perhaps because of those extra recovery files in / and /sbin. Is it safe to delete them?

wiley_hacker said:
Hi:
Tried exactly that. Unfortunately, didn't do the trick for me. I wonder if it's perhaps because of those extra recovery files in / and /sbin. Is it safe to delete them?
Click to expand...
Click to collapse
Try my help page
edit:
wrong link previouly.
http://forum.xda-developers.com/showthread.php?t=1437548
just dl sgs kernel flasher if you're already on gb.
flash entropy's kernel to give you recovery

I do not know if it is safe to delete them. Only thing I would know to do is to go back to stock and install cwm to see if that works. Sorry that I'm not much help.

wiley_hacker said:
Hi:
Following gtg465x's instructions in http://forum.xda-developers.com/showthread.php?t=1107881, I updated my stock recovery to modded 3e recovery. However, continuing with the update for ClockworkMod Receovery, I see a failure.
Here's what I see when I try to "apply update from sdcard":
-- Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It appears the 3e recovery I have isn't modded, and hence is still trying to verify the signature. I've tried downloading the (modded) 3e recovery a couple of times, just to make sure I'm getting the right one.
Interestingly, I don't have a file called recovery in /system/bin, but I do have one in / and one in /sbin. What gives?
I am on GINGERBREAD.UCKL2.
Any suggestions?
Click to expand...
Click to collapse
can't be done on gb, you're trying a froyo proceesure.
kl2 is even worse cuz its hard to root. you need a custom kernel. how did you getroot anyway?

If he still had root, sgs flasher will work.
If not, heimdall one click defuse kernel in dl mode?
Would odin entropy also give you recovery to flash other ROM?

qkster said:
If he still had root, sgs flasher will work.
If not, heimdall one click defuse kernel in dl mode?
Would odin entropy also give you recovery to flash other ROM?
Click to expand...
Click to collapse
yes that all would work. but defuse is froyo so it is temporary so a gb kernel in a cwm package must be on the sdcard first to flash the phone back to a bootable state. kernel flasher will backup the kernel on the phone and make it cwm flashable, but if you have kernel flasher there is no need for defuse. defuse oneclick is a means to an end on gb. it's only foe the purpose of getting cwm to flash something else.

I had this problem just a few minutes ago things how I did it... First use root explorer down load the mod 3e place it in the system folder in the bin ( I didn't see it with astro but root I did) I renamed the recover in there as recoveryold then place the new recovery in there. Now make sure the permission the same as the original.. Now once that done just back out and close root manager... Goto to rom manager go into reboot into recovery. Then once it reboots cycle down to were it says install repackage (or something like that). Choose that option you may have to do it a few times.. I did but it worked... So then you should have cwm?.. Hope that helps
Sent from my Xoom using xda premium
Oh sorry didn't see your own gb.. I did this on froyo.

nthknd said:
I had this problem just a few minutes ago things how I did it... First use root explorer down load the mod 3e place it in the system folder in the bin ( I didn't see it with astro but root I did) I renamed the recover in there as recoveryold then place the new recovery in there. Now make sure the permission the same as the original.. Now once that done just back out and close root manager... Goto to rom manager go into reboot into recovery. Then once it reboots cycle down to were it says install repackage (or something like that). Choose that option you may have to do it a few times.. I did but it worked... So then you should have cwm?.. Hope that helps
Sent from my Xoom using xda premium
Oh sorry didn't see your own gb.. I did this on froyo.
Click to expand...
Click to collapse
Did you extract the recovery from the .zip or renamed the .zip recovery.zip? i extracted the recovery from the zip and placed it in the system/bin and made sure the permissions were correct. Then in cwm i booted into recovery. then phone froze when i tried to do an android back up. And yes i have froyo 2.2.1
***update-DONT RENAME ZIP AND STICK IN SYSTEM\BIN YOU WILL SOFT BRICK YOUR PHONE... I FOUND OUT THE HARD WAY LOL
Sent from my SAMSUNG-SGH-I997 using XDA App

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

[Q] Rooted with SOC without unmounting SD

I performed root of my stock Froyo Infuse using Superoneclick.
I did NOT remove or unmount the SD card prior to doing this (it was not mentioned in the instructions I followed on another site).
The phone was successfully rooted. I see no problems evident in behavior of the phone.
I am contemplating flashing a ROM at some time in the future (after more studying of the qkster's "how-to").
Will this previous error cause me any problems?
Is there anything I should do to fix it before I proceed?
Thanks in advance.

You appear to have done everything correctly so you are safe to continue. When it says not having the sdcard connected it refers to your internal sd card, which cannot be mounted to the pc when running SOC.
What ROM you plan on flashing sir? That way I may be able to make the process simpler for you.
Sent from my sweet & buttery Infuse

Thanks. AEON is my objective.

Very well, then you just only need to install cwm so you can flash the rom.
follow method 1 of this:
http://forum.xda-developers.com/showthread.php?p=14376440
Be sure to first install the 3e modded recovery using an root explorer such as solid explorer or es file explorer, both free.
Sent from my sweet & buttery Infuse

andros11 said:
Very well, then you just only need to install cwm so you can flash the rom.
follow method 1 of this:
http://forum.xda-developers.com/showthread.php?p=14376440
Be sure to first install the 3e modded recovery using an root explorer such as solid explorer or es file explorer, both free.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
Or...since he's rooted download aeon, then download one of entropys DD kernels (any one...its only for cwm and the kernel will be replaced by aeon)
Then go to the playstore and search "sgs kernel flasher"
Flash entropys kernel that you downloaded
After reboot (may boot loop don't worry) boot into recovery by holding both volume keys and power simutaniously until your phone reboots and you see Samsung logo...when you see the Samsung logo release the buttons
Wipe data/factory reset
Wipe cache
Wipe dalvic cache (under advanced)
Install zip from sdcard
Choose aeon
Choose yes
Wait
When done reboot
Sent from my HTC Holiday using Tapatalk 2

promissa reGeneo
mg2195 said:
Or...since he's rooted download aeon, then download one of entropys DD kernels (any one...its only for cwm and the kernel will be replaced by aeon)
Then go to the playstore and search "sgs kernel flasher"
Flash entropys kernel that you downloaded
After reboot (may boot loop don't worry) boot into recovery by holding both volume keys and power simutaniously until your phone reboots and you see Samsung logo...when you see the Samsung logo release the buttons
Wipe data/factory reset
Wipe cache
Wipe dalvic cache (under advanced)
Install zip from sdcard
Choose aeon
Choose yes
Wait
When done reboot
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
I want to follow roughly mg2195’s path suggested above.
I did download SGS.
As a side-trip, I used SGS to install some Froyo-compatible custom Kernels (Infusion 2.0, Infusion 1.8, Defused 1.4).
I now have Defused 1.4 Kernal along with my stock Froyo ROM
I used Root explorer to put the modified recovery file in.
I rebooted several times and used the three-finger press, and now I reach the RED screen:
ClockwordModRecovery v2.5.1.3. But I didn't do anything at that screen yet other than exit.
I have two questions before I proceed;
QUESTION 1 – Can I skip entropy’s DD kernal since I already have CWM red?
QUESTION 2 – I want to verify the modified recovery file that I used is correct:
I use the one suggested in this Infuse video:
http://www.youtube.com/watch?v=Y09p-J_g_Rg
the video links to file
http://llamalord.com/youtube/downloads/3e_recovery_no_sig_check.zip
When I googled that file name 3e_recovery_no_sig_check.zip to double-check, it lead me to this thread for CAPTIVATE:
http://forum.xda-developers.com/showthread.php?t=909213
GTG has a different thread “100% working ClockworkMod Recovery for Infuse 4G” which has a zip file with a different name (recovery-clockwork-2.5.1.2-infuse.zip)
http://forum.xda-developers.com/showthread.php?t=1107881
That 2.5.1.2 is not quite the same version number that I see on my red screen (my red screen says 2.5.1.3) . And on top of that, GTG made some comments on page 1 and 2 of that thread which I didn’t fully understand but lead me to believe Captivate is not a match (so he used i90000 instead). All of this makes me wonder if I have the right CWM red in there.
QUESTION 2 SUMMARY: Do you think my CWM red is good, or do I need to start all over again with GTG’s file?
Additional info found later;
I did find the same file 3e_recovery_no_sig_check.zip that I installed here on xda forums in an Infuse thread by h8rift: http://forum.xda-developers.com/showthread.php?t=1091465 . I downloaded it and verified the zip filename and size is identical to the one I used. That makes me feel a little better about question 2.

Although I've been studying these things, I'm still confused about the next step (trying to figure Q1 answer myself). Maybe if I can understand better, then I can answer myself. The following questions are an attempt to improve my understanding:
Q3 - Does getting the red CWM menu mean my CWM is successfully installed the way it needs to be ready to flash a rom ? (I’d think it does, but not sure).
Q4 - I see the GTG thread was same one linked by andros11. I am totally confused about that thread. Method 1, Step 1 you take a zip (which zip... your ROM or the one linked on the message?) and you rename it update.zip and put it on your sd card (where on your sd card... surely it makes a difference?). And this accomplishes something different than putting the modified file named recovery file into root/system/bin/recovery using root explorer?
Q5 – the only purpose of mg2195’s recommendation to download entropy’s kernal was to get the modified CWM, right?
Thanks for your patience.
========================
I think I will go ahead and flash Entropy's daily driver, should make all my questions irrelevant.
I'll post results, fingers crossed that it'll be a proclamation of victory.
In the meantime, I'm still curious about above, especially question #4.
==================
Edited again - actually I am going to sleep on it for a few days and make sure this is what I want to do.

electricpete1 said:
Although I've been studying these things, I'm still confused about the next step (trying to figure Q1 answer myself). Maybe if I can understand better, then I can answer myself. The following questions are an attempt to improve my understanding:
Q3 - Does getting the red CWM menu mean my CWM is successfully installed the way it needs to be ready to flash a rom ? (I’d think it does, but not sure).
Q4 - I see the GTG thread was same one linked by andros11. I am totally confused about that thread. Method 1, Step 1 you take a zip (which zip... your ROM or the one linked on the message?) and you rename it update.zip and put it on your sd card (where on your sd card... surely it makes a difference?). And this accomplishes something different than putting the modified file named recovery file into root/system/bin/recovery using root explorer?
Q5 – the only purpose of mg2195’s recommendation to download entropy’s kernal was to get the modified CWM, right?
Thanks for your patience.
========================
I think I will go ahead and flash Entropy's daily driver, should make all my questions irrelevant.
I'll post results, fingers crossed that it'll be a proclamation of victory.
In the meantime, I'm still curious about above, especially question #4.
==================
Edited again - actually I am going to sleep on it for a few days and make sure this is what I want to do.
Click to expand...
Click to collapse
Since you already managed to get Cwm red, you have no need of using the 3e modded recovery. That would only allow you to flash the zip linked in the OP of the gtg thread, which should be placed on the root of your /sdcard.
Entropy's dd mg2195 suggested would replace your kernel with a Gingerbread one that included cwm.
I would say to go ahead and flash Aeon since you already have CWM.
Sent from my sweet & buttery Infuse

[DEV] CM7 for Karbonn A9

I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Managed to compile it, finally, check posts below.
Sources: https://github.com/Siarc/a9

Shark- said:
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Sources: https://github.com/Siarc/a9
Click to expand...
Click to collapse
Dude, the only help i could give is test the ROM , let me know when you want it and i will be more than happy to help :fingers-crossed:

I've spent a lot of time, and it's simply not worth it, cannot even manage to get it to compile in the right directory. I can't believe there are so many people who have the knowledge but not one single reply.

CM7!
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I will test it bro..
thnks for compiling.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "

vijetaverma said:
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
Click to expand...
Click to collapse
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.

Great work Friend's
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
Bro please reply fast cant Waite now.I also want to install cm7

Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
just woke up..
I m adding that line.. will Post result in a while
---------- Post added at 10:28 AM ---------- Previous post was at 10:00 AM ----------
Still not able to install..
Error
"
same as previous one..
(status 7)
Installation aborted
"

Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app

Shark- said:
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
all same as before..nothing changed..

Can you post the complete log
Sent from my A9 using xda app-developers app

There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app

SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app

No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app

Well thanks for the encouragement
Sent from my A9 using xda app-developers app

mahfoozceecy said:
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
mahfoozceecy said:
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
So guys is anyone working on CM7 for A9 ?

MiUi Rom released..
http://forum.xda-developers.com/showthread.php?p=41289727