I bought an OG Razr from my friend. It worked great for several months. Basically as soon as I got it, I updated to the ICS update, rooted the phone and switched it to page plus.
Since there was no good way to run a custom ROM on this phone until recently, I've been running the stock one until about a month ago.
I was really hoping that after using safestrap and using CM11 that my problem would stop. It was good for a day or two, but then it started back. I was using the current version of JBX kernel, so I wiped romslot-1 and started from scratch and stock kernel. After this I was convinced it was app-related, but after a lot of trial and error, I'm not sure anymore...
I was convinced it had something to do with sleep mode..I found an app that suppose to keep your phone awake, but it continues to do it even with the app running. The phone will NEVER reset while the screen is on!! I can use it all freaking day and it's perfect...but if I turn the screen off and check back in 20 minutes or so, the phone will be powered off....sometimes it will be hung up, and I will have to do a hard reset. Sometimes it will turn itself off 2-3 times an hour (once again, only after screen is off).
Could this have something to do with me moving the phone to page plus..? I've noticed people saying to wipe the cache and see if it continues...I've been wanting to factory reset my phone and clear cache etc, but I'm afraid it will screw up my page plus config..will it? Will the phone still be rooted?
I can't really find many people having the same issue as me, so any advice is greatly appreciated! I cannot afford a new phone at the moment, nor can I afford for my page plus to be screwed up.. so that's why I'm so hesitant to mess with the primary ROM.
Thanks in advance!
Joshua
Any advice or tips..? Thanks again
Almost 90 views and not one response...?
Thanks.. No really, THANKS!
I have experienced this happening to me as well, although it is very infrequently. This only started after rooting and installing Safestrap. Initially I had flashed CM10.2 Snapshot in Slot 1 and CM11 Nightly from December in Slot 2 while leaving the Stock Slot alone. I can't recall if it was CM11 or CM10.2 when I experienced the phone shutting off. Since then I have deleted Slot 2 and run clean installs of CM11 Nightlies in Slot 1. I no longer see the switching off. GAPPS are the only other packages that I have flashed. I have tried many devs GAPP packages but have been running PAGAPPS for a few months now without any issues. Looking back it's possible one of the GAPPS packages was causing the phone to shut off, IDK.
Sorry I don't have an answer to the problem but thought I'd share my experience hoping you our others may get something out of it. Are you sure the phone is powering off and not stuck in a sleep state? Try plugging the phone in to charge, see of that causes it to wake, also try connecting a PC and see if it is recognized. The only other time this will happen (power down) is when the battery goes dead. Maybe your battery is getting old or possibly a bad connection. Get yourself a spudger tool, remove the battery and clean the contacts or better yet replace the battery. Last time I checked they were very inexpensive.
Good luck!
XT912 - CM11 Nightly - PAGAPPS Micro
as google stated, if you're running CM11, the first thing I would assume is wiping the dalvik and cache (wiping those or even factory resetting shouldn't mess up your page plus setup, that info is written elsewhere on the phone. Second assumption would be that it was a bad gapps flash.
Happened to me on a warranty replacement.
Hi,
I just wanted to add that I've had this happen on a complete stock XT912 refurbished warranty replacement. Had to send it back under warranty, the day after I got it...
Related
I RUU'd to Jan2012 OTA update, unlocked with HTCDev.com, installed AmonRa, rooted using AmonRa and everything has been fine....for about four days. Then yesterday, after using IM+ Free for a few days and liking it, I decided to buy the Pro version. Coincidentally, my extended battery was running out and I didn't have time to charge it at work, so I powered down, removed the battery, put my charged stock battery in and voila...boot loop. No signal at unlock screen, sits for 10 seconds, and reboots. I can do a factory wipe and it will boot, but if I restore anything...data only, system only, secure only...all 3, 2 of 3...doesn't matter...issue returns. Anyone know why this might be happening?
It's because you can't post in the right section!
Have you tried wiping and flashing a Rom? Not restoring
Edit: its probably because of a bad backup or because of the ota, its been known to bootloop
Sent from my ADR6425LVW using Tapatalk
Can a Mod please move this to general?
OT: Check the bootloop thread that will more than likely give you the answer you're looking for.
http://forum.xda-developers.com/showthread.php?t=1394659
My apologies for posting in the wrong section.
My concern is that it was running fine, and then suddenly wasn't when nothing but an app install (IM+) was done. I don't want to go through setting everything up again only to lost it all again four days from now.
I am having similar issues as you are. Tried to charge a 3.8v stock battery overnight and it bootlooped all night long. It seemed like it settled down after putting back in my 3.7v extended. So I called HTC and created a rma for the battery, no big deal.
Then today listening to music while the phone is in the dock i had a few reboots/bootloops, noticed some odd stuff in logcat so I did a reset permissions in recovery. Seems better so far compared to before where it would only take a few minutes to bootloop.
*mine is not the network issue, but good to hear you fixed yours
joblabbo said:
I am having similar issues as you are.
Click to expand...
Click to collapse
Yes, sounds similar...however, I ran my stock battery for about two weeks with no issues, and ran the extended battery for a good month with no issues, and even ran fine for a few weeks after htcdev.com unlock, AmonRA flash and rooting took place. This all came about out of the blue.
Right now, I am attempting to use the guide specified concerning connecting to the wrong type of network. I'll update when finished.
------
UPDATE: That worked. It was a communication issue, the phone had changed it's connection preferences. The sad part is that I've been without a phone for almost a day over this, and flashed all kinds of kernels and recoveries, and even considered going back to Verizon for a replacement. The even sadder part is that I already knew of this fix and completely forgot about it. Thanks a MILLION to MrSmith317, not only for directing me to the fix, but also for not bashing me for accidentally posting in the wrong area of the forum.
I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC
Ok, so my fiancee's at&t note is stuck in a bootloop. I had it running on Blackstar, and since giving it to her hadn't bothered messing with the setup as it was stable. On her way home from work she apparently left the phone in her truck while making a stop in 92 degree weather(Farenheit). Now it will show both Samsung screens and then bootloop. I did some searching here on the forums and have tried everything I can find/think of. Here's a list of everything I've done:
1. Booted into twrp recovery, wiped data, cache, and sdcard for good measure.
2. Got to lockscreen, bootloop.
3. Used ODIN to push Samsung stock files onto phone, including recovery.
4. Got to AT&T easy setup screen, bootloop.
5. Used stock recovery to do hard reset.
6. Still bootlooping from second Samsung screen.
7. Removed back of phone, cleaned power button.
8. Still bootlooping.
I should note that the phone never booted itself after a battery pull, but I figured cleaning the power button couldn't hurt any.
Is there anything else I can try before going to at&t to have it fixed?
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Kies emergency firmware upgrade. Factory cable. Rear (powered) usb port on pc. Battery fully charged. Serial and model number under battery (all capital letters). Pray.
Don't quote, reply. If you quote, edit.
The battery try might be worth a shot. If not.... Surely mobiletechvideos could fix it. If they can be brought back from the dead, surely they can be brought out of bootloop.
Sent from my SGH-I717 using Tapatalk 2
darthmalgus said:
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Click to expand...
Click to collapse
Definitely try the battery. I had exactly this same problem, and even though the old battery seemed to be taking a charge, it was still screwing everything up (in the same ways you described). A new battery fixed everything*.
* - Ok, it actually it took a couple ROM reinstalls, to fix everything I apparently screwed up while trying to fix the devices before switching out the batteries.
Thanks for the info. I went ahead and ordered a new bateery, it'll be here Monday, so hopefully that works. I have the phone flashed stock with Kies at the moment, so I would hope I don't have to do any more reflashing if the battery is the issue.
Yeah i have the same issue. I was running blackstar. I had some issues occasionally with it crashing, nothing major. decided to install JB once ATT had official out. Wiped, installed, gets to att logo and reboot... please post your fix if it works. I have a second battery. I'll give it a shot but I have been keepeing it plugged in while doing these things and it still doesnt work.
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Matt Bernius said:
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Click to expand...
Click to collapse
Tried a couple flashes, with the debloated and bloated Roms based on Official JB. I can get to the getting started screen sometimes. typically I hit the next button and it goes into bootloop. once or twice i was able to select the next button and get to the next screen before it crashed. I'm thinking it's dead but.... idk.
This fixed my issue...
Replaced battery and yeah. I'm all better. so odd.. shrug. The other wasn't giving any indication that it was actually defective.
Awesome ... final step ... change the title to include solved :victory:
Okay, Now I know I am not the only one with this problem. Also, I know I am one of the FEW people who have this problem.
Story:
I bought the Note the other day from someone, they claimed that the note was stuck in a boot loop. I purchased it, Did a factory restore etc. The phone came on and was working perfectly. THEN the battery died, now I understand what she means by stuck in boot loop.
What happens:
Phone turns on
Starts up
Freezes after about 2 minutes
Reboots & Repeats
Now there have been a couple times I can get it to stay on for about 12 hours then it will just freeze and reboot. I have tried factory firmware restore, I have rooted, I have tried custom Roms, I have unrooted, I have done stock rom. The battery is NOT bad, it holds a charge perfectly well, the Power button is NOT stuck. I have no idea what else I can do, I have tried just about everything and looked all over this site for the past 2 days trying to figure out info on this problem, but so few people are having it that it is basically just looked past.
Any help is MUCH appreciated and I will be very grateful if this issue can be resolved.
Have you tried removing the battery / changing the battery / using a different usb/charging cable/ac-dc adapter? Then clear the cache and dalvik cache and reboot. If you can get it to stay on for 12 hours I doubt that you have a serious problem.
Power button perhaps?
http://forum.xda-developers.com/showthread.php?t=2792746
http://forum.xda-developers.com/showthread.php?t=1744395
http://forum.xda-developers.com/showthread.php?t=2596832
http://forum.xda-developers.com/showthread.php?t=2595555
http://forum.xda-developers.com/showthread.php?t=2547025
http://forum.xda-developers.com/showthread.php?t=2522688
http://forum.xda-developers.com/showthread.php?t=1854944
Not sure about power button on this one. It wouldnt freeze, it would just reboot.
I question software on it. If you can get it running long enough to find out what it is running.
I might question more, is it running OS for the right device or possibly was it a clean flash?
Sounds like its running an older 4.2 JB rom......notorious for random reboots. Could be a rom that just may not work on you phone. Mine could run all except Carbon Rom. Dont know why, just couldnt. No biggie, plenty out there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.