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.
Related
Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.
Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.
Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?
I don't know exactly what undevolting implies. Could you give me more details please?
vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.
My n5 reboot today without any reason
That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.
So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work but here you go. Roasted Marshmallow, hot off the build server
EDIT: Title is probably wrong, as pointed out by a mod. I based it on the Git ref being "6.0_r1", which I thought meant "6.0.1". This is really 6.0. Specifically, a build based on the exact instructions posted by Sony.
MOD EDIT by @gregbradley
I edited the title for you .
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
thatguy222 said:
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
Click to expand...
Click to collapse
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Gairtial said:
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Click to expand...
Click to collapse
Bummer. Thanks for nothing, Sony!
thatguy222 said:
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Bummer. Thanks for nothing, Sony!
Click to expand...
Click to collapse
Don't jump the gun. There are a lot of files in a standard Android build and I don't know if it comes from them or if it's a product of the build process. It could just be a misconfiguration on my part. The bug is for info, not because it's their fault.
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
aniket_ said:
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Click to expand...
Click to collapse
I tried that last night using one of the files from the various vendor repos but no luck. The kernel module threw errors about the data being invalid. I'll try extracting from official firmware when I get home. Also that thread doesn't yet have anyone confirming that it works :/
fratzika said:
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
Click to expand...
Click to collapse
I don't have my Z3C with me so I'm unlikely to be able to do anything helpful for ~9h, when I get home. You'll have to be a little patient
Okay, got a build up to date with Git and with a modem copied from one of the latest firmwares (ripped it from the SLIM stock ROM). Wouldn't get your hopes up but it might work
EDIT: No luck. It doesn't seem there's an available modem that's likely to work. Unless someone can suggest another device with close enough hardware and a working Marshmallow modem (seems doubtful), we're lost until someone can extract one from a legitimate Sony firmware or Sony releases it to us (seems unlikely).
Thanks for doing this Gairtail, let's hope you get it up and running soon (if Sony or someone else uploads the modem file..)
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
someone755 said:
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
Click to expand...
Click to collapse
Theliakos said:
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
Click to expand...
Click to collapse
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Gairtial said:
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Click to expand...
Click to collapse
I built on Novenber 5th, worked just fine. Just synced and started another build, but the November security update isn't here yet, bummer. (I reckon another 24 hours should do it.)
If you'd like, I can upload the build for you.
Apo14 said:
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Click to expand...
Click to collapse
I don't know for sure, but wouldn't flashing a stock FTF solve this?
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Also, not sure if you guys also get this, but I've been getting the dwc3-msm wakelock a lot. Happens because of kernel bug that keeps phone awake, thinking it's connected to a power source even after it's been disconnected. Drained my battery for 17 hours before I even noticed. I don't know if the official method with prebuilt kernels also has this, but I build the upstream sonyxperiadev/kernel repo myself. If you use a kernel source too, instead of using the prebuilt kernels, you could try picking this. Looks to be working for me, but it hasn't been merged yet, so take that as you will.
EDIT: Noticed this isn't upstream Marshmallow, but r1. Bummer.
You should really switch to 6.0.1, the 1.3.3 kernel is much better than 1.2.2 (and without the memalloc reboots caused by media/video). Though if you prefer not to switch, you could still add my uploads to the OP alongside yours if you want? That way we have 6.0 and 6.0.1 under one roof?
@someone755 so should i be able to extract those files without the need to flash?
Apo14 said:
@someone755 so should i be able to extract those files without the need to flash?
Click to expand...
Click to collapse
No reason to avoid flashing, really. Make a backup of system and boot, don't wipe userdata, and have a recovery image handy. Flash FTF, flash recovery, restore system and boot.
The only things that get updated are your modem and bootloader etc, your system and data stay untouched.
Though depending on when you last flashed an FTF, it may be a good idea to wipe your data in recovery before you flash (and back it up, of course). Some firmware can only be updated after Android has booted, like NFC for example.
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Apo14 said:
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Click to expand...
Click to collapse
I'm not saying it's best, but it could help you avoid potential issues. I don't know what all you've been doing with your device, so I can't make the call for you. Just telling you how it is.
This is a nice thread: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 You'll also need FlashTool if you go down this route, you can Google it to download.
EDIT: @Gairtial I have today's 6.0.1 source in a nice zip. https://www.androidfilehost.com/?w=files&flid=127723
There's also a folder with the kernels for 6.0.1/7.0/7.1 that I'll try to keep up to date, if there's any interest for that. (The kernel zip will flash to any of the three Android versions, so long as the ROM is AOSP-based. Other than that, it's version-independent.)
Another note would be that I didn't make any changes to the ROM build. GApps will have issues starting unless you do some adb wizardry, and you'll get your recovery overwritten with the useless AOSP one if you flash the ROM zip in recovery. (You could also just try flashing system and boot through fastboot, though I haven't tried.)
someone755 said:
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Click to expand...
Click to collapse
I'm tired of using stock Sony roms, and I'm starting to hate them. Still waiting for those latest camera blobs though for AOSP. I've tried your uploaded build, but it's causing a bootloop somehow. Didn't flash the separate kernel, but I don't see the need for that since there is one included in rom zip. Not sure what is the problem...
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...
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Modzmarvin said:
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Click to expand...
Click to collapse
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Modzmarvin said:
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Click to expand...
Click to collapse
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
The modem i currently have installed is from the 7.1 stock ROM but i think what ill do is download the latest 7.1 and try and see what if it has any improvements as it has been a few months since i flashed the 7.1 modem so there could possibly be an improvement in one of the latest updates.
Truly hope so because although lineage it disconnected often, it would reconnect rather easy but resurrection its become a right pain cause its making me turn the wifi off and back on again before it can find any wifi around me!
Thanks for the links pal, I'll give it a shot once i finally manage to download the ROM lol
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Updated the modem. Now to wait and see if it any better haha. THanks for the links!
Found it was super simple to do.
Pulled the tar.md5 apart with 7zip and then zipped it back up with 7zip and it flashed with odin nice and simple . Links are useful for the img files tho! also good to learn from!
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Modem updated and still getting random wifi drops
Modzmarvin said:
Modem updated and still getting random wifi drops
Click to expand...
Click to collapse
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Modzmarvin said:
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Click to expand...
Click to collapse
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Droidriven said:
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Modzmarvin said:
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Click to expand...
Click to collapse
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out ?. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Modzmarvin said:
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out [emoji58]. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Click to expand...
Click to collapse
Once you get flashed back to stock and then get TWRP installed, make sure you make a nandroid backup before performing the next step, if the issue starts, you can restore the backup and be back to what you had before performing that step. Each time you successfully step up without issues, make a new backup and remove the backup from before that, then perform your next step, always keeping a backup from just before that step.
Sent from my LGL84VL using Tapatalk
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.