Develop Bugs

[Q] Getting CyanogenMod on LG Nitro - Issues

Hello,
I have just rooted my LG Nitro with the Bin4ry root kit, followed a video tutorial. Can't post links because this is my first post on XDA Developers, unfortunately.
Everything seemed to work as expected.
Then I installed ROM Manager, and have proceeded with install instructions for CyanogenMod specific to my phone (I will post this after the end of my message as a reference since again, no links are possible).
In these instructions I began at "Installing a Custom Recovery Image" because the rooting instructions do not work for my phone (it has ICS installed, hence the need for the Bin4ry root method). I'm following the steps to the letter, and got stuck at "Boot into the ClockworkMod Recovery" - when I try doing this, SuperUser pops up and I grant permission to ROM Manager, and then it reboots - but instead of getting any option to install CyanogenMod, it hangs at the LG logo boot screen, with some command line-ish startup text along the top:
Secure booting Error!
Cause: boot certification verify
Enter the fastboot....
Enter the fastboot....
Long time no see!
-----
It will hang here until I hold down the button for 10 seconds or pull the battery. It will reboot normally afterwards though, thankfully. The phone is still working as-is so I'm not dead in the water, but my goal was to install CyanogenMod... is this still possible?
Thank you in advance.
-Owen
-----------------------------------------------------
Installing a Custom Recovery Image
If the LG Nitro HD already has a custom Recovery Image installed, you may skip this section.
Search for ROM Manager in the Market (free or paid) and install the app.
Open the ROM Manager application and select Flash ClockworkMod Recovery.
Click on LG Nitro HD and then give the app root permission if it prompts you.
If it hangs after that and freezes up, just allow the app to Force Close. Then open it back up and repeat steps 2 & 3.
Once the flash was successful, you should see a dialog box that says "Successfully flashed ClockworkMod recovery!".
Press OK.
The ClockworkMod Recovery should now be installed on the LG Nitro HD.
Flashing CyanogenMod
If the LG Nitro HD has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the LG Nitro HD be returned to stock & start over with the full instructions provided above.
Method via Recovery
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Optional: Select backup and restore to create a backup of current installation on the LG Nitro HD.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The LG Nitro HD should now boot into CyanogenMod.
Method via ROM Manager
Launch RomManager.
Optional: Choose the first option in the app, Flash ClockworkMod Recovery to update to the latest version.
Select the Download ROM option from the main menu in the ROM Manager.
Select the CyanogenMod option, and then choose the latest version of CyanogenMod from the menu.
Optional: When you select the latest version of CyanogenMod, check the Google Apps option.
Once the ROM is finished downloading, it asks if you would like to Backup Existing ROM and Wipe Data and Cache.
If Superuser prompts for root permissions check to Remember and then Allow.
The LG Nitro HD will now reboot into the recovery, wipe data and cache, and then install CyanogenMod. When it's finished installing it will reboot into CyanogenMod.

LG has a locked boot loader, that is the reason for the security error. To get around that use the following unbricking guide: http://forum.xda-developers.com/showthread.php?t=2044645.
Since you already have root, just make sure you complete steps 1 - 3, then jump to step 9.
Sent from my LG-P930 using xda app-developers app

How unroot?

Hi to all. I got an used m8, i noticed is s on and locked but got root. How can i remove it? I tried with supersu with the unroot optiin but not worked. If i remove supersu app get root access without needed permissions. Thx

http://bharathsunny.hubpages.com/hub/How-to-Root-HTC-one-M8-Step-by-step-Guide
follow the instruction.

Unrooting procedure:
Yes,there is an un-rooting procedure also for this mobile.We should appreciate the work done by the developers.To unroot,simply follow the steps below.
*Uninstall weak sauce app,
*Un-install supersu app.
*Do a ADB reoot for your device.
That's it.Your phone has been successfully unrooted.
Click to expand...
Click to collapse
I tried to unroot my phone using the unroot option in SuperSu but after a reboot its still there. Best way i found was to use TWRP recovery mode. Make sure thats installed then....
Boot your phone to TWRP recovery mode by turn off your phone then presses Vol up + Power to boot into bootloader then choose RECOVERY. There is a more simple way, by using “adb reboot recovery”.
Once came into TWRP main menu, now tap Mount -> Mount system then taps Home.
Tap Advanced -> File Manager, browse to “/system/xbin” folder. From there delete su, daemonsu or busybox if it exists. Also browse to “/system/app” the get rid of Superuser.apk.
Hope that helps

thx to all, in the end i finally choose to re root with aio toolkit and put android revolution rom

"superuser binary is out of date" but wont update

i just rooted my s6, and i DO have root access, but when i try to open superuser (that was installed along with the root) it says "superuser binary out of date" and asks how i want to update it. The only options it gives me is Cancel and Recovery. If i choose recovery it boots into recovery then does nothing. I found the updated version of superuser online and transeferred it to my phone and flashed it thorug TWRP. Still says it. I tried installing supersu and when i open it it says "su binary is occupied" so i used an uninstaller to uninstall superuser, and supersu still says binary is occupied. So i reinstalled superuser but now i dont know what else to do to get my superuser app to work? Any ideas? TIA

I don't know how comfortable you would feel about this, but a lot of us have moved on to using Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
There are two parts, Magisk itself and the Magisk Manager.
Recommended path is to return to Stock, install TWRP via Odin but don't reboot. Instead shut down, reboot directly to Recovery and flash Magisk. Usually on first boot you will get a prompt to install Magisk Manager, do that and you are set.
Before you do that, take some time to read about Magisk. It is similiar to SusperSu, but allows you to conceal that you are rooted. (A feature that you enable within the manager.) I find it a great improvement.

ohhhh. i get it now. the method i used to root was with magisk. it prompted me to install it when it booted up so i did but didnt really go look at the magisk manager. i didnt realize that was what handles the su. thats why it says its occupied

can't install Magisk

tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?

Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.

no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.

metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.

uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.

Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?

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.