The truth about version of CWM and your ROM - AT&T Samsung Galaxy S II Skyrocket SGH-I727

There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.

I concur. Ive tried all 3 and ive had no issues. I think some folks state to use certain ones because thats what they used and they didnt have any problems, so they keep telling everyone to do what they did.
As with any Rom load, all issues arise or dont arise based on how well you cleaned the slate before applying the ROM.
Dixit

Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!

randomtask16 said:
Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!
Click to expand...
Click to collapse
what issues are you having? right away the first thing i would try is downloading the rom again as you may have had a corrupted download.

From personal experience I have had a ton of issues before I ODINd the 5.5.0.4 recovery. Prior to that I was running the 5.8.1.3 and I was having a ton of issues flashing some of the roms. I don't have any proof of errors or anything but I'm certain that Appdroid will be willing to vouch for me right now.
~PsyCl0ne

I've tried them all without any major issues except for one. Flashing ROMS is one thing but the overall functioning of all the tools within seem to differ. Permissions for example work on some and not on others. They do differ overall but I agree flashing a ROM isn't an issue. Everyone has their preference and if a developer says to use a particular version, there is a reason. I'll ask you since your the expert, do the wipes and cache clears work the same way?
Sent from my SAMSUNG-SGH-I727 using xda premium

Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
I dont use Rom Manager, you wont find alot that use it for those functions either as its essentially passes that request off to CWM when its rebooted. So Id suggest just rebooting to recovery using the toggle panel in Superlite, then in the CWM touch, just backup, restore, do anything.
Dixit

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
This is exactly how I get into recovery on my AT&T phone. Holding three buttons just causes it to reboot over and over again

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Oh yes, you're on rogers. I thought rogers users had to hold volume down only+power button to get into recovery (ie no volume up key involved). I've seen many rogers users say that...
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
bdbx18 said:
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.
Click to expand...
Click to collapse
Oh! Now I get it. I have had weird issues with ROM Manager ever since I had this phone. Backup via ROM Manager worked a couple times on gb roms but then it started doing what you described. Ever since it started doing that I just backup from cwm, and then go back in with Root Explorer to re-name the files so I know what's what...

Can't you just boot straight to recovery from most roms as well as from rom manager if you were on a rom that didn't have that ability? I can't remember the last time I had to press buttons to get into recovery, I'm not saying it's not useful to know, but merely stating that it's highly unnecessary in most cases to ever have to touch the buttons for recovery.

sk8erwitskil said:
There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.
Click to expand...
Click to collapse
You are absolutely correct. That is why I have not required any specific recovery, but told people what I use. yours . But, there is a caveat, since flashing a full rom requires reliable wipe operations from the recovery, it appears to be a hit or miss. That is why, I have specified the requirement that whatever recovery you use, use the recoveries built-in Format /system, /cache and /data, I am not going to do it within my update script.
BTW, thanks for the recovery, it cuts down a bunch of time trying to test, build..

Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR

mhx said:
Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR
Click to expand...
Click to collapse
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...

mohan_kr said:
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...
Click to expand...
Click to collapse
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
I've flashed multiple ICS roms multiple times on multiple CWM (touch and non) recoveries, and I've never had a single issue.

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
If the OP was talking about different features of a particular recovery, then yes there is point to it. He is talking about flashing a ROM with edifying scripting support for the skyrocket, which should work regardless of the version of the base android platform for our device, if of course the ROM creator has put the rights bits in the script for that particular ROM.

Related

Bar None I need bare facts

What is the best rom out there. Also i am running Serendipity 6.2 and for the life of me i dont see detail instructions on how to upgrade nore video. i am stuck. some help please.
Best rom threads are pretty much frowned upon since there have been about 600 of them created (maybe an exaggerated figure). Plus it's based on personal preferences anyway. As to your other problem, to get any help we are going to need quite a bit more detail about what the issue is please.
You download it.
You flash it.
Ipso facto.
Sent from my Captivate
Best ROM can be found here:
http://tinyurl.com/3tq5elx
But dont tell anyone...
MikeyMike01 said:
You download it.
You flash it.
Ipso facto.
Sent from my Captivate
Click to expand...
Click to collapse
let me try to elaborate...
you download the update file for your rom..
you flash the update file for your rom..
dido...
blacura said:
What is the best rom out there. Also i am running Serendipity 6.2 and for the life of me i dont see detail instructions on how to upgrade nore video. i am stuck. some help please.
Click to expand...
Click to collapse
matter of oppinion but i say dragon rc6 is the best. well it has the greatest ever boot sequence. but it is not a popular one and requires odin to get the full seemless splash screen to splash screen to boot animation to live wallpaper sequence.
as for the other question well what problem are you having? i mean if you are already on a custom rom all you need to do is backup the apps in titanium and reboot into recovery which may be in the power menu, otherwise power down, hold both volumes, push power, hold all 3 untill the first splash screen pops up. once in cwm recovery clear dalvik cache in advanced cwm features for good measure, then you go to install .zip from sd card>choose zip from sdcard>find your new rom and flash it.
if all hell breaks loose;
1 you use odin to flash back to stock,
2 master clear, (optional, looses all backups unless you move them to computer before everything went wrong)
3 boot up phone,
4 put rom on internal sdcard,
5 (option a. fast and dangerous) check that 3 button combo works, if it does then odin flash speedmod kernel .tar. phone wont boot. be warned. main reason to verify 3 button is you will need it if the flash goes bad. this is more dangerous from 2.1 but is the fastest way to flash a rom.
5 (option b. slow and safe) alternatively you can root in stock 2e recovery via update.zip then install rom manager
6a (speed mod method from 5a) 3button into recovery it should be cwm, (green letters)
6b.1 (rom manager method) open rom manager, select flash cwm recovery
6b.2 reboot into cwm from rom manager, (it will reboot but not into cwm yet) select reinstall packager, this step may need to be done twice before it enters cwm
7 install .zip from sdcard
8 choose .zip
9 flash new rom
pretty standard stuff. there should be a thread on this, oh wait there are several. so please search and be more specific, if there is a specific question you have then ask. don't just say there is no instructions, well because there is!
I use Andromeda3. It is a great ROM for battery life and reliability.
Cm7 is the best
Sent from my SGH-I897 using XDA Premium App
AdamOutler said:
I use Andromeda3. It is a great ROM for battery life and reliability.
Click to expand...
Click to collapse
Haha nice Adam, posting about your work
But umm, it mostly goes by preference.. I suggest you look them up on youtube (Mobile Techvideo's channel). There's some like Adromeda3 which are very stable and stock styled or some like Team Phoenix's work that are more customized.
At the end, they're all great and you have to choose the one that suits you the best
skizzz said:
Best ROM can be found here:
http://tinyurl.com/3tq5elx
But dont tell anyone...
Click to expand...
Click to collapse
+1 that is the best i have used as well
The search feature works wonders.
Sent from my SGH-I897
There is no best rom, just a best for you rom. Flash a few and find your fav

CWM: A thread of its own

OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!
If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.
boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.
stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.
Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk
kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.
Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk
I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App
Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App
Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.
Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.
Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App

[q] do not use rom manager - help!

I read the posts, but maybe I did not understand?
I downloaded CWM and installed via the Android Market. Then I see the icon is named ROM Manager (whoops, is this already bad). I hit the "Flash ClockworkMod Recovery" button. Then I used up/down volume and power to boot into CWM and did a backup from there.
So am I screwed?
Is the backup good?
Can I use the CWM that I have as long as I boot into it?
Please, I have not been able to understand exactly what the "DO NOT USE ROM MANAGER" means. If I just boot is that ok?
I guess you can tell I'm new but I have a lot of software experience - just not in this environment - maybe I'm moving too fast for my knowledge (I think so now!).
AT&T Galaxy S II Skyrocket, SGH-i727, 2.3.5
Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.
rhtufts said:
Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.
Click to expand...
Click to collapse
Now would be a good time to read:
http://forum.xda-developers.com/showthread.php?t=1311081
As you can see, CWM is included in the kernel you flash, and thus there is no need for ROM manager. It doesn't play nice with this device anyway, and is just unnecessary imo.
Use the recovery not rom manager itself...
Sent from my SAMSUNG-SGH-I777 using XDA App
rcklss1 said:
Use the recovery not rom manager itself...
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
So the OP is fine if he uninstalls Rom Manger even though he used it to flash CWM Recover? That seems a lot simpler then the cwm injected kernal method I just did.
Install rom manger, flash CWM, uninstall rom manger... flash roms all day. Would that work?
rhtufts said:
So the OP is fine if he uninstalls Rom Manger even though he used it to flash CWM Recover? That seems a lot simpler then the cwm injected kernal method I just did.
Install rom manger, flash CWM, uninstall rom manger... flash roms all day. Would that work?
Click to expand...
Click to collapse
No.
What part of "Don't use rom manager" don't you understand?
rhtufts said:
Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.
Click to expand...
Click to collapse
ROM MANAGER IS NOT CWM.
CWM is in the KERNEL (well, to be specific, in the initramfs of the kernel) on nearly all Samsung devices.
ROM Manager is an app that tries to install CWM, but FAILS to do so correctly on our device. CWM versions installed by ROM Manager DO NOT WORK PROPERLY on the I777.
ok heres the deal the cwm you booted into was probably rom manager cwm. so here are the next steps to take. question is are you using a custom kernel that has cwm installed? when you rooted your device did you have cwm installed? i also noticed you were using a skyrocket. when i rooted my wifes SR I did the all in one package. My opinion is just unistall rom manager and reflash cwm. then reboot into cwm and make a nandroid backup. although in theory your backup you did with rom manager is good forever unless you delete the file under /clockworkmod/backup.
miui+siyah = beast
OP, if you ****ed up probably the easiest step of the process(after all in one of the stickies it says DO NOT USE ROM MANAGER, as so), rooting your phone is not for you.
Either that or you're trolling.
bgraves said:
AT&T Galaxy S II Skyrocket, SGH-i727, 2.3.5
Click to expand...
Click to collapse
*kicks to the Skyrocket forums*
Red5 said:
*kicks to the Skyrocket forums*
Click to expand...
Click to collapse
Reading through this made me confused. But to the OP. Mod Manager is fine. You can use that to install CWM recovery. Just be sure to chose the T-Mobile SGSII version of CWM when it asks.
DO NOT USE ANY OF THE ROMS IN MOD MANAGER THOUGH. They are built for the SGSII phones. You can however use Rom Manager for all other options such as installing roms through SD, fixing permissions, and booting up into CWM, etc.
stevehkim said:
question is are you using a custom kernel that has cwm installed? when you rooted your device did you have cwm installed? i also noticed you were using a skyrocket. when i rooted my wifes SR I did the all in one package. My opinion is just unistall rom manager and reflash cwm. then reboot into cwm and make a nandroid backup. although in theory your backup you did with rom manager is good forever unless you delete the file under /clockworkmod/backup.
miui+siyah = beast
Click to expand...
Click to collapse
Using the stock kernel. I rooted with DooMLoRD_v3_ROOT-zergRush-busybox-su. So I can do the uninstall and then reflash CWM. Do you have a URL handy for the reflash? Don't want to make another error.
and thanks, your reply is very helpful.
creepyncrawly said:
No.
What part of "Don't use rom manager" don't you understand?
Click to expand...
Click to collapse
Probably the part about what else he's supposed to do. If I knew, I'd tell him. I assume he should read the whole thread in dev about how to get CWM installed through recovery but I'm just a novice. You might have been more helpful but I see that a lot of you are too busy hanging out in in dark closets having sex with your phones... tin foil hats and all. I know it's a pain answering the same questions over and over. I've provided support on a lot of boards and on a lot of subjects. When I got tired of typing the same answers, I started keeping them all in a text file so I could copy and paste them, links and all. That way, the info is spread all over the place and new users don't have to resort to finding the single "needle in the haystack." I know the L33T (do they still use that term? It's been about 20 years since i've seen it... probably for the good) love to repeatedly type "DO A SEARCH." Why not just help. If you don't want to and only want to maintain being L33T... do it elsewhere. You serve no function other than stroking yourself. I hate the "slam the noob" mentality. We were all one at some point. Merry Christmas.
The confusion here is that the OP posted this in the i777 forum. The i777 CANNOT use Rom manager to flash recovery and they have to use a cwm injected kernel.
The OP needs to learn where to read about his phone and remember what model he has.
Sent from my HTC PH39100

[Q] No recovery after OTA kj6 update....HELP!

I have rooted 2 different phones after the OTA KJ6 update. I rooted one phone with super one click 2.3.2 and the other using doomlord_v3_root and both phones sends the error:
Can't access
csc/ tmb....file? I tried flashing just the csc file using odin but it just soft bricked the phone. Can anyone help with this? I can't get either phone into recovery
I'm pretty certain that being rooted just gives you the ability to push the files needed for recovery to /system... Or, you could flash a kernel with cwm recovery
Sent from my SGH-T959V using xda premium
That "can't access CSC/TMB" error is normal, at least for me. As for getting into recovery, it's different once you flash the Gingerbread boot loaders.
Power off the phone. Hold the volume up & down buttons at the same time. While doing that, press and hold the power button. Once the "Galaxy S" screen shows up, wait a second or two and you'll notice that screen gets a tad bit brighter. When that happens release only the power button while continuing to hold the volume buttons. You should get the recovery screen after that.
I know how to do download mode and recovery, and all that guys. I'm not a noob, I have just never posted anything. But I get stuck because on Froyo (rooted) the 2nd option on the recovery screen it said "reinstall packages" and you choose that one...blah blah blah....well on Gingerbread recovery the 2nd option on the recovery screen is "apply update to sd card" and that option takes me to files, and I can't find an update.zip anywhere in recovery or on the sd card or on the phone. And I keep getting the following error:
--Applying Multi-CSC...
Istallng Multi-CSC
Can't access to /system/csc/TMB/system/
Successfully applied multi-CSC.
What am I doing wrong? I know it has got to be something simple (hopefully), it usually is anyway. I appreciate yalls time.
Have you tried using Odin to flash a modded kernel? It will give root and cwm recovery which hopefully you will be able to access.
Sent from my SGH-T989 using xda premium
I have actually, I flashed KJ1 + voodoo (Dr.honks kernel) and my phone doesn't act stable on it. I installed Busybox and everything but my phone does crazy stuff like shut off randomly and freeze up too frequently.
Is root your goal? Because your title states no recovery which is the reason you received the responses you did.
Sent from my SGH-T959V
Yes I have root, sorry if I'm misleading....that's kind of why I haven't posted anything before...don't wanna crash and get burned on here, ya know
You have root. You know how to get into recovery. What is your question?
Sent from my SGH-T959V
i can't get voodoo, or clockwork recovery. I can't flash anything, the recovery that is shown is the stock recovery. It's almost like I'm missing the update.zip or something. I posted what it was doing, is it not clear? I know it sounds crazy, I've actually never seen this before.
Odin a modded kernal as said above.
Sent from my SGH-T959V
http://forum.xda-developers.com/showthread.php?p=20067583
Sent from my SGH-T959V
Danyelle39 said:
i can't get voodoo, or clockwork recovery. I can't flash anything, the recovery that is shown is the stock recovery. It's almost like I'm missing the update.zip or something. I posted what it was doing, is it not clear? I know it sounds crazy, I've actually never seen this before.
Click to expand...
Click to collapse
I'm going to attempt to clarify things here, so forgive me (and correct me) if any of this is wrong
- You updated 2 different SGS 4Gs to KJ6 (2.3.6) using Kies Mini
- Both phones are now rooted
- You tried using drhonk's KJ1 kernel on at least one them (which gives you root, CWM, and voodoo lagfix) but it was unstable
- You WANT to have CWM vs the stock recovery
What is the current state of either phone with regard to what ROM & kernel are on it?
If you're at stock 2.3.6 (KJ6 ROM) and you were having issues with drhonk's kernel, you can try one of bhundven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]. The latter of which on that list will give you root, CWM, and voodoo lag fix.
---------- Post added at 12:14 AM ---------- Previous post was at 12:11 AM ----------
Note the link that lumin30 gave is flashable via Heimdall. I used it to flash onto my phone and the kernel works great. I'm currently running it, as a matter of fact.
[/COLOR]Note the link that lumin30 gave is flashable via Heimdall. I used it to flash onto my phone and the kernel works great. I'm currently running it, as a matter of fact.[/QUOTE]
Oops... I flashed it in CWM. Kernel does work great. Though bhundven recommends flashing Beta 2d until he releases his new version. Both kernels have worked great for me.
lumin30 said:
[/COLOR]Note the link that lumin30 gave is flashable via Heimdall. I used it to flash onto my phone and the kernel works great. I'm currently running it, as a matter of fact.
Click to expand...
Click to collapse
Oops... I flashed it in CWM. Kernel does work great. Though bhundven recommends flashing Beta 2d until he releases his new version. Both kernels have worked great for me.[/QUOTE]
No oops, you can flash it either way. I had just installed stock 2.3.6 and didn't have CWM, so I went the Heimdall route. I didn't try Beta 2d, I went straight to Beta 3. I dig it.
I think he recommends Beta2d because of a deepsleep issue draining battery for some people.
Sent from my SGH-T959V
Danyelle39 said:
I know how to do download mode and recovery, and all that guys. I'm not a noob, I have just never posted anything. But I get stuck because on Froyo (rooted) the 2nd option on the recovery screen it said "reinstall packages" and you choose that one...blah blah blah....well on Gingerbread recovery the 2nd option on the recovery screen is "apply update to sd card" and that option takes me to files, and I can't find an update.zip anywhere in recovery or on the sd card or on the phone. And I keep getting the following error:
--Applying Multi-CSC...
Istallng Multi-CSC
Can't access to /system/csc/TMB/system/
Successfully applied multi-CSC.
What am I doing wrong? I know it has got to be something simple (hopefully), it usually is anyway. I appreciate yalls time.
Click to expand...
Click to collapse
I get that same error about CSC. I think everyone does. Note that it says "Appling" not "Applying" LOL. Don't think that has anything to do with your problem.
Also what OTA 2.3.6 update? I thought we all had to use Kies Mini to put the stock update on? Or is that just a Tmobile USA thing.
Correct both are rooted...well correction I had to flash one back to stock because I messed it all up playing with Heimdall, so now only one has root. But yes, both are running KJ6 2.3.6 (only one is rooted with the "not working" recovery) neither one has voodoo as of right now. Both phones are giving the same error "cant access to /system/csc/tmb/system/" (even the one that is not rooted). Yes I want cwm or voodoo either one, but I've been experiencing the unstableness with voodoo. On the phone that is rooted...yes it goes into download mode and recovery, but recovery doesn't have an update.zip to flash, so therefore, I can't flash anything. I don't like using custom kernels (although I have found KG4 is probably the most stable), I just wish I could root my Gingerbread and actually be able to use recovery to flash, and fix permissions, and all that good stuff. I don't know what I did wrong. I'm not a noob, I just have never had to actually post anything on here. I find little things all time that ain't right, or just don't make sense about my phone. But I usually either fix it or live with it. But this one has got my brain boiling! I can't figure this one out. I know there are alot going on that doesn't make sense at all, I wish a magic fairy would come in and fix both phones like they just left the store so I can start all over and hopefully not run into this problem....anyone know of any fairys available?
Having CWM or the right recovery you refer to is a modded kernal. The stock kernal gives you the recovery you are seeing. The update.zip was on froyo. Now you just need to ODIN the modded kernal we keep telling you to do. That will give you CWM or the right recovery to flash away with. ODIN A MODDED KERNAL. Take your pick. I recommend bhundven as he is active developer and updating his work. They have worked great for me. No problems.
Sent from my SGH-T959V
And we understand now... you are not a noob.
Sent from my SGH-T959V

[q] twrp recovery?

Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
Sent From my Two Tin Cans & String Device on The Wookie Network
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
RAVEN6 said:
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
That's quite strange... I've been using TWRP 2.2.0 for a while now, and I have no problems. I can boot into Recovery mode with up/down and power with ease, as well as through a ROM.
Click to expand...
Click to collapse
Unless you typed it wrong, the problem seems to be you're holding power down along with the volume buttons. I've never had to do that after the phone vibrates telling me its powering up
Power down the phone, then power it back on, then immediately press and hold both volume buttons only. Just a thought.
I've been using twrp for awhile now to flash skyics. Never an issue getting to recovery.
Edit. Odd that cwm works for you but twrp doesn't. Maybe Odin back to stock and do it all over again?
I've flashed using either method. As long as it works, right?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
TWRP rulez
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
ConfusingCurve said:
RAVEN6 said:
That's quite strange... I've been using TWRP 2.2.0 for a while now, and I have no problems. I can boot into Recovery mode with up/down and power with ease, as well as through a ROM.
Click to expand...
Click to collapse
It is strange. Now that I am back on CWM Touch, I can enter recovery using up/down and power. I'll wait a while before I reinstall TWRP.
Click to expand...
Click to collapse
I personly don't like TWRP it still has issues for me as well. I have had to flash more then once cuz it did not take. I went back to touch and it flashes every time on the first shot. It looks cool but still needs work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
User error
Twrp works fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
RAVEN6 said:
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
If you install goo manager and install the recovery script from the haptick bottom left button, the easiest way to start from recovery is from goo manager or from from manager without the annoying recovery start with the power and volume up + down. Twrp is the smoothest way of flashing , back up and recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
TWRP 2.2 is awesome. Very easy to use and full of features. I have used it to install several updates of SKY ICS 4.2F and CM9 nightlies for my Skyrocket with out a hitch. I prefer it to my older recovery (Clockworkmod Touch Recovery v5.8.1.3 )
For users that can't get into recovery from a complete power down, it would appear that you have a bad TWRP install and/or you are not using the proper key combinations. I suggest the following:
How to Install TWRP via GooManager?
1. Install the GooManager app from Market (Play Store) or install from SD card.
2. Open GooManager
3. Tap menu and hit Install OpenRecoveryScript
4. Tap Yes
5. Verify that the filename displays your device's code name and hit Yes
6. The file will download and your device will install the recovery automatically.
How to boot into recovery only?
1. Unplug USB
2. Take the battery out and place it back.
3. Hold both Vol up + Vol down buttons, press the Power button
4. Release the Power button after one beep.
Another vote for TWRP. First discovered via Rev. Kyle on my HP Touchpad.
Install using GooManager and does everything I want it to do.
Sent from my SAMSUNG-SGH-I727 using xda premium
mindmajick said:
User error
Twrp works fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I don't think so.. it's not difficult to use it just doesn't always work. I really liked having a file manager on board though.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Its worked for me on every rom every time. Used it to flash everything under the sun.
User error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mr_magoo said:
I personly don't like TWRP it still has issues for me as well. I have had to flash more then once cuz it did not take. I went back to touch and it flashes every time on the first shot. It looks cool but still needs work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
User error I've flashed a ton of ROMs 100% of the time it works all of the time
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
User error I've flashed a ton of ROMs 100% of the time it works all of the time
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
User error is not it several people have had issues with twrp. If so then explain to me what I did wrong? I wipe everything and install just like I do with touch. It never fails with touch but has at least twice with twrp. Maybe it doesn't like my phone ... But don't be trying to say I'm doing something wrong I been flashing for a long time..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
you could of had the infamous "sticky power button" , seems more than one user is having this prob and blame it on the recovery, cwm or twrp, or a bad flash.
if you get the vibration, but does not enter in recovery or dl mode, or bootloops, could be sticky power button.
mr_magoo said:
U r a putz. User error is not it several people have had issues with twrp. If so then explain to me what I did wrong? I wipe everything and install just like I do with touch. It never fails with touch but has at least twice with twrp. Maybe it doesn't like my phone ... But don't be trying to say I'm doing something wrong I been flashing for a long time..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Maybe you aren't waiting long enough for the install to settle.
Hes not being "a putz".. just because other people have the same problem doesnt mean its not user error or misinformation. I mean, come on.. i read these threads religiously and have given up correcting all the misinfo that gets shared as fact.
Don't take it personally.. I've been flashing a long time too. AND I've committed user errors. No one is immune. Impatience is usually the biggest err. You know why i don't help people as much as i used to? Its the insulting posts and threats that come with telling someone the right way to fix something.
Edit: "user error" is not an insult. But please refrain from calling people names. THAT is insulting.
Edit2: have you ever read the skyics threads? Plenty of errors are reproduced there.. and usually its "user err". Gets confusing for the devs.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Works perfectly for me since I flashed it a few weeks ago
mindmajick said:
Maybe you aren't waiting long enough for the install to settle.
Hes not being "a putz".. just because other people have the same problem doesnt mean its not user error or misinformation. I mean, come on.. i read these threads religiously and have given up correcting all the misinfo that gets shared as fact.
Don't take it personally.. I've been flashing a long time too. AND I've committed user errors. No one is immune. Impatience is usually the biggest err. You know why i don't help people as much as i used to? Its the insulting posts and threats that come with telling someone the right way to fix something.
Edit: "user error" is not an insult. But please refrain from calling people names. THAT is insulting.
Edit2: have you ever read the skyics threads? Plenty of errors are reproduced there.. and usually its "user err". Gets confusing for the devs.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Very well. I'm sorry if I offended you. I got a little defensive. It still wasn't user error with twrp though.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wow! You are ok. Really. Sorry for the rant too.. I've just run into quite a few unstable folks around here.
I truly respect and appreciate the apology.. thank you is all i can say.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Categories

Resources