Related
Need help with this guys.
Here is what happened. First of all I purchased this phone from a Gumtree user a while back. (stupid I know). Anyways 2 weeks after purchase i noticed my imei number wrong in the phone as opposed to the back sticker. I searched around on the net and some people had the same imei number popping up due to prob rooting or unlocking (my phone is not rooted btw and it is unlocked but i have found out that it was originally locked to EE). I left it for around 6 months before i realised i needed lollipop and i was stuck on Kit Kat as the phone would not update,
So today I noticed someone online showing how to update through Kies using the serial number etc on back of my phone through recovery without Odin or root. I did this and it updated my phone to Lollipop and my imei was back to normal ... The happiness soon died off when i realised my phone would not let me pass the Samsung account stage. Just keeps saying: 'This device is locked because of an abnormal factory reset', and if i fill my details and press enter it gives the following: 'processing failed'.
My phone has updated to the latest 5.01 lollipop but I cant use it. Is there a way i can remove this or login with my details? E.G. by rooting the phone or downgrading to another firmware via odin or something?
I have tried everything. I've spent a whole day on Youtube and the net (I prefer to seek a prob usually before asking) and now finally i am resorting to ask for help from you advanced users.
I hope you can help me. :'(
I have fixed the issue. Well sort of. pending.. For anyone that wants to know..
I reverted to android 4.4. (i used three uk firmware)
downloaded slidesych, that then propmted me to open either a browser or samsung app store.
I clicked app store and then searched for any app to download. It then asked to login..
logged in and pressed back to the point of it asking for details. inputted my login and worked..
Went in to settings and removed the lock.
Now to update it again back to 5.1.1.
Update: Today flashed the stock rom for my phone via Kies by recovery mode and entering serial on the back of my phone. All is well to the point of my phone updated to lollipop but my imei has now gone back to square one. Nonetheless at least I have Lollipop
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
I'm having a similar issue. This afternoon, 2 apps threw errors and closed. I rebooted, which apparently was the wrong thing to do. The reboot stalled on the AT&T logo and stayed that way for 5 min - the unit became very hot & the power button did not respond, even while holding it down. I got into recovery, cleared the cache and factory reset, then rebooted. The unit came back up and started reinstalling everything. I took it back down into the download status and attempted to reload 935x via Odin, only to stall at "initialzation" [sic] as you did. I got out of that after waiting for some sort of response. SuperSU was still in my apps as was Root Checker. Root Checker indicates the system is rooted. SuperSU indicates it needs the binary updated. BusyBox and TiBu indicate they cannot find root. I deleted all the root apps and tried reinstalling root via adb which completed successfully, but the same outcome with all the root apps. So I'm not sure if I'm still really rooted as Root Checker claims, or not.
EDIT: I just saw that I have 2 "Knox Settings" apps. Clicking on either returns, "Unfortunately, Container Agent2 has stopped."
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
NovaEDM™ said:
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
Click to expand...
Click to collapse
I was having the exact same problem you had with Odin. It seemed I was able to flash stock firmware using this version of Odin: http://www.mediafire.com/download/2t2sjqxtogbkafk/odin_3.12.3.rar
rob219 said:
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
Click to expand...
Click to collapse
did you have any problems with the u version of the s7 edge firmware, like the fingerprint scanner not responding? i am on that version and cant get any odin version or any version of s7 edge g935a firmware to flash, tried unrooting and was forced to use the U version of the s7 edge firmware, everything works except the fingerprint scanner, cant get back to full stock firmware, need help!
im having the exact same problem, when i put my phone into download mode and flash the stock at&t firmware, Odin get stuck in "initialization" and my phone screen displays and error message.
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
nicetucu said:
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
Click to expand...
Click to collapse
I used Odin_v3.12.3_Patched_SHA256 to flash the 935U Firmware then used Odin3_v3.11.2 to flash the June Firmware release.
Excellent news and a solution i havent found anywhere else yet!
Follow up from - https://forum.xda-developers.com/galaxy-s8/help/restore-imei-attempt-stock-rom-flash-t3802527
TL;DR attempted to re-root as soon as the bootloader unlocked. It all seemed to stick again, and got the big red message of doom again.
"Official Binaries Only" - Last time i was able to restore to at least switch on the phone to run down the rmm state timer to zero to flash again.
Tried the several methods of flashing through a locked bootloader (old BL file, quickly restart download mode and spam start on odin, etc) - literally nothing would allow me to flash anything that included the BL file. IMEI and baseband remained unknown. Phone went in drawer for a few days.
Just went and downloaded the latest XSA (Australia, Unbranded) build - https://www.sammobile.com/firmwares/galaxy-s8/SM-G950F/XSA/ and guess what boys and girls?
This sucker flashes straight away with Odin 3.13.1
It has completely restored my IMEI and baseband, i now have full Cell connectivity again, and its all back and working again. OEM unlock is still disabled, Samsung Pay still locked out which is fine, but otherwise, i have gone from brick to fully working Exynos S8 again.
TL;DR IF YOU HAVE ISSUES WITH A BRICKED PHONE BECAUSE IT WONT LET YOU FLASH ANY STOCK ROMS TRY THAT ONE.
Thanks for the replies to my other threads trying to help out with this. Much appreciated.
Peace out.
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Ive had a few cracks at this now but the date keeps resetting itself when you reset the phone despite having the automatic update option switched off.
Thanks for the info tho ill keep trying.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, boot it and setup once. Then reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
kratosjohn said:
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, and reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
Click to expand...
Click to collapse
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash) - I used comsy as it is mentioned in hte post OREO S8 update. It allows TWRP to be flashed but maybe thats whats breaking everything else. Ill try magisk next.
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
UPDATE - Everything restored installed titanium backup root held. Rebooted phone aaaaaaaaand - "Only official released binaries are allowed to be flashed" - Back to square one. Will attempt same reflash now, but the root procedure kills everything. Back in download mode again. RMM State: Prenormal returned.
It is now succesfully flashing the stock rom in Odin 3.13.1 - Accidentally started it with Comsy and it DID NOT WORK. You MUST use the normal version to flash the rom im using.
Looks like we def have a stable way to refire up the phone again, and get around RMM state prenormal nice and quickly, so ill go ahead now and try and find whats going on with things breaking afterwards!
Thanks again guys.
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Funkmonkey said:
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash)
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
Click to expand...
Click to collapse
Someone should clean this up and get it stickied.
I imagine there are alot of users here with this same issue, after the CRED update we can't downgrade our bootloader, and in a panic you can get stuck here.
kratosjohn said:
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Looks like that wont be an issue any more to be honest this phone is now a backup thankfully so i can play around with it to my little hearts desire.
Im about to try the magisk install. SuperSU/Aroma definately breaking something somewhere. Or verity. I dont know but rooting the phone at the moment is killing it again.
Also, i have NOT lost IMEI or baseband this time. At the very least for Australian SN-G950F phones, this is a 100% flashable stock rom regardless of your RMM or phone status. I cannot say this for any other model in any other country on any other carrier, but this is all working for a carrier free Exynos S8.
Maybe y'all better archive the actual stock somewhere before someone realises theyve made a mistake somewhere and it gets pulled. Im definantly backing it up.
I just got that oem unlock trick to happen in 2 shutdown/restarts NOT reboots. BUT. I did NOT enable developer mode until i had disabled automatic time updates and turned the date back 8 days. The option came up instantly. Is something comparing a hardware clock deep in the system to a software clock in the os to and developer mode comparing something in between? Either way, on to reflash TWRP again now. This is a good day.
Click to expand...
Click to collapse
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Funkmonkey said:
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Click to expand...
Click to collapse
Have you found and used this after getting your phone setup right (w/twrp)?
I think you should flash magisk, then this after.
After I had this "panic" I flashed the custom rom I was aiming for (once RMM: Official). That rom has a kernel with the RMM state fixed/locked.
Maybe look for a custom kernel if you want root, I believe this is the fight we have to put up even on stock w/root.
Download the Australian stock rom and install it but do not recover IMEI or coverage. I think it's because my G950F (singlesim) cell phone thinks it's G950FD (double sim). This causes the cell phone to get confused and not recognize any imei or sim. Does anyone know how to fix it?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Do we need to factory rest or just reboot phone after we change date?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
Sorry i missed your reply i hope you got it fixed if not post again and ill see if i can help. Ive definantly gotten that oem unlock trick working which is awesome but its fiddly. I dont think it works if you turn on flight mode and you have to let the phone fight you between 'no automatic date and time' and the network forcing the time.
Of course now i cant get the oem unlock trick working...
RE the dual sim issue... i think you would need the stock rom specific to your model try sammobile, see if there is a CRED release for your model. I cant guarantee it will work tho.
kratosjohn said:
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Click to expand...
Click to collapse
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Smartphones13 said:
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Click to expand...
Click to collapse
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Funkmonkey said:
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Click to expand...
Click to collapse
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Smartphones13 said:
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Click to expand...
Click to collapse
I think we might be looking at different issues.
This is to fix a semi bricked phone that has locked up its bootloader. In the past to resurrect a samsung all you had to do was flash twrp and your new rom but since Oreo some funkiness has been added to the system which only lets you flash a stock rom, (i.e. restoring a phone to factory settings and software) via ODIN/HEIMDALL then it locks up the bootloader for a week so you CANNOT flash anything into the phone that modifies the bootloader (i.e. TWRP OR *any* rom) until its timer runs out. This is most likely an anti theft feature esp with samsung and google pay use as it means there is no way to easily break into a stolen phone and use it as normal, and reflashing breaks all of the security features of the phone (e-fuse) - no knox no samsung or google pay no samsung pass as your device is insecure and could spoof false banking details etc.
The rom i linked to is important as it is a new AUSTRALIAN unbranded STOCK rom, that for some reason you can flash OVER a locked bootloader, meaning you can resurrect (australian at the very least) SN-G950F phones (exynos)
If you already have a working phone and can get to your developer settings then most of this thread is irrelevant to you.
Now - OEM unlock - You just bought a brand new galaxy from samsung (or youre me and you bought a MINT second hand one from cash converters for $700 less) - your phone is factory standard and schmicky. THE BOOTLOADER IS LOCKED. THE RMM STATE SHOULD NOT be triggered. If right now you went to flash something it would fail.
So you go to about phone - software information and you tap 'build number' seven times to unlock developer mode. Hit back twice and developer mode will be at the bottom of settings.
Click into this and you should see without swiping down 'OEM UNLOCK' - If you enable this, you can then reboot straight into download mode (power vol down and bixby) and flash twrp or whatever rom.
If you dont see this option, you either have a snapdragon model (youre **** outta luck permanently) or RMM is PRENORMAL and you either have to try the unlock trick(s) or leave your phone SWITCHED ON for 1 week and it will unlock itself.
The biggest issue at the moment is that i keep breaking something after i attempt to root so not sure whats happening there so use major caution.
Now as i said the trick posted above to unlock without having to wait a week (which i think youre asking about) im now not sure how it works because i cant get it to work any more.
Automatic time and date off, set date back 8 days, reset the phone. Do this a couple of times, then turn on automatic date and time again. HERE THERE BE ISSUES. When i first did it - i switch off time and date and change then reset, when the phone came on, auto date and time was on again. Turn off, change date, reset. Again, its back on. Turn off, change date, reset. Its back on. I give up and leave it, and notice later the option was available, so it worked. I broke the phone, reflashed again, did the trick in ONE reboot. Fcked something again, reflashed, now auto time and date stays off and the trick wont work so i cant help you with that until someone comes up with more info im sorry! Its a bit zarbis.
Im not going too nuts trying to fix it as i now have a fully working stock backup phone that sits on DeX plugged into my bedroom tv full time and im not into custom roms, root keeps breaking the phone, and ive sonce replaced it with a mint S8+ that im not even THINKING about considering rooting until its replaced maybe next year. Its not as easy to get around anymore and thankfully a) picasa and hangouts are no longer stock apps and can be banished and b) you can now disable all the other built in apps natively so its now a lot more bearable with a totally stock phone.
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
ugh, the active line... there hasnt ever been much support for those. All you can really do is keep flashing the stock firmware and hope that the errors resolve themselves.
Side note: have you noticed how they stopped making the active phones? They were a dismal failure. All they are is the regular phone in a case that you cant take off :/
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
Might try redownloading a different firmware from a differ location. I had this issue on a lg back in the day the camera wouldnt work no matter what I always restored stock with one firm I had. And it ended up being a bad download. Another possibility is a bad NFC chip. If it's new I'd have it warranted
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
dchalkley said:
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
TheMadScientist said:
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
Click to expand...
Click to collapse
Yeah, it's working on the 5CSI3 build from October 2019, there's been two recent updates since then (and another will come at the end of the month). I don't know what's happening as no one else has reported this issue .
Just wanting to be on the most recent version for security and the annoyance of having data wiped every update.
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Vcek said:
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Click to expand...
Click to collapse
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
moncd6 said:
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
You can backup your data with Samsung backup and restore to Samsung cloud or to your PC with Samsung's Smart Switch app.
As for tutorial I'll try to make one with images for the latest ROM G892AUCU5CTF4 dated 20-Aug-2020 with August security patch. I'll upload it later as I still have to backup my phone before updating.
Thanks!
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
moncd6 said:
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
Click to expand...
Click to collapse
It doesn't have any bugs but some people have issue with flashing new builds, if you have this issue just install CSI3 build or earlier
dchalkley said:
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
... And to top it all off the NFC app is draining my battery.
Click to expand...
Click to collapse
Same. I also tried CTA2 and CTL1. Everything after CSI3 has NFC crashing and excessive battery drain. I've tried multiple flashes on multiple phones.
dchalkley said:
I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Same.
dchalkley said:
I don't know what's happening as no one else has reported this issue .
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
Click to expand...
Click to collapse
Same here. I used Odin 3.14.1, though.
Vcek said:
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Click to expand...
Click to collapse
This did not work for me, not even with "Nand Erase" checked.
moncd6 said:
It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...
Click to expand...
Click to collapse
Same. The problem of the secret dialer codes not working parallels the NFC problem for me; that is to say that it doesn't work on any firmware after CSI3.
moncd6 said:
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
Click to expand...
Click to collapse
Can you please upload G892AUCS5CSI3? it's all dead links i got
rerenz said:
Can you please upload G892AUCS5CSI3? it's all dead links i got
Click to expand...
Click to collapse
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
voidxor said:
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
Click to expand...
Click to collapse
Finally, it works! My NFC is back. Thanks, pal.