Related
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.
RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/
Nexus 6 Rooted and Unlocked and now new OTA – confused
Dear Friends,
I am currently having Nexus 6 with Build Number MRA58N which is rooted unlocked. Last time I had to format Nexus 6 just to update to this build. The nexus toolkit was somehow not working for me.
Now I see again that there is an OTA called android 6.0.1
image hosting
Now I tried using Wugfresh Toolkit first to take android backup but it fails and shows as shown in screenshot that currently there is no modified boot.img available for MRA58N.
free photo upload
I really don’t want to flash factory image bcz it will overwrite everything and erase all.
Kindly help.
Reformatting and again restoring is too much of pain.
Google is your friend, you should Google something like that before creating a post, but anyway you can't take an Ota on a rooted device, if you want the Ota, flash system.img of the current rom, and then take the Ota
I did try and read many posts but still could not conclude anything for sure. Yes I agree OTA cannot be taken on rooted device and thats why my question. you suggested flashing system.img of current rom. Now thats where confusion starts as many posts mention that one needs to be 100percent stock. Many people recommended complete wipe and yet many posed lot of questions because of marshmallow special kernel rom issues which is beyond my technical understanding.
Hence I summarized to pose my query to get considered opinion and guidance. Your response is helpful but am not able to fully comprehend.
Hence request for more guidance.
Really appreciate if some experts would kindly reply to my query and guide me. It will be very helpful as I really want to update but really scared of messing up. Kindly respond.
http://www.droidviews.com/how-to-install-ota-updates-on-rooted-nexus-6/
also watch a few youtube vid's - it is a road well traveled.
i.e.
- Flash the system image for build that you are currently running.
- sideload the update
be patient and don't even think of interrupting the process.
Read the stickies and learn something, toolkits and no skills spell disaster.
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit. Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Now i am stuck at this ADB step. Kindly help Pls.
Something got messed up in the process. You can try to individually flash your corresponding boot.img from your version via fastboot. You can download and extract that boot.img from Google's stock images.
This is just me speaking my mind but why people go through the trouble to root just to keep the stock ROM is beyond me.
Given your situation you are better off wiping/formatting and reflashing a new ROM stock (hopefully not) or custom.
Offering this as a comment, not an answer. I agree with mikeprius - in your position I would bite the bullet, download the latest MMB29K image, and run flash-all to wipe and set your device to the newest version - or perhaps even wait for the one which may arrive within a few days. If you leave the device on stock, unrooted, you'll be able to apply OTAs without any problem at all.
For curiosity, why do you even need root? As you've discovered, it opens up cans of worms that can be more trouble than they're worth unless there's an *overwhelming* necessity for root.
looks like failed with verification of /boot
reflash these for build you are currently on - I've done this without losing data:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
fastboot reboot-bootloader
it''ll probably pop up with the dead android -- don't reboot. Press
power button+vol up
you may have have to do a bunch of times -- eventually it go to the menu to allow you sideload the update.
Why are people so fixated on installing an old ROM and then sideloading the update when the obvious answer is to simply install the components of the latest ROM? I get the desire to retain the existing data, but to my eyes it looks as if the phone is now in an unstable and unreliable state and a complete refresh is the best solution.
it's a choice and there is experience gained in the exercise - and the existing data thing is big deal to many.
Android newbie trying to do a 6.20.651.3 update on a HTC One M8 Sprint variant. I’ve tried the direct download method, I get to 1.06gb, download successful, verified, unzipping update then reboots and flashes up some errors and goes into TWRP recovery.
I have also had a few goes at it from Windows running RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.EXE that fails as well with an error 155: unknown error: cannot update Android phone, please get the correct ROM update utility and try again or just hangs there on 0% for 30 mins.
Device has s-off and is rooted - at least Root Checker app says it is but it can also report not properly installed. I've just tried the direct download method once more having used the Root Check app to confirm that it is rooted but with same result.
Can anyone give me a few pointers in terms of what I have to do to get this to work. Help much appreciated.
You won't be able to take the OTA update with TWRP installed. As for running the latest RUU, you have to have the latest firmware installed first. You'll also need the latest version of TWRP if you want to flash a MM ROM. Check OMJ's RUU thread in Android Development for more info.
An alternative to taking the OTA or running the RUU would be to update your firmware & TWRP recovery, then flash a stock rooted MM ROM.
Thanks for your response. It has given me some understanding of the different types of update. I checked my TWRP and it is 2.8.7.0, which is the latest, and tried a firmware update using the firmware update utility from here
http://forum.xda-developers.com/showthread.php?t=2729173
and downloaded one of the non-Harman extracted firmware versions, renamed to rom.zip, put it in required folder and ran ARUWizard.exe and it is stuck on updating (0/1) sending, has been for 15 mins so I can assume that this will not work.
Any ideas? There are four variants: full, full signed, with / without recovery, boot. Am I running the wrong firmware?
Download the modified MM firmware (no boot or recovery) and place it on your external SD card and rename the file 0P6BIMG.zip (make sure the file doesn't have an extra .zip extension on the end). Reboot to the boot loader and update your firmware when prompted. As for TWRP, there is a newer version available. Check the last couple of pages of the TWRP thread in Original Development. It's version 2.8.9.0.
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
mp
check your mp
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Download the file linked below. Once you've done that, click the link in my signature for the M8 hboot guide. Scroll down to the section on firmware updates (it's in the very first post) and follow my instructions in my guide to update your firmware.
https://www.androidfilehost.com/?fid=24391638059059964
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
atomclock said:
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
Click to expand...
Click to collapse
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
madbat99 said:
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
Click to expand...
Click to collapse
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
atomclock said:
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
Click to expand...
Click to collapse
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
madbat99 said:
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
Click to expand...
Click to collapse
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
atomclock said:
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
Click to expand...
Click to collapse
That thread literally says install the stock firmware. You have to wait for the entire firmware for the new build to be released. no one is extracting anything from any update package. They are just using the full firmware package in that thread. You just have to wait for the full firmware to be posted on mirrors.lollinet.com the November patch for my G6 play was just posted there yesterday. that's why I asked which version of the G6 you have I will link you to the full firmware.
Or, You just fastboot flash stock, take the update, fastboot TWRP, use TWRP to flash magisk. No data loss, easy peasy.
the only difference in those two ways is taking the update after you flash stock or flashing stock firmware including the update. Either way you have to root your device again.
You can even flash stock with RSDlite using service file.xml instead of flashfile.xml
the file they are flashing with fastboot in that thread is the stock firmware. Just the newer one.
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
GotHeart said:
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
Click to expand...
Click to collapse
The question is can i use different software channel for my G6? Example 1925-6 to 1925-7 to gain particular service carrier signal
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.