Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Kiwironic said:
Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Click to expand...
Click to collapse
Did you receive the survey or something? Or are you just being proactive and already creating a topic for when it happens?
Proactive mate, I have already singed up for the program and waiting for the soak for the international version.
Here we can follow updates about different variants of the phone (except for the main Droid turbo USA branch), who gets Soak, or official and news regarding that. I am using a PR XT1225, stock firmware and unrooted sadly due to corporate software.
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
GeodudeFFP said:
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
Click to expand...
Click to collapse
You're lucky you have that option, I don't as I have to use corporate software and cannot be rooted (let's not start talking about root cloaking etc as it didn't work for me)
Let's keep this alive with updates and share stories and we should be fine, I am assuming since Droid US has got 5.1 it won't be far for us. I would give it a month or two.
People keep saying that Droid turbo and Moto Maxx are left behind but the reality is, we are getting the 5.1 update at the same time as the Moto X so we should use the Moto X as an indicator. I think once Moto X (international version) gets the official 5.1 update (currently in Soak testing as the Droid Turbo) we will get it as well.
I think some people won't even have to wait. Tomorrow Motorola will release a downloadable file of Droid Turbo 5.1 for use with RSD lite, and since the Droid Turbo KK worked on Moto Maxx (since it's bootloader can be unlocked), I'm betting this one will too, but with some adjustments (like no flashing the rádio partition/flashing the intl rádio partition afterwards)
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Kiwironic said:
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Click to expand...
Click to collapse
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
DarkLey said:
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
Click to expand...
Click to collapse
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Kiwironic said:
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Click to expand...
Click to collapse
I do remember, for you it's really a no go if you want/have to keep the apps/data. Rootjunkysdl already have the OTA file, I'm backing up now to test my hypothesis.
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Kiwironic said:
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Click to expand...
Click to collapse
BR XT1225. One time I flashed the 4.4 Stock ROM for the Turbo in my device and it worked allright, and since this time I will just do the same then update, I think it'll work the same. Still backing up (a lot of data here).
Keep us updated mate.
Here are some news:
http://www.tudocelular.com/android/noticias/n56970/droid-turbo-moto-maxx-android-5-1-lollipop.html
How did it go??
Kiwironic said:
How did it go??
Click to expand...
Click to collapse
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
:fingers-crossed: Hope it goes well, and thanks for the link.
Hope to see ;
İncreased earpiece and speaker volume.
Better camera
Better calibrated screen for a little colder and more brightness.
Fix memory leak
and i am done.
Sent from my XT1225 using XDA Free mobile app
And better battery performance too
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
Wow. You are brave!
I'm happy right now with CM 12.1 (5.1.1 Lollipop on my two XT1225 phones. I'm actually in Brazil right now for two weeks, using them.
Hope 5.1 files Motorola releases will help for custom ROMs for our phones.
When Motorola does release 5.1 for the XT1225 (Moto Turbo and international Moto Maxx), the kernel source code is the main thing, but won't come for awhile.
First it's the OTA, then the full image, then a month or so later the kernel code. At least that seems to be the pattern.
Related
This post/thread is to summarize where to find full SBF files, leaks, etc for the Moto X (2013 or First Generation).
REMEMBER... Always flash the same ROM/SBF or Newer to your phone. NEVER attempt to downgrade your rom!!! for more info, see DOWNGRADING
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM and Verizon Developer Edition X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
If you have the Retail and/or Moto Maker XT1053 (aka Unlocked ships with T-Mobile SIM, or Unlocked Ships with Net10 SIM), you can also use the GSM Developer Edition (XT1053) roms from Moto's site.
If you have the Retail and/or Moto Maker Verizon X (XT1060), you can also use the Verizon Developer Edition (XT1060) roms from Moto's site.
There might be a delay in Moto making an SBF available.
For other models of X, I know of 3 sites for "leaks" which contain the SBF files for nearly every model of X (2013). You may need to check EACH site to find the particular rom you are looking for. NOTE: None of the following sites are owned, operated, or sponsored by Motorola. They may be down or offline at any time, without warning.
http://sbf.droid-developers.org/ <- DEAD when checking on 8/22/15
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 <- seems to have the most 4.4.4 roms
http://motofirmware.com/files/category/9-ghost/ <- DEAD when checking on 8/22/15 once there, look under the GHOST folder. (as of 11/9/2014, its format and access has changed)
http://motofirmware.center/files/ <- Select Moto X 1St Generation from the list along the right side of the page
Are there any others?
@dagoban has linked a few other in Post #17 of this thread..
dagoban said:
..Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Click to expand...
Click to collapse
See Post #17 for more direct links.
As 5.1 SBF files become available, they are being collected and curated in this thread -> [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1
FAQ:
1. How do I know which file to download?
- If you are NOT running a 3rd Party or Custom ROM... take a look on your phone, under App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until you find the SBF that matches. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. Where do all these SBF files come from?
As mentioned earlier, Moto does make the Dev Edition "recovery images" (in SBF format) available on their web site. For all others, the only way for us to get firmware files, is for a copy to be LEAKED to us.. The "Leaked" firmwares are files that are basically "stolen" by a Motorola or wireless carrier employee, who then posts the file on the internet for us... So we can't always count on this ever happening, nor can we have any expectations that a particular firmware will actually get leaked, or when it will be leaked.
There is some talk about using Motorla Device Manager (MDM) app to upgrade your phone, and how during the update process, the app downloads the full FXZ (another term for SBF) to your PC, so it could be copied/saved to another folder for use later. I have not done this with MDM.
EDIT: As of 12/12/14, Only the filefactory.com link is working. The others appear to be down. I don't know the owners of the sites, so I can't say if they will return or not.
EDIT2: As of 1/2/15, motofirmware.com seems to be back up, but sbf.droid-developers.org appears to be gone.
Great info! ??
SBF is my first choice, but when I needed the 4.4.4 retail firmware not found it in SBF, I had to turn to Google and found it.
FTP of Moto Firmware is empty, but the File Factory folder has many versions! Very cool.
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
x000x said:
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
Click to expand...
Click to collapse
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
edit: problem resolved. see my findings: http://forum.xda-developers.com/showpost.php?p=57122184&postcount=635
Thanks Kidjoe
x000x said:
well issue was I was rooted with twrp and silly me I tried to do the ota update. so now it won't get past the warning about unlocked bootloader. I read after the fact that you needed to revert back to stock before taking ota. mine is 30.71, but the other issue is I cannot find that firmware anywhere. my only option in regards to firmware is to use 4.4.2 that I found. I've posted the question here http://forum.xda-developers.com/showthread.php?t=2542219&page=123
Click to expand...
Click to collapse
BUT if you tried to take the OTA while TWRP was on your phone, just boot into fastboot mode on the phone, and do a mfastboot erase cache will get you out of the bootloop. Then you can flash stock recovery on there, take the ota.
Or you can just flash the 4.4.2 or 4.4.4 for your phone, when completed, flash TWRP on there, reboot hte phone to bootloader, enter Recovery/TWRP and root.
Yes, You can flash a higher/newer version without problems. You just can't flash older once 4.4.2 or higher has been flashed to your phone. (the only time its safe to flash older was when you had 4.4 on your phone, and you were Following the SlapMyMoto process to downgrade to 4.2.2. W/Camera Update as part of the process).
Thank you for this!
KidJoe said:
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
Click to expand...
Click to collapse
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
scryan said:
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
U can always flash newer images without a problem. It's flashing older images (downgrading) that's a problem.
scryan said:
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
The OTA updates are incremental, so you need to be on a certain level to take them. (to take 4.4.4 you need to be on 4.4.2, to take 4.4.2 you need to be on 4.4, etc)
Full SBF/FXZ files are complete roms. They are not incremental like the OTA Updates are. When flashing a FULL SBF/FXZ you can just flash it, so long as its the same version OR newer than what is on your phone, with no need to "step up." In other words, if you have 4.4 on your phone, you can flash directly to 4.4.4 using the full 4.4.4 SBF, without having to flash 4.4.2 on there first.
The risks to keep in mind would be, just like any update...
If you have a locked bootloader, the vulnerabilities exploited to root and disable write protection might be patched in the newer roms, that means you might not be able to root, or the processes may change for the newer rom. However, with an unlocked bootloader, there is no issue rooting and disabling write protection (lollipop is yet to be confirmed).
In either case, since you can't safely downgrade, if you find bugs, other issues (battery life, reception, etc), or there is something you don't like about the rom, you're stuck, since you can't safely downgrade.
THANK YOU SO MUCH every damn site I went to posted a link to a long dead server LIFE SAVER YOU ARE....
Method to go STOCK.
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
the_fiasco said:
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I suggest you use this : perfect compatible stock firmware for xt1052 asia retail first gen moto x. : http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip pl. check it with someone else just in case if I'm wrong. pm me if you have any problems
Hey, thanks for replying!
Yeah, I found this stock recovery a while ago and downloaded it and now back to stock 4.4.4. Thanks a lot!
Sent from my Moto X using XDA Free mobile app
@KidJoe since filefactory is really slow, I searched for some alternatives and found some good ones, maybe you could add it to your 1st post?
Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Some other alternatives:
XT1053 4.4.2; 4.4.3; 4.4.4 (downloading from mega server (fast!)), thx to OP (http://www.grupoandroid.com/topic/110743-aporte-firmware-t-mobile-retail-442/):
TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip: https://mega.co.nz/#!7RJygbQI!Sbx-bGRV8NbRsqLKS-d33nM_SEgY81czr8rye2ROYb0
TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml.zip: https://mega.co.nz/#!HQ4l2JIT!LD1gf8m2GxBou3NDFD8lzuxSi2OCn37X7Vhbe-hjNqc
TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz: https://mega.co.nz/#!zIJhlSCS!o9B7xvRSJ9gTCdTYjXdmVActEmdWRBvhIVjs8JUHI8Q
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/M2H9LMFJbYiag
from mega (fast!):http://www.mega.co.nz/#!jZgjECZT!sG0-9Vqngms551gwv9PfejY1mw_5QCL8Pg48KTVx4m0
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/KLmLR43SbYiaX
XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/hDEHw2O-bYiae
For Brazilians user's
http://www.motoforum.com.br/topic/4...oto-g-2014-moto-e-moto-maxx-nexus-6-moto-360/
Does anyone know of a link that contains the Rogers 4.4.4 file? I need it to update to 5.1.
I have tried the filefactory link but after the countdown, the file is unavailable. I haven't seen any other links for it.
Thanks
I have the same problem. I've looked everywhere and cannot find the rogers 4.4.4 file.
If anyone has it download, could you please share with us.
Alternatively, would i be able to Flash XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml.zip since the build versions are the same?
I only need the 4.4.4 in order to install the Lolipop update.
Thanks
So I just got a email for a soak test, wonder if it would block sunshine again. Luckily I already unlocked by mine.
zys52712 said:
So I just got a email for a soak test, wonder if it would block sunshine again. Luckily I already unlocked by mine.
Click to expand...
Click to collapse
A further reminder to spend the money for sunshine now if you have any desire for an unlocked bootloader. Do not cry here if you take this soak or the ota and can't unlock if you had the opportunity to do so now.
Interesting. Maybe they'll throw us a bone and actually give us some security patches besides the one that stops Sunshine from working.
$10 says it's just a security patch rushed out to block Sunshine. So, EVERYBODY will now rush to install it before unlocking their bootloader.
Motorola Droid Turbo to receive Soak Test; could a surprise Nougat update be on the way?
http://www.phonearena.com/news/Moto...-surprise-Nougat-update-be-on-the-way_id91284
If you own the DROID Turbo, don't get your hopes up too high. These type of surprises rarely ever happen. Additionally, the fact that Motorola wants to rush this Soak Test probably means that the update contains something less earth shattering than a new Android build. Instead, it might offer a few bug fixes or the latest Google security patch.
Click to expand...
Click to collapse
koftheworld said:
A further reminder to spend the money for sunshine now if you have any desire for an unlocked bootloader. Do not cry here if you take this soak or the ota and can't unlock if you had the opportunity to do so now.
Click to expand...
Click to collapse
If we already have bought/used sunshine is there any need to redownload and use it again before/after taking the OTA?
5538dcf5 said:
If we already have bought/used sunshine is there any need to redownload and use it again before/after taking the OTA?
Click to expand...
Click to collapse
If your xt1254 (Verizon Droid turbo) has an unlocked bootloader via the sunshine app before now, then you are safe and it is not necessary to purchase sunshine again.
It is best practice not to take OTA's ever, if you prefer having root access to your phone.
RL_Wells said:
If your xt1254 (Verizon Droid turbo) has an unlocked bootloader via the sunshine app before now, then you are safe and it is not necessary to purchase sunshine again.
It is best practice not to take OTA's ever, if you prefer having root access to your phone.
Click to expand...
Click to collapse
Right. That doesn't mean you can't ever install UPDATES. Just wait until the stupid people take the OTA, see what it does.
Then the update will be posted here in XDA -- in many places and you can install them manually. Like the 6.0.1 Marshmallow firmware update. It's posted here in XDA as:
the full raw update,
a TWRP flashable version, (flashed with RSD or fastboot)
and was turned into a debloated, tweaked ROM version.
All which could be installed by people with unlocked bootloaders. The latter two could be installed via TWRP custom recovery.
There was never any reason to take the unknown OTA from Verizon, and never will be a reason to do so. If an OTA from Verizon is useful in any way, many, many versions will be posted here with expert commentary on what it does, how to install it. Early version of the 6.0.1 Marshmallow OTA bricked Droid Turbos which were encrypted. Verizon/Motorola stopped the OTA for several days. There's NEVER any reason to be the guinea pig for Verizon's incompetence. It's not like they didn't have enough time to test the firmware! The XT1225 got the SAME Marshmallow back in July 2016.
ChazzMatt said:
Right. That doesn't mean you can't ever install UPDATES. Just wait until the stupid people take the OTA, see what it does.
Then the update will be posted here in XDA -- in many places and you can install them manually. Like the 6.0.1 Marshmallow firmware update. It's posted here in XDA as:
the full raw update,
a TWRP flashable version, (flashed with RSD or fastboot)
and was turned into a debloated, tweaked ROM version.
All which could be installed by people with unlocked bootloaders. The latter two could be installed via TWRP custom recovery.
Click to expand...
Click to collapse
Question about the debloated, tweaked ROM version...what difference will I notice versus stock? Is there anything that doesn't work in the ROM?
Everytime sunshine finds an exploit that unlocks Droid Turbo's bootloader Verizon gives us a new update..
Coincidence? I think not.
Dabrador said:
Question about the debloated, tweaked ROM version...what difference will I notice versus stock? Is there anything that doesn't work in the ROM?
Click to expand...
Click to collapse
It's gotten enthusiastic reviews from users, but would be better for you to go to that link and read the op (first post) and then read the last few pages of comments. Not all the pages, but at least the last 5 or 6.
A couple of us already told you about it in the other thread:
ChazzMatt said:
I know you don't want a "ROM", but you might consider ComputerFreak274's stock-based ROM. It's just de-bloated, tweaked stock Verizon Motorola Marshmallow firmware. Has audio boost and some other stuff too -- battery tweaks, speed tweaks, cache tweaks, etc.
If you are a Verizon user, right now this is the only "ROM" that lets you keep VoLTE and Wi-Fi calling on Verizon.
You can still install Xposed with this, he tells you how to do it in his op.
I'm on Resurrection Remix Marshmallow myself, so I'm not suggesting it because I use it (I have XT1225, not XT1254). I'm suggesting it because it's basically stock firmware the way Verizon/Motorola should have released it. It's a "ROM" for XT1254 Verizon users who don't want full custom ROMs.
Click to expand...
Click to collapse
Claps1775 said:
Only xposed I have install is the YouTube add block . I have gravity box for other tweaks. I am on CFs ( ComputerFreak274) 1.06 mm ROM. I like his work. Check it out.
Click to expand...
Click to collapse
Has anyone taken the Feb soak? Anything interesting?
Just got it, it's only a security update. You can check the Droid Turbo Reddit for confirmation, a user there has the same results.
Confirmed by Verizon: https://www.verizonwireless.com/support/droid-turbo-update/
Also, I'm downloading it now, and I'm not part of the soak test. I'll capture the OTA and post it shortly.
Alienite said:
Just got it, it's only a security update. You can check the Droid Turbo Reddit for confirmation, a user there has the same results.
Click to expand...
Click to collapse
A "security update" to block Sunshine? [emoji14]
Now that Sunshine unlocks 6.0.1 bootloader?
Figured as much. The people speculating Nougat were delusional. Lenovo/Motorola hasn't even given all the Quarks Marshmallow yet.
My response to a post from this morning in another thread, but relevant to this discussion...
cod3name47 said:
Any idea about nougat update for Moto Maxx?
Click to expand...
Click to collapse
Nougat? Motorola hasn't even released stock Marshmallow for all the Moto Maxx phones yet! The U.S. Moto Maxx XT1250 (clone of the XT1254 Droid Turbo in every way -- FCC ID, radio bands) is still on 5.0.2 Lollipop!
None of the Quarks are on the Motorola Nougat list, which was released months ago by Motorola/Lenovo. Would be very unusual to give an unannounced Noguat 7.X update, since Motorola/Lenovo seems to want to do less work -- not more -- regarding updates to their customers.
Motorola announced Marshmallow for Quarks October 2, 2015. WHEN did they deliver it?
XT1225 Moto Maxx/Moto Turbo got it in July 2016 (9 months later),
Took Motorola until December 2016 (13 months) to actually give it to the Droid Turbo XT1254 --
U.S. Moto Maxx still does not have Marshmallow (16 months and counting).
If you want Nougat, unlock your bootloader and flash any of the custom Nougat 7.X ROM we have available. Here's the current custom Nougat (7.x) Quark ROMs to choose from.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
[ROM][7.1][All quark] crDroid Android
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI][quark]
OTA posted. https://forum.xda-developers.com/dr.../ota-marshmallow-build-mcg24-251-5-5-t3565697
Hahahhahaha I know they are lazy....Motorola was good untill it was solo company!!! Lenovo ruined it!!
they won't keep us current, but they can bang out an update to patch sunshine, WTF? it's like they want to say FU to us for using this phone..
rhcreed said:
they won't keep us current, but they can bang out an update to patch sunshine, WTF? it's like they want to say FU to us for using this phone..
Click to expand...
Click to collapse
Well to be fair, the android security patch version is now dated January 2017, so at least there's that.
Also, at long last, we are finally protected from the Stagefright vulnerability :laugh:
DD?
ChazzMatt said:
A "security update" to block Sunshine? [emoji14]
If you want Nougat, unlock your bootloader and flash any of the custom Nougat 7.X ROM we have available. Here's the current custom Nougat (7.x) Quark ROMs to choose from.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
[ROM][7.1][All quark] crDroid Android
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI][quark]
Click to expand...
Click to collapse
Still running (unlocked) stock, what do you recommend as a DD? I really just want it to work and have solid battery life (why I bought this phone 2+ years ago). Is there one of these seen as the most stable? (My days of finding a decent rom for my S3 were a nightmare, no one rom was stable enough to "just work") Thx!
rhcreed said:
Still running (unlocked) stock, what do you recommend as a DD? I really just want it to work and have solid battery life (why I bought this phone 2+ years ago). Is there one of these seen as the most stable? (My days of finding a decent rom for my S3 were a nightmare, no one rom was stable enough to "just work") Thx!
Click to expand...
Click to collapse
Any of the top three Nougat ROMS on the list have very high reviews. You can go to those threads and ask questions, and see other Droid Turbo owners.
#2 and #3 are maintained by Droid Turbo owners who use Verizon, if that makes a difference to you. But all three are excellent and many Droid Turbo owners are using all three.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
However, if you need Verizon VoLTE, then you should go with a debloated, tweaked Marshmallow ROM based on stock Motorola Verizon firmware. See below. It's not Nougat, but right now only stock Motorola Verizon firmware or a ROM based on stock Verizon firmware can get Verizon VoLTE on this phone -- until a dev discovers the secret handshake. (ZTE has discovered the secret handshake for Verizon VoLTE. Now a dev just needs to figure out what they did.)
_________
@computerfreek274 has now released a Marshmallow ROM for the Droid Turbo XT1254 based on the Verizon's belated Marshmallow firmware. He has debloated it, tweaked it. It has Verizon voicemail app, Verizon VoLTE (only works on Verizon), Verizon Wi-Fi calling (only works on Verizon), some volume boost, and battery saving tweaks.
* Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
http://forum.xda-developers.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634
Apologies if this has been asked before or if this is a stupid question, but it appears there are no stock images of the XT1687 (US unlocked) version of this phone?
This makes the idea of unlocking the bootloader and trying out custom ROMs kinda iffy if there's no way to easily return to stock. My Nexus, HTC and Samsung phones, for example, could easily be restored to the stock OS with a computer. Only thing I can find for this phone is OTA updates that can be sideloaded... nothing that would enable me to return to stock everything (recovery, OS, etc.) easily in the event that I would want to.
Is there something I'm missing that's different with Motorola phones?
Yes, you can easily go back to stock, I've done it a few times already. You can find threads & info here on it if you search around. Check in settings to see which build you have and the official firmware for Moto G5 Plus (aka potter) is located here:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Some have received OTA upgrades but so far Moto hasn't officially posted those, so the above are what you originally got on your phone and any newer ones will appear there when available.
Dahenjo said:
Yes, you can easily go back to stock, I've done it a few times already. You can find threads & info here on it if you search around. Check in settings to see which build you have and the official firmware for Moto G5 Plus (aka potter) is located here:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Some have received OTA upgrades but so far Moto hasn't officially posted those, so the above are what you originally got on your phone and any newer ones will appear there when available.
Click to expand...
Click to collapse
I don't think any XT1687s have gotten updates to .67, and in fact when I flashed .67 to my phone VoLTE and T-Mobile wifi calling stopped working even though the software channel still says retus...I imagine there are updated binaries for said functions that is why we in the US haven't got the update
bakedpatato said:
I don't think any XT1687s have gotten updates to .67, and in fact when I flashed .67 to my phone VoLTE and T-Mobile wifi calling stopped working even though the software channel still says retus...I imagine there are updated binaries for said functions that is why we in the US haven't got the update
Click to expand...
Click to collapse
I'm running the debloated/deodexed .67-based stock ROM and mine also still shows retus in settings. Everything works identically well to my "assigned" .33 from before, but I'm on AT&T so don't use VoLTE.
Return to stock
I have a moto g5 plus xt1687, where can I download a stock rom. I am currently rooted and do not have a backup to the original rom. What are my options? Thanks.
My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!
You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.
acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.
FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:
Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.
Hi,
I have a stock HTC 10 running Nougat right now. It is not bootloader unlocked, rooted, or s-off yet. I plan on sending it in to sunshine soon. However, I just got the OTA notification for OREO. I am afraid to install it, since I don't don't want to ruin the possibility of me getting s-off and root. Does anyone know if the Oreo OTA affects the paths to root or s-off? Should I avoid it until after I'm s-off? Is there a chance that the OTA will actually make root/s-off easier? Has anyone tested that yet?
Sooner is always smarter than later. Sounds like a question for the sunshine team.
http://theroot.ninja/
This is what it says for the latest version:
SunShine is our bootloader unlock/s-off tool for Motorola and HTC phones. We currently support most HTC phones, and Droid Turbo, Moto X (2014), Moto X (2013), MotoG (2013) and Droid Maxx/Mini/Ultra on Android 4.4.3 and lower. All modern HTC devices (m9 m7 m8 e8 Mini2 remix dna etc) devices are supported up to 7.1.1, as long as they are rootable. SunShine can work without pre-rooting all 4.4.3 and below devices, and some 4.4.4 and 5.x devices. Some 5.0 and above users will have to root with HTCDev.com. Verizon M7 5.0.x users will have to temp root with the Kingroot app. DROID TURBO 2 IS NOT SUPPORTED
Yea they don't say anything about Oreo, though. Guess we'll have to wait until someone is brave enough to try it
deke997 said:
Yea they don't say anything about Oreo, though. Guess we'll have to wait until someone is brave enough to try it
Click to expand...
Click to collapse
My recollection is that anything past Marshmallow on the Verizon 10 and you're in mail-in territory. I can't imagine that Oreo somehow cures that.
I was on Sunshine IRC with a similar question. I bought a refurbished 10 on N and asked if I should take the O OTAs or mail it as is for unlock. The response I got is that it didn't make a difference, and that I could send it either way.
Shipped mine as was. N August 2017 update .23
Flashed the latest firmware from here https://forum.xda-developers.com/showpost.php?p=70340070&postcount=2
This one >> 3.18.605.13 Combined Firmware with stock boot.img and stock recovery removed(will NOT wipe)
Used TWRP (installed to my device with SS mail unlock service) to install the latest Oreo OS (OP prior link) with options as suggested here https://forum.xda-developers.com/showpost.php?p=76271053&postcount=624
All is well.