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.
Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
followed this thread back in november when i first got the phone(its the first thread in the "thread roll-up sticky") : http://forum.xda-developers.com/showthread.php?t=798064
Back then it was much different and said to get voodoo. Everything went fine and I havent seen a reason to update my phone.
Now I want to update to whatever the newest stuff is. I guess we have 2.2 by now? I dont need a lot of stuff. I probably didnt need voodoo. But on my current version things have started to get really glitchy and slow and GPS will not find my location at all.
I also froze the verizon auto update program or whatever its called because they kept trying to update my phone OTA. I dont like that.
What steps do I need to do in order to get up to date and not lose all my stuff on my phone?
I think this really depends on what YOU feel up to date is for YOU.
Plenty of people could push a custom ROM and all its shiny bells and whistles but from the onset you seem like you would just be happy with a functioning stock ROM (perhaps a debloated and debinged one).
I would read through the few ROMs we have, including the latest 2.2 stock ROM and figure out what you would like. Find out if you want a custom kernel or just an easy set and forget one, voodoo or non.
I'll do my best at a suggestion here before I tackle the next part of your post.
I would go here --> http://forum.xda-developers.com/showthread.php?t=1013312
Grab one of the stock ED01 or EC01 (read the bugs n such if you like, basically the same thing) ROM and radio ODIN packages and follow the guide to flashing with ODIN. Grab Imnuts stock voltage PBJ kernel and just keep it vanilla.
**The above will require the use of ODIN and CWR(clockwork recovery MOD)**
Now the "not lose" part of your question. This depends on what you mean by lose. ( I feel like Clinton and his definition of what "it" is....). If you backup with google and/or titanium backup you are pretty much in the clear. Aside from losing maybe a login or some preferences you will not lose any hard data (pics, contacts, apps....etc)
Read all the steps before you do anything. Also, you will need Odin. Just search for it in the forums (or Google) and you should be able to find it.
What you want to do is flash CWM 3 by following this thread: http://forum.xda-developers.com/showthread.php?t=1046905
Then, you should go and backup your stuff with Titanium Backup (get it at the market). Backup contacts with Google.
Get the new radio from http://forum.xda-developers.com/showthread.php?t=1097355 I would go for ED01.
Download ComRom 2.0 (http://forum.xda-developers.com/showthread.php?t=1108991) to your SD Card. I recommended getting a version with a kernel either pbj or otb kernel.
Next, boot to Clockwork Mod (press volume up and down and power) and make a nandroid backup there. (Select the backup option in the menu).
Now, after every thing is backed up, wipe data, clear cache, clear dalvik (under advanced menu I think).
Finally, flash the ComRom by selecting the zip from the sdcard.
Now, as a warning, you will lose the stuff on your phone which is why you made backups. DO NOT flash the nandroid (CMW) backup. That is for if you go back to stock. DO use Titanium Backup and your Google account to get MOST of your stuff back. Everything stored on your SD Card should be safe.
If anything that I said is wrong, xda please correct me, but I've done it a few times... this is roughly what I did, and it worked for me.
EDIT: gkirby11 beat me to it.
I would agree with the previous suggestions, and would add that you should use Titanium Backup to backup all your user apps+data. Do not, however, use it to backup/restore system data, because this has been shown in many cases to be the cause of force closes, and other headaches.
I am thanking you for your great username, Art Vandelay. I assume that is a Seinfeld reference to the importer/exporter.
jptech7 said:
Read all the steps before you do anything. Also, you will need Odin. Just search for it in the forums (or Google) and you should be able to find it.
What you want to do is flash CWM 3 by following this thread: http://forum.xda-developers.com/showthread.php?t=1046905
Then, you should go and backup your stuff with Titanium Backup (get it at the market). Backup contacts with Google.
Get the new radio from http://forum.xda-developers.com/showthread.php?t=1097355 I would go for ED01.
Download ComRom 2.0 (http://forum.xda-developers.com/showthread.php?t=1108991) to your SD Card. I recommended getting a version with a kernel either pbj or otb kernel.
Next, boot to Clockwork Mod (press volume up and down and power) and make a nandroid backup there. (Select the backup option in the menu).
Now, after every thing is backed up, wipe data, clear cache, clear dalvik (under advanced menu I think).
Finally, flash the ComRom by selecting the zip from the sdcard.
Now, as a warning, you will lose the stuff on your phone which is why you made backups. DO NOT flash the nandroid (CMW) backup. That is for if you go back to stock. DO use Titanium Backup and your Google account to get MOST of your stuff back. Everything stored on your SD Card should be safe.
If anything that I said is wrong, xda please correct me, but I've done it a few times... this is roughly what I did, and it worked for me.
EDIT: gkirby11 beat me to it.
Click to expand...
Click to collapse
Okay, I sat here for the past hour trying to get caught up to date before I ask my questions. I only use this site like once a month and there is always new stuff here. I already have odin on my laptop cause I needed it for the tutorial that I linked in the OP
1)I have Rom Manager(v4.3.1.3) and under RECOVERY It says "current Recovery:ClockworkMod 2.5.1.0" and "Latest: ClockworkMod 3.0.0.8. Does this change step one as you posted?
2)I have titanium backup and have used it to freeze some of the bloatware. I do not know how to backup anything with it though. where do the backup files sit anyways until I am ready to put them back on my updated phone?
3)Can I go strait to ED01 from where I am now(DI01--was a few months after phone was released) Or do I have to work my way up through the other updates? What order do they go?
I dont even know what this step is, lol. Radio???
4)I will get the 1.5 OTB voodoo kernal. also, I noticed this roms stup looks like adwlauncher or whatever that other launcher is. Right now i use launcherpro, which i like more. I hate touchwiz. can I still use launcherpro on here?
5)I am guessing this part would be self explanatory once I got to it, but I might as well ask just in case, what is a nandroid backup?
6)Where do I go to complete these functions?
7)Do I just select it using a file browser like astro????
I thought that I had to remove voodoo before I did any of these steps??
What about the bloatware that I have frozen? The only reason I did that was because i was told to so in the tutorial that i linked in the OP . It said I will need them if I ever update.
Thanks for your help guys!!
1. CMW 2.x is fine.
2. Open Titanium, click the backup/restore tab at the top. Now press the menu button (left to your home button), click batch. Now, select RUN next to Backup all User Apps. It will then back them up to your SD Card.
3. Go through the steps listed in the tutorial. You will step through a couple radios to get to ED01
4. It uses the gingerbread launcher (made by google, but it is modified by TSM), but yes, you can use whatever launcher you want on almost any ROM.
5. A nandroid backup is made in Clockwork Mod, and it backs up the system & all your apps & data. If you want to go back to stock, you can flash the stock ROM and then restore this backup, and it will be exactly how it is right now.
6. These functions are in Clockwork Mod Recovery. Hold Volume Up, Volume Down, and Power to get to CWM.
7. No, you select the option in Clockwork Mod. It is something like choose zip from sd card. From there you navigate the SD card looking for the zip file with ComRom.
As a tip, to navigate CWM, use the volume keys to go up and down in the lists and the power button to select an option. Use the menu button to go back to the last list. When you are done, select reboot & cross your fingers.
If you have voodoo, OTB is also voodooo, so you are fine (*should be fine*).
Your bloatware will "disappear". You won't have to freeze it ever again. ComRom doesn't have any of the bing, vzw bloat, etc.
Good Luck & if at first you don't succeed, flash, flash again! For the worst mistakes, Heimdal and Odin work wonders.
Sorry if I miss something but first off try and stay away from rom manager, many people have been having issues with it.
ED01 is what verizon released to us as the official ota. EC01 is one that developers created from the mesmerize I believe. I don't think there's much of a difference between the two. Getting ED01 takes a bit more work as you have to return to stock and ota all the way up through 3g and it takes a bit.
If you're already on voodoo I think you shouldn't have any problems flashing a rom with a packaged voodoo kernel such as otb.
What I would do since you already have a recovery is download a zipped CWM 3.x and place it on your sd. Then download the rom of choice, recommend com rom or evil fascination if you're not going to flash much, they come with voodoo kernels.
Hop on odin and flash the EC01 radio. Boot into recovery and flash CWM 3.x. wipe data, cache, and dalvik. Flash the rom. After backing up of course.
Someone correct me if I'm wrong. Hope this helps
Sent from my SCH-I500 using Tapatalk
Sent from my SCH-I500 using Tapatalk
jptech7 said:
I am thanking you for your great username, Art Vandelay. I assume that is a Seinfeld reference to the importer/exporter.
Click to expand...
Click to collapse
Yep- most people i work with are too young to get that.
bangdrum said:
Sorry if I miss something but first off try and stay away from rom manager, many people have been having issues with it.
ED01 is what verizon released to us as the official ota. EC01 is one that developers created from the mesmerize I believe. I don't think there's much of a difference between the two. Getting ED01 takes a bit more work as you have to return to stock and ota all the way up through 3g and it takes a bit.
Click to expand...
Click to collapse
Yes, I would stay away from ROM Manager. Just boot into CWM.
Also, if you follow the step in the forum post that I linked, you can get ED01 without going back to stock and ota-ing. They have extracted the upgrade packages, so you just have to flash two or three packages to get to ED01. Really though either EC01, ED01, or ED03 should be fine.
Once I boot into clockwork mod I dont get an option for Nandroid backup
this is what I get:
Android system recovery <2e>
Samsung recovery Utils
--For BML--
Reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
E: Can't mount /dev/block/mmcblk0p1
(invalid argument)
#MANUAL MODE#
Click to expand...
Click to collapse
With the exclamation marker and the little android guy. I am affraid to click anything else so I just rebooted the phone and now i am stuck. I started here because this was the first step to do in the tutorial.
also, for me, to select anything in CWM, I need to press the home button, not the power button.
wut do?
You don't have CWM installed then.
Sent from my SCH-I500 using XDA App
If you can boot into android. Make your titanium backups and google backups. Then, get one of the all in one packages for odin and flash it.
Sent from my SCH-I500 using XDA App
jptech7 said:
If you can boot into android. Make your titanium backups and google backups. Then, get one of the all in one packages for odin and flash it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what if i just flashed CWM like you said to do in your original post? Even if its a few extra steps or whatever, it makes it easier for me because I have that list and a tutorial you linked to go off of
fupamobile said:
Once I boot into clockwork mod I dont get an option for Nandroid backup
this is what I get:
With the exclamation marker and the little android guy. I am affraid to click anything else so I just rebooted the phone and now i am stuck. I started here because this was the first step to do in the tutorial.
also, for me, to select anything in CWM, I need to press the home button, not the power button.
wut do?
Click to expand...
Click to collapse
You are booted into the stock Samsung recovery, not CWM. This is why the home key works instead of the power button.
Flash this recovery via Odin if you're on voodoo: (or want to get on voodoo)
http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Or, use this if non-voodoo: (use .tar file)
http://forum.xda-developers.com/showthread.php?t=942021
Once Odin is done, it will power down the phone. Unplug, reinsert battery and boot into CWM by holding vol up, vol down, and power at the same time, continue holding until CWM appears. Go to backup/restore.
artvandelay440 said:
You are booted into the stock Samsung recovery, not CWM. This is why the home key works instead of the power button.
Flash this recovery via Odin if you're on voodoo: (or want to get on voodoo)
http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Or, use this if non-voodoo: (use .tar file)
http://forum.xda-developers.com/showthread.php?t=942021
Once Odin is done, it will power down the phone. Unplug, reinsert battery and boot into CWM by holding vol up, vol down, and power at the same time, continue holding until CWM appears. Go to backup/restore.
Click to expand...
Click to collapse
this is wierd to me though. because when i first got the phone I thought I had done all that already. I followed the tutorial in the OP but this was in november and it was much different then. what that tutorial accomplished was getting rid of bloat, adding voodoo, getting root, installing CWM via Odin, adding launcherpro. I know I did SOMETHING right because my boot animation changed, touchwiz was gone, the bloat was gone, and I have root. but thats all I know that I did........
fupamobile said:
this is wierd to me though. because when i first got the phone I thought I had done all that already. I followed the tutorial in the OP but this was in november and it was much different then. what that tutorial accomplished was getting rid of bloat, adding voodoo, getting root, installing CWM via Odin, adding launcherpro. I know I did SOMETHING right because my boot animation changed, touchwiz was gone, the bloat was gone, and I have root. but thats all I know that I did........
Click to expand...
Click to collapse
If you heard the robotic android lady during install, then you have ext4 file system enabled (aka voodoo). If you don't remember, you can use voodoo control from the market to check if you have etx4 lagfix enabled. If you can't install this, your kernel isn't compatible. I recommend imnuts' PB&J kernels here. Stick with sv (stock voltage) if you aren't familiar with undervolting/overclocking.
http://sites.google.com/a/imnuts.net/android/kernels
If you are on the stock kernel, that can sometimes overwrite CWM. You have to boot directly into CWM after Odin to avoid it. Make your backups and flash ComRom then. Then CWM will stay, and you will have a ROM installed... with Voodoo nonetheless.
You can also get an ODIN package for a ROM. Look at http://forum.xda-developers.com/showthread.php?t=1048380 and get one of the Community Rom ones that wipes data. Make your Titanium,etc. backups, and then Odin that. Then update to the latest ComRom, and make sure to always wipe data, cache, and dalvik. That could be easier for you to do if you are fine with Odin.
artvandelay440 said:
If you heard the robotic android lady during install, then you have ext4 file system enabled (aka voodoo). If you don't remember, you can use voodoo control from the market to check if you have etx4 lagfix enabled. If you can't install this, your kernel isn't compatible. I recommend imnuts' PB&J kernels here. Stick with sv (stock voltage) if you aren't familiar with undervolting/overclocking.
http://sites.google.com/a/imnuts.net/android/kernels
Click to expand...
Click to collapse
yes i definitely heard that lady. so i have voodoo. but i dont have CWM??
so does that mean i can start from step one in the original post that jptech posted in this thread?
thanx guys for your help. i know im probably being a little difficult. i just dont want to screw up my phone.
Personally, no offense.. but it seems that you are having issues with CMW. I too had a disappearing CWM. The easiest route would be to backup what you can with Titanium, Google, etc. Then, use one of the all-in-one Odin ROM packages that I posted. Download one that wipes data, and you will start fresh with ComRom, a new kernel, and CWM. From there, feel free to flash another ROM from CWM. Just remember to wipe in between ROMs, and you'll be fine. Really though, it is very hard to "mess up" a Fascinate. As long as you don't corrupt the bootloader or flash a ROM for another phone, you can always ODIN.
Just a tip: I use the Amazon App Store, and it stores the apps that I have online (just without my data). It is really easy to reinstall things that way, but Titainum is great too. It can store your app's data which is really a nice feature.
Also, remember that it is fine to ask questions (it is the Q and A section). I respect that you are trying to be careful. Everyone starts somewhere.
My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!
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~~~~