Hey guys... I am not new to using odin, flashing roms, pushing stuff to sd, etc, but I have ran into a problem recently that I can't seem to fix. It doesn't matter what rom I flash and use, I keep getting random shutdowns on my phone, especially after it gets below 20%. Other people using the same roms do not have this trouble.
That being said, most of the time, I odin back to Froyo before flashing a new rom (and yes, I wait about 15 minutes without touching the phone after each flash, do factory reset/wipe, wipe dalvic cache, fix permissions, etc). The Froyo files I use are Eugene's 512.pit file and the JK2.tar file. I finally got to wondering if there was more of a problem with the base files I'm using, so then flashed the listed files using odin (which is what I use to "start fresh" before each new rom) and found out that I am still getting random shutdowns!
I really am not sure what to do... do I need to completely blow everything away (as in doing something that will erase everything - music, photos, etc. which normally doesn't happen), unroot, re-root, and take it from there? Am I using old files that are known not to work so well anymore? Any suggestions?
Try fixing permissions in CWM the wipe dalvac and cache. If that doesn't work try factory reset
Sent from my SGH-T959 using xda premium
i have done all that you listed... do it every time after i flash a new rom but it still shuts down...
When is the last time you calibrated the battery?
I remember someone else having g this issue and its related to the battery percentage. As if the phone thinks its at dead battery when its not.
Sent from my SGH-T959 using xda premium
well, i don't do the full calibration i don't think... what i do is: after i flash a new rom, i charge it all the way up, plug and unplug it a few times to make sure it stays at 100%, then (while it is still plugged in) i reboot into recovery and wipe the battery stats. most of the time that's it, i don't let it charge all the way to 0% and then charge all the way back up again.
but i don't think that's the problem because even when the battery says it is still at 50-75% i still have the problem... albeit not as often.
i'm thinking of usin odin to go back to the un-rooted stock and see if that fixes it... from there i can re-root and flash the rom i want.
Let me know if that works, im interested to see if it works! Good luck.
Sent from my SGH-T959 using xda premium
don't if it will help, but try odening back to jfd. I never odin back to froyo always jfd when I want a fresh start. Try running jfd and see if it still reboots. If so then your phone is defective. Also a while back I remember this happening on simply honey and other gb roms. I forgot what the fix was though.
thanks guys... am in the process of going back to jfd now, sure hope that works! i followed sn15's guide on this and actually reformatted both internal and external card as well to wipe everything. i will keep you all posted if it works...
Could it be a hardware issue? How 'bout on stock, does it still do it? Do you have a case on the phone that it might be pushing the power button down that its causing a forced shutdown? Is the power button getting stuck somehow? Have you tried cleaning the hell out of the contacts (battery & phone) and made sure that the contacts are in fact making a good contact? Luck homie.
Yeah definitely give JFD a shot. Root and reflash. I only really ever use Eugene's JK2 if my partitions get mess up or something. If it's still doing it after that then it could be a hardware issue like someone else said.
just wanted to give an update...
after i flashed JFD my phone was still randomly shutting down some, so i decided to give the battery a shot (as was mentioned above) just to see if that was indeed the issue. i switched batteries from the extended battery i was using back to the stock battery. i reconditioned it in JFD following s15n's advise. i have not had any more issues after this! i believe this worked... thanks for all the advise and help.
Related
UPDATED: FOUND A FIX! IF THIS WONT WORK I HAVE ANOTHER METHOD BUT ITS QUITE RISKY.
Please rate my thread if it helped
{Disregard my posts asking for help}
This guide is exactly what I did and it was very successful. Please don't blame me if it doesn't work. Keep in mind I did attempt every other option I could think of and this worked. I am not at fault if something goes wrong.
Begin by flashing to stock 2.1 through ODIN and make sure you repartition. Root the stock ROM so you can flash. Then install the latest Froyo by eugene373(you can try a JI6 ROM if you prefer). Now make sure to use a one click root method to re-root (or method of choice).
Download ROM Manager then install clockwork and reboot into it. Do a simple reboot back into your phone from clockwork. Now reboot your phone normally from Froyo ROM. Yes, it is a lot of rebooting, I know!
From here on, the USB saying its on while not plugged in should be fixed - hopefully! The new ROM seems to fix it because the USB settings are a little different..
After is where I think solved the USB problem when the phone isnt booted. Ok, now this is easy. Get back into clockwork, do the following: "Advanced-> Wipe Battery Stats" choose Yes of course. Then just reboot while plugged into USB so phone starts.
It "SHOULD" be fixed at this point!
Unplug from USB and shutdown completely. Now try to start phone without getting the boot looping battery icon. Reboot again to assure this worked for you. If it boots, jump up and down and hope it never happens again. Pull battery a couple times if necessary. This may help if the above failed.
When all is fixed you can install any ROM you wish granted you flash a 2.1 kernel if your not installing another Froyo ROM. Please make sure you understand this.
I only wrote this to help those who have encountered this nasty issue. I really hope it works for you. It is really worth a shot!
If anything was misunderstood, feel free to ask and I will do what I can to help. Ill respond as soon as I get the time.
I think I will make the guide a new thread if its successful. I need feedback. I will also add all download links and fix it up.
Sent from my GT-I9000 using XDA App which made it very difficult to type all of this!
*****FIXED*****
Hi.. I have the same problem. Can you please tell me how you made the USB mode off when the phone is on?
I turned off USB debugging and changed the settings to "Ask on connection" then restart the phone when plugged into your computer.
Sent from my GT-I9000 using XDA App
I also have the same problem... For me going to "Ask on connection" also helped - but USB does not work at all, the connections sign disappears when I plug in USB.
Additionally, I (mostly) could not boot the phone without having USB plugged in.
Yea its horrible having to boot while charging.
Sent from my GT-I9000 using XDA App
Try either flashing a rom with the JI6 update built in or using odin to flash the JI6 update. I talked with tech support and they said the "fix" was supposed to come in the update but if you are like me you didn't get teh update because you are on a third party rom. I found bionix 1.9.1 had the JI6 update in it and flashed it on a list ditch effort before i crushed the phone in frustration and since then i have been free of the USB annoyance. If that doesn't work though, it is a "known defect" and TMO wil replace the phone. You can also just go that route too if you don't want to try flashing all the rom's.
In my case this issue appeared at first after updating... actually thus I am trying to get completely back to stock, trying to fix it that way.
Sending the phone to T-Mobile is difficult since I bought it used on Ebay, isn't it? Or is it realistic to get some help from them?
Sent from my SGH-T959 using XDA App
*EDITED TO REDUCE CLUTTER*
Sent from my GT-I9000 using XDA App
First post now contains my fix. Just another edit to remove my old question.
Sent from my GT-I9000 using XDA App
I finally fixed the issue. After installing Eugenes Froyo port it fixed the USB from staying mounted when the phone is running. Then to fix the problem when the phone is off I booted into clockwork and wiped battery stats. After a reboot or two it was fixed. Dont know if this will work for everyone...post results if you try this. Thanks!
*Detailed guide in first post*
Sent from my GT-I9000 using XDA App
Hi,
Does the Eugene froyo have the JI6 update?
Thanks
B
It uses the JI6 modem but thats about it. You could flash it but in order to restore your JI6 ROM you must also reflash the 2.1 kernel. Read up on it. Its worth it to get rid of the USB problem. Perhaps you could flash Stock through ODIN then update back to JI6 through Kies Mini instead. That way I think would get you back to where you want to be without kernel issues? It may be worth a shot cause the USB problem makes the phone so horrible. Make sure to do a backup of everything you want with Titanium and save any files you want to external SD. Make sure you wipe everything if you do install Froyo cause that is how I did the process. I hope it works for you if you try. Post any questions...
Sent from my GT-I9000 using XDA App
Thanks for the advice!
I will flash the Bionix-Mod, that also has another kernel I think. Yeah and I gonna take care with Voodoo
Updated w/ Solution and hopefully a working fix for others.
It happened to me, but after I flash back to tmobile stock via odin, root, rom manager and flash to bionix final via clockwork(read instalation guide) it's gone.
Sent from my SGH-T959 using XDA App
Yea I suppose any JI6 ROM would work instead of froyo but it wasnt that easy for me. This guide is for who cant make anything else work.
Sent from my GT-I9000 using XDA App
@deez1234
so can you share with us now your vibrant running smothly, power on off without connect usb cable and charger ?
i've same problem, when i turn on phone not powering just show rounds (cercles) turn of (like blinking)
but when i connect usb cable phone show charging so now i press power button, phone turn on,
if i remove usb cable from phone, but when phone fully loaded on desktop show USB IS CONNECTED,
i've spend 3 days for searching solution of my problem but still not luck,
i've follow all your posted procedure, i've flashed successfully froyo also have install rom manager and clockwork but when i try to rebot my phone by rom manager its not work at all, just ask to me wana restart in recovery, but phone not restart, i think rom manager and clockwork not working on 2.2
please suggest me what is need to do next ?
NOTE: my vibrant is brand new just received before 5-6 days, i'm out side of usa that way not able to ask warranty or something
This guide worked perfectly for me. I tried it without partitioning in Odin first (just for a test) and it did not fix it. I then re-Odin'd the phone (following directions with a partition) and it has worked perfectly. I did not reflash a Froyo ROM, I just reflashed Bionox 1.9 and all is well.
Thanks for the fix
I'm glad I could help. And @Ja, are you making sure your rooted cause both ROM manager and clockwork works perfect on 2.2. You can try a JI6 ROM in place of froyo and see if it helps. And yes my Vibrant is as good as new.
Sent from my SGH-T959 using XDA App
Okay so my phone decided to do a force close on everything that i tried to do so I turned it off and tried to turn it back on again but all i was getting was the galaxy screen flash up and then it would turn black.
I flashed with Odin 3 times now and it says that it was successfull but when i go to turn the phone on it reboots and says that the data wipe has failed and then continues to flash the galaxy screen and then black. Can someone please help. I am a noob and haven't done anything but flash my phone.
The answers you are going to get are to odin back to stock, however ive had this problem and to get past it I had to do a factory wipe all data in the recovery menu then it booted. You lose all data. Before you do that try cycling the phone through restarts with battery pulls, I had another issue where doing this kicked me into normal boot after about 18 tries. I'm no expert but this is how I got fixed. Mine was a busy box issue it was never installed right
Sent from my SGH-T959 using XDA App
yeah, i agree w/ kcp about the battery pull... I would try this to see if you can get your system up and running, so that way you can dl Titatium Backup and Rom Manager. I had a problem on mine that would not let me reinstall packages and then it would never leave recovery, but after i pulled the battery, rebooted, and downloaded rom manager, i found that it was the same issue as kcp (busy box had to be updated). I don't understand why, after you re-flashed the Rom w/ odin it is not working.... did you flash 2.1 or 2.2? Remember, after you flash with odin you need to wipe data and chached memory, then reboot (maybe a battery pull). Try to give more info about exactly how you flashed w/ odin.
Also my titanium says it downloads busy box but doesn't had to go get it from the market and put it in the x bin you might want to do the same when it boots to be safe.
Sent from my SGH-T959 using XDA App
in_dmand said:
yeah, i agree w/ kcp about the battery pull... I would try this to see if you can get your system up and running, so that way you can dl Titatium Backup and Rom Manager. I had a problem on mine that would not let me reinstall packages and then it would never leave recovery, but after i pulled the battery, rebooted, and downloaded rom manager, i found that it was the same issue as kcp (busy box had to be updated). I don't understand why, after you re-flashed the Rom w/ odin it is not working.... did you flash 2.1 or 2.2? Remember, after you flash with odin you need to wipe data and chached memory, then reboot (maybe a battery pull). Try to give more info about exactly how you flashed w/ odin.
Click to expand...
Click to collapse
How do i know if i flashed with 2.1 or 2.2? How do you wipe data and cached memory? I turned it back on after i flashed and it showed that it was rebooting and wiped the cached memory but the data wipe failed.
also, my phone is not unlocked
Update: I flashed with 2.2 but I did not know that it was for tmobile. I am with bell. Now i can't get it to go into download mode so that I can flash with the right rom. It also won't charge when plugged in. Am i going to have to just get a new phone?
anything on this yet? mine is cycling aswell and cant get it into DL mode ;(
I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Doesn't really sound like anything you did would brick the phone - even though the screen doesnt come on, does your computer recognize it when you plug it in?
Yeah I agree. Nothing in those course of events would point to bricking your phone.
I am so sorry for your loss.
btw did you try pulling the battery for a few minutes then trying to power it on?
The phone is bricked. Same thing haopened to me flashing the same rom. I wasnt the first and you wont be the last.
I really wish we could figure out why this is happening.
Sent from my SGH-T959 using XDA App
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
tooclose said:
I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
so you bricked your friends phone, not your own?? thats messed up... why did you wipe data before you flashed the rom?? lol is that a regulation? i never wipe my stuff until after i let the rom run for more than 10 mins. unless im told different.. besides i thought all of tw roms wipe so you didnt need to. lol correct me if im wrong
@jellette no my computer doesn't recognize it....I have a windows 7 pc...and the latest odin
@hazard99 yes I've tried several battery pulls with different options with 3button....no luck =(
@alkaloid i've flashed, rooted alot of phones going back to my pearl, sidekick, bb pearl, htc hd2, my own vibrant....maybe cuz they were all my phones and I took the time to be careful...haha
@kooksta yeah I know I feel bad...im letting him hold my hd2 til I can get a fix or just have it replaced...I usually do a backup and wipe before every flash never had a problem and I thought that was standard but not sure...
@krylon I was thinking the same thing ...when he tried to update it on odin with the froyo update it corrupting something...the devs on here do a great job!! Never before have ever had any problems!
Thinking back to it, the only thing I can think of is after I installed rom manager and flashed clockwork recovery and I booted into clockwork...I think the lettering was still blue? I think its my understanding that if its still blue the phone is not rooted, green lettering means rooted, and red means rooted with voodoo activated...correct me if i'm wrong. But I THINK the lettering was blue, but the phone has to be rooted to run rom manager right?
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
If anyone else has similiar experiences and/or fix....would love to hear them!
Sent from my SGH-T959 using XDA App
Like you said, the Rom would've done it for him regardless. It wasn't his fault he bricked his friends phone. Hopefully he told his friend the possible repercussions of modding his device however. Like Krylon said, its just a corruption caused by odin. Nothing he could've done differently to prevent it besides not modding the phone itself. Oh well, happens. Like Kyrlon said, warrenty replace it. Simple and done.
tooclose said:
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
@tooclose
off topic, i need a new jig (another one), can you send me the link in ebay where you bought that?
or anyone?
krylon360 said:
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
Click to expand...
Click to collapse
Wait, so if I was running Bionix V and wanted to flash a new rom, what would be the proper procedure? All these crashes from Odin is starting to scare me
I forget who the seller was but just do a search for vibrant jigs ...there's several sellers...good luck!
Just got the jig...its a no go =(
Sent from my SGH-T959 using XDA App
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Speaking of the PBL, how can I verify that mine is not corrupt? I flashed bionix V twice and assume the SBL is intact, but I still would like to verify that both are working correctly.
bartek25 said:
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Click to expand...
Click to collapse
I think you should explain it just in case it happens to others later on or make a seperate post on how to please
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
method of unbricking
bartek25: Would love to know your magic to bring the dead phone back to life. Mine is completely dead acting like the battery is dead even though it is fully charged and I've read and tried ever method I can find.
Any suggestions other than sending it in Samsung or the carrier in getting a hard bricked phone fixed? Anyone with a jtag interface who likes to make a few extra bucks on the side?
I'm a noob to all of this custom rom business but earlier today I installed Bionix, everything went great and was a lot easier to do than I had anticipated.
Anyways I'm just wondering, I did not have to use ODIN, really all I did was root, install rom manager, cwr, create nandroid and titanium backups, transfer bionix zip to internal dir and then bootup in cwr.
I guess my question is, why was ODIN necessary for the topic poster?
So I'm a noob to this whole rom thing and i think that i am in over my head...
first i rooted using GingerBreak-v1.20.apk and not knowing what i was doing deleted some of the bloat (games). When I tried to do the bell gingerbread ota update i got the error. I tried to re install them but it didn't work.
So i decided to try to rom my phone.
First i unlocked using the Bell_Ihop from http://forum.xda-developers.com/showthread.php?t=1136261 which worked...
I then flashed a rom from ROM manager. It was ninja v0.3.4 (i think). It worked but i got a grey ? battery error... I didnt realize and my battery ran down. And while i cant be 100% sure yet i dont think my battery works any more (is that possible)
so i posted a Q on the forums and got an answer here http://forum.xda-developers.com/showthread.php?t=1251529
I borrowed a battery which let me turn on my phone but was still unknown...
I followed his answer and did a wipe. I decided i wanted alien so i flashed tanfer cmw recovery and flashed alien using that.
and I got stuck on the boot screen
so i did a wipe again and tried to reboot to bell stock2.2.2 and got an error so i did a reboot and i guess that the stock managed to reinstall the regular recovery..
and im still stuck on the reboot page...
so my question is I cant do anything cuz my battery doesnt work so i cant reflash cmw and I dont know anyone with an atrix to get a battery from (im pretty sure i outstayed my welcome in my local bell store, thats where i did all this)
Is there anyone in toronto that would fix this for me, i need this phone and i would pay for someone to do it for me cuz i cant do anything myself!! (And I'm a noob)
Thanks in advace...
first off, use this to charge your battery: http://www.youtube.com/watch?v=BDtv7qKf8tQ
after you get a charge on your battery again, go into CWM and clear Data/Cache, and then go into Advanced Options and clear your Dalvik Cache.
after that, flash any ROM and try to boot up. if you get stuck into a bootloop, post back here and let us know.
you'll need to flash CWM again using Fastboot, i suggest Romracer's which can be found here: http://forum.xda-developers.com/showthread.php?t=1204500
Thanks I will try this but I have a few questions
1. I did all this (the wipes and the flash) with tenfars, will this make a diff?
2. What tegrapart am I? (remember I cant boot into my phone to check through terminal emulator)
3. Now that I have been traumatized i just wanted to ask, on the alien site he says that it will take an unbearably long time to boot, how long should I expect to wait?
thanks for putting up with my "noobyness"
I don't know how to find your tegra part but it might take up to a few minutes the first time you boot. You'll know if you get a boot loop or not, the whole animation will do a major skip and start back from the start
And I know some people have problems with tenfar's. romracer's is just superior in my opinion.
Sent from my MB860 using xda premium
will i get messed up if i use the wrong tegra?
mypcool said:
will i get messed up if i use the wrong tegra?
Click to expand...
Click to collapse
You shouldn't, as long as all you're doing is flashing ROMs with cwm. All else fails you can just flash a different one.
Sent from my MB860 using xda premium
I tried the battery trick and it caused the usb jacks on my computer to stop working... I also tried to charge with a different phone and it didnt work. I called Motorola and am getting a new battery...
Has anyone ever had this happen that a battery should stop getting a charge at all after a flash?
Buy a cheap wall charger and battery from ebay.
Sent from my MB860 using xda premium
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app