Related
Enrolled in the beta program and allowed it to download and install the 1.1gb Nougat file.
After reboot, still shows 6.0.1.
Any ideas on what happened, or more importantly, what to do to get to 7.0?
Thanks!
You 100% stock?
xxBrun0xx said:
You 100% stock?
Click to expand...
Click to collapse
Yep, no root, no recovery, nothing.
I'm having same problem
after I got OTA and update to 7.0 Still It showing 6.0 so I opt out beta program and soon as I got downgrade to 6.0 message I opt-in again
and I download OTA and install one more time.
now I got bootloop. device is completely stock. no unlock oem or usb debug or root. so when I'm trying to flash factory image.
it keep showing " FAILED (remote: device is locked. Cannot erase)"
so I can't fastboot flash or adb
I don't know what to do.
OK, I ended up downloading and sideloading it. Shows 7.0 now.
I had that problem too. previously using stock MM, no rooted etc. after downloading the N by joining the developer program, it downloaded but after reboot still showed 6.0.1 but with August security update. it also said that i have the latest software version.
a couple hours later, software update notification popped up again and after re-download it shows the 7.0
wililye said:
I'm having same problem
after I got OTA and update to 7.0 Still It showing 6.0 so I opt out beta program and soon as I got downgrade to 6.0 message I opt-in again
and I download OTA and install one more time.
now I got bootloop. device is completely stock. no unlock oem or usb debug or root. so when I'm trying to flash factory image.
it keep showing " FAILED (remote: device is locked. Cannot erase)"
so I can't fastboot flash or adb
I don't know what to do.
Click to expand...
Click to collapse
That's identical to my situation. Will see what Google say when I ring them.
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Hub00 said:
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Click to expand...
Click to collapse
Try it once again... I've never received OTA updates from b560 onwards.. You could flash your way through
crashpoum99 said:
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Click to expand...
Click to collapse
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
You can try local update......And preferably Force update but it will delete all your data so backup your data And Force update........ Btw leave B584 because B588 is avaiable
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
I would try force updating using the Power+Vol.Up+Vol.Down method. Go for B588 if you want, as it's newer with the latest security patch. If the error comes after the reboot, it's most likely that force updating will fix this. Remember, force updating will delete your files!
What actually worked is downloading 'full package' in the update menu (the file was 1.56Go instead of 260 Mo). It updated overnight even with twrp. Of course, I lost gyroscope in the process...
So I'm know with B584. I will try to force update to B588 as soon as it is downloaded.
Ok, i'm know on B588 and I have gyroscope back again. Thanks for your help.
However, despite the changelog, i didn't notice any improvement with the whatsapp notifications.
Any idea why ?
I went to work successfully unrooting my phone earlier this year.
I kept the bootloader unlocked because I didn't see it as a problem.
I began working on locking the bootloader this November after my phone could not successfully install the Nougat update.
I've flashed the stock Marshmallow image from Motorola's website but was never given the Nougat update :{
I've read in some places that image is outdated, so i tried some other "official" images I could find that were supposed to be more up to date.
I had the same problem with them so I successfully flashed a Nougat image from: firmware.center/firmware/Motorola/Moto%20X%20Pure%20%28XT1575%29/Stock/
I've now been hit a security update for nougat (version 25.201.1) and I get this error upon the first reboot
E3005 "/modem/image/adsp.b01" has unexpected contents.
E: Error in /cache/BLur_Version.25.11.22.clarck_retus.retus.en.US.zip
(Status 7)
I don't care if my bootloader is locked or not I just want my phone successfully install these updates
Any ideas?
Thanks
I think you had some errors with last flashing.
You should flash the same stock Nougat one more time.
Each fastboot command should ends with OK. @tijuanagenius
tijuanagenius said:
I went to work successfully unrooting my phone earlier this year.
I kept the bootloader unlocked because I didn't see it as a problem.
I began working on locking the bootloader this November after my phone could not successfully install the Nougat update.
I've flashed the stock Marshmallow image from Motorola's website but was never given the Nougat update :{
I've read in some places that image is outdated, so i tried some other "official" images I could find that were supposed to be more up to date.
I had the same problem with them so I successfully flashed a Nougat image from: firmware.center/firmware/Motorola/Moto%20X%20Pure%20%28XT1575%29/Stock/
I've now been hit a security update for nougat (version 25.201.1) and I get this error upon the first reboot
E3005 "/modem/image/adsp.b01" has unexpected contents.
E: Error in /cache/BLur_Version.25.11.22.clarck_retus.retus.en.US.zip
(Status 7)
I don't care if my bootloader is locked or not I just want my phone successfully install these updates
Any ideas?
Thanks
Click to expand...
Click to collapse
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
acejavelin said:
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
Click to expand...
Click to collapse
How would I properly update my modem firmware? Can i just flash the new modem firmware or do I have to re-flash my entire phone again :{
tijuanagenius said:
How would I properly update my modem firmware? Can i just flash the new modem firmware or do I have to re-flash my entire phone again :{
Click to expand...
Click to collapse
Ignore this^
acejavelin said:
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
Click to expand...
Click to collapse
Thanks! I simply tried flashing the NON_HLOS.bin file again and the update completed successfully!
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
64erbaz said:
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
Click to expand...
Click to collapse
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
swieder711 said:
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
Click to expand...
Click to collapse
I'm having this same issue. How do I flash back to factory default?
baydude said:
I'm having this same issue. How do I flash back to factory default?
Click to expand...
Click to collapse
Covered many times in this thread. Get in edl mode and flash stock with MiFlash
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
I'm having the same problem, any luck? I've been attempting to flash back to an earlier rom to see if that fixes the problem, but I haven't been able to find a stock rom that actually works yet.
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
Weird fix that seems to have worked. make a backup of the system using twrp following this https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407, then grab the boot.emmc.win and reflash it using fastboot. I'm currently installing the 8.1 update as I type this.
Hello people!
I have a Moto G4 Plus XT640-DS stuck on 6.1.0 stock and it's not getting the OTA update in any way. The ROM version is MPJ24.139-23.1 and I wanna know if anyone has a Blur Version update for this ROM or an idea to force the OTA on the system.
gabrielbrondon said:
Hello people!
I have a Moto G4 Plus XT640-DS stuck on 6.1.0 stock and it's not getting the OTA update in any way. The ROM version is MPJ24.139-23.1 and I wanna know if anyone has a Blur Version update for this ROM or an idea to force the OTA on the system.
Click to expand...
Click to collapse
You can install the stock fastboot rom for nougat for example if it's that what you want?
strongst said:
You can install the stock fastboot rom for nougat for example if it's that what you want?
Click to expand...
Click to collapse
I tried some Blur ROMs I found here, but all of them come back with a error because the stock ROM installed isn't on the version the blue version requires
gabrielbrondon said:
I tried some Blur ROMs I found here, but all of them come back with a error because the stock ROM installed isn't on the version the blue version requires
Click to expand...
Click to collapse
Without knowing what version was previously on your device, I'm not comfortable with suggesting OTA updates. If your device was downgraded with Marshmallow, then using blur OTA updates might be risky.
Did you install the Motorola usb drivers, minimal ADB /fastboot and if you're running Windows 10, to ensure you have disabled driver signature enforcement? Just to check you've mentioned it's working for your other device.
If so, and you have fastboot working, then we can try to flash the stock fastboot ROM as suggested by strongst above.
echo92 said:
Without knowing what version was previously on your device, I'm not comfortable with suggesting OTA updates.
Click to expand...
Click to collapse
Sorry, here is the phone specifications:
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
echo92 said:
if you're running Windows 10, to ensure you have disabled driver signature enforcement?
Click to expand...
Click to collapse
How do I disabled that?
gabrielbrondon said:
Sorry, here is the phone specifications:
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
How do I disabled that?
Click to expand...
Click to collapse
Thanks, that's one of the first builds of Marshmallow for our device - seems that the buyer tried to revert back to original condition. However, the problem is that if your bootloader is newer than your stock firmware, attempting to use OTA updates may well corrupt your bootloader and hard brick the device. If you boot to the fastboot screen, what bootloader version (E.g. B1.03, B1.06) listed below the AP secure flash line?
I think you've already got the driver signature enforcement disabled as you mentioned fastboot was working for your own device, but if you want to check, here's a tutorial: www.howtogeek.com/167723/how-to-dis...8.1-so-that-you-can-install-unsigned-drivers/
echo92 said:
If you boot to the fastboot screen, what bootloader version (E.g. B1.03, B1.06) listed below the AP secure flash line?
Click to expand...
Click to collapse
It is B1.06 (sha-0edfb0d, 2017-06-01)
gabrielbrondon said:
It is B1.06 (sha-0edfb0d, 2017-06-01)
Click to expand...
Click to collapse
Thanks, so someone did appear to flash a really old firmware on top of a newer bootloader. By the way, do you mean MPJ24.139-23.1? I'm having difficulty finding MPJ23.139-23.1.
Regardless, you've got a June 2017 Nougat bootloader on a device running Marshmallow, so OTA updates even if you could get them, would hard brick your device, likely.
Any luck on getting the device recognised in fastboot? What happens if you boot the device to the bootloader, connect to your computer, and then in a minimal ADB terminal on your computer, type 'fastboot devices' without quotes? Does that device's serial number appear when you press enter?