A couple of weeks ago I flashed the midNIGHT ROM gingerbread, which worked great at first. As time went on I was having more FCs and 3G issues. Then the phone would randomly become unresponsive, and I would have to pull the battery to restart. Eventually it stopped booting all together. The phone would get to the samsung screen, the bottom buttons would flash once, then stay on.
I have tried to Odin back to EC05 many times, with many cables, and I still get the same freeze at the samsung screen. Surprisingly after flashing EF02, the phone finishes booting, but then the touchscreen is unresponsive (though the buttons work). After flashing with CWM, if I try to boot into recovery the phone freezes at the samsung screen again, and the only way I can boot it up again is to odin.
Any ideas as to what is going on, or methods I could use to debug this issue?
keymakerOvvvv said:
A couple of weeks ago I flashed the midNIGHT ROM gingerbread, which worked great at first. As time went on I was having more FCs and 3G issues. Then the phone would randomly become unresponsive, and I would have to pull the battery to restart. Eventually it stopped booting all together. The phone would get to the samsung screen, the bottom buttons would flash once, then stay on.
I have tried to Odin back to EC05 many times, with many cables, and I still get the same freeze at the samsung screen. Surprisingly after flashing EF02, the phone finishes booting, but then the touchscreen is unresponsive (though the buttons work). After flashing with CWM, if I try to boot into recovery the phone freezes at the samsung screen again, and the only way I can boot it up again is to odin.
Any ideas as to what is going on, or methods I could use to debug this issue?
Click to expand...
Click to collapse
Have you tried selecting repartition and using the Victory pit file when Odin'ing?
kennyglass123 said:
Have you tried selecting repartition and using the Victory pit file when Odin'ing?
Click to expand...
Click to collapse
I've tried both with and without the pit file, with no success.
You can't use odin without the pit file to flash anything. Re download pit and tar and try again. Also try a different usb cable.
jbadboy2007 said:
You can't use odin without the pit file to flash anything. Re download pit and tar and try again. Also try a different usb cable.
Click to expand...
Click to collapse
I'll try downloading again. So far I have tried flashing with a stock cable, palm pre cable, and a blackberry cable.
Try flashing back to an older version of the ROM. DK17 or something. Wait, DK17. crap to many things going on at work today. Anyway, look for one of the odler official releases and ODIN back to that. See if that helps.
If not then at least put an older stock on there and then take it into a Sprint store.
IAmSixNine said:
Try flashing back to an older version of the ROM. DK17 or something. Wait, DK17. crap to many things going on at work today. Anyway, look for one of the odler official releases and ODIN back to that. See if that helps.
If not then at least put an older stock on there and then take it into a Sprint store.
Click to expand...
Click to collapse
Thanks for the idea. I just tried EB13, DK23, and DK17, along with a fresh download of EC05, and a few extended/pre-rooted version for good measure. With all I get the same hanging on the samsung screen.
Looks like I might have to flash EC05 and take it to a sprint store...
jbadboy2007 said:
You can't use odin without the pit file to flash anything. Re download pit and tar and try again. Also try a different usb cable.
Click to expand...
Click to collapse
Not true I have always flashed with Odin without the pit file and never had issues
Sent from my Epic 4gizzle using XDA premium App
This is true. The PIT file is a partition table. It's specifically for if you check the repartition box so it knows how to "divvy" up the disk space for the filesystem.
Esteway.619 said:
Not true I have always flashed with Odin without the pit file and never had issues
Sent from my Epic 4gizzle using XDA premium App
Click to expand...
Click to collapse
Related
hi all, so i flashed the new SFR today, i have odined and flashed and rooted several times so i have a good background with this stuff..
I decided to odin the EE03 modem.
odin hung on modem.bin, so i pulled the battery and i was going to try again. I cant start my phone now. it gives this image of a phone then an "!" then the computer.
i am now trying to odin the full ec05 tar to start over, and its not working. it hangs on factoryfs.rfs and the screen turns a single color. the first time it was red, then next try was blue, next try was grey, next try was totally black.
PLEASE HELP!
DrKaotica said:
hi all, so i flashed the new SFR today, i have odined and flashed and rooted several times so i have a good background with this stuff..
I decided to odin the EE03 modem.
odin hung on modem.bin, so i pulled the battery and i was going to try again. I cant start my phone now. it gives this image of a phone then an "!" then the computer.
i am now trying to odin the full ec05 tar to start over, and its not working. it hangs on factoryfs.rfs and the screen turns a single color. the first time it was red, then next try was blue, next try was grey, next try was totally black.
PLEASE HELP!
Click to expand...
Click to collapse
Sounds like you are sponged. Try a different cable, try a different port. Try checking repartition and put the Victory pit in. As long as you can get to download mode you are not bricked. There is hope. Have you used that tar before? Does it have an .md5 extension? If so remove it. You may try to redownload the tar. What version of Odin are you using?
kennyglass123 said:
Sounds like you are sponged. Try a different cable, try a different port. Try checking repartition and put the Victory pit in. As long as you can get to download mode you are not bricked. There is hope. Have you used that tar before? Does it have an .md5 extension? If so remove it. You may try to redownload the tar. What version of Odin are you using?
Click to expand...
Click to collapse
i am afraid you might be right. my other two cables are not readily available, but i used the one i ALWAYS have used to odin. my main comp is a mac and restored an older XP laptop for the specific purpose of using odin, it only has one USB port (weird I know), but again, i've always used this, probably odined my phone atleast 15 times since i got it. I did check repartition every time i tried. I always use the victory pit. yeah i have several TARs saved on that computer, DI18, EB13, EC05, again i have used all these TARs before as they are old saves from when that respective build was current (i tried them all). I am not at my computer but its odin v1.61? does that sound right, it should be the current version.
I talked to my sprint rep friend, they have a different software package they use that is used like odin would be, so i might stop in and try that. beyond that i have never seen anything like this before.
it hangs on factoryfs.rfs for a few minutes (not unusual especially when coming from a EXT4 rom) then the screen on the phone turns a random solid color. Very, VERY uncool.
i am leaving the battery out to discharge anything left in the phone. I will probably try again tomorrow after work.
anyone else experienced this before??
Try the (non?)-imagionary button that I have.
Sent from my SPH-D700 using Tapatalk
brick phone
Hay dude search video on YouTube make jig or buy at some site that work if you brick your phone if you phone not get in download mode just contact cable with computer and open Odin if port found just run original rom. It sutbe work I did my many time
badboysllll said:
Hay dude search video on YouTube make jig or buy at some site that work if you brick your phone if you phone not get in download mode just contact cable with computer and open Odin if port found just run original rom. It sutbe work I did my many time
Click to expand...
Click to collapse
He is experienced. He odin-bricked.
Did the news get around about a guy named butcher pete?
marcusant said:
He is experienced. He odin-bricked.
Did the news get around about a guy named butcher pete?
Click to expand...
Click to collapse
no who is that?
This happened to me, and I tried it with a different computer... my screen was going Green and getting stuck on factoryfs.rfs
You can also try setting up Heimdall. It iis more robust than Odin.
http://www.glassechidna.com.au/products/heimdall/
marcusant said:
Did the news get around about a guy named butcher pete?
Click to expand...
Click to collapse
DrKaotica said:
no who is that?
Click to expand...
Click to collapse
Ol' Pete just flew in to that tooowwn, he was choppin up all the women's meat.
I had that happen to me once. That image is the download mode thinking it isn't plugged int. I just power drained it (holding down the power key with the battery out) and eventually got back into a connected download mode after about 3 or 4 min.
FIXED
well guys i left the battery out of my phone today to fully "uncharge" any extra electricity running around the phone.
just just got home from work and successfully odined with the battery left out of the phone.
remember i was always able to get the phone into DL mode, just that odin would not complete. so im FIXED! thank jeebus.
i was about to try this heimball, my question for that is when i was looking at screenies of the UI, there appears to be different slots for each partition of the phone? so how would one go about using this to flash ohh say.. the EC05 TAR i have sitting on my desktop
DrKaotica said:
well guys i left the battery out of my phone today to fully "uncharge" any extra electricity running around the phone.
just just got home from work and successfully odined with the battery left out of the phone.
remember i was always able to get the phone into DL mode, just that odin would not complete. so im FIXED! thank jeebus.
i was about to try this heimball, my question for that is when i was looking at screenies of the UI, there appears to be different slots for each partition of the phone? so how would one go about using this to flash ohh say.. the EC05 TAR i have sitting on my desktop
Click to expand...
Click to collapse
You have to use something like Winrar to pull the different sections out. Just learning this myself trying to Heimdall the EC05 modem in. I have to use winrar on the modem tar and pull out modem.bin.
kennyglass123 said:
You have to use something like Winrar to pull the different sections out. Just learning this myself trying to Heimdall the EC05 modem in. I have to use winrar on the modem tar and pull out modem.bin.
Click to expand...
Click to collapse
I have read that 7-zip is best when altering zips. Has to do with 7-zip's ability to auto-convert the file exts. Saves tons of time when dealing with alterations. Probably doesn't matter if you use Winrar if you are just deleting or moving files though.
Ok So Like Im Not Sure What Happend But Ever since i Flashed The Epic Kang Mtd Rom ive been having problems like out of no were it froze so i took out the battery and when i restarted it , When Restarted the Bottom 4 Buttons ,That Usually Turn on once and continue to boot animation, blinks twice and it stays there forever
I Have
-Odin It To Stock
-Used K0anne's method
-Used Samsung Updater
Mos of them didint work and when they did work it was only for a short amount of time so.... Help?
-Forgot to mention that sometimes when im odin'inng it or using the updater it stops in the middle of the process and the screen turns one color
You have a bad cable your screen turning a solid color means its a bad flash/ connection try a blackberry cable and odin back to stock and reroot and flash the cm7 and it should work.
Sent from my OG Epic
Ok So I did That And During The Odin It Didint stop (big help) but when it restarted it went to the samsung logo , The Bottom main 4 buttons blinked twice ,&& it stayed there
Biggoron said:
You have a bad cable your screen turning a solid color means its a bad flash/ connection try a blackberry cable and odin back to stock and reroot and flash the cm7 and it should work.
Sent from my OG Epic
Click to expand...
Click to collapse
Ok So Now i got to cwm i flashed the new cwm ,Flashed the Epic Kang, && rebooted it and it just keeps sending me to cwm but it takes like a couple of minutes to do so
I'm stumped it should have booted did you check repartion when you odin back to stock? If not that could be why its not booting into the bml partition
Sent from my OG Epic
When you odin are you checking repartition since you went over to mtd?
Sent from my SPH-D700 using Tapatalk
Bump hopefully some one smarter can help this guy I tried for 2 hours.... anyways he odined back to stock properly but it just sticks at the sammy screen.
Sent from my OG Epic
MichaelCampos said:
Ok So Now i got to cwm i flashed the new cwm ,Flashed the Epic Kang, && rebooted it and it just keeps sending me to cwm but it takes like a couple of minutes to do so
Click to expand...
Click to collapse
Are you trying to get back on CM7 or Odin to stock? The MTD conversion takes a couple of boots I heard. I imagine the first converted you to MTD and now the second should flash the ROM. Never did it so just going by what I read.
If you are trying to get back to EC05 with Odin then check repartition and reboot, make sure to use the included Victoryxxx.PIT, take out the battery and sd card, use a good cable and with Odin up plug phone into USB port then quickly put it into download mode. The computer will supply the power. It will not reboot at the end until you put the battery in.
kennyglass123 said:
Are you trying to get back on CM7 or Odin to stock? The MTD conversion takes a couple of boots I heard. I imagine the first converted you to MTD and now the second should flash the ROM. Never did it so just going by what I read.
If you are trying to get back to EC05 with Odin then check repartition and reboot, make sure to use the included Victoryxxx.PIT, take out the battery and sd card, use a good cable and with Odin up plug phone into USB port then quickly put it into download mode. The computer will supply the power. It will not reboot at the end until you put the battery in.
Click to expand...
Click to collapse
I've tried my hardest to get it to work it just won't. He odins back properly and it works but won't boot....
Sent from my OG Epic
Biggoron said:
I've tried my hardest to get it to work it just won't. He odins back properly and it works but won't boot....
Sent from my OG Epic
Click to expand...
Click to collapse
Sounds like a bad partition table. If he repartitions with the PIT and the battery out, plus uses the stock EC05 from here:
http://forum.xda-developers.com/showthread.php?t=1052813
He should be able to get it to boot.
kennyglass123 said:
Sounds like a bad partition table. If he repartitions with the PIT and the battery out, plus uses the stock EC05 from here:
http://forum.xda-developers.com/showthread.php?t=1052813
He should be able to get it to boot.
Click to expand...
Click to collapse
Should of had this earlier I got him to take it back to sprint I figured it was hardware related if he can't get a new phone then ill make sure to tell him.
Sent from my OG Epic
Nice job B. Don't forget to refer them to the thread on How to recover a semi-brick in Development. It will save you a lot of typing. I see you answering a lot of questions. Good for you! I try to let you handle it when you get the first answer in. Feel free to PM me whenever you need to. Thanks for the help.
Sent from my SPH-D700 using XDA App
Ok so this morning I get a notification on my phone to for a software upgrade, so i'm like ok cool. Had my WiFi hooked up and everything and then when I try to install the update it stayed frozen on the white update screen and didn't even start the process of downloading or installing anything. So I call t-mobile and they tell me to take the battery out of my phone and try to turn it back on, unfortunately now my phone is booting up and as soon as it hits the software update screen it shuts down and loops.
Master Reset does not work! TRUST ME!!! IT JUST KEEPS LOOPING
After finding out I should have never taken the battery out and trusting T-Mobile I was like damn, should have used kies, I downloaded but it since my phone is looping, kies will try to connect but my phone keeps connecting and disconnecting because it's boot-looping.
Basically T-Mobile broke my phone, and after talking to 10 dumbasses they are finally sending me a new phone, here the problem, i'm do not want to loose my files...
What can I do to fix this problem? I have many important calls to make and I don't feel like waiting for this one in the mail.
All help is appreciated, I bet you know more then the tech support monkeys
Are u rooted?
Sent from my SGH-T989 using Tapatalk 2
AJ26T said:
Are u rooted?
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Rooted? I don't know what that is or how to do that, I have a stalk white galaxy s 2
Stalk? Straight talk? You sure its the T989? If so, i don't think you can return it to T-mobile if you dont have a contract with them.
--Possible remedies:
Odin stock recovery and stock gb.
Husam2011 said:
Stalk? Straight talk? You sure its the T989? If so, i don't think you can return it to T-mobile if you dont have a contract with them.
--Possible remedies:
Odin stock recovery and stock gb.
Click to expand...
Click to collapse
Well I got it from T Mobile but I never done anything to my phone, just used it as is.
If you can get into download mode, ODIN to stock and then do the ICS update via Kies.
belly1026 said:
If you can get into download mode, ODIN to stock and then do the ICS update via Kies.
Click to expand...
Click to collapse
X2, there are very easy to follow instructions here in the T989 development section here on XDA.
Just follow the instructions and you should be fine. If you cannot get it into download mode, you will have to get a USB jig to force it into download mode.
Either way, your phone is not hard bricked
Sent from my Nexus S using xda premium
Can someone please link me to that then????
How do I use ODIN to stalk? I think i downloaded the right riles, I click on PDA, open up the file and click start and get this.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This happened to me a while back. With a. G2. Sometimes I wonder if tmobile technicians actually know what they're doing.
Sent from my SGH-T989 using xda premium
Restore phone via Kies if it will recognize your phone.
I don't know if this will work while you're boot looping but you can try.
1) Start the Kies program.
2) Under Tools at the top left go to Firmware Upgrade and Initilization and it will open up a pop up box asking you for the serial number and model number of your phone.
3) Take out the battery and look at serial number of your phone and model number (SGH-T989) and type it in the S/N and Model Name slots.
4) Put the battery back in and press both the up and down volume and insert the micro usb attached to your computer.
Hopefully Kies will do an emergency firmware recovery.
Questions go in the Q&A section
Try going into recovery mode and doing a factory reset, then try rebooting.
Hold the power button and both volume keys until the phone vibrates and the Samsung logo appears, then let go.
Only thing I can think of...
I have the same phone and i receved the update also. but my phone is rooted i set it for 6 hours and im unsure whats going to happen. What should i do? Should i let it update. or how can i stop it from doing so knowing im rooted?
tParsons, if you have a NON-STOCK recovery (e.g. Clockwork) on the phone then you WILL bootloop if you try to update. You must flash the stock recovery back before accepting the update or you're screwed.
The reason is that the first thing the new version does is try to run the update script, which fails as Clockwork doesn't know how to grok the stock update script process.
It's ok to be rooted (you'll lose root) but NOT ok to have a non-stock recovery when you get an update. Since the most-common way to get root on these devices is by using ODIN to put a non-stock recovery on the phone, accepting an update will almost-always result in a bootloop on a rooted phone unless you flash the stock recovery first.
I actually got the same notification today.
I literally JUST got my White SGS II myself yesterday afternoon (Father's Day Sale from T-Mobile) and spent last night loading it with all my APPS. I thought about going to ICS, but CoPilot Live does not work well (aka: Not at all) with ICS in my experience. That said, I delayed the update till tomorrow till I knew what the update was and popped over here.
Now I'm wondering what's going to happen when the update takes place tomorrow (I delayed it for 24 hours). Is my phone going to bootloop as well?
For the record, phone is completely stock. It's still running GB out the gate from T-Mobile (TouchWiz, Bloatware, and all) with the stock recovery, bootloader, everything. I haven't even had an opportunity to touch this phone yet. So I'm wondering if I'm going to get Bootlooping non-stop the moment it decides to force the update tomorrow.
CoPilot released a (free) update to CoPilot GPS and that version DOES work fine with ICS (I own it and use it)
If your recovery is NOT changed over (you DO NOT have Clockwork on the phone) the update should be ok. No promises, but I did it via KIES and all was good -- all I did was flash back to the stock recovery first.
Genesis3 said:
CoPilot released a (free) update to CoPilot GPS and that version DOES work fine with ICS (I own it and use it)
Click to expand...
Click to collapse
I am aware. It did not work for me on neither my gTablet (using a GPS Puck) nor my Motorola Xoom (both of which were running ICS). It did work for me under Honeycomb though. Apparently, I'm not the only one either. But that is a discussion for another topic. I merely mentioned it as an extraneous point.
Genesis3 said:
If your recovery is NOT changed over (you DO NOT have Clockwork on the phone) the update should be ok. No promises, but I did it via KIES and all was good -- all I did was flash back to the stock recovery first.
Click to expand...
Click to collapse
Well, the phone is (Currently) 2 days out the store from retail. I also carried over my Premium Handset Protection. Something screws up because of T-Mobile, they'll most certainly be replacing it.
Genesis3 said:
tParsons, if you have a NON-STOCK recovery (e.g. Clockwork) on the phone then you WILL bootloop if you try to update.
Click to expand...
Click to collapse
Hmm .. I've updated with Kies and Odin while I had CWM and never had a bootloop.
I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T
anchor_th said:
I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T
Click to expand...
Click to collapse
Do a factory restore and wipe then odin one click stock EL29 and start from scratch.
I can't do a factory restore. When I hold Vol up + power, it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
:edited: Didn't see your response to graydiggy
Redownload a complete one click, verify md5 and try putting the phone in download mode and attempting again. It's possible that your download was bad.
so is there nothing I can do?
By technicality, that is not a brick. You should be able to flash from that message. That was the case with the Samsung Captivate.
I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
thanks for the help but I think it's ****ed. something might have messed up in the filesystem and that's why ODIN gets stuck maybe.
anchor_th said:
I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
Click to expand...
Click to collapse
Ok, so I found a solution by sfhub that worked for someone from a while ago. Try using pc odin to flash each piece seperately. Modem, kernel, then rom..
Here's my ref:
See post #9 http://forum.xda-developers.com/showthread.php?t=1492771
I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.
anchor_th said:
I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.
Click to expand...
Click to collapse
Have you flashed all three pieces before trying to let the phone boot completely? Once you flash the first piece and it restarts, Just hold power+vol down and get back into download. Do that until you have all three segments flashed. Then try letting it boot.
I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\
anchor_th said:
I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\
Click to expand...
Click to collapse
Then there may be one more thread that might help if that's the case.
Kernel is only the zimage file. Hang on, let me find it.
:edit: Maybe this will help you. If not, maybe graydiggy or someone else has some ideas.
With this, you'll have to see if you can't flash a custom recovery. From the sound of it, it may not be helpful at all.
http://forum.xda-developers.com/showthread.php?t=1865102
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Yeah, I don't think there's a way to do that since I can't access ADB...
anchor_th said:
Yeah, I don't think there's a way to do that since I can't access ADB...
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.
anchor_th said:
I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.
Click to expand...
Click to collapse
They will probably know you borked it by trying to flash. If they can get to a recovery to see if you have flashed anything, you are screwed.
Do you by chance have a USB Download Mode JIG?
No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over
anchor_th said:
No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over
Click to expand...
Click to collapse
I have a theory... Give it a couple hours of plug in time without turning it on or trying to flash. Just give it like 3 hours and see if you can flash from there. You may have a battery that is low and it could be resulting in your problem of not being able to flash.
the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?
anchor_th said:
the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?
Click to expand...
Click to collapse
Just keep it completely powered off and use the normal wall charger.
Issue
1. Phone won’t boot beyond the Samsung Logo.
2. It won’t boot into recovery (download mode works).
3. Can flash rom using Odin but phone still won't boot.
Type of Phone
Type: AT&T Samsung Galaxy Note 2
Model: i317
Ownership: Bought in Nov 2012 brand new. Warranty is up but it is insured through AT&T.
History: Rooted and then un-rooted and returned to stock in January 2014.
Actions leading up to Issue
Updated to Samsung’s newest firmware Android 4.3 but didn’t like it. I rooted my phone and tried a custom rom but wasn’t happy. Un-rooted by flashing original stock rom via Odin 3.07. Worked great and I was back in business. But then the phone went through an update and never booted back up.
Detail
I’ve rooted all my other phones but never felt the need to root this one until I updated to Samsung’s new Android 4.3. I wasn’t happy with the decreased battery life and poor performance. So I used the method at http://forum.xda-developers.com/showthread.php?t=2004650 to root my phone using “root66_ATT_I317UCALJ2.tar.md5” with Odin 3.07 and it worked. I then tried a custom Cyanogen Mod rom but it still left something to be desired.
After more research I flashed the original stock rom “KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5” via Odin 3.07 and my phone worked beautifully, at least for a day. Then I started getting the AT&T update window for Android 4.3 and the only way to get rid of it was to pull my battery. It was happening so much that I couldn’t even make a phone call. Out of pure frustration I decided to accept the update.
After the update installed it rebooted and never made it past the Samsung logo. So I figured I would just go into recovery and perform a factory reset as well as wipe the cache. The problem here is that it won’t boot into recovery. Only download mode works. I’m also seeing a red LED which I’ve read is a sign of SDS.
I’ve tried re-flashing the original stock rom again. Every time I do I get the green “Pass” display but my phone still won’t boot. The binary count is now at 21 since I’ve tried flashing so many times. I’ve been working on this and researching for 3 weeks. I’ve never had an issue that I couldn’t resolve when it comes to any of my past phones but this is beyond my skill or understanding. I also tried Samsung keys but it says my device is not supported.
Short of digging a hole in my back yard and burying it, is there anything I can do to fix this?
(Note) My wife has the same phone and also didn’t like the update so I flashed the same original stock rom to her phone via Odin and it has been working just fine. Only difference is I never rooted hers. I should have gone that route with mine.
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
josh3josh3 said:
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
Click to expand...
Click to collapse
Here's the link to TWRP (you want the Odin link toward the bottom):
http://teamw.in/project/twrp2/124
Here's the direct link to the latest philz cwm (you want the md5 file):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
I prefer philz, but you will likely need TWRP to follow the dicksteele guide. You should also track down a CWM flashable recovery package for MH3 recovery to flash back should you need to return the phone for repairs. You can get this by following the i317 link in my sig.
If flashing this in Odin doesn't work that would tend to support the emmc fail scenario. (i.e. you flash it, Odin behaves as if it flashed ok, you power off, attempt to boot recovery with home-VolUp-power and it still doesn't boot). If it does boot recovery, you can try the guide as I mentioned before. Good luck!
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
josh3josh3 said:
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
Click to expand...
Click to collapse
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
So, there appear to be many people who see this update as a bad joke. Like me.
I had a thread a couple days ago about how to kill the notification from att
Without root. Nothing can be done as far as ive heard/seen. Im a bit confused
About needing a battery pull to remove pp note, I have been just reboot and it
Goes away until next data use/net access. When my 8 hrs is up I turn data on
(Data off as 8hrs expires) and immediately get note and then I hit home- get
another 8 hrs. Im sorry to hear they wore you down with the note- im going to
fight and resist for the duration. And keep stock. Its a game now!
R, john
qkster said:
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
Click to expand...
Click to collapse
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
josh3josh3 said:
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Click to expand...
Click to collapse
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
dicksteele said:
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
Click to expand...
Click to collapse
Have tried that many times with no luck. Wish it were that simple.
josh3josh3 said:
Have tried that many times with no luck. Wish it were that simple.
Click to expand...
Click to collapse
Have you tried this yet ?
http://forum.xda-developers.com/showpost.php?p=49826416&postcount=9
Zen Arcade said:
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
josh3josh3 said:
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
Click to expand...
Click to collapse
That would be the Thanks button by the Quote...
OUTSTANDING !!!
Glad you're back among the living.
This will get you back to 4.1.2
http://forum.xda-developers.com/showpost.php?p=49616718&postcount=2
EDIT:
I just did this and it worked perfectly .....
I'm actually doing that step right now also. I flashed back to stock testing the ATT update server.
EDIT #2:
At this step when the phone reboots the script will run. When it completes you want to boot to system. The next prompt will be do you want to install ROOT. If you do the swipe it will install ROOT, there is a DO NOT INSTALL button on the middle of the screen. Just a heads up, don't know if you are turning your phone back in or not now.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.
sgh-i317 EFS seems like its gone
could anybody help me out with my note 2. ive tried just about everything i can think of. im getting pretty desperate. i can get everything to work fine (recovery,download mode,) but something is keeping it from booting up to the main screen, it will just hand at the boot animation, or the att logo. in twrp it tells me failed to mount efs. ive looked around in the file folders and its like it got wiped out? im not sure how though. could that be why its not booting up?
any ideas??