Develop Bugs

[Q] Reboots, crashing and warranty

So my issue is similar to the one of Spectre Nine here.
I have bought a N7100 in January 2013. Until about July it ran absolutely fine, but then it started freezing and rebooting at random.
Here is the data:
Model: GT-N7100
Android: 4.1.2
Baseband: N7100XXDLK7
Build: JZO54K.N7100XXDMB2
Country of origin: Austria
I am running a stock rom which was updated using Kies, afterwards root was installed using CF-Autoroot.
I have never used Odin or other flashing software, and I am also on stock recovery on this device.
TriangleAway has been used due to CF-Autoroot increasing the flash counter.
I have already ruled out the SIM and MicroSD cards, as it happens without them as well.
I noticed that there might have been some data corruption, as my SwiftKey dictionary got wiped for some reason.
Unfortunately, I have found no tools or ways to check the internal SD for errors as opposed to the external ones.
My questions are as follows:
1. Are there any tools or methods for checking the internal storage for file system errors?
2. Any ideas as to what could be causing this issue?
3. If I have to send the device in for repairs, is it enough to just remove the root (confirm device normal status) and do a factory reset?
Thank you very much for any leads or replies at all.
PS: I am trying to record a logcat to find out what happens before the reboot, will also attach it,

Crescento said:
So my issue is similar to the one of Spectre Nine here.
I have bought a N7100 in January 2013. Until about July it ran absolutely fine, but then it started freezing and rebooting at random.
Here is the data:
Model: GT-N7100
Android: 4.1.2
Baseband: N7100XXDLK7
Build: JZO54K.N7100XXDMB2
Country of origin: Austria
I am running a stock rom which was updated using Kies, afterwards root was installed using CF-Autoroot.
I have never used Odin or other flashing software, and I am also on stock recovery on this device.
TriangleAway has been used due to CF-Autoroot increasing the flash counter.
I have already ruled out the SIM and MicroSD cards, as it happens without them as well.
I noticed that there might have been some data corruption, as my SwiftKey dictionary got wiped for some reason.
Unfortunately, I have found no tools or ways to check the internal SD for errors as opposed to the external ones.
My questions are as follows:
1. Are there any tools or methods for checking the internal storage for file system errors?
2. Any ideas as to what could be causing this issue?
3. If I have to send the device in for repairs, is it enough to just remove the root (confirm device normal status) and do a factory reset?
Thank you very much for any leads or replies at all.
PS: I am trying to record a logcat to find out what happens before the reboot, will also attach it,
Click to expand...
Click to collapse
well flashing via kies must have created the issue, rather flash a stock rom via odin adn it wil be fine no need to send it for repairs follow ketan guide here in xda on the procedure to follow flashing rom using odin and everything will be fine.
so i definitely suspect kies for your problem

The Kies update happened in february, and the phone has been running fine until july.
If I use Odin, will Samsung be able to detect it in case I send it in?
shhbz said:
well flashing via kies must have created the issue, rather flash a stock rom via odin adn it wil be fine no need to send it for repairs follow ketan guide here in xda on the procedure to follow flashing rom using odin and everything will be fine.
so i definitely suspect kies for your problem
Click to expand...
Click to collapse

Crescento said:
The Kies update happened in february, and the phone has been running fine until july.
If I use Odin, will Samsung be able to detect it in case I send it in?
Click to expand...
Click to collapse
nope your device status must be normal now and binary count 0 so you good to give it now no need to flash anything via odin just unrootand check your system status

A follow-up here.
The issue suddenly disappeared about 3 weeks after my initial post.
I am baffled as to what could have caused this.
Occasionally, it still happens about once in two weeks.
I still couldn't find any tools to check the internal storage.
When 4.3 is out (probably soon for my provider), would a full wipe get rid of possible errors on the internal sd?

[Q] lazy to turn on screen before some minutes of screen off.

hi.
i read this forums for a long time because there is too much information here. i rooted all my htc devices but now i switch to samsung.
i receive this fome 2 weeks ago and it worked good. then i play with root and custom firmwares but no lucky. sudenly my phone lost imei, csc and other important things. i didnt make nand backup.
some week ago, i restore imei and csc installing an original firmware from cell company. it worked fine for some days but then i try to flash a custom rom again but this time i did a full backup using twrp. all things were worse so i restore again but now my phone gets very slow when you turn screen off. when you push on buton, sometimes screen wakes up faster but sometimes has a extra long lag. some times phone resets automaticaly. if i configure to screen dont turn off, phone can stay for to much long without problems. it works very fast. only problem is when screen turns off and nightmare starts.
i play with odin and using bootloader and pit options.
i read about NOTE 2 SDS and install 2 programs. one programs dont only says its fine. the other gives fw version .
Type: VTU00M
FwRev: 0xF7
i read 0xF1 are the bad devices. this last app did a scan in memory and it was 100 healty.
maybe its a modem or kernel issue? i mess with everything.
thankyou for your time.

maik21 said:
hi.
i read this forums for a long time because there is too much information here. i rooted all my htc devices but now i switch to samsung.
i receive this fome 2 weeks ago and it worked good. then i play with root and custom firmwares but no lucky. sudenly my phone lost imei, csc and other important things. i didnt make nand backup.
some week ago, i restore imei and csc installing an original firmware from cell company. it worked fine for some days but then i try to flash a custom rom again but this time i did a full backup using twrp. all things were worse so i restore again but now my phone gets very slow when you turn screen off. when you push on buton, sometimes screen wakes up faster but sometimes has a extra long lag. some times phone resets automaticaly. if i configure to screen dont turn off, phone can stay for to much long without problems. it works very fast. only problem is when screen turns off and nightmare starts.
i play with odin and using bootloader and pit options.
i read about NOTE 2 SDS and install 2 programs. one programs dont only says its fine. the other gives fw version .
Type: VTU00M
FwRev: 0xF7
i read 0xF1 are the bad devices. this last app did a scan in memory and it was 100 healty.
maybe its a modem or kernel issue? i mess with everything.
thankyou for your time.
Click to expand...
Click to collapse
Well, first things first, make a EFS backup by using Dr. Ketan's Multitool.
The issue at hand happens when you move from one ROM to another and somehow the system data gets corrupted.
Please don't play with ODIN. Especially, bootloader and pit files. A slightest mistake and your phone is a hard brick. Anyways it is your phone. Your choice.
I suggest you install fresh copy of official stock ROM using PC ODIN.
When the process is complete and you reach the language screen, turn off your phone.
Do a wipe / factory reset using stock recovery and restart your phone. (Important!)
All your screen related issues should go away. Later you can root and do whatever.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Well, first things first, make a EFS backup by using Dr. Ketan's Multitool.
The issue at hand happens when you move from one ROM to another and somehow the system data gets corrupted.
Please don't play with ODIN. Especially, bootloader and pit files. A slightest mistake and your phone is a hard brick. Anyways it is your phone. Your choice.
I suggest you install fresh copy of official stock ROM using PC ODIN.
When the process is complete and you reach the language screen, turn off your phone.
Do a wipe / factory reset using stock recovery and restart your phone. (Important!)
All your screen related issues should go away. Later you can root and do whatever.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
thankyou very much for your advide. i was only using pc odin to do things. finally phone works. i download a not to new firmware from my carrier. rom was unlocked. it works with all sims. when i upgrade to a custom rom called DN3_v3.2_by_E-Team_(Vegeta_Edition), i get an unlock message at start. so my sim card dont work. i go to twrp and restore my previeus efs and modem and get DN3_v3.2_by_E-Team_(Vegeta_Edition) working unlocked and now this custom rom reads very well my sim card.
all problems i had was because i install roms from other carriers or using a custom rom that locked sim card carrier. some days ago, i install 4.1.1 to use free code unlock using numbers in dialpad without success because final menu didnt there.
now i can fully use phone and see how well battery works.
thankyou very much.

maik21 said:
thankyou very much for your advide. i was only using pc odin to do things. finally phone works. i download a not to new firmware from my carrier. rom was unlocked. it works with all sims. when i upgrade to a custom rom called DN3_v3.2_by_E-Team_(Vegeta_Edition), i get an unlock message at start. so my sim card dont work. i go to twrp and restore my previeus efs and modem and get DN3_v3.2_by_E-Team_(Vegeta_Edition) working unlocked and now this custom rom reads very well my sim card.
all problems i had was because i install roms from other carriers or using a custom rom that locked sim card carrier. some days ago, i install 4.1.1 to use free code unlock using numbers in dialpad without success because final menu didnt there.
now i can fully use phone and see how well battery works.
thankyou very much.
Click to expand...
Click to collapse
Welcome. Wait for 3 battery cycles before rating the ROM. DN3 is a very good ROM.
Sent from my GT-N7100 using Tapatalk

wipe dalvik and wipe cache

[Q] i467 OTA update fails at 26%, even after unrooting & flashing to stock 4.1.2.

Hi all,
Thrilled and surprised to see we finally got an update for our AT&T Note 8s, but I'm having issues.
I had my Note rooted and unlocked (in an attempt to use TMo's free tablet data promo) previously, but no custom ROM. I don't recall ever disabling knox or any system apps. I first unrooted within SuperSU, but the update failed. I then tried it both with the AT&T SIM and the TMo SIM, both failed. I tried a standard factory reset, still failed.
I started escalating options then, and used Odin to flash a completely fresh and stock 4.1.2, update still failed. I'd love to use Odin to flash the 4.4.2 image, but I can't find an Odin compatible download of it. I did find a cfg of the OTA update someone uploaded, bu I'll admit to having no idea how to manually apply that.
I had thought I got everything back to completely stock, so I'm not sure what's causing the failure. The info on the Odin screen seems to suggest that too:
odin mode
product name: SGH-I467
custom binary download: no
current binary: Samsung official
system status: official
Any ideas of how to get this updated?
Thanks!
edit: I don't have AT&T service any more (although I still have the SIM), would that have anything to do with it?

IIRC 26% is the file ddexe, which is overwritten by the rooting process. Probably this file didn't get restored properly. If the automagical processes aren't doing it you'd need to go into /system using root explorer or similar to delete the invalid one and rename the _original one to replace it.

Well there was progress, but now it error'ed at 31%. Any other files in particular that I'd need to manually revert? I didn't see any others in system/bin that were _real.
Exact steps were: re-root, used ES File Explorer (with root permissions) to rename ddexe to ddexe_root and then rename ddexe_real to ddexe, removed root via SuperSU, attempted OTA update, got excited when it passes 26%, then got said when it failed at 31%.
Thanks!

There's a log that's generated during the OTA update process, off the top of my head I forget exactly where it is, but some googling should point you in the right direction. Examine the log and you'll see an error along the lines of:
file xxxxxxx: signature does not match

Well, I'm not quite sure which part of my tinkering did the trick, but I've successfully gotten my Note 8 (i467) to update OTA to 4.4.2.
I hadn't tried since December, so I started with just a regular update. It of course failed again, like it had been doing previously.
I then downloaded the 4.1.2 firmware file from sammobile and used odin 3.09 to flash the AP. I was surprised that doing that didn't wipe the device (it was late and I was sleepy), so I decided to try again. This time I added the firmware file to BL, AP, CP and CSC, trying to completely reset everything possible to stock. After 5-10 minutes, odin gave a fail message, but it wasn't clear exactly where or when it failed. The Note also would not boot, it asked for a Kies recovery.
I then used odin one last time to flash just AP. This succeeded and the Note was back up and running, with all my previous data intact. Next I did a factory reset within the Android Settings screen. Once that finished and I connected to wifi, it began to download the OTA update on it's own. And low and behold, it rebooted and got past the 31% mark it kept failing at... and made it all the way to 100%! Success!
So I know a lot of that wasn't necessary (and probably not even correct) but I was fed up with months of trying to get this to update so I just said to hell with it and started tinkering with random things. Just in case someone has the same issue I did and stumbles upon this thread, I wanted to record exactly what I did, even though I'm sure most of it was redundant and unnecessary.

Sprint Galaxy Note 4 Android 6.0.1 problems

I'll try this again (this website crashed when first posting this)
Leased phone (January 2017) use for my business. Has had (3) OTA updates since April. Started having issues after 3rd update mid-June (freezes / reboots). Most times have to pull the battery to get it to boot. Have wiped & restore several times, from Settings and Recovery boot menu. Cleared App cache and partition cache. Had the local Sprint Store 'supposedly' flash the OS from a PC but nothing improved. Described these issues below but was only met with a blank stare and an offer to open my wallet to replace with a refurbished phone without knowing what is causing the issue.
On some occasions when the device is not responding it heats up. Messages of Apps that stop responding include System UI, Package Access Helper, Touchwiz and Gmail, among others.
When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '
Further trying to diagnose, Sprint Zone / Device Diagnostics / Flagged / System Updates - always states 'Update now', but Settings / System Update / Software update message reads 'The latest updates have already been installed (N910PVPS4DPE2 / N910PSPT4DPE2 / N910PVPS4DPE2).
Investigated alternatives with Samsung (they replied the same day, Sprint Community message July 20th still hasn't replied) I can take it to a service center to have the hardware checked for a fee but it is not nearby and I'd like to first understand what the issue is.
From what I've described does anyone know what could be causing these issues? I have read where some updates were causing problems but I've tried most of those remedies and nothing has helped yet. Perhaps the Sprint Store, in an effort to extract more money (this is how it seemed) did not or was not able to flash the OS?
Any help would be greatly appreciated.

best thing to do is odin back to an older version and retake the update if you wanna go thru that again
but id recommend reverting back to OG5 and then flashing a rom you will have less reboots....as least on my end i did

JLFitzpatrick said:
...When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '...
Click to expand...
Click to collapse
The stock recovery you describe, it's normal for the Android guy to fall down and display the red x or whatever you saw when there's no update to apply but the dm-verity failure isn't normal. It could indicate bad repair or maybe it was rooted at some point? Wiping and Odin flash doesn't always rid the phone of that but Knox trip remains always until Samsung repairs a rooted phone. Dunno the cause of your dm-verity failure but maybe, if it was stock un-rooted all along, it may a read only partition failed or corrupted?
As suggested above, you may fix the dm-verity by taking a couple of OTA updates after Odin flashing an older one. Don't go back any older than OG5 though.
I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times.
That may solve some issues but it could be hardware failure or a corrupt partition. If the dm-verity goes away, see if your problems are resolved. If you didn't root and have a warranty, make whoever warrants it replace it; the failure is legit.
Sprint Zone and ItsOn is garbage IMO. Bloat that kills the experience that Samsung intended. Albeit, Samsung isn't so innocent with bloat ruining the experience either. Just my opinion on the bloat. By the time users add their own bloat, there's but enough RAM and with all the services running, battery takes a hit and phone lags. Run package disabler (search in Google Play) or root to manage it is what I'd suggest. FWIW, I have no random reboots or phone heating up while in standby running Marshmallow. My phone sleeps like a baby.
If no warranty applies and root is an option, you could try rooting with Chainfire Auto Root for Note 4 and then full un-root. The developer removes the dm-verity flag if it's there for modified read only partition reasons. But of coarse that also trips Knox warranty bit, so be aware. Dm-verity can prevent OTA's from updating but that's an alternative with root and Knox trip risks. No warranty should mean less risk unless the phone belongs to your employer.
Sent from my SM-N910P using Tapatalk

Thank you for your replies.
I had pointed out the 'dm-verity verification failure' text to the goof-offs at the Sprint Store, you'd think I was speaking in a foreign tongue. Phone is leased on our personal family plan and used for my business. I've never rooted it myself, not sure what the Sprint people did at the store but that text was there before they supposedly flashed the OS.
I apologize but am in over my head with the suggested repairs. Although having upgraded PC's am familiar with the process; revert to previous clean OS and upgrade over that. I'll take your suggestions and just have to study a little more to understand the correct procedure.
Yesterday afternoon I tried the folks at Samsung again since their support team had replied the same day before (still waiting for a support response from Sprint since July 20th) and went to a live support chat. The woman was very helpful but unfortunately, I had to jump off for a meeting. Before I jumped off she had me put the phone into Safe Mode. I had tried to get there before but the instructions I was given were incorrect (not found in recovery boot). It has since been in that mode and has been much more stable, still freezes occasionally but doesn't reboot itself and runs zippy as hell except for momentary freezes. I have the Chat ID # and will try again today to see what they can do before trying other suggestions. I gave them the HEX DEC numbers and it sounded like they could access the phone with those, this morning their Chat was full so I'll have to try later.
samep, if you don't mind can you give me some clarification on your suggestion:
"I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times."​
My interpretation:
Settings / Security / disable reactivation lock
Remove accounts (first back up phone log & sms to samsung account, back up wifi passwords to google account)
Settings / Backup and reset / Factory data reset
Boot to recovery menu / factory reset again (partition and dalvik cache evidently get cleared through reset)
Boot to recovery menu / 'flash an older tar' ? (Is this 'Apply update from ADB (Odin)' or SD card? This is where things get fuzzy. Can I load the stock tar (OS?) to a formatted sd card and apply the update from there or do I have to install Odin on a PC? Where is the best place to get a 'stock tar' (or Odin) from and which version(s) should I use for a Note 4, or is that explained on a particular website. There are many sources of information on Odin and firmware but I'm not sure which to trust if I need to do this would prefer to do this just once.)
Thank you again for your help, and I apologize for my ignorance on this subject.
But the best thing about ignorance is that it can be overcome with a little effort and knowledge.

To answer the question, boot into download mode from powered down state by holding volume down, menu and power. Yes, you use Odin installed on PC for that. But first you need the Samsung USB driver and Odin installed, plus the stock tar.
This thread will get you going with resources and brief instructions.
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
I'd suggest PC1 stock tar, then let it OTA.
(Your interpretation was mostly right up to the question about how to flash the tar after the factory reset and power down.)
Sent from my SM-N910P using Tapatalk

Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):

JLFitzpatrick said:
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
Click to expand...
Click to collapse
If you're feeling overwhelmed, you could bring it in. There's a chance it is hardware and the steps may prove redundant.
Up to you. At least you have something to point to as an issue.
Sent from my SM-N910P using Tapatalk

So I've gone through all the steps, phone is wiped, reinstalled Samsung USB Driver, have Odin open as Administrator and the phone in 'Android Recovery', Phone does not show up in Odin.
Have seen a couple versions of setting a connection (Odin open first, phone connected first); tried all of those and tried Odin open not as administrator. There is no connection. Tried other instructions to put into Developer Mode and enable USB bugging. Nothing, disabled USB bugging and booted back to recovery. Still nothing.
In Recovery mode it does not state 'Odin mode'. Tried the Recovery menu option 'Apply update from ADB' message reads 'Update from external storage diabled'. Tried 'Reboot to bootloader' (WTH), that does show Odin Mode at top of screen but phone still does not show up in Odin on PC. Then have to pull battery to reboot to Recovery mode. What steps am I missing here?
When phone is booted up normally it connects to PC without issue.

Finally got Odin to recognize the phone. Through a few searches I tried one remedy that suggested manually updating the samsung usb drivers in device manager which did the trick. Realized earlier that from recovery mode you do need to select boot to bootloader to get into Odin mode (listed on top).
Installed 6.0.1 - PD1 currently phone is installing OTA updates, hopefully this does the trick. Thanks again for your help.

On Tuesday the phone updated OTA from PD1 (April 27, 2016) installed via Odin to PE1 (June 1, 2016) then PE2 (June 29, 2016). Recovery Mode screen no longer shows dm-verity failure message so that's fixed. Phone is mostly stable, however still not as stable as it was on PE1 from what I recall by the release dates. Phone still freezes although it usually does not crash if I leave it alone but still does crash at least once a day. Safe Mode does not help, as the worst culprits are system Apps (Gmail, Drive are the worst).
It seldom overheats now but did yesterday. 3rd Party CPU cooler found Package Access Helper, Context Service and System UI as causing an issue. Cleared App Cache for all three but problems persist. Clearing App Cache in Settings / Storage takes at least three tries to clear all but 4.00 KB. I have been clearing Partition Cache every morning just to get through most of the day otherwise it will freeze when I first start to use it. Battery is also draining faster than before.
Any suggestions? OTA updates were at work on a stable WiFi signal. I'm thinking of Odin flashing back to PE1 (or PD1) and stopping further OTA updates. Anybody tried this? Will be traveling for a couple of weeks and need a stable phone, like I used to have. Thank you.

Samsung has been having memory management issues. IMO, this is the reason they keep increasing RAM in recent phones and getting help from Google. But 3 gigs of RAM should be sufficient.
A custom ROM may resolve that but you could try a package disabler from Google Play to freeze some unneeded bloat.
I couldn't say which stock version is best because I've ran all of them without random reboots and lag is minimum. The custom ROMs have been daily driver stable for me. I use them when traveling too.
Sending PM to OP as well with additional info.
Sent from my SM-N910P using Tapatalk

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?