Database Info

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...

[6045O] Attempting to upgrade to Lineage 13

Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?

If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.

magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.

Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.

magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.

I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.

Set Warranty Bit: Kernel & Set Warranty Bit: Recovery

Good afternoon,
I have a N915FY with marshmallow 6.0.1. I had the Rom installed [ROM] [AROMA] Multi-CSC] Micky387_MM_V3.0 for 915F-FY-G, with which I was delighted, but did not fall into the error message until the battery began to cause problems. Following the steps:
- I tried to install the [AROMA] Multi-CSC again] Micky387_MM_V3.0 for 915F-FY-G, the file Micky387_MM_V3.0 for twrp recovery, but nothing else restarting the error still appears ... and after testing all the kernel I saw, nothing at all, so .. next step
- Install the rom of SamMobile N915FYXXU1DQB2_N915FYPHE1DQB1_PHE, which is the latest version to date, the PHE Black Edition. So far the new phone and without errors.
- Problems begin when installing twrp-3.1.1-0-tblte.img.tar, latest version today with Odin307, Odin_V3.09, odin3_v3.11.1, odin3_v3.12.7 ... and already appears when entering recovery the error "Set warranty bit: recovery". I also installed TWRP-3.1.0-for_915F_915FY_915G.tar, twrp-3.0.3.1_915F_915FY_915G.zip ... with the same result. The truth is that the error of the recovery I think gives a little the same, the problem is the kernel.
- Install the file SuperSU-v2.82-201705271822.zip, latest version today, and restart if "Set warranty bit: Kernel" appears .....
I ran out of ideas, time (I've been with the phone for 2 days, reading and understanding) and I do not know what to do.
I do not want to finish the post without thanking the work of all the experts who, unintentionally advise and support us.
Thank you very much.

Perhaps try RamKernel in the forums, not my favorite but works. I can also say AKLU works really well also. It is hit and miss with ROMs on this thing. I just got fed up and ordered a Note 8 Thurs. I cannot remember exactly it might be either a Signing issue or a SELinux issue. I'm wanting to say a signing, as it says something about SELinux. Its normally not an issue and a Samsung thing used for warranty/support purposes. I have never had issues, is there something specific other than this splash at boot?

I had problems because the battery only charged up to 67%. Then I read in a forum that this problem was due to a kernel error and I was investigating ... but I can not remove it in any way ...

martinetevfr said:
I had problems because the battery only charged up to 67%. Then I read in a forum that this problem was due to a kernel error and I was investigating ... but I can not remove it in any way ...
Click to expand...
Click to collapse
Normal for rooted phones. You can safely ignore it.
Sent from my SM-N915G using Tapatalk

arbit12 said:
Normal for rooted phones. You can safely ignore it.
Sent from my SM-N915G using Tapatalk
Click to expand...
Click to collapse
arbit12, thanks for solving my doubt. I remain calm

Downgrade from Nougat 7 to Oreo 8 G955FD

First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help

heider.raheem said:
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
Click to expand...
Click to collapse
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.

spawnlives said:
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
Click to expand...
Click to collapse
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays

heider.raheem said:
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
Click to expand...
Click to collapse
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes

spawnlives said:
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
Click to expand...
Click to collapse
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?

heider.raheem said:
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
Click to expand...
Click to collapse
Just curious what firmware version are you using.

spawnlives said:
Just curious what firmware version are you using.
Click to expand...
Click to collapse
i use now Oreo G955FXXU4CRI5

heider.raheem said:
i use now Oreo G955FXXU4CRI5
Click to expand...
Click to collapse
Is it working ok or still same problem

spawnlives said:
Is it working ok or still same problem
Click to expand...
Click to collapse
its froze right now it cant even get to samsung logo...and even if i flash the ROM again and get it work it will freez after maximum 600 hours (thats happened 3 times)

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.