Database Users

Lets nail down the cause of JI6 soft bricks

Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.

I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App

Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.

this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App

I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.

just a question, why do people remove media hub? Does the application make the phone slow?

iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.

Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.

My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?

There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.

Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers

My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?

I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.

I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.

PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough

paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p

I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App

Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App

A little help reenabling Voodoo

So i'm running Bionix1.8. I was having trouble permforming a Nandroid restore (still Bionix1.8), and then i realized it was because I have to disable Voodoo before hand. Easy enough. So i did that, and successfully restored.
So then I wanted to reenable Voodoo, so I deleted the "disable-voodoo" file from /sdcard/Voodoo, and rebooted. I heard the robot say she was doing stuff, and the phone hung on bootscreen. I had to pull battery about 3 times before my phone got past boot, only to find that my phone had been wiped!
Can anyone advise me on how to successfully REenable Voodoo on Bionix1.8?

I just delete the DISABLE-LAGFIX file in the voodoo folder and reboot. Takes about 7 minute I would say. It seems like it hangs but it doesnt. Been doing it all the time for the past 3 weeks with all the Bionix versions being released

You can either remove or rename the disable-lagfix folder then reboot. You have to be patient when she starts talking and not remove the battery. Odds are at this point you will have to reflash the rom.
B.T.W. odds are you will be blasted for posting in the wrong section.

Yah i had a sneaking suspicion that impatience had something to do with it....ill try it again right now
-------
Edit: successful. Thanks guys, i wish i could delete embarassing threads like this. Whatever, i have no problem learning a simple lesson the very hard way. At least I can be damn sure i wont do it again!!!!

Moved to Gen.

Locked up my Fascinate--please help

I'm a relative newbie and not very tech-oriented, and I appear to have screwed up big time. I'd appreciate any help that can be offered. To cut to the chase, when I attempt to boot up my Fascinate, it gets stuck indefinitely on the Samsung logo.
Here's what I did to screw it up. I rooted my phone when I first got it last year and did a lagfix. It unrooted with the update to JD05. Yesterday I attempted to root it again using two different 1-click methods, neither of which worked. I then followed the instructions in the "Modified CWMrecovery for Odin" thread, not having it work until finally succeeding in getting root using CWM Red. The phone rebooted and was rooted, and everything seemed fine, so I used Rom Manager to Boot to Recovery. This did something strange--it took 15 minutes to get to the recovery screen, with a digital voice periodically telling me how much longer it would take. When I got to the recovery screen the first thing I did was to perform a backup. I think this effort to be safe did me in, because the phone must have already been screwed up then and I think I backed up the screw-up.
I then attempted to reboot and since then all efforts get me stuck on the Samsung logo. I've tried almost all options from the Recovery screen: reboot system now, apply sdcard update.zip, wipe date/factory reset, wipe cache partition, install zip from ascard, and restore. All bring the same locked up phone.
I'd appreciate any ideas to bring my Fascinate back to life!

First off the only way to get to red CWM is to install a voodoo 5 kernel. I'm thinking the voodoo kernel and the one click lag fix don't play well together. I'm sure someone else will step in with more info however I would start by looking for a thred called how to completely remove voodoo. Then try odin to restore. Good luck.
Edit. I read your post again and not sure if u did one click lag fix or just an older voodoo kernel. Either way same result u have to disable voodoo 4 and one click to install voodoo 5. Odin it. The voice u hear was the voodoo kernel converting your system to ext4 if this was the first time you've heard this I think your first lag fix may have been the one click.
Sent from my SCH-I500 using XDA App

Yes this happed to me too. If i take it to the Verizon store will they know my phone is rooted and moded? i need help ASAP

Search the forums on how to properly removed the voodoo lag fix. Then you need to reflash dj05. Voodoo doesn't really do much except for show you a higher quadrant score and limit to what roms/themes you can install. Same thing happened to me. Just do a quick search, I think its in the development section. The easiest way to remove it is with and. Hope this is somewhat helpful.
so fresh and so superclean.

Don't bring it to verizon because you would be defrauding them for your mistake. see if you can access your sd card through the computer and put either a file or folder in the voodoo folder called disable_lagfix and try booting again. If that doesn't help (it is probably too late for that) then you need to flash back to stock through odin. find the thread in development on how to do that. Good luck. Your phone is not broken. Breathe.
Sent from my sch-i500 using dl09 supah clean

Here is the ODIN back to stock if you don't want to bother with removing Voodoo. That should fix your phone with or without Voodoo. It's always worked for me.

THANKS SO MUCH its back to normal i cant thank you enough

Many thanks for all of the help.

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.

Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.

I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App

Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App

aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.

It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.

I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.

Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.

akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.

Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.

Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.

Try removing the SD card and booting.
Sent from my PC36100 using XDA App

rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!

It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.

bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?

Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.

herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.

Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?

Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol

akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

[Q] How to remove One Click Root...with a twist...

Ok, so before I get flamed, let me say that I did do a search and did see that there are ways to unroot the phone...however, I have what I believe to be a bit of a different case here and am just looking for info before trying any of them.
Background...(this is for a friends phone, not mine, or I would just Odin and call it good. He however does not want to loose any of his settings blah blah blah so doesnt want to go that route unless necessary)...Buddy got his first Epic and had me root it for him (One Click Root 2.5.1), that phone took a **** and had to be replaced. When he took it to Bestbuy (I think there, could be the sprint store, dont know that it matters) they hooked it up to their little file transfer machine, let it do its thing and gave him his new phone. Now, after doing that, it still shows as having Clockwork Mod installed, and you can boot into CWM, but none of the functions work, which I found out when I tried to install EC05 on his phone. I installed the zip to his sd card, rebooted into CWM and selected to install zip from sd...nothing happened...just went to a blank screen and locked up and I had to pull the battery. Rebooted the phone and it went straight to CWM without the three finger grip, I selected to just reboot the phone, lock up and battery pull required. Long story short (I know, too late for that) I tried several options and all of them resulted in a lock up and wouldn't let the phone boot normally...I was really feeling bad thinking that I had actually managed to brick his phone...last thing I tried was the advanced menu and selected to reboot recovery and luckily, that actually worked and booted me into sammys stock recovery mode and I was able to run the zip. Had to reboot several times, but it took and his phone is running well now on EC05.
So now to my question. Since CWM is obviously corrupted on his phone from that transfer and not being properly installed on this phone (I was actually blown away that it transfered in the first place) in order to correct that, do I just apply the newer CWM like its a stock phone and let it try to write over those corrupted/missing files or do I need to try to uninstall what is there first or is he going to be stuck having to Odin and take whatever losses he gets?

Thats actuarry an interesting diremma...
Does the phone show up in adb? Can you SU
Sent from my SPH-D700 using XDA Premium App

If you are rooted still, run MyBackup Root for him and then run Odin. If you're not, run the One Click Root 2.5.5 and then use MyBackup Root.

No, its not still rooted, just showing CWM. Thanks, I will try running 2.5.5 over it. I just wasnt sure if that would cause any problems...will let you know how it goes.

I've had a similar thing happen to me when updating a kernel. Reinstalling the same CWM right over the top worked for me.