Related
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
ponso said:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
Click to expand...
Click to collapse
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Thank you. I went with the 2nd option and my phone is running great with the update.
Although it took awhile to reconfigure everything back.
mjones73 said:
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Click to expand...
Click to collapse
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/
Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,
No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ
Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.
torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.
Hi,
I've got a Moto X 1st gen, XT1052 GB Retail.
Ages ago I rooted it on 4.4.4 using TWRP Ver. 2.6.3.1.
I updated to 5.1 (loading the zip thorugh TWRP recovery, of course not the OTA). Now i get update notifications all the time, that I can't install OTA and that i can't find to install through TWRP.
TWRP is outdated and refuses to update and generally the phone in its current state is a bit of a mess.
So I have two options really:
- update to the latest TWRP and get the required updates for my Android
- update TWRP and go custom ROM
- go back to stock.
I really think the best course of action would be to go full on stock and then, when i have more time and gumption to do it, go full custom with a fresh TWRP install.
But if someone could point me in the direction of the stock recovery, i'd appreciate that. I can't find it on the Motorola site, here or anything hat Google throws at me when i search. I'm either not using the right phrases or overlooking something.
Your help is greatly appreciated!
Thanks!
Cloudhopper said:
Hi,
I've got a Moto X 1st gen, XT1052 GB Retail.
Ages ago I rooted it on 4.4.4 using TWRP Ver. 2.6.3.1.
I updated to 5.1 (loading the zip thorugh TWRP recovery, of course not the OTA). Now i get update notifications all the time, that I can't install OTA and that i can't find to install through TWRP.
TWRP is outdated and refuses to update and generally the phone in its current state is a bit of a mess.
So I have two options really:
- update to the latest TWRP and get the required updates for my Android
- update TWRP and go custom ROM
- go back to stock.
I really think the best course of action would be to go full on stock and then, when i have more time and gumption to do it, go full custom with a fresh TWRP install.
But if someone could point me in the direction of the stock recovery, i'd appreciate that. I can't find it on the Motorola site, here or anything hat Google throws at me when i search. I'm either not using the right phrases or overlooking something.
Your help is greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Update your TWRP first to unofficial 3.0.2* or 3.0.3 (the latter have material design theme and avoid latest 3.1.0), then I suggest to try a ROM + Gapps first.
If you unhappy with custom ROMs, here on XDA, in Dev section (https://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843), there's all stock 5.1 official firmware.
Remember you risk to brick if you try to return on stock KitKat After Lollipop update.
*If you use this remember to set in settings "use rm -fr instead of formatting" to avoid slow wipe because ext4
No news?
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
ravious said:
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
Click to expand...
Click to collapse
I'm not sure how an update installed when you were rooted, that normally doesn't happen. I was going to make a flashable rom today or tomorrow, but if your modem was updated, I'm not sure you'll get service with the older firmware. You may need to change the modem back to the previous version. What firmware version and security patch does it say in settings after the update? You might be better off just flashing the stock firmware with fastboot or RSDlite.
Edit: did you try wiping data of the apps that are giving you trouble?
Sent from my Moto E (4) Plus using XDA Labs
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
shezzy83 said:
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
Click to expand...
Click to collapse
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
shezzy83 said:
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
Click to expand...
Click to collapse
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
GetOffMyLawn&!+¢#{$ said:
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
So you're making a flash-able to give us the update that we can't get now because we have twrp?
shezzy83 said:
So you're making a flash-able to give us the update that we can't get now because we have twrp?
Click to expand...
Click to collapse
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
shezzy83 said:
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
Click to expand...
Click to collapse
Yes it will. Who said you can't restore the stock recovery? You need to restore full stock with fastboot or RSDlite to take the update.
Sent from my Moto E (4) Plus using XDA Labs
I'm uploading a stock rom now. I'll upload flashable of the modem and eom partitions also. Then I'll update and make a stock rom from the newer firmware. I should have links for all of it before the day is over. Watch for a new thread.
Edit: the rom I'm uploading now is untouched for Boost. I'll do Sprint and the retail model next, then I'll make some that are rooted/debloated. I'll need testers for Sprint and retail versions.
Edit-2:
Here's Boost untouched stock. I haven't tested it yet, I'm waiting for my backup to finish to test it now.
Edit-3;
Didn't flash, I think maybe the mount points aren't right. it failed to mount /system. I'll fix it and reupload it.
Sent from my Moto E (4) Plus using XDA Labs
I got a rom working. I tried making it sparse.dat format but it wouldn't provision data services so I tried set metadata and it works fine. Only problem is the zip is 1.9GB. I'll do what I can to decrease the size so everyone doesn't have to use that much data to download it. I'll post a link as soon as I get it shrunk down and uploaded.
Sent from my Moto E (4) Plus using XDA Labs
Here's Boost Mobile stock:
https://www.androidfilehost.com/?fid=745849072291697789
It's not rooted or modified in any way. You'll have to flash a no dmverity zip or just Magisk or it won't boot unless you format data. There's some newer zips here:
https://build.nethunter.com/android-tools/
Or, you can flash the f2fs patched kernel recently posted. I'll make debloated and patched kernel versions when I have time.
Sent from my Moto E (4) Plus using XDA Labs
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Sent from my Moto E (4) Plus using XDA Labs
Y'all might be seeing me soon, if/whwn I can get a device
GetOffMyLawn&!+¢#{$ said:
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Click to expand...
Click to collapse
Does the updated boost version have that f2fs kernel included?
xhan145 said:
Does the updated boost version have that f2fs kernel included?
Click to expand...
Click to collapse
No, it is completely untouched. I was planning on building my own kernel.
Sent from my Moto E (4) Plus using XDA Labs
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
lwang9 said:
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
Click to expand...
Click to collapse
I just got this phone and unlocked bootloader no problem did on Motorola website
skullkid383 said:
I just got this phone and unlocked bootloader no problem did on Motorola website
Click to expand...
Click to collapse
Would it work with Walmart's prepaid xt1774?