Database Info

FRP Lock ON, Secure Download Enabled, No Serial Number, Custom Boot Lock -HELP!

I have experience rom'ng Samsung phones and have never run into something this bad. My S6 Edge SM-G925P will not flash any stock/non-stock rom. Tried OI1/OH/OJ/OF, all fail Nand Write. Some suggest, split ROM in pieces and install separately in ODIN, but do not explain what that means and how to do it. When USB (official samsung cable) plugged in, phone gives Smart Switch error. I am attaching screenshots as these say it all. Please, any 'good' advice on how to attempt fixing this and getting ANY Android OS version installed? Am at wits end with this. Also, I can't get the SN because the dog ate the box and it's not on the back of the phone, plus phone won't boot other than download mode.

I was finally able to successfully install a Stock ROM and when it rebooted it showed the Samsung & Sprint logos and started charging. Currently at 40% and will try to boot the device shortly. I wanted to share that what helped was to use this specific ODIN version found at http://www.galaxys6edgeupdate.com/odin3-v3-10-6-download/ and OJ7 rom. Note the image on the website shows Odin with SM-G920/G925 where other ODINs don't show this. Confirmed! The phone rebooted and is now working. As a matter of fact, much of the data on it was maintained. Now just need to unlock it!

What files did you use.. I am on CUstom Binary and Status and get a nand fail on sboot.sh with a SW REV CHECK FAIL DEVICE 4 BINARY 3

anonymoustl said:
What files did you use.. I am on CUstom Binary and Status and get a nand fail on sboot.sh with a SW REV CHECK FAIL DEVICE 4 BINARY 3
Click to expand...
Click to collapse
I am in the same boat as well ;(

yall still need help with frp lock? if so message me

Kennii said:
yall still need help with frp lock? if so message me
Click to expand...
Click to collapse
Kennii,
I am experiencing the issues mentioned above. Can't flash with any of the stock roms using odin for my SM-G925P neither can come up with a serial number that works with smart switch.
I found a serial number for SM-G925I and the smart switch software goes to the next step. Do you have any serial number that goes with SM-G925P?

Stuck at Powered by Android please help SM-N915G

My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.

Please give some help, thank you.

Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you

wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?

The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.

wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.

The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.

wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.

wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.

The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:

As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.

Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much

Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.

Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.

Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you

Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.

Need Help With My S6 ASAP Please.

Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.

Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).

Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.

wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.

Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!

wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please

I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it

JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.

cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!

[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse

Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:

Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.

cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail

Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?

Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number

S8+ g955f stuck at Samsung logo, bad flash

Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!

thedan55 said:
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
Click to expand...
Click to collapse
Flash full firmware not just AP file. Flashing AP file only is more than likely the reason for difference in storage size.
No need for pit file. If it is needed it can be exacted from the firmware that you have downloaded.

I did flash all 4 files not just the ap. I only wanted to show the version etc
Now when I try to flash Odin says failed

What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin

spawnlives said:
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
Click to expand...
Click to collapse
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.

thedan55 said:
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
Click to expand...
Click to collapse
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.

spawnlives said:
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
Click to expand...
Click to collapse
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?

Why do I get this message every day? Throw the darn thing out already.

thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.

Buy your nephew a damn phone

thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
pego99 said:
Buy your nephew a damn phone
Click to expand...
Click to collapse
I did buy him this phone. Just because it's a little messed up right now doesn't mean I should just thrown it out. This entire forum is dedicated to invigorating devices and keeping them going. XDA didn't accept the philosophy of throwing out devices when they can be repaired. I've been here long enough to know that.
Ffs people are still developing for the hp touchpad and m7 Windows devices!
Unsubscribe from this thread mate. Delete your replies so you don't notifications.
There's no need for your unhelpful comments when others are trying to be of assistance.

spawnlives said:
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Click to expand...
Click to collapse
Thank you very much for your replies. It's very much appreciated mate.
I did flash the pit file and subsequently got errors in odin. I want aware that I was trying to downgrade. I've download from official site and will try flashing today.
Again thanks for the help. Been a while since I've had to do this lol I think the last device I was rooting and roming was my note 3! The support for it is still going strong though!
Cheers

I guess at some point its best to move on. My grandsons S8 had the digitizer go bad tried to fix unsuccessfully bought him a used on on fleabay for $150.

@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.

thedan55 said:
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
Click to expand...
Click to collapse
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?

pego99 said:
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
Click to expand...
Click to collapse
It took less than an hour to fix this phone, that's a cost I can stomach.
if you had actually READ the post instead of commenting asinine remarks them you would know how the phone for corrupted in the first place.
Please stop replying to this now.