• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

New Update Caused Endless Rebooting -Tried most Steps

You'r doing quite well. Some Samsung firmware is provided in 4 or 5 files each one is paced in AP, CP, Bl,or CSC if it comes with a 5th that would be the PIT file. The flashing the Partition Information Table (PIT) file is not necessarily. To my understand it will wipe your imie number. Having a Md5 match you can rest assured your firmware is valid. Breath easy knowing you have been successful. Its a bit confusing at first. I got say, impressed with your progress. You set your mind on it and you didn't give up.


imei= international modelphone equipment identifier.

PS= Sorry for tw bad g4mmer my dumb cat keeps rubbing up against my phone as Im typing.


Okay, so no luck, didnt even start, says failed in the log:

b281337c123754cf47e09ff1743eb0a0.png
 
As for me, Im very familiar with my device and also an XDA member. I can say specifically this or dont do that, with confidence when it comes to an sm-n910p. With your device, I know the overall process is basically the same.
The more information you know better. The XDA member may know something that is specific for you device that I am not aware of. For instance, I knew of only 2 of the 3 unofficial Odins. I've come across them here an there on XDA but never acquainted with them since the normal Odin works for me.
 
I notice it Odin 3.1401 is that correct? Must be a new updated Odin. My eyes are as good as they used be so do you notice something that indicates the nature of the Odin fail? I just see at the bottom fail with no indication.
 
Odin is finicky, some work for one device but not another, thats Odin. At this point you have several options. I can only say, if it was mine phone I'd start by the process of elimination. As I know you want your data then will leve the csc as the last option.
 
Odin is finicky, some work for one device but not another, thats Odin. At this point you have several options. I can only say, if it was mine phone I'd start by the process of elimination. As I know you want your data then will leve the csc as the last option.


No, it just says whats there in the log section. Hmmm. idk

263015186f60a1384ea0e2132f183dd7.png
 
Some opinions, Hopefully its just installing another Odin will work

Reinstall drivers, uninstall Kies, use a different usb port/cable, use a different version of Odin, use a different pc.

Reboot your phone into download mode, but yet not proceed, plug into pc, open odin (as administrator), put the firmware files in their respective places, and finally press vol up to proceed in download mode and press start, it must solve.

Rightclick -> Run as administrator
 
Some opinions, Hopefully its just installing another Odin will work

Reinstall drivers, uninstall Kies, use a different usb port/cable, use a different version of Odin, use a different pc.

Reboot your phone into download mode, but yet not proceed, plug into pc, open odin (as administrator), put the firmware files in their respective places, and finally press vol up to proceed in download mode and press start, it must solve.

Rightclick -> Run as administrator


Thanks. I tried all of that above. Different odin version, running as Admin, and the plugging it but not proceeding yet until files are loaded, etc.... I saw that on reddit too, bunch of people said that worked for them, had my hopes up!
 
Last edited:
Okay, a lot of this is sadly too complicated for me. Does this flashing with odin thing erase my data?
I mainly want to backup some pictures and files first, so perhaps I try ADB? I saw it mentioned online, I have to look into that. I dont know if it applies to me.


-The first thread you linked is about someone using the wrong odin and it bricked their phone.

-The second thread is about a patched odin file, the OP posted 4 different attachments of a 3.13.1, so would it matter which one I download if I proceed to use Odin?
I read through it, including the recent posts on page 22, but I dont know what much of it means.

-For the samsung firmware, I just download the latest one here, or should I be using an OLDER version incase this is the issue causing my rebooting loop?
sdg.png
Yes it does so backup important photos or data if you can
 
Yhere a slight possibility it could be a emmc/mmc motherboard failer but I don't think its very likely since the S8 is not that old. However, it is easy to confirm if you boot into stock recovery as a read failer or something like that. Its been a while since one of my N4s had emmc fail.
 
Yhere a slight possibility it could be a emmc/mmc motherboard failer but I don't think its very likely since the S8 is not that old. However, it is easy to confirm if you boot into stock recovery as a read failer or something like that. Its been a while since one of my N4s had emmc fail.

When you say boot into stock recovery, you mean wiping the phone? Or is that some button combo thing to get into it?
 
You cacn wipe but bye bye data. Botton thing reboot to recovery look at top and at the bottom. That way you know if it is or if it isnt .
 
Also, Iv read contributory information with USB enabled. Some say it needed to be enable in order to flash firmwares and others ssy the have flash it with mo problems with USB disabled. My device os rooted with TWRP custom recovery and my setting are set to usb enabled always. Not sure if that has any baring but it might.
 
Yes it does so backup important photos or data if you can

I was not able to access the phone to back up anything
Also, Iv read contributory information with USB enabled. Some say it needed to be enable in order to flash firmwares and others ssy the have flash it with mo problems with USB disabled. My device os rooted with TWRP custom recovery and my setting are set to usb enabled always. Not sure if that has any baring but it might.

You mean like USB debugging? Mine is enabled, and so is developer options.
 
Are you positively sure all .tars are in the the correct slot. AP, CP, BL? 100% sure? If there mismatched bingo that the problem.
 
Last edited:
Are you positively sure all .tars are in the the correct slot. AP, CP, BL?

So I just tried re-flashing, and it worked! Second times the charm I guess! :D:D

And Yes I believe so on the question about the .tars in the correct slot. I closed out odin, and reloaded them slowly, couple times when the failing issue was happening. So Idk, just had to flash it twice I guess.

When the phone came back up, it says "software update unsuccessful", I presume that is the OTA that caused this issue. Eventually I will be force to reinstall it. May happen all over again, but I will have my data backed up this time at least! What a 3 day nightmare this has been, did not think I was going to be able to avoid a factory reset.
 
So I just tried re-flashing, and it worked! Second times the charm I guess! :D:D

And Yes I believe so on the question about the .tars in the correct slot. I closed out odin, and reloaded them slowly, couple times when the failing issue was happening. So Idk, just had to flash it twice I guess.

When the phone came back up, it says "software update unsuccessful", I presume that is the OTA that caused this issue. Eventually I will be force to reinstall it. May happen all over again, but I will have my data backed up this time at least! What a 3 day nightmare this has been, did not think I was going to be able to avoid a factory reset.

Its been a long time since I flashed separate partitions but I remember once in Odin being confused to what.tar when into each slot. The names of each file dosnt say AP or Bl or CP. The correct order is a must.
 
Back
Top Bottom