Database Info

Touchscreen x axis reversed

I accidentaly flashed the edge version of twrp to my regular s6, 920r4. Now my touchscreen is reversed along the xaxis. When I dial *#2663#, nothing happens, only a dialtone goes on. Any suggestions?

Reflash regular S6 5.1.1 stock ROM via odin.

I did that, still no fix. Then I did a full reset, no fix.

Bring your S6 back to Samsung for repair.

roydok said:
Bring your S6 back to Samsung for repair.
Click to expand...
Click to collapse
Obviously my knox is tripped after flashing TWRP, would samsung be able to fix this anyway?

I hope so...

In other related threads, members were able to use the "secret codes" to update the TSP firmware. Could I perhaps install say the firmware for the 920F, then access the secret codes on that firmware, and in that process update the TSP firmware?

Flash this S6 regular S920R4 5.1.1 stock ROM instead of G920F:
http://www.sammobile.com/firmwares/download/48614/G920R4TYU2BOF7_G920R4USC2BOF7_USC/

Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.

This did not do anything for me. Could i just use the right one instead and all should go well? or there be another solution?
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse

I finally got this issue fixed after almost half a year. I updated the firmware to a newer version, using the software update on the phone. My issue is finally fixed. I think that perhaps the several months new software update was different enough to require a complete changing of the recovery software.
Or at least something like that!
No longer will I be using my old s4, running liquidsmooth, that restarts 3-4 times a day. With a shattered screen at that!

Resurrecting the Thread
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)

Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse

wolkowicz said:
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Click to expand...
Click to collapse
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.

After rebooting my phone couple of times it works. Thanks!!!
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
Ishmael89 said:
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
Click to expand...
Click to collapse

wolkowicz said:
After rebooting my phone couple of times it works. Thanks!!!
Click to expand...
Click to collapse
No problem, glad it worked out and you can use your phone regularly now!

As I have found multiple threads for the same issue, I figured I would post the info in a few of them so if anyone else come looking for the issue and fix - they can get right to the howto instead of digging through multiple threads like I did. More info about the issue was found on the following link/s - https://1024kb.co.nz/galaxy-s6-reversed-touchscreen/ & https://forum.xda-developers.com/showpost.php?p=62289392&postcount=9
You DO not have to flash any stock roms or other versions of twrp to fix this, as it will NOT fix the issue, as near as I can tell something corrupted or changed the setting somewhere on the hidden section of the phone's firmware. All you need to do is access a hidden engineers menu, click on a button and your done.
The hidden adjustment setting is accessible through keypad *#2336# (reverse-entered as #*2114*) (you have to do this as the touchscreen is still reversed so you are unable to enter *#2336# normally). Once the task completed I then was able to press the back key and have it function as normal which confirmed the fix.

Phone powers off after flashing CAF based ROMS no boot.

Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(

Maybe don't flash supersu? Cm comes prerooted?

audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.

Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs

Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!

I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model

I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.

since i dont own the device.... no logs= we cant help you

Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...

I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?

I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(

Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?

Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.

Let me guess. All your phones have been repaired or are second-hand devices, aren't they?

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?

Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.

experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?

Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.

Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...

Camera Issues, cant understand what's wrong?

I am not able to understand these white/blue spots across the images. Please see the attached images and zoom in to look in the highlighted areas. It's not dust for sure as I have cleaned the lens and the photos were shot in auto mode (no change in ISO etc). IS there an issue with Nougat beta camera or is my sensor damaged?:crying:

What variant you have (L09 or L04) and which firmware you're running (B1..)?!

I am sorry for hijacking this forum, but I have an Honor V8 variant (the big sized version) with EMUI 5.0. beta. There is no xda forum on this model, hence I posted here. I am not sure if the s/w is the issue as I tried it with other camera apps as well producing the same issue

try a 3rd party camera to see if it is still there, if so try reflash stock rom.

If 3rd party apps don't work, then look if there's an update for your phone

I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?

linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
yes it is probably a hardware issue, but you will have to flash stock to completely rule out a software issue. back up data using twrp

linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Its a 50 50 situation, some early buyers of honor 8 had the same issue, but after an OTA it's gone.
If it's a hardware issue, return it back if you have warranty.

A friend of mine had the same issue but it was fixed after the update.

Neil6684 said:
A friend of mine had the same issue but it was fixed after the update.
Click to expand...
Click to collapse
Do you mean those spots on zooming in? I have been through 2 beta-Nougat updates, but its not yet resolved. I will factory reset over this weekend and check.

linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.

Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?

linom said:
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
Click to expand...
Click to collapse
It's a software issue, don't worry.
If RAW images are fines, then it's just a problem of processing when taking a JPEG photo
An update should fix this

DarkGuyver said:
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Click to expand...
Click to collapse
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.

linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
It's better for you, and when you buy a device make sure it's officially supported in your country (like honor 8) .
All the best

linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
I'd contact Honor directly and ask them about the problem. Maybe they will release a software patch for it. But I have never heard the Honor 8 had this problem.

I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.

Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.

linom said:
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
Click to expand...
Click to collapse
Unfortunately, we don't know the exact files (libs that are responsible for image processing)

linom said:
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Click to expand...
Click to collapse
You would have to contact Honor directly for instructions on how to restore Marshmallow back onto your device. They will also be able to provide you with a link to the Marshmallow firmware for your device.

Problems with my Xiaomi Redmi 8A

Hello people of XDA Forum,
Since a couple of years I own a Xiaomi Redmi 8A, which I ordered brand new on AliExpress.
After a couple of failed attempts to install a Custom Rom on the device, I still have an unlocked bootloader
and a "offical" stock firmware on the smartphone installed. Sadly now occurs an other problem,
frequently the screen "freezes" when I want to use the touchscreen. Sometimes when I put the power-button
and pressing it another time the screen responsed to it. But not always, it's getting very frustating when
for example I play "Call of Duty Mobile". My question is that I want to know of the problem is software-
or hardware based? Hopefully you can help me out, thnx

Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.

XDHx86 said:
Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.
Click to expand...
Click to collapse
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.

TrippyBlade said:
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.
Click to expand...
Click to collapse
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.

XDHx86 said:
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.
Click to expand...
Click to collapse
Allright, thank you very much for the suggestion. Finally I managed to flash an older Fastboot ROM through
the "MI Flash Tool", which solved my touchscreen problems.

Question Occasionally crash to "waiting to flash full ramdump"

Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance

Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.

vinotux said:
Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance
Click to expand...
Click to collapse
Did you flash the DLKM module?

MarekPietrzak said:
Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.
Click to expand...
Click to collapse
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.

twistedumbrella said:
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.
Click to expand...
Click to collapse
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message. When I restored stock kernel, this issue no longer persisted. I will for sure try again custom kernel, but in two weeks or longer, as ROG phone 5 is my primary device and I need to stay in contact. I will try to reproduce this issue and grab logs. Now I can share my observation, that those crashes occurred when device was idle, and usually on charger.

JazonX said:
Did you flash the DLKM module?
Click to expand...
Click to collapse
Thanks for your response, do I need to? I flashed using FKM and not TWRP

vinotux said:
Thanks for your response, do I need to? I flashed using FKM and not TWRP
Click to expand...
Click to collapse
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
MarekPietrzak said:
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message.
Click to expand...
Click to collapse
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.

twistedumbrella said:
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.
Click to expand...
Click to collapse
Great, I'll just reevaluate when the new update rolls out, thank you .

vinotux said:
Great, I'll just reevaluate when the new update rolls out, thank you .
Click to expand...
Click to collapse
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.

twistedumbrella said:
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.
Click to expand...
Click to collapse
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .

vinotux said:
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .
Click to expand...
Click to collapse
Fair enough. It shouldn't be on you to do it anyway. With any luck, i'll have debugging sorted out before the end of the weekend with proper instructions to avoid all the guesswork.
Asus Proprietary Logs
In trying to debug kernels, I realized that Asus has rerouted the location of some of the more important logs to make them "easily" accessible. Disclaimer: This is not a complete list of every file included, but lists the more "useful"...
forum.xda-developers.com

An error happens, the kernel logs the issue, the device reboots. This is how things are supposed to work. When disabling debugging, an error happens and the device reboots. The logging step is skipped, but life continues.
The problem is when debugging is partially disabled, but still attempting to write. This is basically why there is a "waiting for ramdump" message. It is waiting for the logging to complete to proceed to the next step.
Asus Power Debug: guard debugging so it can be disabled · freak07/[email protected]
Contribute to freak07/Kirisakura_ANAKIN_ROG5 development by creating an account on GitHub.
github.com
This commit set the stage for a future break, which happened in the .176 update when printk_buffer_rebase replaced get_last_shutdown_log.

Hi, just a quick update.
I had been experiencing major issues and the waiting to flash full ramdump debacle had gotten extremely frightening. The phone wouldn't recognize the IMEI of the device, wifi wouldn't work, etc. The error happened multiple times a day. I took it to ASUS and they basically told me to f off due to my phone being unlocked.
As a last resort, I flashed the .151 RAW firmware and I swear all of the problems vanished. If I was a betting man, I'd say that the .176 update caused all of the problems since I've used the device for a week now without any problems thus far.
Major thanks to @twistedumbrella and others for replying to this thread.

I don't doubt you are right about that. 188 improves things a bit, but they definitely broke something significant in 176. I have never crashed as much as on that build.