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.
Related
I just got the new OTA for Lolipop 5.0.1. I used ADB to pull the URL for the download and downloaded the attached ZIP using my browser. The URL pulled from ADB was an extremely long randomized string of characters that expired the moment my device was done updating. It seems the link is only active during the update process, so the only way to leave the link active longer is to battery pull or something in the middle of the update. I love you guys... but not that much
Keep in mind that this OTA was offered to me on 22.21.16, so I am assuming that you probably need to be on that update before you can use this OTA.
Let me know if you guys have any questions or run into any issues!
I'm rooted and running TWRP on my XT1064 with 22.21.16. Is there a way to just fastboot flash this update? I don't mind losing root. Thanks!
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Edit: I went ahead and flashed stock recovery and rebooted. After boot looping several times it rebooted into the system and gave me the message "Software update unsuccessful. There was a problem ....blah, blah, blah." But I still show an update available when I check.
I suspect it is because I am unlocked and rooted, even though I have stock recovery installed. Any thoughts on this guys? I am going to hold fast until I know for sure.
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
DoubleIk said:
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
Click to expand...
Click to collapse
Not sure if it makes a difference or not. I just put what the build was listed as when I got the update notification.
I put that there in case that was why some people couldn't update from 22.21.6 to 22.21.16
shishir95 said:
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
Click to expand...
Click to collapse
Nice theory, but I am now totally restored back to stock with stock recovery and unrooted. Still no luck with the update. Same thing happens.
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
thisisjason said:
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
Click to expand...
Click to collapse
From what I've seen, that is correct.
Any news XT1068 android 5.0.1 #India?
Moto G 2014 5.0.1
Hello good day friends will have some manual to perform the installation ?? and try it for apply update from ADB and I mark error in sideload package , installation aborted
How do I can install this update?
Please help. I am not able to update the new official 7.1.1 update pakage for moto x play xt 1562..i have installed official recovery still while updating there comes error with robot sign. I even tried to search ota update file after downloading file but couldnt be located anywhere on cache and other places. I searched like an hour. But failed to find. Now m stucked. Please help me with solution. Device - unlocked + supersu. Thank you
I just had my bootloader unlocked but was on complete stock and non rooted I also faced the same error
Is your phone soft bricked without OS?
First of all, go to fastboot and flash the custom recovery twrp for moto x play and then flash the debloated 6.0 marshallo file and reboot. Check XDA site regarding this OS.
After booting you have official OS, then go for nougat update manually or wait for the developer to release a method install it on unlocked bootloader phone.
Krishna200894 said:
Please help. I am not able to update the new official 7.1.1 update pakage for moto x play xt 1562..i have installed official recovery still while updating there comes error with robot sign. I even tried to search ota update file after downloading file but couldnt be located anywhere on cache and other places. I searched like an hour. But failed to find. Now m stucked. Please help me with solution. Device - unlocked + supersu. Thank you
Click to expand...
Click to collapse
Even if you flash official recovery, the system status in Bootloader will be 'Modified'. You have to flash stock firmware through fastboot. Only then the system status changes to official. Then you can update the device through OTA
Device is locked. status code 0. software status official. still cant install 7.1.1 , status 7 error,installation aborted. what to do?
how you lock bootloader please details it help many people
I had a Media Pad M3 with unlocked bootloader, rooted and TWRP as recovery. As I wanted to update my ROM to BTV-DL09C100B311 I had some problems in TWRP an thought updating step by step would be a good idea. So I downloaded all missing ROMs throught FrimwareFinder and startet with BTV-DL09C100B307_fullOTA.
The installation in TWRP with ADP sideload worked and when I restartet my device a was a bit suprised that the yellow "Bootloader is unlocked - your device is unsecure" message was missing. I restarted again and the message is still missing. I thought OK perhaps I can now install all updates through the EMUI build in process without FirmwareFinder or TWRP.
EMUI downloaded the update and asked me to restart and install. After the restart the install process went to 20% and told me then there was a verification error. When I restarted the tablet again I got a screen similar to the yellow "Bootloader is unlocked - your device is unsecure". The screen is red an told me "Your device has failed verification an may not work properly".
Now I'm stuck. No updates work and TWRP could not be started or installed again.
I tried reinstall TWRP with fasboot (https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232) but I get the error FAILED (remote: "command not allowed"). I tried the newest TWRP mod from https://androidfilehost.com/?w=files&flid=125388 but same error.
Phone and FRP are still unlocked, as shown in FASTBOOT&RESCUE MODE so this is not the cause of the above mentioned fastboot error.
I installed the Android SDK completly and downloaded the newest toolkit (https://developer.android.com/studio/releases/platform-tools) but still get the above error. So I dont think its a driver problem either.
I did not try to unlock the bootloader again. I don't think this makes sense even if I still have the original codes.
I would like to get TWRP back and update the tablet to the newest ROM version. And it would also be nice to know what happened here
Thanks in advance for everyone helping me back on track. I think the first step should be get over the FAILED (remote: "command not allowed") error and install TWRP again.
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
sebbo2015 said:
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
I am also looking for a way to update my rooted M3 (WiFi edition) to the latest available version with security patch line of November.
Now I wonder whether with this updater in your post above this works immediately or if I also have to go through all the difficulties you faced?
Is it possible to install updates with a rooted device with this updater or do you always need to unlock the bootloader again?
Thanks for your help!
Just tried it out now and it worked! Data is still there, homescreen icons are a little bit messed up and root is gone (no problem).
This is great because I was looking now for a long time to find a way to update a rooted M3 with new OTA updats (all the usual way fails).
I used to do it with going back to stock and a factory reset being involved.
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Borkse said:
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Click to expand...
Click to collapse
Im happy I could help. I dont use Xposed.
Hi, can you, please, describe this in steps? What I have to do before standard OTA update should work? And when (and how) to open bootloader once more? Thank you very much.
Standard ota updates will not work. If you already have an unlocked bootloader you have to use this method https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 to manual update your M3 to the newest version.
If you have no unlocked bootloader please check this first https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232
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.
I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.
mrh45Zed said:
I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.
weazie said:
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.
Click to expand...
Click to collapse
Does locking need to be in the original stock or the latest version also works?
dangelfire said:
Does locking need to be in the original stock or the latest version also works?
Click to expand...
Click to collapse
Latest also works. That way you get the newest one and the OTA update is not needed until the next possible update.
You have to uninstall root, if you had a custom.bootlogo you have to replace it with original bootlogo and you can take the OTA.
Or you can just download full fastboot firmware and flash it
https://mirrors.lolinet.com/firmware/moto/evert/official/
Select your channel (don't know what's your channel? Go to settings> about phone and software channel)
If your channel don't have the lastest build version download from retail folder
Sent from my Motorola Moto G6 Plus using XDA Labs
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
Maybe get the latest version for your channel and flash it using fastboot (as in, full wipe OS reinstall). But wait to see if anyone here has a better idea.
awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
for now there`s no a perfect way to re lock bootloader, if you want to hide the "different OS has been installed" warn only flash this zip before you re lock your bootloader, dont forget that in stock will still show that system is compromised if you try to search for updates. (so my recommendation is dont relock bootloader! flash full stock rom with fastboot commands if you dont want to loose your apps just erase "fastboot erase userdata" from fastboot commands)
https://drive.google.com/open?id=1VE0kaUxmUbbhhNo075MCaW6VxaOTiDL6
For get certified playstore you need to verify that you can install Netflix if you can only wipe app data and playstore will show as certified device.
if you cant install netflix you need to change device fingerprint with a magisk module Safety Net Patch or with Magisk hide props.
ETA: never mind, figured it out.