Related
Guys,
Have a problem with my M8 and not sure what's the cause of it all. Its an M8 that's been converted to a GPE edition via: http://forum.xda-developers.com/showthread.php?t=2708589.
Problem:
The phone keeps restarting randomly, comes on for about a minute and then restarts.
How it started:
Just received the phone back from HTC, I sent it in to get a loose speaker grill fixed. Up until then the phone has been fine on GPE (4.4.2). Prior to me sending it in, the phone had an unlocked boot loader, s-off, custom recovery and rooted.
I made HTC aware of the state of my phone as well as telling them that its an original M8 converted into a GPE version, They didn't have a problem with it and fixed the device under warranty. But on receiving the phone back, HTC have relocked the boot loader and put s-on back, its still rooted.
So first thing i did was unlock the boot loader which went smoothly, next up was firewater to get s-off back. That didn't worked as HTC has apparently patched the exploit so im still with s-on.
After that is where its all gone down hill , tried a nandroid backup, worked initially then the restart began. Did a factory reset and that seemed to work until I tried installing apps, and then the problem came back.
Does any one have any idea what might be the cause or solution? If i had s-off id re flash the RUU, but obviously cant do that.
Hey there,
I'm having exactly the same problem i dont have a google play edition but since yesterday Spotify crashed and my phone keeps rebooting. Now i want to try and install Viper to see if it will solve my problem but right now i am on stock rom.
Wickedd said:
Hey there,
I'm having exactly the same problem i dont have a google play edition but since yesterday Spotify crashed and my phone keeps rebooting. Now i want to try and install Viper to see if it will solve my problem but right now i am on stock rom.
Click to expand...
Click to collapse
Let me know how it goes
The reason for the reboots is SuperSU v2.00
after updating SuperSU my phone gone completely crazy and keeps rebooting every 1 or 2 minutes, had to Disable the app and no problem so far
hope ChainFire fix it ASAP
arDr0id said:
The reason for the reboots is SuperSU v2.00
after updating SuperSU my phone gone completely crazy and keeps rebooting every 1 or 2 minutes, had to Disable the app and no problem so far
hope ChainFire fix it ASAP
Click to expand...
Click to collapse
OH i was thinking about something like that, when i check my active processes Right before it reboots, SuperSu is on. I was just about to sideload viper, now i might try this for a sec !
Hang on
Edit : That works, SuperSu is screwed..
Wickedd said:
OH i was thinking about something like that, when i check my active processes Right before it reboots, SuperSu is on. I was just about to sideload viper, now i might try this for a sec !
Hang on
Edit : That works, SuperSu is screwed..
Click to expand...
Click to collapse
im still on SU 1.94 were you on SU2.0 ?
I was on version 2.0, any more questions ? I'm going to flash to Viper in a couple of moments
You might be right, on SU 1.94 and no restarts. Trouble only happens if i get the latest version.:good:
I have searched the internet for an answer to my problem to no avail. The reason I can not find a solution is that I'm either slow or there is not yet a solution. Had to get that out there. OK here is the issue: I of course have a sprint note 4. I installed twrp and CM 12 official on the third of march. Last night I was up late, bored , and out of my mind. I decided that I wanted to try xposed framework. That went well. Installed a few modules such as Pandora patcher, flat colors, hex clock, call recording for cm, and finally gravity box for LP. Everything was fine after making changes in every module except gravitybox. After I had rebooted my phone to finalize the changes made in GB I had no service. So its recognizing that I'm with sprint and I have service for just a sec when I turn on and off the phone/ airplane mode, but just goes back to emergency calls only. I realize I shouldn't have messed with GB or any other mudules on my note with LP. Things I have tried: I installing the xposed Disabler in twrp, undoing all the changes I made in all of the modules then uninstalling them, restoring my earlier back up, reflashing the stock firmware( although this time it was LP stock), tried to change my network settings(but they are greyed out), and patting my tummy while I rub my head. Please help a brother out. Any help or suggestions would be greatly appreciated. Thank you in advance.
Have u tried ##72786# in dialpad or updating prl and profile on a touchwiz rom then flash cm again but my thoughts on cm are garbage but thats on u
The suggestion above is the first thing you need to try. Second thing is if you have never taken the Lollipop update via ota or odin flash the stock BOB7 rom tar, then that could very well cause issues running Lollipop on KK firmware/modem. You must take the Lollipop update by one of the two methods I just mentioned then you can flash the CM based Lollipop rom and you should be fine in the radio/connectivity department. If you don't or haven't done this already then expect problems. Good luck.
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- Set up phone, comes with Nougat 7.0. Camera works at first, though seems to have problems with the auto focus. Camera app then updates overnight and stops working. Clear data/cache, remove updates, hard reset - no good. Flashlight does not work either, simply says "loading..." and stays like this indefinitely until closed.
- Factory reset, no change. Switch to safe mode, no change. Decided to unlock bootloader and install custom ROM after hearing that would fix it (I know, I know...I should have just sent it back at this point). Install Viper 5.10 + root with magisk, camera and flashlight still not working. Safe mode, not working. Full wipe in TWRP, RUU back to stock firmware (CID: HTC_034, flashed 2.41.401.3 signed firmware). Set up phone again on stock firmware, still no change in camera or flashlight.
- Install LeeDroid 10 3.7.0 custom ROM, root with magisk. I get a breakthrough here; turning off "OK Google" in settings gets the camera and flashlight working again! Still have the "laser autofocus blocked" issue, but I figure I'll deal with that later. Backed up with TiBu.
- Next day, decide to use a ROM that includes the latest security patches (got a bit annoyed waiting for HTC to push out the European updates, still on 1st January patch) so went for Resurrection Remix. Wipe, clean install etc. Camera stops working again, no change in safe mode. Wipe, clean flash back to LeeDroid, camera is no longer working, in normal mode or safe mode.
- Went through a bunch of custom ROMs at this point; ICE, Dirty Unicorns, LineageOS, then decided to try RR, LeeDroid and Viper again - camera still not working in normal mode or safe mode. With the ROMs that required GApps, used every package in both Open GApps and Dynamic GApps to install. No change to camera, Google Camera was unable to start as well.
- Flashed upgraded RUU (2.41.401.4 signed firmware) and went through the process of wipe/clean install custom ROM/test camera with all the above custom ROMs in normal mode and safe mode. No change in camera, though the ROMs were all excellently made
At this point I'm pretty stumped If it was a hardware problem, why did it work when I first installed LeeDroid, but not after? It's not been mishandled, it's just been sitting on my desk since I got it. The fact that it doesn't work in safe mode would suggest to me that ,maybe, a camera driver has been deleted somewhere along the way? I also tried a load of other methods I found on various message boards; flash it with no SD card inserted, flash without SIM card installed, etc. but absolutely nothing works.
Third party camera apps also don't work; most simply crash on starting. Open Camera says "Unable to access camera. Maybe being used by another app?", so I tried removing the permissions of all apps that had access to the camera except the camera itself - no change. Deleted cache/data/preferences of all apps - no change.
Finally, I had a look at the HTC diagnostics test using *#*# 3424 #*#* on the dialler - the camera test doesn't even show up! :crying:
I've run out of things to try at this point, so I'm posting this here to see if anyone can possibly shed some light on this very strange situation. Is there something I can do to fix it? Or should I start begging Amazon to give me a refund? Unfortunately I'm a week outside their 30 day return window...lesson learned for next time; if in doubt, send it back!
Oops, meant to post this in the Q and A forum. Don't want to spam a duplicate, is it possible to move it over?
Hardware issue. Contact HTC for a replacement. sounds like it may just not be connected. I had one with no working vibration notification, the motor would turn on, you could hear it, but the phone wouldn't vibrate. Got it replaced ASAP! I recommend you do the same!
FinnMacKool said:
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- !
Click to expand...
Click to collapse
Same issue here. The only thing that works for me (so far) is flashing back to a Marshmallow rom. HTC has been completely silent on this issue in terms of actually fixing the problem. They know the problem is there for only a small number of us and so aren't going to do anything about it. Fine. This was my first and will be my LAST htc phone. Buh bye htc, you'll never get another dime from me.
Did you fix the issue, coz i have the same in my HTC 10
Hi
follow my post in anildsouza73 blog..I will show how to fix it if someone really spoiled it...have a good day..
from yesterday morning the problem appeared to me. Initially, the difficulty in focusing, then rebooting the impossibility of opening the camera app and the flashlight. I found on Youtube the videos that showed the same problem. Is there a solution today?
Hi all
I found if I cleared my flashlight cache and then the camera cache, soft reset phone I could get the camera working again. Only problem now is the autofocus is not working properly. Any ideas for that?
Same problem. Focus stopped working, then I cannot launch camera app. Anyone found a solution?