Related
Please bare with me.
This is the second time this particular problem has happened to my device.
So I was on the tram coming back from my maths exam today.
(Running a ROM with Hardcore's SpeedMod K2-15)
I decide to change the song, all of a sudden, my screen turns black and I can't turn my phone back on. I as soon as it happened I thought uh oh. (the battery was at 74%.
So I tried to reboot my phone, didn't work.
Tried to get into download mode, didn't work.
Tried to get into recovery mode, didn't work.
Went to see if anything happened if I put in my charger AND USB cable. Both instances nothing happened.
When the incident happened last time, I was about to have it shipped to Samsung, was in the car on the way there and I was still pressing the power button in hope that it would work. Low and behold, it turned on, I flashed a different ROM and kernel and was on my merry way until today.
After browsing Q&A for around an hour the only other instances I've found with this problem are my original thread (around a month ago) when the same problem occurred.
http://forum.xda-developers.com/showthread.php?t=1302645
And another one I found today whilst browsing.
http://forum.xda-developers.com/showthread.php?t=1289063
also here
http://forum.xda-developers.com/showthread.php?p=18139062
So up to my knowledge this seems like a problem that isn't only a one off if I'm not the only one reporting it.
Is there anything I can possibly do to fix my phone or something to avoid doing so others don't run into the same unfortunate set of circumstances?
PS. two days ago I deleted a few folders on my USB storage as they were taking up too much storage space. I doubt they had anything to do with the problem though and that's the only difference I can think of that MAY have trigged the event. But I have no reason as to why it happened. I am also using NoMoarPowah and Chainfires3D mod (which I've been using for ages and i'm sure had nothing at all to do with the problem)
hopefully someone knows of a definite solution. :\
Wow the same thing is happening to my phone as well. Thanks for the detailed description. Hopefully we'll find a response soon. Also, I would suggest you investigate the volume of chode in the nearby vicinity of your phone, may be a problem (personal experience)
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
pokergirl said:
You spelt bare wrong
Click to expand...
Click to collapse
I've made similar mistakes in life. You don't want to mix them up at the wrong time. *Shows bear scars*
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
ALSO Don't dinosaur with it, nor allow for sluts to touch it xoxoxoxoxoxoxoxoxox bb <3
pokergirl said:
last edited by pokergirl; today at 01:04 pm. Reason: I did it wrong!
Click to expand...
Click to collapse
you're doing it wrong!
Too late for the sluts, they're all over it! x0x0x0x0x0x
H3h3
H3h3h3h3h3h3h3h3h3 its ****ed darl <3 xxxxxx
Leopardkitty69 stop degrading urself g1rL g3t urs31f @ [email protected] xo
- A girl who knows how to control balls
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
I dropped it quite hard and it caused corruption on /efs partition.
lol'd
This thread has suddenly become a lot more interesting.
pokergirl said:
Through implementing my CAS 89 values and inserting chode = 2x length into my TVM solver i introduced the viagra into my phonem therefore, bringing its pwoer to 9001 and causing for it to groan in pleasure. Through utilising square volume = 2 * x * l with x = your vaginas length and y = The radius of your arsehole i solved this problem. (Personal experience, for more information visit (it made me delete the link))
P.s chodemaster - Your personal experience is obviously limited and incredibly detrimental to the phone. When YOU have caught all 151 original chodes you should post in this forum in a SERIOUS and well rounded individual manner
P.P.S NEED MOAR PYLONS
P.P.P.S THIS IS YOUR BIRTHDAY CARD FOR NEXT YEAR
Click to expand...
Click to collapse
Sigh I really need a solution. Not thread spam >.<
This sounds like a serious issue with your phone's hardware. You should return it to Samsung.
with the phones hardware itself?
If they manage to fix it do you think the'll notice it's been rooted?
I've removed the triangle and reset the flash count i've just got a new ROM on it.
(as in will it still be under warranty)
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Freakgs said:
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Click to expand...
Click to collapse
but it currently won't turn on at all ;|
giga502 said:
but it currently won't turn on at all ;|
Click to expand...
Click to collapse
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Freakgs said:
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Click to expand...
Click to collapse
I've given it to a friend but I highly doubt it would work. Anyway for now, I'm going to place it in rice JUST IN CASE there is a tiny bit of moisture on some part of the motherboard which is messing things up. If that dosn't work i'm going to go down to my mobile dealer and hope for the best
thanks for your help!
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
ante0 said:
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
Click to expand...
Click to collapse
no I havn't done that. I'm taking it back later today
ICS update bricked the prime. it's now hung on the boot screen. where says "eee pad, asus, nvidia tegra"
called asus USA support, first asked to do a data wipe. did that and didn't work. now told to let it sit on the hanging boot screen to completely drain battery. then charge it for 2 hours. the tab will revert to honeycomb. once it boots, then go from there.
anyone know if they are BSing or this will actually revert?
leo221 said:
ICS update bricked the prime. it's now hung on the boot screen. where says "eee pad, asus, nvidia tegra"
called asus USA support, first asked to do a data wipe. did that and didn't work. now told to let it sit on the hanging boot screen to completely drain battery. then charge it for 2 hours. the tab will revert to honeycomb. once it boots, then go from there.
anyone know if they are BSing or this will actually revert?
Click to expand...
Click to collapse
I don't see any way that a power drain will melt the ICS away, that's pure bs. But you can still follow their instructions and be pleasantly surprised if it happens. Which then leads to the question, how about the rest of us, will our ICS update suddenly vanish and revert back to Honeycomb one of these days?
tedr44 said:
I don't see any way that a power drain will melt the ICS away, that's pure bs. But you can still follow their instructions and be pleasantly surprised if it happens. Which then leads to the question, how about the rest of us, will our ICS update suddenly vanish and revert back to Honeycomb one of these days?
Click to expand...
Click to collapse
really disappointed. it's like being told, put it under your pillow, problem will go away.
please tell me your kidding? this will be the third story I have heard now where Asus said something totally bogus just to get a customer off the phone this is sick.
PrimeTimeBro said:
please tell me your kidding? this will be the third story I have heard now where Asus said something totally bogus just to get a customer off the phone this is sick.
Click to expand...
Click to collapse
nope. i was told that!
suppose they have a solution in the making and just want me to wait, why not telling me the truth?
leo221 said:
nope. i was told that!
suppose they have a solution in the making and just want me to wait, why not telling me the truth?
Click to expand...
Click to collapse
Actually it isnt complete BS. There is a post that follows the battery drain, which is said to work for bricked devices/failed otas. It has worked for a number of people.
PrimeTimeBro said:
please tell me your kidding? this will be the third story I have heard now where Asus said something totally bogus just to get a customer off the phone this is sick.
Click to expand...
Click to collapse
Surely, there seems to be a considerable amount of conflict between the ICS and the current crop of Primes out there. Missing serials, bricked tabs, dead gps/wifi, etc. What in the whole wide world is Asus doing for compatiblity between generations/ batches of these units with the latest build of ICS? I can only imagine one tired and overworked programmer staying up in the wee hours trying to finish up an ICS update so Asus can claim to be the first tab with the new OS. Quality, or the lack of it, is a serious issue here, the Prime fans are kept in the dark which makes the situation worse.
Its gonna work
Mine is totally fine but my Neibor did the update with a low battery and his stuck on the boot screen after the update. After the thing totally drained he plugged it in and charged it overnight and it reverted to honeycomb like nothing ever happened when he turned it on.
Sent from my SPH-D710 using xda premium
ajkid93 said:
Actually it isnt complete BS. There is a post that follows the battery drain, which is said to work for bricked devices/failed otas. It has worked for a number of people.
Click to expand...
Click to collapse
If it works for the bricked units it should also work for the nonbricks, or is there ai routine that can tell the difference between the two and prevents the fallback to the Honeycomb? This is a very interesting feature of the Prime, reflashing through a power drain process.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
ilostmypistons said:
Its gonna work
Mine is totally fine but my Neibor did the update with a low battery and his stuck on the boot screen after the update. After the thing totally drained he plugged it in and charged it overnight and it reverted to honeycomb like nothing ever happened when he turned it on.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks, I'm impressed! That means the boot process performs a check on the update to ensure completeness and accuracy and dumps the garbage if it fails. I believe it now.
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
tedr44 said:
If it works for the bricked units it should also work for the nonbricks, or is there ai routine that can tell the difference between the two and prevents the fallback to the Honeycomb? This is a very interesting feature of the Prime, reflashing through a power drain process.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Thanks, I'm impressed! That means the boot process performs a check on the update to ensure completeness and accuracy and dumps the garbage if it fails. I believe it now.
Click to expand...
Click to collapse
It also means the Honeycomb is a permanent resident while ICS updates are tenants that come and go as upgrades become available. So there should be no way to brick a Prime if the Honeycomb is hard coded in rom.
tedr44 said:
...
[/COLOR]
It also means the Honeycomb is a permanent resident while ICS updates are tenants that come and go as upgrades become available. So there should be no way to brick a Prime if the Honeycomb is hard coded in rom.
Click to expand...
Click to collapse
well, if that's true, we learned something new. what prevents working units reset back to honeycomb when battery power runs out? some logical errors are in the theory.
very nice asus could write such feature into the firmware (but not able to write a stable update in the first place, that is if battery < x percent, prompt power, else continue update...)
seems odd.
This isn't going to work, tried it with my first prime. although I hope I'm wrong for the op's sake
Sent from my Galaxy Nexus using Tapatalk
pyro6128 said:
This isn't going to work, tried it with my first prime. although I hope I'm wrong for the op's sake
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
how did you know? did asus people told you?
Was it the ICS update (so the GPS fix) or the update to ICS...
Big difference there, if the latter then yeah... can imagine that if the update didn't complete you can do the trick described.
leo221 said:
how did you know? did asus people told you?
Click to expand...
Click to collapse
Hey leo221, I think you should give it a try because some people have done it and reverted back to the Honeycomb. You have nothing to lose and if you unbrick your Prime then that would be great! Let us know the results so others will be informed. Thanks.
No but I read on the forums that people were able to recover their devices by lettering the battery drain when there were problems with one of the hc updates. I figured it might work with my issues after the ics update. I let it die, then charged it when I got home from work, still bootlooped.
Sent from my Galaxy Nexus using Tapatalk
dagrim1 said:
Was it the ICS update (so the GPS fix) or the update to ICS...
Big difference there, if the latter then yeah... can imagine that if the update didn't complete you can do the trick described.
Click to expand...
Click to collapse
was the ICS update. when I do the vol down+power hold, it says I'm on US_epad-9.4.2.11-20120117.
dagrim1 said:
Was it the ICS update (so the GPS fix) or the update to ICS...
Big difference there, if the latter then yeah... can imagine that if the update didn't complete you can do the trick described.
Click to expand...
Click to collapse
More details please, why is there a difference? Does Honeycomb disappear altogether when ICS with gps fix is installed?
I think the difference between this and the non-bricked devices is that the OTA update didn't work, so when the battery totally drains it reverts back to the last working setup. May be wrong though. I'm sure it wouldn't work if you were using ICS and it bricked for some reason down the line after a successful OTA update.
tedr44 said:
Hey leo221, I think you should give it a try because some people have done it and reverted back to the Honeycomb. You have nothing to lose and if you unbrick your Prime then that would be great! Let us know the results so others will be informed. Thanks.
Click to expand...
Click to collapse
yeah. think I'll just give it another day. sure will report back if anything happens.
pyro6128 said:
No but I read on the forums that people were able to recover their devices by lettering the battery drain when there were problems with one of the hc updates. I figured it might work with my issues after the ics update. I let it die, then charged it when I got home from work, still bootlooped.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well in this case, the solution came from an Asus engineer so there must be some credibility in that process.
---------- Post added at 03:35 PM ---------- Previous post was at 03:29 PM ----------
bfmetcalf said:
I think the difference between this and the non-bricked devices is that the OTA update didn't work, so when the battery totally drains it reverts back to the last working setup. May be wrong though. I'm sure it wouldn't work if you were using ICS and it bricked for some reason down the line after a successful OTA update.
Click to expand...
Click to collapse
Ok, the OP said,
"was the ICS update. when I do the vol down+power hold, it says I'm on US_epad-9.4.2.11-20120117."
so I assume that he will be able to revert back to Honeycomb, hopefully.
---------- Post added at 03:46 PM ---------- Previous post was at 03:35 PM ----------
Just my own thoughts, it appears the process of updating to ICS opens up a register that allows the flashing of the ICS code into an eeprom device and when competed the register is closed but when the update does not take and the process hangs, the register is left open and the power drain wipes the eeprom. So the tab reverts back to Honeycomb, very similar to an image recovery process in the pc world.
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
I was performing a nandroid backup when then the progress line stopped. I let it sit for over 4 hours and the line did not move. The phone was locked up. I took the battery out to reset the phone and now it will not turn on. I tired several different key comobs, including volume up+down and power, with no efffect. When I plug it in it does nothing. I was using ISCrewD with the Siyah kernal now for a couples months with no issues. That was actually the only custom rom I ever flashed to the phone, loved the rom. From reading the forums, it seems I am hard bricked. How did that happen? Any suggestions?
Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones.
Version 2.6.13.
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Galaxy_Cat said:
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Click to expand...
Click to collapse
For real? Siyah 3.1.rc6 is for GB?
You were doing a nandroid backup, not a restore, and on gingerbread, so it's hard to say what caused the problem. I don't believe I've seen any report exactly like yours.
You tried several button combinations, including recovery mode, which did not work, but did you try to get into download mode? First try to enter download mode with the battery in -- hold vol+ and vol- (but not pwr) and then plug in the usb cable. If no success with that, pull the battery and do the exact same sequence to enter download mode. The usb cable will provide the power. Sometimes there is a problem with the battery. If you can get download mode, you're not bricked.
votinh said:
For real? Siyah 3.1.rc6 is for GB?
Click to expand...
Click to collapse
what are you talking about? Read OP response.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
My bad. I've only had this phone for a week and never used that ROM...just assumed it was ICS based on the name.
Galaxy_Cat said:
what are you talking about? Read OP response.
Click to expand...
Click to collapse
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
votinh said:
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
Click to expand...
Click to collapse
I misread you (had to reread this thread three times to get it straight!) sorry for confusion.
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
gandalf21502 said:
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
Click to expand...
Click to collapse
You need the USB dongle to force it to
Go in download mode.
Sent from my GT-N7000 using XDA
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
I called AT&T this morning, I can get a refurbished one to replace mine, guess I will go that route....
gandalf21502 said:
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
Click to expand...
Click to collapse
So just because it might not work, you're not going to try it? Try it!
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
gandalf21502 said:
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
Click to expand...
Click to collapse
Just to be clear, when we say USB dongle, we're not taking about a USB jig...we're talking about the USB-to-MicroUSB data cable that came with the phone.
I have already tried the micro usb cable that came with the phone and tried to get Odin to see the phone, no go. I ordered a Jig to see if it would force the phone into download mode...
Got my USB Jig today. Took the battery out (even tried wifes 'good' battery). Put the battery in, then the Jig...nothing. I would assume the phone has some form of hardware failure...guess time to get ahold of AT&T and get a warranty exchange.
AT&T is sending a 'refurb' phone today...should be here soon...hopefully they don't get my phone to work and see the custom kernal/rom...No matter what I try, it just won't come on.
I just cracked the screen on my i605 yesterday, and they're sending me a replacement today. What are the odds that it'll have 4.3 on it? Because, I'd really like to unlock the bootloader.
crbnfbr said:
I just cracked the screen on my i605 yesterday, and they're sending me a replacement today. What are the odds that it'll have 4.3 on it? Because, I'd really like to unlock the bootloader.
Click to expand...
Click to collapse
Just got my "new" replacement phone, and yep 4.3 on it. So, no unlocking the boot loader. Is there any way I can installed sophisticated ROM, or better yet CWM recovery?
crbnfbr said:
Just got my "new" replacement phone, and yep 4.3 on it. So, no unlocking the boot loader. Is there any way I can installed sophisticated ROM, or better yet CWM recovery?
Click to expand...
Click to collapse
No there is not at this moment.. sad to say.. There is one option but it might cost you about a $100.. You could look online for a 4.1.2 motherboard for i605, the specific model.. it very simple to swap out..took me only about 15 mind and I have never done it before.. If your not comfortable PM me and I can recommend someone you can send it to that guarantees their work/parts for 3 months.. good luck man!:good:
lacoursiere18 said:
No there is not at this moment.. sad to say.. There is one option but it might cost you about a $100.. You could look online for a 4.1.2 motherboard for i605, the specific model.. it very simple to swap out..took me only about 15 mind and I have never done it before.. If your not comfortable PM me and I can recommend someone you can send it to that guarantees their work/parts for 3 months.. good luck man!:good:
Click to expand...
Click to collapse
I actually tries "saferoot" and so far so good. I'm still waiting to see if it'll restore my data through Titanium Backup. Root checker does show it is rooted though.
I though about taking the mobo out of my cracked screen phone and swapping it once I booted this replacement and saw it was 4.3.
crbnfbr said:
I actually tries "saferoot" and so far so good. I'm still waiting to see if it'll restore my data through Titanium Backup. Root checker does show it is rooted though.
I though about taking the mobo out of my cracked screen phone and swapping it once I booted this replacement and saw it was 4.3.
Click to expand...
Click to collapse
Dude thats a GREAT idea! You should.. as long as it was not damaged with the phone..
You can root 4.3 just fine.. that is the same method I used when I did it.. Make sure evrything is installing properly and you have no errors when the script runs through..
If you need any helping swapping motherboard out.. Hit me up in a PM and I can maybe provide some pointers..
lacoursiere18 said:
Dude thats a GREAT idea! You should.. as long as it was not damaged with the phone..
You can root 4.3 just fine.. that is the same method I used when I did it.. Make sure evrything is installing properly and you have no errors when the script runs through..
If you need any helping swapping motherboard out.. Hit me up in a PM and I can maybe provide some pointers..
Click to expand...
Click to collapse
Is it just a matter of taking out all the baby silver screws, and connecting some ribbon cables? Also, will I still keepxmy CWM recovery and old sophisticated root?
I've done dzens of pc mobos but never a phone.
crbnfbr said:
Is it just a matter of taking out all the baby silver screws, and connecting some ribbon cables? Also, will I still keepxmy CWM recovery and old sophisticated root?
I've done dzens of pc mobos but never a phone.
Click to expand...
Click to collapse
Yes..thats all it takes.. Umm not to sure.. Whatever you had on your old one might still be there.. not sure if it resets or anything..
If you have done PC's then it should be no problem for you.. take your time..just smaller pieces..
Good Luck!:good::highfive:
lacoursiere18 said:
Yes..thats all it takes.. Umm not to sure.. Whatever you had on your old one might still be there.. not sure if it resets or anything..
If you have done PC's then it should be no problem for you.. take your time..just smaller pieces..
Good Luck!:good::highfive:
Click to expand...
Click to collapse
I've already sealed it up in the return envelope, but I'll cut it open for a chance to run a custom recovery and better root. I just don't think I can last a full year before my contracts up.
Even if it does reset my CWM backup I'd hope would restore everything.
crbnfbr said:
I've already sealed it up in the return envelope, but I'll cut it open for a chance to run a custom recovery and better root. I just don't think I can last a full year before my contracts up.
Even if it does reset my CWM backup I'd hope would restore everything.
Click to expand...
Click to collapse
Worse case scenario is just running CASUAL again and unlocking it. Let me know what happens:good:
lacoursiere18 said:
Worse case scenario is just running CASUAL again and unlocking it. Let me know what happens:good:
Click to expand...
Click to collapse
At the very least I'll at least I'll get my boot loader unlocked, CWM recovery and sophisticated rom all back.
crbnfbr said:
At the very least I'll at least I'll get my boot loader unlocked, CWM recovery and sophisticated rom all back.
Click to expand...
Click to collapse
Well, I swapped the old mobo with the new one. Now, neither the old mobo or new mobo works with the replacement phone. I made sure everything was connected the same way, but still it won't even power on.
crbnfbr said:
Well, I swapped the old mobo with the new one. Now, neither the old mobo or new mobo works with the replacement phone. I made sure everything was connected the same way, but still it won't even power on.
Click to expand...
Click to collapse
That does not make any sense... Did you watch that video? and stupid ? is your battery charged?
I watched the video. Battery was at like 90%. Now with the now mobo in the new phone if I hit the power button 3 times the LED will turn red, but when it's pliugged in charging it doesn't do anything.
I did leave the speaker and antenna from the new mobo in the replacement phone. Do I need to swap those too?
crbnfbr said:
I watched the video. Battery was at like 90%. Now with the now mobo in the new phone if I hit the power button 3 times the LED will turn red, but when it's pliugged in charging it doesn't do anything.
I did leave the speaker and antenna from the new mobo in the replacement phone. Do I need to swap those too?
Click to expand...
Click to collapse
I can now get the green LED light to come one with the new mobo and charger plugged in if I hold the power button, but that's all it will do.
crbnfbr said:
I can now get the green LED light to come one with the new mobo and charger plugged in if I hold the power button, but that's all it will do.
Click to expand...
Click to collapse
Sounds like something wasn't put together right.. I would start over and make sure all is connected properly.. And this motherboard was from same device correct? Not like one from tmobile, sprint etc ect Verizon to Verizon..
Yeah, it was from a i605 I got two weeks short of a year ago. I also agree about something not being put together right. I'm going to swap the antenna and speaker too.
crbnfbr said:
Yeah, it was from a i605 I got two weeks short of a year ago. I also agree about something not being put together right. I'm going to swap the antenna and speaker too.
Click to expand...
Click to collapse
Ok..I didnt have to that.. and i was in the same scenario.. but just make sure you go over everything carefully...:highfive:
lacoursiere18 said:
Ok..I didnt have to that.. and i was in the same scenario.. but just make sure you go over everything carefully...:highfive:
Click to expand...
Click to collapse
Well, I've made some progress. It boots up with the blue LED and I can hear the Verizon chime, but I get absolutely nothing on the screen. It's completely black.
crbnfbr said:
Well, I've made some progress. It boots up with the blue LED and I can hear the Verizon chime, but I get absolutely nothing on the screen. It's completely black.
Click to expand...
Click to collapse
Weird sounds like something is not hook up to the screen? You didn't force it open and mess the screen up right..
Sent from my SCH-I605 using xda app-developers app
I'm thinking I must have messed up a ribbon cable by accident. The insurance company is going to send me a new one, and I'll just keep the locked bootloader and "saferoot" so I can use Titanium Backup and Rom Toolbox.