Related
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??
williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?
I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD
This happened to me too, though I have the wifi-only version. So it's not just the radio.
I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !
rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,
spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.
khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.
OFFICIAL FXZ IS AVAILABLE: http://sbf.droid-developers.org/phone.php?device=0
I can verify, I was about to get a refurb from Verizon and this was the only thing could unbrick it.
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
icase81 said:
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
Click to expand...
Click to collapse
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Q9Nap said:
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Click to expand...
Click to collapse
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
icase81 said:
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
Click to expand...
Click to collapse
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Q9Nap said:
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Click to expand...
Click to collapse
Cache definitely didn't fix it. Tried that last night. I spent 40 minutes redownloading and setting up apps, so wiping user data again wouldn't be fun. I'll check it out in a few minutes and report back.
EDIT: Nope, cache and userdata wipe did not fix it. Oh well, I'll just wait until the fxz image is out for 4.4.2 and try that then.
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
I would like to know this as well!
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
your question really belongs in the q & a section...
as the op states, this recovery is for use only if you have bricked while attempting to apply the update.
to apply the update successfully, you need to have an unmodified system. so if you've made any changes to system files, you should start from the beginning to get to unmodified, rooted 4.4; then apply the update.
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Q9Nap said:
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Click to expand...
Click to collapse
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
icase81 said:
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
Click to expand...
Click to collapse
sure, np. glad you got it working. it's unfortunate that locked users lose root with the 4.4.2 build though.
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
wmjchoi said:
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
Click to expand...
Click to collapse
I'm not familiar with that particular toolkit, but I'm assuming it flashed gpt and motoboot to the 4.4.2 version (I'm also hoping you meant to type 4.4.2, otherwise, flashing an old version might be your problem) both of which you shouldn't try to downgrade. I would recommend re-flashing all of 4.4.2 from the sbf (which is hopefully what that toolkit does -- you should probably post in that thread for this)
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
leffer said:
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
Click to expand...
Click to collapse
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
KidJoe said:
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
Click to expand...
Click to collapse
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Would I use the T-Mobile fxz to fastboot flash a Dev Ed. GSM on T-Mobile plan?
leffer said:
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Click to expand...
Click to collapse
I might be in the same boat, any help would be appreciated. I was rooted pre-4.4.2, and took the VZW OTA, root survived... everything has been good. Now when I try a factory reset it, it boots to FastBoot mode and Recovery option just reboots the phone.
It does say: Partition (recovery) Security Version Downgraded
Fastboot Reason: Boot Failure
Phone can reboot into Android and works just fine. Should I flash the entire 4.4.2 image or is there a glaring red flag that I'm missing like trying 4.2.2 or 4.4 first?
Thanks all!
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
*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
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
thank you! worked great!
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.
spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Is something up with the OP or is it just my XDA app causing it to show like this..
aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update