HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Good point cindy if its an internal hardware issue verizon will replace it at no charge
From my Wicked S3 running MIUI
how is this even possible?
gorilla29 said:
HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Click to expand...
Click to collapse
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
cyberkeeper1 said:
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
Click to expand...
Click to collapse
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
I wish it was.
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
No, Cindy, it isn't under warranty anymore. It has been more than one year. I wish it was though!
Thanks, but...
JudgeFutta said:
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
Click to expand...
Click to collapse
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
gorilla29 said:
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Click to expand...
Click to collapse
Try flashing the .tar file from the second post. Also make sure you have odin setup correctly like cyberkeeper1 said.
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
SlimSnoopOS said:
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
Click to expand...
Click to collapse
Many thanks, Slim.
Should be made a sticky. This is important stuff for this phone.
Sent from my SCH-I535 using XDA Free mobile app
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Would the file go under PDA (AP) or BL?
gorilla29 said:
Would the file go under PDA (AP) or BL?
Click to expand...
Click to collapse
PDA (AP)
JudgeFutta said:
PDA (AP)
Click to expand...
Click to collapse
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
gorilla29 said:
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
Click to expand...
Click to collapse
However, the phone will still shut down once booted, despite it being connected to power.
gorilla29 said:
However, the phone will still shut down once booted, despite it being connected to power.
Click to expand...
Click to collapse
It may be the battery or the phone just went out.
JudgeFutta said:
It may be the battery or the phone just went out.
Click to expand...
Click to collapse
Maybe, but the phone never shuts off during recovery. I bet the phone is just done. Lol
Related
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
background: rooted and was running 4.1 stock and CWM 10.0 on verizon gs3. i wanted to bump up to jelly bean 4.2 with CWM 10.1.
first i tried using Rom Manager and Rom Toolkit to flash a new rom. from Rom Manager, i rebooted into recovery and got stuck on the CWM boot screen.
After 30 minutes or so i pulled the battery and tried flashing the stock .tar.md5 using Odin and ended up with this:
"System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help."
now i can't boot into download or recovery. i just have this screen with the yellow exclamation point and the above message.
how screwed am i? i've tried reading everywhere and from what i can gather i didn't wipe my cache sufficiently, but all the other threads just say 'use Odin to get back to stock', but i can't get into download mode so i can't use odin.
please help.
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have noticed that a lot of people have not unlocked the bootloader are posting on here that they have "bricked" their phones.
jmxc23 said:
I have noticed that a lot of people have not unlocked the bootloader posted on here that they have "bricked" their phones.
Click to expand...
Click to collapse
Ha, I agree although I think its occurred in decreasing fashion since August. Being "bricked" is used overeagerly by folks not wholly understanding their situation. You really have to try to brick this device before that word can be used correctly.
Your phone has not been bricked. You will know that you have bricked your phone when you can't turn on your phone at all. No download mode and no recovery mode also no pulling of the battery just a dead phone.
ClockworkMod
When you fix your phone, root then unlock the bootloader... You can try RM again but I believe that it is best to use ClockworkMod (or the Touch version) for flashing instead of ROM Manager - old fashion, maybe, but it works!
NOTE: Once you start flashing it becomes addictive - you have been warned
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
jondotwoz said:
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
Click to expand...
Click to collapse
youll need to put the battery back in......lol
ddurandSGS3 said:
youll need to put the battery back in......lol
Click to expand...
Click to collapse
obviously. i've tried this a million times. It shows the download screen green android robot and the text in the top left for about 4 seconds. then it goes black and the yellow triangle comes back telling me unauthorized software is on there.
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
ddurandSGS3 said:
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
Click to expand...
Click to collapse
thanks that's a very helpful thread. However, i still can't get into download/Odin mode. i'm guessing if/once the USB jig can force the phone into download mode, this is where i'll start.
thanks for everyone's help and patience.
All,
Hopefully this is an easy one. I looked through the board and did not see anything I haven't similar but i can be wrong. Quick background, I rebooted the phone it looked normal on shutdown but it never came back up.. What I have tried is tremove the battery and left it for day and tried to turn on with no luck. A couple of times it showed the battery indicator but would go black screen if i tried to turn it on. I have reloaded the stock rom using ODIN still no luck. The only thing I can make it do is go to the download screen, that's it. This is a stock ATT Skyrocket no mods or anything. It seems to be a software issue but I do not know how to fix it. Any Ideas Thanks
oops!
l33t_killa said:
I'm in the same boat. Root was a confirmed success after the OTA update, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), the Samsung logo comes up before this and it's all that it does now. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. PLEASE HELP.......
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
Click to expand...
Click to collapse
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
xcrazydx said:
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
Click to expand...
Click to collapse
Didn't notice that....
l33t_killa said:
Didn't notice that....
Click to expand...
Click to collapse
Glad I caught it before you bricked using our files. Good luck!
Sent from my GT-P5113 using Tapatalk 4
Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:
error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse
I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..
Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app
I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse
Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.
There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.
Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.
Hello I have tried to avoid posting this at all cost, however after days of relentless research I have drawn a blank. I have a friend who had a Verizon Galaxy S3 and when he went to reboot the phone it went into a boot-loop. Before I had a chance to look at his phone, he took it into a place to get it looked at. After taking it there they returned the phone to him and said that it was hopeless and now the phone would not boot, vibrate, or go into boot into download mode.Soon after this he bought a S4 and gave this one to me. I want to fix the phone so that I can give it to my wife to use, however I need to try to get it going from there. I know that the boot-loop problem was caused from a bad power button, which I successfully changed out. The phone was operating on 4.3 and was never hacked. After many hours of searching I found some really good debricking information including the debrick file for 4.3. I was able to finally get the phone to boot, but not very far, all I was able to get to come up is the following on the Display and I also included a pic:
Boot Recovery Mode
Check Boot Partitions.
Copy from T-Flash.
Boot Recovery..
Write 159488 sectors.
FLASH WRITE FAILURE
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: None
QUALQUAMM Secureboot: Enable
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
This is the first instance when I have had to write a post for help and help I definitely need. Any help is greatly appreciated. Thank you
dkmac said:
Hello I have tried to avoid posting this at all cost, however after days of relentless research I have drawn a blank. I have a friend who had a Verizon Galaxy S3 and when he went to reboot the phone it went into a boot-loop. Before I had a chance to look at his phone, he took it into a place to get it looked at. After taking it there they returned the phone to him and said that it was hopeless and now the phone would not boot, vibrate, or go into boot into download mode.Soon after this he bought a S4 and gave this one to me. I want to fix the phone so that I can give it to my wife to use, however I need to try to get it going from there. I know that the boot-loop problem was caused from a bad power button, which I successfully changed out. The phone was operating on 4.3 and was never hacked. After many hours of searching I found some really good debricking information including the debrick file for 4.3. I was able to finally get the phone to boot, but not very far, all I was able to get to come up is the following on the Display and I also included a pic:
Boot Recovery Mode
Check Boot Partitions.
Copy from T-Flash.
Boot Recovery..
Write 159488 sectors.
FLASH WRITE FAILURE
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: None
QUALQUAMM Secureboot: Enable
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
This is the first instance when I have had to write a post for help and help I definitely need. Any help is greatly appreciated. Thank you
Click to expand...
Click to collapse
you use Odin to flash stock 4.3?
-somebody- said:
you use Odin to flash stock 4.3?
Click to expand...
Click to collapse
Sorry forgot to mention that, yes I did try to use ODIN to flash the stock 4.3, when tried to flash, ODIN would come up with a fail every time. This is where I am really getting stuck. When I boot the phone with the SD card, the information that I gave earlier is all I can get the phone to do. I cannot flash anything to it and it will not go into download mode and I have nothing that I can select from on the phone. Thank you again.
Donny
dkmac said:
Sorry forgot to mention that, yes I did try to use ODIN to flash the stock 4.3, when tried to flash, ODIN would come up with a fail every time. This is where I am really getting stuck. When I boot the phone with the SD card, the information that I gave earlier is all I can get the phone to do. I cannot flash anything to it and it will not go into download mode and I have nothing that I can select from on the phone. Thank you again.
Donny
Click to expand...
Click to collapse
Try to use Odin again and flash the pit file with Odin along with the stock image.
http://forum.xda-developers.com/showthread.php?t=2586319
I'm confused what you're saying though, you can't enter download mode at all? That looks like you're in download mode.
Sent from my SCH-I535 using Tapatalk 2
There's no option in the recovery to boot into download mode? I had a similar problem with 2 older droids (Galaxy Proclaim and ZTE Merit). I screwed around and hard bricked one and soft bricked the other. One would turn on and vibrate but the lit up and stayed black and the other was stuck on a boot loop. Neither could boot into download mode.
Luckily a few days of googling and I found a solution with odin and adbtool... I was able to get them to detect the phones and I used the tool to force one into download mode and Odin to flash firmwares, bootloaders, and roms.
Also do you know was the phone rooted?
Well after several days of trying I am still at square one, I have read and read many post and cannot seem to get anywhere with this darn thing. I get nowhere with Kies, Verizon Tool hangs up at 83% and disconnects, and Odin will not flash anything including a new PIT, which is what it says my phone is missing. I have also attempted to NAND Erase all as suggested in one post and unchecked Re-Partition when trying to install the PIT and new stock ROM provided by the guides.
BadUserName, I was thinking that I was not in download mode because when my phone boots, it comes directly to the screen that I posted in my original post. At the top of the screen it says Boot Recovery Mode so I assumed that it was not in download mode because I never got the other screen that it should have booted to. Again the screen shot that I sent is the only screen that I am able to get it to boot to and will only boot when I use the SD card to boot it from. Any help is greatly appreciated, thank you and take care.
Donny
dkmac said:
Well after several days of trying I am still at square one, I have read and read many post and cannot seem to get anywhere with this darn thing. I get nowhere with Kies, Verizon Tool hangs up at 83% and disconnects, and Odin will not flash anything including a new PIT, which is what it says my phone is missing. I have also attempted to NAND Erase all as suggested in one post and unchecked Re-Partition when trying to install the PIT and new stock ROM provided by the guides.
BadUserName, I was thinking that I was not in download mode because when my phone boots, it comes directly to the screen that I posted in my original post. At the top of the screen it says Boot Recovery Mode so I assumed that it was not in download mode because I never got the other screen that it should have booted to. Again the screen shot that I sent is the only screen that I am able to get it to boot to and will only boot when I use the SD card to boot it from. Any help is greatly appreciated, thank you and take care.
Donny
Click to expand...
Click to collapse
Ya I don't think you're in download either.
So volume down + home + power boots you to that exact same screen?
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Ya I don't think you're in download either.
So volume down + home + power boots you to that exact same screen?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes, even if I boot holding down volume down + home + power it still boots to the same screen shown in the picture that I posted with the text that I posted in the OP. I know that it is having issues with the PIT, but no matter what I do it will not flash a new PIT. I am not sure what 1000phones did, but they did something nasty to this phone. I know the power button is now good because I replaced it with a new one and I am a experienced 2M tech and it responds when I only hit the power button, so I know that what ever the problem is it is software related. I have also tried multiple cords and computers to flash this phone with. All the correct drivers are installed. Again I greatly appreciate any and all help on this one.
Donny
dkmac said:
Yes, even if I boot holding down volume down + home + power it still boots to the same screen shown in the picture that I posted with the text that I posted in the OP. I know that it is having issues with the PIT, but no matter what I do it will not flash a new PIT. I am not sure what 1000phones did, but they did something nasty to this phone. I know the power button is now good because I replaced it with a new one and I am a experienced 2M tech and it responds when I only hit the power button, so I know that what ever the problem is it is software related. I have also tried multiple cords and computers to flash this phone with. All the correct drivers are installed. Again I greatly appreciate any and all help on this one.
Donny
Click to expand...
Click to collapse
Ya, well if you aren't in download mode you can't flash anything from Odin.
Can you make a USB jig from a micro USB cable and try to force it into download mode?
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Ya, well if you aren't in download mode you can't flash anything from Odin.
Can you make a USB jig from a micro USB cable and try to force it into download mode?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I am not too sure how to do that, all that I have read about and tried is using a class 10 micro sd with the debrick file for 4.3, which is what this phone has.
dkmac said:
I am not too sure how to do that, all that I have read about and tried is using a class 10 micro sd with the debrick file for 4.3, which is what this phone has.
Click to expand...
Click to collapse
That's for a hard brick, yours isn't quite hard bricked.
Look up how to make a USB jig, or you can buy it for cheap on Amazon and eBay, but that's what I would try next.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's for a hard brick, yours isn't quite hard bricked.
Look up how to make a USB jig, or you can buy it for cheap on Amazon and eBay, but that's what I would try next.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I did look at how to make one and it seems pretty straight forward and completely doable, however my phone will not even turn-on, vibrate, or charge without the debrick sd card. From what I understood is if the phone will not even respond to anything without the debrick SD in it, it is a hard brick. I am a Noob when it comes to this phone, I was able to help another friend out get his right up, but am stuck on this one. I am use to messing with HTC phones, so I am defiantly learning as I go with this one. Thank you again and do appreciate all your help.
Just added a screenshot of what ODIN is doing no matter whart I do to flash my phone.
Try checking re-partition?
Sent from my Nexus 7 using xda app-developers app
timedroid said:
Try checking re-partition?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately I have tried that with no luck. When I try flashing it with the re-partition checked, ODIN attempts to flash then immediately comes back with a fail. Never have I ran across such a stubborn phone when trying to repair or flash. I think that this is something that has a lot of people stumped at this point. I am still appreciative about any help that will lead me in the right direction. Tomorrow if I get a chance, I am thinking about going to Radio Shack to get the parts I need to build a jig to see if that does anything. Thank you and take care.
Donny
dkmac said:
Unfortunately I have tried that with no luck. When I try flashing it with the re-partition checked, ODIN attempts to flash then immediately comes back with a fail. Never have I ran across such a stubborn phone when trying to repair or flash. I think that this is something that has a lot of people stumped at this point. I am still appreciative about any help that will lead me in the right direction. Tomorrow if I get a chance, I am thinking about going to Radio Shack to get the parts I need to build a jig to see if that does anything. Thank you and take care.
Donny
Click to expand...
Click to collapse
Ya it isn't in download mode so it isn't going to flash.
I think you might be able to get a jtag repair to fix it at this point. I can't think of anything else. if it's hard bricked then you can get a riff box to force a bootloader transfer and boot from your internal card.
Maybe try doing the hardbrick method again after formating your external SD card. Sounds like you're doing everything right.
Sent from my SCH-I535 using Tapatalk 2
Seems like it is on download mode, but can't write anything. Have you tried with NAND erase all checked?
Sent from my SCH-I535 using xda app-developers app
timedroid said:
Seems like it is on download mode, but can't write anything. Have you tried with NAND erase all checked?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It isn't in download mode, it doesn't say "do not turn off target" and it's displaying information about a recovery partition.
It's in some sort of system diagnostic mode. Never anything I've seen before.
Sent from my SCH-I535 using Tapatalk 2
timedroid said:
Seems like it is on download mode, but can't write anything. Have you tried with NAND erase all checked?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
As stated in one of my replied, I did attempt a NAND erase all but with no luck. All I got was a fail in ODIN and the phone displayed erasing in blue but does nothing else.
BadUsername said:
It isn't in download mode, it doesn't say "do not turn off target" and it's displaying information about a recovery partition.
It's in some sort of system diagnostic mode. Never anything I've seen before.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That is why I started this thread, it is really weird. At first I thought that I was doing something wrong, so I formatted my SD card several times and reflashed the debrick file and got the same thing every time. What ever the phone repair place did to the phone they did it good. LikeI said, a brick like I have never seen. Thank you and please let me know if anyone can figure something out.
After doing some more research and trying, I am curious to know if it is possible to obtain a PIT from someones phone that has 4.3. When I look at all the available PIT files, they are from a while ago and none were extracted from a S3 with the new 4.3 OS on it. I am curious that since mine has this unique brick if a possible change was done to the new PIT file during the 4.3 update??? If anyone can post this for me it would be greatly appreciated. I figured at this point it would be worth a try.
Donny
dkmac said:
After doing some more research and trying, I am curious to know if it is possible to obtain a PIT from someones phone that has 4.3. When I look at all the available PIT files, they are from a while ago and none were extracted from a S3 with the new 4.3 OS on it. I am curious that since mine has this unique brick if a possible change was done to the new PIT file during the 4.3 update??? If anyone can post this for me it would be greatly appreciated. I figured at this point it would be worth a try.
Donny
Click to expand...
Click to collapse
I've got the exact same error screen you've run into. I've tried to NAND Erase All and that failed. Going to try re-partition now