Develop Bugs

[Q] phone keeps restarting. need help

i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks

antn said:
i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
Click to expand...
Click to collapse
wipe and reflash the rom. or wipe and try another rom and kernel. every time you wipe, you want to reflash.

yea i already tried doing that and it would do the same thing.

I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.

I'd rather flash the takju build via fastboot using efrants step by step instructions. If I were to buy a used phone I'd want to do all the rooting and flashing as if it were a new device.
- Google

kvirus11 said:
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
Click to expand...
Click to collapse
restore point? lmao! theres no such thing. you can restore a nandroid backup, but i doubt the previous owner would leave it in your sd storage considering all his/her personalinformation/data would be contained in it.

i got it to work now. i was able to learn and unroot the phone through the guide. at first i thought it wouldnt work cause i couldnt access the phone to put it in debugging mode but i guess it was already on and i did the whole unrooting process and flash stock image with no problems. thanks guys

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.

kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.

Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!

any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..

Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!

DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!

Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.

DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!

S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?

In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...

Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.

The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.

....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?

Maybe your battery is dying. it happens. That would explain a big drop from the start.

To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

Cannot get a clean flash to install correctly regardless of ROM

So this is bugging me out. I received my Verizon Dev Edition last week. It came with NJ5 already installed, so I skipped the first step to flash custom recovery, and then I rooted. Everything is great I have a rooted stock NJ5 ROM with a custom recovery. Now when I wipe my data, system, dalvik, and cache (clean install) to install any rom (Definitive/FireKat) I get a Amazon Kindle unfortunate force close error at the start up wizard, also the samsung keyboard swipe feature and suggestions at the top do not work at all. After I let it settle I bypass the wizard by pressing skip, then I turn off auto sync. I log in to google and I try to launch Maps and I get a force close error. I tried updating it in the Play Store and it gets a download error. What is going on?? I am going kind of insane trying to fix this. I ODIN Stock NJ5 restore to get maps, kindle, and the keyboard to work correctly. I spent all day trying to figure this and I can not for the life of me get a good solid flash! I am thinking of ODINing Stock NI1 Restore to see what happens. Will I break my phone if I downgrade? Does anybody have any suggestions to fix these errors? It is only when I flash a ROM from TWRP. Thanks in advance!

jcip17 said:
So this is bugging me out. I received my Verizon Dev Edition last week. It came with NJ5 already installed, so I skipped the first step to flash custom recovery, and then I rooted. Everything is great I have a rooted stock NJ5 ROM with a custom recovery. Now when I wipe my data, system, dalvik, and cache (clean install) to install any rom (Definitive/FireKat) I get a Amazon Kindle unfortunate force close error at the start up wizard, also the samsung keyboard swipe feature and suggestions at the top do not work at all. After I let it settle I bypass the wizard by pressing skip, then I turn off auto sync. I log in to google and I try to launch Maps and I get a force close error. I tried updating it in the Play Store and it gets a download error. What is going on?? I am going kind of insane trying to fix this. I ODIN Stock NJ5 restore to get maps, kindle, and the keyboard to work correctly. I spent all day trying to figure this and I can not for the life of me get a good solid flash! I am thinking of ODINing Stock NI1 Restore to see what happens. Will I break my phone if I downgrade? Does anybody have any suggestions to fix these errors? It is only when I flash a ROM from TWRP. Thanks in advance!
Click to expand...
Click to collapse
It sounds like you have mixed firmware. I would think you would be safe downgrading as long as you use dev edition files. Make a back up of your partitions first with these instructions if you haven't already. Atleast you will a safeguard in case something goes wrong.

Misterxtc said:
It sounds like you have mixed firmware. I would think you would be safe downgrading as long as you use dev edition files. Make a back up of your partitions first with these instructions if you haven't already. Atleast you will a safeguard in case something goes wrong.
Click to expand...
Click to collapse
Thanks I will try downgrading, but not sure what to do after. I guess I should try NI1 definitive rom and see if I get the errors. I did the Aboot backup yesterday using EFS Professional so I think I should be good!

jcip17 said:
Thanks I will try downgrading, but not sure what to do after. I guess I should try NI1 definitive rom and see if I get the errors. I did the Aboot backup yesterday using EFS Professional so I think I should be good!
Click to expand...
Click to collapse
That sounds right. If there aren't any NJ5 ROMs out yet then I can almost guarantee that's the problem. I know that sort of thing happens when you mix firmwares, I had a lot of folks doing that with the S5 ROM I made.

Misterxtc said:
That sounds right. If there aren't any NJ5 ROMs out yet then I can almost guarantee that's the problem. I know that sort of thing happens when you mix firmwares, I had a lot of folks doing that with the S5 ROM I made.
Click to expand...
Click to collapse
But definitive ROM has a NJ5 version and so does FireKat V8. Even the Stock root deodexed NJ5 ROM does not install correctly. It is very weird

jcip17 said:
But definitive ROM has a NJ5 version and so does FireKat V8. Even the Stock root deodexed NJ5 ROM does not install correctly. It is very weird
Click to expand...
Click to collapse
I'm wondering if it might be your recovery version. I don't have a dev phone or root so I can't help out that much.

Misterxtc said:
I'm wondering if it might be your recovery version. I don't have a dev phone or root so I can't help out that much.
Click to expand...
Click to collapse
I understand I really appreciate the help though. So the keyboard is fixed by updating the language, for some reason lol. I am going to delete kindle and maps and try to install it through the play store and see what happens.

So deleting maps and installing it through the play store worked and once I opened maps I got a play services error and it said it needed to update. And I updated and I have the new play store icon now and everything seems stable now. I guess I will have to do this with every ROM I install. Or until lollipop fixes these issues. It seems like I am the only asshole who is experiencing these problems! lol

T-Mo Note 3 Stock Firmware Issue

I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.

What are the links to all these incorrect firmwares?
Posting the links would be more informative than suspicions.
Pp.

wallacengineering said:
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
Click to expand...
Click to collapse
Yes, could you post the links that you say have the issues?

AxAtAx said:
Yes, could you post the links that you say have the issues?
Click to expand...
Click to collapse
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.

wallacengineering said:
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
Click to expand...
Click to collapse
I just put that stock rom on my wifes phone a few days ago, and it defaulted to Note 3 on hers. well, never mind, as you have seem to have got it rolling now.:good::good:

I must be taken crazy pills.
Pp. :what:

Can i ever unbrick my note 3
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.

boofydon said:
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.

Ravoz88 said:
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Click to expand...
Click to collapse
Thank you for your time. I flashed it with a new stock from sammobile but it's still in a boot loop state even though odin always show pass. And when I flashed it with twrp my note 3 was unable to enter recovery mode.

Galaxy Tab S 8.4 keeps soft-bricking itself.

Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?

AussieMouse said:
Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?
Click to expand...
Click to collapse
Can i ask how you updated from kk to lp did you use oden or kies.......for me i use oden and jump to mm use updato to get a good clean rom to flash in oden.....you may have flashed a crupt file is has happened to me once.....

stinka318 said:
Can i ask how you updated from kk to lp did you use oden or kies.......for me i use oden and jump to mm use updato to get a good clean rom to flash in oden.....you may have flashed a crupt file is has happened to me once.....
Click to expand...
Click to collapse
I used Odin but skipped past Lollipop to Marshmallow (the ROM was the Official ROM from Samsung Updates). I don't think the file was corrupt as I had this problem with the tablet before I started flashing the same KitKat ROM it was originally preinstalled with, and Marshmallow later on.

AussieMouse said:
I used Odin but skipped past Lollipop to Marshmallow (the ROM was the Official ROM from Samsung Updates). I don't think the file was corrupt as I had this problem with the tablet before I started flashing the same KitKat ROM it was originally preinstalled with, and Marshmallow later on.
Click to expand...
Click to collapse
Were did you download the rom from.....

stinka318 said:
Were did you download the rom from.....
Click to expand...
Click to collapse
This website http://live.samsung-updates.com/, I believe.

AussieMouse said:
This website http://live.samsung-updates.com/, I believe.
Click to expand...
Click to collapse
Try updato and download the required rom it is fast and clean

stinka318 said:
Try updato and download the required rom it is fast and clean
Click to expand...
Click to collapse
I have already done so. It's up to date with the latest official version in my region.

AussieMouse said:
I have already done so. It's up to date with the latest official version in my region.
Click to expand...
Click to collapse
Well if update with the rom that you got from updato there would not be a problem....in my experience if a download take a long time it has a greater chance of having issues if it is a fast clean download it would be clean with no errors.

stinka318 said:
Well if update with the rom that you got from updato there would not be a problem....in my experience if a download take a long time it has a greater chance of having issues if it is a fast clean download it would be clean with no errors.
Click to expand...
Click to collapse
I don't think the issue did start with the update. If anything, flashing the ROM (combined with factory resetting) seems to temporarily fix the bootloop.

AussieMouse said:
I don't think the issue did start with the update. If anything, flashing the ROM (combined with factory resetting) seems to temporarily fix the bootloop.
Click to expand...
Click to collapse
When a download is slow it get interrupted with advertising bots and sometimes depending on were the errors happen it may have been a crupt....i had the same problem with t705y and t805y until i download it from updato now i get nothing no errors......just my experience thats all.

stinka318 said:
When a download is slow it get interrupted with advertising bots and sometimes depending on were the errors happen it may have been a crupt....i had the same problem with t705y and t805y until i download it from updato now i get nothing no errors......just my experience thats all.
Click to expand...
Click to collapse
Ah, I see! No worries, I'll download the ROM again and make sure the download isn't interrupted. Thanks for the advice! I shall let you know how it turns out.

AussieMouse said:
Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?
Click to expand...
Click to collapse
Well, this may not get to the root of your problem, but it's a bit of a no brainer really.
If your having to restore your device so much why not just bung twrp on it, make a device back up, literally a few minutes and if it all goes Pete Tong again, simply boot to twrp, hit restore and you're back up and running in a few minutes?