Hello everyone!
Before, with the help of Nexus Root Toolkit; i used no-force encryption stock 5.0.1. Anyway, arrived two days before the 5.1 update via OTA. I tried the update, but the installation did not happen and n6 remained 5.0.1.
After i wiped the phone today with TWRP and i used Nexus Root Toolkit 5.1 with no force encrypted (LMY47D) I tried the installation. But the phone; "Android is starting - optimizing the app saying" and come back to the boot screen and continue like this constantly. In the meantime i tried LMY47E version.
Currently I'm back to 5.0.1 and the "no-force encrypted 5.0.1" I'm satisfied. But I want to get the 5.1 update. What could be the cause of this problem?
"Sorry for my English!"
There's a bug in NRT where it downloads the boot image based on your current Android version. Either wait for the next version of NRT or just choose 5.1 as your current version before flashing.
Only just, i tried with NRT "encryption -E" and it was.
I guess for 5.1 yet, "unencrypt" version is not ready or deemed necessary.
I'm running 5.1 unencrypted and achieved this with the Nexus Root Toolkit. What you need to do is to choose that you're running 5.1 (even if you're not) in the main window (top left) before flashing the factory image with "No force encrypted".
Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.
QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.
I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.
I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
Hi guys,
just after Android 9 had been released I flashed my device back to Android 8, because I was experiencing wifi-drops every few minutes. The phone worked without problems with that version.
Now I wanna try upgrading to Android 9 again.
My phone says there is an upgrade for Pie available, but when I try downloading and installing it, it always fails. That's why I tried a guide mentioned here in the forum. But installing that version (ab_delta-Blur_Version.27.301.32-29.11.36.payton.retail.en.US) from my SD card also didn't work, because it couldn't be mounted or something.
So, please, tell me, how do I upgrade to 9.0 again? It was a nightmare flashing it back to 8.0. It almost took me like 10 hours or so .
Thanks.
You have to flash the pie firmware completly ota does not work after a downgrade.
Latest Pie for XT1900-7 is here:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETEU/
Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.
Hello guys,
Few years before I was more confortable with root. Now I don't find what I need to update my S10.
It's a Snapdragon G9730.
I'm currently running Android 9.0 Rooted with Magisk. At the beginning I had random reboot issue (due to kernel issue). After years it's almost gone and I was running normally my phone.
I decided (don't know why....) to update magisk and magisk installer. Now I have reboot every single minutes... So I think I need to move to android 10 as the kernel issue is fixed in this version.
How to update to Android 10 without wipe?
How to keep root or root after update.
All topic I find are for G973...not mine...
Thanks for your help.