Related
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.
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
hi everyone,
I am actually a long time custom ROM flasher started since Desire days, but registered recently because of this problem I have with the Tab 10.1 Wifi.
Despite me trying everything I can think of, I couldn't flash any other ROMs now, including GalaxyTask, Overcome, AOKP CM9, except the stock Honeycomb sans TouchWiz ROM, and of course PhantomTask. I am pretty sure PhantomTask is the last ROM I've flashed until this problem comes up.
I have made sure that I have done a full clean wipe every time before I flash any of them, wipe data -> cache -> dalvik cache, I even format /system partition, but still none of them works. They always get stuck at boot screen, unless the either one of the two ROMs I've mentioned, stock or PhantomTask.
I am sure that my downloads are complete too, as I've checked MD5 for each of them.
So I really don't know what to do now, any ideas?
I'd really want to test out AOKP
Define stuck. It's not uncommon to have to sit for 5 or even 10 minutes at that first boot. How long have you waited?
Sent from my GT-P7510 using XDA App
Wrong section pal. Might want to post in Task's thread.
Sent from my Galaxy Nexus using XDA App
Just wait. It sometimes takes 15 minutes or so for my tab to boot up the first time.
thanks for the reply
It gets stuck at the Samsung Tab logo, and not proceed to the boot animation. I've tried waiting up to 30 minutes or more at one point, just leaving it there and do my own things. Though after that one time I'm not sure I've waiting that long.
I'll try again tonight and see how it goes.
@hbkmog I would have posted at Task thread if I could.
Have you tried with a newer version of ClockworkMod? Perhaps this one: ClockworkMod 5.0.2.7
thanks Maple Syrup, I have flashed that recovery yesterday, and I've tried flashing CM9 after that. I left it overnight to boot, it still didn't boot pass the logo, and the battery drained out.
I'll give it another try later.
ok I've tried everything I can, and still can't get this to work.
Then finally I've decided to try to unroot and restore everything to stock.
I've followed each and every step of this guide
http://forum.xda-developers.com/showthread.php?t=1474971
After everything is done, Odin is showing the pass sign, according to the video its suppose to reboot into Android, but weirdly its stuck at a black screen. So I unplugged it from the PC rebooted it by holding down power button. But now its stuck at the boot logo, and won't proceed, its been more than 10 mins.
I am still able to boot into download mode, but when I boot into recovery wanting to do a factory reset, it shows a black screen and nothing else.
any idea what's going on?
first post this everywhere. oh you're doing that already. :screwy:
follow the overcome recovery from the link given after one of your other posts or just look for the thread.
Sent from my GT-P7510 using one stinky finger.
thanks for the reply man, but yea kinda desperate here
I'll try it out and report back
It's all good. I sounded rude I think and not helpful really, but I had just replied to your other post exactly like this one. I understand the desperation cause I've "been there done that"
Hope you get'er going.
Sent from my GT-P7510 using one stinky finger.
OMG
Benzoman said:
first post this everywhere. oh you're doing that already. :screwy:
follow the overcome recovery from the link given after one of your other posts or just look for the thread.
Sent from my GT-P7510 using one stinky finger.
Click to expand...
Click to collapse
Finally got the time to do it this weekend and... OMG it worked!! THANKS MAN!! MILLION THANKS
j3nnning said:
Finally got the time to do it this weekend and... OMG it worked!! THANKS MAN!! MILLION THANKS
Click to expand...
Click to collapse
Thank you! As I seem to be saying a lot lately, it's success posts like this that keep us trying to help in the first place. Makes us feel good to know we helped.
Sorry again for the rude first post. I think I was extra grumpy that day. Probably from some ungrateful user asking for help and then getting rude that the suggestion(s) didn't help them exactly like they wanted or even some days not fast enough for them. Funny how sometimes people trying to help have things to do other than sit and work on someones problem 24/7. not directed towards you.
Glad to hear you got it going.
Sent from my GT-P7510 using XDA Premium HD app
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
http://forum.xda-developers.com/showthread.php?t=1461337
ajt167 said:
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
Click to expand...
Click to collapse
I can fix your phone remotely do you have teamviewer?
Go download and install teamviewer and pm me your id and password and ill fix it.
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
K3VlN said:
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
Click to expand...
Click to collapse
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
You need to flash CWM5 for correct conversions
Sent from my SPH-D700 using Tapatalk
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Yep yep I've done this quite a few times now
My record for unbricking flashing to stock and rerooting and restoring a backup is like 10 minutes xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Its not bricked if it turns on! And you don't have to wipe 3 times... only 1 time each on all 3 things! Update your cwm and try to flash again, if that doesn't work odin to stock and start over... this time don't use an old version of cwm use the newest (5.0.2.7)
Sent from my SPH-D700 using Tapatalk
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
here is a link for qbking77 with a tutorial for ODINing back to stock...
http://www.youtube.com/watch?v=YQ2g6J1JgjU
the links for the software are under the video.
hope this helps.
bigron is da man and can help u, but if you want to play more with ur phone, BigRon might be with one of his "Honies" and you can't disturb da playa.
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I always heard it was good to know that there is a way to fix it thanks for the info
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
http://files.devphone.org/epic4g/SPH-D700-EC05-8gb-REL.tar
MD5SUM: 4ea4dfea809c1a6d59b9fccf9e939f35
That's the file you'll have to use with Odin to flash your phone back to stock 2.2. That file will go in the PDA slot of Odin. Don't bother with a PIT or repartitioning (probably not needed in your case).
Once you boot with stock 2.2, let the phone OTA to EI22 and EL30 to get to stock gingerbread with the updated modem. From there you can start the root/rom flash process again.
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm just glad no one has suggested the good o'l magical restore button anymore xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Thank you all for your help. Man, you guys are awesome! I'm going to try to reload stock using Odin this evening. If I'm unable to do this, I'm going to get Biggoron to help me via teamviewer.
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
ajt167 said:
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
Click to expand...
Click to collapse
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
wscott9903 said:
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
Click to expand...
Click to collapse
Welcome to the Sponge club and also the halls of Asgard to visit Odin or heimdall.
It worked!
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
ajt167 said:
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
Click to expand...
Click to collapse
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
luna_c666 said:
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
Click to expand...
Click to collapse
I have a good cable that I'm planning on using, I just left it at work last night. I'll read up on those types of ROMs. Thank you.
My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .
I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.
upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app
tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:
Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app
slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.
First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work
i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...
My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility
About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.