Database Info

[RECOVERY] TWRP 2.8.6.1 for D80130b

Hey guys,
Using a guide for the g3 by @topet2k12001 i was able to get permanent recovery working for our d801's running the new 30b Lollipop. I compiled the necessary files into a flashable zip for you all. The zip contains bump'd lollipop boot.img, kk aboot.img, and twrp 2.8.6.1 recovery.
as always... FLASH AT YOUR OWN RISK
Prerequisites:
- Running Stock D80130b
- Rooted
- Autorec installed
Getting Started:
- Copy TWRP-2.8.6.1_D80130b.zip to your phones storage
- Run Autorec and flash TWRP (2.7)
- Reboot to recovery
- Flash TWRP-2.8.6.1_D80130b.zip
- Enjoy!
You should now have a permanent recovery.
DOWNLOAD:
Twrp for d80130b:
https://mega.co.nz/#!qFUDWC4a!nHj3R-gPAEqvZ-yLcQMZxXvTN8eFJg99vWfopnCjR_w
Stock d80130b bootstack + recovery: (flashes stock recovery in case anything goes wrong)
https://mega.co.nz/#!KI9k1YxT!HDJEDSd0X1MEsdr5oiNdutg0aADuqB3A1XrNQUjsqrQ
Credits to @blastagator for the Recovery and @Cloudyfa for Autorec

Great work man...i had a feeling you would bring us a working fix

Was going to try this and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nalanotae said:
Was going to try this and got thisView attachment 3241785
Click to expand...
Click to collapse
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions

Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?

Thanks very much!! Works great
Sent from my LG-D801 using XDA Free mobile app

snowlin said:
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Click to expand...
Click to collapse
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response

Messip3 said:
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Click to expand...
Click to collapse
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.

nalanotae said:
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Click to expand...
Click to collapse
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery

Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?

snowlin said:
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
Click to expand...
Click to collapse
Alright man...thank you.

mjoecarroll said:
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
Click to expand...
Click to collapse
I pulled the aboot.img and laf.img from 20e , bumped the stock lollipop boot.img using a guide i found in the g3 forums and packaged it with twrp 2.8.6.1.
I'm not super experienced or anything but this kind of stuff interests me so i learn as i go

That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.

mjoecarroll said:
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
Click to expand...
Click to collapse
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.

snowlin said:
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
Click to expand...
Click to collapse
Worked just great, thanks a million.

snowlin said:
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Click to expand...
Click to collapse
That was my plan....... When i first flashed this rom i had no problem with installing autorec but then i got the security error.. So i just flashed kdz then rooted and set the phone up...... Can't wait to get all this going.... Really untested to see how sins if these custom roms run with new radio

Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem

jamesd1085 said:
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
Click to expand...
Click to collapse
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?

snowlin said:
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
Click to expand...
Click to collapse
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk

jamesd1085 said:
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
Click to expand...
Click to collapse
maybe try flashing blastagators twrp package for the 801 : http://blastagator.ddns.net/twrp/2-8-6-1.php
even though this is what i used in mine anyways, it's worth a shot. You will still be able to boot after flashing this since it is only recovery.

S6 Bootloader and Modem Odin Flash Failed Red

Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
you phone g920i?

agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.

furkanndk said:
you phone g920i?
Click to expand...
Click to collapse
Yeah sorry i mentioned its Samsung SM-G920i

bininga59 said:
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.
Click to expand...
Click to collapse
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?

agentdangermouse said:
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?
Click to expand...
Click to collapse
Actually issue is resolved, i installed Samsung Phone Info from app store and i double checked my bootloader and modem installed i am already running latest bootloader from here http://forum.xda-developers.com/galaxy-s6/development/g920i-bootloader-modem-updated-10-10-t3221796
So i guess the fact is i cannot downgrade maybe thats why this is the issue. So i think all is ok
Thanks for the assistance

[ROM] SU4TL-49 100% Stock

SU4TL-49 Stock Image for XT1254: https://mega.nz/#!TwYShBCb!OFxwiUnUO2MiOHEVc8XluNP1uPSf5tTBaVdmyZ-mwSA
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
If you get errors while flashing this, try using TWRP Mod 3 instead of Mod 4.

Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...

Nice! Thanks a lot!

rjansen110 said:
Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...
Click to expand...
Click to collapse
1. Yeah, that's kind of what I meant by the last sentence of the OP.
2. That always happens whenever you go from CM to stock. It's harmless.

So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app

joeriv5692 said:
So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.

TheSt33v said:
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.
Click to expand...
Click to collapse
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?

Glad to see the return of @TheSt33v !! Thank you for your work!!
joeriv5692 said:
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?
Click to expand...
Click to collapse
the answers to "one more thing":
1) yes, if you flash stock recovery it will take TWRP off. 2) it will not relock your bootloader.
edit: ****** 3) it will *not* take away all traces you have modded/hacked/rooted
Stock.
NEXT DAY EDIT: i just restored pretty much stock 5.1 su-44. after all the uninstall crud there, i booted to twrp, and flashed this. all went perfectly. Thank you @TheSt33v !!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[emoji92] [emoji95] [emoji95] [emoji95] [emoji95] [emoji109]
edit again: same line added to build.prop enables tethering on this build too.
net.tethering.noprovisioning=true

kitcostantino said:
Glad to see the return of @TheSt33v !! Thank you for your work!!
Click to expand...
Click to collapse
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.

TheSt33v said:
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.
Click to expand...
Click to collapse
TheSt33v said:
Now that we've got some Sunshine in our lives, sadly (not really) it is time for Turboid to be retired. We don't need it anymore.
I think that about covers it. Go forth and flash! Thanks for letting me play dev for a few months
Click to expand...
Click to collapse
Ha ha, brother. I guess i just took this post in the Turboid thread wrong.
-King of Unsolicited Advice

I did a system-only backup in TWRP after updating, so I don't think I need this, buuuut, never hurts to have a 2nd option! 44 did save my bacon so update was possible. ?

Thank you for the De-Odexed build!!!
-King of Unsolicited Advice

Has anyone had issues w this ROM or is it all good?

its all good.
-King of Unsolicited Advice

No luck with de-odexed version
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.

yeah, i can confirm. same issue. the fix was wiping data for the app via TiBup. i use a transparent google drive, though, and had presumed it was just me.

sgeek7 said:
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.
Click to expand...
Click to collapse
Weird. I forget, is Drive a system app in the stock rom? If so, maybe try removing it altogether with TiBu and reinstalling it from the play store?

It might be. The non de-odexed version is having no issues on my phone. Thanks for the idea just in case.

Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?

Is anyone having issues with the play store crashing everything you start it up? I flashed the de-odexed and non-de-odexed but play store keeps crashing every time. Any ideas?
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
snugroho3 said:
Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?
Click to expand...
Click to collapse
It's included

Your device is corrupt

I tiried to flash the new oxygen pie beta. For whatever reason something went wrong and now here I am.
First time i flashed the beat I got the "Your device is corrupt" error. It's not the typical unlocked boot loader error. The explanation point is red, there is no mention of unlocked bootloader and I need to press power button in order to proceed. I tried flashing again at this point and I wiped everything in TWRP, but that didn't help.
Afterwards I have decided to go back to oreo and just upgrade to pie by local upgrade, but after flashing oreo I still get the red "your device is corrupt". However, I can still boot to the oxygen os and it seem to be working fine.

think its the encryption so reformat the data partition and start from scratch

RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
Formatted data and wiped everything. Flashed the pie beta. I can boot to the os, but I still get the error..

RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
I am decrypt and still get the same warning. I'm sure it'll be fixed later.

mikex8593 said:
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
Click to expand...
Click to collapse
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails

Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.

Can you post the link to the file?
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse

Guess it is actually form Oneplus site:
https://forums.oneplus.com/threads/...ficial-oxygen-os-roms-and-ota-updates.835607/
In rollback builds under Signed flashable zips (Android P Developer Preview)

Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nameless said:
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/one...ional-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
View attachment 4587785
Click to expand...
Click to collapse
The URL you shared is giving 404 error
Please share correct URL

https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again

:good:

soldier1 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
Click to expand...
Click to collapse
So you are now back to P beta 1 without the error? Hmm. I got my phone back to 8.1 without the area. But once I flashed it again, the same thing came back.
Thanks
Ended up using qualcomm tool, then flashed P beta 1, then unlocked bootloader, installed twrp, installed magisk7. Everything is good now.

Flashing stock didn't help me, I still had the error. I used the qualcom tool and now I'm on pie without the error.

Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Also had the same and flashing back the roll back package fixed it, definitely keeping this zip!

Spoke too soon got the corrupt message after going back to 5.1.11 then to oos beta 1 so had to use the unbrick tool instead.

my guess is that the bootloader can not tell if phone is bootloader locked or unlocked. Has any1 tried flashing the bootloader files to see if that could fix it without debrick tool?

mati11233 said:
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Click to expand...
Click to collapse
No its not, safetynet will not pass, says so even in changelog

Yeah i got the same error, only solution for me was to use unbrick tool

Flash OOS Beta over H2OS beta, no need to wipe data between the two. But it works wonders.

Question Ramdump Mode

Good time of the day, for some reason my phone began to get into Ramdump mode quite often, Is it because of the reusable firmware? And what can be done to fix it? Also a note, I can't flash it through the Archive, it writes an error with the Super file, but if I start flashing it through Android Flash Tool, then everything is fine

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What rom are you using?
And when is this happening?

Ghostcain said:
What rom are you using?
And when is this happening?
Click to expand...
Click to collapse
This happens on any firmware when I start unlocking the screen with my fingerprint

It may happend due to bad memory from the device

Ghostcain said:
It may happend due to bad memory from the device
Click to expand...
Click to collapse
90gb free

I mean bad RAM maybe it crashes and dump the errors

Ghostcain said:
I mean bad RAM maybe it crashes and dump the errors
Click to expand...
Click to collapse
maybe) idk how fix it

Ghostcain said:
I mean bad RAM maybe it crashes and dump the errors
Click to expand...
Click to collapse
Now I will try to install a custom kernel, maybe something will change

Is this happend on stock rom to?

Try to reflash Kernel only...
It clearly says Kernel Panic which mean kernel is the problem..
Try installing Stock ROM

Max0nchik said:
View attachment 5873071
Click to expand...
Click to collapse
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.

nathanxbox911 said:
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.
Click to expand...
Click to collapse
I have an assumption that this is due to problems in slots A B, most likely some module broke them. In my case, this especially often pops up if you put a root

nathanxbox911 said:
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.
Click to expand...
Click to collapse
Once FPS stops working its broken for good. In almost all cases its a result of flashing something that corrupts/trips the Titan security chip. Mine hasnt worked in months.

ctfrommn said:
Once FPS stops working its broken for good. In almost all cases its a result of flashing something that corrupts/trips the Titan security chip. Mine hasnt worked in months.
Click to expand...
Click to collapse
Bro, were you able to fix this?

Max0nchik said:
Bro, were you able to fix this?
Click to expand...
Click to collapse
No, there is no fix apart from sending it back to Google (or wherever you got it)

ctfrommn said:
No, there is no fix apart from sending it back to Google (or wherever you got it)
Click to expand...
Click to collapse
Thanks for the information, but it sucks to know...

Once Titan is tripped its not really fixable as far as I can tell.