Related
Hello,
I plan to upgrade my Australian (Telstra) Motorola Defy to an Android 2.2 (Froyo) ROM that is ideally without Motoblur.
I have comprehensively read hundblues of the Defy modding threads through Search, Browsing and Cross-Links on XDA, however there are still a few areas I am still unsure about and feel the need to ask.
I absolutely require downgrade-ability back to the Telstra stock firmware (A variant of 2.21), Because if I become affected by the Speaker issue, then I will need to restore to stock for Warranty.
I am also conscious of using the Chinese 2.2 ROM due to risk of blowing the Camera Flash LED.
Maintaining Downgrade-ability
Higgsy has made a thread how to upgrade to 2.2 (Froyo) without losing downgrade-ability, but I am not clear on a few points, my comments are in blue
Instructions in the thread:
"Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here [http://www.sorensiim.dk/higgsy/.sbf/2.2CN_SBF.zip] Is this the unmodified Chinese 2.2 ROM?
Need the system.img nandroid and boot/devtree.sbf – Download here [http://www.sorensiim.dk/higgsy/TMOB_US_3.42_Files.rar] This must be the "Tmob 3.42 system image(pre rooted)"
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear [http://www.sorensiim.dk/higgsy/GB_3.4.2_system.img.rar]
• Flash the Chinese .sbf by RSD lite OK I understand that the Chinese 2.2 ROM is downgrade-able, makes sense so far
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder) What makes this 3.4.2 ROM different from the others in that it is still downgrade-able?
• Once restoblue pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done. See below about Camera Flash LED issue
If you want to use the GB release then just restore the system.img from the GB release. Similar to the T-Mobile 3.4.2 ROM, what makes this UK 3.4.2 ROM downgrade-able?
"
If there has been a modification done to the T-Mobile / UK 3.4.2 images provided which makes them downgrade-able, what is it?
Can it can be applied to other 3.4.2 ROMs too (eg: Finland 3.4.2 155-002 which is Blurless).
Based on Which SBF code group prevents downgrade, I am guessing that the CDT(CG31) has been removed from the image (to keep CDT on version 2), but I'm also guessing that this would also screw up SYSTEM (CG39) because that would also need to stay on version 2, when 3.4.2 uses (and needs to be?) version 4 (or else it will screw up the signature?).
Preventing the Camera Flash LED from blowing when the Chinese 2.2 ROM has been used
I seem to have found two theories on this one:
1. Higgsy's 'Devtree' theory (see thread above) that the Devtree in the Chinese 2.2 ROM is causing the issue, and a Devtree copied out of a different ROM should be used. (This leads to more questions: What is the Devtree? Where is it located? How is the Devtree copied out of a ROM? I can't find any information about Devtrees)
There is a followup post in this thread in reference to the Devtree theory which says "I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?"
I am not sure if this users's reference to the "flash fix" is referring to the 'Devtree' fix or if it was another "flash fix" that they tried. Nor do I know if the user followed the instructions for this "flash fix" correctly, but it is casting some doubt if the Devtree fix is correct or not?
Also in the instructions above, if the T-Mobile or UK 3.4.2 image is flashed after the Chinese 2.2 ROM was installed, wouldn't the non-Chinese Devtree already have been installed?
2. 'build.prop' theory
The post reads:
"I was going through build.prop for some thing else and noticed these settings on my 3.4.2-145 build.
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
What are these set to for the Chinese ROM?"
There are no followup posts to this to confirm the values of the Chinese ROM, to confirm that this prevents Camera Flash LED burnout, or to confirm that this doesn't work.
Or use the downgradable method I list in my post (http://forum.xda-developers.com/showthread.php?t=977989).
That way you dont have to flash any chinese firmware and worry about camera/flash issues.
Your ROM seems to be just what I am looking for. I want to be as close to the Stock Android Experience as possible (I've tried Motoblur and it's not for me) and without the bloat.
I have a few questions about the process that Barebones uses, because I think that it's important to learn what I'm actually doing.
"2. Restore your Froyo Nandroid of choice.
Barebones: CEE3.4.2_155-002_DEBLUR.Nandroid.zip"
I guessing that this contains ONLY the SYSTEM partition, which has been taken from the unmodified CEE 3.4.2-155-002 Deblur ROM, as the SBF method would change the version making it un-downgradeable?
"Flash the fixed sbf.
Barebones: Fixed.CEE.3.4.2_155-002_DEBLUR.zip"
I guessing that this "fixed" version contains unmodified CEE 3.4.2-155-002 Deblur partitions PDS, LBL, MISC, BOOT, CACHE, USERDATA & KPANIC, but not CDT (To allow downgrade), SYSTEM (To allow downgrade, it has already been installed at Step 2 instead?) and RECOVERY (To retain Clockwork Recovery)?
"5. Reboot into Froyo; install Clockwork Recovery; copy Barbones to sdcard.
Barebones: Barebones_12-signed.zip"This must be the bit where all the modifications of Barebones itself are made? And hasn't Clockwork Recovery already been installed to the RECOVERY partition from Step 1 or does Clockwork have elements that need to be reinstalled? (eg: in the BOOT/SYSTEM/USERDATA partitions)
"Swype, Gtalk, Voice Commands, GreekIME, CarDock, Recovery, and Easy Installer -> Download update.zip"With the Extras package, can these components be installed separately or are they all installed together? Some of these extras may not be applicable like GreekIME (If the user is not Greek).
Is the Swype in the package the same as the latest Beta from beta.swype.com and isn't Clockwork Recovery supposed to be already installed?
Also, is there a way to reinstall some of the 'Removed' APKs like BlurAlarmClock, Calculator, ClockWidget, DLNA, Quickoffice, WeatherWidget (assuming that these APKs will still work on their own) or will I need to copy them before installing Barebones_12-signed.zip
Finally, you have done a great job so far and it is far better than anything else out there for the Defy at the moment, thank you.
My only bit of [constructive] criticism (and I am by no means ungrateful) is that I think that some of the Added & Value Added features of Barebones (especially the Wallpapers and Sounds) would be more suited to the Extras package (as optionals) to keep in line with the goal rather than being bundled in the Barebones package.
Barebones faqs. . .
Why its downgradable ?
This works is because the fixed sbf has partitions taken out; specifically CG31 (CDT) and CG39 (System). Reason being these are the parts of the sbf that prevent you from downgrading. So, this lets you make up the rest of a 'whole' rom using the nandroid; and bingo Froyo with downgrade.
Barebones.zip ?
Unlike some of the other roms posted here, which are nandroids, this one is based on an update-script. Meaning it just changes a stock rom into Barebones; does not restore a complete system. So a factory reset is not enough.
Why install clockwork a few times ?
Nandroid doesnt come with the app, my rom doesnt come with it; yes clockwork is installed just not the apk, so you need that to boot into recovery. Reason why, defy bootloader is locked - so recovery has to be initiated from within the android os, hence bootstrap.
Update.zip ?
If you read the build info it states that it copies all the extras to the sdcard. While Easy Installer is the only program in that update that get installed automatically. Point being you use it to install whatever you feel is missing and delete the rest.
Other apk's not in update.zip ?
Not my problem, I cant please everyone; and I'm not going to make update.zip's with every apk under the sun. The update.zip is already half the size of my rom, so . . . Barebones ? Maybe use adb to pull /system/app after you restore the nandroid and before Barebones. You could then copy them back to the /system/app folder after Barebones is installed. If you try to install the apk's before Barebones they will be erased by my update-script. To be honest I probably didnt include most of these apk's because they must be installed to the /system/app folder (eg: MediaGallery, BlurAlarmClock). They just wont install to /data/app.
But its not Barebones . . . .*tear
OK I get it guys, my 380kb of extra noise's offends, so wait for v1.3 if its too much. This is my first android phone, I got it in December; I learned to cook this rom in that time (so google and read). So lets face it, I make this rom for my phone; just sometimes other people like it too.
Hope this clears up a few things . . . and enjoy the rom.
Hello,
i have some Problems with my Galaxy Nexus. I still try to Upgrade my Android from 4.1.2 to 4.2.1 but it allways, if CWRM check the Hashes, occur an Error and stop the Upgrade (OTA). It says, that the Build.prop have wrong hashes (i think, it is the problem, because there was postet a lot of letters and digits, looks like a hash). I used once a little hack, to enable my Bootsound but i deleted it and the entries in the build.prop also. So, where is the problem? I hope you can help me
Greetings
DrTrax
Phone: Galaxy Nexus
Android: Stock Android 4.1.2 (JZO54K)
Kernel: Stock Kernel
Root: YES (Superuser)
Busybox: 1.20.2-cm9
you modified your build.prop. thats all it takes.
you need an original build.prop to get the OTA.
okay and how could i restore it (whitout reinstallation)?
i never did a Nandroid, i only did a normal backup with the Galaxy Nexus Toolkit
Grab the build.prop from JZO54K factory image and push it to /system.
sent from my Google Galaxy Nexus
Hmm, i can't unzip the System.img :/
7Zip, WinRAR, unyaffs, deamon tools and VirtualBox couldn't unzip/mount or open it
Linux also don't unzip it
Can someone post the build.prop of a Galaxy Nexus (Android 4.1.2 yakju)?
I grabbed a Build.prop from my Friend's Phone (The same Phone, same Android, just non-root) and still don't work. Maybe, i must force the Update but i don't know how and what will happen with my Data (Apps, Data, Music, Videos, ...)
You can't 'force' the update, if you've modified it somehow that's why it's not working and until you get it back to stock it will continue to not work. You're better off biting the bullet and flash the stock factory image to 4.2.1 and then set the phone up again (backup sd card first, tho)
Okay, i fixed it
Well, problem was not really the Build.prop (Why did it prompt, that there was something wrong with the build.prop?!)
Problem was, that many Google-Apps was deactivated ^^ After reactivating and updating these Apps, it finally works
*CLOSEREQUEST*
Just picked up a Note II and was shocked to see how difficult it seems to be to root from stock 4.3. Many posts from users who say the stated methods aren't working for them ...
What is the current status on the best way to root from stock 4.3? The Tmobile bloatware is killing me ...
Forgot to say that I don't care about tripping the counter for knox or ota or any of that. Just want to root, get rid of bloatware, be able to use custom rom, etc.
Just use cf auto root
Haints said:
Just picked up a Note II and was shocked to see how difficult it seems to be to root from stock 4.3. Many posts from users who say the stated methods aren't working for them ...
What is the current status on the best way to root from stock 4.3? The Tmobile bloatware is killing me ...
Forgot to say that I don't care about tripping the counter for knox or ota or any of that. Just want to root, get rid of bloatware, be able to use custom rom, etc.
Click to expand...
Click to collapse
Its not difficult. I put this together today for installing note 3 features on T-Mobile Note 2. It's easiest way to do it. You need to learn basics first. So read about what recovery mode is, download mode and what Odin is and how to use it. It's all very easy and if you have TeamSpeak I wouldn't have a problem helping you with it, but you void your warranty and if you brick your phone - oh well, that's the chance you take. I've been doing it for about a month and its fun. Here's my guide. ezKAT rom is fun as hell! Enjoy!
Simplified procedure for installing ezKat custom rom on T-Mobile Note 2 (SGH-T889) ONLY
WHY THIS GUIDE?
#1 – For first time rooters, this is the easiest way to root your phone, period!
#2 - When I followed the original ezKat instructions, things didn’t go smoothly. After some trial and error and quite a bit of searching, this method worked easier, was repeatable, and also added some additional functionality – primarily stability and the ability to install games etc. to external SD Card.
I just put this together to save people time so they don’t have to go through what I did – namely fumbling around and being frustrated. Most of the solutions to problems turned out to be simple if I’d only known where to look the first time around. Unfortunately, it seems information on T-Mobile stuff is always harder to find compared to AT&T or International Note 2’s.
FILES: See the XDA forums ezKat Developer page for links to files and to acknowledge their awesome work. This is the best rom I’ve ever worked with and was well worth a little extra effort to unleash its full potential on my Note 2.
Problems others have reported that this method either avoids or solved for me:
1) No keyboard working
2) “no Sim card inserted” error after install
3) “code 7” error message during rom flashing that “ezKat 2.0 has error” and failed installation, as well as general instability reported by
others in the XDA forums.
4) Inability to install programs to External Micro SD Card
5) No sleep/coma problems
6) Stock browser is included and fully functional.
Last time I’m going to say this – these instructions pertain to the T-MOBILE NOTE 2 SGH-T889 ONLY!! I assume they probably work on the Canadian version too, but I don’t know. Regardless, whatever you choose to do with your phone is your responsibility. Your warranty is void the first time you root your phone regardless – we’re all adults here. Also, this assumes you know what flashing and Odin are… otherwise run away now!! Go read about download mode, recovery mode, and flashing, then come back if you’re not scared away by the prospect of possibly bricking your phone. Still here? Ok then…
Preparation step ONE OF THREE – freshly format your micro sd card (yep, get over it – this solves two major problems up front*)
Preparation step TWO OF THREE – copy these files linked from the ezKat PAGE to your external micro sd card:
-eZKAT_v2.0_n3feat (rom .zip)
-eZKAT_2.0_S5Keyboard (keyboard fix .zip) (do NOT try the “NEW2.0” keyboard file it does not work)
-T889UVUCMK7_Modem-Dec_9_13 (t-mobile modem fix .zip)
-UPDATE-SuperSU-v1.99
Preparation step THREE of THREE: Make sure these are installed to your PC:
-Odin v1.85
-Samsung USB drivers (duh!)
-**Mr. Robinson’s Pre-Rooted Stock 4.3 Rom “root66_TMO_T889UVUCMK7_2.tar” (for flashing with Odin)
-Philz Touchwiz Recovery “philz_touch_6.00.8-t0ltetmo” (Do Not Use TWRP for these steps – I love TWRP, but for some reason – ezKat doesn’t like it)
OK – here we go! Do these in order and you can’t go wrong. Do not skip any steps!!!
1) FLASH MR. ROBINSON’s PRE-ROOTED 4.3 ROM with Odin 1.85 – phone will auto-reboot.
2) Setup Wifi-Settings and shut off phone.
3) Power on phone in Download Mode
4) Flash Philz Touchwiz 6.00.8 with Odin - phone will auto-reboot.
5) Shut off phone and restart in recovery mode.
6) Flash eZKAT_v2.0_n3feat rom in recovery mode (do not reboot yet)
7) Flash Keyboard fix and Modem fix. Reboot phone.
8) Phone should be working – you’re going to be amazed and want to play around – STOP gawking and shut the
phone down!!
9) Boot back into recovery mode – Flash SuperSU 1.99
10) Clear Cache, Clear Dalvik Cache – Reboot phone
11) Download and install BusyBox from Google Playstore
12) Reboot Phone and ENJOY!!
Congratulations. If you don’t care about installing apps etc. to SD CARD, you’re done!! Enjoy your new Note 3 and S5 features on your Note 2.
Make sure to thank the ezKat team for their amazing work on this rom.
If you do want to install apps to External SD Card, then go to Google Play Store and install “NextApp SD Fix” and “FolderMount Premium” (the free version limits you to a very small number of moveable folders) NextApp SD Fix works automatically with two clicks after installation and there is a simple Youtube video showing how to use FolderMount. Again, it is a VERY simple utility to use. Simple click through – it does everything automatically.
NOTE: Contrary to some posts I’ve seen around stating that you can no longer move programs with FolderMount, I tested it again today while editing this guide and it works perfectly with this ROM. I will not attest to any other roms.
*If you didn’t format your Micro SD Card at the beginning of this process then you may have received the “error 7” code during the flashing of the rom. If so, start over.
**Some experienced rooters will choose not to flash over Mr. Robinson’s rom because they normally prefer to flash over a “clean” install base. If you go this route and experience stability or other issues, then I strongly recommend starting from the top with Mr. Robinson’s as a base. I’ve had a lot less issues since going this route.
Good luck everyone! I hope this helped you out.
Thanks to both of you for responding! I'll check out both of the methods you suggested.
Haints said:
Thanks to both of you for responding! I'll check out both of the methods you suggested.
Click to expand...
Click to collapse
You're well welcome. Good luck.
towelroot works on 4.3 for sgs3 so it should work for note 2 also. no pc required
mattlowry said:
towelroot works on 4.3 for sgs3 so it should work for note 2 also. no pc required
Click to expand...
Click to collapse
I tried won't work
terpin32 said:
I tried won't work
Click to expand...
Click to collapse
What error did you get?
It reboots the phone
Just rooted mine finally. Used the autoroot which didn't work and caused the supersu to just close out with knox errors. Then flashed twrp latest 2.7.2 and used it to fix permissions then flash superuser. Booted and it gave knox error, tried opening supersu and it asked if I wanted to try to disable knox. Choose yes, it said successful and Finally im rooted.
I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?
I currently have a T-Mobile HTC One M8.
I am running 4.4.4 with Sense 6.0
It is rooted, custom recovery (TWRP), S-OFF, with Xposed Framework installed.
I know this has been asked and discussed a million times in bits and pieces around XDA and the internet in general, but I am still having trouble finding one source with a definitive answer as to the steps I should follow.
I would like to update to Android Lollipop 5.0 (5.0.1)
- The OTA that has shown up on my phone as of now is Software Update: 4.20.531.4 (632.7 MB). I am not sure if there is already another one that would follow this one if I were able to successfully update to this version.
With that being said, I did not make a backup of my stock rom, nor recovery.
I am assuming that the process I need to take is this (to return my device to stock):
1) Uninstall XPOSED Modules and XPOSED Framework
2) Flash a STOCK ROM via custom recovery (TWRP)
3) Flash a STOCK RECOVERY via custom recovery (TWRP)
- Is this correct?
- If so, can someone provide me a link to the STOCK ROM and STOCK RECOVERY that I would need?
- If not, what are the steps I should follow?
Then what do I need to do to update my device to Lollipop?
Do I just refresh and check the software update in the ABOUT section of settings and update it as an OTA?
Can I skip all of these steps and just flash a factory LOLLIPOP IMAGE and RECOVERY via ADB with my device in it's current state?
Thank you in advance to anyone who will help me out
-----
UPDATE...
-----
*** I finally updated to Android Lollipop 5.0 (5.0.1)
This is what I did:
* I kept my device plugged into my computer this entire time
1) Download this STOCK ROM zip (TMOUS-M8-3.32.531.2-Stock-TWRP.zip)
2) Download this STOCK RECOVERY img (Tmo-M8-3.32.531.2-recovery.img)
3) Download this OTA zip (OTA-3.32.531.2 to 4.20.531.4)
4) Backup CURRENT ROM via TWRP (just in case)
5) Extract the files from STOCK ROM zip and place them in a folder named STOCK ROM
6) Move the STOCK ROM folder to your device under |sdcard / TWRP / BACKUPS / "random numbers & letters" / Place the folder here|, next to your CURRENT ROM backup
7) Move the OTA zip to your device under |sdcard / Download|
8) Move the STOCK RECOVERY img to whatever folder you have ADB (fastboot) setup in, on your computer
9) Reboot into TWRP, click restore, select STOCK ROM, then swipe to restore
10) After it finishes restoring, do not reboot. Just click back until you can select reboot, then select to reboot bootloader
11) Once it reboots to the bootloader and you are at the screen where it says FASTBOOT, open ADB (fastboot) command prompt and flash the STOCK RECOVERY img by typing: fastboot flash recovery "name of recovery".img
12) Once that has completed, reboot the device
13) Once the device has rebooted open ADB (fastboot) command prompt again and reboot into recovery by typing: adb reboot recovery
14) For me, it rebooted to a black screen, then turned into a black screen with a warning triangle, then I hit the volume buttons a few times as well as the power button and then it loaded up the recovery options (sounds weird, but this is how it happened for me)
15) Once the options appear, use the volume and power buttons to select apply from phone storage, then locate the OTA zip file that you moved into the Download folder, select it and hit the power button to apply it
16) Let it run and apply the update, then follow the instructions at the end to reboot the phone
17) Now you will have Android Lollipop 5.0 (5.0.1) on your device
*** When you apply the OTA zip, it will sit at "patching system files" for quite a while, so don't worry. Applying the OTA took around 15 minutes to complete for me
*** I never wiped data or cache or anything like that during this entire process. All my apps, settings, etc... remained how I had them before. I didn't have to set anything up after the final reboot. Everything was just like I had had it on my CURRENT ROM
*** I never uninstalled XPOSED Modules or XPOSED Framework, or unrooted the device. I simply did all the steps I just listed. Nothing else.
*** Of course after completion of this update process you will lose root, and would have to re-root and re-install XPOSED (which is possible now that XPOSED is compatible with Lollipop)
I would also like to know...
It's somewhat old, but the instructions using Method #1 more or less apply. Just make sure that when/if you reflash TWRP that you flash 2.8.5. Nothing older.
http://venomroms.com/viperonem8_3-0-0-requirements/
This is of course irrelevant to the OP, but for anyone who's still considering the move, my advice would be not to "update". I see absolutely no advantage of Lollipop in comparison to KitKat, at least as long as stock Sense 6 phones are concerned.
I have a completely stock, unrooted (although not SIM-locked) HTC One M8. A few weeks ago the OTA came and I "updated". Now, my phone worked perfectly before: fast, on battery for more than 2 days, etc. After the "update" there where problems after problems after problems. The keyboard lags, the battery life is way worse, etc. Yes, some of the problems can be overcome. But in my opinion if you just want a working phone, this "update" is simply not worth your time.
unifex_ said:
This is of course irrelevant to the OP, but for anyone who's still considering the move, my advice would be not to "update". I see absolutely no advantage of Lollipop in comparison to KitKat, at least as long as stock Sense 6 phones are concerned.
I have a completely stock, unrooted (although not SIM-locked) HTC One M8. A few weeks ago the OTA came and I "updated". Now, my phone worked perfectly before: fast, on battery for more than 2 days, etc. After the "update" there where problems after problems after problems. The keyboard lags, the battery life is way worse, etc. Yes, some of the problems can be overcome. But in my opinion if you just want a working phone, this "update" is simply not worth your time.
Click to expand...
Click to collapse
Have you factory reset your device after the update? I'm 100% stock, not rooted (although S-OFF) and it lasts well over a day but I always factory reset after every major update
EddyOS said:
Have you factory reset your device after the update? I'm 100% stock, not rooted (although S-OFF) and it lasts well over a day but I always factory reset after every major update
Click to expand...
Click to collapse
Yes, I did the factory reset. Strangely enough (although perhaps not so strangely) the reset kept the data of old apps. For example, I had some navigation app that downloaded lots of maps. The app is gone, but the maps are still there, even after the reset. They are just a dead weight now, with no way of accessing them - although I'm not sure whether I will be able to access them if I reinstall the app. Same with dictionaries.
The battery life got a bit better lately, perhaps after the Google Services update. But it's still not as good as it was on KitKat.
And finally, shouldn't the update bring improvements? So far we've been talking about issues and how to deal with them. I honestly have not seen any single improvement over KitKat. Perhaps something "under the hood", but then I would expect the phone to be more responsive, not lagging. So looking back, I just don't see what was the point of this update. Maybe with Sense 7 ...