Koush's Recovery builder is now building CWM Recovery v6.0.0.0, the recovery is already included in the latest nightly of CM9. My question is how to get this to people that aren't using cm9, or make a permanent one that can be downloaded and flashed or odined separate from any roms. There is a build made for epicmtd at http://jenkins.cyanogenmod.com/job/recovery/1585/ you can download the recovery.img file from there, but I was hoping to make a flashable zip or something from it. The builder is pretty sweet, can also build a touch version. I understand I already have it on my phone because I used the latest cm9 nightly, but does that actually replace the older CWM, or just add another one that resides inside the kernel... if I'm not mistaken in the past I ended up with 2 versions of CWM on my phone, one that was odined in and permanent, and another that was actually a part of cm9. I also was going to build the touch version to check out but I didn't and will hold off until I hear back from people on this thread.
the CM team had a temp boot CWM Touch available some months back. They said there was an issue with flashing it permanent, and hadn't heard or seen any update for it since then (think this was march or april)
I'd love to see a fully working CWM Touch for our Epics.
Related
CWM Rogue Recovery doesn't seem to be sticking on my E4GT. Flashed CM9 Alpha 3 from stock rooted rom. When Alpha 4 was released, I tried to boot into CWM Recovery and ended up with stock recovery. Ended up having to odin back to stock and start over to get Alpha 4 running. Same problem now that Alpha 5 is out there, tried to boot into CWM Rogue Recovery and get stock recovery.
Doing a search shows that this seems to occur on other phones. They've resolved it by deleting a boot recovery file with Root Explorer. I was just hoping to confirm with someone that this method will work on the E4GT and the name and location of the file that needs to be deleted.
I'm assuming I'll have to odin back to stock and start the process over again and delete that file once I load up CWM Rogue Recovery again?
Thanks for the help.
CM9 comes with stock recovery. Look up EL26 kernel and learn to use it. Its your best friend for flashing on this phone. Also read up a little more on CM9 as it explains this.
This method will not work. With our phone, recovery has to be packed into the kernel, its not separate from other partitions like it is on other phones. This is why whenever you flash a new rom, your current recovery is replaced by the new roms packed in recovery. The reason its stock Android recovery is because of the bricking issue we've been having in ICS custom recovery so devs aren't including it into the kernel<rom.
So when you need CWM, flash the directboot CWM under the tools page in the epic4g touch CM blog spot website. You Odin that and it takes you straight to a sage recovery where you can flash the alpha 5 update. Understand?
Sent from my SPH-D710 using Tapatalk
Thank you both for pointing me in the right direction. I realized that I would have to go back to the EL26 to flash new roms. I didn't realize that I would have to do that to flash over an existing rom with an update. Thanks for setting me straight.
hmmm....interesting. The CM9 instruction page does not mention that you need to Odin the DirectBoot CWM when upgrading. I can see why a lot of people are skipping that step.
Thanks for the heads up, I am going to upgrade to alpha 5 after work. I'll make sure to Odin the DirectBoot CWM kernel first.
mjs2011 said:
I can see why a lot of people are skipping that step.
Click to expand...
Click to collapse
It is a new kernel modification that did not exist a couple weeks ago. The EL26 CWM kernel itself has been around since the end of last year. Being completely optional to use the new modded one you probably wont find it in instructions. I for example will never use it but others will find it easier because they do not understand why the phone goes into bootloops.
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.
Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.
Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!
Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.
I was wondering, if I have CM 9 installed can I download the nightlies (If I wanted to try them) and install them on my Samsung EG4 touch?
i want to leave this planet.
if you have installed cm9 correctly you should just be able to flash the nightly over your stock cm9, that is if you have a NOT stock recovery. I know from experience that it will work on the safe CWM that agat and chris41g have put together.
http://e4gtcm.blogspot.com/p/cm9-install-guide.html
go to the bottom where it says upgrades. and read that. just to be safe.
hope this helps
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^
I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.
Metal_Koola said:
I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.
Click to expand...
Click to collapse
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?
amzi said:
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?
Click to expand...
Click to collapse
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.
Metal_Koola said:
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.
Click to expand...
Click to collapse
While I cannot answer your question myself, I can help elaborate with the hope you get a better response. The question posed here pertains to the recovery image for the ROM that holds the fresh boot image of all the system files ('factory reset')
I haven't spent any time researching how Android recoveries function - but when you update CM through the OTA updater, I believe it only patches modules in the system rather than updating the entire boot image itself - if they updated the whole package daily that would be terribly taxing on the person packaging and distributing the ROM, not to mention ISP bandwidth (I have never tried CM myself, so I couldn't tell you for certain if this is the way it works or not).
In any case, the OP is asking about the ROM image in recovery not the recovery itself (i.e. - TWRP, CWM, etc.) . Hopefully someone with a better understanding of Android can chime in for you.
Sent from my SGH-I747
I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.
marinierb said:
I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.
Click to expand...
Click to collapse
Alright, it might have been special for my Captivate then. Thanks for letting me know.