Develop Bugs

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

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.

Note 4 bootloop... hardware failure?

Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.

Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk

samep said:
Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply...
Ive been messing with it all morning... and if i leave it a lone and it cools, it will last a little longer than when it becomes warm, rebooting quicker and quicker.
i managed to get into recover and did a factory reset and cleared cache.
it has made no difference.
The longest time its gone before rebooting is the lock screen.... and the it reboots again.
as it warms, it eventually wont even get past the Note 4 welcome screen before rebooting.. and then finally freezing and will require a battery pull.
Makes no difference if its on charge or off.
i have a sinking feeling about this.....

Could be terminal but you haven't tried to flash firmware on partitions with Smart Switch, KIES or Odin yet. Right? You can check the phone status while in download mode to verify reactivation lock is disabled.
Try one of those on PC or take it to Sprint to have it flashed again.
If you purchased at Best Buy and they have a Samsung Experience kiosk, they can do that too. Dunno, maybe it doesn't matter if you purchased there or not but they've flashed my phone a couple of times.
I've tried to guide you down the path of least effort to restore your, if possible. There's still some hope of recovery.
Edit: Your battery could be suspect. Let it cool and plug in to make sure it's at least 60% or higher. If the battery is near a year old, I'd suggest fully charging but get a replacement if you frequently discharge it to 15% or lower. Especially if you use fast charging.
But you've most likely discharged it with all that reboot activity and heating up. Kudos to you if you're managing all that and keep a healthy battery. Otherwise, the battery may be contributing to or causing your issues.
Sent from my SM-N910P using Tapatalk

thank you for the help..
reactivation lock is off.
i can't get it to reliably not reboot anywhere in any screen.. only screen that will stay on for any period of time is recovery... but the phone stays cool.
Its not the battery, i have two, and both do the same thing.. the battery does not get warm, area that gets warm is neft to the battery below the sd card slot. (sd card removed).
Frequency of hang/reboot seems to be related to how warm that area gets.
The most i have managed to do is get into my phone past the lockscreen and it will shortly freeze and reboot as it warms up.. it will reboot at the note 4 welcome screen or sprint logo... and repeat... eventually to hang.
Both batteries are charged fully using the external charger. (samsung oem)
Shame, not a scratch on her....
Oh well, on to Ebay for parts/AS IS and time to move on...

Even if doubtful, I'd still take it back to Sprint or place of purchase.
The Note 4 has a bit of history with eMMC failure. It's even happened with updates and Samsung and Sprint is apparently aware of it. A while back I saw that listed as an ongoing carryover of known issues that needed resolution.
I don't have true stats on exchanges but several users here have repeatedly gotten deals on replacement phones, paying a small percentage when they failed- similar to yours.
OTA updates have also been suspect to cause eMMC failure. But honestly, l don't know what causes this: bad hardware or updates? Maybe it's just bad hardware not taking updates well? Nonetheless, I don't know if I've just been lucky or my hardware is stable. Still going strong here with no hint of failure.
Sent from my SM-N910P using Tapatalk

can i still take it back even though its out of warranty?
nearing 2 years now....

asmd6230 said:
can i still take it back even though its out of warranty?
nearing 2 years now....
Click to expand...
Click to collapse
No promises. Couldn't hurt. If you don't like the answer you get from first Sprint store, try another.
I would mention that bit of history with the updates.
Sent from my SM-N910P using Tapatalk

asmd6230 said:
Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.
Click to expand...
Click to collapse
I have the exact same issue going on with my wives phone. Just started yesterday out of no where rebooting over and over. Never really getting past the Samsung splash screen. She got an update like a week ago, but other than downloading a new app several hours earlier nothing sticks out to why its happening. I was able to once get into safemode, but the phone rebooted a minute into it and typically doesn't even get to the sprint splash screen when I've tried to do it since. It's totally stock and has not been unlocked or rooted. I thought it could be the battery since so many of these boot issues on the Note4 deal with that when googling, but my battery from my working Note4 in her phone does the same thing and her battery in my phone works just fine. I can get into the recovery options menu (volume up + home + power) and I can get into the download area (volume down + home + power) for loading bootloaders and such for long periods of time with no issues. I've cleared the cache with no luck. Haven't tried factory reset yet because I want to try to recover the photos and stuff first. Searching for the issue on google I came across this software (android-recovery.net/android-recovery-mode.html#two) where I was able to use the download area and connect the phone with this app which used its own bootup and it was able to show me all the files on the phone for recovery so we could retrieve them. It wanted $50 to complete the process though and, knowing the advances that everyone here has made on their phones I decided to decline that and search these forums for a way to just access the file directory of my the phone and retrieve my wives stuff prior to factory resetting it. I believe something is wrong with the bootloader of the phone and that is why it cannot get to the android OS to start up, but I could be wrong. Reading various articles made me to believe that if I just were to unlock the phone for rooting that possibly that could fix this issue with the bootloader or at least be able to recover her photos and stuff. I do have insurance on the phone and could get it fixed or replaced, but that would be a $200 deductible I believe and first thing they're going to try is factory resetting the phone which will lose her data we're trying to save.
It almost seems as if I were to get TWRP installed that I'd be able to access the files without the need of loading any ROMs. But I'm not sure if that will work in my case or erase data when I do it. The threads I'm reading aren't clear on that part. I would really be grateful if anyone could help me out with figuring out the easiest way to recover her stuff or get it working. Its been a long time since I've unlocked any phones and they were all iPhones back in the day when they were only on AT&T and I had T-mobile and wanted to it work.

@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk

samep said:
@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?

dsm_gsx97 said:
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?
Click to expand...
Click to collapse
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk

samep said:
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.

dsm_gsx97 said:
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.
Click to expand...
Click to collapse
In that case, try the most recent stock tar in the first thread you were about to try.
Something seems off but trying to flash the original stock tar would be problematic if it was updated beyond Android 5.0
If it doesn't boot, you'll most likely have to factory reset it.
Sent from my SM-N910P using Tapatalk

Note 4 bootloop
just heat main ic little bit with past and check there is no heatup board on boot.and set is ok.tested

Recovering data from boot looping device (or fixing it)

My friend has an AT&T S6 Edge+ that is boot looping. Initially it was just frozen/unresponsive on the home screen. Rebooting just went to a boot loop showing the Samsung splash screen over and over again, although once in a while it does actually seem to do something which appears to be perhaps a failed attempt to apply an update (see attached image)
All I really want to do is to recover contacts from it. For some reason it seems the device was not configured to sync them to Google (or Samsung Cloud afaik), and they are not stored on the SIM, so they must be on the device only. If my best option is to try to fix the boot looping (i.e. get it to boot) in order to recover this data, let me know.
I have done recovery and rooting and custom ROMs on Nexus/Pixel devices for years, but never on a Samsung device. This was running the stock ROM (but I am not sure of which version exactly)
Is it conceivable that I could use ODIN to flash the same (or perhaps a slightly newer) AT&T ROM onto it in order to get it to boot? Does that flashing process have to wipe the user data from the device? (I have already download a fairly recent AT&T ROM) This won't cause a KNOX issue, will it?
Is there another way? Can I install a custom recovery on it and access user data via ADB? Seems like that might require it to have an unlocked bootloader, right? And I bet there is no way to unlock the bootloader without first booting it and enabling "OEM unlock", is there?
Does anyone know where the Samsung Contacts app stores its data? What is the full package name of that app?
Would it be better to post this on the regular "Galaxy S6" non-Edge+ forum? Or on the non-carrier-specific forum?
Do people in AT&T stores have the ability to repair the OS or access data with a device in such a state?
Take it easy on me because I am a noob with Samsungs but otherwise pretty experienced with this sort of stuff.

scootley said:
My friend has an AT&T S6 Edge+ that is boot looping. Initially it was just frozen/unresponsive on the home screen. Rebooting just went to a boot loop showing the Samsung splash screen over and over again, although once in a while it does actually seem to do something which appears to be perhaps a failed attempt to apply an update (see attached image)
All I really want to do is to recover contacts from it. For some reason it seems the device was not configured to sync them to Google (or Samsung Cloud afaik), and they are not stored on the SIM, so they must be on the device only. If my best option is to try to fix the boot looping (i.e. get it to boot) in order to recover this data, let me know.
I have done recovery and rooting and custom ROMs on Nexus/Pixel devices for years, but never on a Samsung device. This was running the stock ROM (but I am not sure of which version exactly)
Is it conceivable that I could use ODIN to flash the same (or perhaps a slightly newer) AT&T ROM onto it in order to get it to boot? Does that flashing process have to wipe the user data from the device? (I have already download a fairly recent AT&T ROM) This won't cause a KNOX issue, will it?
Is there another way? Can I install a custom recovery on it and access user data via ADB? Seems like that might require it to have an unlocked bootloader, right? And I bet there is no way to unlock the bootloader without first booting it and enabling "OEM unlock", is there?
Does anyone know where the Samsung Contacts app stores its data? What is the full package name of that app?
Would it be better to post this on the regular "Galaxy S6" non-Edge+ forum? Or on the non-carrier-specific forum?
Do people in AT&T stores have the ability to repair the OS or access data with a device in such a state?
Take it easy on me because I am a noob with Samsungs but otherwise pretty experienced with this sort of stuff.
Click to expand...
Click to collapse
You can flash the latest firmware via Odin under CSC. Just make sure to untick F. Reset under options and choose HOME CSC as it will keep device data intact, leaving the contacts you are trying to get. Not sure if that will fix the issue on your friend's phone though. Good luck!

Rehvix said:
You can flash the latest firmware via Odin under CSC. Just make sure to untick F. Reset under options and choose HOME CSC as it will keep device data intact, leaving the contacts you are trying to get. Not sure if that will fix the issue on your friend's phone though. Good luck!
Click to expand...
Click to collapse
Thanks for the help @Rehvix. I thought CSC was just for location/carrier features. Do you think that will fix the boot loop? Is that a common situation? I was thinking I might have to flash the Android System which I believe is "AP". Maybe I should try CSC first and then AP. What effect will unticking the "F Reset Time" have? Does that option (if ticked) just reset a flash counter? And in the ROM that I got from another post on XDA (version G928AUCS5ERA2), there is only one CSC_ATT.....tar.md5. There is no separate CSC file with HOME in the name. Maybe I need to read up on Odin some more.

scootley said:
Thanks for the help @Rehvix. I thought CSC was just for location/carrier features. Do you think that will fix the boot loop? Is that a common situation? I was thinking I might have to flash the Android System which I believe is "AP". Maybe I should try CSC first and then AP. What effect will unticking the "F Reset Time" have? Does that option (if ticked) just reset a flash counter? And in the ROM that I got from another post on XDA (version G928AUCS5ERA2), there is only one CSC_ATT.....tar.md5. There is no separate CSC file with HOME in the name. Maybe I need to read up on Odin some more.
Click to expand...
Click to collapse
I apologize for creating confusion. CSC is used on phones starting with the s7 because the firmwares started getting really big so they had to break them up into chunks for flashing. For the s6 edge+ there will only be one AP file, as you mentioned. This one should end in HOME (mine goes G928TUV...EQC6_HOME.tar.md5). Flashing this should upgrade the OS to the latest version without wiping it, unless the SD Card is bad, it may or may not flash at all.
As for F Reset Time, it's not factory reset as I believed it was. It resets the flash counter, so you would want to leave that checked.

Please help me recover my S9 data

Hello, I have an unrooted galaxy s9 (G960U1) stuck in a bootloop. An app had froze which required me to shut off my device. I have not been able to access it since. Around 1 in 4 bootloops I will have access for no more then 5 seconds. If I open bixby or camera I see the errors "process system isn't responding" as well as "system UI isn't responding" appear. Also worth mention, when I enter recovery mode, I receive a screen that says "installing system update" which seems to fail, followed by a brief flash of the slanted android logo with a yellow exclamation point with the words "no command". Also if I choose the option "run graphics test" in recovery mode, I will get the same screen which says "installing system update" followed by "error" and "no command" with the slanted android/exclamation point present. It will then say "erasing" with a progress bar which will reach 100%, followed by another progress bar with the slanted android/exclamation present which will fill 1/5th and then fill out fully before returning to the recovery mode screen.
The data on this phone is extremely valuable to me and a factory reset is simply not an option I can consider. I am dealing with some severe health issues which have kept me bedridden for 4 years. I had been meaning to create a backup but never had any sense of urgency as I felt the risk of my device being broken, lost, etc was extremely low given my circumstances. Much of this data pertains to my condition
Im very new to these sorts of things and my brain does not work very well anymore but I will do everything I can. I see options in recovery mode listed "install update from adb" as well as "install update from sd card". I can also access download mode. Would these options be of any use to me?
I have also heard things about TWRP. Would this be an option or must bootloader be unlocked?
I am running on 8.0 oreo. Is there a way to update and would this be helpful?
Is remote control via team viewer or others possible or worth a try?
Can the flash memory be removed and extracted or placed in a new s9? - (Someone looks to have attempted this with another device and succeeded. There also seem to be a few other viable methods mentioned? https://forum.xda-developers.com/showthread.php?t=2154652&page=1).
Mobile data recovery service? (this seems the most promising)
Some of these proposals may sound dumb as I'm still very new to this but I am willing to try anything. Thank you very much

Flash the latest U1 firmware with ODIN 3.13.1 and use HOME_CSC not CSC to retain data

*Detection* said:
Flash the latest U1 firmware with ODIN 3.13.1 and use HOME_CSC not CSC to retain data
Click to expand...
Click to collapse
Wow don't know how I missed this. I came across odin previously but quickly dismissed it as the impression I got was that data loss was inevitable flashing firmware. Apparently not
Ive looked through multiple guides and see many of them look to be leaving out certain files. Is there any added risk in using HOME_CSC, BL, and CP than just AP alone? Is using AP alone even an option for me?
Also, I remember my internal storage being nearly brimmed before the bootlooping begun. The firmware file looks to be about 4gb which I know I don't have. Is this a problem?
Thanks

NewguyS9 said:
Wow don't know how I missed this. I came across odin previously but quickly dismissed it as the impression I got was that data loss was inevitable flashing firmware. Apparently not
Ive looked through multiple guides and see many of them look to be leaving out certain files. Is there any added risk in using HOME_CSC, BL, and CP than just AP alone? Is using AP alone even an option for me?
Also, I remember my internal storage being nearly brimmed before the bootlooping begun. The firmware file looks to be about 4gb which I know I don't have. Is this a problem?
Thanks
Click to expand...
Click to collapse
Leave Odin on default settings, (Dont change anything), flash AP, BL, CP and HOME_CSC together
The firmware will just replace the broken one already installed, no extra storage needed

*Detection* said:
Leave Odin on default settings, (Dont change anything), flash AP, BL, CP and HOME_CSC together
The firmware will just replace the broken one already installed, no extra storage needed
Click to expand...
Click to collapse
I managed to successfully flash the latest firmware but unfortunately my device is still bootlooping. The nature of the bootlooping although is very different. Now it will remain on the samsung logo wirh the blue light much longer than previously. Eventually the blue light will disappear and I will see a "phone is starting" box pop up and will begin optimizing my apps. Afterwards the screen will just go black. If don't interfere I'll later get a recovery mode screen with the message "Your phone could not start normally. Some configuration data may be corrupt. Follow the instructions below" which will then give me the option to retry, erase app data, or suggest taking my device to a service provider if I do not wish to erase data. Unfortunately the majority of my valuable data is app data
Im still able to access download mode and the weird errors I was getting before in recovery mode seem to have gone away. I've messed with a few things in recovery mode as well as cleared cache to no avail. Is there anything I can do from here?

NewguyS9 said:
I managed to successfully flash the latest firmware but unfortunately my device is still bootlooping. The nature of the bootlooping although is very different. Now it will remain on the samsung logo wirh the blue light much longer than previously. Eventually the blue light will disappear and I will see a "phone is starting" box pop up and will begin optimizing my apps. Afterwards the screen will just go black. If don't interfere I'll later get a recovery mode screen with the message "Your phone could not start normally. Some configuration data may be corrupt. Follow the instructions below" which will then give me the option to retry, erase app data, or suggest taking my device to a service provider if I do not wish to erase data. Unfortunately the majority of my valuable data is app data
Im still able to access download mode and the weird errors I was getting before in recovery mode seem to have gone away. I've messed with a few things in recovery mode as well as cleared cache to no avail. Is there anything I can do from here?
Click to expand...
Click to collapse
Try making a backup with Samsung Smart switch, then reset the phone, once it is booting and working properly, try restoring the backup, but chances are if it's telling you the problem is app data, it's corrupted anyway and you've already lost it
Important data such as media can be copied manually via USB > PC first
Which "app data" is important?
Texts and such will backup with Smart Switch

*Detection* said:
Try making a backup with Samsung Smart switch, then reset the phone, once it is booting and working properly, try restoring the backup, but chances are if it's telling you the problem is app data, it's corrupted anyway and you've already lost it
Important data such as media can be copied manually via USB > PC first
Which "app data" is important?
Texts and such will backup with Smart Switch
Click to expand...
Click to collapse
The exact message regarding the app data is this
"2. Erase app data
Deleting app configuration data may allow your phone to start in safe mode. Safe mode allows access to basic functions, so you can back up any important data stored on your phone. After backing up your data, a factory reset may be needed to get your phone to start normally"
I have many concerns but the app data i'm most concerned with are my notes and book writing progress which I have stored in non system apps
As for media being copied you mean this in the context of a successful smartswitch backup correct? Or in the current state of my device?
Is flashing again worth a try? Heres some additional info I left out that may be helpful. I used Samfirm v0.3.6 to download latest 9.0 firmware for SM-G960U1, with CSC code XAA. Also used Odin 3.13.1. Maybe try downloading the firmware from a different source or try different versions?
I found this link (https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857) which looks to have resolved a post-odin bootlooping problem with the S8. Would I be able to do something similar?
I also found this (https://www.google.com/amp/s/forum....id/software/patched-odin-3-13-1-t3762572/amp/) updated patched odin which looks to replicate the popular prince comsy version. Would this be useful?
Thanks

NewguyS9 said:
The exact message regarding the app data is this
"2. Erase app data
Deleting app configuration data may allow your phone to start in safe mode. Safe mode allows access to basic functions, so you can back up any important data stored on your phone. After backing up your data, a factory reset may be needed to get your phone to start normally"
I have many concerns but the app data i'm most concerned with are my notes and book writing progress which I have stored in non system apps
As for media being copied you mean this in the context of a successful smartswitch backup correct? Or in the current state of my device?
Is flashing again worth a try? Heres some additional info I left out that may be helpful. I used Samfirm v0.3.6 to download latest 9.0 firmware for SM-G960U1, with CSC code XAA. Also used Odin 3.13.1. Maybe try downloading the firmware from a different source or try different versions?
I found this link (https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857) which looks to have resolved a post-odin bootlooping problem with the S8. Would I be able to do something similar?
I also found this (https://www.google.com/amp/s/forum....id/software/patched-odin-3-13-1-t3762572/amp/) updated patched odin which looks to replicate the popular prince comsy version. Would this be useful?
Thanks
Click to expand...
Click to collapse
Have you not tried safemode yet to remove the faulty app(s)?
To boot your S9 or S9+ into Safe mode, start by pressing and holding the power button until the power menu appears on your screen. From there, long press the "Power Off" button until it turns into a "Safe Mode" button. Simply tap on "Safe Mode" once it appears and your device will automatically reboot to safe mode.

*Detection* said:
Have you not tried safemode yet to remove the faulty app(s)?
To boot your S9 or S9+ into Safe mode, start by pressing and holding the power button until the power menu appears on your screen. From there, long press the "Power Off" button until it turns into a "Safe Mode" button. Simply tap on "Safe Mode" once it appears and your device will automatically reboot to safe mode.
Click to expand...
Click to collapse
I have tried this but unfortunately it seems i'm unable to access my device to the degree where that would be possible. The screen that pops up with the app data message is in the recovery mode interface. Meaning volume up/down to move, power to select, etc. Ive tried accessing safe mode with the power/volume down method as well with no success
I was able to use the method you're describing before flashing firmware however, also with no luck

Sounds to me like the partition is corrupted which will require re-flashing with Odin but using CSC to force the partitions to be re-written and phone reset
Without being able to get back into Android your options are limited
Try flashing with HOME_CSC as many times as you like, unlikely to help but try older firmware (But make sure it's still Pie or Oreo, you cannot downgrade from Pie to Oreo without resetting and expect the phone to work properly)
Other than that, remember to make regular backups next time and reset the phone

*Detection* said:
Sounds to me like the partition is corrupted which will require re-flashing with Odin but using CSC to force the partitions to be re-written and phone reset
Without being able to get back into Android your options are limited
Try flashing with HOME_CSC as many times as you like, unlikely to help but try older firmware (But make sure it's still Pie or Oreo, you cannot downgrade from Pie to Oreo without resetting and expect the phone to work properly)
Other than that, remember to make regular backups next time and reset the phone
Click to expand...
Click to collapse
Oh man this doesn't sound good
For this should I just focus on flashing HOME_CSC or should I mess around with the others as well? Also, if i'm downloading the same firmware with the same product code and everything does it necessarily matter where I'm getting it from or is it all the same?
Do you think I should prioritize trying the same firmware with different product codes or older firmware as you mentioned(but still pie/oreo)?
As for the functionality problems downgrading to Oreo, will the amount of function I receive(If I'm lucky enough for this to work) be enough to back up?
Thanks

NewguyS9 said:
Oh man this doesn't sound good
For this should I just focus on flashing HOME_CSC or should I mess around with the others as well? Also, if i'm downloading the same firmware with the same product code and everything does it necessarily matter where I'm getting it from or is it all the same?
Do you think I should prioritize trying the same firmware with different product codes or older firmware as you mentioned(but still pie/oreo)?
As for the functionality problems downgrading to Oreo, will the amount of function I receive(If I'm lucky enough for this to work) be enough to back up?
Thanks
Click to expand...
Click to collapse
If you flash from Pie to Oreo without resetting, the phone will crash more than it already is, if it boots at all, the apps are not backwards compatible, you could end up worse off
Different product/region codes will make no difference
Don't just flash HOME_CSC, always flash all 4 sections at once, I meant you can keep flashing the firmware as many times as you like using HOME_CSC rather than CSC
All firmwares will be the same regardless of where you obtain them, only the build number / date of firmware makes any difference, and even then most of them are just different security updates
The problem is not with the firmware from the sounds of it, it is from your DATA partiton, which does not get touched when you flash unless you flash with CSC, so every flash will likely result in the exact same outcome
Firmware is fine - data partition is corrupted, only likely solution is factory reset I'm afraid, and if that doesn't fix it, there could be a hardware problem with the NAND (storage chip)
AP - System partition
CP - Modem partition
BL - Bootloader partition
CSC - Country Specific Code with repartition
HOME_CSC - Country Specific Code without repartition
DATA partition is not part of the flashing process unless you flash with CSC in which case it will be erased as part of the repartitioning process
Your problem appears to be the DATA partition, so you can see your issue now with the above firmware information

@*Detection* @NewguyS9 I'm very uneducated in all the stuff said in this thread but I have the exact same issue going on, and don't want to factory reset my phone as I have pictures and videos I don't want deleted. Was there ever a fix? If so, what can I do to fix it?