Related
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.
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
esjames said:
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
Click to expand...
Click to collapse
How long do you think that will take since this is my only phone?
You will have to wait until an Odin flashable package of CRD4 or another bootloader 3 firmware becomes available. Without a complete BL3 system flash you are SOL
I think I'll hold off on the OTA update until I hear some safe reports
LordAbolition said:
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Nitefire77 said:
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Click to expand...
Click to collapse
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Do you have z3x?
You dont need z3x to flash the tmobile variant, but it makes it far simpler. Which version of odin are you using? If its the prince comsey you will more than likely get the mismatch error.
LordAbolition said:
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Click to expand...
Click to collapse
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
SprintBama said:
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
Click to expand...
Click to collapse
No worries. I fixed the situation. Thanks for reading!
I am clarifying this, this is s8 plus now stuck on rev3? I got an s8 and went to another forum thread and was told this isn't true. I am stuck on rev3. FYI, updato has the new s8plus firmware if you haven't got it already.
Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.
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
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.