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

Troubleshooting GT-i9082 Galaxy Grand Duos Bootloop/BootScreen strucked

Greetings users,
I am new to XDA but when I was looking around here and there i found that users has been facing several issues regarding bootloop or bootscreen struck problem. Then I found people on facebook struggling from the same problem. So what I lastly found is a basic and easy solution for this.
Follow these steps and it will take you out.
1) Firstly install Philz Touch Recovery so that you could enter custom recovery menu to make some patches.
Please note: You might need to enable USB debugging to install Philz Touch.
2) Now after you have installed Philz Touch Recovery, Go to recovery mode.
* Wipe Data/Factory Reset
* Clean to Install a New ROM
This will clear the whole things in the smartphone that needs a change.
3) For security, once again, Clear Cache and Clear Dalvik Cache.
4) Now everything has been cleared from the smartphone.
5) Now, make a reboot in recovery again and install your ROM from ZIP.
Note: What I have found is that, you have to put the ZIP file in SdCard1 or extSdCard outside any folder. Generally the recovery don't take it from the folders and might cause some bug.
For those who are using TouchWiz Revolution 7
It has some serious bugs and issues, I have tested it on specific more than two or three GT-i9082 devices.
I have also reported some bugs from it, please have a look over them HERE.
Anyone who got a bootloop/bootscreen struck, follow these.
1) Firstly install a Stock ROM of GT-i9082 using ODIN.
2) Now open and start the phone (it will take sometime to open and the stock rom will patch the original odex and library files)
3) Now Go to Settings > About > Click 6-7 times on Build to enable Developers Mode
4) Now Enable USB Debugging and Allow Mock Locations from Developers Options.
5) Now Install Philz Touch Recovery using ODIN.
6) Enter the recovery menu and perform:
* Wipe Data/Factory Reset
* Clean to Install a New ROM
7) For security, once again, Clear Cache and Clear Dalvik Cache.
8) Reboot in recovery again and install TouchWiz 7 from external Sdcard.
9) Profit!
Note: Allow 4-5 minutes after you have installed new rom after Boot Screen starts.
QUICK LINKS:
ODIN v3.07
Philz Touch Recovery
There is a thanks button out there :good:

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...

I have the same problem

Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???

I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.

Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.

I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.

Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.

No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.

karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

startup problem after installing new ROM by TWRP

after receiving a phone with a problem Gyro sensors and aceelérmetre, I tried to solve the problem by installing twrp and trying other ROMs, but one moment the phone does not want to start and stays every time in the start screen installation infinitly
i still have access to twrp, and i tried all knowns solutions except flashing throw EDL mode
Please help me

More details required!
What rom did you try to install.
And before testing other roms. You should have checked that it wasn't a hardware problem (faulty device) with stock rom.
^^^ Tap on kernel version a few times in about would open a service menu, where it is possible to test hardware.
MIUI doesn't boot with TWRP installed if you don't flash lazyflasher or use a TWRP version that includes it.

Question: does your phone stay permanently in this mode? What rom did you install and what type of ARP do you have? What version of twrp do you have? I remember I had the same issue because I force encrypted my phone accidentally but then it just didn't start sometimes. That's why I am asking.
Option 1: go back to twrp -> format your device (should erase all sort of encryption and it has the same effect as a factory reset as well) -> reinstall custom rom and your stuff again -> flash lazy flasher or Magisk (that should take care of dm verity & force encryption as well).
Option 2: check your ARP version (fastboot getvar anti) custom roms usually don't have any firmware whatsoever and as long as you don't downgrade you are safe anyway. Just to be safe: if you are on version 3 everything should be fine, if you are on 4 you have to do some research what to do but it's not a big deal to be honest.
Option 3: Install redwolf instead of twrp (then you don't need to flash lazyflasher as well) -> install rom.
Tell me if anything has worked.
Installing recovery either via fastboot flash recovery recovery.img -> power off -> power on + volume up -> allow modification to system partition.
Or do it like fastboot boot recovery.img -> install (in your recovery) -> select image (bottom right) -> flash recovery.img (works especially good with ARP v4)
Either way after that do your thing in case you want to change/update your twrp or redwolf.

Boot screen problem
I am using orange fox recovery r10. When i flash havoc os 3.0, evolution x os and other os it always stuck in boot screen. It just opens with the pixel experience rom only. And when i tryed to restore my phone rom it shows "mount read only" . I am using redmi note 5 pro (whyred). Please help me to solve my problem.

if i were you, i will boot to twrp - boot to fastboot - flash miui using fastboot. if you're not confident google how to do it.

Instructions for keeping twrp and root after updating the UL USER rom:

1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken

This did not completely work for me going from .35 to .64. All the steps completed successfully but when I rebooted the phone, Magisk was not installed so I didn't have root. I was able to then boot to TWRP and successfully install Magisk, but I don't know why it didn't work the first time. Anyone else try this? Did it work as intended for you?
One other thing I noticed - TWRP no longer has an option to wipe the cache under wipe > advanced, only for Dalvik/ART cache. Why?

Wish I would have tried this before i updated and lost root, i flashed a root boot.img with fastboot now im bricked and don't know what to do.
EDIT: got twrp did a factory reset and im in now.

dungnghien said:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
Click to expand...
Click to collapse
In my experience after install back twrp reboot back to recovery (twrp) before flashing magisk .

Does this work when updating to A10?