Develop Bugs

Random Reboots...

Hey everyone, I looked around and didn't find anyone having my particular problem, but If I put this in the wrong place, or someone has already solved it, just let me know. Don't want to waste your time!
I got my DINC the day they came out in stores...the first one my local store sold in fact. It was working great, but I hated the bloatware and the fact that the Bluetooth stack was not up to date...couldn't connect with a new hands free speaker phone I just bought (Parrot mini-kit slim). I had occasional random reboots, but not too many. Once or twice a week maybe.
So when the unrevoked one-click came out I tried it. Worked great.
Then I started trying ROMs. With everything I've tried I get random reboots...a lot of them. Sometimes it reboots once and works fine for a couple hours. Other times, it will loop until I do a battery pull. When it loops it will sometimes make it all the way to the lock screen, sometimes it will only make it to the boot animation, and sometimes it won't get past the white HTC screen.
I've used a couple different nightly builds of CM6, with and without google apps. I've used Skyraider 1.8 and 1.9 with and without sense. I've tried "touch of photons". Same results and activity on all of them.
Last night I gave up and downgraded to unrooted 2.1 with sense...factory fresh. I reformatted my SD card with the phone, reformatted the phone storage, and I've done factory resets. It still isn't working right.
At this point, I'd be happy to get it back to pre-Unrevoked and just wait for the official OTA Froyo which is supposed to come out soon. Rooting and using a stable rom is fine with me too. I just need a phone that works consistently.
Any ideas? I'm pretty desperate.

sounds like you needed to return it and get a new one since it was doing random reboots from the day you bought it.
have you used any of the hydra kernels to try and OC it, the 1.15 OC would cause mine to reboot. a good stable rom that i tried was JagerRom, 1.7.4 is without sense, and chocolate is with sense. don't try the OTA one because that is for people who updated to the OTA leak and im going to assume you aren't one of thoes people. haha
http://incredibleroms.com/roms/jager/
hope this helps

Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Does anyone know if there is something that could have gotten messed up with unrevoked or the roms I tried?
Is there another downgrade method I can use? I just installed the PB31IMG.zip you can find in a few places out there...is there a known reliable source for the downgrade zip?
If I can avoid fighting with Verizon on this I'd like to. I'm obviously outside my 30 days, and I don't want to wait a week or 2 or three or more for a new incredible (if I can convince them to get me one). I'm not even sure warranty or Asurion will do anything with this kind of a problem either...I fear I'm stuck with a $500 reboot roulette machine.

re
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..

I also have had a reboot issue. I rooted the phone the day I got it and installed a senseless rom. It worked perfect the 1st day then started into a downward spiral of reboots till it went into a full boot loop. I did a nandroid back up of the original rom. No real issues since. Im still rooted and have only had one random reboot in about a week that I know of. I know the first issue was because of the rom but what causes the random reboots. Is it aloss of signal? Im a noob so Im just trying to get some insight.

Im on #2
I got my 2nd Incredible on Friday. Prior one would just get hotter and hotter (possibly due to signal issues) until it would enter a reboot loop. Hoping # 2 fares better.

johnsquared said:
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Click to expand...
Click to collapse
ya everything works in jager. but from what everyone else is saying it seems like it could be the signal (or lack there of) that's causing the reboots. have you tried the hybrid prl? it uses the verizon and altell towers instead of just the verizon ones. i haven't tried it because im in cali and there aren't any altell towers near me, but if your stuck with the phone you might as well give it a shot if you live in the supported areas. good luck man.
Link to PRL thread:
http://forum.xda-developers.com/showthread.php?t=723829

If you don't have problems with signal don't bother with the hybrid prl... it kills your data speeds because it switches you from Verizon data network to Sprints data in most areas. I know in the Carolinas phones randomly reboot a lot because thats Alltel country and phones don't work properly without the hybrid. But down south its mostly Verizon. Out west Texas/Ok is mostly Alltel.
But man honestly - I have the same issue on custom roms. My stock Sense rom does fine though. Sometimes I'll be on a custom rom typing a text and the keyboard just freezes and its over. lol nandroid time to me - I can't take the reboots but hate not having the features of newer software.

re
i have tried the hybrid prl and it did not help my rebooting issues.
i have also tried switching to the the cdma codec to -b the higher quality compression... with no luck in fixing the reboots.
I have also made sure there was not an issue with an app causing it, i have tested mine with a clean / factory reset with absolutely no apps installed.
I have had 100% good luck with the leaked ota update, the one upped the camera to 720p recording as well as a hand full of other fixes, and not once did my incredible reboot or crash.
I'm pretty confident that htc has fixed this issue for me, once they drop the 2.2 update that everybody seems to be speculating will be released in a handful of weeks.

Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.

Me Too
johnsquared said:
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Click to expand...
Click to collapse
Same EXACT thing happened with me and telesales. No scripts, no hard reset, no task killer; NOTHING. Said "my phone gets hot and reboots" and they said (last Thurs), let's get you a replacement overnight so you can try the new one out of the weekend. No muss, no fuss. Got here 10:30AM the next day, and my evil super-heating 4-to-13-reboot-try prone phone is going back.

sprintrjm said:
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
Click to expand...
Click to collapse
I don't believe towers/signal would have any effect on shutting down or booting. Basically once you're on a current PRL, you really shouldn't even have to update it. Unless you're having that poor service deal where an Alltell/Vzw hybrid would benefit you.

[Q] Anyone else getting random resets on thier S3?

Been getting these ever since the phone was new...a lot like the E4GT did when the 4G was turned on running custom ROMs? It does this just enough to be anoying, not enough to take it in and complain...yet!
I'm rooted and stock ROM, but it did it on blazer ROM too. Also did it completely stock - no root! Back then with the shortages of phones I thought I'd wait to do something and hope maybe a software update might come in to save the day? lol
I guess it does it about once/day on average. Anyone else getting this?

Never happened to me thankfully in about 2 months of owning the phone.

This happened to mine as well... I guess its a TWiz glitch because it has not happened since I switched to CM10. Try an AOSP ROM and see if it helps. I used to get daily reboots just like you.
Sent from my Nexus 7 using xda app-developers app

I have had this phone for about 2 months now, runned a couple of custom roms, and I've never seen that.

ok, I guess I'll take it in to sprint store and see what they say...If they're feeling generous maybe they'll just replace it?

Well, I spent some time with a Sprint Technician last week trying to fix this "reseting" problem. The gal told me she'd call on Saturday to see if the phone had reset at all ...in other words to see if what she had done fixed my problem? Well she never called me back!!! So I phoned Sprint on Monday and told them it had reset twice on me in the time period
So, the gal I talked with created an "E-Ticket"? Then told me to take the phone to my local store and let them determine what to do next...My question is this:
I'm rooted and running stock right now (LI3) Both Modem and ROM.
Should I do a restore to stock before I go in?
Will they be able to tell that I was rooted?
Will they care?
Or should I just take the phone in like it is and be above board with them the whole way?
They prolly won't believe me when I tell them the phone did this when it was bran new un-rooted

Anyone?

This is probably not the response for which you are looking, but I have zero problems of any kind. I have been running the LIG leak since the day that it became available. I wish that I had some insight for you or could be of help.

[Q] restart

hey, i have had my Galaxy S3 sence black friday of 2012, and it is not rooted or anything. but just recently within the last few weeks, it has randomly restarted, like im texting or playing on FB and then screen goes black then i see samsung logo. any sugestions on how i can fix this?

Mine recently started doing the same thing. After being rooted about a year ago, and being stable on the same ROM for the last 6 months or so, it randomly started rebooting itself 10-20 times a day.
I tired installing a stock ROM, stock kernal, etc. but nothing helped. I eventually unrooted it using QBKing77's video (on this site) and used Odin to install the stock tar image. This was in preparation to take it back for what I could only assume was a hardware issue. After a *lot* of automatic OTA updates (maybe 8 -10 or more!) it seems to have solved the issue. The phone has been stable without a restart for the last 48 hours.
In addition to that, I also pulled my sd card and ran it through the windows disk tools which said it found a few errors and corrected them. So at this point I don't know if it was ROM/kernal related, card related, or a perfect storm of a combination of each. I'd suggest you pull your sd card and use windows to check it 1st since that'd faster and easier. If that doesn't work, unroot.
I plan on waiting another day or two before I unroot again, just to be sure it's still stable. Hope this helps.
** Just saw that you're unrooted. If you're still in warranty, take it back. If not, try rooting it, and installing a new kernal or ROM and see if that helps.

i am not in warrenty, i wish but im not. i dont want to root it,

Check if your battery is swollen, the spin test works pretty well if you're unsure just by looking at it. A swollen battery is one of the most common reasons for frequent reboots if you're running stock.

Power button failure known defect with S3. They replace them at Sprint. It's referred as Sudden death syndrome.
Sent from the future via Tapatalk 4

[Q] Epic 4G in Recurring Sloth Mode

What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?

DeafScribe said:
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
Click to expand...
Click to collapse
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.

Worth a try...
KennyG123 said:
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Click to expand...
Click to collapse
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.

DeafScribe said:
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
Click to expand...
Click to collapse
I just hooked one of my old ones up to freedompop through the BYOD program. Nice to see the old girl getting use at least as an emergency phone.

SM-G925T problems. Please help ASAP. Thanks

I have yet to find a answer to this question anywhere. Any help would be greatly appreciated.
I have a SM-G925T and I had rooted and flashed roms to this device in the past and have been able fix all of the problems I have run into until now. I am not currently able to use my phone for texting/caling/mobile data until I connect to wifi (with wifi calling on t-mobile) I am not able to do anything, but when I do connect to wifi I can make calls and tests. I have been looking everywhere and not seen anyone with the same problem. I feel as though I corrupt the EFS folder or IMEI as my IMEI now shows 360000000000006 and the actual IMEI is entirely different. If anyone has an answer to this that doesn't involve sending it to Samsung I would love the help.

What have you tried to fix this problem? Reset APN? Reflash rom? What rom are you using? Also dont sent it to Samsung, just ask for tmobile to replace it unless you dont have insurance.
Sent from my SM-G925T using Tapatalk

The problem is rooting.
Returning to stock will fix and solve all your problems.
Pp.

i ran into the same issue 2 days ago and searched this plus many other sites for a solution. i kept getting answers saying something about a root key needed to be fixed. or the other answer i was getting told was to flash [KERNEL] UniKernel v8-0002 COH9. i ultimately ended up taking it back to t-mobile and got a new phone. but the manager told me it was missing certificates and the stock kernel. i hope this little piece of information helps, and i hope you have better luck in restoring your phone than i did.

Every time this phone S6edge, gets an update it becomes harder and riskier to root the S6e and still have a working phone.
This top of the line device (until the S7 gets here) isn't your average phone to experiment with, try a plain android like a nexus Google phone, there's probably a handful of developers working on the Nexus alone Vs one (maybe) for the S6e?
I know xda forums are all about taking control of your phone but not this puppy, you must surrender to Samsung on this one.
My phone is 6 months old and works great, even after updates it just gets better and better and after marshmallow gets here this phone will be a greater device.
I have stayed stock and never attempted to root because I was following and reading all threads started on the S6e and it was a hot mess, a lot of stuff and phones going wrong at first and as soon as some one found an exploit Samsung had it removed and safe root went right out the window.
I have learned to like stock and I'm ok with it. And my phone works all the time.
Pp.

PanchoPlanet said:
Every time this phone S6edge, gets an update it becomes harder and riskier to root the S6e and still have a working phone.
This top of the line device (until the S7 gets here) isn't your average phone to experiment with, try a plain android like a nexus Google phone, there's probably a handful of developers working on the Nexus alone Vs one (maybe) for the S6e?
I know xda forums are all about taking control of your phone but not this puppy, you must surrender to Samsung on this one.
My phone is 6 months old and works great, even after updates it just gets better and better and after marshmallow gets here this phone will be a greater device.
I have stayed stock and never attempted to root because I was following and reading all threads started on the S6e and it was a hot mess, a lot of stuff and phones going wrong at first and as soon as some one found an exploit Samsung had it removed and safe root went right out the window.
I have learned to like stock and I'm ok with it. And my phone works all the time.
Pp.
Click to expand...
Click to collapse
Totally agree!

+2!!!!!

I personally have had no problems with rooting my phone or with custom roms. The only time I had an issue was when I changed my boot splash. The first time I bricked my phone and had to use emergency recovery with Smart Switch. I am also going to suggest you try that before you return your phone. Make sure you backup you internal SD first though because Smart Switch will erase everything. I think it will fix your problem be cause the emergency recovery is started with your serial number. so I do believe it will fix your efs issue. It is definitely worth a try.
Future reference. TWRP does backup your EFS if you click the checkbox for it.