Database Develop

blue screen brick?

i was restoring to jf6 with the one click downloader and halfway through the phone turned to a bluish black screen. i let it sit here for 10 min but the restore had stopped so i unplugged it and took out the battery and then tryed to turn it back on and nothing happens. Has this happened to anyone else?

Your phone is bricked. This happened to me about a week ago. Had to take it to the att store for a replacement.
Sent from my SAMSUNG-SGH-I897 using XDA App

it is NOT bricked. if you read around the forums there are several posts about this. but the gist is put it back in download mode (same as always) and you will be fine.
And yes I know this works, I had the same issue myself a few weeks back.

yep. not bricked.
i had a green screen the other day. i was in the middle of a one click restore and all the USB ports stopped working on my desktop (office PC). Used the USB+Button method to get back into download mode and everything worked

the problem is when i plug it in and try to go into download absolutely nothing happens i dont even get that computer ! phone screen

igm503 said:
the problem is when i plug it in and try to go into download absolutely nothing happens i dont even get that computer ! phone screen
Click to expand...
Click to collapse
I know what you're saying. When this happened to me the phone was completely dead. It would not turn on no matter what I tried, and I tried every method I could find in XDA. There was no fixing it, so I had to return it for a new one.

Not booting (into anything)

My phones battery died over the weekend, I got it charged back up, the phone was acting real sluggish so I restarted it, came back a few hours later and noticed it was still on the white HTC screen, I watched it for a few minutes and noticed it would sit on this screen for about a minute, then go dark, then back to the HTC screen and we go round and round.
I tried hboot, all the options do this. Fastboot, recovery even factory restore all trigger this infinite loop...
What has happened? How can I fix this?
Note that it was a stock phone, no mods, no custom ROMs or anything else. It was OTA updated to ICS about a week ago, and has been fine since then.

echodreamz said:
My phones battery died over the weekend, I got it charged back up, the phone was acting real sluggish so I restarted it, came back a few hours later and noticed it was still on the white HTC screen, I watched it for a few minutes and noticed it would sit on this screen for about a minute, then go dark, then back to the HTC screen and we go round and round.
I tried hboot, all the options do this. Fastboot, recovery even factory restore all trigger this infinite loop...
What has happened? How can I fix this?
Note that it was a stock phone, no mods, no custom ROMs or anything else. It was OTA updated to ICS about a week ago, and has been fine since then.
Click to expand...
Click to collapse
So can you get to the bootloader and send fastboot commands?

Sorry I am not a modder or anything like that, do you mean select the "fastboot" option?
I tried running fastboot reboot from my PC while it was plugged in and my phone was in the hboot area, and it just says "waiting for device" and never does anything.
If I select "fastboot" from the hboot menu the phone restarts, a bar goes up the side of the HTC screen then about 30 or so seconds later it goes black and repeats process.

Ah, yes I can. I figured it out, plug into USB, select fastboot, then it goes to USB. I was able to reboot the phone.
EDIT: Tried running the update from HTC's website, took it about 5 - 10 minutes or so. It completed without issues, however the phone is still doing this infinite rebooting cycle...

You mean the RUU? And for ICS? That is supposed to be the ultimate method to unbrick and return to stock. Sounds like the OTA messed something up. When you say go dark you mean the screen goes of then it comes back to the HTC screen? This is probably obvious but have you tried a battery pull? Taking out aim card anything is worth a shot.
Sent from my HTC PH39100 using xda premium

Yes the RUU update from HTC's website. The phone started this morning without issues. Then after a restart it starts the whole cycle over again.

[Q] Rogers i896 will not boot and computer does not recognize phone

I have had my captivate for 1.5 years and I have never done anything to it. A little while ago it would start to pop up with an error about twlauncher or something like that. That would happen multiple times per day. I held the volume buttons and powered it on to get to the screen that lets me restore. I did that and the problem did not go away. I didnt care though because the phone still worked.
2 weeks ago I turned it on and it would not boot past the initial screen. I can still get into the volume up/down power screen and all of my buttons still work. I tried to reset the phone and it still wont go past the "i896 samsung" screen.
Also my computer will not recognize my phone. It hasnt been recognized in some time.
Any suggestions would be greatly appreciated.
I am going to get the Note2 when it releases, but I have been reduced to using my caveman Iphone 3g while I wait. That thing is 5 years old and the battery wont last for more than 30 minutes with the screen on.

If factory reset/ wipe data will not do anything to help u get it booted, then u could put it into Download Mode and flash a Stock firmware and that should get ya up and going.
TRusselo has Rogers Stock firmware links...see Post #4 in the Stock Roms stickied thread in the Dev forum.
Sent from my SAMSUNG-SGH-I897 using xda premium

Note Stuck on booting strange one..

Im on the the official N7000XXLSZ rom and ive been on it for the past few weeks. Before that I did play about with the super nexus rom but flash it back to normal because I missed the pen. (no root)
Its been working really well up until today when it kept on some how rebooting in to the samsung logo. then it would be ok for a few minutes then the home button wouldnt work to wake the device up. When I hit the power button it would come on after 5 seconds.
So I tried taking the battery out and back in but now its stuck on the Samsung Galaxy Note GT n7000 screen. I've tried clearing the cache but no joy?
Any ideas? I've done everything ok with the modding on safe kernals and its been working perfectly for the past 3 weeks. Very strange
Any help would be great, i dont really want to wipe the device. Is JB safe to wipe on??
Cheers
Baker0

Fixed it in the end by wiping.
Sent from my GT-N7000 using xda app-developers app

its happen again... the battery was on 1% and I shut the phone down. I charged it fully and through out the day it kept on rebooting and getting pretty hot. With very light use it went down to 5% after 5 hours. What can be causing this?? the SD card was also playing up so Im currenty wiping to see if that helps.

Came across a new problem I can't find anywhere else.

I've recently come across a new issue on my T-mobile Galaxy Note 4 that I haven't seen before. I've been searching online as well and can't seem to find anyone else posting about this problem either. I'm not the best but I have some experience. I've recently rooted and flashed tekxodus hybrid n4 5 1 1 rom on my note 4 through TWRP recovery. It took a few tries but everything worked. After using it for 3 days, I decided to turn it off and hard reboot it which I've done plenty of times before. But this time, upon rebooting it starts up and shows the tmobile logo screen and turns black. Vibrates twice as if you plugged it into the charger but remains black, and stays that way. If i plug it into the charger it shows the green battery screen and charges normally. I can enter twrp recovery and download mode as well. But it just can't get past the logo screen. I've also tried using a different note 4 battery from other videos, clearing the cache, delvik-cache, but nothing seems to work. As earlier mentioned, I can't seem to find any other post with this exact problem so I've come to reddit for help. Thank you in advance for any feedback.

You try flashing backup/ Odin stock?

yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk

Bruce lee roy said:
You try flashing backup/ Odin stock?
Click to expand...
Click to collapse
Yeah, unfortunately that's what I had to do. I was trying to figure any other option other than having to reflash everything. Thanks for the tip though

ayeitschris said:
yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw

Try flashing another kernel, sounds like that could be the culprit
JonakaJon said:
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw
Click to expand...
Click to collapse