Develop Bugs

Can't seem to update to MA7

It seems my phone is stuck on ALJC. I flashed the stock recovery via Odin and did a temp unroot, downloaded the OTA update. The phone rebooted and went to the stock recovery and appeared to be installing the update. Upon reboot, my phone was back in rooted condition (not sure if this is normal for voodoo unroot or not). This has happened twice. The first time it happened I had not noticed it, but now that it has sent a second update request to me today, which I used the same method only to discover that it doesn't seem to work. Now when I request an update it tells me no update is available. Suggestions?

Ignore this thread, I said screw it and just did it all manually.

Dm-verity fail?

Got my Note 4 rooted it right away with no issues been running smoothly for a week or so. This weekend it has just got into a bootloop several times, the only thing I have been able to do is wipe data and start over. I mean I have Titanium Backup of all the apps but it is still a hassle. The only thing I have noticed is in the stock recovery it says "dm-verity failed"
I have read running a non-stock kernel will take car of this but not sure this is the issue. Has anyone else had this issue or have a solution?

It's the root. That root is causing that error to pop. Un-root your device.

I am trying to correct this issue as well for s friend who bought a used note smn910p.
It boots up
Its in the abnormal factory reset, reactivation loop i have to provide samsung account from unknown previous owner
rooted s5 smg900r4

fixed dm verity issue using kies3, updated firmware and initialization option.
rooted s5 smg900r4

Random restarts and then asking for a password (that doesn't exists)

Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.

Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk

Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.

LG G3 with cm-13.0-20161002-NIGHTLY-d850. Issues faced, guidance required.

New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S

Random Reboots and other strange things

Hello, I think I have a really strange problem. I'm running Exodus 6.0 (and I made a full and fully functional backup that worked without issues) and yesterday I wanted to install AICP 12.0 (Android 7.0).
So I did a clean flash, but the SIM card detection didn't work and baseband showed up as "unknown" (according to the AICP members, I am the only one with such an issue).
So I tried several times but no success. They told me that it could be a problem of the 20G modem and bootloader. So I decided to revert back and since then I only have problems.
This is what I've done: Firstly, I flashed the 20D kdz. The phone booted fine. So I tried to install TWRP through ADB. (The phone was recognized and I was able to perform ADB commands). So I booted to bootloader, typed in the commands, but....nothing. TWRP didn't boot and I couldn't install it, no matter what I've tried. No I was on stock Rom without root and custom recovery, so I decided to revert back to Lollipop. I flashed the 10c kdz, flashed the rooted system image, wanted to flash TWRP (3.0.2-1) via Flashify, no success. Not until I tried TWRP 3.0.2-0, I had success and TWRP has been flashed. So ok, all fine now I thought, so I flashed the complete 20D stock Rom via TWRP, booted it up, worked. Now I wanted to give AICP a try again. So again installed, again no SIM card detection. With the CM 14 nightly 10/21 flashed afterwards (always clean flashed), success! SIM card was detected fine. So, again AICP tried and surprise, SIM card was detected as well. But now I had new problems: When I flashed SuperSU, SIM card wasnt't detected again.
Without SuperSU and stock AICP kernel, I suffered random reboots while setting up the WiFi connection in setup wizzard. Without SuperSU and Llama Sweet R7 kernel, I suffered a system crash and got a green screen saying something like "App F1Q: XPU Error!". So after some time I gave up and wanted to clean flash Exodus again, again no success, because the setup wizzard stopped (unfortunately:laugh:).
So ok, last rescue: My full backup. So I restored it (Exodus 6.0 10/22 nightly, opengapps pico 10/23, SuperSU SR1 2.78 in systemless mode, systemless xposed v86.2) and seemed to work fine. Today, I wanted to run SafetyNet Helper, and the phone suddenly rebooted. I wanted to run Pokémon Go, the phone suddenly rebooted. Nova Launcher can't get permissions for showing up unread labels correctly (though I have Nova Prime and all permissions are granted for sure!), other apps seem to work correctly. But all in all it's very strange because I have the feeling that somethink went completly wrong. So I don't know what I've done wrong, what do you think about this?