LG is most likely developing the Android 6.0 Marshmallow operating system and may release it for its G3 and G4 flagships via an over-the-air (OTA) update, in the coming weeks. Although the update schedule is yet to be revealed.
The company's Korean support site has listed the Android 6.0 Marshmallow update for some variants of the LG G3 and LG G4 flagships, which include the LG G3 F400S, F400K and F400L as well as the LG G4 F500S, F500K and F500L. All these variants are currently running on Android Lollipop operating system.
Click to expand...
Click to collapse
View full post here: http://www.ibtimes.co.uk/android-6-0-marshmallow-update-lg-g3-g4-likely-be-released-soon-1522322
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
I'm guessing this will mean a new root method will be required?
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Also a 6 month+ wait for Telstra to do their "testing". Unless we can simply flash it the way we do now with locked bootloaders and injecting root.
I'm excited for the camera app from the V10 being ported over!!
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
I'm hoping that it'll only be a couple weeks before MM is released to the G4, but I'd be happy if it's before the new year. It would make sense to have it out before Xmas so people might buy the G4 as a gift.
I guess not too many of the general public are going to care/know about the latest release of android, whereas people do want something that can handle iOS 9 or whatever version they're on now.
Here's hoping for a fairly quick release and a screen saturation control!
Amazed at how much the price of the G4 has dropped. I bought mine for £360 three weeks ago and it's dropped another £42 since! Probably £299 by Xmas. Why bother waiting for a One Plus/Nexus etc.?
bustervic said:
I'm excited for the camera app from the V10 being ported over!!
Click to expand...
Click to collapse
+1
It is inevitable i believe because both phones use identical sensors...
frnkly said:
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
Click to expand...
Click to collapse
+1
We should get much better battery life, especially in stand-by. But i'm hoping for beter power managment
while in use and a better optimised cpu governor... Lag shoulden't be a problem in MM...
daglesj said:
Here's hoping for a fairly quick release and a screen saturation control!
Click to expand...
Click to collapse
+1
That would be great...
I'm wondering how long it will take Big Red to push this out.
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
Well said, it's a big if... But nevertheless, someone will find out the way to root, someone always does
About the MM release, i believe it will be out around the new year, probbably in early january :fingers-crossed:
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
djkinetic said:
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
Click to expand...
Click to collapse
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
karendar said:
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
Click to expand...
Click to collapse
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
biff6789 said:
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
Click to expand...
Click to collapse
Yea with the current changes that Google made with M at the kernel level bootloader locked devices have very little hope of being rooted, the reason why we can still root on nexus devices is because our bootloaders are unlockable you take that away and we would be in the same boat, this release of android has pretty much signaled the end of me buying any carrier phones that i know will be locked down. its simply too much hassle for most devs to bother with finding new exploits in the coming android versions.
Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
Man. Sweet.
Sent from my LG-H811 using Tapatalk
Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
It does? It looks to me like it says both the g3 and g4 are in Manufacturer Development not testing. The nexus 6 is the only device I see that's in testing. I would be shocked if it comes out before December and I would not be shocked if we don't see it until next year.
biff6789 said:
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. .
Click to expand...
Click to collapse
Please, most of the world has unlocked bootloaders.
Mad_Duke said:
Please, most of the world has unlocked bootloaders.
Click to expand...
Click to collapse
Just Europe and T-Mobile USA (AFAIK) at the moment.
The percentage of G4's with unlockable bootloaders is pretty small.
Related
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for notifying, now about the locked bootloader, got any where on that? is it the same as the AT&T s4? confirming if recoveries, kernels can be flashed. Also do you have a recovery.img available? (so I can build cwm and twrp)
emwno said:
Thanks for notifying, now about the locked bootloader, got any where on that? is it the same as the AT&T s4? confirming if recoveries, kernels can be flashed. Also do you have a recovery.img available? (so I can build cwm and twrp)
Click to expand...
Click to collapse
I need to find a rom download somewhere to extract recovery.img as I cant dump it without root to my knowledge.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
DanMc85 said:
I need to find a rom download somewhere to extract recovery.img as I cant dump it without root to my knowledge.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.
emwno said:
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.
Click to expand...
Click to collapse
I am compiling the kernel from source tonight or tomorrow, after that I will extract all parts for a recovery for you.
dirtydroidx said:
I am compiling the kernel from source tonight or tomorrow, after that I will extract all parts for a recovery for you.
Click to expand...
Click to collapse
Any luck with this?
- Dan
DanMc85 said:
Any luck with this?
- Dan
Click to expand...
Click to collapse
Working on it right now. PM me when you get a chance.
Time to start fiddling
Sent from my GT-N5110 using xda premium
emwno said:
yeah you cant, its either root and use the dd method or a stock firmware, do let me knowif you find one.
Click to expand...
Click to collapse
dirtydroidx said:
Working on it right now. PM me when you get a chance.
Click to expand...
Click to collapse
Hey Guys,
Here is an extracted boot.img, recovery.img, and sboot.bin from the I467UCAMF1 firmware... they have since updated to I467UCAMF2 OTA via AT&T, but it might be worth still looking into making a root/recovery for the MF1 version or possibly seeing if it will also work on MF2 or if it is possible to downgrade via ODIN.
- Dan
Sweet jeebus.. AOSP here I come. Touchwiz can uhh.. Well you know...
Any update on this?
Very interested for this...
-Sent from my Kangabean Google Ed S4
MrKal_El said:
Very interested for this...
-Sent from my Kangabean Google Ed S4
Click to expand...
Click to collapse
I'm interested in this too
DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi DanMc85,
Have you already root your i467? I'm about to buy one today but would like to know if we will see some new ROMS from XDA, etc. Could you confirm to me that your i467 is LTE like Canadians one?
Thanks,
JmCourir.
RIP
Nobody made a custom recovery or ROM for this device. Rest in Pieces Note 8.0.
Bricked it, Reflashed JB, Bricked it, Reflashed JB, Updated to kitkat, Tried to reflash JB, failed.
:crying: RIP :crying:
I know this is an old thread, but I just can't let go of this tablet! I need a tablet that is not too big or too small so that I can take notes with it. A 10" tablet gets heavy in your hand after a while. Further, very few tablets come with a built-in stylus. If I have to carry an extra stylus, I would either forget or lose it. In fact, I read a 2017 report that Note 8.0 is considered one of the best tablets for note taking! Enough promotion for this aging (4-year-old) device. Now the reality...
Until anyone comes up with a bootloader exploit, the SGH-I467 (AT&T version)'s obituary is essentially written. Yes, you can root it with KingoRoot. Since it's one-click, it cannot get simpler. However, if you can't bypass the bootloader, you are stuck with 4.4.2.
However, the Canadian version (SGH-I467M) has an unlocked bootloader. If anyone would just port a kernel for this tablet, it would give this one many more years of life. Even with the GT-N5120 Lineage OS 14.1 ROM and Boeffla kernel, I can get LTE connection and Nougat out of the box. Light sensor and MIC are still broken, which is expected since this is N5120's kernel. N5120 has two MICs and proximity sensor while I467M has only one MIC and no proximity sensor. I assume N5120's kernel on an I467M would be looking for the wrong MIC and there is some correlations between the proximity and light sensors. Bluetooth is also broken. I don't have explanation for it. I can't explain either why Boeffla kernel would enable the LTE connection since the European radio bands are different than the North American ones. I'm happy it's fixed though! The native kernel from the 14.1 Lineage OS can never establish the radio link though it does see the SIM and IMEI. (The 13.0 LOS cannot detect the IMEI and SIM at all and Boeffla in this case cannot fix it either.)
I am not a developer, but if anyone is willing to port a kernel for SGH-I467M to work with LOS 14.1, I'd be happy to be your beta tester. Thank you
---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------
Darklordevo said:
Updated to kitkat, Tried to reflash JB, failed.
Click to expand...
Click to collapse
SGH-I467 (NOT I467M, the Canadian version) has a locked bootloader. Once it is upgraded to KitKat, you cannot go back to JB! When I used to hack SGH-I467, I downloaded the -AMF1 firmware (the only one in circulation), thinking if anything went wrong, I could always re-flash with this official firmware. Boy, I learned my lesson when I bricked it. Since mine already had Kitkat, this official JB firmware in circulation is useless. I almost sold it for parts until I came across someone on eBay offering the KitKat firmware!
---------- Post added 2nd March 2018 at 12:18 AM ---------- Previous post was 1st March 2018 at 11:56 PM ----------
DanMc85 said:
Samsung released the official kernel for the AT&T Galaxy Note 8.0
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-I467_ATT
Perhaps some mods are in this tablets future...
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's funny Samsung released the kernel source code for a tablet with a locked bootloader. What can you do with it? I think they are doing it for the sake of fulfilling their open source obligation.
On the other hand, if SGH-I467 and SGH-I467M share very similar kernel, I can imagine someone can port it for SGH-I467M. I am actively looking for a kernel for the Canadian version, I467M, to extend the life of my Note 8.0
I have both I467 and GT-N5110, and are both on the latest 4.4.2 introduced last year about this time.
I am not a dev, but since owning the two devices, i have modded my tablets to be nearly identical. The GT-N5110 has Boeffla kernel and the I467 is stock.
Both run circles around any developed ROM, as for 10 hours of use on battery and no issues, plus mods from S5, Tab 4 and wee mods never released in any developed firmwares to complete a full featured gallery, and allow color blind, interactive control and grey scale mode.
It took messing with 5 different roms and combining missing systrm files for adding hidden features in stock framework and touch wiz.
Only needed a wee mod to remove the few stage fright mp4 issues to button up left over security issues.
gooberdude said:
Both run circles around any developed ROM, as for 10 hours of use on battery and no issues, plus mods from S5, Tab 4 and wee mods never released in any developed firmwares to complete a full featured gallery, and allow color blind, interactive control and grey scale mode.
Click to expand...
Click to collapse
Could you share some instruction on how you did it? Have a 5110 and love it, but it's starting to slow down. Factory resetting, but would love to speed it up
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]
With 5.1.1, many other changes also coming to tablet. Like, Reactivation Lock, Download booster, etc. and Stagefright fix ofc.
Full changelog at source below.
The build no. is P905VVRUANK5 and P905VVRUBOH1.
-- SOURCE
Would you believe my first VZW Note Pro 12.2 is arriving today? Yes I am late to the party but it's on FedEx truck for delivery now. This is my first Android tablet. You JUST made my day! Wow what timing!
Edit : I hope this is true. Source page gives a not found 404 error
Edit Edit: the URL had an error. Here it is again:
http://www.theandroidsoul.com/andro...y-note-pro-12-2-tablet-rolling-out-now-84315/
I am simply beside myself on the timing of this upgrade.
Sent from my SM-N920V using Tapatalk
Did the upgrade this morning. Bit of a heart stop when it sat at the Verizon screen for about 5 minutes on the reboot, but then it finally brought up the updating apps screen.
Only problem I've found so far is that for some reason, it removed just about every one of my purchased apps. All the free ones were there, but had to go out to the store and re-download all those I had bought. Strange...
Verizon Messenging crashes for me, but if I uninstall the Verizon Messenging app update it will work. Other than that 5.1.1 working thus far.
Sent from my SM-N920V using Tapatalk
How in the world did the Verizon version come out before the wifi?!?! Verizon is NEVER first... They are usually dead last! As with my note 4....still on 5.0.2 several months after the release of 5.1
Sent from my SCH-I605 using XDA Free mobile app
Has anyone been able to root or keep root after updating?
Has anyone found where we can download the update from so I can flash it with Odin?
SugeLover said:
Has anyone been able to root or keep root after updating?
Click to expand...
Click to collapse
I too am awaiting confirmation on this before updating
I have the update.zip if it will help any devs with root or bootloader unlocking. It seems the update is a 2-parter, I have the the first update which according to the description "prepares your device for the 5.1.1 update." Please contact me if anyone can use it
Due to some new policies at work, Rooted devices weren't allowed to be connected to our E-mail, so I went ahead and took the plunge to 5.1.1 without worrying about rooting (gasp....did I just say that?). Anyhow, this thing feels like a new device. Much smoother, more responsive and it seems that the battery life is actually improved. IF Root does come along for the 5.1.1 update, I may root it and just use one of my other tablets for work, but I'm pleasantly surprised how well the NP runs at this point. Also...REALLY surprised that Verizon actually had the 5.1.1 update.
tdetroit said:
Due to some new policies at work, Rooted devices weren't allowed to be connected to our E-mail, so I went ahead and took the plunge to 5.1.1 without worrying about rooting (gasp....did I just say that?). Anyhow, this thing feels like a new device. Much smoother, more responsive and it seems that the battery life is actually improved. IF Root does come along for the 5.1.1 update, I may root it and just use one of my other tablets for work, but I'm pleasantly surprised how well the NP runs at this point. Also...REALLY surprised that Verizon actually had the 5.1.1 update.
Click to expand...
Click to collapse
Can you test the old root method and see if it works? TIA
It does not.
tdetroit said:
It does not.
Click to expand...
Click to collapse
Hi - I just got my NP today delivered and got the new OTA update. Can you provide any of the root methods that previously worked for you on the P905v? You stated that your job doesnt allow the rooted device but I am wondering if this one can be rooted still any way? I want to run linux deploy on here to run Fedora or Ubuntu but always end up down a rabbit trail with this setup that I can never get out of
Thanks for any help!
ckozler said:
Hi - I just got my NP today delivered and got the new OTA update. Can you provide any of the root methods that previously worked for you on the P905v? You stated that your job doesnt allow the rooted device but I am wondering if this one can be rooted still any way? I want to run linux deploy on here to run Fedora or Ubuntu but always end up down a rabbit trail with this setup that I can never get out of
Thanks for any help!
Click to expand...
Click to collapse
I don't think there's a root yet for the Verizon variant, and I've not actively searched for one at this point. It was needed while the Tablet was on 4.4.2, but 5.1.1 gives me enough control not to worry about it too much right now. Before I used Towelroot, which will NOT work on the new version.
tdetroit said:
It does not.
Click to expand...
Click to collapse
tdetroit said:
I don't think there's a root yet for the Verizon variant, and I've not actively searched for one at this point. It was needed while the Tablet was on 4.4.2, but 5.1.1 gives me enough control not to worry about it too much right now. Before I used Towelroot, which will NOT work on the new version.
Click to expand...
Click to collapse
Thanks for the feedback!
I have a specific reason to root and thats to use linux deploy so I can have a fully functional Linux OS on my tablet which would be really ideal so I think the root is still required. What control did you gain in upgrading to 5.1.1 ? Linux deploy needs root and SELinux permissive, from what I can tell, to use a loopback device and install the Linux OS there so I think even if I did get root, I'd still need to custom compile a kernel and to that end, I am not too confident in possibly bricking my brand new tablet. For now I seem to be able to settle on a VNC session to a Linux VM I have on DigitalOcean
i'm totally excited that my NP will eventually be updated to 5.1.1 it's just i'm still completely confused on why my stock (no-carrier) branded NP is still on 5.0.1, when Big-Red carrier is rolling out 5.1.1 to their devices.
I think I can smell the money being transferred to Sammy for Bid-Red's propriety rollout.
ckozler said:
Thanks for the feedback!
I have a specific reason to root and thats to use linux deploy so I can have a fully functional Linux OS on my tablet which would be really ideal so I think the root is still required. What control did you gain in upgrading to 5.1.1 ? Linux deploy needs root and SELinux permissive, from what I can tell, to use a loopback device and install the Linux OS there so I think even if I did get root, I'd still need to custom compile a kernel and to that end, I am not too confident in possibly bricking my brand new tablet. For now I seem to be able to settle on a VNC session to a Linux VM I have on DigitalOcean
Click to expand...
Click to collapse
I've actually noticed less bloatware, and apps that I couldn't disable before (which is why I rooted so I could get rid of them), I can disable now. I have a 128GB card in it loaded with Music, Books, Images, and on 4.4.2-the device would often F/C which it's no longer doing. I've also noticed that the micro-stutters as I call them, are gone. Everything is a lot smoother.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
lawalty said:
i'm totally excited that my NP will eventually be updated to 5.1.1 it's just i'm still completely confused on why my stock (no-carrier) branded NP is still on 5.0.1, when Big-Red carrier is rolling out 5.1.1 to their devices.
I think I can smell the money being transferred to Sammy for Bid-Red's propriety rollout.
Click to expand...
Click to collapse
Trust me friend....I was just as surprised when my Verizon Tablet had the update. I read about it while at work and told my Team Lead that I MUST go home right now, work from home or something, but I gotta leave NOW.
Do I have to throw my Verizon SIM to get the update or can I just keep it on WiFi?
sebastianraven said:
Do I have to throw my Verizon SIM to get the update or can I just keep it on WiFi?
Click to expand...
Click to collapse
Mine came over Wifi but I've always had my Verizon SIM in. Not sure if there was a pre-check before downloading.
I'm upgrading my rooted tablet now using Kies (I figure the upgrade is worth risking losing root--but I'm not sure it'll work anyway since I outright deleted Knox). I'll let you know if TR works to re-root, or if I lose root in the first place.
---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------
dot dot dot ... apparently I didn't read the threads above I'm upgrading regardless.
So apparently our phone is vulnerable to a newly founded exploit being dubbed "Quadrooter" that allows for privilege escalation. Do any of you think that this could lead to root on marshmallow if used right?
EDIT: Link to CNET article - http://www.cnet.com/news/quadrooter-security-flaws-said-to-affect-over-900-million-android-devices/
Saw this today. Curious to know as well. Not that this might be any use for me anymore as I'm still waiting to see if LG will fix my bootloop issue.
aarick said:
Saw this today. Curious to know as well. Not that this might be any use for me anymore as I'm still waiting to see if LG will fix my bootloop issue.
Click to expand...
Click to collapse
That's unfortunate. I fear it may be any day for me. We're there any signs before it hit the hay?
I am curious how they claim to be able to gain root access on multiple phones running marshmallow. DM Verity in the kernel is supposed to stop a phone with modifications from voting, so I am not sure how it's supposed to work, unless it's only some form of temp root. Kind of corps of this will be the next 'towel root'. Probably not, but I could hope I guess.
I have the ATT model and would love rooted MM. Hopefully this vulnerability can be used to our benefit.
I hope my H815t could be rooted by that
I have H815T and it's rooted, bootloader is unlocked and running Genysis 4.3 with G5 theme.
But I found the four vulnerabilities in my phone too.
What to do now?
claro4u90 said:
I have H815T and it's rooted, bootloader is unlocked and running Genysis 4.3 with G5 theme.
But I found the four vulnerabilities in my phone too.
What to do now?
Click to expand...
Click to collapse
The vulnerabilities are because your processor (Qualcomm Snapdragon). So, you can't do anything until LG implement arrangements in an update (OTA, KDZ).
lept_2014 said:
The vulnerabilities are because your processor (Qualcomm Snapdragon). So, you can't do anything until LG implement arrangements in an update (OTA, KDZ).
Click to expand...
Click to collapse
Yes you are right.
But my device is rooted and unlocked and OTA updates are disabled. So how would a user like me gets his security patch or such kind of updates?
claro4u90 said:
Yes you are right.
But my device is rooted and unlocked and OTA updates are disabled. So how would a user like me gets his security patch or such kind of updates?
Click to expand...
Click to collapse
You must flash a KDZ (for your G4 model) with LGUP. You'll lose root access, and OTA updates will be enabled. Or you can wait, and flash the KDZ with the fixes.
lept_2014 said:
You must flash a KDZ (for your G4 model) with LGUP. You'll lose root access, and OTA updates will be enabled. Or you can wait, and flash the KDZ with the fixes.
Click to expand...
Click to collapse
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?
claro4u90 said:
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?
Click to expand...
Click to collapse
You can't apply a official OTA with a rooted device without a error.
And the updates are in the firmware (aka ROM), so if you change de ROM, you will lose all updates.
What to do?
Install drweb antivirus for check apps before install.
This is the unic risk i found.
Sent from my XT687 using xda premium
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
Quadrooter affected
http://forum.xda-developers.com/showthread.php?t=3435585
Quadrooter affected
Sent from my XT687 using xda premium
---------- Post added at 10:40 PM ---------- Previous post was at 10:33 PM ----------
This is not so relevan more than, they are promoting goglebley site.
Ah! Stay protected:
I found in Settings.apk that this app access internet, for ... for example here, when i connect to wifi or 3g, my lightningWall is not on time delay to impess certain connections, so slowly i will forbid internet in some another apps by force , this app begun deny connection because some chitty google domains are included by me on the etc/hosts . So, is only prevent this app access internet , for security, this may gain privileges
I rebuilded with Lucky Patcher with denied INTERNET.permission in manifest.
Rebuild your Settings.apk, because this may gain privileges.
Sent from my XT687 using xda premium
lept_2014 said:
You can't apply a official OTA with a rooted device without a error.
And the updates are in the firmware (aka ROM), so if you change de ROM, you will lose all updates.
Click to expand...
Click to collapse
And will there be unofficial updates or such security patches for custom roms?
We have started a Q&A here, I hope many will get benefit from this conversation
Of course, mine is old xt687 , the motorola will never update anymore this, nicht paying!
Sent from my XT687 using xda premium
I hope it can be used to gain root on vs986 marshmallow
Sent from my VS986 using Tapatalk
claro4u90 said:
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?
Click to expand...
Click to collapse
If you are talking about the update.zip, it should be in the cache partition.
Using RR build 20160808 on h815 with llama kernel r6.
Sent from my LG-H815 using XDA Labs
Really! I believe this app haves a fake scanner with a png image as result.
All images are the same CHIT to promote goglebley crappy.
Sent from my XT687 using xda premium
Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
I am on July security patch and just got the prompt so don't think patch level matters
xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly
Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.
For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.
DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...