Develop Bugs

Device strange issue will not stop giving problems!

This is a list of events that I have gone through today. I received a new charger because the old one I had became defective & was charging my phone up & then it would go back down to 0% & then shut off & it would end up in a problem where the phone would not turn on unless I pulled out the battery while the AC was in & then it was able to charge but still it would turn on, on its own to drain the battery when off & this was very frustrating. The charger I have now works but the device acts strange over the last few months doing a task29 & flashing the first ROM after would make that ROM not work & then I had to flash a totally different ROM to make it work. I was using Android & it had died a few times & also I experienced the same thing I did when it would charge up & go back down to 0%. please read below:
I got my new charger today & at 62% of charge I decided to flash to a custom ROM via mem card again well the ROM was a success but when pulling battery out to restart it didnt want to work. So I went to flash again in bootloader by memory card it shut off on me in the middle & restarted into bootloader again & shut off again right away. I did a task29 it worked got it out of bootloader & now the orange led flashes off & on when its off & now ive gotten that to stop. What exactly is wrong with this device?
it was @ 73% and finally setup a ROM NRGY however it ended up shutting off on its self & going into a power boot loop constantly restarting until that ROM can no longer start & now its stuck on the boot screen w/ its info.
I flashed the stock SPL on USB now im going to try to flash the carriers ROM back.
Stock SPL = Successful!
2nd Touch Pro 2 ROM Version Flash = Successful!
Its working for now. Battery is @ 80%
AHH! After charging to 100% idk what it did but when I went into the other room to check out its all possessed.
I have a black screen w/ white text that says:
The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
This operation will delete all your personal data and restore the device to its factory default settings.
IDK how this happened.
When I hit any key it didnt do anything it was stuck until I did a battery pull. Then I restarted the device it was stuck at the boot screen w/ its red info. It erased the entire ROM. Then I tried to do recover mode & it did nothing. I tried to flash the stock ROM again & no results & then again & still no results. I think its now not accepting the ROM at all since from: in the ROM update utility is blank.
Now it decides to get past the boot screen but then it malfunctions again & restarts itself & it tries to setup a 2nd time then after it does & its on sense home for a couple of mins it reboots twice & now its stuck on the boot screen again.

Things that I can think of.
- Isn't your batterie just broken? You will break your batteries when you deplete them completely. Maybe try a new batterie, because you said that you let it die for a few times. It could be that this is causing your problems.
- Did you flash true usb when you were in the bootloader? Give that a try, because I believe that the customruu performs some sort of checks. Maybe this is nonsens, but you can try it.

The battery was fully charged & it was working better than before.
I reflashed the Stock SPL to flash the carriers ROM back & that worked but at anytime it just rebooted for whatever reason to make it so the ROM was unusable at any time I would reboot it would decide to actually go past it seldom. I experienced that at one point oddly it went into setup n it did it again after a while its just acting strange.

If you're back to stock SPL and stock ROM, can't you just send it back for a warranty replacement ?

IDK how old it is. I bought it brand new from ebay.

Viper Matrix Wireless said:
IDK how old it is. I bought it brand new from ebay.
Click to expand...
Click to collapse
No warranty bro...
You can try but no warranty 9/10 times.
What ROM are you using? I used to have that issue with my betas.
It wld destroy itself after softreset and I would have to reflash.
Try to flash, turn off right after it boots, turn on and see how that works for ya.

Rep had told me I could get it replaced & they know I bought from ebay. But I havent called them on this yet.
It doesnt work. It usually doesnt go past the boot screen. Flashing does nothing to help it. Whenever it feels like it it may have to stay on for a few mins to go into setup but most of the time it will stay there & reboot, reboot, reboot, reboot each time its a different # of times & it will reset itself at anytime. Ive even had bootloader shut off on me & restart itself during flashing its a pain. I had another issue I didnt mention my device on any custom ROM when I had 0.85 olinex SPL the device would just freeze & not respond every time. Now this is a different situation. I am back of SPL 0.87 which is the default. I flashed the entire carrier ROM which 0.79 was rewritten w/ 0.87 & that was successful but its still rebooting & causing fatal problems including the black screen w/ white text.
UPDATE: I just walked into the kitchen. Somehow the device turned on by itself & now its sitting on the sense home screen. I know its not fixed but idk why it would turn itself on.

Moved as not ROM Development.

Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....

I got so frustrated I just got done calling T-Mobile Tech Support & they are going to ship me a replacement.

ultramag69 said:
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
Click to expand...
Click to collapse
I thought I would reply to you.
This is what started my problems is when I did a task 29 my device was acting funny afterwards. I did it again about a month later cuz I flashed way too much & it kept getting worse. But Task29 didnt help this time its what caused me to have to flash 2 different ROMs cuz the first one I flash after doesnt work.

I received the battery & it didnt do anything.
I'm still waiting on the replacement to come.

Help! URgent!!!!

I decided to try out the new RcmixHD 6.0 today...I backed up my Rom , wiped data n Cache n Dalvik Cache..The phone rebooted n now I am stuck on the bootscreen with white background n htc...plz someone help!!...I dont know what to do!!!....neone?..plz reply soon..

OK, i'm only new to this, so it might be better to wait and see if someone more experienced can answer you question.
but if its still stuck on the white screen then remove the battery & then put it back in again then hold down the Vol down button and power button until the bootloader loads up. then select 'recovery', it hopefully should take you back into the clockworkmod recovery & you can then flash your rom.
again, i'm only new & thats just my best guess.

first off, when you flash a new rom, it tends to stay on the white htc screen a bit longer. make sure you give it a few minutes (i'd say a good 3-4 minute wait should suffice but lets say 5 just to be safe). if nothing happens by then, you can always follow the method listed above by henipah to restore your backed-up rom.
once you have restored your rom and your heart rate has returned to normal levels, you can try flashing the new rom again. remember to wait it out a bit at the white htc screen.

First boot can take an age, if you issue the command
Code:
adb logcat
it will at least confirm the phone is doing something and hasn't hung, if it has hung issue
Code:
adb reboot recovery
and reflash your chosen rom.

Thank you for the replies...flashed it again n its fixed...it was stuck on Boot screen for about 15 minutes!!!..I thought I bricked by device or something...lolz..neways, all is well now..

Help plzzzz!!!!
I am a newbie here and am facing a problem with the data connection on the phone. I have flashed the new RCMix Rom v6.0.0.1 with partial Sense 3.0.
The problem is that if I leave the phone unattended or even otherwise, the data connection turns off. Is this a bug with the ROM, cause I see that the option for the Mobile Data Connection is still ticked in the Notifications Menu, but for me to be able to connect, I have to untick and then tick it again for the connection to happen again. Would also want to specify that I am not on 3G. Any help would be really appreciated.

[Q] HELP! - Phoen does not turn on.

So i been trying to fix my phone for 2 days now and getting nowhere, i trust somone with better mind can help me.
Problem started 3 days ago,when my Htc One with S-off - ARHD 31.3 started just turning on and off.
Sometimes it will just loop between the Htc one logo than shut down n Repeat- once in a while it will let me great through than i could use my phone.
Next day it would not even turn on sometimes.. if it did just stuck in Htc one logo. but few time it would load .. than when phone starts it would start saying your
unfortunetly, -htc sence stop working.
- phone *app
- etc all pop ups with preety much all my phone systems apps names- stop working-
i was able to by pass this sometimes by scrolling down on my tab n going to setting but most apps that was already in the phone would not work.
i tried several times.. but it all end with these pop ups then phone shutting down.. than repeat boot load..
Strange thing is i flashed 31.3 AGES ago when it came out... n had no problems it at all.
Anywho i than flashed the 33.1 boot img - 33.1 ARHD rom flashed with full wipe yesterday.
seeing if that would solve it as i was going to flash it anyway soon.
but i still get same problem.. with boot logo repeat and when it does get through, i get to have about 30min-1hr or so using my phone after than systems app stop working again.. n shut down.. and sometiems no matter if i try to turn it on with button or Button+ power down it does not turn on. -> when its like this i plugged it to my comp .. n my computer says a device has been plugged but not recognised..(comp makes a notifcation sound)
Thank you if you read though any help is much appriciated.

Sleep/Wake problems [SOLVED]

So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.

msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel

powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.

So enjoy the fix if you ever run into the above issue.

Im fine with stock, but I miss the fun of trying new roms.

Suddenly corrupted system, lit blue LED, fastboot only

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.