This is a pretty specific question and i'm not sure this is the correct place to ask this but i recently installed the stock rom (Via Zip) on this thread: http://forum.xda-developers.com/showthread.php?t=2527806 . I flashed just the rom NOT including the bootloader (Because i don't know what it does) and the .97 radio because there seems to be some issues with it. Now, everything is working perfectly as it did before. What i'm wondering is after today's random new 4.4 factory image and ota update from Google (I think its krt16s); i know they are probably going to compile a flashable zip, and if they do what exactly do i need to do?
I'm extremely weary when i do these kind of things, the last time i flashed any sort of rom was on my OG RAZR. Would i have to install that new bootloader? (Also what exactly does it do) And would i have to wipe?
I can make the radio judgement on my own but i'm just not entirely sure.
If anyone could answer my questions that would be wonderful, i'm also sorry for posting this here, i'm not allowed to post in that thread because i'm "new" to the site.
Thanks!
you dont have to sorry as you are in the right section for asking questions.
You can either wait for a day or two for someone to post a flashable zip file. If someone do post it; all you have to do is copy it to your phone. Reboot to recovery mode; make sure you have cwm recovery installed. From there choose "install zip" > install zip from sdcard, choose the flashable zip. Once it finishes installing, clear cache partition and reboot. You will not lose anything in the phone.
If you want to install the new krt16s stock update. First, copy all of your files (pictures/music/data etc...) to your computer. This will wipeout everything. Download the image file. Open it with winrar or 7zip. Extract all the files to a folder. Connect your phone to the computer and reboot it to bootloader. Run the "flash-all.bat" file from the extracted files. Wait for it to finish. It will update everything (kernel, bootloader and the new 4.4)
You should know what something is before flashing them wildly, that's the easiest way for people to brick their phone by flashing something incompatible with their devices. Bootloader is the main program that boot first when you turn on to phone to make selftest and boot normally into the operating system kernel, with Nexus you can use it boot into recovery and flash images to partitions as well. It's very recommended to update it along with new Android version or you may run into issues. You should already know this since you had to access the bootloader screen to boot into the CWM recovery.
Stick with using CWM for now and flash the flashable zips. Just make a full backup of your device you can always restore it later. Just know that unless you flash radio separately (aka baseband), roms generally and should not come prepackaged with the baseband, so it is not affected when you flash a different rom, you have to upgrade it manually.
When you flash a new Android version, usually its recommended to do a factory reset in your recovery to avoid issues.
Installing factory image takes a few more steps and required using fastboot, but if you want to check the link in my sig. Also I recommend switching to TWRP recovery, but that's just me.
badboy47 said:
you dont have to sorry as you are in the right section for asking questions.
You can either wait for a day or two for someone to post a flashable zip file. If someone do post it; all you have to do is copy it to your phone. Reboot to recovery mode; make sure you have cwm recovery installed. From there choose "install zip" > install zip from sdcard, choose the flashable zip. Once it finishes installing, clear cache partition and reboot. You will not lose anything in the phone.
If you want to install the new krt16s stock update. First, copy all of your files (pictures/music/data etc...) to your computer. This will wipeout everything. Download the image file. Open it with winrar or 7zip. Extract all the files to a folder. Connect your phone to the computer and reboot it to bootloader. Run the "flash-all.bat" file from the extracted files. Wait for it to finish. It will update everything (kernel, bootloader and the new 4.4)
Click to expand...
Click to collapse
I see, me personally, I'm not very fond of using adb; I haven't used it at all prior to yesterday. I may try this out, but should someone post the new kernel, boot loader, 4.4 and radios would that be the same as flashing the factory image?
This probably seems like a really stupid question but I wouldn't be smart to try to download the ota directly from the phone (via check for updates) would it?
joshvader8 said:
I see, me personally, I'm not very fond of using adb; I haven't used it at all prior to yesterday. I may try this out, but should someone post the new kernel, boot loader, 4.4 and radios would that be the same as flashing the factory image?
This probably seems like a really stupid question but I wouldn't be smart to try to download the ota directly from the phone (via check for updates) would it?
Click to expand...
Click to collapse
You need to learn to use adb and fastboot if you want to be able to do advance things with the phones, or just avoid flashing too much, because once you run into trouble (especially due to using toolkits), you will not know how to recover your device.
If you want your device to be stock and able to receive OTA updates, in addition you also need your stock rom to be an "odexed" version, some roms are "deodexed" which will not receive OTA. You also need to have stock recovery, which CWM isn't.
eksasol said:
You need to learn to use adb and fastboot if you want to be able to do advance things with the phones, or just avoid flashing too much, because once you run into trouble (especially due to using toolkits), you will not know how to recover your device.
If you want your device to be stock and able to receive OTA updates, in addition you also need your stock rom to be an "odexed" version, some roms are "deodexed" which will not receive OTA. You also need to have stock recovery, which CWM isn't.
Click to expand...
Click to collapse
Thank you! One more question, let's say I revert back to my nandroid back up. I backed my ROM up on Android 4.3 rooted and unlocked with CWM. If I flashed the 4.4 factory i image what exactly would happen? Would I boot into 4.4 absolutely stock? Or would I end up with 4.4 unlocked etc...?
Thank you for the help I really appreciate it. ☺
joshvader8 said:
Thank you! One more question, let's say I revert back to my nandroid back up. I backed my ROM up on Android 4.3 rooted and unlocked with CWM. If I flashed the 4.4 factory i image what exactly would happen? Would I boot into 4.4 absolutely stock? Or would I end up with 4.4 unlocked etc...?
Thank you for the help I really appreciate it. ☺
Click to expand...
Click to collapse
When you flash factory image (using fastboot method), it will wipe your entire device and all user data, and you will boot into stock. Except if you do it manually you can prevent datas from wiping, follow these steps and pay attention to the red texts.
Sometimes apps data from older version can cause issues with newer version though, so a clean install is always best.
But if you have custom recovery, you can flashable stock roms, such as this one by fireb33, it's essentially the same as stock. Get the "odexed" version which is required to get OTA updates. Some peolpe say they can get OTA with custom recovery, but I have never tried that. The safest bet is to use fastboot to restore to stock recovery. You could also use custom recovery to flash OTA update packages to update versions that way.
As for backing up, people tends to call the backup "nandroids". After you do backup, if you're doing something that required the device to be wiped, you need to copy the backup to your pc. The CWM nandroids are usually located in 'clockworkmod' folder, but if you don't see it, search in "/data/media". I do not use CWM so I don't know what it allows you to back up, but generally "boot" (which is the kernel), system, and data partitions. It will not restore everything to stock such as your radio (baseband) or recovery.
I highly recommend switching to TWRP recovery, it will make flashing a lot easier.
Related
hi there, so my question is really simple.
I know how to flash a recovery .img via terminal (on my mac), but just can't seem to be able to permanently flash the .zip downloaded via ROM Manager. I reboot my phone in recovery, apply update from sdcard, new recovery replaces older one just for the time being because the next time I reboot my phone in recovery, the new recovery is just gone I am stuck with the older one.... the only way I have been able to update my recovery so far is by flashing it via terminal, I mean the update.zip must be there for a reason.... if I could just flash it without having to use the terminal, it'd be brilliant
So anyone knows how to permanently flash the .zip downloaded via ROM Manager without logging on to a terminal on a computer?
.Zips from ROM Manager are supposed to be 'temporary' ones. Only IMG files can be flashed permanently.
Have a look at the following thread. Should help you out!
http://forum.xda-developers.com/showthread.php?t=1245018
Thanks
So I guess I am just gonna have to download and flash the .img file every time I want to permanently flash a recovery image.
Yes, but I personally don't think that Recoveries is one thing that needs to be updated on a very frequent basis. (I am still on 3.2.0.0)
I agree, not something I'd upgrade on a regular basis. I only updated in order to get rid of the off-mode charging bug which I had in my old recovery and had been annoying me for months! Flashed with Unrevoked, now everything's working perfectly.
thanks for this information
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
1. Spot on, reading the update script it doesn't look for additional files. I said otherwise previously, my bad.
2. Also true. Updater script does no hash check on the two recovery files either, so even if you deleted /system/etc/install-recovery.sh it will still be fine. My bad also.
3. Spot on.
Thanks for this writeup albundy :good:
So I was running ics roms well before they came to my ns4g... I didn't bother with ota since there was already a port available almost immediately... that fixed most of the bugs we experienced with pre-ota ports...
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Sent from my Nexus S 4G using Tapatalk 2
ioplkj13 said:
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yes, but the question is when that will happen. Google pushes updates in waves, it could take weeks before it gets pushed to your phone.
And all those people already getting anxious now how to prepare their phone for ota-push don't strike me as the waiting kind... in fact, it's really silly making all that fuzz now, still another 2 weeks before 4.1 gets released.
the1dynasty said:
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Click to expand...
Click to collapse
So far the NS4G always had to wait to get an official update, Sprint taking it's time. The first OTA's will probably be for 9020T/9023 again, different radio. So unless you are willing to wait, you need a custom-zip anyway, don't use the dl-link from Google that will be floating around in 2 weeks.
But to answer your question:
First OTA's have always been incremental updates, so one needed to be on prior stock-rom to apply it. (In this case: 4.0.4 stock -> 4.1 update)
Of course they could change it this time and release everything at once (full rom, factory images, all models), but I heavily doubt it.
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
grigri444 said:
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
Click to expand...
Click to collapse
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
ac17 said:
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
Click to expand...
Click to collapse
I have Titanium backup pro. But which method is the wiser?
OTA and reroot or update zip and re-install all apps?
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
caliban2 said:
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
Click to expand...
Click to collapse
Because, i will make a wipe data in order to get a clean install of the new ROM. In our case the 4.1 stock.
you don't have to wipe sdcard to get a clean install... but go ahead, it won't do any harm.
will I get the OTA?
So I've got cyanogen mod 9 on my nexus s with Clockwork mod bootloader will I get the OTA update? if not what changes do I have change back? ps I would rather not format the Internal USB drive.
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
JavaJunkay said:
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
Click to expand...
Click to collapse
Too many steps. From what i have learned, download the JB flashable zip (probably it will be available the same day when ota is pushed) put to sdcard, make a wipe data and flash through cwm. The ics zip was releashed the same day, was root, busybox and superuser.
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Can you have a custom kernel ??
Sent from my Nexus S using xda app-developers app
snandlal said:
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Click to expand...
Click to collapse
Every stock zip contains a directory called "recovery". Delete it before flashing and you don't have to care about cwm getting overwritten.
btw are really needed only stock rom and stock kernel???
what about the 'ota survival' option present in superuser?
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
I suspect in some of the "misinformation" you have missed the distinction between preparing the phone for automatically receiving and automatically installing properly an actual Over the Air update from Google, vs. preparing for you actually installing an OTA file, or some form of new Jelly Bean. You don't explicitly make this distinction or don't really clearly say which you are discussing. The title of your post points one direction, but the contents the other. Or maybe the "rant" style of writing just confuses people more, including me.
Hi, I am not too sure if I posted this in the right place or not but please let me know if it is posted in the wrong place. I am actually relatively new towards rooting of an android device so i need to clear my doubts.
I used Wugfresh toolkit to root my Nexus 10. The toolkit also have an option to install TWRP. But the version of TWRP is not the most updated one. So, can I just download the latest one and flash it or i need to remove the current one before I can update the version.
Also, I am interested in flashing a custom ROM. But my question is if a new stock firmware is out, how am i going to update to the latest stock firmware when I am in a custom ROM.
Please let me know if you don't understand my question. I will try my best to explain further and also thank you in advance.
iOrdinary said:
Hi, I am not too sure if I posted this in the right place or not but please let me know if it is posted in the wrong place. I am actually relatively new towards rooting of an android device so i need to clear my doubts.
I used Wugfresh toolkit to root my Nexus 10. The toolkit also have an option to install TWRP. But the version of TWRP is not the most updated one. So, can I just download the latest one and flash it or i need to remove the current one before I can update the version.
Also, I am interested in flashing a custom ROM. But my question is if a new stock firmware is out, how am i going to update to the latest stock firmware when I am in a custom ROM.
Please let me know if you don't understand my question. I will try my best to explain further and also thank you in advance.
Click to expand...
Click to collapse
TWRP typically recommends installing and updating their recovery via Goo's app thing, but if you know where to look (openrecovery on goo + manta), you can get the .img and then flash it with fastboot. I usually do fastboot erase recovery and then fastboot flash boot TWRP-IMAGE.img. But if you don't feel too comfortable with fastboot, then Goo's program should take care of it I think.
If you want to try the latest stock when you're using a custom ROM, you'll need to flash the latest factory image from Google to go back stock, and then update it (unless the factory image is updated to the latest, which doesn't usually happen till days later). Just want to make sure you backup anything important.
espionage724 said:
TWRP typically recommends installing and updating their recovery via Goo's app thing, but if you know where to look (openrecovery on goo + manta), you can get the .img and then flash it with fastboot. I usually do fastboot erase recovery and then fastboot flash boot TWRP-IMAGE.img. But if you don't feel too comfortable with fastboot, then Goo's program should take care of it I think.
If you want to try the latest stock when you're using a custom ROM, you'll need to flash the latest factory image from Google to go back stock, and then update it (unless the factory image is updated to the latest, which doesn't usually happen till days later). Just want to make sure you backup anything important.
Click to expand...
Click to collapse
So, for TWRP, it means that I can restore the stock recovery before I flash the TWRP img right? Because I am using the Wugfresh toolkit to run all these fashboot commands and they only have the options to either flash a custom recovery or to restore the stock recovery.
As for the custom ROMs, every time I flash a ROM, all my stuff in my Nexus 10 will be gone right? For example my game progress etc. Because if I were to backup, I will make a nandroid backup which means every single thing in my nexus. So, correct me if I am wrong. Every time I flash a ROM, my nexus will be back to a clean state right?
Thank you in advance for your answers. ^^
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Ohmster said:
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Click to expand...
Click to collapse
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
nypeach said:
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
Click to expand...
Click to collapse
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
Do you think it would work if I did a Full Unroot using SuperSU and then uninstalled it using TiBu. Then flashed stock recovery using the restore to stock tool. So at that point I would have unrooted, removed SuperSu, and flashed back the stock recovery image. Do you think this would do the trick, or is it just best to completely flash the entire device using the restore to stock tool in full. I can recover from a soft brick but don't want a complete brick. Do you think my method is worth a try and that it wouldn't cause a complete brick condition? I would like to not have to reset my phone completely, but will if that is the only best way to get onto MM. Thanks.
nypeach said:
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
Click to expand...
Click to collapse
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Ohmster said:
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Click to expand...
Click to collapse
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
nypeach said:
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
Click to expand...
Click to collapse
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
robn30 said:
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
Click to expand...
Click to collapse
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
That boot img is for style only, not for pure. There is another called boot_root_mm_clark_retus.zip
Search for that file, it's the one you need for Supersu 2.5.2
You can use either supersu 252 of 256. I used 252 and have had no problems. If you have flashed TWRP, just put the supersu of your choice and the boot_root.zip files on you phone and flash with TWRP.
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
IGNORE ME My Bad.... Back at 5.1.1 and staying here for a while Thanks again for your awesome support. I really appreciate it.
nypeach said:
Hi OldBaldy. Sorry I'm still having a tough time. As mentioned, I got back to 5.1.1 per the above process. I read your latest note and flashed the latest twrp (2.8.7.1) and took the MM OTA. It's now flashing the "teamwin" screen over and over. Should I be patient or bail? Thanks again for your patience and help!!!
Click to expand...
Click to collapse
You have to take the OTA BEFORE you flash TWRP. What you need to do now is get back into fastboot and flash the stock recovery img from the 5.1.1 factory image. Then reboot into system and take the OTA. After it installs, then follow the above instructions.
Sent from my XT1575 using Tapatalk
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Ohmster said:
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Click to expand...
Click to collapse
Yup, I realized that plus someone else informed me that wasn't the one. I got her all taken care of and she is up and running smooth as can be. The battery on MM is really good. I'm impressed. I also wrote up a huge how to on the whole process and posted it. Should contain all the necessary steps in one place now. It gets a bit crazy having to dig all over the place to gather all that is needed. These threads get quite large and finding stuff gets more difficult as the days go by.
Sent from my XT1575 using Tapatalk