Hello all,
I have installed custom roms, and after I turn of car and start it again for a few hour units boots, last application - radio is going up, but I cannot run others appk, buttoms are working perfectly, but unit in inactive to my fingers touch. I have to push power on for a few second and start unit again, unit boots into recovery, I confirm restart unit and after boot all works perfectly. But after I stop the car for a few hours, still the same.
I tried malasky rom, DSA rom and still the same.
Regards,
Jiri
Related
Hello, i have a new P3300. The first time i opened it it started installing some basic stuff/programs and then worked quite good. Then i turned it off and when i turned it on again it shows the first splash screen with the htc logo, shows IPL and SPL versions on the left top side (like it should do) and then it instantly turns off. I have tried installing the official WM6 ROM again and again but after the installation finishes the problem remains. Also, when in confirmation dialog for the ROM to be installed or not when it shows the old and the new version, the old is completely blanc.
P.S.: Something else, when i connect it to charger (or USB cable) the orange light keeps going on and off about every 30 seconds.
Any help would be highly appreciated guys.
Send it back to your vendor for warranty...
Cheers
After many tries i managed to install some older official ROM but again after the initial screen calibration and the other stuff some customizations started installing and when PDA rebooted the problem appeared again. But tomorrow I'm getting it to service (and getting my Qtek 8310 back which by the way got a repair although unlocked ).
FIXED NOW!
Need help.
I burned the new Kavana ROM. everything was working ok.
placed my microSD and the device didn't recognize it, so i rebooted.
upon reboot the device got stuck on the white HTC screen.
pulled battery
tried again, rebooted, past the HTC screen to the Windows Mobile welcome screen but freeze again. hard reboot didn't respond.
pulled battery, then turned back on. device didn't even turn on!
tried several times with/without battery hooked up to power , and with/without SIM and/or microSD (all possible combinations) and nothing.
had lunch
went back to it and the device magically booted it but after the white HTC screen i got a blue screen asking about error from last reboot. said yes to correct. rebooted went past white HTC and into Windows mobile welcome screen and froze again.
repeated the process several times and finally got to the blue screen again asking about error from last boot, this time said 'no' and device continued boot in a white screen without HTC logo and froze.
all hard reset attempts were unsuccessful (if i'm doing it right: hold two soft keys and then power button).
now the device boots to the white HTC screen and then is stuck.
what to do?
edit: got the hard reset to work and reconfigured my phone. i only noticed the black screen for a split second because my Dash has issue that it thinks that the green send button is being pressed all the time (anyone know how to fix that?).
Thanks
Find your original rom in sticky, go into bootloader and flash original rom, then flash to wm6.1.
have the same issue!!... did you fixed? the main problem is activesync is not running so how do i install another ROM?
Active sync doesnt have to be working aslong as u got ur s621 pluged in and u wait for a few seconds before starting the ROM it will work.
Hello,
So, I flashed Booroondook's 5.1.1 ROM a few days ago to replace the stock 4.4.4 firmware and all has been fine and dandy except for one thing that didn't happen with the stock firmware.
On a cold boot, the boot logo will show up, load into the home screen, and then go back to the boot logo. The unit boots to the home screen fine after the second time. Also, even though my unit is set to stay on for 30 minutes on ACC OFF, when I turn on my vehicle within the 30 minutes, the home screen shows up for a slight second then goes back to the boot logo before booting back to the home screen. I've changed the timeframe of ACC OFF to other durations, but they all show the boot logo.
Is there a way to fix this, or am I stuck with this issue? Could this be an issue only tied to specific ROMs?
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.
Hello!
After recently getting my hands on an old Samsung A50, I thought I might as well reflash and do some stuff with it.
After installing Orangefox and Lineage, everything worked fine until the phone eventually ran out of power.
I plugged it in and let it charge for a bit, but it was just constantly showing the gray circle with a charging/power icon in it, but no battery indicator.
This usually means that the phone is completely empty and has to charge a bit before booting.
After letting it sit for a long while and nothing changing, I got a bit worried.
At this point, unplugging the phone does not change anything - it will continue showing the indicator even while unplugged.
Holding power and volume down (or power + both volume) briefly blacks out the screen, but it simply comes back to the indicator a few seconds later.
All of this happened a few days ago - I eventually got it to boot again through some key combination while the screen blacked out, sending me to orangefox or download mode (i dont remember),
from which I was then able to boot into lineage again. In lineage, everything worked fine again, including the battery indicator which showed that the phone was full, and the battery seemed to work completely fine.
After that, I turned from lineage to Fresh, which also ran fine until Fresh wanted to install an update which sent me to TWRP. Not sure what to do, i just booted back into System which worked fine, but the Fresh update hadn't succeeded.
I attempted to update again and this time shut down from TWRP - big mistake. Now i am once again stuck in the low-power indicator.
I believe that last time i escaped by booting into orangefox - but i think fresh replaced orangefox with twrp?
Anyway, i tried holding different button combinations while the screen is briefly blacked out but nothing is happening (also tried getting into download by plugging into pc, holding power+volumedown, then holding volume up+down while screen is black).
I also let the battery empty itself until it went black by itself and then tried again, but no success.
I'm now again unsure what to do. How do i unbrick this to boot into the OS again? How do i prevent this from happening again?
Thank you all.
Same issue with my Redmi 9, it seems a battery issue idk if i had rekt mine after flashing a latest CN rom then after not being satisfied tried to flash thru recovery to its stock rom and it went bootloop. Fixed it by flashing with SP flashtool and some bypass stuff, but damage has been done with my batt. Maxing out the volume when I try to play something video or music would trigger a reboot to my phone.