Related
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
I've never rooted my Galaxy S7 before, but looking at doing it now. I have the AT&T SM-G930A model. My phone just installed OTA Oreo. In my searching and reading here I have found several threads that discuss the rooting process for older versions, but not Oreo yet (on my model).
I realize that Oreo is newly released, so this process may not be available yet, but I was hoping to get more information. Can I root my G930A with Oreo installed?
I'm also hoping to get a more streamlined explanation of the rooting process. All the other threads I have read don't seem to really explain the process; they just say, "download this file, flash with odin". As I've not rooted before, I am hoping for a little bit more explanation of what the process is, like what the file to download is and how to flash it with odin.
It also seems to matter quite a bit of what versions of odin and TWRP etc are used. What versions would I want for this process?
Thank you!!
I'm trying to root my AT&T G930A as well with Oreo 8.0. Sadly the bootloader is locked and I can't find any info on processes for rooting.
The method for older versions was to flash an engineering bootloader to allow Odin flashing, it might still work with Oreo but having the wrong bootloader for your android version can have unwanted side effects.
Beanvee7 said:
The method for older versions was to flash an engineering bootloader to allow Odin flashing, it might still work with Oreo but having the wrong bootloader for your android version can have unwanted side effects.
Click to expand...
Click to collapse
Such as what unwanted side effects?
Battery only charges to 80%, app crashes, phone reboots, general instability. The engineering bootloader was for engineers to use for testing and whatnot, so it's not built for daily driver use.
Beanvee7 said:
Battery only charges to 80%, app crashes, phone reboots, general instability. The engineering bootloader was for engineers to use for testing and whatnot, so it's not built for daily driver use.
Click to expand...
Click to collapse
Ok, thank you.
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
kpwnApps said:
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
Click to expand...
Click to collapse
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
cooltt said:
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
Click to expand...
Click to collapse
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
snaksalot said:
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
Click to expand...
Click to collapse
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
cooltt said:
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
Click to expand...
Click to collapse
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
snaksalot said:
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
Click to expand...
Click to collapse
Hmmm so it may be that loophole is now closed, what you need to think about is if you deffo need root? Or is it just nice to have. I'm sure a dev will get round it soon.
snaksalot said:
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
Click to expand...
Click to collapse
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
kpwnApps said:
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
Click to expand...
Click to collapse
Okay I was completely unaware of TWRP being an option or the possibility of Magisk with a locked bootloader, now to clarify I'm running the latest unbranded US Region firmware for the US T-Mobile version of the Qualcomm Galaxy S7 "(TMB) G930UUEU9CSA3" that being said I have a few questions about how to specifically to proceed if you don't mind helping me?
First is the version of Odin available from the post provided above inst the modified version I've been required to use for all my previous flashing "Odin3_v3.13.1_3B_PatcheD" should I use this one or the version provided in the post above "Odin3_v3.13.1"?
My next question is that all the different versions and variants of TWRP available for my device the Galaxy S7 and the S7 Edge are either for Exynos Canada/International or Korea or the Chinese Qualcomm variant of each. Should I download and use the TWRP for the Chinese Qualcomm S7?
The sammobile link in the original post for "Android 8.0 Oreo Stock Rom" provides me with a list of the latest and up to date international versions of firmware for the Galaxy S7 Edge "SM-G935FD" I'm assuming I should just use the stock firmware image for my device "SM-G930U" instead?
The link for the no-verity-opt-encrypt-6.0 is dead but I don't think its needed because of something someone said in the original post about this method failing after latest security update "the one I'm on" https://forum.xda-developers.com/showpost.php?p=78115895&postcount=18 he said he solved it easily with information and another flash able zip from this post https://forum.xda-developers.com/showpost.php?p=77000849&postcount=47 and the zip from here https://forum.xda-developers.com/showpost.php?p=76564735&postcount=37
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
snaksalot said:
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
Click to expand...
Click to collapse
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
I'd be interested to know how this turned out if the device with V9 bootloader could be rooted with temp TWRP method.
Can i actually flash magisk on my 930u?
Is there any way to root my g930t ?
I'm on v9 bootloader, and i don't care about knox tripping.
Did developpers really failed to break the security of this little old device ? Or no one worked it ?
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Toolmighty said:
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Click to expand...
Click to collapse
Yes same hardware
cooltt said:
Yes same hardware
Click to expand...
Click to collapse
Can't get twrp to flash. Tried w rom as is, tried factory reset tried reinstall w/o auto reboot. All get same error
what about jruze root?
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
nm it uses flashfire
Toolmighty said:
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
Click to expand...
Click to collapse
Yes by using 1st and #1623 post number it can be rooted easily. I already have done that on both G930P and G930U.
I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.
Hi
I've been trying to downgrade my S8 from pie to oreo or nougat and no matter what I flash in odin the device stays at android pie.
My goal is to downgrade to oreo or nougat in order to get access to the OEM Unlock button in the developers menu which is nowhere to be found on the current pie system, from then I'd put TWRP and a custom rom on the phone... if I can get this far.
Thanks for any help
Lahpyrcopa said:
Hi
I've been trying to downgrade my S8 from pie to oreo or nougat and no matter what I flash in odin the device stays at android pie.
My goal is to downgrade to oreo or nougat in order to get access to the OEM Unlock button in the developers menu which is nowhere to be found on the current pie system, from then I'd put TWRP and a custom rom on the phone... if I can get this far.
Thanks for any help
Click to expand...
Click to collapse
What model is it? Post a screen shot of it in download mode.
You can still root on android 9 ( Pie )
Downgrading is generally not possible due to Bootloader version numbers.
Generally in the past people have used the date method to to get bootloader unlock option in developers option.
There are many guides out there to do with this.
ie:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
Note: Being on pie unlocking the bootloader in developer menu does not necessary mean that the kg / rmm has change. You can check in download mode.
Backup your device before hand.
spawnlives said:
What model is it? Post a screen shot of it in download mode.
You can still root on android 9 ( Pie )
Downgrading is generally not possible due to Bootloader version numbers.
Generally in the past people have used the date method to to get bootloader unlock option in developers option.
There are many guides out there to do with this.
ie:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
Note: Being on pie unlocking the bootloader in developer menu does not necessary mean that the kg / rmm has change. You can check in download mode.
Backup your device before hand.
Click to expand...
Click to collapse
As far as a picture goes, here's one of the download mode.
It's a SM-G950W, Canadian model.
Download Mode https://i.postimg.cc/MGrR81dC/IMG-20210505-081735.jpg
Lahpyrcopa said:
As far as a picture goes, here's one of the download mode.
It's a SM-G950W, Canadian model.
Download Mode https://i.postimg.cc/MGrR81dC/IMG-20210505-081735.jpg
Click to expand...
Click to collapse
I don't own a snapdragon version model and haven't kept up with threads involved with them.
The snapdragon (US) variants U/ U1/ W you cannot unlock you bootloader. So any conventional means of rooting/custom roms can't be done.
If there is any possible way to root your phone check out threads by extreme syndicate, jrkruse usually found in Samsung Galaxy S8 roms,kernels,recoveries & other threads but i don't like your chances of rooting/custom roms your phone on Android 9 ( pie ).
spawnlives said:
I don't own a snapdragon version model and haven't kept up with threads involved with them.
The snapdragon (US) variants U/ U1/ W you cannot unlock you bootloader. So any conventional means of rooting/custom roms can't be done.
If there is any possible way to root your phone check out threads by extreme syndicate, jrkruse usually found in Samsung Galaxy S8 roms,kernels,recoveries & other threads but i don't like your chances of rooting/custom roms your phone on Android 9 ( pie ).
Click to expand...
Click to collapse
This is the general consensus I have been determining through my queries online that it's either not rootable or will take more skill than I have to do it, it's unfortunate too. The S8 with its original firmware on it is basically a dud to me because I detest samsung's software.
¯\_(ツ)_/¯ Oh well... Move on.