Develop Bugs

Phone Not Booting - Very Weird Issue

I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?

OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.

Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.

OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).

aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.

OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.

hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.

My Screen Died

Ok, so to clean my S3, I splashed little drops of water on it and rubbed it then dried it (I do this pretty often). 30 min later lines flickered on the screen while I was browsing for about a second then it went black. I immediately removed the battery, put the phone on my heater for about 5 min. Then tried booting but screen still off. I tried 2 more time in a couple of minutes then put it in rice for the night. Got back from school and tried booting but screen still blank. Download mode and recovery doesn't work either. The touch screen is still functional tough.
I am pretty sure I ticked the counter wile flashing and I am on rooted stock rom. I tried using odin but i get this message
Can't open the specified file. (Line: 1949)
I am thinking of returning it to Telus and maybe they might fix it but i need to find a way to return it to stock.
Any ideas?

I managed to flash stock rom so I am no longer rooted. Now i just need to reset the counter

Woblebox said:
I managed to flash stock rom so I am no longer rooted. Now i just need to reset the counter
Click to expand...
Click to collapse
Sounds like your LCD's gone. Normally, flashing a complete stock image like the 4.3 stock restore would remove root, install factory settings and install stock recovery. The only thing that cannot be reversed once tripped is the warranty bit. For older ROMs you could run Triangle Away. Unfortunately, however, you would need to see what you are doing on the screen.

Larry2999 said:
Sounds like your LCD's gone. Normally, flashing a complete stock image like the 4.3 stock restore would remove root, install factory settings and install stock recovery. The only thing that cannot be reversed once tripped is the warranty bit. For older ROMs you could run Triangle Away. Unfortunately, however, you would need to see what you are doing on the screen.
Click to expand...
Click to collapse
thanks, I didn't know that. But too late =( they wouldn't repair it because it's physical damage

Continuous reboot out of box T Mobile Note 3

I purchased two note 3's. The black one boots up fine on 4.4.2 just fine, but the white one however out of the box
experienced serious rebooting issue that almost made it impossible to root and attempt to tweak. Both these phones were factory sealed in the box. I was eventually able to get white note 3 rooted. I unlocked using chainfires region unlock.apk, and sure enough that unlocked the phone
domestically for use on At&t's network. However, when I attempted to flash back to Jelly Bean modem the phone accepted modem, but still had reboot issue. I tried to install HyperDrive Rom, and even that couldn't fix reboot issue. I turned OFF wifi scanning, and all of the other tricks that have helped people, but this phone continues to reboot about 30 seconds to 1 minute into main screen boot. Any IDEAS??
I am open to trying a myriad of ideas to fix this, I really need to get fixed to sell ASAP. Thanks for your help!
Neither of these phones can be sent back to Samsung. Need to fix myself
Thanks:good:

twill1987 said:
I purchased two note 3's. The black one boots up fine on 4.4.2 just fine, but the white one however out of the box
experienced serious rebooting issue that almost made it impossible to root and attempt to tweak. Both these phones were factory sealed in the box. I was eventually able to get white note 3 rooted. I unlocked using chainfires region unlock.apk, and sure enough that unlocked the phone
domestically for use on At&t's network. However, when I attempted to flash back to Jelly Bean modem the phone accepted modem, but still had reboot issue. I tried to install HyperDrive Rom, and even that couldn't fix reboot issue. I turned OFF wifi scanning, and all of the other tricks that have helped people, but this phone continues to reboot about 30 seconds to 1 minute into main screen boot. Any IDEAS??
I am open to trying a myriad of ideas to fix this, I really need to get fixed to sell ASAP. Thanks for your help!
Neither of these phones can be sent back to Samsung. Need to fix myself
Thanks:good:
Click to expand...
Click to collapse
So u have a recovery on the device? If so, try this zip out.. https://www.dropbox.com/s/okx7op92cirn3l1/Brick_Loop_FIX_afterRestoringBackup.zip

Have you reset it from the menu or have you full restored to stock

mrej201 said:
Have you reset it from the menu or have you full restored to stock
Click to expand...
Click to collapse
Thanks for your help guys. Yes, I have performed a factory reset. Flashed stock firmware in Odin and Heimdall, flashed JB modem. Rooted, flashed Hyperdrive Rom, turned wifi scanning to off, and seriously tried every trick in the book. Perhaps try another rom on JB? I've heard some Note 3's have a Kitkat issue. Someone suggested hardware could be faulty but that doesn't add up since the phone doesn't reboot in download or recovery mode..

downgrading sgh-m919 from 4.4.4 to 4.4.2 for towel root guide

i just recently got a replacement galaxy s4 from tmobile because of a manufacturer defect. when this phone was shipped and i received it the stock firmware was the dreaded 4.4.4 firmware which breaks functionality with towelroot. i was somewhat dismayed because i really wanted to root my replacement without tripping the knox counter on my phone like before in case i have another problem (3rd galaxy s4 in about 1 year exact, first 2 both had same manufacturer defect. it was the "sim card has been removed error" which i can confirm after speaking to advanced technical support from tmobile that a defective batch of samsung galaxy s4's was sent to tmobile and they were extremely helpful and understanding.) Since rooting 4.4.4 is impossible to do without tripping knox (to my knowledge) i was looking for a way to downgrade to 4.4.2 without voiding the warranty. i can also confirm that according to samsung and tmobile downgrading to an official firmware will not void any kind of warranty as long as there is no custom recovery or anything of sort. i had read over other forums that people were having trouble with knox and the counter and a few other things and downgrading and even read some that: some people tripped the counter, was completely impossible to do, or would still be unable to root. all of this dashed my hopes of rooting and maintaining my warranty. i still wanted to try and after talking to tmobile and samsung gave it a try.
These are the steps i used and i hope they can help others who want to maintain their warranty while rooting after updating to 4.4.4 and finding out they might be in a hopeless situation.
~Things you will need: odin3, stock firmware 4.4.2 for sgh-m919 (can be downloaded from several places, good place to start is sammobile), windows computer, charging and sync/charging cable, your sgh-m919
Step 1: open odin on your computer and connect phone in odin mode (volume down+ power+ home)
Step 2: in pda option select the official stock firmware you downloaded before and click start
Step 3: it should start pretty quickly but if you notice no progress for a few minutes then check and see if you have text in the bottom left corner saying "get pit for mapping". if that is the case i had the same issue and all i had to to do was switch what usb port my phone was connected to on my computer and click start again.
Step 4: this where i had some more issues. after the phone reboots after odin is done i got stuck in a weird boot loop i believe and somehow fixed it pretty easily. so after getting stuck in the boot loop i removed my battery and then put it back and and tried booting in to recovery mode to perform a factory reset. i unfortunately was able to get to download mode. every time i tried it would it was recovery booting and then completely reboot. i tried several times with no luck. so i tried to see if odin mode would work and it did. so i held the power button and did a regular boot and removed the battery and put it back in and then tried to boot into recovery mode and it worked just fine this time.
Step 5: after reaching recovery mode again you will want to perform a factory reset. after it is done select the reboot phone option.
And that's all i had to do to downgrade. you should be on stock 4.4.2 firmware
i can confirm that after using this method i was able to root with towelroot and have not tripped knox
i have no idea if this will work on other samsung galaxy s4 models and do advise caution when flashing any kind of firmware without confirmation that it will work on your phone model
i have no idea if this has been covered but was unable to find anything myself after countless hours of searching the internet and hope that by creating this it will pop up in a search with key words pertaining to this issue in order to help people who just cant find this exactly while searching.
i would love to know if this works for any other galaxy s4 models so we can spread sneaking behind knox security to root without tripping the knox counter ( keep in mind that any form of custom recovery will trip knox)
hope this helps someone

Set warranty bit kernel rooted note 3 N900T

I have previously rooted and been running darklordn5 custom rom with TWRP recovery on Note 3 N900T. I dropped the phone and messed up the screen, it was still working otherwise. Replaced with new screen, lcd digitizer. Powered phone on and was stuck in loop set warranty bit kernel with the note 3 logo, just kept cycling through that. I was able to boot into recovery and backed up the darklord rom thrpugh TWRP. I reinstalled factory firmware and phone starts fine. Flashed TWRP and installed SuperSu updated zip. Rebooted and updated SuperSu through play store. Updated SuperSu binary and rebooted. Root verified. Restored darklord rom back up through TWRP, same issue, set warranty bit kernal and continues to loop on that. Reflashed stock rom several times, did factory reset, advanced wipe (dalvik, system, data and cache) tried reinstalling darklord rom fresh, same results. Seems i can root no problem, but can't flash custom recoveries. Don't understand why it worked before but not now. Am i missing something? Of note, I think I messed up the vibration motor when putting it in new screen/lcd frame, don't know if that would have caused this problem though. Help please, I want my note 5 edge back.

You were able to install TWRP and install supersu from recovery so I'm not sure what you mean when you say "but can't flash custom recoveries".

I can install the custom rom in TWRP. When it is done and I reboot system that's when it shows warranty bit set kernel and displays the Samsung note 3 logo...sits there for a few moments then restarts again, it continues doing this loop over and over. I have followed other advice to go into download mode then press down volume to restart, still same problem. I have to reinstall stock firmware (lollipop 5.0 N900TUVUFOL1) to get the phone to boot up.

Sounds to me like the backup is not being restored properly. You may have to start from the beginning again.

I have tried from scratch as well. The thing is, the custom rom was fine before I replaced the front part of the phone (sccreen with frame and lcd/digitizer assembly). I know this because I was still receiving calls, texts, notifications etc before I powered the phone off for the repair. After the replacement is when I encountered the problem. Could this change have corrupted something internally?

UPDATE!!! I swapped everything back to my old phone and it boots up...So why would new digitizer and frame assembly cause a conflict with my custom Rom? Also my phone is T Moblie branded but has ATT stamped inthe frame the replacement was LTE ??? could this have caused the problem...also the framebon the replacement is thicker than my original an the back does not fit quite right either.

Third party screens can cause all sorts of problems and it seems that the replacement screen doesn't work properly with the hardware.
The 900T and 900A have many interchangeable parts.
To confirm the motherboard's model #, boot into download and look at the model # displayed.

I think that the unbranded LCD is definitely the issue...I just went ahead and found a brand new, unused Note 3 for $210.00 on ebay and will root and start over fresh...root then custom rom.