Database Info

bricked sensation

i have sensation from last 3 months all was going smooth...but recently 2 days back when i wake up in morning my phone was off i tried to power on but no boot then i connected it to wall chager for around 1 hour but no luck ....phone is not booting ..not able to go in bootloader
can someone help me .

did you pull the battery and put it back on then put it on the charger?
I have had the problem when it completely dies it will not charge until the battery is pulled out and put back in. Scared me a few times too.

You should definatly pull the battery and put it back on then put it on the charger.

additionally, holding down
volume up
volume down
power
buttons simultaneously for a few secs will mostly reboot the sensation (kinda like CTRL-ALT-DEL). That way you can avoid opening your phone everytime it crashes

You now are aware that modern batteries don't respond well to going flat - try not to do it

ptschack said:
additionally, holding down
volume up
volume down
power
buttons simultaneously for a few secs will mostly reboot the sensation (kinda like CTRL-ALT-DEL). That way you can avoid opening your phone everytime it crashes
Click to expand...
Click to collapse
For some reason, this rarely ever works for me and I wind up having to pull the battery. It works fine when there is no reason for a battery pull.

mrg02d said:
For some reason, this rarely ever works for me and I wind up having to pull the battery. It works fine when there is no reason for a battery pull.
Click to expand...
Click to collapse
Ditto, I usually try to use adb to run "adb reboot" or "adb reboot recovery", if I am around my netbook. ADB works 80% of the time

I thought I was going there when I started boot looping on my initial ICS install. A rather overconfident decision re Super Cid and the 3.24 firmware that failed after I had already flashed my first Rom.
It took me several hours of hunting and I very nearly went to the used phone shop for a cheapo to replace it - then I discovered the adb fastboot threads. If you are very stuck I really suggest trying it in a very step by step way. Perhaps find the commands to help you there. Then you may be able to root, supercid etc and reflash a rom that gets you oin your feet again.
I do hope this works for you.

thanks for all ur replies tried adb reboot bootloader commands with putting a new battery in phone now phone is booting ..
once again thanks.

G2x - overheat, won't reboot

Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks

Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
If you don't mind losing your internal sd card data you can try this and then flash the rom again to see if it fixes it.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA

I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?

Xura08 said:
I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?
Click to expand...
Click to collapse
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA

mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Actually most of the time you will be fine if you send in a rooted phone. There was a thread about this.
Sent from my Handheld Portal Device

mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!

Xura08 said:
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!
Click to expand...
Click to collapse
You can use the reference link in the batch cleanup op. That one pushes stock 2.3.3. I don't think it is rooted either.
Does your phone boot loop or does it boot back into recovery?
Sent from my LG-P999 using XDA

bootloop. I can't get it to go into recovery. It won't bootloop, or boot at all, unless plugged into a power source. Does that sound like possibly a failed battery? It was taking forever to charge and whatnot a few weeks prior..

Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.

let it charge for $15 mins and redo CWM recovery again.
6 month ago one of my friend g2x fried up the main boardduring charge, I have to paid $100 for broken phone to get the main board replaced

Blazing angel said:
Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.
Click to expand...
Click to collapse
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile

Xura08 said:
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile
Click to expand...
Click to collapse
No problem. I was pulling my hair out when my phone did it too. It took a lot of experimentation to figure it out!
Now, onto the next problem. I suggest you run the g2x nullifier script to clean out anything on the rom. It might be messing with the phone. Then flash something known to be stable!
My phone also did the 999% thing. It was messing up a lot too, but the nullifier fixed it. Try it out

Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
This SAME EXACT thing is happening to me except I had NO issues with the phone before. The battery had died down after a normal day of use, I charged it that night and then I wake up to it not powering on. Then with charger only a continuous bootloop of the white LG logo

Note 10.1 not Powering

I have a 3 week old Note 10.1 with rooted ROM that will not power on. It was put on the charger overnight with battery depleted (should have charged it before it went completed out.)
In the morning I unplugged it and turned it off before putting it it a sleeve. When I went to turn it on in the afternoon, it doesn't do anything to indicate turning on or waking up. I have it on the charger again, but nothing shows to indicate that a connection to the charger is being made on the Note 10.1
I will need to return it to Bestbuy, but can't do it in it's current stage as it's rooted and has my personal data still intact. Can anyone please suggest any options, I tried few that I had read about (holding power button for 30 seconds and touching the screen, attempt to go into recovery) but none pans out.
Thanks
Dave

Try plugging it into the computer to see if it shows up. If it does, try erasing the cache on it to see if that fixes it.
Sent from my EVO using xda app-developers app

plegrand said:
Try plugging it into the computer to see if it shows up. If it does, try erasing the cache on it to see if that fixes it.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately have the same result. Its seems as dead as a nail

Even in odin?
Plug in an otg cable with something lightey (led) to see if the mainboard doing basic jobs.

Can you get into either download (power/vol down) or recovery (power/vol up)? If you can get into recovery, try dirty flashing your ROM. If you can get into download, you should be able to Odin back to stock, though you will lose whatever data you have on your device.

Thanks for all the suggestions, greatly appreciated! Last night I decided to put it back on the charger one more time just to make sure it had juice in the morning to attempt the "finger on the screen and power button" option. It kept just flashing "Samsung Note 10.1" text for few seconds without going any further. I then decided to try "power button" and "volume up" option, took me to the "downloading" screen as it seemed like it was waiting for Odin download. I then proceeded to turn off the tablet and rebooting, which then took me to normal boot up. System indicated charge of 96%, this must have been what I have been reading online (Screen of Death or deep sleep.) I then did a restart to recovery, to perform restore from an backup that was done prior to root. After going thru all the clearing cache etc... and the tablet started to perform the restore, system shut itself and now I have nothing again.
When I was doing the restore from backup, I did not have the tablet connected to any usb connection, maybe that 96% battery was false or something. I put the unit back on the on the power charger again (thinking the battery is depleted again.) Very frustrating, I just want to unroot this tablet and take it back now to Bestbuy.

reminds me on what happened with my note. But for me I thought: "naah, you aren't dead. You're my new babe."
I flashed it immediately after buying and so far... odin always helped. With stock kernel most roms work. Some overclock kernels freeze my note or it isn't bootable 'til stock flash.
edit: you should add a [Solved] into your threadtitle.

Sorry not yet fixed, as mentioned its back on the charger and dead as a nail again.
Sent from my Nexus 4 using xda app-developers app

Try plugging it in and using adb command to get the list of devices and see if it shows up.
Sent from my EVO using xda app-developers app

unodish said:
Thanks for all the suggestions, greatly appreciated! Last night I decided to put it back on the charger one more time just to make sure it had juice in the morning to attempt the "finger on the screen and power button" option. It kept just flashing "Samsung Note 10.1" text for few seconds without going any further. I then decided to try "power button" and "volume up" option, took me to the "downloading" screen as it seemed like it was waiting for Odin download. I then proceeded to turn off the tablet and rebooting, which then took me to normal boot up. System indicated charge of 96%, this must have been what I have been reading online (Screen of Death or deep sleep.) I then did a restart to recovery, to perform restore from an backup that was done prior to root. After going thru all the clearing cache etc... and the tablet started to perform the restore, system shut itself and now I have nothing again.
When I was doing the restore from backup, I did not have the tablet connected to any usb connection, maybe that 96% battery was false or something. I put the unit back on the on the power charger again (thinking the battery is depleted again.) Very frustrating, I just want to unroot this tablet and take it back now to Bestbuy.
Click to expand...
Click to collapse
didn't think Best Buy would take stuff back after 3 weeks. Thought u only had 15 days.

I believe premier members get 60 days for returns

plegrand said:
Try plugging it in and using adb command to get the list of devices and see if it shows up.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Attempted to check for devices using adb, nothing at all listed under attached devices after entering "./adb devices" command. I think the board might have gone bad, as the tablet will not boot at all now, even after 8 hours of overnight charging, it's dead. Is there anything I can attempt to revive so I can unroot it, to take it back for refund? Thanks in advance

I'd take it back to the store and see if the Geek Squad can get it to power up. If they can't then they'll never know you rooted it anyway and you can swap it for a new one. Assuming that it's still in the zone or return/swap of course.

jusliloleme said:
I'd take it back to the store and see if the Geek Squad can get it to power up. If they can't then they'll never know you rooted it anyway and you can swap it for a new one. Assuming that it's still in the zone or return/swap of course.
Click to expand...
Click to collapse
I was thinking of doing that, just was worried what the consequences might be if they would to find out it was rooted later down the line. It's still in the return/exchange window. I guess I'll be taking that chance with them, if they get it to boot, I'll be happy with that and re-store to stock.

[Q] Rebooting phone causes pseudo-brick

This is going to be a long question/story thanks for your patience!
Whenever i try to reboot my phone, regardless of method, it takes an elaborate set of actions (elaborate as in it requires a power cord, a complex series of button presses, chanting, chicken blood, etc...) for the phone to turn back on.
I'm going to include a lot of details, relevant or not, i cannot decide.
I was using SlimBean Build 7 for weeks. I was able to reboot normally. I had heard about an app, WifiKill, installed it, caused short lived havoc at work, no issues so far. A few hours later, I attempted to tether my laptop using the hotspot function (something I've done many times before with no problem). The wifi turned off immediately and would not come back on. My exact thought was "Huh, that's weird" and attempted to reboot the phone, it seemed to shut off normally but did not come back on. At this point i believe the battery was at 60% or close to it.
No matter how I tried the phone would not power back on.
I charged the phone over night, and it actually came back on. Of course the first thing I tried to do was reboot the phone. Same result.
Now the phone is still not starting when turn off or rebooted with the power button command, it will not reboot when done with adb, it will not reboot when I try within the recovery. Any of these things cause the phone to act as if "hard bricked" with no response from any of the buttons or screen.
My first thought was to flash a stock rom with odin, when i plugged it into my PC (windows 7 ultimate 64bit) it asked for QHSUSB_DLOAD drivers. I tracked those down and installed them of course they did not work for odin.
I ordered but have not received a download mode jig.
I thought maybe it had to do with the act of charging the phone that sparked the brief show of life so i drained my battery using another phone and then charged it in the skyrocket for two days. Battery at 100% at this point.
At this point, I've discovered that if I hold the power button long enough while plugged in the phone will vibrate over and over until the button is released and by accident I learned that if i unplug the phone wile doing it's little vibro-trance it will start normally.
If I try to reboot the phone with any of the methods I listed above, I have to pull the battery, wait 10 minutes, plug in a power cord (not connected to a computer) hold the vol+ and vol- and power buttons, wait till it starts buzzing and insert the battery, if the charging icon appears the phone will power on, if not, I have to start again.
Once I learned that trick I was able to boot the phone into download mode and flashed back to stock JB and twrp.
I have since flashed slimbean build 8 and twrp 2.6.0.0. The phone is working fine but I don't have the guts to attempt WifiKill, tethering or reboot.
If you're still with me, good on you. I think the universe is mad at me for messing with people's wifi connection.
Anybody got any ideas?
THANK YOU!!!

ilike3point14 said:
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, I'm guessing that wifi kill app had something to do with it. I've tethered on slim bean 7 & 8, so I doubt it has anything to do with that or the ROM. Is say it's like you said, karma rearing its ugly head for playing wifi gatekeeper on unsuspecting individuals
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Damn phone stuck in bootloop!

Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.

thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).

follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...

Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.

My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app

bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????

My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app

This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.

Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?