Related
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
Ok, Hey Everyone, I'm kinda new to these forums, I have a question, one that has been bugging me a while now.
First off I had a cyanogenmod rom, I think it was 6.1. Then after a while I decided to Un-Root my G1, and go back to stock, so I did. But when I went back to stock I noticed that my camera would always force closes, I can't get into it. It happens all the time.
Then I tried Rooting again, and I flashed this rom called "GinSense" (a very fast and stable rom) by Rushness, But still my camera force closes. I really do not now why because it can't really be my kernal (which sometimes causes camera to force close) because when I un-rooted it would have been back to stock also.
Please I hope someone can help me, its really got me confused, so I turned to you guys.
I hope this way the right place for my post.
Get a new phone
But not knowing the exact procedure that you used to go back to stock, you still might have not flashed the kernel or something else could be wrong. I would try using the instructions here. If you have already tried that, it wouldn't hurt to try it again.
If that doesn't work, when the camera force closes, were you able to at least get into the camera app for a few seconds and see if the camera was actually working before it FC'ed? I know with my G1 (long long ago), I had an issue with the camera and it was the connection on the sensor going to the board.
You might be able to have better luck posting here. I see another user has posted about his camera not working either here. Search next time, it really comes in handy.
Thanks
hhilton said:
Get a new phone
But not knowing the exact procedure that you used to go back to stock, you still might have not flashed the kernel or something else could be wrong. I would try using the instructions here. If you have already tried that, it wouldn't hurt to try it again.
If that doesn't work, when the camera force closes, were you able to at least get into the camera app for a few seconds and see if the camera was actually working before it FC'ed? I know with my G1 (long long ago), I had an issue with the camera and it was the connection on the sensor going to the board.
You might be able to have better luck posting here. I see another user has posted about his camera not working either here. Search next time, it really comes in handy.
Click to expand...
Click to collapse
Ok, Thanks for your reply. I will try the instruction on that link and post back. No when I enter my camera I see nothing but a black screen then it tells me to force close about 5 seconds later.
Edit : BTW Can a dev move my post or something, as well I don't want to get hated on for creating a second post about the same thing? xD
Flash cm6.1 again
Sent from my HTC Wildfire S using xda premium
Yeah
Android311 said:
Flash cm6.1 again
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
Yeah, I was thinking on doing this, but for me that rom goes unstable after about a month or 2, so its just a waste of time.
This rom I have now runs so smooth I don't really want to change
Ok, So after un-rooting, re-rooting, trying different kernals, and everything, it still doesn't work.
I think it must be hardware.
What rom are you running?
Sent from my HTC_A510c using XDA
GinSense
Android311 said:
What rom are you running?
Sent from my HTC_A510c using XDA
Click to expand...
Click to collapse
I'm running GinSense 1.0, but after Un-Rooting and it still not working, So I currently have my phone opened up infront of me, to see if there is anything wrong I'm video taping it xD I don't know why.
Is there any more custom roms? Maybe they are just buggy
Sent from my HTC_A510c using XDA
Yay
OMG, It actually worked, So it was a hardware problem, I think it may have been a lose cable, because I pulled the camera cable out and put it back in. Couldn't believe it actually worked.
That's good man, glad you fixed it
Sent from my HTC_A510c using XDA
Hey guys, so I just finished up changing my infuse over to Legend 2 ICS edition and I've been playing with it for about a week and I'm having a rather large issue. Whenever I leave the gps ability enabled so that my apps can find where I am the phone has a tendency to dump battery life like there is no tomorrow but worse than that it stops sending and accepting text messages randomly while the rest of the phone continues to operate. There are no warning signs so that I know this is happening and I have to reboot the phone to get it to work again. If I leave the gps feature off this is not an issue however, this is rather useful to have running so that my apps all work. Any idea how to fix this problem?? Thanks for your time.
I've been running legend 2 for almost a couple weeks and legend before that, my gps was buggy at first-it wouldn't lock on to my location. I did a complete wipe and reinstall, then let the phone boot up and let it settle for a while before I did anything else. Haven't had any problems since
---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1318160
http://forum.xda-developers.com/showthread.php?t=1561463
use clean wipe, I run that a few times just before I flash a rom now, haven't had any problems since I started using that.
Thanks a bunch I'll try that out and get back to you on if it works or not in the next couple of days.
Thanks
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Klevin2011 said:
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Click to expand...
Click to collapse
Hmmm, the phone shouldn't be overheating at all, do you do any tibu system restores? I've had an app cause an overheating problem before. One thing I've learned is when you do allot of flashing, checking out different roms or themes, its good to just do an odin or hemdall flash back to stock that has repartitioning.
It gives you a fresh start.
TiBu
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Klevin2011 said:
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Click to expand...
Click to collapse
Have you tried the new version 3 to see if maybe that helps? This is first Ive heard anything like this. I guess it works fine using another rom?
Sent from my SAMSUNG-SGH-I897 using xda premium
I didn't even know there was a version 3. I'll have to go take a look at that and see what happens. Thanks for the help.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Still having issues
Ok so I'm still having an over heating issue and my phone refuses to send or recieve texts for periods of time. I'm going to delete a couple of apps to see if they're causing the problem. If that doesn't work any chance that I'm having a hardware issue with the phone, it wouldn't be the first time I've had issues this would be my 5th replacement due to hardware issues in the phone.
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2
Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?
Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...
No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium
I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2
I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd
After doing some digging I see there is a new LS996ZV5 update. I am rooted so have not gotten any OTA notifications. Has anyone gotten it and does it help with lag and battery?
My phone seems pretty snappy as is but always want the latest if possible.
Guess one last thing. What are thoughts on timetable of custom recovery and maybe some rooted roms for us Sprint users?
Any discussion welcome!
Sent from my GT-N8013 using XDA Free mobile app
Got the update OTA this morning (I am stock). Phone is absolutely flying now.
Not sure on battery life yet as it's only been a couple of hours since I updated.
I unrooted and took the system update. It wasn't the new firmware though. Not sure what it was. I tried to have phone look for firmware update afterwards and it didn't show the new one yet.
Sent from my GT-N8013 using XDA Free mobile app
I'm rooted and received the android system update notification this morning. Should I proceed, or is that a bad idea if rooted?
zoundguy said:
I'm rooted and received the android system update notification this morning. Should I proceed, or is that a bad idea if rooted?
Click to expand...
Click to collapse
it won't work while rooted, i've tried, twice. i'm waiting on the update prompt again to try my next thing, but if you want to try it feel free. if you open up superuser and go to the settings there is an option to fully unroot the device, its towards the bottom. After you do that restart and then try and apply the update.
let me know if it works! hopefully i get the update prompt again in the morning and will finally be able to get this thing updated!!!!
So curious as to what this update was. All I know is that today my battery life isn't nearly as good. Normally after working for 8hrs my phone is around 75%... Today it was at 40%... Massive difference and i did nothing out of the ordinary
That sounds like my phone, I've noticed that I Google services is using more battery than the screen recently.
Sent from my LG-H959 using XDA Free mobile app
My battery life has actually been really good. I was getting 15-20 hrs before the update and now I am getting 25-30 hours after. (Light use)
My battery seems pretty good also. Plus it does appear the widgets are loading faster and less jumpiness between screens. Rerooted after the update and all seems fine so far
Sent from my LGLS996 using XDA Free mobile app
i didn't get prompted with the update again this morning so i wasn't able to try anything to get my phone to update today. if someone hasn't applied the update yet but has the prompt would you be able to grab the update file and post it? i'll do the same if i get the update prompt again and nothing has been posted yet. at least that way we can try stuff without having to wait for it to decide to check for an update since the manual update check doesn't appear to do anything.....
Hmmmm. I guess I'll use GServiceFix app. See if that solves my issues
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
Yeah. Its the android system using the battery. Used this fix app before and it solved my problems. Hopefully its still reliable.
again this morning, no update prompt and the "check for update" function continues to say i'm up to date. because i had issues with my first two i signed up for sprint insurance. if i don't get prompted for the update by monday morning i'll stop in a sprint store and see if i can get it swapped again. only problem with that is chancing getting one that overheats or has a bad screen like my previous two did
i rooted and got the OTG upgrade message, and i try but it show error and said my device is rooted then can't upgrade software. Then i try to use "fully unroot" in supersu, the supersu gone, but the error still shown. do anyone know how to unroot and upgrade? thank you very much!
johnsc said:
i rooted and got the OTG upgrade message, and i try but it show error and said my device is rooted then can't upgrade software. Then i try to use "fully unroot" in supersu, the supersu gone, but the error still shown. do anyone know how to unroot and upgrade? thank you very much!
Click to expand...
Click to collapse
sorry, you are stuck there are a couple of other threads with further discussion on it but so far no one has been able to get the OTA to apply after they have rooted. some of us have been able to get new devices through sprint with having their insurance and play it off as the OTA won't update. they have had enough issues with the device they don't really question it.
shuka325 said:
After doing some digging I see there is a new LS996ZV5 update. I am rooted so have not gotten any OTA notifications. Has anyone gotten it and does it help with lag and battery?
My phone seems pretty snappy as is but always want the latest if possible.
Guess one last thing. What are thoughts on timetable of custom recovery and maybe some rooted roms for us Sprint users?
Any discussion welcome!
Sent from my GT-N8013 using XDA Free mobile app
Click to expand...
Click to collapse
can you post the zv5 ota files here. i need it to save my dead phone
Help! On screen buttons not working!
I really need help. I factory reset my LG G Flex 2 cause I wanted to erased my info and give it as a present to my father for his birthday next october 14 and now the onscreen buttons don't respond, only the back button, nor the multitasking or home button. I turned it off and on, reset it several times, cleared the partition cache or whatever it is called but no luck, mine is running LS996ZV5. It was perfect before the reset. I feel so bad. Thanks in advance for your help.