Related
Anyone else received a software update this morning? I just did, it was like 41mb. Don't see any difference yet but I'm still looking.
It was a security update. Maybe to close possible holes that could have been used for rooting.
veritasaequita said:
Anyone else received a software update this morning? I just did, it was like 41mb. Don't see any difference yet but I'm still looking.
Click to expand...
Click to collapse
What is the date of your security patch level in about phone after updating?
Ss
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
cr1130 said:
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
Click to expand...
Click to collapse
LOL the bootloader is locked. So either an exploit is needed in the system ( not impossible one was found on the Verizon s6 and patched a week later) but samsung has gotten really good at not releasing with an exploit or they give us a way to unlock the bootloader
cr1130 said:
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
Click to expand...
Click to collapse
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
i got "b6 " in the last 2 digits on build number
veritasaequita said:
Ss
Click to expand...
Click to collapse
looks like a baseband update ,
muniz_ri said:
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
Click to expand...
Click to collapse
So should I update my S7 to the new security update. Does this new update improve performance battery life etc.? The security update is 41.27mb. That is the update that I am getting. So a Root for the T-Mobile S7 is probably never going to happen? If I update to new security update will it prevent bootloader to unlock even more?
passion4tech said:
So should I update my S7 to the new security update. Does this new update improve performance battery life etc.? The security update is 41.27mb. That is the update that I am getting. So a Root for the T-Mobile S7 is probably never going to happen? If I update to new security update will it prevent bootloader to unlock even more?
Click to expand...
Click to collapse
We have seen leaked engineering bootloaders and kernels on other samsung locked bootloader devices recently which have allowed root (albeit not very practical root implementations). That is likely the best chance of getting root on this device, i.e. unlikely.
Hope I am wrong but I would take the security update without hesitation and settle in to the fact that root is probably not going to happen on this device.
muniz_ri said:
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
Click to expand...
Click to collapse
muniz_ri said:
We have seen leaked engineering bootloaders and kernels on other samsung locked bootloader devices recently which have allowed root (albeit not very practical root implementations). That is likely the best chance of getting root on this device, i.e. unlikely.
Hope I am wrong but I would take the security update without hesitation and settle in to the fact that root is probably not going to happen on this device.
Click to expand...
Click to collapse
OK I won't hesitate to take the new security update. But can you tell me if the new update 41.27mb improves performance and battery life? Can someone tell me their experience with this new update?
Yes it does improve the battery life. The initial update will some what drain the battery fast. Dont worry just allow it to completely dies then fully charge it. After 2 or 3 charge cycle you wont see a huge dip in battery drain like at the time of initial updates. I was furious at 1st as my phone dies in like an 3 to 4 hours usage as before i can be go a full day of 8-9 hours of heavy usage. Wity a full charge at 5am and dont have to fully charge it until 7pm is very impressive. Thats with web browsing, facebook, youtube and Pandora. fb Messaging
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Just got mine
You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.
nothing in eu yet
iks8 said:
nothing in eu yet
Click to expand...
Click to collapse
As far we know so far, this is for the XT1575 only... just the December 2016 security update to 6.0, very minor update. Started rolling our about a week ago... a big push seemed to happen on the 14th and 15th with many users receiving it those days.
autosurgeon said:
You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.
Click to expand...
Click to collapse
Edited/fixed
it has been rolled out worldwide... its been like (3weeks ) since i updated it...
Got mine yesterday
Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.
Firefishe said:
Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.
Click to expand...
Click to collapse
No, WiFi is required to get a Moto OTA.
Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.
strafer69 said:
Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.
Click to expand...
Click to collapse
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Sent from my SM-G935P using Tapatalk
We should all agree that Pure program by GG is a fail. GG initiated it with HTC, Moto... with Pure Edition and commit that they would be upgraded just after Nexus lines
You guys are missing the point.
Nougat 7.1 came out in December. In order to have a smooth update to 7.1, you need the pre requisites which is the security update
piscesjoey said:
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Click to expand...
Click to collapse
I understand your sentiment regarding the near vanilla, and I'm surprised Google didn't commit Lenovo to keeping the pure/style updated. Lenovo has given over to "standard business practices", which unfortunately means that the manufactures focus on updating their newest flagships first (Moto Z line, G5, GS7, HTC 10). This is nothing new and has been this way for a while. Once again, the rule applies: if you want the latest and greatest Android updates upon release buy a Google phone (Pixel). Aside from that I expect very little. If I want the latest and greatest, I turn to XDA and other sources for custom ROMs (which is nothing new for me).
_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting promoted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?
---------- Post added at 11:56 PM ---------- Previous post was at 11:56 PM ----------
_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting prompted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?
It'll be another 2-3 months to even get 7.0 and than no more updates. That's why **** motorola/lenovo nobody buy the G6 or G6 plus so they finally go out of business!
Sent from my XT1575 using XDA-Developers Legacy app
you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
_litz said:
you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.
Click to expand...
Click to collapse
why is it so difficult to apply a few security patches. at this point i'll wait for nougut. I've been eyeing a few of the nougut roms, but I see comments about stability and features not working.
do we need to relock the bootloader too? or just no root, stock partitions, and stock recovery?
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
I have TA-1043 and August update.
It sucks and Nokia seems to be silent on this. Everyone (or most) who have software build 2_22A_SP01 seem to be stuck on June. If you have a different build you are getting updates.
Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.
Ozhora said:
Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.
Click to expand...
Click to collapse
Bull IT Will come over WIFI. No problem.
No updates found over WiFi or cellular network
Hello,
go to
nokia.com/en_int/phones/security-updates
select nokia 6.1
and you 'll see that only 3 firmwares are on july update.
00WW_2_13B_SP03
00WW_2_22A_SP02
00WW_2_22E_SP01
I have 2_22A_SP01 and even with sim card out, in other words, Wifi only, no update is available and I (and many others) am stuck on June.
The option here is to unlock the bootloader and using OST LA, flash the system image again, there is a thread here to do this. For me everything worked fine, and I'm now on August SP
For people stuck with June Patch and a A or B builds variant, you can follow this guide (no bootloader unlock needed) :
community(dot)phones(dot)nokia(dot)com/support/discussions/topics/7000032724
It works and I'm now with the August Patch and a 2-22E build (I was 2-22A with June Patch before).
Follow exactly the different steps (skip Google account is very important)
eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...pl2-222e-0-t3831764/post77389130#post77389130
It kinda worries me what HMD is doing. The shell is top notch and I actually applaud them for valuing scratch resistance over shatter resistance because one happens in an accident where the other is a constant bugger. But if they are going to do Android One with such problems Google better punish them for not staying up to standard.
Just got July SP on my 1043, however cannot install it...
Finally, phone updated on its own (without special measures), first to July, then to August security patch. Software is now 00WW_2_22E_SP02.
Could unlocked bootloader be the reason I cannot install OTAs ? Because I'm full stock since i flashed back 8.1 firmware using Ntools.
Try clearing data for Google Services Framework. It should work after that. I tried this yesterday but didn't get any updates. I just switch the phone off after that. This morning I powered it on, and 2 updates, July and August came in quickly. Just has to re-connect my google account and all is working well for now.
Hope this helps others.
My note 8 had OneUI pushed to it about a week ago even though I kept refusing not wanting to while I was sleeping. It says my bootloader is v5. This is actually what it says (N950USQU5DSD3). My problem is that when I search for the firmware I'm wanting to downgrade to (the last oreo update possible for this particular phone) on Sammobile I can't find the one for At&t. I see ones for Verizon, sprint, etc. But nothing for at&t, which one am I supposed to use and where can I get it? This is going to be my very first downgrade/upgrade, really my first time doing anything like it on android. And I CAN do this right? There's nothing I should be aware of that makes what I'm trying to do not able to be done is there? The biggest reason I'm asking is because I have very limited tools to work with, I have a little 12" Acer aspire one (no disk drive) running windows 7 home basic, mobile hotspot from my wife's phone(the last software I tried to download and use came from xda out of a thread I found titled, "Stock Oreo N950USQS5CRF6 Odin*files*for AT&T*NOTE*8" it failed halfway through 2 nights ago during the beginning of storm, and the whole time it would only download around 32kbs so it literally to FOREVER! Only for it to fail halfway through. Was I wasting my time or was this in fact the firmware I'm looking for? If not, as I asked before, where could I find it?? Thanks a bunch for any help.
https://forum.xda-developers.com/at...n950u-stock-n950usqs5crf6-odin-files-t3821222
^^^^^^^Is this all I need? Do I need to follow this tutorial or a different one?? What version of odin, do I need anything else
Sorry for so much all at once, I really hate this update and want Oreo back.
https://forum.xda-developers.com/ga...m-n950u-u1-t3685884/post74087340#post74087340
Follow the steps from the above-linked post, and follow them very carefully. I did, and I was able to successfully downgrade from Pie to Oreo on my AT&T NOTE8.
I actually flashed the unlocked firmware, which has zero AT&T bloat. It works just fine for my needs. I don't think AT&T WiFi calling works on this unlocked firmware (I haven't tried - I don't use it).
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
pyrolad said:
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
Click to expand...
Click to collapse
A little off topic, but has anyone seen an AT&T security update for May yet? I'm still on April security, and it's basically mid June?
Tha k you I'll check it out when I get off work, I didn't know you could flash the unlocked firmware on a carrier locked phone
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
marhodges said:
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
Click to expand...
Click to collapse
Yes you CAN downgrade back to Oreo. BUT you MUST go to a bootloader 5 firmware.
---------- Post added at 07:55 AM ---------- Previous post was at 07:54 AM ----------
Superloud024 said:
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
Click to expand...
Click to collapse
Yes you can go to that firmware. You will want to back up and allow it to factory reset. Be sure to use the modified version of Odin. Go HERE, post #2
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.