Related
EDIT [4-26-11]: Sorry guys for the delay on updating this thread. I currently have no free time, so defer to other threads for up-to-date information. I will probably be back in a couple weeks.
EDIT [4-8-11]: jt1134 has put a lot of work into fixing the mounting/filesystem/permissions issues over the last couple days. I will update this post as soon as he makes his latest compile available.
Original Post:
Because of the confusion over the different versions of ClockworkMod Recovery, I will try to address the major questions in this thread.
This all started out when some people started asking questions about why themed nandroid backups always had problems when they were restored (very informative thread detailing the process). After figuring out that something was broken in CWM, I decided to try to find it. Thankfully, it was an easy fix that me and jt discovered whilst chatting in the IRC. While I was poking around, I fixed a few other small problems too. Since then, jt has worked on making sure the mounting/permissions work right. I think we finally have a winner.
[SIZE=+1]Changelog[/SIZE]
Bug: The old CWM did not have root shell access because of a typo in the old initramfs, so this caused lots of issues when ROMs and themes did not set the correct permissions in their scripts. This is where most of the "Force Close" problems and boot loops came from when flashing roms and also when restoring Nandroids backups. Fix: corrected the init script typo from "ro.secure=01" to "ro.secure=0"
Bug: "Voodoo lagfix is actually: disabled" even when it is enabled. Fix: working (probably as a result of the root fix)
Bug: "Fix Permissions" script is broken. Fix: updated to new version and then modified to auto-mount the correct partitions and use correct files
Bug: Mounting menu typo "umount /dbdata". Fix: corrected to "unmount /dbdata"
Bug: Battery Stats wiping returns immediately to menu. Fix: added a print out to confirm to the user that battery stats wipe was ran
Bug: "Format Boot" option does not work. Fix: not compatible with the Fascinate, removed from menu
Bug: "Enable/Disable Puzzle LockScreen" does not work. Fix: no longer compatible, removed from menu
Bug: Miscellaneous quirks and issues. Fix: mounting and permissions code improved throughout, and making it more robust in handling ext4 and RFS configurations.
[SIZE=+1]Frequently Asked Questions[/SIZE]
Q: After I enter CWM, it says I am at version 2.5.1.x. Does that mean I'm on the correct version?
Unfortunately, the last several updates have been minor bugfixes, and the version number has stayed at 2.5.1.x. Hopefully this will be remedied soon. An easy way to check is to go to "Advanced" menu. If you don't see "Enable Puzzle LockScreen", then you are on the newest version (this menu option was removed because it has not been functional for a long time).Q: Does battery stats wipe work yet?
It was working on the on the old CWM, it just didn't give you a confirmation after wiping. If for some reason it wasn't working on the old CWM recovery (because of the ro.secure bug that was fixed), then I can definitely confirm that it is working now.
In the newest fix, I added a notification before returning to the menu that tells the user that the battery stats had been wiped.Q: Does Fix Permissions work yet?
If you select "Fix Permissions" you should see it doing a lot of work (should take 1-2 minutes). If it returns to the menu immediately, it means one of two things:
You just wiped /data or /dbdata, in which case, there is nothing to fix permissions for (completely normal)
Your /data or /dbdata partition is unable to mount, which means you may have had a bad voodoo conversion, or something that will probably require Odining back to stock to repair (not normal)
Q: I have the new CWM and the feature you said was fixed doesn't work!
Maybe, but I'm guessing you have an old copy, or you have flashed a file that has overwritten your recovery partition to an old version. That's why I have included the SuperClean ROM's with the updated CWM, because most people don't know about this. If you prefer to not re-download the whole SuperClean file, you can take the zImage2 file from the CWM ZIP file and drag and drop it into the /kernel_update/ directory in your current SuperClean file.
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
However, if you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
Download to PC
CWM-Recovery Odin Package
MD5 Checksum:
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ROM of your choice
MD5 Checksum:
Now that's done, on to the fun part....
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Unplug USB Cable, THEN reinsert your battery
Hold both the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache/Dalvik Cache only. Flash the ROM of your choice
Reboot. Since you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot; enter CWM; wipe Cache/Dalvik Cache only; enter CWM; flash theme
If you need to install a kernel, reboot; enter CWM; flash kernel
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
I haven't gone into the specifics of how to do all the above, because there are several tutorials with pictures and well-written guides already in existence.
[SIZE=+1]A couple of things about ClockworkMod Recovery that a lot of people don't know[/SIZE]
The CWM package in this post is the ONLY CWM file you ever need, for any Samsung Fascinate ROM. Even Eclair ROMs. Even Non-Voodoo Roms. Doesn't matter. Delete all your old copies.
When you flash a CWM Recovery, you are writing an entire kernel into the recovery partition of your phone (bml8). This does not affect your current kernel because it is stored on your kernel partition (bml7).
When you download a ROM, it is up to the ROM author to decide if they want to include a kernel and/or CWM. For example, SuperClean bundles the ROM/Kernel/CWM all into one flash file. When you flash SuperClean, it will overwrite your kernel partition (bml7), your recovery partition (bml8), and your system partition (stl9).
[SIZE=+1]A few other questions that might get asked[/SIZE]
Q: What is that MD5 gibberish under the download links?
A: MD5 (and other checksums/hashes) can be used to verify the integrity of a downloaded file. Basically, you download the file, then use an MD5 tool to calculate the checksum. You then compare the file's checksum to the checksum I have posted under the link. If it matches, then you know that your download is not corrupt.
The whole process is much easier/quicker then it sounds, even if you've never done it before. Also, there are many free MD5 calculators (I use HashCheck).Q: Is this CWM 3? Why isn't my menu orange?
While this is the newest fully compatible CWM for the Fascinate, it has NOT had any of the CWM 3.0 code base ported into it. As of CWM 3.0, Koush ripped Amend scripting support for flashing. Most of the rest of the world has already moved to Edify scripts, but in Samsung Fascinate land, we still cling to Amend scripts in a lot of our ROM/patch flash files because of some of the issues that Edify has had with the way Samsung laid out the partitions and devices. This is why we have stuck with CWM 2.5 for so long, because so many ROMs, themes, and patches are still using Amend scripts.
Really though, its time to merge the CWM 3.0 base, port the voodoo options, cut ties with amend, and get the Samsung Fascinate's funky mounting/partitions/layout fully compatible with CWM. Someone just has to do the work, because Koush doesn't seem to be that interested in it any more.
There are a lot of improvements in the back end of CWM 3.0 that make it more reliable. Also, if someone were to be slightly ambitious, there are quite a lot of previously unseen (on the Fascinate) features that could be ported from other people's CWM mods. One easy one would be backup and restore of the kernel, which would allow for a more complete Nandroid. It's actually already half-way implemented in the code, so it wouldn't take much more work to get it done, even on the current version.
Then there is the EFS partition... which is a subject avoided by most people but is an important aspect of the phone that no one currently is backing up. There has been a lot of work done for the other SGS variants, but no one has really spoken up about it in the Fascinate world.Q: Will this overwrite my kernel/custom kernel files on my system partition/knock up my daughter?
The CWM ZIP package has been cleaned of the system files, and the ODIN package has been correctly configured to flash to the recovery partition only. SuperClean will behave like normal, which involves flashing your kernel/CWM/system/daughter.
Until Adrynalyne and jt1134 adopt these files (or make their own), then this applies to files that are downloaded from the links provided in THIS THREAD ONLY.
Q: Why did you start a new thread for this?
Because in the main threads, I answer the same questions every 20 posts. This is more visible. If this information is merged into Adrynalyne's SuperClean thread and JT1134's CWM thread, I will ask for a mod to close this thread.
Good job
I‘m done with the 2.3 ROM!
How foooooolish I am
So..... I'm currently running sc 2.9.2 with voodoo ..... Do I need to just flash the sc + voodoo update in cwm? Wipe data/cache/dalvik?
Sent from my SCH-I500 using XDA App
Nice write up. This should help a lot of people have a better understanding (assuming they actually read it).
chefthomas99 said:
So..... I'm currently running sc 2.9.2 with voodoo ..... Do I need to just flash the sc + voodoo update in cwm? Wipe data/cache/dalvik?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
well if you want to do it the way he spells out in the op, you need to do alot more. flashback to eb01 is the first step. just follow the steps.
thanks for this. a new thread was very needed aswell.
Is the recovery-all zip dated 3-30 in this post any different from the modified one for custom kernels that you posted in jt's thread a couple days ago?
garywojdan81 said:
Is the recovery-all zip dated 3-30 in this post any different from the modified one for custom kernels that you posted in jt's thread a couple days ago?
Click to expand...
Click to collapse
Let's just go ahead and assume that there are no files outside of this thread that are identical to the files in this thread.
Even though that may not be exactly true, most people do not know what version of the file they have, since they all have the same file names. This is another reason why I provided the MD5 checksums, since that is a unique identifying mark.
If you ran the MD5 checksums on all the files, you maaay just find that the ODIN file in this thread is identical to the ODIN file in JT's thread. Since he first posted a very naughty ODIN that overwrote your kernel instead of recovery, I'd like people to just assume that they should trash every CWM file they currently have and download it fresh.
This isn't a april fool's joke is it? I would be sad.
RacerXFD said:
This isn't a april fool's joke is it? I would be sad.
Click to expand...
Click to collapse
lol. where as i dont think he would ruin a good joke, i dont think would go this far to make a joke. gizmo is a pretty straight forward and generally helpful guy.
Not that there is anything wrong with using recovery stand alone...
The post I am waiting for is the one that tells me how to setup Rom Manager to work with _any_ froyo+ rom kernel combo, be it via red cwr our blue cwr or a well placed recovery-update.zip. I thought I had this working once but it is gone.
soba49 said:
Not that there is anything wrong with using recovery stand alone...
The post I am waiting for is the one that tells me how to setup Rom Manager to work with _any_ froyo+ rom kernel combo, be it via red cwr our blue cwr or a well placed recovery-update.zip. I thought I had this working once but it is gone.
Click to expand...
Click to collapse
If somebody can make recovery-update.zip from this recovery and paste it over rom
manager, it might just work.
uslacson1 said:
If somebody can make recovery-update.zip from this recovery and paste it over rom
manager, it might just work.
Click to expand...
Click to collapse
"Might" is the key word there.
ROM Manager sends commands to CWM on reboot. If you try to mix a new ROM Manager with any CWM before 3.0, it might use different syntax in the commands. Sure, it will probably work most of the time, but why take that chance?
The only real solution is for someone to port the CWM 3 stuff. Project voodoo already has quite a bit done on it, it just needs to be adapted to the Fascinate.
After that, Koush would probably be more helpful at helping us get the code successfully pushed into the CWM that ROM manager downloads.
gunnermike said:
lol. where as i dont think he would ruin a good joke, i dont think would go this far to make a joke. gizmo is a pretty straight forward and generally helpful guy.
Click to expand...
Click to collapse
Haha, pretty much. I'm a jokester in real life, but interwebz is serious business.
I think a more important point is that I wouldn't spend 4 hours typing this post if it were a joke xD
Thanks for posting this to clarify the why fors and the what nots. So its more than edify and amend scripting that's holding us back from an official CW recovery we need to have project voodoo updated as well for 3.x compatibility? Reminds me of the slcd Incredible issues we had. That has only been sorted out for a month or two. (amoled/slcd) Anyway thanks for this post it really does clear up some questions/concerns.
Sent from my SCH-I500 using Tapatalk
thanks for this thread. helps alot.
GizmoDroid said:
Haha, pretty much. I'm a jokester in real life, but interwebz is serious business.
I think a more important point is that I wouldn't spend 4 hours typing this post if it were a joke xD
Click to expand...
Click to collapse
Gizmo,
As much as I would love to trust your new CWM... I can't trust anyone today. In fact, I'm running to the basement as we speak with my aluminum foil hat. Please understand that no words that come out of anyone's mouth can be taken with any seriousness.
On that note, your CWM recovery works fantastic.
I appreciate it! Thanks.
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT
Where might these be found?
So, I tried step 1. I flashed, via Odin, the stock EB01 tar from adyn's stock post. Also pulled the atlas_v2.2.pit from his "how to fix brick after 2.7" post. I believe I'm bricked. I selected repartition, pit in pit section, eb01 tar in pda section. My phone now boots directly into the samsung stock recovery. I don't get a samsung boot logo either. I can get into download mode via holding down vol-down, but no matter what I flash now to try to bring my phone back to life, I'm still stuck. Has anyone run into this? I'm not a noob when it comes to Odin, so I don't believe I've made any mistakes.
EDIT: Ugh, I flashed what I thought was the full EB01 stock rom. It was the pre-rooted version I found a while ago. When flashed with the atlas v2.2 pit, it soft bricked the phone. So, just a suggestion for the OP that you can get the needed EB01 tar and atlas files from adryn's post on fixing your phone after it's borked with SC 2.7: http://forum.xda-developers.com/showthread.php?t=977493
I'll shut up now.
Before I begin, I will say that there is no hostility intended in this thread AT ALL. It’s just how I convey intense anger. Lulz.. jk
I don’t know about the rest of you, but I can’t count how many times I have read somewhere about somebody having some random ass issue with rom “x” and not a single person besides them is having said issue.
I understand the inconvenience in wiping data, contacts, apps, all that. But let’s be srsly. How much more annoying is it, and frustrating, to sit there in your messy room in your mother’s basement trying to watch porn all stressed out because your phone won’t connect drivers to your computer or connect to 4G? srsly. And how much more annoying is it for everybody else to have to listen to your whiny ass in the thread of said rom? I can tell you, Very. But I, like many, will still offer you help, always. So here it is, some pre-help!... for those of you who love flashing custom roms on your E3D.
First of all, I will say this… download the synergy superwipe/format tool. It’s a zip file. If you can’t find it, it’s in the development section in the thread titled “SYNERGY”… i had to tell you where it was, because i knew somebody would chime in here "hAlp, where can i haz it!?!"... never fails.
This should be used EVERY time you install a full ROM. Whether or not the dev’s tell you to wipe data or not, they always will recommend it because they know this is the only way to ensure a clean, install. So have this handy on your SD card. Because if you are a rom flashing whore like me, you will need it.
And for the record, I have had ZERO problems with EVERY rom I have installed on my E3D, with the exception of the bugs that are clearly stated in the OP of the rom’s thread. If you are popping up random little glitches, it is likely something you are doing wrong. Just sayin.
So let’s get started with the actual “guide” here… we’ll make this short and sweet. I will give you different scenarios too, ie flashing only a rom, a rom with a kernel, a rom with some cosmetic mods (battery indicator zip, etc.), and a rom with a kernel on top of it AND some cosmetic “theme” .zips, and maybe even a flashable boot animation. The current set up I am running is the steel rom, with the bc kernel, a boot animation, and a battery indicator change (thanks scrosler for that! Its dope as ****). K, here we go. Pay attention…
1. First of all, before you flash ANY rom, make a back up of your data and apps, I prefer myback up root or pro simply because I have never had a single issue with this app in the 9 months I have been rooting my phones. I would recommend this app to anybody. Also, if you are using windows, after you download your rom right click on the zip file, select “properties” and then select “unblock” and then “apply” and the “ok”… now place the .zip on the root of your sd card. I have had problems with roms not flashing properly when I forget to do this. So do it, just for peace of mind. Everything you intend on flashing, should be on your SD card before you begin.
2. Boot to recovery
3. Wipe (in this order) cache partition, dalvik cache, and data/factory reset. Do all of those TWICE, just to be thorough.
4. Flash the synergy superwipe, your phone will reboot itself into recovery when completed.
5. Flash your rom. If the rom has a kernel included, boot up the phone – even if you intend on flashing a different kernel, boot up the phone. The only time you should flash kernel right on top of a rom is if the rom does not include one... ok, phone boots, nowdDo all your google **** blah blah, maybe browse the internet a bit, verify that some basic things are functioning properly. This helps you verify that the ROM itself isn’t causing issue “x” after you flash a kernel or some other bull**** in the next few steps. We do process of elimination as we install, and prepare for troubleshooting by collecting useful information beforehand. This way, you have some information as to why something is not working properly if something is not working properly. Make sense? Thought so.
6. If you are going to flash a kernel on top of it, proceed to this step. After you have booted the phone successfully, power down to recovery mode again (I ****ing love recovery by the way, it’s a ****ing bios on my phone)… and again, you will want to clear cache partition and dalvik cache, in that order. After it is done successfully, go ahead and flash your kernel. After that is done, boot to system. If you get some kind of error after this point that you did not experience earlier, you can safely assume one of these 3 things, in this order… you got a bad download when downloading your kernel (re-download, and start over at step 1, annoying I know, but the only way to ensure proper install, again. Patience pays with these devices as they can be extremely tempermental.), something is actually faulty in the kernel build (you should be reading other’s experience with said software anyways, so you know what to expect), or your phone just doesn’t ****ing like you (this happens sometimes, it’s nothing personal.)
7. Assuming your phone has booted properly (****ing yayyyy) you may now proceed to this step (and this step can also replace step 6 if you are not flashing a kernel). Boot down to recovery again, clear cache, clear dalvik… you see the pattern here… flash your other little ****. For example, when I installed the steel rom with the bc kern, the battery mod, and the boot ani’… I followed this guide pretty much to the T. Anyways, I will use that as an example… after cache and dalvik cache are cleared, flash your battery icon, then right on top of that, flash your boot ani’.
8. Boot to system. You are now running a bastardized rom with a 99% chance of it running ABSOLUTELY flawless.
Furthermore, sometimes I will even run a rom for a couple days before proceeding to flash a kernel on top of it. This is simply to have useful information if a problem arises mid-use. For example, if I am running a rom for a week with zero issues, then flash a kernel, and immediately start getting random reboots, disconnected interwebz, or some other odd issue that pops up out of nowhere, I can safely assume it was something I recently changed (something I flashed). So again, either I got a bad download, or there is a design/programming issue. This will allow me to better pinpoint root cause of bugs that pop up on my hAxor3d evo.
Anyways, that’s about all I can think of for now. The purpose of this is really to help some of you learn how to better troubleshoot problems yourself before asking, if you would rather ask, that’s fine really. It’s just always better to learn.
Hopefully some of you find this useful, and if there is anything else somebody feels should be added, please do so, and I will edit the thread accordingly.
Thanks,
CB
maybe i should have posted this in the dev section....
oh well. mods can move it if they so choose, their call anyways.
Will this work for the evo 3d?
mattfmartin said:
Will this work for the evo 3d?
Click to expand...
Click to collapse
well, that's a more intelligent question than the ones i was expecting.
"where is the synergy superwipe found????" lol
Great guide! I've personally never had issues flashing ROMs if I just do a single wipe, but I guess all phones are different.
I hope it's almost completed so we can start flashing some ROMs
I've never built a CWM binary before (CWM integration has been done my someone else on every other device I've developed for) and it requires a full CyanogenMod source tree - mine got corrupted so I lost a few hours doing a full resync.
CWM integration is a poorly documented black art - especially on Samsung devices.
I've got something compiling now, maybe 10% chance it works. If it doesn't I won't be touching it again until sometime this week, as a friend of mine is arriving in town in about an hour to visit.
Edit: It booted, but it acted like the VolUp key was stuck (just kept looping up through the menus) and it spewed a ton of errors
Edit 2: Somehow it's treating side-to-side tilt as up/down, and I need to move recovery.fstab somewhere else...
Right now I have it compiled and not spewing errors,however:
Our accelerometer spams /dev/input/event1 with a lot of crap. CWM treats this spam as keypresses, making CWM unusable. I need to figure out how to filter out event1 keycode input to get anything workable.
This is really interesting, please keep us posted! I'm really looking forward to a good custom ROM for my Galaxy 5
Atleast we got a good kernel already :d
Im using rj kernel for sgp 5.0, and its working fine. The games who had some lags after some time playing are runing smooth so far.
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
@Entropy512 - Thanks a ton for you efforts! Really looking forward to this.
Entropy512 said:
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
Click to expand...
Click to collapse
That's the open-source philosophy.
With r7 kernel, you can do full Nandroid backup and restore (system, data, cache and dbdata). There are issues yet, but hopefully will be fixed soon.
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
zBusterCB87 said:
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
Click to expand...
Click to collapse
ClockworkMod Recovery comes from the same guy who maintains ROM Manager, but they are NOT the same thing.
CWM's source code is published, so people can port CWM without Koush's involvement. Which is what rumirand and I did - we have CWM 5.0.2.7 working on the USA and International Galaxy Player 5.0 units at this point. (You necroed an outdated thread, we've had CWM working for a while now.) For CWM on a USA version, install my kernel, for CWM on an International unit, install his.
Thanks but I'm having problems.
Entropy, I have your Kernel installed and I can boot into the CWM-based recovery but ROM Manager doesn't recognize that I have CWM installed and won't let me do anything. Does this happen to you too?
I have really been having a HELL of a time trying to do things with this since support for this device is so scarce. I couldn't find anything about Clockwork Mod for this device anywhere. I searched for hours and kept hearing people referencing the xda developers site so I decided to look here and I installed your kernel hoping it would help and it does. But ROM Manager still doesn't recognize that CWM is installed and tells me to install it and gives me a list of phones which my device is not on and doesn't let me do anything until I install a version of CWM.
So is there an official port for CWM available that ROM Manager will recognize or is there only the ports contained in your and your friends kernels??
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
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.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Two thumbs
Flashes fine and boots into recovery and can flash files as well. On aokp 35.1 for the record.
Sent from my SCH-I500 using Tapatalk
I will warn you all to use care with this, it does not play well with other recoveries and roms, and sometimes even with Odin. I used it a lot trying to test things for steve and we decided to put it on the back burner, it is cool but causes trouble sometimes. Basically, it's awesome to use and has lots of handy features (zip queue ftw) but try not to flash anything with it if you aren't near a computer that you can Odin with just in case.
Sent from my SCH-I500 using Tapatalk 2
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
tonu42 said:
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
Click to expand...
Click to collapse
yeah it changes some boot stuff and tries to reinject itself when you flash kernels. Which is handy if you want it but if you don't it causes problems. I was able to flash a glitch kernel from twrp but then it would just keep rebooting to glitch (cwm) recovery as though I had done three finger reboot. I flashed cm7 which put me back on blue older cwm5 and after flashing it again the phone booted so then I flashed back to ics.
Sent from my SCH-I500 using Tapatalk 2
It is really a 50/50 as to which way to go, a bunch of flashing or a bunch of Odin and then restore. Time difference is not to much. Were you able to do any backups and restores with it. I didn't have time to try that out yet. I also didn't have time to check to see if the problems made the bug report or not
Sent from my SCH-I500 using Tapatalk
Things I would like tested before I include it in AOKP.
1) data wipe. You can flash the ROM again boot and if all is well go back and restore.
2) flash the ROM or Efpophis kernel and tell me what recovery you have. It should be blue or red not twrp.
If those are good I'll look into including it.
Sent from my Glitched AOKP Unicorn.
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Dees_Troy said:
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Click to expand...
Click to collapse
Looks good both issues look fixed. I'll play with it a bit more. But I think you did a great job.
Sent from my Glitched AOKP Unicorn.
I guess you have your answers. I was flashing the zip version, but I do not ha e the further details you want.
Sent from my SCH-I500 using Tapatalk
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Stephen.k.spear said:
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Click to expand...
Click to collapse
ill fershur test this after it gets outta alpha stage, i dont wanna screw up my phone
Okay so far I'm loving this recovery, still have more testing, but I'm insanely impressed!
~~~~There is no spoon~~~~
After serious testing on this recovery last night I have come to the following conclusions:
1 This is the ONLY recovery that will let me backup/restore my device correctly on this phone
2 USB Mount doesn't seem to work, but if I had to trade USB Mount for working backups it is NOT a hard choice.
3 This recovery is one of the simplest to use and most functional recoveries I have used on ANY phone
4 This recovery is extremely responsive, full featured and beautiful to look at with the theme I have on it. Oh yeah, did I mention you can THEME THE RECOVERY?!?! WIN!
5 Any more bacon packed in this package would cause massive coronary problems.
6 If you are scared to try it, don't be. I am using ONLY TWRP recovery from this point on. I'm sold.
So if any of you are on the edge about this recovery, take the plunge. I promise you will not regret it.
my only problem is that i cant restore my CWM backups with TWRP
ztotherad said:
my only problem is that i cant restore my CWM backups with TWRP
Click to expand...
Click to collapse
This is definitely worth starting fresh and making a new backup.
~~~~There is no spoon~~~~
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
ztotherad said:
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
Click to expand...
Click to collapse
I haven't tried that yet, I was waiting for the next kernel it ROM release before flashing just to see if I could get cwm back on.
~~~~There is no spoon~~~~
Happy new owner of Amaze after three plus years on my Nexus One.
My device is unlocked, rooted, with S-On.
I purchased and successfully used 4ext, tried two CM ROMs in the last week.
Before trying these Roms, I Nandroid backed up the ROM installed on the phone when I first got it, which was running ICS 4.0.3 / Sense 3.6. (Didn't like Sense UI - was dissatisfied with one UI over another); I like the mimimalism of the CM ROM, as I've gotten used to CM7 on my Nexus one.
Anyways, settled on a CM10 ROM. This too is backed up in addition to the first Sense Rom. Man.... wish the audio skip wasn't there when playing music and was really not thrilled with low speaker volume after putting up with that on my Nexus One for years.
So I decided to try CM9.
Downloaded a CM9 zip from Goo and the correct Gapps.
Before asking for help, I have Googled several variants of my problem until I see purple links highlighted: translation, I have not been lazy to not try and look and find a solution - the links on the page aren't blue anymore, but purple because I looked and read those. I have seen plenty of threads describing my problem; maybe I've overlooked something , but this is the first time in years I have decided to ask for help. Moreover, I spent a good week bookmarking over 40 threads - organized into specific headings - in order that I could fast search for typical problems like I have now. Hate being defensive, but I see the last couple years the landscape is rife with folks rightfully being told to search before asking questions.
'nuff talk, here's the problem.
I placed the CM9 and Gapps thread onto my internal sd card as usual, then booted into recovery, into 4ext no problem. Prepared to wipe "data/factory rest/wipe and wipe cache, wipe dalvik cache".
This is what I did different from previous flash. After wiping data/factory reset... I choose "format all partitions (except sdcard" I had read enough tutorials to see that was an additional option to the wipe cache/wipe dalvik cache. Also, I was prompted to - (and this was maybe the stupid thing I did differently) - prompted with an option to uninstall smartflash. I choose the tick box... big no-no? (But I have seen in several repeated attempts to recover and restore either Rom back up, the option to "enable or disable" smartflash.
So maybe it never was actually uninstalled from 4ext? since I can see it as an option when I return to recovery. Of course I have done this after my first attempt to reboot - after installing CM9... which is described next
So after wiping data/factory reset and "format all partitions (except sdcard" ...then I installed the CM9 zip and the gapps zip, then selected reboot.
Upon selecting 'reboot' - got the infamous HTC splash screen. Then I calmly read many threads, thinking I'd solve the problem.
So far, here's what I tried as an attempt to fix/restore or learn something useful that will help me with any future steps i need to take.
1) I tried to reflash the CM9 zip. (Still did the wipe/rest but then wiped cache/dalvik cache" (no change, got splash screen)
2) Tried to restore either back up a couple times. (Each time did the wipe/reset but then wiped cache/dalvik cache" (no change, got splash screen)
3) Tried to reflash the 4 ext zip. (Hmm... won't install it aborts installation)
4) I can toggle usb storage
5) Looked at all the options within the 4ext UI just to be a 'rat in the maze' and get familiar with all the options so when i ask fort help i can perhaps navigate their faster with some confidence.
6) Went to sleep at 4am... not complaining at all.. we all have done this playing with these devices. This is just an inconvenience, I get it. I'll be putting my sim card into my Nexus one to be phone functional today while I stay on the road to figuring this out. (I know I need a 4g sim card if I want to use wifi callling on my Amaze.... but I don't care about that right now)
7) Fully charged Ruby just in case battery power could be an issue. Tried to reflash again this morning. No dice.
I know there's an answer. I know I have probably read the answer.. or the steps I need to take are in a thread somewhere... but I am a rat in a maze and don't know where to turn.
Thanks fellas.
Ed
Instead of wiping
additonal info/may help
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Also:
1) I have enabled "smart flash" under the option. (so I assume smartflash was never uninstalled)
2) Looking in the 4-ext "boot_backup" folder. I see boot.img files. There are three new ones that were added after my problems started.
I just read:
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
discslinger said:
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Ed
Click to expand...
Click to collapse
do a full wipe from 4ext recovery,reflash cm9 and gapps,
and for splash screen,you are missing kernel as you are S-ON,use hasoon tookit to flash your kernel here
http://forum.xda-developers.com/showthread.php?t=1493905
read above mentioned thread instructions completely...and for your kernel,its in your cm9 zip file named as boot.img,extract it and you will find it...
if i've helped you,don't forget to hit the thanks button
---------- Post added at 09:59 PM ---------- Previous post was at 09:00 PM ----------
discslinger said:
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
Click to expand...
Click to collapse
thats what i am talking about.. glad to see a good reader
Read the cm9 thread (just after the last release date). I believe cm9 is messed up. Missing or a bad boot.IMG. there are steps there to fix.
Sent from my HTC_Amaze_4G using xda app-developers app
Thanks guys!
Fixed.:good: