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.
I have tried for the past 4 hours to install the AOSP MIUI ROM. I have tried a newer recovery, a mtd kernel. No luck. I install the rom in CWM 2.5, but it boot loops at that point and states that the sd card can not be mounted. It then counts down to 20 and resets over and over. Can anyone shed light and provide steps?
Well the first thing I would do for yourself is to Odin back to stock using the 2.2 pit file as well as odining the stock 2.2 ROM. Make sure you repartition as well so that everything is formatted!!! This will solve SO many issues and give prospective forum members a place to start with your problems you are having.
2.2 Pit file - http://download180.mediafire.com/09z...atlas_v2.2.pit
2.2 stock froyo - http://www1279.megaupload.com/files/...EL.tar.md5.tar
I am going to assume you have odin and not link a download simply for the fact that if you have read ANYTHING pertaining to CM7 or MIUI in our forums you should be well aware of how to use it.
After wiping you will need to flash the modem you want via odin. They are located in the sticky in the dev thread.
After this you will need to flash the CWM that is located in the CM7 or MIUI threads themselves.
here is a link : cwm3_fixed_for_cm7-ODIN.tar
Use odin to flash it, then simply flash the AOSP package of your choice from the their respective threads here in the forums.
TedLWJR said:
I have tried for the past 4 hours to install the AOSP MIUI ROM. I have tried a newer recovery, a mtd kernel. No luck. I install the rom in CWM 2.5, but it boot loops at that point and states that the sd card can not be mounted. It then counts down to 20 and resets over and over. Can anyone shed light and provide steps?
Click to expand...
Click to collapse
Also worth noting that I missed in the first post. You mentioned CWM 2.5....sadly this will not work nor will it work with any other CWM floating around. The ONLY way currently to flash it is with the CWM I linked above. These are from JT and fixed to work with the AOSP ROMs.
from JT himself
*** The recoveries attached below are ONLY to be flashed on a BML ROM, ie: touchwiz based ROM or earlier, non-MTD CMx ROM. DO NOT FLASH THEM IF YOU ARE CURRENTLY ON CM7 OR MIUI MTD ROMS! ***
Click to expand...
Click to collapse
Thank you, I tried to use the new recovery provided by JT, alas it did not work for MIUI, I will try again tomorrow when spirits are higher, I usually start from DL09 and OTA my way back to ED04, Do i have to stay on EB01 or can i use ED04, and yes i am familiar with odin. Thanks again my friend.
TedLWJR said:
Thank you, I tried to use the new recovery provided by JT, alas it did not work for MIUI, I will try again tomorrow when spirits are higher, I usually start from DL09 and OTA my way back to ED04, Do i have to stay on EB01 or can i use ED04, and yes i am familiar with odin. Thanks again my friend.
Click to expand...
Click to collapse
Don't quote me.... It shouldn't matter (EB01, ED01, ED04...etc) All that is needed is the updated recovery to run the package install. The package will format your filesystem so your version should not matter. If you are referring to the modem... its your preference. I am on EC01 but last time I was on like ED04 or something...
Might also try flashing CM7 first, booting in, then flashing MIUI since they use the same BML format.
Still no dice, I'm sick of trying this, I have Odined back to 2.2 around 10 times already. A good write-up is definitely necessary.
What kernal are you loading with ED04, etc.. before trying CM7?
Stock as i think i read that the rom includes a kernel, should i try a MTD kernel and then flash CM7/MIUI?
No, I was just making sure you weren't loading any voodoo kernals.
When I had issues loading MIUI, I went all the way back to the DI01 all in one rom (odin) then DL09, then CWM Fix all (3.x), then MIUI. Load the rom before you load the MIUI cwr.
I'm having major problems too. I've tried about every method to get onto CM7, but I either end up with boot loops or get stuck on the GalaxyS/CM7 boot screen for a long time (over 30 minutes).
I've started from almost every platform (stock back to DI01, comrom, evil, ....)
Used JT's cwm and still no go. I've rebuild my partitions in both odin and heimdall, I don't know what else to try myself.
I've gotten to the same place with the Galaxy S and Cyanogen screen, help is appreciated.
Sent from my SCH-I500 using XDA Premium App
im in teh same situation. ive tried doing everything i can find and i NEED miui on my phone.
haha seriously any additional help would be appreciated
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
My AT&T Samsung Captivate i897 has gone bad so I just purchased a used Note i717 (i tis on the way). I like the larger format, dual cameras +flash, LTE speed.
The phone is already in stock ICS 4.04 (build UCLF6). I would like to 1) root, 2) add CWM, 3) flash to final CM9 stable (like I have on my Captivate). I have read and read threads and posts to the point that I am a little dizzy. My questions are:
1) what is the best way for ICS 4.04 stock to be rooted and injected with CWM (the posts all seem to be targeted at the original GB)?
2) if I get in trouble and brick it (always seems to happen on my root attempts), is there a SuperOneclick or Heimdall or Odin approach that will push stock software (or any) so that I can retry 1 - in the past Heimdall was the savior)?
Thank you and I look forward to participating in this forum :good:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
gregsarg said:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
Click to expand...
Click to collapse
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
tonyo123 said:
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
Click to expand...
Click to collapse
Go to the last page in that thread. I posted an easy, fool-proof root method. It was simple enough that even I could do it.:laugh:
root for the ICS 4.0.4 is easy....
It consists of Odin pushing a CWM image, and flashing SU from your new found recovery.
But there are a few tips that will help you out...
follow teyshablue...and you'll be rooted in 10 minutes....g
THANKS
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
tonyo123 said:
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
Click to expand...
Click to collapse
Yeah, the video tutorial saved my bacon!:good:
Okay I'm planning on doing similar tonight with my newly arrived refurbed i717. It shipped with ICS.
I'm confused however...if I simply want to flash a custom ROM (versus running rooted stock ICS), I've seen threads stating that I don't need Root, but instead install TWRP2 via Odin from here:
http://forum.xda-developers.com/showthread.php?t=1584576
...then flash custom ROM via TWRP2 recovery.
Am I missing something? Searching on Q&A seems to indicate some worrying issues about attempting this method of root on these refurbed Note's running ICS:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
TIA
Root is your first step.....as you need the custom recovery to flash the roms...
ultimately.....pushing a recovery via Odin, is giving you root....g
You don't need to root to flash a ROM. You can flash cwm through Odin then flash the twrp zip if that's the recovery you desire. I'm not sure if all the bugs are worked out on the twrp Odin tar. Once you flash a recovery, you can make a backup of your stocker and then flash your ROM of choice. Again, you do not need to root. Flashing a custom recovery through Odin does not root your phone, and is the first step. If you wish to root , then you would flash the su binaries zip in a custom recovery. I just don't want there to be any confusion.
Gubment Cheeze
Oh boy...want to be sure here...
Froid, I think what you type is consistent with Teyshablue's process.
1) This process first adds CWM (the custom recovery) using ODIN with the file “odin_ni717_cwm_recovery_b4.tar" in PDS slot. I assumed it needed root first but here CWM is the first step.
See here:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
1A) Then, I think I should nandroid back up the Stock ICS ROM here with CWM? I think so but it's not in the guide.
2) The next step using CWM is to load "Superuser-3.0.7-efghi-signed.zip ". So this roots correct Froid?
3) After that, then I can nandroid back-up rooted ICS ROM again with CWM.
4) Then can clean cache, Dalvik, and flash CM9 with CWM (Do I need to do some factory reset full wipe before adding CM9 ROM)?
Am I missing anything?
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------
On a side note, make sure you do your homework on the available recovery options before diving in head first. I personally use TWRP and would highly recommend.
Gubment Cheeze
Froid said:
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
Click to expand...
Click to collapse
Froid, mind checking me one more time? I edited my prior post (with numbered steps) as you were typing the reply. I am not sure about skipping the rooting step but I know you are probably right. I think I will run through the process as stated adding the stock backup then the rooted backup. Sound okay?
MUCH THANKS !!!! :good:
On the recovery program, I have only used CWM while I had my Captivate. TWRP is new to me. More options better program?
That will absolutely work. Not a bad idea to have both stock and rooted backed up. Always full wipe when flashing a new ROM. follow the OP of the ROM you're flashing. I don't use cwm so do some research on whether or not you need the latest version to flash a cm9 ROM. There was an issue in the past with using an older version of cwm. Not sure if that still exists. Good luck
Gubment Cheeze
Rooting Upgrading Anxiety
thanks all for the help, knowing that I just purchsed a close to $500 (shipping and accesories) used phone and knowing how many times I messed up my Captivate did not allow me to sleep well last night. I really want to do this right and not be panicked with a messed up Note to start with. I will sleep better knowing that I have a thought out and tested approach for when it arrives tomorrow.
And yes, TWRP has a few more options. I was always a fan of cwm, and its a great recovery. I just prefer TWRP for its UI, backup speeds, and being able to name the backup beforehand.
Gubment Cheeze
Let me know of progress
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
tonyo123 said:
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
Click to expand...
Click to collapse
Yes, naming backups is good as I have had to go back and just had many dated files which became almost hunt and peck in finding the exact one I needed. As for CWM, I also used the Devil Kernel, not sure if it is available for the Note, that beyond speed, also gave a few added optionsto CWM including a file manager which came in handy in swapping out system files (like CM9's Trebuchet launcher being replaced by a lighter version). But, a step at a time. I only used the added kernel because the Captivate with single core was a bit speed challenged (but CM9 made it like new).
Success!!
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Madtowndave said:
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Click to expand...
Click to collapse
Awesome for you. I am awaiting dilivery from USPS. I hope they don't let me down after payong $40 for the overnight.
Two questions:
1) What did(do) your Win7 drivers in 'device manager' indicate? Was it something like “Samsung Mobile USB CDC Composite Device" or did it identify the phone by name. I have seen both types in my Win7 setup with my Captivate so want to make sure I get this right.
2) So, you did not specifically root (no need for the "Superuser-3.0.7-efghi-signed.zip" or something like it). So assuming adter I add CWMm I flash the CM9 (Cyanogenmod 9 stable) ROM will that root my phone? I guess the more general question is do these ROMS automatically come rooted?