Related
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
OK, the question came up a couple of times, so let's have a guide out there.
Some people want 100% unrooted stock back, and not a trace of any rooting or TWRP. So here you are.
1) Boot into TWRP, do factory reset, and flash "5.2.0_stock_recovery_only.zip" from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
2) Reboot into recovery, and sideload whatever stock you want (say, 4.5.3) as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
3) don't ROOT 4.5.3
4) full stock !!!
bibikalka said:
OK, the question came up a couple of times, so let's have a guide out there.
Some people want 100% unrooted stock back, and not a trace of any rooting or TWRP. So here you are.
1) Boot into TWRP, do factory reset, and flash "5.2.0_stock_recovery_only.zip" from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
2) Reboot into recovery, and sideload whatever stock you want (say, 4.5.3) as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
3) don't ROOT 4.5.3
4) full stock !!!
Click to expand...
Click to collapse
Hopefully someone can help. I followed the instructions and my Kindle Fire HD 7 4th gen was back at 4.5.3. I allowed the device to OTA update to 4.5.5 and it restarted to complete the update and now it won't turn on at all. No Amazon logo, no signs of life. Any help?
arrfenwoof said:
Hopefully someone can help. I followed the instructions and my Kindle Fire HD 7 4th gen was back at 4.5.3. I allowed the device to OTA update to 4.5.5 and it restarted to complete the update and now it won't turn on at all. No Amazon logo, no signs of life. Any help?
Click to expand...
Click to collapse
Happened to me too, just returned it and got a refurbished one back.
If you use this, DO NOT OTA UPDATE. If you want to update to 4.5.5, I think you can get the 4.5.5 update bin, rename bin to zip, and flash in TWRP. (Or just flash 4.5.5)
Gimzie said:
Happened to me too, just returned it and got a refurbished one back.
If you use this, DO NOT OTA UPDATE. If you want to update to 4.5.5, I think you can get the 4.5.5 update bin, rename bin to zip, and flash in TWRP. (Or just flash 4.5.5)
Click to expand...
Click to collapse
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
bibikalka said:
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
Click to expand...
Click to collapse
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Gimzie said:
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Click to expand...
Click to collapse
bibikalka said:
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
Click to expand...
Click to collapse
Ok, just to add to this: Would it be possible to flash back to 4.5.3 (With Fire OS 5 developer preview enabled), then update to 5.0 with OTA, and request a downgrade through Amazon officially? (Or would the OTA not work)
Gimzie said:
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Click to expand...
Click to collapse
Gimzie said:
Ok, just to add to this: Would it be possible to flash back to 4.5.3 (With Fire OS 5 developer preview enabled), then update to 5.0 with OTA, and request a downgrade through Amazon officially? (Or would the OTA not work)
Click to expand...
Click to collapse
Why do all this ?
Any 5 version will let you downgrade to 4.5.3. The earlier developer preview then allowed any other bootloaders to run (4.5.4, 4.5.5, 5.0 preview, so upgrades were safe). But the latest 5.2.2u2 can only be downgraded to 4.5.3 and upgraded back to itself (with root), and will brick with any other bootloaders, see this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Why do all this ?
Any 5 version will let you downgrade to 4.5.3. The earlier developer preview then allowed any other bootloaders to run (4.5.4, 4.5.5, 5.0 preview, so upgrades were safe). But the latest 5.2.2u2 can only be downgraded to 4.5.3 and upgraded back to itself (with root), and will brick with any other bootloaders, see this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
I followed that guide and already have rooted Fire OS 5.
So I guess to get to as stock as possible, I should simply flash 4.5.3, then block updates with ADB.
Gimzie said:
I followed that guide and already have rooted Fire OS 5.
So I guess to get to as stock as possible, I should simply flash 4.5.3, then block updates with ADB.
Click to expand...
Click to collapse
Well, the best stock is the one with ROOT When the device is rooted, it's literally a few simple modifications to the /system, so there is no need to fetishize ROOT-less stock.
But note that updates overwrite everything. So chaining versions makes no sense, and one should take the shortest route from where they are, to where they want to be while avoiding the bricking hazards.
bibikalka said:
Well, the best stock is the one with ROOT When the device is rooted, it's literally a few simple modifications to the /system, so there is no need to fetishize ROOT-less stock.
But note that updates overwrite everything. So chaining versions makes no sense, and one should take the shortest route from where they are, to where they want to be while avoiding the bricking hazards.
Click to expand...
Click to collapse
Well, I'm now running Fire OS 4.5.3, with root and TWRP installed. Blocked updates, and registered. Works like a charm. I find Fire OS 4 to be faster then Fire OS 5, although the sound quality went down for some reason.
@DoLooper recommended me to here, are any of these steps safe for me to use? I've never used Lolipop, only the rooted 4.5.4 with a different launcher from a the original root instructions you two came up with. I'd love to be on the latest non rooted firmware if possible.
My thread which has a bit of information. http://forum.xda-developers.com/fire-hd/help/factory-reset-rooted-fire-hd-t3338487
Shadowshinra said:
@DoLooper recommended me to here, are any of these steps safe for me to use? I've never used Lolipop, only the rooted 4.5.4 with a different launcher from a the original root instructions you two came up with. I'd love to be on the latest non rooted firmware if possible.
My thread which has a bit of information. http://forum.xda-developers.com/fire-hd/help/factory-reset-rooted-fire-hd-t3338487
Click to expand...
Click to collapse
Yes, if you have TWRP, I recommend that you follow this post :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Basically, I recommend that you install stock 4.5.5.1 and flash bootloaders to 4.5.3 ( +TWRP), perhaps also make_space*zip. This would be step 2 (a), (b), and (c). Then reboot. So you'll have stock OS (with OTA blocked), but will have an option to boot into TWRP, and update at any later date you want.
It work with cm 11 rom
i restore fw 4.5.3 my device working but after i update ota firmware 4.5.5 my fire return hard brick Pls hep me
Not to practice necromancy on this thread but I'll admit I am a bit confused. I thought this guide restored your Fire back to stock, and by stock I mean just like you pulled it out of the box new, like complete factory defaults stock. I see mention of disabling OTA updates which on a stock Fire you can still do without issues. So my question is if there is a way to really REALLY restore a Fire that had TWRP / Rooted back to being completely stock?
Hi there,
i try to install factory image on my nexus 6P 8.0.0 (OPR6.170623.017, Sep 2017) with the adb commands, everthing works ok but after turn on the device, the logo of starting android is moves and moves and moves and no start of the system, in the previus version it works correct, there is something on these version that makes it wrong?
secondly, i think i will downgrade to 8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi), there is option to upgrade using flashfire ? if so, which version i need to download full ota image or factory image for that?
thank you
update:
so i managed to install factory image 8.0.0 (OPR6.170623.017, Sep 2017) , but when i go to settings under updates still there is update of 991MB - it's very strange.
also i need to know about the flash fire which version i need to security updates full ota image or factory image for that?
thank you
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
wizardwiz said:
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
Click to expand...
Click to collapse
and where i can find these to download? it's not on the developer site,
also i have another questions
thank you
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
wizardwiz said:
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
Click to expand...
Click to collapse
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
I7210I said:
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
Click to expand...
Click to collapse
New link
https://forum.xda-developers.com/showpost.php?p=73762462&postcount=282
I used the 019 OTA and flashed it after unrooting, and reverted to factory recovery. Kept ElementalX kernel and it worked like charm.
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
I7210I said:
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
Click to expand...
Click to collapse
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
v12xke said:
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
Click to expand...
Click to collapse
i assume you don't have TWRP?
I7210I said:
i assume you don't have TWRP?
Click to expand...
Click to collapse
Yes, I use TWRP. It is always preserved using FF.
so you need to preserve the recovery, isn't it?
I7210I said:
so you need to preserve the recovery, isn't it?
Click to expand...
Click to collapse
haha. yes, you use (select) the preserve recovery option. It makes a copy of your recovery partition (TWRP) so you don't lose your custom recovery. There is a FAQ on using FF here. Best of luck to you.
Thank you
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work
Just received the stable Nothing OS 1.5 based on Android 13. Finally the wait is over. Check for updates.
What country are you in and what build where you on when you got the update?
bariz143 said:
What country are you in and what build where you on when you got the update?
Click to expand...
Click to collapse
I am using an Indian unit and was using 1.5 beta
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
You'll get it by the end of the week.
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Nothing stable version 1.5.2 arrived via OTA right now in Czech Republic EU.
I was an official beta tester!
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Got it overnight, Croatia
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
dedors said:
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
Click to expand...
Click to collapse
Open magisk, select uninstall and then restore stock images, DO NOT REBOOT, perform the OTA update, after it finishes DO NOT REBOOT, open magisk, select install, select install in the inactive slot.
After it finishes reboot when magisk ask you to.
You can only apply ota updates if system and vendor partitions are not modified.
You have to restore them if you have modified them or deselect the magisk modules that modify them.
Revanced yt is systemless, like busybox, universal safetynet fix and (obv) systemless host.
If a module modifies system it should be noted on the official repo or xda page.
After the update you can re activate all the modules that modify system and vendor.
Update when you feel it, sometimes it's good to wait, sometimes it's pointless.
If you don't have the ota update message you can update with the zip file.
You still have restore stock images, then either install the ota via dialer (which worked for me) or sideload recovery (which didn't).
After it finishes installing, reboot into fastboot and boot the modified boot.img
Open magisk and direct install it.
Depending on WHERE the operation goes wrong you could need just to boot the modified 1.1.8 boot img again to return in the previous context, maybe you could need to flash the full zip because of a soft brick or in the most extreme cases EDL mode with the guide here in xda.