Develop Bugs

Would like to know what happened?

I was using my phone flashed with Mokee Nightly rom and everything was working great until the screen stopped working for no obvious reason. It happened yesterday, I tried to use the phone and the Home button didn't open the screen anymore. Then, I tried to reboot the phone but all I could see was the blue led flashing as if the phone was booting but there was nothing on the screen. When I got back home, I tried to repair the problem and I was able to enter download mode, so I used that opportunity to reinstall the factory firmware with Odin. I was able to get it working but I'm just wondering what was the cause of this? I know I'm a serial flasher so maybe something got ****ed up while flashing it and it caused it to bug later?

Nico3d3 said:
I was using my phone flashed with Mokee Nightly rom and everything was working great until the screen stopped working for no obvious reason. It happened yesterday, I tried to use the phone and the Home button didn't open the screen anymore. Then, I tried to reboot the phone but all I could see was the blue led flashing as if the phone was booting but there was nothing on the screen. When I got back home, I tried to repair the problem and I was able to enter download mode, so I used that opportunity to reinstall the factory firmware with Odin. I was able to get it working but I'm just wondering what was the cause of this? I know I'm a serial flasher so maybe something got ****ed up while flashing it and it caused it to bug later?
Click to expand...
Click to collapse
With custom ROMs, especially nightlies, errors like this are not to be unexpected. Recall it is still undergoing development and may not be bug-free. If you must stick with this ROM, I'd suggest you wait for the stable now that you know what may happen.

[Q] Touchscreen and sim reader both stopped working at same time

I have the ATT sgh-i747. I was using it as normal. The battery was low and i could not charge it before it got to 0%. After it died, I connected the charger and started it back up. When the screen came on, the "no sim-emergency calls only" message was there and the touch screen did not work. Also, the time and date were off. it said 3:59 September 15th. I tried the normal reset (take battery out, replace, turn back on) several times and still the same thing. I had just replaced the sim reader a month ago, as well as the rear camera and speaker, and everything was working as normal. I opened the phone up to make sure all connections were set. Still the same message. I did a factory reset and after I turned it on, still, the touchscreen does not work and it says no sim. I find it odd that both these things would stop working at the exact same time. Also the phone is long past its warranty. Any ideas on what this could be?

Anyone?

Have you tried flashing another ROM?

I don't know how to do that, if you could point me in the right direction I'd appreciate it.

Before anyone can give you advice, we need as many details as you are able to provide.
Was your phone running a stock ATT ROM? What ROM was it running? Are you able to boot into download mode?

Stock Rom, phone is not rooted and I can boot to download

What stock ROM? It's important that anything you flash does not try to downgrade the bootloader if you were on stock 4.3 or 4.4.

I'm not 100% sure. I want to say 4.3. There was a software update for the phone that automatically downloaded about a week ago but im not sure if that is related.

Since you received an update a week ago, you may be on KK.
I suggest flashing Philz Touch recovery via Odin and see if you can boot into recovery. In recovery you can see if the digitizer responds.
Flash the latest tar version from here in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

Stuck in the airplane mode after flashing custom ROM.

Hello everyone.
So I finally decided to reflash my Moto g5s (Montana), because an official stock ROM was driving me crazy because of its lags.
I have some experience with flashing. But never had a problem such as this.
I unlocked my Moto g5s.
I installed TWRP 3.2.3-0
I tried flashing my phone with:
LineageOS 14.1
Resurrection Remix
ViperOS
But decided to stay on ViperOS, as if it makes any difference because no matter what, I always had this problem after flashing with a custom ROM, my phone thinks it's in the airplane mode.
I even tried Android 8.1.0 Oreo - Stock Firmware.
Of course, I tried a factory reset and wiping everything that can be wiped.
I tried reflashing the same ROM several times, after flashing GApps, every time after an install wiping all the stuff via TWRP.
I tried reflashing TWRP.
I tried all the "simple" solutions there are, such as "turn on airplane mode and restart your phone, then turn it off".
But after every restart, when I long press power button, below options "Power off", "Restart", I see "Airplane mode is ON", even though it's turned off in the quick drop-down menu section.
I tried *#*#4636#*#* - Cellular Radio Power is always off and if I try to turn it on, nothing happens really, and after some time it switches off again by itself.
*#06# - Shows all my IMEIs are in place.
And still, when I try to dial a number, I have this message "Turn off airplane mode to make a call".
The only solution I've found but never tried yet is shown here (YouTube), but I need a ROM where my SIMs would work, which I don't have, obviously.
I reached the point where I would try anything only to get rid of this problem. And after many hours of trying decided to ask for your help, because I can't resolve it on my own.
Thank you in advance.

I tried flashing Montana-xt1793_nougat && oreo_stok-rom TWRP flashable, and that, from the look of it, resolved my problem.

Quodpipax said:
Hello everyone.
im glad you fixed!
no more need by my post.
thankyou!
Click to expand...
Click to collapse

hey i flashed the same but it still didn't fix it for me. also, my fingerprint sensor is not detected. please help

Im facing the same problem with with mi a2 lite
Quodpipax said:
I tried flashing Montana-xt1793_nougat && oreo_stok-rom TWRP flashable, and that, from the look of it, resolved my problem.
Click to expand...
Click to collapse
Im facing the same problem with my mi a2 lite...can you help me with the solution ple

G960F green tint issue.

Hello, after update received problem green screen. It only happens if wake from standby with power key. If wake by 2 tap on screen or fingerprint it wakes ok and no issue. The AP is G960FXXSFFUB3 installed custom rom based on the stock one with root but the problem still exist. Is it a hardware issue from the power button or software one? Would like to try to downgrade to older kernel but odin does not let me to downgrade the bootloader. Do you think downgrading the kernel would fix this?
Thanks in advance.

An update installed stock G960FXXUFFUC6 the only firmware odin let me flash but things got even worse the display got even darker and could barely see anything so reverted back to G960FXXSFFUB3 now and at least can use the phone so definitely it is a software issue. Do you know if update to LOS or AOSP kernel would fix this issue? And is it possible to flash F bin firmware to AOSP or LOS?

Is it possible to downgrade via ADB sideload command with root? Or with "fastboot flash boot" to flash old bootloader?
Is it possible to brick the phone? Someone tried?

Hi, did you solve the problem? Many people noticed that issue after upgrade from 9 to 10. Bootloader is blocked to the newest version of course and downgrade with Odin isn't possible in simple way.

Try using "oled saver" app. It mitigates the issue

Power button dead

Hello, has been a w hile since I was here last time. However, my moto g 5g plus gives me a hard time now. I was using it and at some point the power button stopped working. First it worked only randomly but now it is dead. Before the phone shut down i was able to test the fingerprint sensor and it worked. The last few days i noticed that the connection resets randomly from 5G to 4G to H+ and sometimes i had to restart the phone to have a working connection. I was thinking there is a firmware bug in the stock firmware that continues showing up over time. Last time i did a firmware recovery using the motorola rescue tool but that doesen't work anymore because i cant enter boot loader mode. I have seen that there is the qualcom flash tool out there and im wondering if im able to flash the device without bootloader mode as im not able to start it. And if the problem is software related or not. For the qualcom flash tool i probably need the "firehose" files, where can i find the right one for my device?

I have an update, I think it is a software problem. I have tried unlocking the bootloader and as soon I did everything worked same before. Then I flashed linageos and as as able to use it for one day until (when playing pokemon go it happened again) now the power button responds with delay. But it responds. I have tried to reflash lineage and stock using rescue assistant but nothing helps. Then I tried reboot in edl mode for blankflash but that one also doesent work. It starts the process when it sees the device but it terminates with an error. I have dumped all partitions using the recovery shell. But not sure where to search for as I don't have a dump of the stock partitions. I think there has been some corruption of one of the data in _a slot and now _b slot too. Someone knows what and where to look for? Maybe I need a dump of stock device?

It seems there is something wrong with bootloader. Now I'm not able to flash in fastboot mode. But it works when I flash the gpt.bin after restart in fastboot. I start the download on the PC and then connect the phone and power up in bootloader mode. After that I can flash as normal but after reboot everything same before, no fastboot working. And if I flash stock ROM and lock the bootloader it says no operating system found. I have tried using blankflash from lolinet but that one also doesent work. It recognises the device but then it stops. Is it possible that I have got this sort of thing ota? This is so weird. The power button works but just delayed. Is it on a different chip what is maybe broken? But that would be very strange. I have another phone I treat not as nice as this one and that works like new.

Ah I enter edl by using linage recovery

Deleted all the partitions, now it seems the device doesn't boot the stock ROM if I flash it. What are the essential partitions needed to boot the stock ROM? How can I restore the missing partitions? Thanks