Related
Hello all,
Got my Droid Incredible 2 back in July 2011. Rooted and flashed a custom ROM pretty much right away. Since, I have had almost no problems with this phone (except the alarm clock stopped working a few months ago...) and it has been through a lot.
Recently, my phone has been acting kind of weird. I am not quite sure what the problem is (sometimes the battery seems to drain extremely fast, pretty much only symptom atm and very random). I am going to keep using it regularly for a few more days to see if the problem is persistent.
Anyways, if the phone is actually OK still, I was thinking it might be nice to get a fresh new ROM. Like I said, got the phone 07/11, haven't touched it since.
I am liking this ROM: http://forum.xda-developers.com/showthread.php?t=1892450
What is the recommended process of backing up my data and flashing this one on? I see the instructions in the thread and intend to follow them, if anyone has more detailed explanations or would like to walk me through it that would be appreciated.
Do I need to update anything else? Like I said, phone is on pretty old software/firmware since I have not received any official updates over the life time of my phone. I am seeing kernels and radios, will mine work? Can I tell? Are there better ones I should use?
I am currently rooted. Running rmk's Ginger Sense ROM (found here: http://forum.xda-developers.com/showthread.php?t=1161411) which is Android version 2.3.3 and Sense version 2.1. I have Titanium Backup and Superuser apps installed.
So, its been a while. Help me update right. I will continue to research but my knowledge relating to this process is currently severely lacking, so any help is appreciated. My phone has been fast, smooth, and stable - I would love to keep it that way!
Thanks
Just follow the instructions in the op. Do them as it says. Be sure to reboot recovery after installing rom and before flashing gapps. It wont break your phone if you forget, but it might help the soft keys work right. No need to update firmware. The kernel he includes is custom too so you dont have to flash a different one, research if you want to though, there are others that work. Try it without changing radios, if you want to change radios its simple and there is a thread that has them on xda.
Sent from my Incredible 2
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
internetpilot said:
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
Click to expand...
Click to collapse
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.
That's what I recall from when I still had stock about 9 months ago...
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.
Sent from my buttered S3
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
internetpilot said:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
Click to expand...
Click to collapse
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there.
Click to expand...
Click to collapse
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
internetpilot said:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
Click to expand...
Click to collapse
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
Click to expand...
Click to collapse
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
internetpilot said:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
Click to expand...
Click to collapse
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
flastnoles11 said:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
Click to expand...
Click to collapse
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
internetpilot said:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
Click to expand...
Click to collapse
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
flastnoles11 said:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
Click to expand...
Click to collapse
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).
In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.
Sent from the future via Tapatalk 4
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
internetpilot said:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
Click to expand...
Click to collapse
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
edfunkycold said:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
deutscher3891 said:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
Click to expand...
Click to collapse
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
internetpilot said:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
Click to expand...
Click to collapse
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
deutscher3891 said:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Both directly from Sprint.
lvpre said:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
Click to expand...
Click to collapse
The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.
I searched and couldn't find an answer to my specific situation but apoligize in advance if this is addressed. I really am new to this so don't want to screw something up.
Basically, if I am rooted with the current stock 4.3, can I take an OTA update? I don't mind losing root.
Background info:
I rooted a while ago, can't specifically but I recall it being a "one-click" method. I checked with root checker from the play store and it says I have root access. If I open SuperSU it tells me KNOX is detected and I know I never removed them so I think it's right. I am running L900VPUBMK4.
I hope 4.4 is released soon, so I'm really just preparing for that day. I need to do a factory reset in the next day or two anyways because my phone is acting up and I have a ton of junk on it anyways so I want a fresh start. I originally rooted to get wifi tethering working but that never worked out for me and I really don't need root at all.
Thanks in advance.
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Elw00d said:
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Can this be moved to QA then?
So did I install a custom recovery to root? Is there a way to check? I've tried several varieties of volume +/- and power to try to boot into recovery but nothing happens.
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
m5james said:
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
Click to expand...
Click to collapse
I looked on my laptop and remember what I used. I used Kingo Android Root to do it. It didn't appear to work because I never got a "success" popup. But when I did a root check it says I have it.
How do I check if I have a custom recovery?
I'm with you M5James - very confusing. Even the "one-click" idiot proof method I used confused me. Different boxes to check that I have no idea as to what they mean.
I've rooted, installed ROM's and kernals, OC'd, custom baked my own ROM's using 7Zip, I tweaked my GF's phone so that she could use it here in the States and then while we were in Dubai as well, etc. Nowadays, when it comes to things like pushing through ADB (I have no clue what that even means, I've just heard it enough that it sticks lol), all the [xxx] before the title of the ROM, kernal, etc and I just become a dear in headlights. Lastnight I tried Googling random things on how to remove root easily and one mentioned using Superuser and just clicking the Unroot Complete icon, which I did. Running random apps says I've removed root, Market doesn't work anymore (I'd upgraded to the Lucky Patcher Market is where I'm guessing the problem is), yet even though I don't have root, I still can't get the OTA to push 4.3 to my phone. I don't even really care about having 4.3 because I'm fine w/ using 4.1.2 at the moment, I'm just sick of the random pushes to my phone asking me to update.
In regards to my Note II with just installing things like custom ROM's, I haven't wanted to do anything wild to it for fear of being like the days of when I had a custom Samsung Epic...worked great OC'd, but could never get battery stats to work right, then the phone would freak out and become laggy, I'd reboot and then suddenly the battery was dead. I just want a simple root, add root-only apps as needed like WiFi Tether, then continue on being a texting whore lol.
If you have rooted your epic and installed custom recovery all this should be pretty simple. All the info is here. Its to the point where rooting and unroofing can be down in probably under 10 mins. You have to read.
Sent from my SPH-L900 using XDA Free mobile app
I read it all, but it's gotten to the point where it's overly technical sometimes. I get lost in jargon, acronyms, I liked it better when there were 5 REALLY good guys making ROM's that worked, not 30 people making their own variations in their basement, then it turns into a pissing match of who's got the latest, fastest, most battery efficient, you've gotta do this to do that, but don't do this if you want that (assuming I know WTF "that" is in the first place) otherwise you'll brick your phone (but you can maybe unbrick it this way), if you swallow this pill you'll get rid of one symptom but you'll get 15 other problems in it's place, etc...then I just say F'it and leave my phone the way it is lol
My wife has the note2, I have the s3 (both rooted, I'm running a custom rom). I think I'm gonna take her back to stock so so she can get the update, then I'll just flash a custom recovery and su zip. It'll give me a chance to clean up her phone.
Edit: thinking of using this
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
I flashed the LRX21P factory image onto my Nexus 7 2013 yesterday and to be honest I'm really quite disappointed with the performance. Most of the material design animations seem to be running slowly or dropping frames, scrolling is jittery and even the performance of many of my games (the ones that still work, anyway) is much worse than before.
I've seen comments elsewhere with other people having the same experiences, just wanted to get a feel for how common this is and if there is anything that can be done to fix it.
Did you wipe data? Old data cannot remain or it will ruin performance.
madbat99 said:
Did you wipe data? Old data cannot remain or it will ruin performance.
Click to expand...
Click to collapse
I used the script included with the factory image. Unfortunately my Nexus 7 won't even boot right now, so I'm going to restore it from my Kitkat backup and not muck about with it again.
You really need to do a fresh install when upgrading to a major new version of an OS. Trying to keep your old data and settings is a recipe for disaster.
On my Nexus 7 2013 at first time it was running laggy, but now, after few reboots it's running OK, but I think it can be faster.
a lot of people have same problem
Reboot and install clean master. Maybe fix it
It is slightly laggy but not a deal breaker
I used the Stock Factory Image to upgrade, and it gave me absolutely no issues at all..
I did a COMPLETE WIPE, then installed the image via Wugfresh's NRT Program/Tookit and played with it for about a week.. It broke a few of my apps.. So I decided to go back to Carbon's Nightlies 4.4.4.. I won't go back to Lollipop until a decent Custom rom is released with Xposed modules... I did not notice a performance boost or anything different other than a complete interface change.. I had to download a beta copy of Titanium Backup to restore the Data of my apps so I could at least restore a few things.... Lollipop isn't ready for prime time, stick to your latest version of Kitkat..
Zaphodspeaks said:
I used the Stock Factory Image to upgrade, and it gave me absolutely no issues at all..
I did a COMPLETE WIPE, then installed the image via Wugfresh's NRT Program/Tookit and played with it for about a week.. It broke a few of my apps.. So I decided to go back to Carbon's Nightlies 4.4.4.. I won't go back to Lollipop until a decent Custom rom is released with Xposed modules... I did not notice a performance boost or anything different other than a complete interface change.. I had to download a beta copy of Titanium Backup to restore the Data of my apps so I could at least restore a few things.... Lollipop isn't ready for prime time, stick to your latest version of Kitkat..
Click to expand...
Click to collapse
Xposed doesn't work on art. And there is waaay more than a ui change. There are security enhancements that I have been waiting for. Even though one of my favorite apps isn't updated to work yet (dish anywhere) I can't go back, lol. Onward to the 21st century!!
madbat99 said:
Xposed doesn't work on art. And there is waaay more than a ui change. There are security enhancements that I have been waiting for. Even though one of my favorite apps isn't updated to work yet (dish anywhere) I can't go back, lol. Onward to the 21st century!!
Click to expand...
Click to collapse
I know Xposed doesn't work on ART, hence why I downgraded to my trusty Carbon 4.4.4 where its tried and true..
The developer of Xposed doesn't even know if he will port Xposed over to Lollipop, although I have confidence that he will eventually.. I never liked the Stock version of any version of Android.. But because its open source, or at least up until now, there will always be someone out there with a CM port, or Carbon.. ETC..
Lollipop broke a lot of my apps.. Thats because some developers haven't caught up.. I like Lollipop, but I hate the middle pull down menu.. other than that, it's fantastic.. Battery life really good, smooth and gave me not a single issue while I used it for just over a week... But I missed some of my games.. and favorite apps.. Then I temporarily downgraded to 4.4.4.. Until the 3rd party developers can polish this amazing rom..
Mine lagged after flashing as well. I just reflashed and now its a smooth as ever. Stock kernel
I'm quite happy back on Kitkat. Since Google appear to have pulled the OTA update I can't see a reason to rush to upgrade right now and I probably shouldn't have been so impatient.
Interesting to see the poll is almost neck and neck too.
I was worried after seeing some of these comments, but I flashed Lollipop last night and my tablet is running great!!
timrock said:
Mine lagged after flashing as well. I just reflashed and now its a smooth as ever. Stock kernel
Click to expand...
Click to collapse
Absolutely great advice for any issues after a rom flash. If you are fastboot flashing rather than taking an OTA, it's so easy to just reflash the system. If needed, reflash all components.
I got a Nexus 7 2013 (32GB wifi) off of reddit.com/r/hardwareswap for $80, and absolutely love it.
Naturally I applied the 5.0 OTA update, rooted it, and installed ClockworkMod Touch first chance I got.
Frustrated by not being able to apply the 5.0.2, I realized that Cyanogenmod 12 was based on 5.0.2 (or at least the latest nightly was) so I figured that was the best way to get the newest version, and would make updating easy after that (cyanogenmod's update tool works great, much easier than flashing updates individually, or hoping a stock ota update will play nice with your custom recovery)
After that my nexus 7 was almost perfect, but I had to get the stock boot animation back because it's way cooler than CM12's.
Finally, I REALLY wanted the ability to double tap the screen to wake it. This is something that I've gotten so used to on my Xperia Z3, and there was a nice way to do it that required Xposed framework, which doesn't work on ART, so that is out. It seems that getting a custom kernel that will play nice with the TouchControl root app is the only way I've been able to find that will let you do the double tap to wake thing.
Anyway I flashed the lastest Franco Kernel and it totally jacked up my Nexus. I had anticipated that and made a backup, and restored to that backup, but that didn't fix the problem and now it just bootloops the splash screen, although I can get into recovery and the bootloader.
So now, I figure I can either try flashing the original CM12 kernel over the broken franco kernel, or I can just re-flash the ROM and start from scratch. I'd really rather not do that, but I may have to. I can't get into the filesystem or get adb to find the device because of drivers, so I'm not sure which will be more of a headache: figuring out getting drivers to work in recovery/bootloader, or setting up android from scratch.
I just realized that it might be easiest to do a factory reset THEN restore from the backup, so I'll give that a try.
All of this got me thinking, is CM12 better than stock Lolipop 5.0.2? I just flashed it for easy updates and to get to the latest version, but what is everyone elses experiences between the two?
Also I'd love to hear of other ways to get the double tap to wake on Lolipop that might not involved flashing custom Kernels. Though I think I might give the ElementalX Kernel a shot, and it looks like that one won't break everything.
Franco's L kernel works with CM12, but if you have problems, just reflash the CM zip. Nothing else required.
I wouldn't use CM12 atm unless you like to test drive stuff, it's too early in development you can encounter quite a few bugs.
ElementalX kernel has the double tap to wake and a few other features. The only issue which is minor IMO is that is you update to the newest nightly you'll go back to CM kernel, and have to flash the ElementalX again. There may be a way around this, but I've only been on that kernel for a couple days now and haven't really looked in to a solution.
---------- Post added at 09:50 AM ---------- Previous post was at 09:41 AM ----------
k3lcior said:
I wouldn't use CM12 atm unless you like to test drive stuff, it's too early in development you can encounter quite a few bugs.
Click to expand...
Click to collapse
I can't say that I have encountered any real bugs, it seems very stable. Early on there seemed to be a battery drain and data connection seemed exceptionally slow at times, these may have been just due to my setup. I haven't had any of those problems for the last two weeks or so. Have you used it? If not why would you discourage someone when you have no personal experience?