So what is the difference between s-off and root
Sent from HTC desire S Android 4.0.4
powerwill said:
So what is the difference between s-off and root
Sent from HTC desire S Android 4.0.4
Click to expand...
Click to collapse
There is no difference between root and s-off.. Basically if you want S-OFF you need to root your phone.
I Guess you know already what S-OFF and Root means.
Thanks yeah I do know I think I'm new to all this and I want to learn as much as I can before I start messing around with my phone I've already upgraded it which I really regret
Sent from HTC desire S Android 4.0.4
flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
To receive S-OFF it requires a another procedure. For the HTC one i read somewhere that S-OFF is still not possible exept for the Verizon one..
Related
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Pride4u said:
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Click to expand...
Click to collapse
Does it happen on any other ROM, or only on Endymion? Have you tried Reaper and tried to reproduce the problem there?
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Pride4u said:
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Click to expand...
Click to collapse
Why use Unity kernel with Endymion when Endymion kernel is excellent on the ROM by itself?
I would suggest you try another ROM like Reaper and see if the problem persists...
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Pride4u said:
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Click to expand...
Click to collapse
Why I asked you to try another ROM is because if my hunch is correct, you have a hardware problem... I just didin't want to say it till we had ruled out the software issue. This is the exact same thing that happened to my wife's phone a month after purchasing it (Desire S) and HTC put it down to a hardware problem (mainboard) and replaced the device free of cost under warranty (wife never allowed me to touch her phone, so it was S-on, stock!!)
I hope you don't have the same problem, but it sounds exactly like the problem my wife's phone had... the only way is to flash another ROM and see if the issue persists. Make a nandroid backup. What have you got to lose?
What I've got to lose is the time spent, but I guess I have no other choice so I'll get around to it as soon as I find the time.
If it's HW problem I may encounter some trouble as I've bought the phone from an e-shop that sells unofficially distributed phones because they offer considerably lower prices, although it is true that the customer service and complaints may be rather poor.
I'd have to send the phone to them and wait like a month or so until they finally decided that my complaint wouldn't be accepted :-D Not to mention that I would have to unroot the phone and change it back to the S-ON setting.
Anyway, let's hope for the best.
Shameless bump - I'd like to ask a question about Titanium Backup.
I've backed up my installed apps but would like to know whether it will be OK if I back up the system and user data - I don't if it matters that the data will be from a different ROM - in other words, if the system structure doesn't change.
For contacts backup Google sync will be the best I guess.
EDIT:
Installed Reaper 1.6 and the problem is gone. I lost some data in the process as Titanium backup didn't back up the notes from Endymion HTC Notes, never mind, though.
EDIT2: EPIC FAIL! I was probably just unlucky not to see the phone flashing for a long time but today I've seen the screen turning on of its own accord again. Repair service, here I come! :-(
Hi,
Sorry I've been away for a few weeks. I used to follow these threads like a hawk but I just got too busy with a huge dev project that ate my life like they can sometimes do... I read through threads about rooting 1.85 and unlocking...But I'm just confused. Sorry if this is redundant but...
I'm currently on 1.74 (if I'm reading that right, 1.73.502.1 710RD ... oddly enough I tried to update but it didn't let me... assuming that annoying message I kept declining for days was the 1.85 update).
Now I could go to check for updates again but I'm not. I figured I better ask around and see what the best course of action is.
I rooted a while ago when it was first available. So I have root.
So that's where I'm at. Now, my question is what's the best course of action?
Am I not able to update OTA to 1.85? Because I already rooted?
If I can check for updates and get the update, will it remove my root?
The last post in the 1.85 root thread says that they may have fixed their servers to avoid rooting 1.85??
Can I just now unlock my phone and flash ROMs? and not worry about carrier updates?
Is there anything I'm missing with the 1.85 update? That I couldn't get elsewhere?
I may or may not flash a ROM. I just don't want to be prevented from doing so if I want. HTC's Sense is not crashing like it used to, so I have no major need to flash a ROM yet... Improved performance would be the only reason. Maybe some development reasons as well.
Opinions?
Thanks much. I appreciate the help.
crap this isnt under general is it...
tom_m said:
crap this isnt under general is it...
Click to expand...
Click to collapse
Haha no it's not. Also, it should be under Q&A.
You can go ahead and unlock and flash a custom rom. There's no need to get the OTA (which would most likely make you go through the rooting process again). Since your'e already rooted pre-1.85 you can flash a rom and guarantee that you'll retain your root status.
:laugh: Suffer the wrath of trolls.
Nah, I would download the 1.85 firmware update RUU [ran from your computer to install instead of OTA] and root [SOON] or root / unlock bootloader / install custom recovery then flash a new rom. First idea for a rom would be CleanROM. If all you want is root status, I would start there because It gives you basically a clean slate with bloatware removed and some minor tweaks I believe. Otherwise you could use CM9 or one of the few other roms that you may like. Personally I get the best performance out of KingCobra's rom. So idk :b
Gotta add my two sense for unlock and flashing Sick Sense. Very smooth.
Sent from my HTC One X using Tapatalk 2
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
my vote goes to scott standard clean rom! it has eqs, and a couple other little tweaks, that way u can add whatever u want!
tom_m said:
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
Click to expand...
Click to collapse
I have had the same issues with data and have had my phone swapped twice because of it and the 1.85 update nor any of the other radios has made any difference so I would just unlock the bootloader, flash a custom recovery and then rom of choice.
tom_m said:
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
Click to expand...
Click to collapse
There is a new radio that should fix that stuff. Lemme find it. Here ya go. the latest ATT at the bottom. ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L http://forum.xda-developers.com/showthread.php?t=1694012
This should help wifi and mobile data. I also replaced a phone because of the mobile data issues. New phone did it also. Once i installed 1.88 ruu it was all fixed. You dont have to install the ruu now. Just pick your favorite custom rom and then flash this radio. The radio from 1.88 fixes it also but its from an asia ruu,. This new ATT radio is promising, i'd go with that.. Thank Designgears for that leak
Clean rom is good. Sick Sense as well as King Cobra. I'm rockin the new king cobra 1.2 and its pretty amazing. Any of these roms will be much much much better than stock. Tons of great mods, Speed and stability is great with all of them. You will think your CPU speed doubled..No lies! Install Titanium Backup (purchase it) and back up all of your apps. If you get the paid version, you can restore them all to your new rom 1 touch. The free version you have to do each app 1 at a time.
Edit. Of course you are rooted. But did you unlock the BL through HTC Dev also? If you mentioned it i must have missed it. If not you need to do that first.
nugzo said:
There is a new radio that should fix that stuff. Lemme find it. Here ya go. the latest ATT at the bottom. ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L http://forum.xda-developers.com/showthread.php?t=1694012
This should help wifi and mobile data. I also replaced a phone because of the mobile data issues. New phone did it also. Once i installed 1.88 ruu it was all fixed. You dont have to install the ruu now. Just pick your favorite custom rom and then flash this radio. The radio from 1.88 fixes it also but its from an asia ruu,. This new ATT radio is promising, i'd go with that.. Thank Designgears for that leak
Clean rom is good. Sick Sense as well as King Cobra. I'm rockin the new king cobra 1.2 and its pretty amazing. Any of these roms will be much much much better than stock. Tons of great mods, Speed and stability is great with all of them. You will think your CPU speed doubled..No lies! Install Titanium Backup (purchase it) and back up all of your apps. If you get the paid version, you can restore them all to your new rom 1 touch. The free version you have to do each app 1 at a time.
Edit. Of course you are rooted. But did you unlock the BL through HTC Dev also? If you mentioned it i must have missed it. If not you need to do that first.
Click to expand...
Click to collapse
I still have data issues even with the leaked radios.
Tiffany84 said:
I still have data issues even with the leaked radios.
Click to expand...
Click to collapse
What kind of issues? :crying: the same as before? they completely went away for me.:fingers-crossed: Have you seen anybody else still having issues with 1.88 or newer? Maybe you actually have bad hardware..coincidences happen.. I'd swap again if the new radios are working for most others. You paid to much for that phone for it to be poopoo.
nugzo said:
What kind of issues? :crying: the same as before? they completely went away for me.:fingers-crossed: Have you seen anybody else still having issues with 1.88 or newer? Maybe you actually have bad hardware..coincidences happen.. I'd swap again if the new radios are working for most others. You paid to much for that phone for it to be poopoo.
Click to expand...
Click to collapse
Well, I've swapped it 3 times now. The first one I do not remember having that problem. Not saying it didn't but I can't remember. I returned it due to random reboots. Other than that the 1st one was flawless. Ever since then the phones I've received and have swapped have an issue where if I got into work where I have a hard time getting a signal the phone doesn't automatically re-connect when I go outside and have great signal. Even though it shows I have 4g and full bars if you look in the settings menu at mobile network it says turning on instead of connected and the only way to be able to make or receive phone calls or text messages is either toggle airplane mode or reboot the phone. Problem now is I'm past my thirty days so it would probably have to be done threw the warranty and not an in store swap.
Just sent my HTC Sensation off for repair under warranty due to this fault :
Running OpenSensation nightly 20120810 and TamCore 3.0.40 without any issues and updated the nightly every 2-3 days with no issues. had the phone 12 months and had it s-OFF and unlocked about 4 hours after buying it. At that time running CM7 as that's all there was, updated to various ROMs until I settled on OpenSensensation (tried CM9 a couple of times for a few days but prefer OpenSensation). All ROMs installed fine over the past 12 months
Installed Kingdoms and Lords off Google play (huge game 200MB data download via wireless), after first game phone froze and reset. So I reduced the overclock, game running fine. Had another game later on in night playing for about 15 minutes. Phone froze again, switched itself off and didn't come back on again !!!!
Tried charging it thinking battery was flat, no charge. Took battery out as it was an Anker 1900mah just in case it had blown. Put original HTC battery back in, no charge light, nothing. Took battery out and left it out 2-3 hours as suggested on 'net as it 'might' help
No charge, tried another USB lead plugged into desktop. Still no charge .... oh crap
Took to T-Mobile shop I got phone and explained situation, forgetting to mention it was running custom ROM, they tried. Still no charge, no reaction in shop. Zero, zip
They sent it off for inspection/repair yesterday under warranty and said it should take 2-4 weeks
It had been running custom firmware since the day I got it on contract and has never caused me any grief, apart from some roms running better than others while I made a choice which ROM to stick with
Question I'm asking is can HTC still test the phone even though its not taking a charge or I assume not powering and just froze and died, assuming the motherboard is fine does anybody know if they use test points that bypass the USB socket to power it up
And how can just playing a legitimate game downloaded off Google Play freeze the phone and shut it down never to power up again
I'm guessing the possibilities of a faulty USB charge socket, faulty power switch or fried CPU/GPU/motherboard considering it just froze and died
I used it as a phone but did play games quite a lot during the day when I had a few minutes while not working, and had it overclocked to around 1625-1728 which it ran stable at without overheating
If they send it back refusing to touch it due to finding custom firmware on it I'm looking at the Samsung galaxy SIII over the HTC Nexus One simply because the Samsung has a removal battery and additional microsd card slot where for some reason I assume is to make rooting more awkward the HTC has a hardwired battery and NO extra sim card slot. I was looking to replace it when my contract expired in February but if they refuse to fix it citing custom firmware (even though it has been working perfectly for 12 months running various custom firmware) I have no real choice but to buy out my contract and get a new contract. Bummer
Hmmmm,
Reading a few postings it appears there is a possibility that the motherboard is fried somehow, or a 'hard brick' through a bad ROM install ... I wasn't updating and firmware, not updating any ROMs
Just playing a game downloaded and installed off Google Play, but if it means the motherboard is fried then at least it means HTC will have to replace it as 'faulty' so saving me the upfront cost of buying out my contract thas has 6 months to run
Actually if you overclock the device or flash a kernel htc doesn't have to replace anything.. by "playing a game downloaded from google play" you mean "playing a game downloaded from google play on a device controlled by custom drivers which clearly make your device out of warranty". So I'm not sure.. altough it's possible that it's not the fault of the kernel but the mainboard had some issues. They are able to test the charging port and the main board seperately. Let us know abouth the end.
It would interesting to see HTC's response either way so I'll report back once they have a look at the phone
As I don't have a loan phone at present so have no phone until they get one back from customers having their phone repaired, I have to use the 'net to check on the status of the repair via the T-Mobile website
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
thescrapyard said:
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
Click to expand...
Click to collapse
for replaced mother boards ..there is a different version of jb ..check my soff guide ..link in my signature
Will let you know how it goes, thanks
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
thescrapyard said:
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
Click to expand...
Click to collapse
for flashing eng-hboot aka changing from LOCKED to Juopunutbear
check the troubleshoot point #3 solution in my soff guide ..its explained there
and for thanks ..there is a button to say that
All sorted, now running the latest nightly of Kanga JellyBean 4.1 and full rooted and back to how it was before the motherboard dies, apart from running Android 4.1
Also feels much smoother and much faster, even though its only running the default slight overclock that Kanga sets as teh default, so might leave it at that as it feels faster than previous when running OpenSensation 4.03
Great stuff
I couple of months ago I bought a Sensation XE (beats) which came with ICS. My previous phone was an Incredible S but I got the sensation primarily for it's bigger screen (and on paper faster CPU but I can't say in normal use that made any difference)
However, after living with it. I found that the more I used it, the more it annoyed me:
- the vibrator didn't always work, but would sometimes work after have the phone a shock (as was described as a fix on this forum somewhere).
- mobile data after I had been using wi-fi. The G/3G/H icon was there but when you try to use an app that needs data it just waits and eventually times out complaining about no connection. Data would come back after a reboot but that soon got tedious.
My previous phone (an Incredible S) was rock solid on gingerbread but went flaky after it's ICS update (bluetooth problems mostly) so although at first I thought perhaps I had a dodgy handset, I had been wondering if the Sensation might be better back on gingerbread.
I had looked into what was involved to downgrade but it seemed like a lot of faff (I was sim-free on hboot v1.29, S-On, HTC unlocked, Rooted) but this week-end I finally decided I'd had enough and was even thinking of selling it, but decided to try gingerbread first. After about 6 hours (!) it's back on GB.
Today is Tuesday, I reverted it on Friday so it's been running for about 3 1/2 days. So far (touch wood) neither of the earlier problems have presented themselves (and no new problems have appeared).
With the HTC overlay the difference between the ICS and GB (visually) is actually very slight IMHO, ( especially since I don't use the stock launcher anyway) and other stuff like general speed of response and battery use seems no different.
So, in summary, at the mo, I think it's the best decision I ever made about this phone. If you are getting beaten up by ICS I'd recommend giving this a thought.
[This is a repost - because I originally posted in the Sensation Q&A forum by mistake..]
Hi , How are you downgrading Hboot 1.29 with S-On ? I have the same phone and been looking for a way to downgrade back to GB for a year now lol
scaffman said:
Hi , How are you downgrading Hboot 1.29 with S-On ? I have the same phone and been looking for a way to downgrade back to GB for a year now lol
Click to expand...
Click to collapse
With S-ON you can't downgrade
You have to S-OFF first
Sent from my HTCSensation using xda premium
I had good battery life before rooting 4 - 1/2 hours, once I rooted / installed custom recovery and flashed the .17 modem battery life went to hell.
I just flashed back to complete stock and relocked the bootloader and then did a factory reset just for overkill and to be double sure it's complete stock. after rooting I experienced draining straight from 100% to 0 really quick without any usage, getting maybe an hour of on screen time.
the battery graph would be a rather steep line straight down even when the phone wasn't being used at all for hours.
I tried installing the .23 modem again, flashing stock 4.2.2, cyanogenmod and purity and always experienced the same issue. Starting to think it's a GAPPS issue not the rom. Anyway hopefully the complete stock image with a locked bootloader will fix my issues.
I was getting this every time I flashed a stock or custom rom, without installing a single app. Just using what comes with the stock or custom rom.
At this point I'll be happy if I just get my battery life back from going to stock, but I want to know if anyone else has experienced similar issues
At some point I might consider rerooting because I'm a tinkerer at heart and just curious if other's have experienced this.
Just rooting should have had no impact on battery life. How did you root it? Don't use a tool kit
jd1639 said:
Just rooting should have had no impact on battery life. How did you root it? Don't use a tool kit
Click to expand...
Click to collapse
I used Wugfresh's Nexus Root Toolkit.
I've used the same toolkit with each of my nexus device's
Galaxy Nexus, Nexus 4 and now Nexus 5 and I've never had an issue with his toolkit before.
You only have problems when you don't check and make sure the usb driver's are 100% working before using it.
It did instal TWRP as well as rooting. Run the EFS backup script and install the .17 modem from the modem thread.
But again I've used his toolkit's for years without issues, I really don't think it was the toolkit, everything is working perfectly, I used the same toolkit to return to stock and relock my bootloader.
everything worked perfectly.
While I know how to usb adb and did it many times in the past, Heck I even did the pin shorting bootloader unlock on my htc rezound. (I'm not inexperienced)
But, I've grown lazy and not quite the flashaholic I used to be, so I normally wait a few months now, enjoy stock android on my devices until the toolkits are updated and working well before playing with my phone.
movielover76 said:
I used Wugfresh's Nexus Root Toolkit.
I've used the same toolkit with each of my nexus device's
Galaxy Nexus, Nexus 4 and now Nexus 5 and I've never had an issue with his toolkit before.
You only have problems when you don't check and make sure the usb driver's are 100% working before using it.
It did instal TWRP as well as rooting. Run the EFS backup script and install the .17 modem from the modem thread.
But again I've used his toolkit's for years without issues, I really don't think it was the toolkit, everything is working perfectly, I used the same toolkit to return to stock and relock my bootloader.
everything worked perfectly.
While I know how to usb adb and did it many times in the past, Heck I even did the pin shorting bootloader unlock on my htc rezound. (I'm not inexperienced)
But, I've grown lazy and not quite the flashaholic I used to be, so I normally wait a few months now, enjoy stock android on my devices until the toolkits are updated and working well before playing with my phone.
Click to expand...
Click to collapse
Problem is on the rooted device? BetterBatteryStats log.
battery life is determined by your personal setup, your personal usage, your personal management of your apps installed, and the quality of your personal phone/data signal. everything else will have a minor impact on battery. root has nothing to do with your battery life, it only gives you superuser permissions to use root enabled apps.
simms22 said:
battery life is determined by your personal setup, your personal usage, your personal management of your apps installed, and the quality of your personal phone/data signal. everything else will have a minor impact on battery. root has nothing to do with your battery life, it only gives you superuser permissions to use root enabled apps.
Click to expand...
Click to collapse
I know this, but that's the thing I eliminated most of this. I experienced this on multiple roms stock and custom with only the normal GAPPS apps installed nothing else. I even turned google sync off. Signal quality is poor in my apartment, but it's always been poor and I've had always gotten 4 1/2 hours on screen and a full day out of my nexus 5. the poor signal quality didn't change before or after rooting and neither did the android version it was 4.2.2 both before and after rooting. I didn't upgrade to 4.4.2 and immediately root or anything.
Regardless of if I had sync on or off and what google apps I was using, something else system wise had to be messed up in order to go from 4 1/2 hours SOT (with about 50 apps installed) to 1 hour SOT with only google's stock rom apps installed)