Got the latest update.zip for the October Security patch. Wasn't stored in the normal location /cache But the update.zip file isn't recognized by flashfire? Would like to install it instead of flashing the full system image files.
Related
I want to flash ota with twrp...i dont know the default location...need help
On my G4 (not Plus!) the OTA updates are downloaded to:
Code:
/data/data/com.motorola.ccc.ota/app_download
For example, the latest one OTA update file is called:
Code:
Blur_Version.24.24.4.athene.retail.en.US.zip
Let us know if you succeed with flashing the OTA zip. So far from what I've read - it's not possible to flash it once you modified the system partition (e.g. installed SuperSU or similar).
Don't know if flashing from TWRP is possible. https://twrp.me/faq/officialota.html
If you already changed your system partition (for example, mouting it in TWRP in r/w mode) the hash was changed and the OTA update will fail. You'll need to find a flash image and flash the system partition again to be able to update using the OTA. Remember to take note of the version you have to flash that exact version.
I am having some issues since I updated to Shield TV v3.3
I had root on v3.2 but since the update OTA now I dont have root.
I still have TWRP recovery but TWRP wont show my SDcard.
Has anyone updated to the latest version ?
http://nvidiashieldzone.com/2016/10/shield-android-tv-ota-update-3-3/
I cant find a way to flash supersu.zip since my sdcard wont show up in TWRP and system is read only...
Update: Got it working! adaptive storage was messing this all up.
Got it working! adaptive storage was messing this all up.
If your shield is rooted and you want to keep it using the OTA 3.3 upgrade you have to stop the update from installing when the download is complete. (I unplugged the unit). Search for the OTA update zip using a file manager. Its about 900 meg, I think. (I transferred the ota zip to a sd card.) Then flash the zip file using FLASHFIRE. Select everroot option to keep your system rooted when you flash the zip file. Select wipe if you want to start from a stock install. (You will loose everything with a FULL wipe, of course) I also preserve the recovery as I have TWRP installed for emergencies. Look through the options in Flashfire I seem to recall having to select something else when flashing an OTA zip. Never hurts to make a backup (with Flashfire) of your upgraded system and vender images after flashing.
Or wait for Nvidia to release the images.
HERE: SHIELD Developer OS Images
Hello,
i am using oxygen os 3.1 with TWRP recovery. No root no modifications other than TWRP.
Is it possible to update without factory reset to the latest oxygen os without losing my custom recovery TWRP?
I read about signed flash able zips - but i am not sure on how to proceed.
Guidance is appreciated !
Thank You
Device is Oneplus two 64gb.
german_oneplus_two said:
Hello,
i am using oxygen os 3.1 with TWRP recovery. No root no modifications other than TWRP.
Is it possible to update without factory reset to the latest oxygen os without losing my custom recovery TWRP?
I read about signed flash able zips - but i am not sure on how to proceed.
Guidance is appreciated !
Thank You
Device is Oneplus two 64gb.
Click to expand...
Click to collapse
You want to upgrade to latest 3.5.5 ? You'll have to wait until signed flashable zip for 3.5.5 is made. For now 3.1.0 is the latest flashable zip.
Check this thread -> http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Thank you,
so i will wait for the full signed flashable zip.
still - my questions remain - i do not completely understand this :
Note: Since OTA incremental update zips will fail on rooted devices or devices with modifications to system files, it's not possible to use these to update without reverting back to completely stock, unrooted first.
To update you must either wait for the new, full, signed flashable zip to appear (usually a few weeks after the OTA update) or use the following workaround:
Boot into TWRP recovery
Flash the latest full signed flashable zip
Flash the new OTA incremental update zip
Flash the SuperSU zip
Reboot
Is it possible with the full signed flashable zip to keep twrp and my settings ?
Thank You
german_oneplus_two said:
Thank you,
so i will wait for the full signed flashable zip.
still - my questions remain - i do not completely understand this :
Note: Since OTA incremental update zips will fail on rooted devices or devices with modifications to system files, it's not possible to use these to update without reverting back to completely stock, unrooted first.
To update you must either wait for the new, full, signed flashable zip to appear (usually a few weeks after the OTA update) or use the following workaround:
Boot into TWRP recovery
Flash the latest full signed flashable zip
Flash the new OTA incremental update zip
Flash the SuperSU zip
Reboot
Is it possible with the full signed flashable zip to keep twrp and my settings ?
Thank You
Click to expand...
Click to collapse
As it says you can't use incremental update zips if you're rooted or has a modified system. You can either Flash the latest full signed flashable zip & then Flash the new OTA incremental update zip (without rooting) OR just wait for the Full signed flashable zip & then flash it(whether you're rooted or not). As for now neither "Incremental" nor "full" signed zip exists for 3.5.5.
And Yes. You won't lose TWRP.
To understand more about "Incremental" & "Full" update packages, read this -> https://source.android.com/devices/tech/ota/tools.html
you can flash full rom zip and without restarting flash twrp image in twrp itself, its kinda tricky but it works
3.5.5 Full Signed Flashable Zip's now available. Check the thread I sent before.
german_oneplus_two said:
Hello,
i am using oxygen os 3.1 with TWRP recovery. No root no modifications other than TWRP.
Is it possible to update without factory reset to the latest oxygen os without losing my custom recovery TWRP?
I read about signed flash able zips - but i am not sure on how to proceed.
Guidance is appreciated !
Thank You
Device is Oneplus two 64gb.
Click to expand...
Click to collapse
I was on 3.1.0 with Hybrid recovery and root before the OTA for 3.5.5 came through. It installed itself via the ota (1.2gb) and when it was done I was back on default recovery and no root...which i fixed in few minutes..So I am now on the latest OS 3.5.5 with Hybrid Recovery and Root..everything is perfect! No network drops so far e.t.c
Edit: I didn't have to unroot for the OTA to work..It just did. Also didn't lost any data. all apps +data still intact
Thank You B!Gguy.
Signed flashable worked flawless
Installed TWRP by OldDroid on Nougat b370
After that, I flashed a SuperSU 2.82
So my phone is rooted now, but whenever I grant permissions to text editor or ES File manager and try to edit system files it says "Read-only system"
How can I edit system files on Nougat?
Coolyou said:
Installed TWRP by OldDroid on Nougat b370
After that, I flashed a SuperSU 2.82
So my phone is rooted now, but whenever I grant permissions to text editor or ES File manager and try to edit system files it says "Read-only system"
How can I edit system files on Nougat?
Click to expand...
Click to collapse
Hello.
I just found a solution to go to b380 without root.
Can be you can test since l21c432b370.
Downloaded the b380 full ota mf zip.
With huawei extrator retrieved the file. (Boot, system, cust, vendor, version).
Downloaded the toolkit beta and twrp edit de hassans.
So since b370 stock no root.
Install twrp of hassans.
Then went into bootloader mode, connected to the beta toolkit, gone to Unbrick and flash boot.img, system.img and cust.img.
Finished, do not reboot, unplug cable, went to recovery twrp.
Install image, vendor.img and install image version.img.
reboot.
Normally all works. Zero bug.
I just did it on the l31c432b380.I went to b382, then 384 and i got to b388.
For root, I use simo255 root.
I just purchased the ph1 and plan on rooting the device and also flashing twrp. I've found the guides and everything seems pretty straight forward. The phone should be arriving tomorrow so at this point I'm unsure of the build it will have when I receive the device. I noticed a thread regarding the February update not working with twrp. Has this issue been resolved or will I need to flash to the January version to complete the task? Is the February and January builds mentioned the most recent updates for the device? I've found the links to the essential website but it gives me a error that its server IP cannot be found so I've been unable to check it. Is the site going to be down indefinitely due to no longer supporting the device? Does anyone have a link to the updates hosted elsewhere? The device was listed as GSM unlocked and did not mention any carrier tied to it so I'm assuming it's a factory unlocked device but will have to verify upon receiving it. Is the updates carrier dependant or do they all utilize the same files? Whats the consensus on roms/kernals on this device as opposed to rooting and using twrp on the most recent stock builds? Which Rom would you recommend if I do decide to go that route? Thanks for any advice you can offer, it's greatly appreciated.
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
SirDigitalKnight said:
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
Click to expand...
Click to collapse
I ended up receiving the device and it had Android 8 out of the box. I received a update that took me to Android 9 which was roughly 1100mb and another to Android 10 which was a little over 1000mb. The second update automatically included the February security patch. Rather than downgrade to January, I simply patched a February boot image with magisk and flashed with fastboot. I also flashed ElementalX kernel via fastboot. As far as I can tell they are not carrier specific. I am considering going to January now so I can use twrp to test some custom roms. For downgrading to January do I simply flash the January boot image which shows to be about 65mb or do I need to find the firmware in it's entirety? Also rather than down grade and use twrp can I just flash custom roms via fastboot? I would say you might have to downgrade to January to use twrp to flash Android 11 unless it's possible to flash the roms on fastboot, hopefully someone chimes in bc I'm unsure at this point.
Noob question, but what's the advantage to changing just the kernel?
Coming back to XDA after over a year. Realized Google Play Store update ruined my Magisk status, and evetually root (SafetyNet stuff). Here are some notes I took while I flashed in 2019, hope it helps.
1. DISABLE Security (PIN/Pattern/Fingerprint)
2. Backup Internal Storage
3. Boot to recovery TWRP, and backup nandroid.
(must go to bootloader and change slot to boot twrp.img flashed on that boot partition slot)
4. Normal boot and drag drop nandroid backup to PC.
5. Syncthing/Resilio for extra measure.
Have latest OTA.zip, boot.img (same version as OTA.zip), and latest Magisk.zip in root internal phone storage.
Have twrp.img in platform-tools adb root for flashing in fastboot.
twrp.zip is optional stored in root internal phone storage.
Flash OTA.zip update in TWRP. (assuming system is under slot_b)
This will flash to opposite slot, _a.
(I flashed under slot_b and new OTA went to slot_a, I booted back to _b and
old system version remained with broken Wifi becasue I accidentally flashed new boot.img in TWRP image over older system image
in slot_b, without the image flash, I suspect the old slot_b would have been perfectly untouched and rooted, as OTA applied to slot_a)
(Went back to A and new OTA was perfectly fine, although unrooted).
Boot to slot_a (system_a), make sure it runs good and verify version within settings, should be unrooted.
Boot to bootloader (under same OTA slot_a), default recovery should be stock recovery (droid logo) after OTA flash.
fastboot flash boot twrp.img (this will replace stock recovery to twrp recovery, deleting stock boot img as well, breaking OTA slot)
Reboot to recovery twrp (remain on same slot and will run off of RAM, leaving boot partition open to flash back stock boot.img)
Install boot.img (make sure version is correct) boot partition should be back to working condition although unrooted OTA system.
Try booting back to recovery on same slot, and stock droid recovery is back. (you cannot edit partitions from fastboot, hence twrp flip flop)
Try booting to system, it will boot but broken, no wifi. How? Not sure, maybe used old boot partition .img in slot_b to boot to system_a
Then flash latest magisk zip to patch stock boot.img for root.
(if you flashed twrp.img and magisk, then you're patching twrp, which is incorrect.
You want to boot to twrp, then flash boot.img back to boot_a partition, then run magisk.zip to patch stock boot.img in that boot_a partition)
Magisk.zip flash log:
Current boot slot: _a
Mounting system
Mounting vendor
Device is system-as-root
System-as-root, keep dm/avb-verity
Encrypted data, keep forceencrypt
Target image: /dev/block/sde11
Device platform: arm64
Constructing environment
Boot image is signed with AVB 1.0
Unpacking boot image
Checking ramdisk status
Stock boot image detected
Backing up stock boot image
Patching ramdisk
Repacking boot image
Flashing new boot image
Sign image with test keys
Unmounting partitions
Done
Updating partition details...
...done
Wipe cache/dalvik
In TWRP, tap reboot button and switch slot_a to other slot_b (older system version).
Reboot to bootloader_b in TWRP.
Flash twrp.img in that other old slot_b (For backup purposes and to have twrp at hand because boot_a has patched rooted boot.img and not twrp anymore)
Done!
Click to expand...
Click to collapse