Im still on 5.1.1 official version and my device is bootloader unlocked and twrp installed help me how to install official 6.0 version
First just flash 6.0 image through fastboot process in this twrp will be replace with stock recovery, Second flash someone's 6.0 Nandroid backup through TWRP...
Sent from my Toilet using Moto G3....
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
beworld16 said:
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
Click to expand...
Click to collapse
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
That's very much true.. Don't flash ota with TWRP with having root access..
Sent from my Moto G(Osprey)
Thanks for the reply
I have downloaded Official Firmware of 6.0 for XT1550 from here.
So Now, can i process with this using fastboot command.
If yes, will it look the bootloader ?
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
I thought OTA's worked fine with root installed, although you often lose root in the process, it was custom recovery they burped at?
Related
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
stivelio said:
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
Click to expand...
Click to collapse
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
gee2012 said:
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
Click to expand...
Click to collapse
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
stivelio said:
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
Click to expand...
Click to collapse
Your radio is not 5.0 compatible (stock), everythinhg has to be 100% stock and not rooted to be able to install the OTA
And if I unlock bootloader I will lose my data. Right?
stivelio said:
And if I unlock bootloader I will lose my data. Right?
Click to expand...
Click to collapse
Yup, there is no other way though. Backup everything you can before you unlock.
-Edit- You could try to root the device with CF Auto Root, install Bootunlocker from PLay and unlock the Bootloader without loosing data. Then unroot from the superSU app and flash the 5.0. radio, wipe caches in recovery or fastboot erase cache and see if the OTA can be installed
by sideloading it in stock recovery, link to the OTA http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
gee2012 said:
Yup, there is no other way though. Backup everything you can before you unlock.
Click to expand...
Click to collapse
Ah ok. I guess I will wait until 5.1 or something to do this when there are major updates
I'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!
arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
I've got my FRD-L14 (64GB US honor 8) running stable with B360 firmware (released 02-13-17) bootloader unlocked, SU flashed via TWRP.
I wanted to try the latest B385 OTA firmware flash so I used fastboot to flash my current stock B360 System.img, boot.img, and recovery.img to be sure I am running all stock boot/system files before flashing the B360 OTA.
I rebooted from fastboot successfully and continued with the OTA interface to install latest system update, it rebooted into Huawei recovery interface, verifying, installing, and then fails to verify and install.
Do I really have to lock the bootloader and wipe the entire phone in order to install latest OTA and then re-unlock bootloader, reflash twrp, and restore data ?
Thanks !
Well, that wasn't hard.
I used the "download latest full package" in the top-right menu of the OTA updates screen. This successfully installed B385 OTA update package for me without failure, while bootloader unlocked. Imagine that. I hope this helps someone else! Now, to figure out how to use magisk rather than supersu....
[remove, accidental doublepost]
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
crowruin said:
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
Click to expand...
Click to collapse
I just got the new update
mine26135 said:
I just got the new update
Click to expand...
Click to collapse
same here hahaha updating now.
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
br54 said:
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
Click to expand...
Click to collapse
Since when do you need to relock to install updates?
br54 said:
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
Click to expand...
Click to collapse
freeza said:
Since when do you need to relock to install updates?
Click to expand...
Click to collapse
There is no need to relock.
I didnt whe 110 came out and it still updated... rooted with Magisk as well
@any_thing
Check the ROMs/Kernels/Recoveries section, there's a modified stock recovery that allows for updating w/o relocking the Bootloader.*
Once complete, put TWRP back & root, you will not lose any data/apps/etc...... as you would by simply relocking your Bootloader....
* YMMV,this modified recovery may not be compatible w/your model.
https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
Sent from my HUAWEI BKL-L04 using XDA Labs
Good luck then.... Personally I don't care.. Mine works fine
any_thing said:
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
Click to expand...
Click to collapse
I have the BKL-L04 model & got an update notice earlier today:
While on stock rooted with TWRP & Magisk,the update downloaded & attempted to install,but,it failed.
So,just flash the stock recovery for your model & take the update w/o relocking your bootloader.
You will not lose any data from switching recoveries,at least on this phone.
(If you want to unroot 1st,that's fine,but,not necessary,flashing the modified stock recovery image unroots your phone anyway.)
After taking the update,flash the TWRP & Magisk (& Magisk Manager App,if it disappeared) as you did previously.
Just posting what worked for me,& in no way are my experiences/usage intended to contradict posts/suggestions from others,especially if they have the exact same model of phone as yours.
Hope this helps. :good:
any_thing said:
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
Click to expand...
Click to collapse
Just install stock ram disk...
It would automatically remove twrp and root.. And u will b able to install update once updated just reflash twrp ram disk and install magisk zip to get root back..
That's how I did it on c675
(--light--) said:
Just install stock ram disk...
It would automatically remove twrp and root.. And u will b able to install update once updated just reflash twrp ram disk and install magisk zip to get root back..
That's how I did it on c675
Click to expand...
Click to collapse
will i lose my data?
any_thing said:
will i lose my data?
Click to expand...
Click to collapse
No not at all... Ramdisk is a different partation
I had rooted phone with magisk installed, I received 2 updates like that - automatically lost root privileges, but I didn't receive .161 update (EIS update still not available for me?) any way to get this update?
PS my bootloader is unlocked... do I need lock it to get an update? and how to lock it?