Database Users

downgrading problem oreo to nougat s8

hello,
i managed to get the phone back to get in download mode. stock everything, no root whatsoever. my goal is to root my phone and i have experience doing so but i guess i was just unlucky this time.
i tried searching allover the internet for a fix, searching xda etc.
first off: my device is running oreo 8.0 and it's type is G950FX.
I want to downgrade to 7.0 because FRP lock is on, i did turn on oem lock before starting however i am unable to log in to my old google account connected to my phone.
when i try to flash any bootloader i get SW REV CHECK FAIL DEVICE 2, BINARY 1. i tried almost any trick in the book like downloading 7.0 from sammobile, flashing using odin.
the things i run into when flashing are:
1.can't flash the bootloader, probably because of frp lock.
2. when i don't flash the bootloader for 7.0 i get dm-verity error 0x2.
3. when i only flash 8.0 oreo pda & csc and then flash 7.0 pda on top i do get to boot but i get encryption interrupted error.
4. i am able to boot in 8.0 but can't get past the frp.
i'm out of answers, i really hope anyone can help me out of this situation as i want to use my phone.
Help is much appreciated!
edit: i tried flashing multiple versions of android 7.0 but i keep getting sw rev check fail bootloader device 2 binary 1
i basicly want to do this, a downgrade: https://forums.androidcentral.com/s...s8-plus/878062-how-downgrade-oreo-nougat.html
the problem is i didn't sign out of google or samsung accounts before resetting to factory

You can't. You have a new bootloader v2.
A simple search gives you this answer, if you have u2 and CRED bootloader installed you are stuck. No way to go back anymore.

i'm on u2 and CRED bootloader. i did search for this indeed but i didn't want to give up.
do you think there will be ever be a way to get back into my phone again?

If you have FRP lock good luck. I haven't seen a way yet.

I know it's been 5 months and you've probably either gotten rid of the phone or it's sitting in a dusty bin somewhere, but have you tried Galaxy Reaper? It's a pretty legit FRP bypass tool.
Edit: Scratch that. It's apparently been patched since I last knew it to work. Just wanted to double check, and sure enough..

Essential PH-1 downgrade

Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?

arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)

If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs

SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.

F$ck1ng OEM Update Disaster S8 Oreo

Tech savvy newbie here looking for newer information on the OEM unlock option on an s8 with Oreo, July 1 security patch. This is the international version of the phone, g950f, not the US one...
Is the 7 day wait still mandatory? I have tried following the guide with the manual date change, but no luck. I'm not sure if I am doing it right, or if it will even work.
Questions: when using the date bootleg do you have to have the SIM card in or be connected to Wi-Fi? does the phone have to stay on the entire time and connected or no? if I connect it to Wi-Fi do I have to worry about Android downloading even more updated firmware that will make this even harder to root?
If I can't bootleg the time using the above method what needs to be completed to initiate the beginning of the seven days? Does it need to be signed into a Google account? does it need to have Wi-Fi or a SIM card inserted?
I even tried negotiating with the Samsung technical assistance team and after 30 minutes still couldn't even get them to acknowledge that it has an oem unlock option LOL . I'd be grateful for any information that anyone can provide and it sure would be nice to not have to wait 7 days to root this rig. Thank you very much for everyone's time and thoughts...

KG Prenormal

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

Help Needed - Pixel 4 - No WiFi+Data after update

Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.

Did u solve this?