Related
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
ThomasHunter said:
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
Click to expand...
Click to collapse
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
NQNH said:
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
Click to expand...
Click to collapse
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
ThomasHunter said:
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
Click to expand...
Click to collapse
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
NQNH said:
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
Click to expand...
Click to collapse
Yeah, I'm S-On. Was just wondering if I could also flash boot.img via recovery, instead of via fastboot. But I'll use fastboot then. Thanks a lot!
I have HTC One x (At&T) US Version and using it in India.
It has Stock ICS 4.0.4 and Already Rooted,
Already S-OFF,
has Custom Recovery TWRP and
SCID is 111111111 and
Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 .....
Now my Questions is :
1. How to Update is to jelly Bean and if i Update it to Stock/Custom jelly bean then do i have to unlock/S-off it again? If Yes then How to do it? Any Given Link will be Highly Appreciated.
2. I read some Posts/Comments on some 4.2.2 Custom roms threads that "Highly recommend latest Jellybean firmware".. what does that mean? (my confusion is if i already have latest jelly Bean Firmware then why would i search update for jelly bean? )
3. if it is recommended to have latest jelly bean firmware before update to 4.2.2 then can anybody give me the link for that?
4. HTC One x AT&T has beats Audio.. if i update it to Any 4.2.2 Custom Rom.. then will beats Audio Work on new Rom? (I know it is Noob Question but i really want to know because i want Beats Audio For Music)
Thanks in Advance
1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita
timmaaa said:
1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita
Click to expand...
Click to collapse
First of all thanks a lot for replying So fast and giving your time to help me...
my bootloder details:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-1.14.0002
and also my Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 ..... is it ok or first i need to update both ?
If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita
timmaaa said:
If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita
Click to expand...
Click to collapse
i have build number 2.20.502.7.. do i still need 2.15 firmware?
For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita
timmaaa said:
For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita
Click to expand...
Click to collapse
i am stuck at firmware...this error comes everytime... screenshot attached... please see ...
Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita
timmaaa said:
Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita
Click to expand...
Click to collapse
everything has done successfully... thanks a lot for you help...
but
when i rebooted my phone (ICS) and gone to Settings>about>Software Information... it still showing 2.20.502.7 710RD.... is it normal or something is wrong..... Attached Screenshots both.. phone and my command window.... please check this.. (i am sorry i am disturbing u
a lot coz i am noob :'( )
You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita
timmaaa said:
You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita
Click to expand...
Click to collapse
Yes, i have already installed Custom Recovery TWRP... now i think all i need to do is install a ROM .... so should i directly install any 4.2.2 custom ROM or first i should install 4.1 then after 4.2 ?
You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita
timmaaa said:
You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita
Click to expand...
Click to collapse
Oh!! yehhh .. nice nice nice... thanks a lot a lot a lot......u r really nice person... u made my Day...
No problems, glad I could help.
Sent from my Evita
timmaaa said:
No problems, glad I could help.
Sent from my Evita
Click to expand...
Click to collapse
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
and i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?
info2shail2010 said:
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
Click to expand...
Click to collapse
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita
timmaaa said:
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita
Click to expand...
Click to collapse
i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?
Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita
Click to expand...
Click to collapse
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5, where to find and what to check in it and how to check ?
info2shail2010 said:
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5 and what to check in it ?
Click to expand...
Click to collapse
Ok there's your problem, TWRP 2.5 is full of bugs. Download the modified version of TWRP 2.6*from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to install the ROM.
An md5 is like a digital fingerprint of a file. It will be listed on the download page for a ROM/kernel/radio. What you do is use an md5 checking app/program to check that the md5 of the downloaded file matches the md5 listed on the download page. If it matches you're all good, if it doesn't match it means the file became corrupted during the download. You should always check the md5 of anything you're about to flash, a corrupt file could damage your phone if you install it.
Once you have installed the ROM you should reboot back into TWRP and use the backup feature to backup system/data/boot. Then if you have any problems in the future you can use the restore feature to restore it and you'll have a working OS.
It's also a good way to have your favourite ROMs backed up. Once I decide I like a ROM I set it up with all my apps and settings and then make a backup. That way if I ever want to use that ROM in future I can easily restore the backup and have a fully setup ROM ready to go. It's much easier than installing a ROM from scratch and setting it up all over again.
Sent from my Evita
Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon
EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)
Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon
Hi Guys,
Yesterday I revived notification that new update is available, so not thinking much I installed it. After update I realized that my phone is not getting service, or getting it only outside, for short time.
My current version of CM is 11.0-XNPH05Q. I rooted my phone today and now I am wondering if I can install this version of CM - cm-11.0-XNPH33R-bacon-signed-fastboot_16GB?
I know this might be silly question but I am complete newbie, please advice.
Thank you!
Just flash one of Calkulin's stock rooted ROMs from the dev section, he has one for each CM11S release.
Transmitted via Bacon
timmaaa said:
Just flash one of Calkulin's stock rooted ROMs from the dev section, he has one for each CM11S release.
Transmitted via Bacon
Click to expand...
Click to collapse
hey, I want to downgrade to 44s too (as I have bluetooth problems). I'm fully stock and not rooted at all( :cyclops: ), I updated to 05q manually by flashing zip in stock recovery... can I downgrade the same way? flashing 44s zip (I guess it's full and not incremental like 05q) without wiping anything to keep my data?
FreakyDR said:
hey, I want to downgrade to 44s too (as I have bluetooth problems). I'm fully stock and not rooted at all( :cyclops: ), I updated to 05q manually by flashing zip in stock recovery... can I downgrade the same way? flashing 44s zip (I guess it's full and not incremental like 05q) without wiping anything to keep my data?
Click to expand...
Click to collapse
No you can't, you need to unlock your bootloader and flash the stock images with fastboot to downgrade properly.
Will this void the warranty?
ashrafmansuri said:
Will this void the warranty?
Click to expand...
Click to collapse
Nope. It's pretty much impossible to void the warranty on one of these things. You can unlock the bootloader, you can root it, you can install custom recovery, custom ROMs, custom firmware, custom kernels. Pretty much the only things that void the warranty are bricking it, and physically opening the device up.
Transmitted via Bacon
timmaaa said:
Nope. It's pretty much impossible to void the warranty on one of these things. You can unlock the bootloader, you can root it, you can install custom recovery, custom ROMs, custom firmware, custom kernels. Pretty much the only things that void the warranty are bricking it, and physically opening the device up.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank You for the great info
After clean flashing multiple ROMs, I have a mobile network signal battery drain problem that is severely reducing my battery life. I used to be able to get nearly double the amount of battery life I currently get when I was on stock CM11S. Is there a way to check what is happening and what is causing the drain? I already greenified pretty much all apps.
geokilla said:
After clean flashing multiple ROMs, I have a mobile network signal battery drain problem that is severely reducing my battery life. I used to be able to get nearly double the amount of battery life I currently get when I was on stock CM11S. Is there a way to check what is happening and what is causing the drain? I already greenified pretty much all apps.
Click to expand...
Click to collapse
Looking at the screenshot, I feel that you are on Lollipop ROM.
I suggest you to visit general section of this board and check out the index thread (sticky thread) and find out the links for modem (radio) threads
Try flashing different modems which are compatible with your ROM and use the modem which gives you good network signal.
You need to download the compatible modem zip or img, and if it is a zip, you can directly flash via recovery like TWRP or if it is a img file, you need to flash from bootloader mode using fastboot commands
Mr hOaX said:
Looking at the screenshot, I feel that you are on Lollipop ROM.
I suggest you to visit general section of this board and check out the index thread (sticky thread) and find out the links for modem (radio) threads
Try flashing different modems which are compatible with your ROM and use the modem which gives you good network signal.
You need to download the compatible modem zip or img, and if it is a zip, you can directly flash via recovery like TWRP or if it is a img file, you need to flash from bootloader mode using fastboot commands
Click to expand...
Click to collapse
Yes I am on Lollipop. Still getting used to it. Kit Kat was much better in my opinion even though it's much older.
I've downloaded a couple modems and firmware files, including the latest one by @jgcaap and the latest OxygenOS firmware. Both as I understand, include modem files which are named NON-HLOS.bin. I flashed the OxygenOS firmware in TWRP 2.8.6.0 but the baseband version remains the same, ending in NAZM-1. I then extracted it and flashed the Oxygen NON-HLOS.bin via Wugfresh and the baseband version is still NAZM-1. I know I'm not the only one having troubles flashing firmware and modem files via TWRP 2.8.6.0 or 2.8.7.0 but it appears that flashing via fastboot (Wugfresh) doesn't work either? Or am I doing something wrong here?
geokilla said:
Yes I am on Lollipop. Still getting used to it. Kit Kat was much better in my opinion even though it's much older.
I've downloaded a couple modems and firmware files, including the latest one by jgcaap and the latest OxygenOS firmware. Both as I understand, include modem files which are named NON-HLOS.bin. I flashed the OxygenOS firmware in TWRP 2.8.6.0 but the baseband version remains the same, ending in NAZM-1. I then extracted it and flashed the Oxygen NON-HLOS.bin via Wugfresh and the baseband version is still NAZM-1. I know I'm not the only one having troubles flashing firmware and modem files via TWRP 2.8.6.0 or 2.8.7.0 but it appears that flashing via fastboot (Wugfresh) doesn't work either? Or am I doing something wrong here?
Click to expand...
Click to collapse
You are absolutely correct.
Last suggestion would be
Flash CMOS12 fastboot images
Complete system wipe including internal storage is recommended
That's the last try you can do
Mr hOaX said:
You are absolutely correct.
Last suggestion would be
Flash CMOS12 fastboot images
Complete system wipe including internal storage is recommended
That's the last try you can do
Click to expand...
Click to collapse
Is the mobile network bar supposed to be completely filled like that though? Or should it have black spaces in between?
I had already flashed the latest CM12S images in the past as you recommended but it didn't change anything.