Galaxy Tab S 8.4 keeps soft-bricking itself. - Galaxy Tab S Q&A, Help & Troubleshooting

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?

Related

[Q] Grand rebooting problem help

my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.

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. )

[Q] SM-T210R Problems after update

First this is the kids tablet and I don't spend tons of time on the Samsung side as I am mostly hanging in the HTC parts of XDA. I've spent a lot of time in this forum this week reading up and trying to find a solution but I am getting nowhere.
I have downloaded Odin v 3.09 and have been trying to load the firmware update for the WiFi only version and even though it seems to complete fine with no errors when it boots it seems that most everything generates a force close (settings, start wizard, etc.), or what appears to be system reset (not a full reboot but just the OS resets).
I have redownloaded the update a couple times thinking that perhaps I got a bad download or something but that hasn't made a difference.
I have tried downloading the previous firmware a couple times and loading that but I can't seem to get that to boot as it sticks on boot screen.
I just don't know what to do with this at this point and really need some help from the community to get this functional again (my kids are driving me nuts!!!)
Thanks!
MG
moregadget said:
First this is the kids tablet and I don't spend tons of time on the Samsung side as I am mostly hanging in the HTC parts of XDA. I've spent a lot of time in this forum this week reading up and trying to find a solution but I am getting nowhere.
I have downloaded Odin v 3.09 and have been trying to load the firmware update for the WiFi only version and even though it seems to complete fine with no errors when it boots it seems that most everything generates a force close (settings, start wizard, etc.), or what appears to be system reset (not a full reboot but just the OS resets).
I have redownloaded the update a couple times thinking that perhaps I got a bad download or something but that hasn't made a difference.
I have tried downloading the previous firmware a couple times and loading that but I can't seem to get that to boot as it sticks on boot screen.
I just don't know what to do with this at this point and really need some help from the community to get this functional again (my kids are driving me nuts!!!)
Thanks!
MG
Click to expand...
Click to collapse
Did you do a factory reset before upgrading. The jump from 4.1.2 to 4.4.2 included a lot of changes. If you didn't, try that; then report back.
Our 4.1.2 version roms use the /data/media directory as the "internal sdcard".
4.2+ versions of Android use the /data/media/0 directory due to support for multiple users.
If you switch to a different Android version, you need to be aware of this difference.
I recommend wiping "internal sdcard" also before switching from 4.1.2 to 4.4.2.
Click to expand...
Click to collapse
gr8nole said:
Did you do a factory reset before upgrading. The jump from 4.1.2 to 4.4.2 included a lot of changes. If you didn't, try that; then report back.
Click to expand...
Click to collapse
Thank you for the reply. At some point in the process I did try that but didn't initially before I started. I have tried that again today and then loaded again and still get the force closes, and such. Tablet is really unusable at this point.
Thanks,
MG

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.

Help - Galaxy Tab S 10.5 Bootloop Out of Nowhere

So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.

Categories

Resources