i am currently using Beanstalk 4.4 rom on my infuse 4G running CWM-based Recovery v6.0.4.5.
i would like to run CWM 11 as i see on the rom file for beanstalk but when i installed the rom i was still running 6.0.4.5 instead of CWM 11. i extracted the files from the .zip file but i couldnt find thw CWM recovery .img file to upgrade to CWM 11 only. i dont want to upgrade to a new os, Beanstalk 4.4 works great for me but i still want to upgrade just the CWM recovery
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
There must be a misunderstanding...
There is no ClockworkMod version 11, in fact, nothing higher than 6.0.x. You must be thinking of Cyanogenmod 11 (also known as CM11), which is a ROM that BeanStalk is based off of.
As for where recover sits in the ROM file, just search the zip for any .img file. Should be called recovery.img, but it may be considered something else entirely.
thanks
thanks I have been searching tirelessly to find a newer recovery due to misinterpretation. This has relieved a huge headache ive been having
Related
Well yesterday i have rooted my nexus s and i have the kernel Air_Kernel_Stable_r1_JBN_BlueColor on jelly Bean 4.1.2 (OTA).Today i tried to put a rom but after downloading a rom my nexus can not start.It goes only in fastboot MODE.If i try ti start it,it stands a black screen after loading the GOOGLE (symbol).Sorry for my english.Can anyone help me?
well... you need to try someother rom.. again. something not working right,
like yesterday I tried to put Baked_blackbean-5 on my crespo (9020a) and it didnt work
then I tried Slim 2.7 but I think I like CM10 nightly more.
Can you send me a rom to put on my nexus? i have not CWM..!
for ROM you asked download CM10 from this ... Download: cm-10-20121020-NIGHTLY-crespo.zip
md5sum: 9bbbfdf49af6624fdc3ee983ca58e1e0 http://get.cm/get/4mC
To put CM10 you need CMW Recovery. you cannot do it with stock recovery.
so ... put your phone into fastboot, and using the guide put ClockworkMod Recovery image
If you dont have CWM then what you have? Stock Recovery? or anyother?
How were you flashing that ROM yesterday?
Regards
OK so I have a Motorola xoom WiFi version with clockwork mod recovery and android 4.2.2 called my,wingray or something I got it from some other thread of xda but I have a couple of questions because I have tried to flash other ROMs and non of them will work so I need to know if I want to change things from what I have now what will work. So in the end I would like to have twrp, team eos with android 4.1.2 island I have tryed doing this over and over again and the best I have gotten is the eos logo to flash and stay like that and then I tryed CM and it did the same thing so I guess I need a link or something for this and do I normally have to flash 1 or 2 zip files to change the rom .
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
The files you got are .ZIP files.
It should be possible to flash these using the recovery. I have To check back for further instructions cause i'm not familiar with the s+ but cwm should be installed automatically when the kernel has be installed.
Sent from my GT-I9100 using xda app-developers app
Did it work?
Sent from my GT-I9100 using xda app-developers app
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
lil.masoud said:
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
You have to wipe data and cache, wiping dalvik cache is useless.
anoopgkris said:
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
Click to expand...
Click to collapse
It is not necessary to install recovery before every ROM installation. CWM 5.5.0.4 is a stable and safe recovery for our device.
According to the kernel i recommend you to use K^Kernal 3.4.x. It is more battery friendly with good performance.
The procedure is as explained in there
1. Boot in to recovery and
2. flash CWM 6.0.3.2 (if you want to, otherwise skip this) and reboot in to recovery.
3.Wipe data(not necessary when you are coming from a previous build of the same ROM, but recommended), wipe cache, and wipe dalvic cache
4. Flash ROM, Flash Gapps and flash kernel and reboot,
You are done.!
[SOLVED] How to install CyanogenMod 10.1 on my Samsung Galaxy S Plus
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
anoopgkris said:
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
Click to expand...
Click to collapse
You tried to flash .IMG recovery file via Odin. That won't work.! You need a .tar or .tar.md5 file to flash via odin.
Sent from my GT-I9001 using xda premium
Good battery life - CM 10.1
Hey Jabrief, thanks for the advise, I'll note it.
Until now, CM10.1 - 4.2.2 is running very smooth on my SGS+. Getting a very good battery life too. GPS is somewhat slow but maybe it's because odd the cloudy weather all the month.
Attaching a battery stats pic.
Got 32 hours and 40 mins on single charge.
About 16 mins of call, 45 mins of browsing in all.
thanks,
Anoop
After upgrading to BigPart i wanted to go back to the last "official" 4.1.2 based Roms to compare speed and stability with more up to date cm10.1 and 4.3. To try it out without reverting BigPart, I patched and recompiled Cm10.0 stable. I found cm10.0 stable and faster. Wanted to share, but I can't post in developers thread yet
perhaps someone could copy to the right thread http://forum.xda-developers.com/showthread.php?t=2506997
Link is to Boot image as cwm flashable zip. To use, flash full cm10.0 stable, then flash this boot image over the top before rebooting, so the new partitions are recognised. [ same technique as all other boot images in the main thread ]
http://d-h.st/wJc
Cool
Thanks a lot red321z
your CM10.0_wingray_BigPart_boot_image works very fine :highfive:
I couldn't get the BigPart boot.img to flash.... Formatted as BigPart (currently running CM11). I flashed CM10, it worked, then flashed the boot.img and got an error. Is it my recovery? I'm using TWRP 2.6 or 2.7 RunAndHide05 edition. I can't remember if 2.6 can flash 4.1 ROMs or not....
gapps problem
I just installed CM11 { cm-11-20140708-UNOFFICIAL-2037+0200-wingray } in my motorola xoom mz604. but i forgot to flash gapps-kk-20140606-signed. then i tried to flash this file later but i only get error. please help.
my recovery R.A.H._TWRPv2.6.3_BigPart_selinux
coro1937 said:
I just installed CM11 { cm-11-20140708-UNOFFICIAL-2037+0200-wingray } in my motorola xoom mz604. but i forgot to flash gapps-kk-20140606-signed. then i tried to flash this file later but i only get error. please help.
my recovery R.A.H._TWRPv2.6.3_BigPart_selinux
Click to expand...
Click to collapse
Please start your own thread. Your issue is completely unrelated to this thread.
red321z said:
After upgrading to BigPart i wanted to go back to the last "official" 4.1.2 based Roms to compare speed and stability with more up to date cm10.1 and 4.3. To try it out without reverting BigPart, I patched and recompiled Cm10.0 stable. I found cm10.0 stable and faster. Wanted to share, but I can't post in developers thread yet
perhaps someone could copy to the right thread http://forum.xda-developers.com/showthread.php?t=2506997
Link is to Boot image as cwm flashable zip. To use, flash full cm10.0 stable, then flash this boot image over the top before rebooting, so the new partitions are recognised. [ same technique as all other boot images in the main thread ]
http://d-h.st/wJc
Click to expand...
Click to collapse
Going to give this a try later. The 4.4.4 ROMs are great, but I want to try out CM10.0 without un-doing BigPart.
jparnell8839 said:
I couldn't get the BigPart boot.img to flash.... Formatted as BigPart (currently running CM11). I flashed CM10, it worked, then flashed the boot.img and got an error. Is it my recovery? I'm using TWRP 2.6 or 2.7 RunAndHide05 edition. I can't remember if 2.6 can flash 4.1 ROMs or not....
Click to expand...
Click to collapse
I'm using 2.7.1 TWRP and got the same error. Tried flashing CWM recovery but it also failed. I tried flashing through the recovery, maybe it would work if done through fastboot?
First, I have to apologize for being more or less a noob. I have been away from Android for a few years and just returned with a Galaxy S5. I used to flash ROMs all the time but it has been awhile and I have not had a Samsung before.
I was running stock Lollipop, then I rooted and installed phillZ CWM recovery. I then downloaded MOAR 6.2 and attempted to flash it from recovery, but keep getting errors, it says something about the signature and then it fails and reboots. I tried downloading it several times from both the main source and the mirror, and I did check the MD5. It is on the root of my SD card. So what am I doing wrong? Hopefully someone can help me get back into my Android ROM flashing!
Thank you in advance for your help.
I figured it out - I had flashed the CWM recovery but for some reason I still had the stock android recovery. It's all good now!