KG Prenormal - Samsung Galaxy S8 Questions and Answers

I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.

Someone?

up.

costafabiof said:
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Click to expand...
Click to collapse
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561

spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
I just got it to work. I'm just testing the procedure again to make sure and put it here.

I arranged this item like this.
In Android 9, installing TWRP soon after installing Android no longer works, after installing TWRP, it appears in red "only official realease binaries are allowed to be flashed" and restarting in the download mode appears KG STATE PRENORMAL.
To fix I installed Android 9 again without the TWRP, Magisk, etc, that is, pure. I entered the system and started the updates by Google, when I came back to check in download mode KG STATE was with CHECKING which is normal.
With this I returned everything to normal, I installed TWRP, Magisk, etc. and I continued.

spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.

DSMB said:
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
Click to expand...
Click to collapse
Have a look here
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post79745844

Related

Samsung SM-T580 FRP Lock

Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
TheHapist said:
Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
lewmur said:
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
Click to expand...
Click to collapse
I can't do anything as I had the tablet already locked :/ I can just access the recovery and the download mode (As well as the normal boot, but it is pointless here).
I already flashed a stock ROM via Odin, and it worked fine as it was the same version in the tablet
TheHapist said:
I can't do anything as I had the tablet already locked :/ I can just access the recovery and the download mode (As well as the normal boot, but it is pointless here).
I already flashed a stock ROM via Odin, and it worked fine as it was the same version in the tablet
Click to expand...
Click to collapse
This one works with the latest build from PL4 to QC2 ( P= 2016, Q= 2017 ) , Android 6 ; not work with Android 7
https://www.youtube.com/watch?v=Xo9uJDDuSxw
Try it, if you can get the Assist then it will work as you can open Chrome to download Google Account Manager to add you own Google account and do the factory reset or just keep it as you are the owner now, taking full control of the tablet.
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
lewmur said:
Before attempting to flash ANY ROM on a T580, you have to enable "OEM unlock" in the /Setup/Developer options. If you don't, the way to unbrick the tablet is by using the Samsung Smart Switch app via a PC.
Click to expand...
Click to collapse
If you can go to Setting and enable the OEM Unlock, you're not FRP lock and in owner account.
FRP ( Factory Reset Protection ) is a secured method from Google prevents anyone to continue in the settings without passing the verified account steps.
Without the previous synced account ID and password, it will keep you in a loop in the setting steps.
Beut said:
This one works with the latest build from PL4 to QC2 ( P= 2016, Q= 2017 ) , Android 6 ; not work with Android 7
https://www.youtube.com/watch?v=Xo9uJDDuSxw
Try it, if you can get the Assist then it will work as you can open Chrome to download Google Account Manager to add you own Google account and do the factory reset or just keep it as you are the owner now, taking full control of the tablet.
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
If you can go to Setting and enable the OEM Unlock, you're not FRP lock and in owner account.
FRP ( Factory Reset Protection ) is a secured method from Google prevents anyone to continue in the settings without passing the verified account steps.
Without the previous synced account ID and password, it will keep you in a loop in the setting steps.
Click to expand...
Click to collapse
Obviously it is to late for the OP to change to "OEM enable" setting. I was merely pointing out the cause of the problem. But it also seemed apparent that the Google account settings are unknown.
I bought a tablet on eBay that had this problem and was able to get it working using Samsung Smart Switch run from a PC connected to the tablet in the download mode.
TheHapist said:
But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
The latest build QC2 from US can bypass easily by Google Account Manager app, I believe it will work with your build.
Beut said:
The latest build QC2 from US can bypass easily by Google Account Manager app, I believe it will work with your build.
Click to expand...
Click to collapse
Yep, it WORKED ! I'm really grateful, I was losing hope. Thank you so much !
The hapist how did you manage to bypass the frp on the tablet I am having the same problem I can’t get it to figure out please help me I have the t 580 Samsung Tab a 10.1 running Android 7.0
El sal said:
The hapist how did you manage to bypass the frp on the tablet I am having the same problem I can’t get it to figure out please help me I have the t 580 Samsung Tab a 10.1 running Android 7.0
Click to expand...
Click to collapse
Watch the youtube video posted by Beut in post #4
TheHapist said:
Hi everyone !
I'm actually working in an IT centre (Don't know how to call that, or to traduce to you), and I just got a customer who handed me a Samsung SM-T580 tablet who is FRP locked... I've been searching since 3 days now, trying various methods, even trying a downgrade to other versions, but no luck. I've searched on XDA to see if anyone has got the same problem, but everyone has a different build number, as mine is T580XXU2AQA2. I've seen that if the 3 finals letters/number are PG1, I'm in luck, but if they're PL4, I'm unlucky. But what about QA2 ? And what about the FRP Lock on this build ?
Thanks for help, as I begin to lose hope...
Click to expand...
Click to collapse
I have same problem QA2 & FRP lock SM-T580 but I have the original owners info but error message still says wait 24 hours?????
Ahlonnae said:
I have same problem QA2 & FRP lock SM-T580 but I have the original owners info but error message still says wait 24 hours?????
Click to expand...
Click to collapse
You see this message because you're still at first page of sign in. Reset it: Power + Volume Up + Home you should get to the Recovery and do a Factory Data Reset.
If you already have original owner information, you shouldn't have any problem of setting the tablet at the step of verifying google account.
I have done FRP bypass on the SM-T580 at least 10 tablets a day, so I can say FRP of Google is a joke. I have to deal with FRP lock everyday and I only need 10 minutes to bypass it.
[EDIT] Damned font I misread FRP for FAP
Posted elsewhere, but as I'm getting rather anxious and as I'm waiting for DBT-T580XXU2BQE4-20170525170357.zip to download... I ended up with a FAP lock. I can't find out if there's any difference from FRP lock - is there any?
Also, about Smart Switch, do the instructions from https://www.sammobile.com/forum/showthread.php?t=34745 apply? Smart Switch tells me that the device is unsupported and I don't get the Device Initialization tab!
Thanks!
[EDIT2] FW downloaded. Tried to use Odin, but there are four options: BL/AP/CP/CSC. Yet the FW package has these entries:
AP_T580XXU2BQE4_CL11316739_QB13491827_REV00_user_low_ship_meta.tar.md5
BL_T580XXU2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
CSC_OXA_T580OXA2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
HOME_CSC_OXA_T580OXA2BQE4_CL11316739_QB13491827_REV00_user_low_ship.tar.md5
So which one is CP?
You only need to load BL, AP, and CSC, ignore the HOME_CSC, but it seems you're flashing the Android 7 build from Germany which no method works.
You need to downgrade to Android 6, region doesn't matter for the purpose of bypass FRP. When it's done, flash back to your original region in Android 7.
Cellular South PL4 is the build you can downgrade and bypass FRP.
Beut said:
You only need to load BL, AP, and CSC, ignore the HOME_CSC, but it seems you're flashing the Android 7 build from Germany which no method works.
You need to downgrade to Android 6, region doesn't matter for the purpose of bypass FRP. When it's done, flash back to your original region in Android 7.
Cellular South PL4 is the build you can downgrade and bypass FRP.
Click to expand...
Click to collapse
First of all, thank you for your reply indeed.
Yes, I guess it was from Germany since German was its language when it first booted and it was 7.0.
So I'm downloading XAR-T580UEU2APL4-20170407113933.zip (Cellular South PL4) and flashing it with Odin, but once it's done, how do I flash 7 again? Use Odin with the initial BL/AP/CSC that I got?
Again, thank you!
[EDIT] Oh yeah, 6.0 flashed successfully and I'm off FRP lock!!!! Thanks so much... Now I guess I turn on OEM enable in Dev options and flash BL/AP/CSC in Odin?
No need to flash back if you want to keep current US build if it has your prefer language.
However, it's now US tablet, it only update the latest one from US build.
No need to turn on OEM unlock if you know your own Google ID and password.
If you like, flash the Europe build as it has more languages than US one, the same way as you downgrade firmware: load BL, AP, and CSC to Odin.
You're right. I was asking because I thought I'd have lost OTA, which was not the case - device updated OTA to 7.0 so I then proceeded and rooted it again. *Now* OTA is dead, but I'm good.
I was thinking, probably, than on Samsung devices tripping Knox would disable OTA.
Thanks for your reply once more
Tripping Knox doesn’t disable OTA but if the status of firmware is Custom, you won’t be able to update software. I have some tablets which have Knox count more than 1, they update normally because I run stock firmware
Beut said:
Tripping Knox doesn’t disable OTA but if the status of firmware is Custom, you won’t be able to update software. I have some tablets which have Knox count more than 1, they update normally because I run stock firmware
Click to expand...
Click to collapse
Yup! I'm learning by doing
I guess that having an official FW but custom recovery equals to Custom, correct? Which means if I reflash original OTA will be back?
In the setting, About Tablet, Status, if the device status is Official, you have no problem of update via OTA.
Or in Download Mode, if the System Status is Official. I believe your system is Custom if having custom recovery.
Rooted device will become Official if you flash back the stock firmware , however the Knox counting is not rolling back to zero.
Yup, I did know about Knox (that would defeat the purpose, right? ).
If I'm not mistaken flashing original FW will erase data, no? So I'll save it for when there's a decent Oreo ROM out there. Then again, it won't be Original even then so I guess I'm off that road, but I don't think Samsung will be releasing any new OTAs any time soon so there's no meaning in it, surely?

Felt confident, shouldnt have

I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?
PA_Pyroholic said:
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?
Click to expand...
Click to collapse
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.
Fear_The_Fluff said:
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.
Click to expand...
Click to collapse
I did get the update to 5 unfortunately and am no longer with sprint, paid everything off an account is closed. I did some more digging and realized many mistakes yesterday. I tried the latest 'U' FW (binary 4), it failed, and then I tried the latest 'P' FW (binary 5) right afterwards and it failed... But I didn't cycle the phone in between attempts so of course it was going to fail. Ended up reflashing with the latest 'P', and went through the easy, "just say yes to everything" set up and all the bloatware reloaded onto it. Reflashed and wiped device, and was careful this time... 90% of the bloatware I wanted was gone. Package disabled the rest. Only thing I can't seem to get rid of is the Sprint logos on start up.
After stumbling my way through this first attempt, I'll do better research next time!
Sent from my SM-G935P using Tapatalk
PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
Unfortunately, your phone is on the newest firmware, B5. You'll only be able to flash one of the latest sprint firmwares to get your phone to work. All the other carriers and U firmware are still running an older binary boot. You may also need the special version of ODIN...you can probably find it in the same forum about installing the U firmware. But if you download the latest sprint firmware, your phone should boot again.

**FIX** BL Flashed through RMM State Prenormal (OEM Locked) - IMEI/BASEBAND RESTORE

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.

Sm-g955f bricked - flashing stock firmware only made it worse

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

[issue found][archived] FRP / OEM locked device that won't start OS

Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .

Categories

Resources