Develop Bugs

OTA 4.1 upgrade pushed available on my phone help needed

Hey Guys I am currently running JRN84D MoDaCo custom Rom on my nexus how ever today I noticed an icon in the notification bar for System Update to 4.1 it says its downloaded and verified and ready to be installed.
What should I do?

i think u have to go back to stock image(rom) than update if u recive, this is update so is not going to wipe ur device

Do not accept the update when you're on a custom ROM.
It will not work.

martonikaj said:
Do not accept the update when you're on a custom ROM.
It will not work.
Click to expand...
Click to collapse
I'm in the same situation,
My nexus is running JRN84D, with the CWM recovery, and rooted. The radio is I9250XXLF1. The OTA message keeps coming. I don't want to wipe to get on 4.1.1. What should I do?
1 - Flash the stock bootloader? where can i find it?
2 - Unroot? how?
3 - Flash another radio? which?
And try to apply the OTA or should I directly flash a 4.1.1 rom from CWM and just accept the wipe, in that case which rom do you recommend?

By the way, I got in 4.1 through this process: http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
Method 1: CWM 5.5.0.2 recovery already installed
1) Download takju JRN84D from here (this is Koush's repack) to your computer and rename (or delete) this file: /system/etc/install-recovery.sh. Use 7zip to do this, not WinZip or WinRar or whatever. This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is. (We all know that if you have CWM, you will have to install the update manually through CWM -- it will not install automatically, but it will install just the same, right? ) Note: Some users have reported that they could not flash the zip after deleting the install-recovery.sh file. If it doesn't flash for you after you deleted the file, just re-flash the unmodified zip.
2) Move the file to /sdcard on your phone.
3) Download the CWM-flashable version of the XXLF1 radio from here and the CWM-flashable version of the LC03 bootloader from here to /sdcard.
4) Backup your app data using Titanium Backup. Root is required for this step. Alternatively, if you do not have root, you could try using this, but no guarantees it will work.
5) Reboot your phone into CWM.
6) Select "wipe data/factory reset" and select "Yes -- delete all user data"
7) Select "wipe cache partition" and select "Yes - Wipe Cache"
8) Select "advanced" and select "Wipe Dalvik Cache" and select "Yes - Wipe Dalvik Cache"
9) Select "*****Go Back*****" to return to the main menu
10) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the bootloader file you downloaded, and flash it.
11) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the radio file you downloaded, and flash it.
12) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the JRN84D file you downloaded, and flash it.
13) Optional -- If you want root, flash one of the attachments the same way. (Either ChainsDD's Superuser or Chainfire's SuperSU.)
14) Go back to the main menu and select "reboot system now".
15) Done! Enjoy stock Jelly Bean 4.1
Click to expand...
Click to collapse

snahrck said:
I'm in the same situation,
My nexus is running JRN84D, with the CWM recovery, and rooted. The radio is I9250XXLF1. The OTA message keeps coming. I don't want to wipe to get on 4.1.1. What should I do?
1 - Flash the stock bootloader? where can i find it?
2 - Unroot? how?
3 - Flash another radio? which?
And try to apply the OTA or should I directly flash a 4.1.1 rom from CWM and just accept the wipe, in that case which rom do you recommend?
Click to expand...
Click to collapse
Accepting the update will NOT wipe anything.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Find 7: "no su binary installed and supersu cannot install it"

Hi folks,
I've follow ParotZ's Recovery Installer process to root and am having SuperSu issues.
I install recovery (option 5), then reboot to recovery (option 0), system > reboot > swipe to install > and then once it loads I'm greeted with
"no su binary installed and supersu cannot install it"
I've put UPDATE-SuperSU-v2.16 on internal storage and tried earlier versions and flashed, with the same result.
The SuperSu app is installed. I attempted a manual update on the Play store, but the 'no su binary' message is still there.
I can't uninstall supersu, either with an uninstaller app or through Play (it does not show 'uninstall', just shows 'open')
It persisted after I factory reset and wiped (not through recovery).
Any help? Keen to get on Cyanogen.
My phone specs.
Model
Oppo x9076
ColorOS
v2.0.0i
Android version
4.4.2
Build number
FIND7WX_12_141017
Kernel
3.4.0-S3753
Baseband
Q_V1_P14
I've seen others with the question, but none with answers for the Find 7 :/
Cheers!!

solved
Hi folks,
I've solved the issue. I could not root using that method because I had updated the OS and there was some form of conflict that stuffed the SuperSu binary.
So I downgraded back to stock (the earlier ColorOS) and reapplied the root process.
For those with the same issue follow these steps http://theunlockr.com/2014/08/22/how-to-unroot-the-oppo-find-7-video/
Then reattempt the root.
Note that step 6. "Using the volume buttons to navigate and the power button to select the option you want, select Wipe Data and Cache." will erase the OS you just copied over, so do this prior to copying the OS or you'll just need to do it again.
When the OS loads and you come to the update SuperSu step, my Play store wouldn't load due to I think a delay in the accept terms of use popup. So I used the TWRP method and it worked fine.
Good luck.
Darren.

Cannot update 3.2.8 to 4.0.1 without getting dm-verity warning

So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again

Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.

Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups

install beta 7 firmware

Don't bother! It's not worth it! It's just a stupid message!

I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.

It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .

cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.

bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip

Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks

Updating from OB9 to OB20 (Pie)

Can someone tell me how I can safely update from open beta 9 to open beta 20 while maintaining root. I just want to make sure if there are any extra steps since open beta 9 was before the treble update. I am rooted with magisk.

also can anyone share updated twrp links or links for anything else I need if possible. Thanks

I heard that, I followed the guide in the development section and got and error when trying to flash it. I'm on TWRP 3.2.3-1 as well.

Yes, everything is fine, I have root. It took me a while, because of TWRP. The only problem is, that while you can get magisk, twrp will get overwritten by stock and I could not prevent it.
Process:
1. Install stock recovery (from here: https://www.androidfilehost.com/?fid=674106145207488252) in fastboot (fastboot flash recovery filename.img)
2. Install the new open beta
3. Download magisk on your phone
4. Install TWRP by codeworkx (from here: https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673) in fastboot and boot to twrp immediately.
5. Install magisk from within TWRP's first boot
6. After reboot twrp will most likely get overwritten by stock recovery, but we don't care as we have magisk already.
7. Profit.

@jazzgott so is there no way for me to reinstall twrp after updating? How will I update to new versions after?

@jccspeed
1. flash twrp via fastboot (pc, usb cable and phone and everything in need for this needed)
2. after flashing the recovery, turn off your phone, this is important.. do NOT boot your phone into the OS after flashing.. turn it off (chose power off with your volume keys within the fastboot mode and press the standby button once shortly)
3. hold volume down und power button at the same time until you see the "boot loader unlocked" warning stuff.. keep it pressed there for 2 or 3 more seconds. then let loose of these buttons.
4. you should now be in TWRP. congratulations.
if you now flash magisk, you will keep twrp as long as you keep magisk installed. you can freely boot into the OS and still have TWRP installed. How ever, if you don't install magisk and boot into your OS, your OS will overwrite TWRP with stock recovery.
forgot to mention: please use codeworkx pie twrp. its the one I have installed and have gotten into no problems so far.

@jazzgott @moeq123
Does this method erase the user data? I am encrypted and rooted(magisk). I want to preserve all my data.

@ajithpoison
at first I want to mention something important: always do a full backup.
if you unroot your phone (say, if you uninstall magisk using the uninstall.zip from within the magisk app itself and reboot) you should be able to update to open beta 20 via system update settings (where you need to choose a .zip file for the update.. so you need to download the open beta 20 rom from onceplus website).
(please verify that you are on stock recovery after the uninstalling magisk and reboot process. do this by booting into recovery with the power and volume down method. if you don't know how, google how to boot into recovery for your device)
This updating process should not erase your user data at all.
But be aware, that, if you want to go back to stable releases, you have to wipe everything.. so your user data will be erased if you choose to go back to stable releases.
if you want root and twrp back again, follow my instructions mentioned above.

@moeq123
Let me explain my situation in brief.
I am on the open beta channel. I am rooted(magisk) and I have the official TWRP and I am encrypted.
This is how I update everytime:
1. Download the zip
2. Reboot to recovery
3. Wipe cache and dalvik
4. Install update.zip
5. Install Magisk
6. Wipe cache and dalvik again
7. Reboot
This time, the above method will not work due to the compatibility thingy. I want to preserve app data. There are specific apps which I use and I don't want to lose those app's data. Previously I used titanium backup to take backup of app data. I am not sure whether backing up the app data and then restoring it will work since I am upgrading from oreo to pie. Is there any definite way to backup and restore app data after upgrading to pie?
I am summing up the method which I have to follow now. Correct me if I am wrong.
There are two methods which I know as of now.
Method 1:
The official method given by FunkWizard which involves deleting the compatibility.zip for which some users have reported ERROR 7.
Method 2:
1. Download Magisk & OB20 and have it in internal storage and switch off the phone.
2. Install stock recovery via fastboot.
3. Install the new open beta via stock recovery and switch off.
4. Install TWRP by codeworkx and boot to recovery
5. Install magisk from within TWRP's first boot
6. Clear cache and dalvik
7. Reboot to system and Profit.
(Will TWRP remain as a recovery after following all this or will it get overwritten by the stock recovery?)

@moeq123
Nevermind. I have got it to work without losing any data. I followed all the steps which were in the post by @funkwizard who put up the OP5T OB20 Official update post. It worked well except for one thing. The magisk manager did not show up even after installing magisk through the recovery. (I use BluSpark recovery). So I did a manual installation of the magisk manager apk and everything worked fine. I did not lose any data and so far no bugs.

Question OTA update while retaining magisk

I would like to install the latest Google OTA update but also keep root.
I heard you can do the following to retain root:
Open magisk
Click on "uninstall magisk"
You will then be asked if you want to "completely uninstall" or (restore image). You will choose to restore image
This restored image allows you to update your phone and you still retain root AS LONG AS YOU DON'T RESTART. So you do just that, you update and DON'T restart
After the update go back to magisk manager and press install. You will be asked how you want to install it (patch boot image, direct install etc). Select inactive slot.
Reset phone and enjoy!
But I walk against a wall against at step 3
Magisk never backed up my original boot image as I flashed it through fastboot. Where do I place the original image for magisk to find it? And what will my file have to be called? Magisk is probably looking for a certain file name
Then I also have a problem with step 5. I only get the option to direct install and patch boot image. I am not given the option to install it in an inactive slot.
What do you guys do to update your phone? Install it manually through fastboot? I would just prefer to skip the fastboot part going on. I just the commands so rarely that I always forget them and always have to look them up xD. Just seeing if this community know something I don't