Related
My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?
mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ
DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....
mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.
gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!
Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.
CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ
I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!
Lucky Armpit said:
I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!
Click to expand...
Click to collapse
what are you doing wrong? well thats an easy one, youre a first time flasher, what are you doing using a root toolkit? did you learn anything from it? did you learn how to flash the factory image the right way? no. that's your issue. it takes less than 5 minutes to flash a factory img the right way.
if you know how to do things properly, then its alright to use a toolkit. if you have no idea jow to do things right, a toolkit wont show you how.
Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Didgeridoohan said:
Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
right, thats what i was trying to say
Thanks for the replies, guys. I was able to figure it out. I didn't have the bootloader unlocked. I know, noob mistake. I've got LMY47Z and no encryption now. Sure hope this fixes the jank I've been experiencing, which was the whole purpose of this little experiment.
But to answer your question, I used a tool because it automates the commands and makes the experience easier. Yes, I ran into trouble at first but I figured it out. In my defense, I did read that thread before posting that recommended issuing commands rather than using a tool. I was already vested in NRT so I figured I'd see it through.
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline
Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
To fix your storage issue, either factory reset or fastboot format userdata.
Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
or just format the cache.
simms22 said:
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline
Click to expand...
Click to collapse
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?
Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
simms22 said:
or just format the cache.
Click to expand...
Click to collapse
Sorry, didn't see this until after I replied. I formatted the userdata and that fixed the storage issues. I'm back to 64GB. Thanks!
Lucky Armpit said:
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?
Click to expand...
Click to collapse
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck
simms22 said:
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck
Click to expand...
Click to collapse
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha
JNMM said:
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha
Click to expand...
Click to collapse
i still have the old elementalx app, and im still using it as my cpu control app :angel:
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
So now you are not rooted anymore???
Did you get any takers yet?
Looking like all hope is lost for 5.1.1 root. Thanks for trying @trailblazer101
trailblazer101 said:
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
Click to expand...
Click to collapse
Actually, I have been thinking about this myself and I agree with your observations...
In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either
A. Solidified my thought process
B. Guessed and theorized for 7 days with a loaner phone lol, like I did...
Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
scrosler said:
Actually, I have been thinking about this myself and I agree with your observations...
In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either
A. Solidified my thought process
B. Guessed and theorized for 7 days with a loaner phone lol, like I did...
Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
Click to expand...
Click to collapse
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..
i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..
you guys are more experienced with android than i am for sure!
Extreme Syndicate L
elliwigy said:
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..
i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..
you guys are more experienced with android than i am for sure!
Extreme Syndicate L
Click to expand...
Click to collapse
I'm considering getting rid of s6 edge in the next couple of days. If my plan comes through I will test your theory prior to selling my phone
Sent from my SM-G925V using Xparent Green Tapatalk 2
trailblazer101 said:
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
Click to expand...
Click to collapse
I'd be happy to test this out; I don't mind losing root if it comes to that.
Let me know what needs done and I'll try to help out also...
Sent from my SM-G925V using Tapatalk
pm sent trailblazer, lmk
PM'd. Willing to take the plunge!
I'm on OG5, so I wouldn't be much help..
Have you guys heard any news? Unfortunately, I am pretty close to being done with using the old software version and the bugs it comes with, just to retain root.
It's really nice to have, but with (hopefully) Samsung Pay around the corner, I'm likely going to be throwing in the towel since it will require a software update.
haven't heard anything from OP
I'm pretty sure no one is working on rooting this device for OF1 and above anymore.
Sent from my SM-G925V using Tapatalk
its not a matter if anyone is working on root for of1 since roots are typically exploits in the android os so new root methods are typically based on OS... for example, if root is done for android 5.1 it might work on OG5 5.1 for us..
known exploits for 5.0 were patched in OFx firmwares so new exploits need to be found in general.
Sent from my SM-G925V using XDA Free mobile app
Would love to know if this worked. I really want to update to 5.1.1 and see how it is for myself but don't want to lose the ability to downgrade again. I may end up just doing it anyways though so I might as well test this in the process. I've been seeing that no one's gotten a response though
Sent from my SM-G920V using XDA Free mobile app
The title pretty much says it all... I want to go back to TouchWiz but still want root, my app data and xposed. How do I go about doing this? Your help is much appreciated!
Those are two completely different operating systems and moving data between them will prove impossible.
you will definitely not get to keep Xposed. your app data might be salvageable with some kind of app like Titanium Backup, but i wouldnt count on it. you can root again once you have installed TouchWiz. very easy.
so, this is part of the process with rooting and flashing new ROMs. i have clean-flashed and completely set up my system at least 400 times over the years. you should really consider a clean flash of whatever TouchWiz ROM you want and set it up from scratch. i really dont know how else you can do it.
WaxysDargle said:
Those are two completely different operating systems and moving data between them will prove impossible.
you will definitely not get to keep Xposed. your app data might be salvageable with some kind of app like Titanium Backup, but i wouldnt count on it. you can root again once you have installed TouchWiz. very easy.
so, this is part of the process with rooting and flashing new ROMs. i have clean-flashed and completely set up my system at least 400 times over the years. you should really consider a clean flash of whatever TouchWiz ROM you want and set it up from scratch. i really dont know how else you can do it.
Click to expand...
Click to collapse
Thank you very much for your reply. I figured most of what you said would apply but allow me to clarify a few things...
If I do a clean install of Touch Wiz and root, will I lose my in-app purchases, game progress, etc?
Is there no way to get xposed on TouchWiz? I thought it was device specific, not ROM specific.
Could you also please direct me to the correct resources for going ahead with the process? I don't want to mess anything up. Thank you!
musichasm said:
Thank you very much for your reply. I figured most of what you said would apply but allow me to clarify a few things...
If I do a clean install of Touch Wiz and root, will I lose my in-app purchases, game progress, etc?
Is there no way to get xposed on TouchWiz? I thought it was device specific, not ROM specific.
Could you also please direct me to the correct resources for going ahead with the process? I don't want to mess anything up. Thank you!
Click to expand...
Click to collapse
any purchases you have made through the play store will still be valid. in-game purchases will probably depend on the game itself, but i am willing to bet progress and payments are both saved online. i would check with google or other users to verify before taking any action.
i am not sure about game progress, but i would think some of them save progress online so you can play on multiple devices. probably depends on the game, itself.
you can get xposed for touchwiz, but the ROM has to be deodexed. i have had some trouble installing xposed myself on touchwiz, so i usually find a close-to-stock ROM that already has it installed. there was a special version of xposed for touchwiz last time i was looking a couple months ago and i could not get it to work, but i did find a debloated, deodexed stock rom that had it already installed.
before i throw resources at you, are you planning on restoring to stock and then building the ROM the way you want it? or are you going to start with a custom touchwiz ROM and work from there?
I'm not an expert modder by any means (though eager to learn).
Basically, I have had a lot of issues with Cyanogenmod and want to go back to what's intended but I prefer being a power user and having root access and have certain xposed modules I'm really used to. I don't want ANY bloat either. If there is a custom yet STABLE rom for my phone then great! Otherwise I don't mind getting stock, deleting bloat, and installing xposed.
I have no idea what deodexing is...
Thanks again!
musichasm said:
I'm not an expert modder by any means (though eager to learn).
Basically, I have had a lot of issues with Cyanogenmod and want to go back to what's intended but I prefer being a power user and having root access and have certain xposed modules I'm really used to. I don't want ANY bloat either. If there is a custom yet STABLE rom for my phone then great! Otherwise I don't mind getting stock, deleting bloat, and installing xposed.
I have no idea what deodexing is...
Thanks again!
Click to expand...
Click to collapse
Another question...
Which cyanogenmod did you install? I know of one stable CM 13 (marshmallow) and one stable CM 12.1 (lollipop). If you're willing to give it another try I'll bet it'll be worth your while. Touchwiz, in and of itself, is bloat and I will probably never encourage it for anyone who actually uses their device.
Either way, I'd be happy to help with suggestions. What do you mostly use your phone for, and what about your experience with it do you care bout most?
Is there 13 for my phone? I've only seen 12.1
I'd love to move on to marshmallow
musichasm said:
Is there 13 for my phone? I've only seen 12.1
I'd love to move on to marshmallow
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-tmobile/development/rom-t3336468
Try this one.
Download ROM & gapps and put on root of internal storage
From recovery make a backup, then wipe system, data, cache, dalvik cache
Flash ROM and gapps in recovery
Wipe cache & dalvik cache before booting
Reboot and enjoy
Give the ROM a day or two to "settle in" before passing judgement on it. Might be laggy for a day
WaxysDargle said:
http://forum.xda-developers.com/note-4-tmobile/development/rom-t3336468
Try this one.
Download ROM & gapps and put on root of internal storage
From recovery make a backup, then wipe system, data, cache, dalvik cache
Flash ROM and gapps in recovery
Wipe cache & dalvik cache before booting
Reboot and enjoy
Give the ROM a day or two to "settle in" before passing judgement on it. Might be laggy for a day
Click to expand...
Click to collapse
I'll try it out later this weekend and let you know how it went. Thank you!!
musichasm said:
I'll try it out later this weekend and let you know how it went. Thank you!!
Click to expand...
Click to collapse
Also if you want S-pen features download "CM Spenadd-on" and "note buddy" and then a good notepad app (I use handraw).
OK, so I've installed it, restored my app data with Titanium and so far I'm impressed. It feels good to go to a stable ROM instead of nightlies...
BIG issue though...
Cell standby shows like 25-30% battery usage. My battery drains a lot and I'm using amplify and greenify... :/
musichasm said:
OK, so I've installed it, restored my app data with Titanium and so far I'm impressed. It feels good to go to a stable ROM instead of nightlies...
BIG issue though...
Cell standby shows like 25-30% battery usage. My battery drains a lot and I'm using amplify and greenify... :/
Click to expand...
Click to collapse
That happens to some people. I wouldn't even bother with it.
Try this one:
http://forum.xda-developers.com/note-4-tmobile/development/rom-slimremix-rom-v1-x-t3156059
This is my failsafe ROM. Fastest ROM I've ever used. Battery life is good enough for me. Love it. Only bug I've found is that you have to toggle Bluetooth every once and a while when pairing. Always works.
I am currently rooted running stock A11. I noticed that the update to A12 is now available. Just for fun, I checked updates on my phone & it says there is an update for A12 available. I thought being rooted, with the boot-loader unlocked, I wouldn't get updates. But there it is, asking me to download it.
Would it work if I downloaded and installed it via OTA on my phone? Would it wipe all my data (internal storage) and un-root me? Would it brick me? Just asking because I thought the proper way to update while rooted was this way (step #4), but doing it via OTA doesn't get much easier.
I am currently happy with how my phone is set up and running. I don't have an urgent need to update and really dislike setting up a phone as new. Of course, if an update to new a new OS is available...I'm going to want to install it eventually.
Thanks for the advice!
I'm not going past Q on my stock N10+'s, one still running very well on Pie. It's load is over 1.5 years old.
The first thing I do on my stock phones is disable OTA Updates. I may eventually update the Pie one to Q but it's more restrictive than Pie. I gain some nice features and it runs a bit faster, but loose some functionality as well.
Security simply isn't an issue with Pie in everyday use. Q may prove more troublesome.
Going to R would break them. It's a mess. CPU cycle burning scoped storage and tard repetitive security permissions. All my apps are vetted and trusted, many wouldn't load on R. Some aren't replaceable like my free office app which I use a lot. Plus forced encryption on first boot up... trashware.
Trust 12 to be better? When pigs fly.
Rule #1, if your OS is running fast, stable and fulfilling its mission let it be.
At the best you'll waste a lot of time that wasn't worth the trouble and at the worst end worse off than before. I'm not buying the hype.
mn1968 said:
I am currently rooted running stock A11. I noticed that the update to A12 is now available. Just for fun, I checked updates on my phone & it says there is an update for A12 available. I thought being rooted, with the boot-loader unlocked, I wouldn't get updates. But there it is, asking me to download it.
Would it work if I downloaded and installed it via OTA on my phone?
Click to expand...
Click to collapse
Yes, you can update via OTA.
mn1968 said:
Would it wipe all my data (internal storage) and un-root me?
Click to expand...
Click to collapse
The OTA preserves /data, but because it updates the boot image, you will lose root.
mn1968 said:
Would it brick me? Just asking because I thought the proper way to update while rooted was this way (step #4), but doing it via OTA doesn't get much easier.
Click to expand...
Click to collapse
Why would an OTA update brick your device? The answer is no. However, due to Android Verified Boot features, you will need to disable both dm-verity and vbmeta verification in order to flash and boot a patched boot image. Unfortunately, this has required a data wipe to work. Those of us on the Pixel 5 are experiencing the same issue and are still working on the "why". If you leave /vbmeta and /boot stock, you can still temporarily boot a patched image....which just means that you'll lose root when you reboot.
mn1968 said:
I am currently happy with how my phone is set up and running. I don't have an urgent need to update and really dislike setting up a phone as new. Of course, if an update to new a new OS is available...I'm going to want to install it eventually.
Thanks for the advice!
Click to expand...
Click to collapse
Understandable. As I mentioned above, if you want to upgrade to Android 12 and have permanent root, it's likely that you will have to wipe. However, you can try following this guide and see if it works for you. Be warned, the user that posted that was on the 12 Beta, and had wiped previously when upgrading from Android 11. It won't cause a brick, but you may still have to wipe your device. If you're prepared to bite that bullet, you can give it a try.
Ultimately, you have 3 options:
Stay on Android 11 with root
Upgrade to Android 12, keep data, but lose root
Upgrade to Android 12, most likely wipe data, and reroot.
blackhawk said:
Rule #1, if your OS is running fast, stable and fulfilling its mission let it be.
At the best you'll waste a lot of time that wasn't worth the trouble and at the worst end worse off than before. I'm not buying the hype.
Click to expand...
Click to collapse
There is a certain degree of logic to this. I used Windows 7 and refused to update to 8.1 or 10 for a long time. Now that I'm on 10 Enterprise LTSC, I'm refusing to upgrade to 11. If it ain't broke, don't fix it.