Unlocked Verizon phone. It will not charge in normal or safe mode. Bring up bootloader, go to "Factory mode" and it charges. Have tried numerous cables, power adapters and a factory reset. None of these has worked. Any other suggestions?
I'm curious as to why its unlocked. If it was to only move it to another service or if you or a previous owner had installed a custom rom or something else.
A custom rom or could introduce battery charging issues. If its stock rom then it could be a physical problem that for some reason is improved by going to the bootloader. I would expect either that or an OS bug that is prevalent even after factory reset - in which case if a custom rom doesn't fix it then the phone may be regarded as borked in my opinion.
Related
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.
Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?
Hello,
I received a at&t galaxy s6 edge, it was rooted and kept popping up knox warnings, so I looked at the baseband version and it was G925AUCU6EQCF, I googled that + stock rom which lead me to this thread.. which I downloaded and flashed using Odin, afterwards my touchkeys/softkeys just no longer work. They were working before flashing.
I've tried, wipe cache, factory reset, safe mode booting, *#2663# -> sensorhub fw update is grayed out, I also tried multiple new charging ports.
Little background, I don't know much about rooting and android roms, but I run a repair shop and do bunch of hardware repairs. I recently received a dozen or so assorted s6, s5, s6 edge, note3, note5 which all appeared to have been throwing KNOX warnings (among other issues, broken screens, charge ports, etc..). Now I'm not completely oblivious to this stuff, but I've flashed stock roms and installed twrp +root before on samsungs. For 10 of the phones I googled the baseband +stock rom and was able to flash it back to stock and KNOX warnings went away and all were fully functional, not sure If I'm doing it right but it works, perhaps unrooting would have been easier/quicker?
I opened up the phone and tried a working charging port from another s6 edge which I know the softkeys work, but I still got no touch on them, they only light up but no function or vibrate, so I did some googling and noticed I may not be the only one. I've seen some threads here but for other samsung phones, some mention something about "flash some idlekernel that will update the touchkey's FW", another mention build.prop and other "qemu.hw.mainkeys=".
Now, I am not all too technical with this so I was hoping some handsome generous person could help me out or point me somewhere, anywhere
Thanks!
So I have a Galaxy S10 verizon that was working fine, was up to date with all updates and etc and all of a sudden it decided to keep on freezing then reboot. Figuring it was a software issue I already have done the following with no luck
-Wiped cache
-Ran in safe mode
-Full wipe restore of the system
None of them have worked so I then proceeded to obtain the combination files and have reloaded the phone fresh using Odin new figuring it was a corruption in the software.
After it successfully finished loading the problem is still present after about 30 seconds after rebooting the phone. I don't know what else I can do next besides playing around with a custom rom maybe to see if the reboot loop is still present.
Any Ideas what else I can do or try?
Phone is in perfect condition, never dropped, no water damage, never flashed anything to the phone and was running just the stock verizon firmware. Phone doesn't even has a scratch in it...
Any ideas would be greatly appreciated!
If a data factory reset in recovery didn't work nor flashing stock firmware with ODIN, then it's probably hardware related and thus you will need to claim insurance if you have it with your carrier or warranty thru Samsung if it's still in warranty.