Related
Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?
I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails
Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?
You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2
You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?
Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.
I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?
I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise
I used Google's batch file on windows to flash the stock 5.0, having unlocked the bootloader and also installed the chainfire root. Just wondering whether I'll get any fixes, or whether i'll have to always repeat this process, wiping out everything on the device in the process.
You may get prompted to download and install new updates when they arrive, but they will fail upon installation unless you're 100% stock.
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Does the Google image download page (https://developers.google.com/android/nexus/images) get updated as Lollipop gets updated? Or am I going to have to do OTA updates?
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
igeigeige said:
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
Click to expand...
Click to collapse
Well, I'm a bit confused. I'm on stock, but i need root, so i installed cfar, which I think included super su. when a new version of super su came out (i was alerted via google play), i needed to install the twrp recovery (which I didn't have installed at that point) to update it. So I guess I'm not stock any more, even though I've not actually put a non-stock image on. So even if the OTA update message popped up, I doubt it's safe to install it that way, even if it let me. I'm just not sure whether I need to a factory reset/wipe etc before updating, or if I can do a dirty update (the OTA is effectively a dirty update, isn't it?). And, like i said, i'm not sure whether that page gets updated with new images, or whether you're supposed to just put the initial one down and then do OTA updates (and only then root, change the recovery etc).
You have a stock rom but with a CUSTOM recovery. Yes, ota will prompt you to update, but DON'T. You should convert to stock recovery first. Because if you do, the update will push through, but once it asks you to boot to make the update in effect, you will have a NO COMMAND error - bootloop, and only fastboot and recovery (sort of dysfunctional). Just like most of the people here, including me. So make backup of your files first before doing the update. Cheers :good:
Sent from my Nexus 10 using XDA Premium 4 mobile app
If having a custom recovery is an issue, why could I flash ota zips from custom recoveries ever since buying the tablet?
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Rizz67 said:
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Click to expand...
Click to collapse
Hi, what i did was flashing the official factory image from google via fastboot/bootloader... Make a nandroid backup first though.. Because you'll need to clean flash (system partition/cache and data) to avoid future problems.
please educate me
A few weeks ago I rooted my N4 with CFAR (& of course had to wipe out everything). My understanding was that now that my bootloader is unlocked, I can sideload new images, thus sparing me a rewipe -- & in my ignorance, was anticipating that ChainFire would make 5.0.1 images in due course.
So, If I want to root subsequent 5.x.x releases, how would this work in real life??
Can i just restore stock recovery and then install the 5.0.1 ota update without losing everything?
Just switched on my Moto G 2015 (US Retail, XT1540 2GB) for the first time in a week or two and got an update notification...
April 1 2017 security update, Build Number MPIS24.65-25.1-19 and System Version 24.221.19.osprey_retus_2gb.retus.en.US.retus
Is this news to people, or am I just way behind?
I have the same model, just did check system for updates and the update notification popped up. No notification before checking.
you are just way behind........got this update months back
RijuSarkar said:
you are just way behind........got this update months back
Click to expand...
Click to collapse
But you have something different than a 1540. I believe 1540 was the last to get the January update, while there are other models with 6.01 which the 1540 most likely will never get.
I've never got an update.
Just got mine today, 6/26/17. Also have an XT1540.
So I followed the same instructions here as I did for the last security update to a rooted device. It worked perfectly with the exception of the unlocked boot loader warning. The dark logo I used survived the January security system update, but was lost with this update.
@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader
25vikasp said:
@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader
Click to expand...
Click to collapse
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.
MrTooPhone said:
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.
Click to expand...
Click to collapse
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition
25vikasp said:
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition
Click to expand...
Click to collapse
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.
MrTooPhone said:
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.
Click to expand...
Click to collapse
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
That is correct. I still have stock recovery installed, but I use fastboot commands to boot into TWRP recovery.
After connecting the phone to the usb, using Linux, I do the following commands from the same directory where my TWRP img file is located.
Code:
./adb reboot bootloader
sudo ./fastboot boot twrp-osprey-3.1.0-r1.img
This loads TWRP in your phone but does not install it.
From windows I think the commands basically the same without the "./"
25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
You can boot TWRP without flashing it to get root.
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.