Related
My plan when the 5.1 update comes is to wait for someone to release the files, which hopefully will happen soon after the update if people will use Motorola Device Manager to update to get the files.
Then once the 5.1 system.img is pre-rooted, I would flash that along with the 5.1 kernel/radios but leave the bootloader and partition table on 5.0 until we know if mofo.exe works on 5.1. This may or may not be stable doing it this way, I will have to see. And mfastboot may or may not have checks in it to prevent me from flashing the 5.1 kernel/radios with a 5.0 bootloader/partition table, idk.
I don't think that 5.1 bootloader should have patched whatever exploit mofo.exe takes advantage of since mofo.exe was not even released until after 5.1 was released on the Nexus 6. I doubt there was time for Motorola to patch this or even figure out what mofo.exe is doing.
Thoughts anyone? And if someone is planning on upgrading to 5.1, please use MDM and post the files!! Thanks!
Edited - would I need to flash the 5.1 recovery too?
Edited - maiko1 has posted that MoFo won't work on 5.1 so that is something to think about before upgrading.
I'm also waiting for 5.1, and assuming it can be used with mofo, I _WILL_ go and buy mofo))
Reminder - if you upgrade to 5.1, YOUR VERSION OF MOFO.EXE WILL NOT WORK ON 5.1. This is because the way maiko1 has configured things - your version of mofo.exe will only work on 4.4.4, 5.0 and 5.0.2 bootloaders. He needs to make some changes to the purchase process to allow you to redownload (for free) a new version of mofo.exe that will work on 5.1 because mofo.exe not only checks your device serial number but also checks the version of the bootloader you are running.
So you will not be able to use mofo.exe if you upgrade to 5.1. You will need to wait for maiko1 to make the necessary changes to his site to allow you to redownload an updated copy of mofo.exe that will be able flash your device once you have a 5.1 bootloader.
I just wanted to give everyone using MoFo a heads up here - maiko1 hasn't been responding to emails and hasn't been on XDA for a week. So if you upgrade to 5.1 and need to wait on maiko1 to make his updates before you can redownload a copy of mofo.exe that will work on the 5.1 bootloader, there is no telling how long it will take for him to make his updates.
The problem is not just that maiko1 is not responding lately, we also will have to wait for the 5.1 fxz to show up. This is true for the XT1096 users even if we just want to flash modified 5.1 system images w/o updating the bootloader. The XT1097 users can likely modify the Pure Edition 5.1 system.img.
Well the update still hasn't arrived !
@maiko1 has edited the OP of the MoFo thread to say that MoFo doesn't work on the next update Idk if that is 5.1 or the minor 911 bug.
Wasn't the 911 bugfix update only for the 2013? Unless we got one too (I froze the OTA app in TiBU but haven't heard of the 2014 getting it).
As much as I'd like to have 5.1, my plan is to wait until a flashable 5.1 image with root and xposed becomes available. Now that I have root, I don't want to give it up even for 5.1.
I got an invitation for the 5.1 soak test from Motorola today. I'd like to help, but I don't want to lose root.
I got an invitation also. Not going to accept it unless it can be MoFo'ed
Can I have your invitation Ive never even rooted this phone lol
Sent from my XT1096 using Tapatalk
Temporary root from Kingroot on att running lollipop xt1097
I obtained root using kingroot on my att xt1097, it was temporary, about 5 minutes. Has anyone use kingroot? I root on the first try, then I thought I did something wrong so I tried it again and it didn't work... Tried it like 15 more times and it worked again tried to install binaries with supersu and rebooted and lost it again. Repeated the process again and keep losing the root. Any ideas?
Not sure if anyone got back to you on this but, kingroot is a temp root, it doesn't last past a reboot. I'm not entirely sure it'll even stay during a session on the moto x at all. Our phone, (last I checked) wasn't officially supported by the kingroot app yet.
It appears the 5.1 update is live for soak testers...hopefully someone can get the files for you guys to test out MoFo
So allow OEM unlock is under developer options... Not near a pc to attempt it. That is if it works similar to my n6 and is as simple as fastboot OEM unlock
GatorsUF said:
It appears the 5.1 update is live for soak testers...hopefully someone can get the files for you guys to test out MoFo
Click to expand...
Click to collapse
For xt1096??!! Haven't got my update yet
tacosrdelicioso said:
For xt1096??!! Haven't got my update yet
Click to expand...
Click to collapse
Yep. Seems smooth. I hope it means unlocking will soon be possible. It would be like having a mini nexus 6 lol
And tried to unlock... Need code. Motorola won't give it up. Dang them.
I got the ota uploading to drive. Once it's done I'll post a link so someone can check it out.
---------- Post added at 08:12 AM ---------- Previous post was at 07:59 AM ----------
https://drive.google.com/file/d/0B-05eXAx4kW7aFV3Z3I0OG4yUU0/edit?usp=docslist_api
Soak ota
shane1 said:
I got the ota uploading to drive. Once it's done I'll post a link so someone can check it out.
---------- Post added at 08:12 AM ---------- Previous post was at 07:59 AM ----------
https://drive.google.com/file/d/0B-05eXAx4kW7aFV3Z3I0OG4yUU0/edit?usp=docslist_api
Soak ota
Click to expand...
Click to collapse
@JulesJam go go go
I didn't take the update for obvious reason, does anyone know if this updates bootloader?
Does anybody know if I will have problems if I install the OTA if I am currently rooted with MoFo? I understand that I will likely lose root, but will I brick my phone or anything?
bhmcarr said:
Does anybody know if I will have problems if I install the OTA if I am currently rooted with MoFo? I understand that I will likely lose root, but will I brick my phone or anything?
Click to expand...
Click to collapse
your phone would have to be running a stock system image for the update to even install. if you have anything in the system thats altered it will halt the update and fail. I dont know if just having root will stop it.
Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-late...xploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
glitch3yf0x said:
Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-latest-on-stagefright-cve-2015-1538-exploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
Click to expand...
Click to collapse
Historically only one file needs to be renamed to effectively disable OTA without hampering other functionality. Also makes the block easily reversible. PM me for details. Not a secret but there are several similarly named files. Those who tinkered with the wrong file(s) on other device types earned a brick. Needs proper testing on this device with FireOS 5.1.1 (preferably w/5.0.1 bootloader) before being released in the wild. Obviously hiding/disabling components is not reliable.
glitch3yf0x said:
Surprised there wasn't a central place we could share information and progress toward root yet.
I test FireOS 5.1.2 for common vulnerabilities and one thing came back positive:
CVE-2015-6602 (StageFright vulnerability)
https://blog.zimperium.com/the-latest-on-stagefright-cve-2015-1538-exploit-is-now-available-for-testing-purposes/
A note to all developers, when a root method is found, if you make a root program or script, make sure it nukes OTA updates completely. Amazon, without a doubt, will pull a d*ck move like this again.
Click to expand...
Click to collapse
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
sd_shadow said:
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
http://www.kingroot.net/
Is this the right one?
glitch3yf0x said:
http://www.kingroot.net/
Is this the right one?
Click to expand...
Click to collapse
yes, here is xda thread
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from my KFFOWI using XDA Labs
Davey126 said:
Obviously hiding/disabling components is not reliable.
Click to expand...
Click to collapse
Is renaming the OTA apks failing to work? I know pm hide is not a reliable or preferred method but I was hopping that renaming the apks worked.
sd_shadow said:
looks like kingroot windows program roots 5.1.2 now
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
It .apk version failed for me...
Is it the Windows version?
glitch3yf0x said:
It .apk version failed for me...
Is it the Windows version?
Click to expand...
Click to collapse
yes windows Version 3.2.0 Build 1128
Sent from my KFFOWI using XDA Labs
Why are we renaming or hiding? I'm confused. AutoRootScript just delete the components to OTA and OTACerts.zip. Is it frowned upon to completely delete the dependencies?
Not sure what SuperTool does.
glitch3yf0x said:
Why are we renaming or hiding? I'm confused. AutoRootScript just delete the components to OTA and OTACerts.zip. Is it frowned upon to completely delete the dependencies?
Not sure what SuperTool does.
Click to expand...
Click to collapse
SuperTool just uses adb hide command
if you delete it is harder to update if want to
Sent from my KFFOWI using XDA Labs
---------- Post added at 09:14 PM ---------- Previous post was at 09:10 PM ----------
adb hide has proven to be less than adequate to stop updates
Sent from my KFFOWI using XDA Labs
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
You guys are awesome, thanks for all the hard work!
blueberry.sky said:
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
Click to expand...
Click to collapse
renaming or deleting the update apps works or freezing with titanium backup pro
Sent from my KFFOWI using XDA Labs
blueberry.sky said:
Sorry, I'm a little behind on the best method for blocking OTA. Since both of my Fires are 5.0.1 and on SlimLP. But I'd like to block OTA on a friend's Fire, once it's possible on 5.1.2.
Click to expand...
Click to collapse
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_Has this not worked for some people?
I also pm disable com.amazon.otaverifier (although I'm not so sure this is bullet-proof anymore).
The only (poor) option for unrooted is pm hide, which doesn't work on OS 5.1.1. Someone suggested using pm clear with this, but it didn't work for me.
DoLooper said:
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_
Click to expand...
Click to collapse
This is the GOLD standard. What you rename it to is irrelevant; just ditch the 'apk' suffix.
As well as original Stagefright vulnerability CVE-2015-6602 mentioned in the OP, FireOS 5.1.2 may also be vulnerable to the relatively new CVE-2015-1805
Google confirmed that CVE-2015-1805 was already being exploited by a "publicly available rooting application":
https://source.android.com/security/advisory/2016-03-18.html
Zimperium went further and confirmed that the "publicly available rooting application" is KingRoot:
https://blog.zimperium.com/zimperium-applauds-googles-rapid-response-to-unpatched-kernel-exploit/
Affected devices are unpatched Android devices on kernel versions 3.4, 3.10 and 3.14, including Google’s own Nexus 5 and Nexus 6 devices running the March 01, 2016 Security patch level or below.
Click to expand...
Click to collapse
Davey126 said:
This is the GOLD standard. What you rename it to is irrelevant; just ditch the 'apk' suffix.
Click to expand...
Click to collapse
Same as i do i just add a letter after apk and it isnt seen as a application until it is changed back. Very effective
DoLooper said:
This one file rename has not failed me through many versions on many gens of ROOTED Amazon tablets (including Fire on 5.1.1):Rename /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to DeviceSoftware OTA.apk_Has this not worked for some people?
Click to expand...
Click to collapse
Thanks I just did this to stay on 5.1.1.
Here is a link to the original proof of concept files that were sent to Google for CVE-2015-6602:
https://code.google.com/p/android/issues/detail?id=182908
Also, Trend Micro have recently published a detailed blog entry about CVE-2015-1805:
http://blog.trendmicro.com/trendlab...lity-allows-permanent-rooting-android-phones/
Apparently I've missed something somewhere, what does the pm mean in 'pm disable'?
Don't do it period.
Dunard said:
Don't do it period.
Click to expand...
Click to collapse
Is this the firmware for the Kid's Version only? I bricked the Kid's Version after trying RootJunky's method to root and I assumed the 5.3.1 is the same as the 5.1.4 since both Kindles are identical besides the foam case it comes with. So basically when I get my new Kindle Kid's Edition, how can I root it?
fusion01k said:
Is this the firmware for the Kid's Version only? I bricked the Kid's Version after trying RootJunky's method to root and I assumed the 5.3.1 is the same as the 5.1.4 since both Kindles are identical besides the foam case it comes with. So basically when I get my new Kindle Kid's Edition, how can I root it?
Click to expand...
Click to collapse
You cross posted the same question in three different thread, don't do it. The answer is the same: 5.3.1 is unrootable so far.
fmc000 said:
You cross posted the same question in three different thread, don't do it. The answer is the same: 5.3.1 is unrootable so far.
Click to expand...
Click to collapse
Sorry about cross posting but I wanted a quick answer as I was posting about this on Root Junkys channel and never got a response about this firmware. So how long will it be before 5.3.1 is rootable and who actually will make it happen? I'm new here and new to rooting and following one of the best supposedly I got bricked. I should have come here first to see this warning. Now Im screwed having to send it back to Amazon. Once they find out it's bricked they may still make me pay for it. If that's the case I will be pissed.
fusion01k said:
So how long will it be before 5.3.1 is rootable and who actually will make it happen?
Click to expand...
Click to collapse
Well, who knows?
Apart from the 5.0.1 and 5.1.1 versions, who can be easily rooted because their bugged fastboot implementations allows a custom recovery to be loaded even with the locked bootloader, so far only the 5.1.2 version is rootable and the process is no different compared to what is used to root other devices. In short, you have to find a bug in the software that allows for a privilege escalation, and that's what for example KingRoot does.
So far, no such bugs have been found in 5.1.2.1, 5.1.3, 5.1,4 and 5.3.1 FireOS releases. The first three have many parts in common, therefore they can downgraded to 5.1.2 and subsequently rooted. Nothing can be done for 5.3.1 thus far.
fusion01k said:
Sorry about cross posting but I wanted a quick answer as I was posting about this on Root Junkys channel and never got a response about this firmware. So how long will it be before 5.3.1 is rootable and who actually will make it happen? I'm new here and new to rooting and following one of the best supposedly I got bricked. I should have come here first to see this warning. Now Im screwed having to send it back to Amazon. Once they find out it's bricked they may still make me pay for it. If that's the case I will be pissed.
Click to expand...
Click to collapse
Amazon will exchange a bricked device no questions asked. Just don't volunteer too much information. Less is more ...
fmc000 said:
Well, who knows?
Apart from the 5.0.1 and 5.1.1 versions, who can be easily rooted because their bugged fastboot implementations allows a custom recovery to be loaded even with the locked bootloader, so far only the 5.1.2 version is rootable and the process is no different compared to what is used to root other devices. In short, you have to find a bug in the software that allows for a privilege escalation, and that's what for example KingRoot does.
So far, no such bugs have been found in 5.1.2.1, 5.1.3, 5.1,4 and 5.3.1 FireOS releases. The first three have many parts in common, therefore they can downgraded to 5.1.2 and subsequently rooted. Nothing can be done for 5.3.1 thus far.
Click to expand...
Click to collapse
Thanks fmc000, I appreciate the thorough explanation. I think when I first turned in my kindle it updated from 5.1.4 to 5.3.1 before I could do anything to stop it, so there was no way from the get go for me to root my week old Kindle I bought on Amazon's Prime Day. Hopefully this changes going forward. Maybe I'll have to buy a rooted Kindle on eBay...
.
I see there has been no activity on this thread for a few months. Any new news on rooting or rolling back 5.3.1.0?
Revonoc said:
I see there has been no activity on this thread for a few months. Any new news on rooting or rolling back 5.3.1.0?
Click to expand...
Click to collapse
5.3.1 can be rooted. Look at other Amazon forum threads. SuperTool can now be used to root 5.3.1.
gtallmadge said:
5.3.1 can be rooted. Look at other Amazon forum threads. SuperTool can now be used to root 5.3.1.
Click to expand...
Click to collapse
So far I can't root 5.3.1 regardless of what other threads say - kingroot initially says there is no root available, and tries anyway, no dice.
Ive tried reflashing, resetting, different versions, nothing seems to work.
iRub1Out said:
So far I can't root 5.3.1 regardless of what other threads say - kingroot initially says there is no root available, and tries anyway, no dice.
Ive tried reflashing, resetting, different versions, nothing seems to work.
Click to expand...
Click to collapse
Have you tried rooting with different versions of Kingroot? Supertool has 4.8.5 if I remember correctly, give the newest one (5.0 I think) a go.
Also try multiple times, in my case it was sometimes the 3rd time that actually worked.
iRub1Out said:
So far I can't root 5.3.1 regardless of what other threads say - kingroot initially says there is no root available, and tries anyway, no dice.
Ive tried reflashing, resetting, different versions, nothing seems to work.
Click to expand...
Click to collapse
It works. Not reliably, not consistently, not conveniently. But eventually. Many skeptics have preceded down river of denial only to find joy you when root is eventually secured.
Best results have been reported with Kingroot 4.85, 4.92 and 4.96. WiFi must be enabled. There's also a desktop build but the interface is in Chinese.
Avoid 5.x.x builds as removal and migration to SuperSU can be problematic. SuperSU is a FlashFire prerequisite which itself is a prerequisite for flashing custom ROMs on this device.
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
amerkiller1995 said:
Have you tried rooting with different versions of Kingroot? Supertool has 4.8.5 if I remember correctly, give the newest one (5.0 I think) a go.
Also try multiple times, in my case it was sometimes the 3rd time that actually worked.
Click to expand...
Click to collapse
Avoid KingRoot v5 as removal can be problematic; see previous post. Stick with v4.85-4.96.
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, what happens if I update while I get rooted? My phone suggests me the 139.50 update, but I'm rooted, will it work? Do I need to root it again after the update?
Thank you I'm sorry for the stupid questions. This is my first post with this account, I'm not that newbie but I've never had a Motorola phone.
Guygiorge said:
Hey guys, what happens if I update while I get rooted? My phone suggests me the 139.50 update, but I'm rooted, will it work? Do I need to root it again after the update?
Thank you I'm sorry for the stupid questions. This is my first post with this account, I'm not that newbie but I've never had a Motorola phone.
Click to expand...
Click to collapse
Since you're rooted, I'm assuming you probably have a custom recovery like TWRP installed.
Any official update (OTA) will work only with a stock Android recovery installed.
This means no, you cannot have an OTA update once you root. However, there is a thread on this forum somewhere which has a very reliable but slightly complicated method of getting OTA updates even of rooted.
You may refer to that. And ya, welcome to the XDA family!
Sent from my Moto G (4) using Tapatalk
1chrome said:
Since you're rooted, I'm assuming you probably have a custom recovery like TWRP installed.
Any official update (OTA) will work only with a stock Android recovery installed.
This means no, you cannot have an OTA update once you root. However, there is a thread on this forum somewhere which has a very reliable but slightly complicated method of getting OTA updates even of rooted.
You may refer to that. And ya, welcome to the XDA family!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Thank you so much. It looks way harder than I thought. You need to update each version til the latest one. SMH. I'm not trying to be spoon fed here. But do you remember the keywords to this thread?
LOL it seems like it's gonna be a long day to update my phone.
https://r.tapatalk.com/shareLink?ur...share_tid=3472658&share_fid=3793&share_type=t
[GUIDE] Sucsessful OTA-Update after Rooting + other system changes
Sent from my Moto G (4) using Tapatalk
---------- Post added at 05:33 PM ---------- Previous post was at 05:31 PM ----------
Thread name:
[GUIDE] Sucsessful OTA-Update after Rooting + other system changes
Sorry not able to paste link from my app!
Sent from my Moto G (4) using Tapatalk