Related
Hey every1!
I was hoping that my first post here would be something more funny then this... But... you can´t always get what you wan´t.
My problem... My note is completly dead!
I was messing around with editing some pictures i just took on the kids when my phone just frooze... I then held the powerbutton for about 15sec before it died. After that... stonedead!
No matter what i do with it, it´s just black and doesn´t respond to anything.
- Had 20+% battery in it when it frooze, i´ve tried to charge it but no difference.
- Had the battery pulled for 30mins+ , no change.
- Can´t get to recovery mode whatever i do.
- Connected it do the computer, no sound no nuttin.
The phone is/was rooted, running rocketrom V.20 with abyssnote kernel 3.3 when it died.
Haven´t had any issues with it until now.
So... Any ideas on what i should try next? Besides using it as a really expensive paperweight that is
HELP!! =)
/Swe
dude dont worry , may be you need to charge your mobile then turn it on ( i hope it's just battery dead)
Hold the power button for 30 seconds or more just to be sure it's resetting
Sent from my GT-N7000 using xda premium
Have you tried getting into the download mode ?
SweCrow81 said:
Hey every1!
I was hoping that my first post here would be something more funny then this... But... you can´t always get what you wan´t.
My problem... My note is completly dead!
I was messing around with editing some pictures i just took on the kids when my phone just frooze... I then held the powerbutton for about 15sec before it died. After that... stonedead!
No matter what i do with it, it´s just black and doesn´t respond to anything.
- Had 20+% battery in it when it frooze, i´ve tried to charge it but no difference.
- Had the battery pulled for 30mins+ , no change.
- Can´t get to recovery mode whatever i do.
- Connected it do the computer, no sound no nuttin.
The phone is/was rooted, running rocketrom V.20 with abyssnote kernel 3.3 when it died.
Haven´t had any issues with it until now.
So... Any ideas on what i should try next? Besides using it as a really expensive paperweight that is
HELP!! =)
/Swe
Click to expand...
Click to collapse
OC? ? And when you will say yes 1704?? But don't worry just put it on charge for 30 45 minutes and then try to boot up.
Sent from my GT-N7000 using Tapatalk
carhigh said:
Hold the power button for 30 seconds or more just to be sure it's resetting
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Done that... didnt do anything...
buk_grudziadz said:
Have you tried getting into the download mode ?
Click to expand...
Click to collapse
I did yes... it just won´t go anywhere from dead :S
Braxos said:
OC? ? And when you will say yes 1704?? But don't worry just put it on charge for 30 45 minutes and then try to boot up.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Not OC no... undervolted thoo... but have been running the same UV setting for 3 weeks.
Must be hardware problem, no doubt about it.
Try charging it for a while and then press the power button for 10-20 seconds.
Hope it's that simple! Good luck!
Sent from my GT-N7000 using Tapatalk
mfractal said:
Try charging it for a while and then press the power button for 10-20 seconds.
Hope it's that simple! Good luck!
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Well... Been charging the brick overnight (12+ hours), and still not a single sign of life.
I guess there's nuttin more to it then to return it.
Hopefully they won't notice the root and custom rom and kernel, i meen... It's completly dead so it shouldn't be a problem right?!
If you find, try other battery once.
- Use JIG
Switch off your phone and take out the battery for 15-20 seconds
Install the battery back but DO NOT turn it on
Plug this USB JIG DONGLE into the micro-USB port of the phone
Wait for a few seconds. You should see the Download Mode logo on the screen.
Unplug the module.
dr.ketan said:
If you find, try other battery once.
- Use JIG
Switch off your phone and take out the battery for 15-20 seconds
Install the battery back but DO NOT turn it on
Plug this USB JIG DONGLE into the micro-USB port of the phone
Wait for a few seconds. You should see the Download Mode logo on the screen.
Unplug the module.
Click to expand...
Click to collapse
If i had a jig i would have tried that for sure. However, i got fed up on trying so it's now returned to the store and sent away for service.
Ty every1 for ur efforts with trying to aid me!
I would be interested to see what Samsung say if they noticed the root... might make me think twice about rooting it on such a expensive device. Good luck though!
iceghost1210 said:
I would be interested to see what Samsung say if they noticed the root... might make me think twice about rooting it on such a expensive device. Good luck though!
Click to expand...
Click to collapse
I´ll report back here then It would take around 3 weeks for me to get it back thoo
SweCrow81 said:
Hey every1!
I was hoping that my first post here would be something more funny then this... But... you can´t always get what you wan´t.
My problem... My note is completly dead!
I was messing around with editing some pictures i just took on the kids when my phone just frooze... I then held the powerbutton for about 15sec before it died. After that... stonedead!
No matter what i do with it, it´s just black and doesn´t respond to anything.
- Had 20+% battery in it when it frooze, i´ve tried to charge it but no difference.
- Had the battery pulled for 30mins+ , no change.
- Can´t get to recovery mode whatever i do.
- Connected it do the computer, no sound no nuttin.
The phone is/was rooted, running rocketrom V.20 with abyssnote kernel 3.3 when it died.
Haven´t had any issues with it until now.
So... Any ideas on what i should try next? Besides using it as a really expensive paperweight that is
HELP!! =)
/Swe
Click to expand...
Click to collapse
I'm not sure if your problem is related to the thread below. Kindly see my posts in the thread. Have you tried plugging-in your SGNote with other chargers?
http://forum.xda-developers.com/showthread.php?t=1470082
wolfmanx said:
I'm not sure if your problem is related to the thread below. Kindly see my posts in the thread. Have you tried plugging-in your SGNote with other chargers?
http://forum.xda-developers.com/showthread.php?t=1470082
Click to expand...
Click to collapse
I did yes... Tried my GF htc one, and a universal 2A charger to... Still dead... Now i´m just waiting to c what service finds... :S
SweCrow81 said:
Hey every1!
I was hoping that my first post here would be something more funny then this... But... you can´t always get what you wan´t.
My problem... My note is completly dead!
I was messing around with editing some pictures i just took on the kids when my phone just frooze... I then held the powerbutton for about 15sec before it died. After that... stonedead!
No matter what i do with it, it´s just black and doesn´t respond to anything.
- Had 20+% battery in it when it frooze, i´ve tried to charge it but no difference.
- Had the battery pulled for 30mins+ , no change.
- Can´t get to recovery mode whatever i do.
- Connected it do the computer, no sound no nuttin.
The phone is/was rooted, running rocketrom V.20 with abyssnote kernel 3.3 when it died.
Haven´t had any issues with it until now.
So... Any ideas on what i should try next? Besides using it as a really expensive paperweight that is
HELP!! =)
/Swe
Click to expand...
Click to collapse
any news on your note? hope its ok now
weng_cas said:
any news on your note? hope its ok now
Click to expand...
Click to collapse
Hey!
Yes, great news actually!
I got it back like 5 days ago...
And, it was the main circuit board that had faulted! That ment they couldn´t get the info of it ,or atleast they decided that it would be to much trouble to do so.
So it´s now back and running again... rooted, running RR v22 and franco kernel v6
Didn´t cost me anything
Hopefully it won´t happen again thoo... I can´t be without it anymore! Used my old 3gs when it was on service... goddam hated it!
Congratz! Good to hear that your sgn is ok
Sent from my GT-N7000
SweCrow81 said:
Hey!
Yes, great news actually!
I got it back like 5 days ago...
And, it was the main circuit board that had faulted! That ment they couldn´t get the info of it ,or atleast they decided that it would be to much trouble to do so.
So it´s now back and running again... rooted, running RR v22 and franco kernel v6
Didn´t cost me anything
Hopefully it won´t happen again thoo... I can´t be without it anymore! Used my old 3gs when it was on service... goddam hated it!
Click to expand...
Click to collapse
First and for most I want to congratulate you on having your phone back & fully functional again. I too am in the same situation right now where my phone is hard bricked and can't turn on in any shape or form. I sen't it to a local shop to fix who do Jtag for this phone but say they can't get it to start. I wanted to know when you said "the main circuit board that had faulted" did they replace any parts? or just flash software with JTag again? Any help would be really appreciated.
Did yummy take out the battery and then insert it and den did yu try booting it up????
press thanx if I helped yu sent from sga
hey guys i searched and havent really found anything that matched quite what i had going on so here we go... I was 95 percent through flashing the ICS rom it got through the hboot section and rebooted.. on the screen i saw two arrows in circular form above a phone .. and something was definitely being downloaded.. then the phone went black, doesnt go into hboot, doesnt a charging light when plugged in , but is picked up by the computer, ie. connection noise. Im in no way a noob at flashing roms , but something is definitely wrong with my phone.. Any ideas? It was charged full battery by the way.. it does glow in a dull light when i push volume down and power, or power alone...
Your phone indeed seems to be bricked. The identification noise from the computer may just mean that your USB is receiving power from the battery.
When my friend had a similar problem with his Amaze, he went to the HTC service center and they replaced his phone after keeping it for 4 days
So taking it to bestbuy to get it serviced is probably the only alternative, since its insured through them... lol just my luck
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Dxtra said:
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's not fair to say. There's plenty of users that flashed without bricking their devices.
I followed the alternate directions here and had no issues.
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
meatwad0222 said:
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
As far as im concerned each one of us is responsible for what happens to our phones, warnings are put for a reason.. ive jailbroken, rooted the hardest of phones .. it was just my time for the inevitable to happen. I get my phone back in three days and you can be sure ill be back here again doing crazy rooty stuff to my phone no rom or dev should be held responsible for what ive done ..
Sent from my MB860 using Tapatalk
dusty2422 said:
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
Click to expand...
Click to collapse
Saying something is noob proof will inevitably prove that some where some noob will sow its not noob proof. I'll admit there were a few moments of panic when I flashed the zip method pg released. When that happened I just breathed deep and took my time and everything worked great in the end. I personally feel that what the devs have put out there is fairly safe as long as the directions are followed exactly.
Sent from my HTC PH39100 using xda premium
Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't have the money to buy tons of new devices....its about knowing ur own limitations...do not criticise a devs hard work when it is proven to work...no its defenitly not idiot proof but it is very easy...I've done it to 3 phones already with no problems...the devs are not responsible for bricked phones
Sent from my HTC PH39100 using XDA
yea i must say it was a hundreed percent my fault in bricking my device so im not mad at anyone..and as far as the money goes its not a super big deal..i always make more o and btw im gonna be getting my replacement today and im gonna try this all again aft6er reading everything again and again and agian o and again lol
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
I bricked my phone Sunday night, still not 100% sure what I did wrong but it did what yours is doing now. I simply called the AT&T exchange by mail and used the factory warranty. Granted I guess there is a slight chance they could find out it was rooted (if they can somehow get it to recover or even turn on) but it got me a replacement... Food for thought.
Btw I got the new one and used the RUU and it worked seamlessly.
Sent from my HTC PH39100 using xda premium
bsSkunkApe said:
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
Click to expand...
Click to collapse
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
dizzyraider said:
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
Click to expand...
Click to collapse
Fraid it doesn't search for anything. I posted in the threads and tried everything I could think of and everything that was suggested. Though there isn't much you can do besides keep removing the battery and trying vol dn + pwr. Just a black screen.
Just a few things I tried (removed battery each time)- vol down + power (no sd card in) = blank black screen
vol down + power (with sd card and PH39IMG file) = blank black screen
vol down + power > boots to blank black screen, wait few seconds > press power button (like I'm going to fastboot) > plug into computer > type fastboot command into command prompt = command prompt says waiting for device
I always read the directions and threads a bunch of times before doing anything. Did lots of reading, google-ing, and searching. Fraid it bit the dust. I appreciate the help though. This is the first device snafu I've had. I've never had to send a phone in for any kind of warrantee work before. Hence my question above about getting it fixed.
Just in case, if it were to boot to that screen, what would I want to do? Just the PH39IMG? Or is there some other procedure?
Dxtra said:
Why would I tell anyone to flash when is not safe to.
Click to expand...
Click to collapse
Who TOLD you to flash the phone??? When I got my first android phone, a Samsung Fascinate, I LOVED the phone but nervous AS HELL that I would brick the phone. And I read, and read, and REREAD, trying to make sure I understood everything so that when I went looking for help, I at least could say, "Yes, I already tried this, this, and this".
I think the key thing to all of this is in two-fold - one, as someone stated before, this is a developer's forum. If you work on your car, and forgot to put oil in it, are you going to blame your mechanic? If you change your brakes and did not do something correctly, causing an accident, are you going to blame the car manufacturer??? Two, it states in MANY places, before you post, READ, READ, READ. It was actually ADVISED to NOT FLASH this ROM...
From this point forward, it almost seems as if there needs to be a waiver release to download roms, stating you will not ridicule nor torment the developers. And though I had heard about it but never seen it before, as I am on my 4th Android phone, there definitely are a few VERY NOTICEABLE disrespectful and ungrateful individuals in this forum. If you were my kid, and acted like that to me for something I GAVE YOU, I would do the same as PG - TAKE IT WAY and forget you.
Hi All,
Just picked up stock Tab 8.9, I'm fairly well-versed in rooting, CWM, Odin, etc. Enough to be dangerous I guess. In my haste I flashed a 5.5+. version of CWM that I only saw after the fact specifically warned that it does NOT work on the LTE version, but that is what I have (SGH-I957).
Now, I get absolutely nothing. I cannot get any screen - recovery, download, Odin, etc with any button combination that I try (power + vol up, down, both, etc.) As if there is simply no power to the device, whether plugged in or not. Battery was fine before I did this. When I plug in to USB I get 3 quick tones, neither Odin nor Kies sees the device.
Any advice would be greatly appreciated.
Howard
hdrewh said:
Hi All,
Just picked up stock Tab 8.9, I'm fairly well-versed in rooting, CWM, Odin, etc. Enough to be dangerous I guess. In my haste I flashed a 5.5+. version of CWM that I only saw after the fact specifically warned that it does NOT work on the LTE version, but that is what I have (SGH-I957).
Now, I get absolutely nothing. I cannot get any screen - recovery, download, Odin, etc with any button combination that I try (power + vol up, down, both, etc.) As if there is simply no power to the device, whether plugged in or not. Battery was fine before I did this. When I plug in to USB I get 3 quick tones, neither Odin nor Kies sees the device.
Any advice would be greatly appreciated.
Howard
Click to expand...
Click to collapse
Hello Howard,
That is pretty f*ckd up sorry for my languege lolz!
I guess you have hard bricked your device and that is also why you cant get it back to live.
The only option left is return it to samsung.
Sorry mate i wish i would know something but hard brick is almost unbrickable.
Greetings SK
+1 you're screwed, sorry. Do take it back and tell them it won't turn on, than play dumb. I just did that with my i957. It wasn't bricked but did have a custom rom, nrvate's. I should have it back tomorrow from Samsung. Then twrp and nrvate's cm10.
I did the same with a phone I did brick.
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
+1 you're screwed, sorry. Do take it back and tell them it won't turn on, than play dumb. I just did that with my i957. It wasn't bricked but did have a custom rom, nrvate's. I should have it back tomorrow from Samsung. Then twrp and nrvate's cm10.
I did the same with a phone I did brick.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Does the 'back to Samsung' advice hold for a tablet I bought used?
If it's still under warranty Samsung should take it and fix it free. If its out of warranty they'll fix it but at a cost. They can track it by its serial number and let you know if it's under warranty. Warranty is one year.
Your other Option is to jtag it, that'll run you about $50
Sent from my SGH-I727 using xda app-developers app
hdrewh said:
Hi All,
Just picked up stock Tab 8.9, I'm fairly well-versed in rooting, CWM, Odin, etc. Enough to be dangerous I guess. In my haste I flashed a 5.5+. version of CWM that I only saw after the fact specifically warned that it does NOT work on the LTE version, but that is what I have (SGH-I957).
Now, I get absolutely nothing. I cannot get any screen - recovery, download, Odin, etc with any button combination that I try (power + vol up, down, both, etc.) As if there is simply no power to the device, whether plugged in or not. Battery was fine before I did this. When I plug in to USB I get 3 quick tones, neither Odin nor Kies sees the device.
Any advice would be greatly appreciated.
Howard
Click to expand...
Click to collapse
OUCH! From experience, I can tell you it's definitely bricked. I know because I've done it - TWICE!
First time I was half asleep and made a bonehead move. Second time, I flashed a zip that should have worked in CWM, and it just never came back to life. Wouldn't charge. Wouldn't Boot. Nothing. All's I did was mail it back to the U.S., and both times I quickly received it back all shiny and new and stuff. Yea. Just play dumb...
Even though I screwed up twice (somehow), I'm gonna try it again on Hubby's Tab right this minute. But this time, I'm frigging terrified so wish me luck. I'm reading everything - TWICE!!! Hopefully, third time is a charm.
Oh. And don't feel bad. You''re not a Dope. We're learning. I've been flashing since back in XDA's baby-days and the days of the first Windows phones, but never ever bricked anything until now (except that one time in St. Louis). But blankety--blank happens and sooner or later I think it happens to all of us. Good luck with the return.
Good luck Punto on your. Rom install. I got my tab back last night and am up and running nrvate's cm10. I also flashed gapps 4.2 on it. Camera is crap though put I like the pinch to zoom in email.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
YAYYYYY!!!
I DID IT! YAYYYY!! :victory: I was up till 7:30a, but got it done right this time. In retrospect, after reading mountains of posts, I realized that my mistake was in not knowing there is a HUGE difference between the P7300 and the I957, and that you ABSOLUTELY CAN NOT, NEVER, EVER, EVER FLASH A P7300 ROM TO AN I957. WHO KNEW??? I thought they were the same. NOT!!!
FTR, I'm running CWM 5.5.04 flashed through ODIN, and AOKP Jelly Bean flashed of course through CWM. No worries...
Anyways, going forward, I'm able to make voice calls out, but not receive any. Guess I'll read up on this to see if there's a patch or fix or sumpin'.
Ya gotta love this forum and all of the superbright Devs out there. (Are they still called "Chefs" like back in the good old days?
Goog going! The biggest mistake people make is not getting a Rom specific to their device. There are so many different flavors that it's easy to do. I did it to when I got started, but lucky only soft bricked.
Which Rom are you using? The tab comes to life with An updated rom doesn't it? The devs are great!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Goog going! The biggest mistake people make is not getting a Rom specific to their device. There are so many different flavors that it's easy to do. I did it to when I got started, but lucky only soft bricked.
Which Rom are you using? The tab comes to life with An updated rom doesn't it? The devs are great!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Thanks jd1639. I'm using AOKP Jelly Bean. I agree. This ROM definitely brought this thing to life. I knew I had to change it cause Honeycomb sucks big wind. It belongs to my thoroughly-non-technical-hubby so this new ROM almost makes me jealous. I have another one coming as a warranty return and I'm gonna flash that one too. Who knows? I may keep it instead of selling it. I have a Padfone1 that I'm also going to sell, but I just got the GN2 cause I just couldn't live without 3G anymore (I'm in Panama so no 3G here). I'm falling in love with the GN2 but coming from the PadFone's larger screen, I wish it were a 7" instead of a 5". This 8.9" is a pretty good size though, so I'm thinking: "Hmmm... What if?..."
PuntoG said:
I'm using AOKP Jelly Bean. I agree. This ROM definitely brought this thing to life.
Click to expand...
Click to collapse
Congrats on yours, mine is going back to Samsung.
Can you reply with the link to the exact ROM you flashed? Also...CWM or TWRP? Links to the those?
Thanks.
Make sure they're for your device. The are a number of different tabs out there.
Sent from my SGH-I727 using xda app-developers app
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
I read lot about "antutu benchmark" as it's bad for Nexus 4 and cause this problem!.
hope somebody can help you out.
maddoggin said:
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
Click to expand...
Click to collapse
If it's easy to take back do it. However couple of folks have got it fixed by opening the backplate and disconnecting/reconnecting battery terminals.
Almost 90%+ people having this issue were running Antutu.
Why would you think its a good idea to flash a custom kernel on to stock?
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
http://forum.xda-developers.com/showthread.php?t=2128392
XxSilent22xX said:
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
Click to expand...
Click to collapse
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
This for the help. I'll try this tomorrow morning. Of course I tab a search bit could not find the threads. I hit red light and it took me to legacy phone. I type brick in search fort n4 and nothing. So I never saw those threads about this issue. So thanks. And ive never had a problem with running custom kernels on stock ROM. Never! Lol
Any ways thanks for help! Can moderator close this thread please! Thanks!
Sent from my Galaxy Nexus using xda premium
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Franco R53 is fine on stock - running it here with minimal other changes (I.e. root + email security policy hack)
I've updated every Franco kernel and all seen OK. Perhaps the benchmark related hardware failure is worth looking closely at.
FWIW, if you're back to stock, lock the bootloader and send it back as it sounds hardware to me.
Daern
Sent from my Nexus 4 using Tapatalk 2
synergeticink said:
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
Click to expand...
Click to collapse
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Charge your phone?
Im pretty sure you get the red light if your device has not enough power to display the screen.. Put your phone on charge through the main plug
qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So true man so true!
Sent from my Galaxy Nexus using xda premium
This happened to me, except I was bone stock. You need to hold down all 3 buttons at the same time; several times, and then try to get into the bootloader. That's what worked for me. Once you're in the bootloader you can flash the stock image(s) via fastboot.
qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
if this is true then why do i need to pull the phone apart and disconnect the battery and reconnect? apparently this is a known issue and has happened to others and taking phone apart and disconnecting battery and rconnecting it fixes the issue. unfortunately i dont have the right tools to do this so i will be taking my phone to t-mobile this morning. thanks for all the help guys. really appreaciate all the responses i got.
At times the power button wont work. In some cases of soft bricks. I have this issue since i had HD2.
Sent from my GT-N7000 using xda app-developers app
estallings15 said:
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Click to expand...
Click to collapse
That's exactly what I said in my last post. Next time the op needs to clarify if the custom kernel supports stock. But regardless I was correct.
OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
The service manual says ten seconds but yes it fully cuts power from the battery.
So sitting in my car waiting for t mobile store to open I decide to plug phone in to car charger since I know this will be first thing t mobile does and lo and behold phone booted up and start working. Battery drained to 0 and charging now. Go figure
Sent from my Nexus 4 using xda premium
Hi. I'm very new to xda and unsure how it all works, so please excuse me if my 1st post isn't written with the proper terminology! Ok. So, here's my issue. I, have the Samsung Galaxy Exhibit 4g. It, was rooted with cwm, running on jellybean 4.1.2. Recently, I was installing a new rom, from Slim. I, found it on xda. I, believe it's called Black Out. I, was doing a backup, while, in cwm recovery mode, and I happened to fall asleep in the middle of the backup. I, woke up an hr or so later, only to discover my phone completely turned off and wouldn't turn back on! I, had a full battery. I, have tried on numerous occassions to leave the battery out for several hrs and replace it, but still nothing! I've used different chargers and still nothing. Not, even a light blinks! The only thing, I haven't tried is replacing the battery. The phone is only 3-4mo old, so I didn't think it would be the battery. I've never seen this happen before! The ROM, didn't even get installed! I've searched high and low about my problem, and haven't come across not 1 solution! Could, this just be a case of a bad battery, or of a bigger issue?? I'm still under waranty but of course already being rooted, and having no way to get into my phone to unroot, I've voided that! PLEASE, if anyone can help with some support I'd GRATELY appreciate it! Anything, that can help save me $, would be wonderful! Thank you!
lovelyles said:
Hi. I'm very new to xda and unsure how it all works, so please excuse me if my 1st post isn't written with the proper terminology! Ok. So, here's my issue. I, have the Samsung Galaxy Exhibit 4g. It, was rooted with cwm, running on jellybean 4.1.2. Recently, I was installing a new rom, from Slim. I, found it on xda. I, believe it's called Black Out. I, was doing a backup, while, in cwm recovery mode, and I happened to fall asleep in the middle of the backup. I, woke up an hr or so later, only to discover my phone completely turned off and wouldn't turn back on! I, had a full battery. I, have tried on numerous occassions to leave the battery out for several hrs and replace it, but still nothing! I've used different chargers and still nothing. Not, even a light blinks! The only thing, I haven't tried is replacing the battery. The phone is only 3-4mo old, so I didn't think it would be the battery. I've never seen this happen before! The ROM, didn't even get installed! I've searched high and low about my problem, and haven't come across not 1 solution! Could, this just be a case of a bad battery, or of a bigger issue?? I'm still under waranty but of course already being rooted, and having no way to get into my phone to unroot, I've voided that! PLEASE, if anyone can help with some support I'd GRATELY appreciate it! Anything, that can help save me $, would be wonderful! Thank you!
Click to expand...
Click to collapse
Sounds like you may have installed a rom for a different phone as I have not heard of a slim blackout rom. I am sorry to say you probably bricked your device. If it doesn't even power on them you have no way of getting into Odin mode.
Sent from my Galaxy Exhibit 4G
If you didn't install a ROM and just did a backup your batt is prob just dead try leaving it charged for a few hours. Doing a backup won't brick your phone
Sent from my SGH-T679 using xda premium
Yeah if its a backup then you can't brick your phone doing it. Sounded to me like you were installing a rom when it happened though?
If you want to see if its the battery, go to batteries plus, they will let you try the battery to make sure that is the problem
Sent from my SGH-T679 using xda app-developers app
lovelyles said:
Hi. I'm very new to xdaand unsure how it all works, so please excuse me if my 1st post isn't written with the proper terminology! Ok. So, here's my issue. I, have the Samsung Galaxy Exhibit 4g. It, was rooted with cwm, running on jellybean 4.1.2. Recently, I was installing a new rom, from Slim. I, found it on xda. I, believe it's called Black Out. I, was doing a backup, while, in cwm recovery mode, and I happened to fall asleep in the middle of the backup. I, woke up an hr or so later, only to discover my phone completely turned off and wouldn't turn back on! I, had a full battery. I, have tried on numerous occassions to leave the battery out for several hrs and replace it, but still nothing! I've used different chargers and still nothing. Not, even a light blinks! The only thing, I haven't tried is replacing the battery. The phone is only 3-4mo old, so I didn't think it would be the battery. I've never seen this happen before! The ROM, didn't even get installed! I've searched high and low about my problem, and haven't come across not 1 solution! Could, this just be a case of a bad battery, or of a bigger issue?? I'm still under waranty but of course already being rooted, and having no way to get into my phone to unroot, I've voided that! PLEASE, if anyone can help with some support I'd GRATELY appreciate it! Anything, that can help save me $, would be wonderful! Thank you!
Click to expand...
Click to collapse
If you didn't install the ROM try another battery try getting the premium battrey got one 2 wks ago and works good even has a chip in it that prevents the battery from over heating Which probley happened in your situation.
---------- Post added at 05:52 PM ---------- Previous post was at 05:42 PM ----------
lovelyles said:
Hi. I'm very new to xdaand unsure how it all works, so please excuse me if my 1st post isn't written with the proper terminology! Ok. So, here's my issue. I, have the Samsung Galaxy Exhibit 4g. It, was rooted with cwm, running on jellybean 4.1.2. Recently, I was installing a new rom, from Slim. I, found it on xda. I, believe it's called Black Out. I, was doing a backup, while, in cwm recovery mode, and I happened to fall asleep in the middle of the backup. I, woke up an hr or so later, only to discover my phone completely turned off and wouldn't turn back on! I, had a full battery. I, have tried on numerous occassions to leave the battery out for several hrs and replace it, but still nothing! I've used different chargers and still nothing. Not, even a light blinks! The only thing, I haven't tried is replacing the battery. The phone is only 3-4mo old, so I didn't think it would be the battery. I've never seen this happen before! The ROM, didn't even get installed! I've searched high and low about my problem, and haven't come across not 1 solution! Could, this just be a case of a bad battery, or of a bigger issue?? I'm still under waranty but of course already being rooted, and having no way to get into my phone to unroot, I've voided that! PLEASE, if anyone can help with some support I'd GRATELY appreciate it! Anything, that can help save me $, would be wonderful! Thank you!
Click to expand...
Click to collapse
If you didn't install the ROM try another battery try getting the premium battrey got one 2 wks ago and works good even has a chip in it that prevents the battery from over heating Which probley happened in your situation.
BrandonCormier said:
Sounds like you may have installed a rom for a different phone as I have not heard of a slim blackout rom. I am sorry to say you probably bricked your device. If it doesn't even power on them you have no way of getting into Odin mode.
Sent from my Galaxy Exhibit 4G
Click to expand...
Click to collapse
Yes, I did notice it wasn't the correct rom for my device afterwards But I never got the chance to install the rom. It was on my sd card but never updated. I was in the middle of backing up my phone, on a full battery before it just went dead! I'm going to try a new battery and see if that was the problem. I hope so! Thank you for your advice!