Related
S8 plus stuck in recovery with following message:
"Support SINGLE-SKU
Supported API: 3
dm-verity error
failed code : 0x02"
Is there a fix for this yet?
cheers
Matt
...? Elaborate?
What did you flash that lead to this?
dm-verity is what you usually get when you flash something incompatible, or when some insecure fw image is rejected.
Reflash the firmware using ODIN, and the latest FW package for your model / region. (in the AP box)
If you end up with DRK error afterwards, then you're boned. You need Samsung to help you out.
TL;DR: Careful when flashing stuff next time, always verify what you're flashing is for your device's model.
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Comarrid92 said:
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Click to expand...
Click to collapse
Took it back to Samsung and had to pay them £290 to fit a brand new board.
Out of warranty coz i rooted it.
only way out.
Gutted.
Matt
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
CoreyHUN said:
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
Click to expand...
Click to collapse
Wrong.
I did flash it, and it was rooted for about a week, but for some reason, i was bored, just potching around with my phone and decided to uncheck 'allow OEM' unlock, but forgot to re-check it before i restarted the phone...too late though...as Samsungs awesome security basically said...NO WAY...he's tinkering about with root triggered the efuse on the board and the ONLY way to fix that was a brand new board.
I'm not a newbie (hence my 371 thanks meter) when it comes to rooting phones....i've been on here since 2011 and rooted stacks of phones....HTC HD2, HTC Sensation, Desire HD, LG G2, LG G3, LG G4, HTC One-X, HTC One-x Plus, HTC Desire eye and a LOT more...Just made a silly mistake a week AFTER I rooted the phone.
I gotta be hnonest, I thought i'd miss root, but can hand on heart say....i'm not missing it one single bit.
My lovely Samsung still has 20 months warranty and i'm keeping it that way by not rooting.
LOVE my S8 Plus and to be honest, with Knox etc....I'd advise everyone not to root this EXPENSIVE beast of a phone!:good:
Matt
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
CoreyHUN said:
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
Click to expand...
Click to collapse
WRONG!
Hardware problems -> YES
Problems due to wrong use of your phone (i.e. root and phone won't do anything anymore): NO
And I do agree with Samsung: if you temper with the FW, and your phone doesn't do anything anymore -> IT'S YOUR OWN F...... FAULT ! ! !
Here's the nice big fat bill I got for repairing it.
Eeeuuurrreekkaaaaaa!
So after being presented with this error due to my own stupidity (trying to diagnose why MTP wasn't working on windows 10 and disabling Developer Options and not re-enabling OEM Unlock), I managed to get around it quite simply although at the cost of my data... BUT at least its not bricked.
The solution is simple;
1. Use SamFirm and download the latest firmware
2. Using Odin Load all the firmware options (BL, AP, CP and CSC) and in the options tab select all the checkboxes except "Flash Lock" and "T-Flash".
3. Press start and hold your breath.
Upon completion the phone may not reboot automatically so you will have to manually reboot using the Bixby, Volume Down and Power Buttons. Once rebooted you'll see it erasing the remaining userdata and finalising the re-partitioning process but a few minutes later you'll see the samsung logo and the welcome screen.
I hope this helps someone. Good Luck Peeps
I have the same problem guys but my odin isn't working the ID thing specifically the computer isn't recognising the phone.
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
LodeUnknown said:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
Click to expand...
Click to collapse
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
*Detection* said:
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
Click to expand...
Click to collapse
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
LodeUnknown said:
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
Click to expand...
Click to collapse
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
*Detection* said:
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
Click to expand...
Click to collapse
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
LodeUnknown said:
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
Click to expand...
Click to collapse
If your phone is a US model S7 (snapdragon) you cannot flash custom ROMs
My instructions are for ODIN (version 3.12.7 for Nougat)
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
LodeUnknown said:
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
Click to expand...
Click to collapse
You cannot flash a custom ROM to a snapdragon phone using any method, it has a locked bootloader
ODIN is for stock ROMs only (and TWRP recovery which you cannot use on snapdragon either)
You can use ODIN on any S7 for stock ROMs
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
LodeUnknown said:
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
Click to expand...
Click to collapse
Yes, only Exynos has an unlocked bootloader (See the snapdragon vs exynos custom ROM dev forums)
Yes you could still use a US carrier as long as the phone is SIM unlocked (carphone warehouse phones are all unlocked), I have no idea of the limitations / implications, but some people here already do that, and the G930W8 (Canada) is Exynos
No idea about warranty, but if you bought it from say the UK and had it shipped, you'd have to discuss with Samsung if they would accept it into a US service centre or if you'd have to ship it back to the UK, no idea about that, no doubt there are places in the US that you could buy a Exynos from
Hit Samsung up on twitter and ask them
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
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 XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Frostyb said:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Click to expand...
Click to collapse
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
BloodyFruitDestroyer said:
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
Click to expand...
Click to collapse
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Frostyb said:
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Click to expand...
Click to collapse
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc
whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.
BloodyFruitDestroyer said:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
Click to expand...
Click to collapse
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Frostyb said:
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Click to expand...
Click to collapse
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
BloodyFruitDestroyer said:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
Click to expand...
Click to collapse
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Frostyb said:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Click to expand...
Click to collapse
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
BloodyFruitDestroyer said:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
Click to expand...
Click to collapse
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Frostyb said:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Click to expand...
Click to collapse
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
BloodyFruitDestroyer said:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
Click to expand...
Click to collapse
So the first image is of the current firmware that successfully flashed to my device via Odin.
The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.
What were your exact model and region again? Probably won't matter, please wait a minute
BloodyFruitDestroyer said:
What were your exact model and region again?
Click to expand...
Click to collapse
BloodyFruitDestroyer said:
What were your exact model and region again? Probably won't matter, please wait a minute
Click to expand...
Click to collapse
SM-G996B
Region is Ireland (CSC is MET)
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Hi there, I can help you out! I have some experience with Samsung.
So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.
It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Edit: It seems like someone more experienced appeared while I was writing this! Sweet!
BloodyFruitDestroyer said:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.
BloodyFruitDestroyer said:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Click to expand...
Click to collapse
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Frostyb said:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Click to expand...
Click to collapse
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.