So yesterday morning I went to turn on my phone, but nothing happened. It was on the charger all night so it should have been a full battery.
Here are my symptoms:
1) AC plugged in without battery - Phone's screen turns on for a second, turns off, and then repeats.
2) AC plugged in with battery - Phone will start to charge (has the loading symbol in the battery), but then turns off immediately. It cannot boot into recovery. It CAN boot into download mode, but my computer will not recognize it to restore the phone with odin.
Any ideas?
I don't have an official upgrade until October, but I'm going to call customer service to try and get them to bump the date up so I can get a new phone.
First possibility to suspect is a failed battery. If you know someone else with an s2, ask to borrow their battery temporarily to see if your phone will boot. Or perhaps go to an AT&T store to see if you can borrow a battery.
If it's not the battery, then the next step to try is to boot into download mode with the battery out of the phone to see if Odin will recognize the phone with the battery out. With the battery out of the phone and the USB cable plugged into the computer, hold down the vol down button while plugging the USB cable into the phone. The computer will supply the power. This assumes that you have the proper "Samsung USB driver for mobile phones" installed on your PC.
That's a start.
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
sfb14 said:
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
Click to expand...
Click to collapse
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
creepyncrawly said:
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
Click to expand...
Click to collapse
I just did. Still no boot.
sfb14 said:
I just did. Still no boot.
Click to expand...
Click to collapse
OK. Did the flash to stock succeed? In other words, you got a pass in odin?
Which version of SHOstock was installed, the latest? And which version of stock did you flash?
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
sfb14 said:
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
Click to expand...
Click to collapse
This is sounding a bit like nand read/write corruption, which is fixable. Try this:
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful and boots normally you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Will try that later. Thanks for your help!
Sent from my SAMSUNG-SGH-I337 using xda premium
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
sfb14 said:
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
Click to expand...
Click to collapse
Going through the exact same issue with my kids phone with the same results. Tried creepy's 6 steps, but still no luck.
I think it was caused by my kid killing the battery.
update: got it to boot into custom recovery, then reflashed ROM. It stills acts weird though. Very laggy.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t-usb-port-repair/
Sent from my SGH-I777 using xda app-developers app
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
jvick920 said:
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
creepyncrawly said:
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
Click to expand...
Click to collapse
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
jvick920 said:
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
Click to expand...
Click to collapse
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
creepyncrawly said:
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
Click to expand...
Click to collapse
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
jvick920 said:
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
Click to expand...
Click to collapse
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
creepyncrawly said:
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
Click to expand...
Click to collapse
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
jvick920 said:
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
Click to expand...
Click to collapse
I have never used Cyanogen Mod or any of the other AOSP firmware, and I don't know how the firmware would affect this issue, if at all. But I suspect there may be some link.
I think what you need to do is to flash back to stock firmware, or perhaps use one of the stock plus root packages, and then a custom kernel, and then reload CM 10.1. So try this:
Pull the battery and leave it out. Open Odin3 on the desktop and then while holding down the volume buttons, plug in the usb cable. See if the phone will boot into download mode this way, and if Odin will recognize it. If so, then go ahead and flash the stock of your choosing. I think if it were me, I would flash 4.0.4 UCLL6 plus root.
Related
I'm not one to ask many questions i usually just read everything and tinker until i fix it but this has me stumped.
I have a fascinate with MIUI on it currently it runs fine for the most part.
But When the battery runs out or it gets powered off it ends up in a boot loop after i change the battery or plug it in. (the screen flashed the battery icon for a second then goes black then flashes the battery icon)
I can temp fix it by ODIN'ing a recovery (usually CWM-recovery all i have tried a few others one for Cyanogen mtd , etc) and it will boot up fine and run perfect until i need to shut it down. then it loops again
I have done a ext4 format before loading miui.
when it is loaded and up and running if i plugg it in to a pc it connects and disconnects over and over.
any suggestions?
I was wondering if there was a possibility that i screwed up the samsung recovery and it isn't loading up the custom recovery unless i odin it each time?
Thanks in advance!
edit: i odin'd an old eclair stock rom and get the same thing
Dustin1980 said:
I'm not one to ask many questions i usually just read everything and tinker until i fix it but this has me stumped.
I have a fascinate with MIUI on it currently it runs fine for the most part.
But When the battery runs out or it gets powered off it ends up in a boot loop after i change the battery or plug it in. (the screen flashed the battery icon for a second then goes black then flashes the battery icon)
I can temp fix it by ODIN'ing a recovery (usually CWM-recovery all i have tried a few others one for Cyanogen mtd , etc) and it will boot up fine and run perfect until i need to shut it down. then it loops again
I have done a ext4 format before loading miui. any suggestions?
I was wondering if there was a possibility that i screwed up the samsung recovery and it isn't loading up the custom recovery unless i odin it each time?
Thanks in advance!
edit: i odin'd an old eclair stock rom and get the same thing
Click to expand...
Click to collapse
when you odin back to the stock rom did you put the atlas 2.2 pit file in the pit function of odin and make sure repartition is checkd?
I've had this happen a couple of times. Just hold vol up and power till you see samsung.
good day.
droidstyle said:
when you odin back to the stock rom did you put the atlas 2.2 pit file in the pit function of odin and make sure repartition is checkd?
Click to expand...
Click to collapse
yes. I used the atlas 2.2 file when i went back to stock. I have tried a few stock roms too.
chopper the dog said:
I've had this happen a couple of times. Just hold vol up and power till you see samsung.
good day.
Click to expand...
Click to collapse
How long should that take?
I pulled the battery and replaced it to start a loop.
Then I held volume up and the power button and nothing happened but the same loop?
Should i pull the battery and put it back that way?
I can't even get volup voldown power to work only vol down and power.
the vol up key does work when a rom is up and running
****now it just flashes the battery logo once and turns off unless you hold down the power***
I should know better than to attempt fixes when i'm not near a pc to undo it...
now i'm phoneless until 5pm...
oh well
odining a recovery got me back running but i still can't shutdown or remove the battery with out having to odin a recovery
Dustin1980 said:
odining a recovery got me back running but i still can't shutdown or remove the battery with out having to odin a recovery
Click to expand...
Click to collapse
edit* Thats a wierd one not sure what the issue is. Normally repartitioning will take care of issues like that.
droidstyle said:
edit* Thats a wierd one not sure what the issue is. Normally repartitioning will take care of issues like that.
Click to expand...
Click to collapse
Yeah I can wipe everything back to stock use it like normal just if the battey dies, i shut down, or the battery gets pulled i get a loop of the battery screen then black. i can't even do a power off charge on it( power off the phone and plug it in so you get the green battery charging screen)
battery draining strange
I also have noticed that the batteries have been draining in an odd manner. after i take it off the charger it will stay at 100% for a long time then drain very quickly.
Have you by chance tried another battery? Maybe it's starting to crap out on you??
I have a few batteries. One is brand new. I have the OEM that came with it, a replacement oem, and a generic.
None will allow me to power the phone off and boot it back up successfully. All show the battery charge screen for a second then go black.
use a download mode jig (301kohms between USB pins 4 and 5). If that does not work, then just say funk it and install the Fascinate UnBrickable Mod. UBM allows you to upload "Download Mode" to any kind of bricked device when it's powered off.
I can get into download mode holding down volume so it's not as if it is totally fubar it just doesn't like being powered off and back on.
Ed05 froyo official full odin tar
when i'm on a stock rom i can occasionally get into recovery after a shut don and get booted back up with a custom rom i can't with out odining another copy over top
usb issue too
I also have issues with a usb connection connecting and disconnecting repeatedly when i have any rom loaded
Dustin1980 said:
I also have issues with a usb connection connecting and disconnecting repeatedly when i have any rom loaded
Click to expand...
Click to collapse
You've got a bad cable.
I have a few cables. they all do that.
Sent from my SCH-I500 using XDA App
on the brightside my gps seems to be locking much much quicker!
OK, here the story. My SGS2 started acting up a few days ago, it thinks it's charging all the time now. I searched and found that this seems to be a common problem with the port, so I cleaned the contacts on the microUSB connector, but it's not helping. I decided today that I'll just take it in since it's still under warranty, and I'd like to do it after work today since I live almost an hour away from the AT&T Store near the hospital. Problem was, I'm running AOKP on it and I don't have access to a computer with Odin on it where I can restore it to stock. Then I find the thread that details how I can download the .tar file and flash on the phone with Mobile Odin. Seems to work great, but it goes into a bootloop afterwards. One member posted that he had the same problem, but it was solved by booting into recovery and doing a full wipe. Here's where I have a problem now.
I can only boot into Odin mode, and it gives me the choice where it's asking me if I'm sure I want to load a custom binary or cancel and reboot. When I click that I want to load the binary, I get to the Odin mode screen; it reads
Custom Binary Download: No
Current Binary: Samsung Official
Downloading...
Do not turn off target!!
That's it. If I reboot normal, it goes into bootloop. Otherwise, it sits there with the battery logo showing, whether it's plugged in or not.
I'm pretty sure when I get home tonight, I can plug it in and get something going on my desktop, but I'd like to hit up the store before I head home. Anyone got any ideas or suggestions?
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
Yup, and that's what comes up. I'm thinking it has something to do with the fact that the phone thinks it's plugged in. I guess I'll just have to plug it in my desktop when I get home and work on it from there. Worst case scenario is that I just take it to AT&T tomorrow as it is, tell them about the false charging problem, and when I tried to do factory reset to see if it would fix things, this is where it's stuck.
I can't believe I spent the first 30 years of my life without a cell phone and now I don't feel right if it won't work for a day or two.
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
drjim said:
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
Click to expand...
Click to collapse
need adb.
adb reboot recovery
Google
Update:
I actually managed to catch it when it didn't think it was plugged in and do full wipe. It worked after that, sorta. It didn't think it was plugged in all the time, but it was still real funky; like the power usage curve started high, had a sudden big drop, then went up from there. Plus, when it was off, it would flash between a grey battery with a circle and a green on, back and forth. And I couldn't power it on unless it was plugged in. Once I showed them that, AT&T gave me a new SGS2. It's rocking Shostock2 now, so problem solved.
I was flashing from MIUI 1.9 to MIUI ICS in CWM and all seemed well until upon boot it hung on the MIUI bootup screen. After waiting about 15 minutes I figured I would simply ODIN back to stock and try again as I normally do when I have a problem flashing. In ODIN however I was unable to make it past the boot.inf stage of the flashing. Stupidly I unplugged the usb cable mid flash and tried again, and again same result, it would hang at boot.inf. After trying a couple different stock ODIN files the phone will not turn on at all. Even if I pull the battery and connect the phone to the pc I cannot boot into download mode. When I connect to the wall charger the battery screen does not come on either.
Strangely if I press the power button on the phone with the phone connected to the pc, windows will make the sound of a usb device being connected, however, if I release the power button it makes the sound of a usb device being disconnected. ODIN does not seem to be recognizing my phone anymore since I haven't been able to boot into download mode.
I've bought a usb jib hoping this would solve the problem but it hasn't seemed to work. Maybe I'm doing something wrong.
Please someone help me get my phone up and running again. I've flashed numerous roms before and had trouble but nothing as serious as this.
Try reading up on Droidstyles Guide . Its in General section .
Sent from my SCH-I500 using xda app-developers app
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
iztel said:
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
Click to expand...
Click to collapse
Can you "3 finger" into recovery ?
Sent from my SCH-I500 using xda app-developers app
No, when I try to use the 3 buttons to boot into recovery the screen stays black.
Another strange thing it's doing is when I connect the phone to my Mac with the SD card in the phone the Mac will continuously popup a window that asks whether I want to connect the usb device to the Mac or my virtual machine. It flashes so fast I'm unable to click either option. If I connect the phone without the SD card in this menu never comes up but I'm still unable to boot into download mode.
Hmm....I've never heard this before...have you tried plugging phone charger in ( wall outlet ) and let it charge 8 full hours
Sent from my SCH-I500 using xda app-developers app
You say you bought " out of contract", from a private seller ? No warranty?
Sent from my SCH-I500 using xda app-developers app
I charged it from the wall charger overnight still no luck. Yeah, I bought it a year and a half ago used from ebay. I think it's really strange too. I've had plenty of hiccups flashing roms before but it's never been something ODIN couldn't fix and I'd at least be able to get into download mode.
I think you are going to have to use UnbrickableMod.
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
iztel said:
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
Click to expand...
Click to collapse
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Magickly said:
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Click to expand...
Click to collapse
I had the same issue. I think it had to do with the battery being too low. I think that ODIN could have a check in place to allow only to flash if the battery is not clos to low in case things go wrong. I had a second fully charged battery and when i read the above post, i changed the battery across and it set it to download and ODIN eventually detected it. Thanks for the help guys.
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
mvmacd said:
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
Click to expand...
Click to collapse
I think the problem is you used the wrong Devil... the latest is 1.6.1 and the older ones will not work with the new partition layout. Get it from http://rootaxbox.no-ip.org/derteufel/
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
netlagger said:
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
Click to expand...
Click to collapse
You are suggesting we leave the battery out while Odining? what good would that do?
mvmacd said:
You are suggesting we leave the battery out while Odining? what good would that do?
Click to expand...
Click to collapse
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
mezster said:
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Crawshayi said:
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Click to expand...
Click to collapse
how would the battery cause the phone to reboot?
I have never Odin'd without the battery. And I never had any problems
Verizon SGS3. This is my first Samsung, so I have no doubt that it was something I did - been running my OG Droid since it came out and I'm not very familiar with the Samsung setup.
I followed this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The forum won't let me post my question there, due to my low post count, so I put it here...
I used Odin to flash the image in the PDA field. Right after that, without checking to see if the phone was working properly, I used ADB to put CWM on there. The phone was turned on (not in Odin mode) when I pushed the recovery. Now I can't get the phone to turn even turn on, much less get into Odin mode to reflash....(yes, I've pulled the battery).
My computer recognizes when I plug my phone in (it give the "you plugged something in" tone), but it doesn't register in Windows explorer.
Any ideas...?
Not sure if this will be any help but..
I was flashing the same rom as you and my computer randomly blue screened in the middle of it and my phone wouldn't boot. I tried just flashing it again with odin right over it, but same problem.
I had to do a factory reset, flash the Samsung stock rom (which unrooted), I think I did another factory reset, and finally re flashed the root 66 rom. I also booted up the phone and did the initial setup before pushing recovery over with adb, but I'm not sure if that makes a difference.
Good Luck!
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
letinsh said:
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
Click to expand...
Click to collapse
Was your battery full/plenty of charge when you first flashed through ODIN? What happens when you try to turn it on? No luck with download mode? Are you getting any feedback whatsoever from holding the power button?
Which recovery did you download and flash? I ask because I did this same thing last night and had the same issue. I used the touch recovery (TWRP 2.2.0) from HERE but the direct download link is bad. It gets you the wrong recovery if you download it directly to push via ADB or terminal. You need this one HERE
I hope im wrong but it sounds like a brick. If you can get into download mode your fine.
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
letinsh said:
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
Click to expand...
Click to collapse
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
adb doesn't see the device, even though windows registers something as plugged in (tone thru speakers when plugged/unplugged)
mustbepbs said:
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
Click to expand...
Click to collapse
Tried this just now. No joy.
....can a mod please verify my account so I can post more often than every 5 minutes...it's very frustrating.
bump
letinsh said:
bump
Click to expand...
Click to collapse
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
mustbepbs said:
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
Click to expand...
Click to collapse
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
letinsh said:
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
Click to expand...
Click to collapse
Sorry, that's not entirely true. I followed those instructions but used the root66 image from this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The CWM file i used was from the [ROOT] [RECOVERY] SCH-i535 thread
After some searching, this same sort of brick seems to be happening when dudes are flashing roms coded for other carriers....but I've got an i535 and have only used i535 files....hmm.
Shot in the dark
This is really just a shot in the dark, but have you tried power,home and volume button?
-SmithTech- said:
This is really just a shot in the dark, but have you tried power,home and volume button?
Click to expand...
Click to collapse
Yes, both vol up and vol down. I've tried every iteration I can think of. I'm waiting to hear back from Josh @ MobileTechVideos to get me an address. I'll be driving out there to have him give it a crack at unbricking...
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
nosympathy said:
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
Click to expand...
Click to collapse
+1. Always make sure to verify MD5's before flashing anything, especially in our case. Hopefully you can get that fixed, OP. That's really bizarre.
Possible Fix
Curious.... when you you type ./adb devices does it list any devices there? (Windows its just adb device)
I have seen this happen on Samsung Vibrants and it sounds like your device has forgotten what the hardware keys actually do. If adb works, you can reboot to download it it doesn't a resistor can be built with a Micro usb end to trick the device into download mode. Some were made for the Vibrants and should be able to find them on the forums over there. I believe Team Whiskey built them
I literally tried everything with this phone. Was able to root, went to install siyah kernel from zip and now I get the samsung logo. I can boot into CWM recovery, but none of the functions work--just hangs on the hat. Any ideas are greatly appreciated. Thanks. I just want to flash it to stock and sell it on ebay. Loved this damn phone. I just upgraded to the S3.
keltaurn said:
I just want to flash it to stock...
Click to expand...
Click to collapse
Use creepyncrawly's guide:
http://forum.xda-developers.com/showthread.php?t=1313659
keltaurn said:
I literally tried everything with this phone. Was able to root, went to install siyah kernel from zip and now I get the samsung logo. I can boot into CWM recovery, but none of the functions work--just hangs on the hat. Any ideas are greatly appreciated. Thanks. I just want to flash it to stock and sell it on ebay. Loved this damn phone. I just upgraded to the S3.
Click to expand...
Click to collapse
Okay. I've read all your posts. You have not provided any information that would be useful to troubleshoot your issue. However, I can make a few guesses that could possibly help, and then you need to give us some details so we can help further.
1) You don't say if the phone is stock and what version of stock was on it, or whether you have custom firmware. I'm assuming you have stock, then rooted and installed the wrong version of Siyah, or perhaps a version for Siyah not made for the I777. As far as not being able to use the functions when you boot into CWM, it is probably because the select key is the home button, and not the power button.
2) You can't flash back to stock using CWM. I'm not aware of any zip with straight stock. You must use Odin to flash stock. Since you are having connection problems using Odin, I am guessing that you either did not follow the correct sequence, or that you did not install the correct USB driver on your Windows pc. Another possibility is that you have a bad usb cable or connection.
3) If you spent a month searching on the xda forum for this phone, you would have found any number of posts by myself that detail all the answers to all the questions you have posed so far. I've posted these things several dozens of times.
Please let us know if any of the above helps you. Please search these forums for issues connecting to Odin. If you are unable to find any answers that way, please post back here with more detailed information.
I have an issue with my S2 I777.
When it last booted it was on cyanogenmod 9 with siyah v4.3.3 and is a good setup. My problem is i let it die/dead battery and didn't bother to plug it in for about 4 days or so.now when i try turning it on with any button combo i get nothing.when i plug it in the battery icon just flashes and not even my jig will get it into download mode to use odin
Sent from my Nexus 5 using Tapatalk
enter download mode WITHOUT a battery in the phone
follow these steps:
-remove the battery from the phone
-hold down vol+ & vol- & power, then plug in the usb cable
-continue holding the buttons until the phone shows the download mode prompt
-put the battery into the phone (while the phone is at the download prompt)
happy flashing
-Cyril
jball said:
I have an issue with my S2 I777.
When it last booted it was on cyanogenmod 9 with siyah v4.3.3 and is a good setup. My problem is i let it die/dead battery and didn't bother to plug it in for about 4 days or so.now when i try turning it on with any button combo i get nothing.when i plug it in the battery icon just flashes and not even my jig will get it into download mode to use odin
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
cyril279 said:
follow these steps:
-remove the battery from the phone
-hold down vol+ & vol- & power, then plug in the usb cable
-continue holding the buttons until the phone shows the download mode prompt
-put the battery into the phone (while the phone is at the download prompt)
happy flashing
-Cyril
Click to expand...
Click to collapse
K that part worked as far as getting into download mode so the phone is salvageable. However as soon as i put the battery in wile plugged in and in download mode it just shuts down.wile still plugged in i repeat the button combo and it does flash in red that the battery is to low .before posting in here it had been plugged in for one day and all last night. I was getting excellent battery life before this issue started .have tried multiple charger cords
?
Sent from my Nexus 5 using Tapatalk
I have heard with these devices that they behave poorly when the battery is allowed to die completely, citing that the phone needs power to start/maintain the charging circuit (it sounds silly, I agree). One common suggestion is to purchase an external charger, or go to a local mobile store and ask them to put the battery on a charger for a few minutes, or to simply purchase another battery.
Hopefully one of our peers can chime-in to verify this, or provide other options.
jball said:
K that part worked as far as getting into download mode so the phone is salvageable. However as soon as i put the battery in wile plugged in and in download mode it just shuts down.wile still plugged in i repeat the button combo and it does flash in red that the battery is to low .before posting in here it had been plugged in for one day and all last night. I was getting excellent battery life before this issue started .have tried multiple charger cords
?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have a dock/external charger and extra battery being shipped.
I will let you know how it goes
Sent from my Nexus 5 using Tapatalk
Update
This is the external charger i received today
http://www.amazon.com/gp/aw/d/B0080XSEYI
Wile charging it indicates red and when finished charging it turns blue.
100% battery life just like it did before i let it drain.
Sent from my Nexus 5 using Tapatalk