Related
If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"
rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.
Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man
samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.
Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?
There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it
So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?
As of now it makes no difference.
Stupid question, but how do you turn off automatic OTA on lollipop?
guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well
TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha
ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]
I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.
I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.
MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]
My V20 currently is the Us996 version with 10h. 10H seems to be unrootable at the moment,but before I flashed 10H (By mistake) I made 3 twrp backups on my external SD card. Is there any way to possibly restore my phone using the backups I have saved on my SD card even though I don't have root or TWRP installed?
You need TWRP to restore a backup. You may be able to downgrade to an earlier version if there is a kdz available. OK, I found one.
Here is a link to the 10f firmware (kdz):
https://lg-firmwares.com/download-file/?fileId=5252
You might want to search and see if anyone has tried downgrading to this first. If it's possible, then you can add TWRP and root.
As an a side, I'm on h918 10j. 10k is not rootable and 10p is anti rollback. The upgrades are minimal and no one can point to any significant advantage. I have a custom ROM with lots of nice tweaks and I won't be installing any more upgrades. In fact, I expect there will be fewer and fewer upgrades coming as the phone gets older. No problem. Too many people want to jump on the next upgrade as if if will make the phone suddenly work differently. It won't.
There will be new customizations coming that will only work on a rooted phone (like second screen). Those that upgrade and are stuck with stock may not be able to take advantage.
So I hope you can use this to downgrade to 10f. Just research it first.
Cheers.
androiddiego said:
You need TWRP to restore a backup. You may be able to downgrade to an earlier version if there is a kdz available. OK, I found one.
Here is a link to the 10f firmware (kdz):
https://lg-firmwares.com/download-file/?fileId=5252
You might want to search and see if anyone has tried downgrading to this first. If it's possible, then you can add TWRP and root.
As an a side, I'm on h918 10j. 10k is not rootable and 10p is anti rollback. The upgrades are minimal and no one can point to any significant advantage. I have a custom ROM with lots of nice tweaks and I won't be installing any more upgrades. In fact, I expect there will be fewer and fewer upgrades coming as the phone gets older. No problem. Too many people want to jump on the next upgrade as if if will make the phone suddenly work differently. It won't.
There will be new customizations coming that will only work on a rooted phone (like second screen). Those that upgrade and are stuck with stock may not be able to take advantage.
So I hope you can use this to downgrade to 10f. Just research it first.
Cheers.
Click to expand...
Click to collapse
Sadly 10H has anti rollback on it as well. I guess I am stuck with what I've got.
Slashbeast24 said:
Sadly 10H has anti rollback on it as well. I guess I am stuck with what I've got.
Click to expand...
Click to collapse
It's still a great phone even stock. You never know if a dev who waited until the price of the phone came down doesn't jump on board and find a fix.
Enjoy the phone as it is. And there lots of tweaks you can do with stock (second screen tweaks are already here).
By the way, the camera in manual mode, is awesome. Play around with different settings and you will get far better pics than auto mode.
Select AE-L and then adjust the S exposure. Then adjust the iso (daylight = 50, night time is 800 or above). Play with white balance and you can make pics that are very different
That's not to even mention wide angle. I've taken some of the best pics ever with this phone and that doesn't even require root.
Cheers..
Slashbeast24 said:
Sadly 10H has anti rollback on it as well. I guess I am stuck with what I've got.
Click to expand...
Click to collapse
wtf are you talking about?? 10h does not have anti rollback
dimm0k said:
wtf are you talking about?? 10h does not have anti rollback
Click to expand...
Click to collapse
Yours says US99610h_00 mine says US99610H, and when I used LGUP I can't downgrade. The program crashes when I try to flash any KDZ that isn't the one on my phone, but if I try to flash the 10H Kdz it checks for anti roll back and doesn't crash.
Slashbeast24 said:
Yours says US99610h_00 mine says US99610H, and when I used LGUP I can't downgrade. The program crashes when I try to flash any KDZ that isn't the one on my phone, but if I try to flash the 10H Kdz it checks for anti roll back and doesn't crash.
Click to expand...
Click to collapse
apologies for the "wtf" comment... was under the influence at the time lol
anyway, how did you update toe 10H?
also, if you don't already know, entering this string in the Dialer app will give you the screen I have above to see the ARB status... *#*#244773825625#*#*
just curious about ARB in general... yours is the US996 unlocked version or the US Cellular US996 version?
dimm0k said:
apologies for the "wtf" comment... was under the influence at the time lol
anyway, how did you update toe 10H?
also, if you don't already know, entering this string in the Dialer app will give you the screen I have above to see the ARB status... *#*#244773825625#*#*
just curious about ARB in general... yours is the US996 unlocked version or the US Cellular US996 version?
Click to expand...
Click to collapse
Thanks for the info. I didn't know about that screen. I updated to 10H using the US996 firmware zip posted in one of the other threads, it wasn't rooted and I figured if I flashed SU behind it I wouldn't have any issues. WRONG. I went to put my phone in TWRP recovery and it erased everything that wasn't on my External SD CARD. I couldn't believe it. Oh and I have the unlocked 996 and not the US Cellular version.
Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
psychopac said:
Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
Click to expand...
Click to collapse
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
acejavelin said:
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
Click to expand...
Click to collapse
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
psychopac said:
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
Click to expand...
Click to collapse
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
acejavelin said:
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
Click to expand...
Click to collapse
That's a bummer. Anyways I hope that no one bricks their phone
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
jmindset said:
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
Click to expand...
Click to collapse
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
acejavelin said:
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
Click to expand...
Click to collapse
Well I just hate the fact that night mode was removed. Now when I use an app for blue light filter, it only works while using the phone. Not on the lockscreen not the pulldown notifications bar. An annoyance more than an actual issue but still...
riyan65 said:
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
Click to expand...
Click to collapse
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
acejavelin said:
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
Click to expand...
Click to collapse
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
riyan65 said:
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
Click to expand...
Click to collapse
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
acejavelin said:
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
Click to expand...
Click to collapse
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
jmindset said:
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
Click to expand...
Click to collapse
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
acejavelin said:
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
Click to expand...
Click to collapse
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
jmindset said:
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
Click to expand...
Click to collapse
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
acejavelin said:
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
Click to expand...
Click to collapse
Lol and for that exact reason, I will not purchase another Motorola device. So glad that the mid-range phone market is getting wider each year. I will purchase a Nokia 7.1 next. At least that phone will get guaranteed updates for the next few years.
Just adding to this thread, even if it were possible to downgrade the system to nougat, you would have problems with losing your IMEI. The fix would require root access, and again that's not possible on a locked bootloader.