heyyyy, so, i can't manage to get OTAs to install...
bootloader is unlocked, and i had installed TWRP for a while, but ultimately reflashed an older version of the stock recovery.img
now, i'm still having issues with OTAs... they download and begin to execute as normal, but the progress bar on the update screen stops at about 10% and then the screen with the android figure with it's chest cavity open pops up and simply says error!
the phone reboots itself as normal after a minute or so, and once booted up properly, it just says "update failed, no changes were made"
any thoughts or suggestions on that?
i've got the -01 version, north american retail...
imho OTAs aren't working since you cannot re-lock the bootloader of the z2 play because there is no boot.img signed from motorola available.
so you will have to install OTAs manually when the become available through e.g. TWRP.
the OTAs recognize an altered boot.img and don't get installed this way.
I had originally unlocked my phone and did the whole TWRP/root thing, but with the lack of development, I went back to stock, using the images Junior Passos has posted. I still have an unlocked bootloader, but I can apply OTA updates fine (I've had the last three OTAs install without issue).
Related
The lack of a proper forum has made it very hard to find much information regarding the LG G-Slate. I am posting this for those who are having trouble finding the very useful information buried within these forums. This is a very significant mod/hack for the G-Slate and I would like to thank ChiefzReloaded for the amazing work he has put into it!
This was taken directly from our G-Slate project page. If you are unfamiliar with "Fastboot" I recommend reading up on it before proceeding.
In no way am I responsible for your device. This process below assumes that you know what you are doing, so if you do not, PLEASE AVOID THIS!
Unlocking the bootloader
Copy bootloader.zip to /sdcard/
Download Clockwork Recovery 5.5.0.2 (Attached Below)
Reset to Fastboot mode and boot Clockwork Recovery 5.5.0.2.
Code:
fastboot boot recovery.img
Install the bootloader.zip:
Install ZIP from sdcard
Choose ZIP from sdcard
bootloader.zip
Yes - Install update.zip
Let it flash, it will take about 60 seconds, then:
Go Back
Go Back
Reboot System Now
The system will reboot to a "Downloading Now" screen. Let it finish, and it will reboot.
All done!
Click to expand...
Click to collapse
Instructions courtesy of dasunsrule32 from G-Slate IRC.
You now have the ability to flash custom kernels/ROMs/mods/hacks again!
If you are interested in more info, please visit our Project Page!
bootloader.zip
DOWNLOAD
CWR 5.5.0.2
DOWNLOAD
Thank you...so much! LG can go suck a big one.
...
Like STDs and all...I strongly dislike that company.
stuck at lg boot screen after reboot
There's a new OTA update being sent out to G-Slates. Mine downloaded it today, it says:
System SW update to v10p Downloaded and Verified 13.3MB
This important system software update includes security fixes, USB game controller support and a fix for an Android Market download problem.
Click to expand...
Click to collapse
I have not applied it yet. Given they locked the bootloader last time, I'm very leery about what they're securing in this latest update. It is NOT an ICS update. From discussion in a T-Mobile forum thread, I know it does change the radio amoung other things.
But I have not unlocked my bootloader, I am rooted though. I'm wondering:
If I take this OTA update before unlocking the bootloader, will the unlocking process still work for me?
If I unlock the bootloader and then try to install this OTA update, will the update even work or will it try and re-lock my bootloader after being unlocked? (I know I can hide the fact I'm rooted.)
How could we get the benefits of the OTA update without installing the one provided? I mean, might someone turn it into a flashable zip that could be installed via Clockwork Mod Recovery?
If I have to choose, I'll probably unlock the bootloader without ever trying to install the update. But given my current state I'm trying to weigh the options and have the best of both worlds, the update and an unlocked bootloader .
If someone wants a copy of the OTA for investigation, just let me know how to pull it and I'll do it.
Unlocked the bootloader tonight, using the newer version of CWM from here.
Over on that forum, someone plans to make a safe flashable zip of the OTA. The one that came OTA will relock things if used. You can remove the downloaded OTA file by going to /cache and remove the .zip from there that was downloaded. Since they have a dedicated G-Slate forum, it seems more development for our device is going on there, so that's the forum to check out.
The nag screen will continue, but if you stop "LGESystemService" from autostarting, the nags won't be so frequent, just after reboots. I'm not sure how to totally get rid of the nag messages totally yet. I'm hoping maybe after flashing the safter version once one is made that the nags will go away.
Hi, i have some kind of problem with my nexus 7 2013.. I already have lollipop 5.1.1 official on my tablet and have root and unlocked bootloader (root with king root, yes it works and is rooted.. And bootloader unlocked with boot unlocker.. I know you might think that this are not the best way of rooting or unloking the bootloader but it worked for me and im happy) and since yesterday the tablet keeps telling me to update via OTA the 5.1.1 update witch i already have..i press update to install it as normal, it reboot as normal too and when it shows me the parte where it suppose to be installing the update (you know, with the android with the chest open part) the only thing that says is "error" it doesn't install anything..i did this like 3 times now and every one of them says error.. The annoying part is that it keeps showing me the notification to update it..so any solutions? Thanks!
Sorry for bad english blah blah...
You can't take ota updates if you modify system files, you did that with root. Don't know why it's showing you 5.1.1 when you already have it.
Just flash the factory image with fastboot (probably no need to wipe, just flash boot.img and system.img and format cache).
That should fix the problem. It will also remove root. I'd recommend not using that king root **** but whatever. Probably better to just flash the su zip in twrp or use CF-Auto-Root.
When the next update comes remember you won't be able to take the ota. But that doesn't matter since google posts factory images and all you need to do is flash it with fastboot, then root again.
yosmokinman said:
YDon't know why it's showing you 5.1.1 when you already have it.
Click to expand...
Click to collapse
There's a new 5.1.1 = LMY48G
Original 5.1.1 is LMY47V
^Oh yeah, lol.
Still the rest of my post will get it installed for op.
I'm an idiot who just assumed that the unlocked phone he bought new in Europe was the European version (dual-SIM) and didn't first take a backup of all the partitions before messing around with it.
I'm wondering if I got sold some other region's hardware by a shady seller. How can I tell? Do I just have to flash every firmware out there until I get it to boot, or is there another way?
Model: XT1635-02
Type: M1D64
And dual-SIM.
I unlocked the bootloader, flashed TWRP, decided that I wanted to take the OTA, reflashed recovery to stock from the latest EU package...and it would no longer boot. Flashed back to TWRP, same. Reflashed the entire firmware package following these instructions, but it still won't boot.
Thanks.
--
Update: after considerable fiddling, I reloaded TWRP and got it to install and boot the Cyanogenmod 14.1 release, meaning my device is not permanently trashed beyond repair-- it just doesn't like any of the firmwares I've tried to feed it. Obviously this is still sub-optimal since CM requires some blobs that Moto haven't yet released to support the camera etc., but it's better than nothing. My goal is still to get stock firmware back onto this phone.
Update2: buoyed by my CM14.1 success, I decided to try to apply a similar methodology to get the stock firmware running. I failed utterly. Maybe if I build a TWRP-flashable copy of the stock RETEU package I could get it to flash fully and boot, but all it does at this point is loop over the bootloader unlock warning screen and occasionally attempt to auto-erase itself in Recovery before bootlooping again.
Update3: aaaand my IMEI is "0." This seems bad.
boot to fastboot screen and take a pic of it and post it.
Hi, recently I bought my Moto Z2 Play (XT1710-09).
I really wanted to root my phone, but because of some weird bug, it soft-bricked it. Fortunately I had Absolute backup of whole internal storage so I have Original files.
Also I have not flashed TWRP, I have only fastbooted TWRP (Which is propably why I soft-bricked my phone)
So my question is very easy. Is it possible to lock bootloader if I have recovered back whole system and all it's files by stock files with which it (Moto Z2 Play XT1710-09) arrived?
Also the phone is fully functioning at the moment, with original files mantionet above, but it can't make working OTA updating process. And it's pain in ass, because the update manager is still apearing with new update...
So I have decided to lock bootloader even if it means to wipe all personal data and factory reset. Just for sake of getting rid of that stupid OTA updatete fullscreen pop up, that I have a new update waiting to be downloaded and installed.
You may ask as well "Why do you want to lock bootloadert insted of buying Titanium backup pro and freezing that update manager". The reason is simple. I'm afraid of rooting my phone again, because last time, it soft-bricked it and next time, it may full-brick it.
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Surely there is a fastboot command somewhere (which I think I saw in another thread) without having to flash some firmware?
https://forum.xda-developers.com/showpost.php?p=77270030&postcount=9
So that does mean. As long as I have 100% of stock files with which it come to me, it will lock?
julesism said:
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Click to expand...
Click to collapse
Every firmware I try fails to lock my bootloader, validation fails because non of them are above the security level of my device before I unlocked. Is there any newer firmwares ?
in brief
I have unlocked the botloder with commands in cmd, I have uploaded magisk, I expanded internal memory by sd card (my error). Unfortunately, after the upgrade to Android 9, the phone fail at receive any new updates (installation error of 30%). Subsequently, dumped magisk, did not help, , I uninstall sd card, now I did restore the factory data and the updates still do not work. November version of Andorida is badly bugged and there are problems even with the camera. So it looks like I'll have to send a phone for guarantees, a question now how to block a botloader or you have an idea how to fix ota update.
same here, but now you can download the full 10.0.3.0 rom to install with miflash. https://en.miui.com/download-354.html
fine but how to reblock a botloader ?
karenz88 said:
fine but how to reblock a botloader ?
Click to expand...
Click to collapse
use this on fastboot:
Code:
fastboot oem lock
Warning: this will wipe your data and if you have tampered with phone's partitions phone will hard brick. Make sure to have a backup. Other people have also experienced issues with January update. Locking the bootloader and booting the phone successfully doesn't mean that you will have January update for sure.
There's no point in locking the bootloader or returning the phone just because you failed to apply OTA update. Your phone is perfectly fine. Most of us had problems and bootloop while trying to apply Magisk OTA. This has been a frequent issue since the initial Pie update and the phone has nothing to do with it. It's either Google implemented stricter security policies or current version of Magisk are having Pie compatibility issues. If OTA is to important to you, just flash an official fastboot image and don't root your phone.
Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...
karenz88 said:
Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...
Click to expand...
Click to collapse
Fastboot image of 10.0.3 is already out. You could consider flashing your phone with "flash all" option to fix the errors. And i would recommend keeping the bootloader unlocked because many mi a2 owners got their phone bricked as a result of ota update with a locked bootloader in which case the only workaround is to disassemble the phone.