Related
This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...
those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc
enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards
iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.
Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).
I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.
I found a simple fix, get Titanium Backup and freeze that crap app, done.
yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...
saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it
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?
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
connorhiller said:
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
Click to expand...
Click to collapse
I'm in the same boat. No one knows yet. There are not even factory images available nor full OTA images on the google site here.
https://developers.google.com/android/images
Until such time as they appear don't sweat it. After they do then you can re-ask your question but you'll probably get it before you can hit send. Someone said they got an OTA on Verizon from 7.1.2 to 8.0 but I'm a little leery of that claim since no one else I've seen has received it.
I believe it was destined for the Aug 21 deadline but some major problems have arisen and I believe it was pulled for further testing. Bluetooth is one of them, random rebooting, stuff like was on some dp4 devices. I also saw some volume control issues too. Yes, I know others haven't had issues and someone will post a link to the factory images on the android site but that doesn't help any of us with locked bootloaders. Besides the fact that I like the background install and being able to use the phone while it's updating. Then a simple reboot and you're done. It'll happen soon but no one knows when yet.
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
sitnaing said:
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
Click to expand...
Click to collapse
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
bobby janow said:
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
Click to expand...
Click to collapse
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
sitnaing said:
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
Click to expand...
Click to collapse
Well that's a bit of good news. One thing is that on G+ no one has posted the inevitable screenshot of the OTA notification (which are at best annoying but they do it anyway), so it must be rolling out very slowly. The other thing is that once an OTA is released the system images are usually available with the OTA images shortly thereafter. I don't see either of those at this point.
I mean I'm gonna wait and I'm sure it'll be here, but the question is when. I'm on VZW so they might be tweaking some things before the let Google release it. Not sure how that works.
Did yours install in the background and then a reboot to 8.0? How long was the bootup process if you watched it?
For carrier, like you said roll out will take some time. For me, time taken is similar to update and reboot as normal security patch monthly update where it should take longer as this is the whole different version. May be backbone still same but with just UI change and some tweaks.
Just got it 30min ago, The android on it now is 6.0 emui 4.1 and it wants me too update too 7.0 5.0. Is it ok too update too it now before unlocking the bootloader and root?
Why i ask is i think it would be a good idea too test the phone for a few days first too make sure it has no issues.
Also from reviews and from what i herd about the phone from others. They say the back plate is metal? From what i can tell its plastic on mine is that normal? Or did they just meant its a metal like finish?
gordesky1 said:
Just got it 30min ago, The android on it now is 6.0 emui 4.1 and it wants me too update too 7.0 5.0. Is it ok too update too it now before unlocking the bootloader and root?
Why i ask is i think it would be a good idea too test the phone for a few days first too make sure it has no issues.
Also from reviews and from what i herd about the phone from others. They say the back plate is metal? From what i can tell its plastic on mine is that normal? Or did they just meant its a metal like finish?
Click to expand...
Click to collapse
Welcome on board!
I suggest you to update the system and testing it a while before unlocking the bootloader, just to be sure it's OK.
The back of my phone it's like gray metal, I can't tell if it's real or plastic. Feels like metal though.
You could check some videos on the web to see if your phone it's just like the other.
Goodnight
Inviato dal mio BLN-L21 utilizzando Tapatalk
Landrea said:
Welcome on board!
I suggest you to update the system and testing it a while before unlocking the bootloader, just to be sure it's OK.
The back of my phone it's like gray metal, I can't tell if it's real or plastic. Feels like metal though.
You could check some videos on the web to see if your phone it's just like the other.
Goodnight
Inviato dal mio BLN-L21 utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks
Just did the update a hour ago
And yea its hard too tell sense some metals can feel like plastic lol But im pretty sure its metal now reviews says the top and bottom edges are plastic but the middle part is metal and i still have the plastic cover on the back so its a bit hard too tell lol.
So far its working great i probably will run it for couple days before i do anything too it bootloader etc.
Big performance boost from my old htc droid the droid is still a decent device but the battery is on its way out will ony hold about a 50% charge:/ and max it runs is 6.0 and the biggest issue is no mico sd slot...
welcome
So far still running great really loving the performance!
I have question tho. Under security it says patch level march 2017. Is that normal? or should i be on a newest date?
Its on 7.0 5.0 build number b360 and says there's isn't a new update.
Model is bln-l24 us.
gordesky1 said:
So far still running great really loving the performance!
I have question tho. Under security it says patch level march 2017. Is that normal? or should i be on a newest date?
Its on 7.0 5.0 build number b360 and says there's isn't a new update.
Model is bln-l24 us.
Click to expand...
Click to collapse
The US version doesn’t get timely security patches from Huawei.
gordesky1 said:
So far still running great really loving the performance!
I have question tho. Under security it says patch level march 2017. Is that normal? or should i be on a newest date?
Its on 7.0 5.0 build number b360 and says there's isn't a new update.
Model is bln-l24 us.
Click to expand...
Click to collapse
I have the US model and it just got an update to EMUI 5.0.1 tonight. The update probably has bug fixes, but I know it comes with the October security update for sure.
SenyorMauricio said:
I have the US model and it just got an update to EMUI 5.0.1 tonight. The update probably has bug fixes, but I know it comes with the October security update for sure.
Click to expand...
Click to collapse
Hmm so far nothing for me. Maybe it takes time too roll out too others.
gordesky1 said:
Hmm so far nothing for me. Maybe it takes time too roll out too others.
Click to expand...
Click to collapse
It rolls out in batches if new OTA comes. However, for regualr or old update it comes very quickly once you insert the sim. You may wait for couple of days though before trying anything new
So looks like everything is fine on this phone hardware wise So im looking into unlocking the boot loader and doing root but want too keep the stock feeling.
When i go too this thread https://forum.xda-developers.com/honor-6x/how-to/root-huawei-honor-6x-install-twrp-t3671822 and when going too twrp i see they saying fastboot flash recovery twrp-3.1.1-0-berlin.img..
Is there a img for the usa model? Or will the berlin.img work too?
shashank1320 said:
It rolls out in batches if new OTA comes. However, for regualr or old update it comes very quickly once you insert the sim. You may wait for couple of days though before trying anything new
Click to expand...
Click to collapse
Should i wait doing the bootloader and root?
When looking for root all i see its for other versions like berlin. unless that works for the usa model too?
Hmm just noticed the thread i posted is yours lol
Does it work with the usa model? what got me hang up is the berlin step.
i just unlocked the bootloader Tried doing it with the UC browser on the device and it wouldn't load the sites in the guide... But it worked doing on this page and doing it from my pc. https://www.gadgetcreed.com/100-working-huawei-honor-6x-unlock-bootloader-guide/
Gave me my unlock code and i followed the guide and it worked OEM unlock was showing for me too which says some users wont have it on 5.0.
Now for root question. Will i still get updates if i root? I probably wont mess with custom roms for awhile cause i like the stock look lol
gordesky1 said:
i just unlocked the bootloader Tried doing it with the UC browser on the device and it wouldn't load the sites in the guide... But it worked doing on this page and doing it from my pc. https://www.gadgetcreed.com/100-working-huawei-honor-6x-unlock-bootloader-guide/
Gave me my unlock code and i followed the guide and it worked OEM unlock was showing for me too which says some users wont have it on 5.0.
Now for root question. Will i still get updates if i root? I probably wont mess with custom roms for awhile cause i like the stock look lol
Click to expand...
Click to collapse
You will still receive OTA updates; however, I don't know if they'll install on your device properly after rooting. If you get an update, I'd recommend unrooting, reflashing the stock bootloader, and then relocking the bootloader. The Android 8.0 update is likely to come out for the Honor 6x in December or January, so I wouldn't have rooted now if I were you. I think 8.0 might be the last major update for the Honor 6x for a while, so I would recommend rooting then, honestly. Even the guys who make the Stock ROMs (Open Kirin) stopped development for Nougat in favor of Oreo ROMs, so many of the Nougat stock Android ROMs are buggy.
SenyorMauricio said:
You will still receive OTA updates; however, I don't know if they'll install on your device properly after rooting. If you get an update, I'd recommend unrooting, reflashing the stock bootloader, and then relocking the bootloader. The Android 8.0 update is likely to come out for the Honor 6x in December or January, so I wouldn't have rooted now if I were you. I think 8.0 might be the last major update for the Honor 6x for a while, so I would recommend rooting then, honestly. Even the guys who make the Stock ROMs (Open Kirin) stopped development for Nougat in favor of Oreo ROMs, so many of the Nougat stock Android ROMs are buggy.
Click to expand...
Click to collapse
Oh i ony did the unlocking boot loader so best case is too just wait not rooting it right now till when 8.0 comes out? Having the boot loader unlocked wont effect updates etc tho right?
But yea i was ony going too root for the root apps and the trwp recovery but stay on the stock rom that comes with it.
gordesky1 said:
Oh i ony did the unlocking boot loader so best case is too just wait not rooting it right now till when 8.0 comes out? Having the boot loader unlocked wont effect updates etc tho right?
But yea i was ony going too root for the root apps and the trwp recovery but stay on the stock rom that comes with it.
Click to expand...
Click to collapse
You will get OTA but wont be able to install as boot.img modified. Best way in that case would be to flash the stock boot.img, stoct recovery.img and proceed with ota download and installation.
Or other way, be as it is, download full firmware and update via Dload. These manual update is way faster before OTA even rolls out.
gordesky1 said:
Just got it 30min ago, The android on it now is 6.0 emui 4.1 and it wants me too update too 7.0 5.0. Is it ok too update too it now before unlocking the bootloader and root?
Why i ask is i think it would be a good idea too test the phone for a few days first too make sure it has no issues.
Also from reviews and from what i herd about the phone from others. They say the back plate is metal? From what i can tell its plastic on mine is that normal? Or did they just meant its a metal like finish?
Click to expand...
Click to collapse
I have also recently purchased honor 6x , and mine also is on 6.0 emui 4.1.3, by checking system update it says no updates, have you found any solution ( also i dont want to unlock bootloder and root my device , so please suggest other than this)
shashank1320 said:
You will get OTA but wont be able to install as boot.img modified. Best way in that case would be to flash the stock boot.img, stoct recovery.img and proceed with ota download and installation.
Or other way, be as it is, download full firmware and update via Dload. These manual update is way faster before OTA even rolls out.
Click to expand...
Click to collapse
You mean if i root? Or the unlock bootloader for the ota updates part?
And whats Dload mean? Did some research and found out what dload means its doing it manual from the dload folder on a sd card
Sorry for these stupid questions hehe i been out of the loop with this phone stuff for awhile lol
NinadMestry said:
I have also recently purchased honor 6x , and mine also is on 6.0 emui 4.1.3, by checking system update it says no updates, have you found any solution ( also i dont want to unlock bootloder and root my device , so please suggest other than this)
Click to expand...
Click to collapse
Mine had the update from the start when i click check for updates for 7.0 5.0.
gordesky1 said:
Mine had the update from the start when i click check for updates for 7.0 5.0.
Click to expand...
Click to collapse
my honor 6x is indian variant bln-l22
whats yours
NinadMestry said:
my honor 6x is indian variant bln-l22
whats yours
Click to expand...
Click to collapse
bln l24 usa model
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.