Develop Bugs

[Q] Galaxy Nexus won't turn on after attempting a flash stock + Unroot???

So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.

you cant get into to recovery either? or fastboot mode?

k786 said:
you cant get into to recovery either? or fastboot mode?
Click to expand...
Click to collapse
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.

AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
Then I am afraid you're hard bricked pal
Sent from my GNexus

AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
what about fastboot mode?

Same
AdmiralAqbar said:
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
Click to expand...
Click to collapse
I'm having a similar issue. I wanted to flash the memory so i relocked the phone using the wugkit, then unlocked and rooted. For some reason, it wouldn't load a new rom. I kept getting the triangle exclamation point android graphic. I pulled the battery and that was it. Black screen. Won't turn on. A cpl of times, it was almost recognized by the computer via USB, but just kept failing. This sucks.

cyberelli said:
just a thought: are you sure it's charged up enough to boot? i know i've mistakenly thought my phone was messed up when the battery was just dead
Click to expand...
Click to collapse
Yes the battery is charged. Occassionally, when I plug it into the computer, it makes the new device notification and then fails over and over again. I keep trying to get a glimpse of a lock so i can adb it.

[Q]Rogers Galaxy S3 constantly restarting even in recovery/download mode

So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.

Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.

There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.

Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.

[Q] Bricked Samsung Note 2

Hello everyone.
I have a rooted note 2. Rooted it about 6 months ago, and it have been working without any problems.
Then last night my phone worked fine, no problems at all. Then i wake up this morning, and my phone is turned of.
Tried to turn it back on but when it starts up, I am stuck on my rooms logo. Can't get past it. Then i went to recovery mode (Power+Home+VolumeUp) And did a clear catche. Then did a reboot. And my screen just turned black. Can't turn it on. Now it's just bricked. It wont even charge. When i try to start it up, pushing the home button nothing happens, only the red led light is blinking. Otherwise it is completely bricked. Please, what can i do? I am traveling in Thailand atm. and are so dependent on my phone. This is a really big problem.
Thanks for the help.
Regards Andy

solving soft break
Here have 2 method
1. flash official stock rom through ordin
2. flash stock or other custom kernel through ordin or recovery
than you will solve the brick

i think your phone got SDS.
the only solution is to change your motherboard.
read this thread for more info about SDS.

But when i hold Power+Home+VolumeDown. It doesn't react. The phone is completely dead. Doesn't respond to anything. So how can i flash official stock rom?

sora9009 said:
i think your phone got SDS.
the only solution is to change your motherboard.
read this thread for more info about SDS.
Click to expand...
Click to collapse
OMG. Really hope that this isn't the case.
So weird, last night no problems. Then the next morning it's SDS. LOL

McAndy87 said:
Hello everyone.
I have a rooted note 2. Rooted it about 6 months ago, and it have been working without any problems.
Then last night my phone worked fine, no problems at all. Then i wake up this morning, and my phone is turned of.
Tried to turn it back on but when it starts up, I am stuck on my rooms logo. Can't get past it. Then i went to recovery mode (Power+Home+VolumeUp) And did a clear catche. Then did a reboot. And my screen just turned black. Can't turn it on. Now it's just bricked. It wont even charge. When i try to start it up, pushing the home button nothing happens, only the red led light is blinking. Otherwise it is completely bricked. Please, what can i do? I am traveling in Thailand atm. and are so dependent on my phone. This is a really big problem.
Thanks for the help.
Regards Andy
Click to expand...
Click to collapse
this might help you
http://www.youtube.com/watch?v=0U3x9f_0qLM

But my phone doesn't respond to anything. And i need to get it in recovery mode to unbrick it.
Think that i have SDS though. Really sucks. This is my first and last samsung phone i will ever buy.
Have had so many problems with my Note 2.
Gonna buy the Sony Xperia Z1 next month.

McAndy87 said:
But my phone doesn't respond to anything. And i need to get it in recovery mode to unbrick it.
Think that i have SDS though. Really sucks. This is my first and last samsung phone i will ever buy.
Have had so many problems with my Note 2.
Gonna buy the Sony Xperia Z1 next month.
Click to expand...
Click to collapse
Can you get into download mode. ? If so you may be able to flash stock via Odin.

Constantly rebooting (stock, nonrooted, no physical damage)

here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?

ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
there was an ota update a bit ago, 4.3...um, is it under warranty or does she have insurance, if so, go to the sprint techs and have them look at it, if not, what you can do/try for it is to completely flash the 4.3 ota update again using odin and download mode...you can do this by clicking on the 2nd link in my signature and see what happens, fixed my phone like this after 4.3 and myself messed it up lol and it's the exact same thing the sprint techs would do for it if you brought it in
so there's your options man...good luck, any questions just post up but the guide is very simple and straight fwd to follow and I provided all that is needed in my download bundle from my dropbox account
edit...if you can't boot up to enable the usb debugging mode, it should still work but it's recommended to do but again, shouldn't really matter, as long as it boots into download mode you should be ready to go

ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
This isn't an uncommon problem with the S3. I just recently went through this. In my case, and in many other cases, it's a faulty motherboard. Nothing you can do to fix it other than get Sprint to replace the handset.
For me, if I left it completely off for a long time, when I turned it back in it was stable for a couple of hours. Not sure if it was a coincidence, happened a couple of times that way.

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .

Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.

maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)

DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.

This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.

What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!

LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!

DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.

DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.

DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited

Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.