Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers
AFAIK no flashing of ROM is necessary as long as you're on stock. What you need is a stock recovery. I reckon you flash that ASAP.
Also, you might need to look into your system apps and make sure that you haven't deleted/disabled or converted to user apps.
Besides these steps, you'll be fine and will be able to update.
Androphilius said:
Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers
Click to expand...
Click to collapse
You have to install stock firmware and re-lock your bootloader. The guide to install stock firmware is on the general sub-forum and should be here.
I suggest using SMS Backup & Restore to backup your SMS. However, I recommend waiting until root is out to flash Android L. Then you can use Titanium Backup to restore your user apps & data.
I'm running L myself so I have to patiently wait for root. Good news though! The Moto X got a root solution by chainfire for Android L already. This means we could get root soon for Moto G.
Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself
Androphilius said:
Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself
Click to expand...
Click to collapse
Nope, no re locking required. Just do the samsung needful. I had one of its ****ty mobile too. So hi5 there.
Anyways, I don't understand why are doing this stuff. Most probably a flashable zip would be uploaded on XDA the same day or max the next day. Just chillax and wait for the good news to arrive, which I hope is any day now
P.S Oh and also make sure that you don't lock your bootloader at all. Because then you wouldn't be able to unlock it, at least not right now, hence you wouldn't be able to root.
Related
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Toys Samurai said:
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
Click to expand...
Click to collapse
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
samwathegreat said:
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
Click to expand...
Click to collapse
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
SR3TLAW said:
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
Click to expand...
Click to collapse
Flashing Krypton is possible from Custom recovery, unlike an OTA / FXZ. In addition, I believe that Krypton only includes the /system and /boot partitions. This is why he states that you need to be on 4.4.2+ first.
The FXZ overwrites all relevant partitions with new data.
Vekhez said:
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Click to expand...
Click to collapse
Unfortunately the X is nothing like the N5.
KJ said:
Unfortunately the X is nothing like the N5.
Click to expand...
Click to collapse
Yeah, I've found that out as of recently, they are very different devices, very very different indeed
Hi,
My HTC One is rooted and Unlocked. I've just received the OTA upgrade but didn't install it yet.
I was unsure to do it or not.
What do you suggest? I've read FAQ n. 24 but still no answer to my question.
Relock and unroot.
If you're going to attempt to take that OTA (which I honestly wouldn't do as you are), you should unroot your phone and relock your bootloader.
Your best bet, since the OTA of this phone has been made into a rooted stock rom, is to simply download that and install. You'll get everything and you'll still be rooted and unlocked.
Hi!
thank you for your reply @MFOsaka.
I would actually chose the second solution. Is the update available on the HTC official website? Can I install through the Recovery as usual for the .zip files? Does it erase something on my phone?
fbcyborg said:
Hi!
thank you for your reply @MFOsaka.
I would actually chose the second solution. Is the update available on the HTC official website? Can I install through the Recovery as usual for the .zip files? Does it erase something on my phone?
Click to expand...
Click to collapse
Installing a new ROM inherently requires that you erase most things on your phone (TWRPs default swipe to wipe works great). You will lose all your settings, apps, and app data. However, your "media" will remain untouched (photos, Titanium backup files, music).
I would recommend the 4.4.3 stock ROM if you want to be on the bleeding edge of things, but that ROM isn't "stock" in the conventional sense. Its a port. Sprint never actually got that update, and certain things, such as the HTC Eye app, aren't compatible with the M7 yet.
If you want something stable, I recommended the 4.4.2 ROM, which is the latest available software for the m7spr.
There's more development for the 4.4.3, though, so choose your priorities.
Both of these ROMs are available in the Android development section as flashable zips.
Have fun, and remember to nandroid backup!
Forgive me if this has been asked before. I did search, but I couldn't seem to find an answer to this.
I have a dev edition model. I really want to root, but have been holding off because there are bugs with the current build of Lollipop and I'm kind of hoping Moto will release a 5.02 update soon to kill the memory leak and other issues. That being said, I have really been itching for root.
If I did root, what would I have to do to this phone to update it to the new version? Would I have to completely return to stock and wipe? Or could I ADB sideload? Seems like I was reading that you can't update at all when you're rooted, even if you disable root.
Without any idea how much longer it'll be before the next update, I'm finding it harder and harder to hold off on root, but I don't want to go through hell to get it back to stock and update it.
Thanks for any help and sorry if this has already been asked.
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
diggitydogg said:
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
Click to expand...
Click to collapse
Thanks for the reply.
Most of the time, that's true. I have updated a lot of phones by simply unrooting, applying the update, and rooting again, or using ADB sideload and then just rooting. But from what I have been reading about the Moto X 2014, you have to completely restore it back to stock before doing anything, even if you just use the temp boot method to root.
Is that wrong? I can't seem to find any info that confirms either way.
I've installed custom recovery, how can I reverse it and install the original recovery for update?
One advantage of root is you'll have Titanium Backup, so even if you do have to do a full wipe before applying the update, you could just update it and restore everything back quickly using TiBu. With lollipop, apparently the update file checks for the entire system checksum as a whole instead of each file so any slight modification to the system will mostly require pure stock and this is the same even with the nexus. So yeah, you most likely have to wipe your device before updating. I'd say, wait till Xposed for Lollipop is out, its almost there, once it comes out go ahead and root it, it'll at least be worth the hassle then
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Steve-x said:
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Click to expand...
Click to collapse
Right. All you need to do is flash the stock /system partition and also the recovery if you replaced it. I don't know why everyone's talking about having to wipe the entire phone with the all the stock images.
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.
Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.