I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
Thanks for the info. Will give it a try.
bumping this up b/c 5.1 is coming soon!!!!
JulesJam said:
bumping this up b/c 5.1 is coming soon!!!!
Click to expand...
Click to collapse
Any link that says so?
Sent from my XT1095
Hopefully there's some Verizon love
AGISCI said:
Any link that says so?
Click to expand...
Click to collapse
http://www.droid-life.com/2015/05/0...droid-5-1-updates-here-are-the-release-notes/
Why? What is wrong with ota?
lobango said:
Why? What is wrong with ota?
Click to expand...
Click to collapse
Nothing is wrong with it. The point in getting the fxz is that it will be a full image that we can share.[emoji2]
Sent from my XT1095
i saw this on gsm arena.
http://www.gsmarena.com/motorola_posts_android_51_release_notes_for_1st_and_2nd_gen_moto_x-news-12165.php
nevermind
bump!
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
jcracken said:
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
Click to expand...
Click to collapse
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
JulesJam said:
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
Click to expand...
Click to collapse
But that shouldn't preclude the second option of manually flashing the img files, right? Can someone post the FXZ? I'd like to try this.
jcracken said:
But that shouldn't preclude the second option of manually flashing the img files, right?
Click to expand...
Click to collapse
Correct.
jcracken said:
Can someone post the FXZ? I'd like to try this.
Click to expand...
Click to collapse
Nobody has that yet. That is the whole point of this thread - to get people to use MDM so that we will have the fxz for all of the devices.
MDM won't update the devices until the OTA is pushed. But if your phone has started to download the OTA, MDM will say an update is in progress so it won't download the files.
What I am saying is that people should not take the OTA - disable MotorolaOTA - and use MDM to update to get the fxz.
bump
JulesJam said:
bump
Click to expand...
Click to collapse
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Steve-x said:
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Click to expand...
Click to collapse
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
JulesJam said:
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
Click to expand...
Click to collapse
Very cool, and very useful.
bump!
Related
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!
Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol
Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...
Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip
If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE
sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.
With the stock rom, can I just flash it using a custom recovery?
yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.
Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download
as many of you might have seen everyone who updated his phone via fota got stuck in recovery..why?...cant I update if my phone is rooted?...should I always wait for the flashable file?
Never OTA if modified. Period.
liavo555 said:
as many of you might have seen everyone who updated his phone via fota got stuck in recovery..why?...cant I update if my phone is rooted?...should I always wait for the flashable file?
Click to expand...
Click to collapse
Well....
chaki- said:
Well....
Click to expand...
Click to collapse
so how do I get the update if not with the official method
if you have custom recovery never ota
You can ota with root if you meet the following requirement:
1)you don't have any mods
2)you don't use xposed
3)you haven't removed bloat
4)you have not modified system partition in other words the system folder
5)and most importantly you do not have custom recovery, for ota to work you need the stock recovery to work
DO NOT RESTORE BACK TO 4.4. THIS WILL BRICK YOUR PHONE.
--UPDATE--
JUST FLASH THIS! (In stock recovery) https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view
--
(if the above doesn't work, or if you are not on totally stock, use the following method)
Here is how to upgrade from 23.11.14 to 23.16.3
What you need: https://yadi.sk/d/cBaKACE7hQH9Y (upgrade from stock 5.0 to 23.16.3)
http://www.graffixnyc.com/motox.php (stock 5.0 image. You need to use this one. The one found in Motorola's site WILL NOT WORK WITH THIS METHOD)
Unzip the stock 5.0 image
Boot into fastboot
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Boot into recovery
adb sideload Blur_Version.22.21.11.victara_tmo.tmo.en.US.zip
reboot!
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Grzesiek1010 said:
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Click to expand...
Click to collapse
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
bongostl said:
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
Click to expand...
Click to collapse
ok but what with all apps data setting ?
Grzesiek1010 said:
ok but what with all apps data setting ?
Click to expand...
Click to collapse
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
bongostl said:
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
Click to expand...
Click to collapse
better wait for official update too much risk lost data ...
I successfully downgraded to 5.0, and I've attempted the sideload method twice and failed. Each time it says there is an error in the package, status 7. I get the same result when I apply update from sd card. Any ideas?
---------- Post added at 12:25 PM ---------- Previous post was at 11:43 AM ----------
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Use the files I posted.... That's what I used
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
leffer said:
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
Click to expand...
Click to collapse
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
sivarticus85 said:
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
Click to expand...
Click to collapse
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
leffer said:
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
Click to expand...
Click to collapse
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Success!
Stanleywinthrop said:
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Click to expand...
Click to collapse
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
thenestor said:
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
thanks for your help. I tried to download from your link and for some reason the file will not extract. However, I noticed that your image file is named exactly as the image file linked in the OP to this thread. Are they one in the same?
sivarticus85 said:
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Click to expand...
Click to collapse
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
thenestor said:
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
Good catch! I have fixed the original post
Stanleywinthrop said:
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
Click to expand...
Click to collapse
I've updated the original post to make this clearer.
anyone able to root this new OTA?
CF auto root was working on every previous OTA from 4.4 to 5.0 and 5.1 but now causes boot loops. I am able to TWRP back to the unrooted build to get me out of the bootloops.
leffer said:
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
Click to expand...
Click to collapse
Thanks! And no, the name is normal. The OTA filename always states the version you need to be on to install it, not the version that it contains.
this is a thread for brainstorming and testing an upgrade path from 4.4.4 stock to 5.1 stock that retains root (that is all).
i'm assuming trying to flash a pre-rooted 5.1 system .img (if ever becomes available) using mofo is not going to work unless something changes [ie, how would you get the new modem, kernel, etc?]
idea 1:
a. use mofo to flash xt1254.system.21.44.12.quark_verizon.rooted.ext4.img (stock 4.4.4 with root baked in, no other system modifications).
b. next, manually flash the android 5.1 OTA patch .zip (whenever its public, or if any soak members are willing to test now)
c. question for a willing tester (realize once you go 5.1 you cant go back and might not ever see root again), does root remain or is it lost during the upgrade?
idea 2:
a. if the above system upgrade from 4.4.4 to 5.1 does work but root is lost (and there is no "OTA Keeper" type app in the image), could we bake in a 'backup' of root and a 'restore' app into the xt1254.system.21.44.12.quark_verizon.rooted.ext4.img and then could we again upgrade to 5.1 and 'restore' root on a temporary basis (better than never having root).
b. of course this is not ideal, but if that does work, then maybe someone could also bake into the base 4.4.4 image an app that auto-restores root quickly on every boot, for a virtual perm temporary root solution.
idea 3:
put your thinking cap on and please provide.
Idea 1 is a no go
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
well, bummer, thanks. sounds like we'll have to skip to idea 3.
but to confirm, does the 5.1 OTA patch not manually flash over a clean xt1254.system.21.44.12.quark_verizon.rooted.ext4.img ? OR it does, but root lost?
Doesn't flash at all
Has someone tried using Mofo that has taken the new update? I saw that the 2nd gen Moto X works with Mofo & 5.0 Lollipop, but not sure about 5.1.
I'm kind of confused. Can't we just modify the stock 5.1 image to have root? Or does mofo refuse to flash it?
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Can you install the update on a rooted phone? Or do I need to go back to stock?
janitorjohnson said:
Can you install the update on a rooted phone? Or do I need to go back to stock?
Click to expand...
Click to collapse
back to stock. it will fail if rooted
Does anyone have a completely stock system image ?
Anyone tried kingroot?
Can't get back to stock for some reason ..rooted .. Can some one help me
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
hotrodwinston said:
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
Click to expand...
Click to collapse
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
johnbravado said:
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
Click to expand...
Click to collapse
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
I would think you would just look at the SuperSU.zip script file and then insert all required files as described in the script.
https://su.chainfire.eu
Tomsgt said:
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Click to expand...
Click to collapse
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
PILLMUZIK3600 said:
Does anyone have a completely stock system image ?
Click to expand...
Click to collapse
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
does mofo flash the modem/kernel, data, etc ? or is it only going to flash the system partition?
chip! said:
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
mofo already said its not going to work on 5.1.. so we know you can only use mofo with droid turbo when the phone is still on 4.4.4. and i dont see how you can go 4.4.4 -> 5.1 from a 'system' partition .img alone. someone feel free to set the record straight, but it would be surprised if modem, kernel, etc are embedded on system partition.
Click to expand...
Click to collapse
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Faith age, boys.
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Sweet can't wait
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app