So I am still on the first root basically...in other words I Unlocked and rooted my PXL right away once it was available and haven't really touched it since as far as installing twrp or side loading updates since everything is still in the early stages of development. So anyway I want to update to the newest build with the lift to wake and double tap. I'm having a brain fart and can't really figure out where to start. I'm verizon on build NDE63P and I'm reading that I can't update to that build unless I'm coming from V. Basically what I'm looking for is for somebody to walk me through step by step where I should go to get to where I want to be. If twrp is still buggy I think I'd rather hold off til it's at least in beta. I just want to be on the newest build and retain root and bootloader unlocked. Anyone want to be kind enough to help I would much appreciate it. And download links would be a bonus. Thanks in advance
Related
I was wondering if someone would know of a simple way to receive an update to my gs3 after rooting, I recently purchased it. It is the U.S cellular variant and I must say I was pretty impressed (shocked) that on my first attempt ever at rooting a device I was able to root my gs3 without a single problem using the CMteamepic root file>>cwmrecovery tar file>> odin file>>> based on the sprint illustration on youtube. Followed it to a T and voila'... It was done, I actually did it without a single issue to the root process or to phone If someone could help with the update issue, I tried updating and the phone actually went through the process all the way to where it asks where you want to boot from and then press the power button. I'm not sure if I was suppose to scroll to something else prior to pressing the power button but when I did so from the first selection and phone booted up it said update failed. If anyone could please help I would greatly appreciate it.
tuckytuck0204 said:
I was wondering if someone would know of a simple way to receive an update to my gs3 after rooting, I recently purchased it. It is the U.S cellular variant and I must say I was pretty impressed (shocked) that on my first attempt ever at rooting a device I was able to root my gs3 without a single problem using the CMteamepic root file>>cwmrecovery tar file>> odin file>>> based on the sprint illustration on youtube. Followed it to a T and voila'... It was done, I actually did it without a single issue to the root process or to phone If someone could help with the update issue, I tried updating and the phone actually went through the process all the way to where it asks where you want to boot from and then press the power button. I'm not sure if I was suppose to scroll to something else prior to pressing the power button but when I did so from the first selection and phone booted up it said update failed. If anyone could please help I would greatly appreciate it.
Click to expand...
Click to collapse
You can't apply ota updates while rooted. You need to unroot if you really want the update. Honestly, most devs just incorporate the updates in to their roms once the updates are are released anyways.
The above is true however...
In my opinion I say **** the whole OTA. The baseband is what counts. The rest of the updates are sprint garbage. As above post states,Most roms are updated to reflects the ota's however if your on an older build I recommend grabbing the newest baseband here http://www.mediafire.com/?u4793wlu5r97t3g. Then stop the update nag by flashing this http://dl.xda-developers.com/attach...2042/503dad17/1/2/4/4/2/7/7/blazerOTAkill.zip. Just my 2 cents.
Voodoo OTA rootkeeper...no?
evoer said:
Voodoo OTA rootkeeper...no?
Click to expand...
Click to collapse
I've used that and it worked
Sent from my SPH-L710 using xda app-developers app
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
Pretty sure stock recovery and no root is required to take the OTA. Best bet is to just flash the newest factory image and start over with root etc.
ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
You have unlocked bootloader, flashed custom software and now you are worried about some security patch.
Not worried. At all. As I said I'm happy with my setup. Problem is how can I make the notification go away? It keeps coming back.
I'm a big fan of flashing roms onto phones, but i'm also a fan of stability and want to continue using official OTA for now. Once the OTAs stop coming, I will be willing to explore keeping my phone up to date via flashing ROMS.
Given the nature of the "fix" to unlock the bootloader (converting it to dev edition), it seems to me this is something that will always work, even in the future. Do you guys agree with that?
If it's not the case, I'd rather take necessary precautions now to get my phone converted over and possibly flash stock/de-bloated ROM going forward.
You guys think it's safe to just take OTAs for now?
I don't think the CID exploit used to unlock the bootloader will/can be patched out, but that exploit needs temp root to work. Who knows if/when temp root will be available for a stock Note 4 on MM?
I would do the dev conversion now. You can always flash a safe upgrade package once the stock MM update becomes available.
I agree. Just wait for a stock "safe" upgrade package to be released. I would at least postpone immediate install of the released official UG to see what it does to the phone.
For me, I have finally got control back on my phone. I went from the note 2 to note 4. I'd still be on the 2 if it hadn't got run over by a car, But the 4 is a good hardware upgrade but I felt it was an overall downgrade with the locked boot loader. Now that I have it, I would stay on 5.1.1 forever if it meant keeping the boot loader unlocked.
Has anyone even heard any info about an update?? I figured it would be outside the window for them to consider it.
rpn377 said:
I'm a big fan of flashing roms onto phones, but i'm also a fan of stability and want to continue using official OTA for now. Once the OTAs stop coming, I will be willing to explore keeping my phone up to date via flashing ROMS.
Given the nature of the "fix" to unlock the bootloader (converting it to dev edition), it seems to me this is something that will always work, even in the future. Do you guys agree with that?
If it's not the case, I'd rather take necessary precautions now to get my phone converted over and possibly flash stock/de-bloated ROM going forward.
You guys think it's safe to just take OTAs for now?
Click to expand...
Click to collapse
Don't touch any OTA or boot.img until I look at it and make a post in my OP.
I'm... asking for a friend....
But seriously, I tried following the instructions on the "[Guide] Step by Step from Stock N910V 6.0.1 to hsbadr's CyanogenMod 13.0 " thread, intending to bypass them when I got to the point of being able to jump over to the newer roms, and all I got was a boot loop when I tried flashing in 5.1.1. Is it because I'm on a retail 910v or was it a user error kinda thing? I tried multiple times and couldn't get it to boot after the flash, ended up flashing 6.0.1 back just to get my phone back.
I'm also ready to free the bootloader and root this thing. It seems emotion OS is the most popular and up to date now, correct?
I have the CPL1 update from Verizon( Dec patch). I know there are a bunch of threads with how tos, but it's unclear how outdated they are and whether it works with these latest versions. If someone can confirm the best way to go from cp1 to emotion.. Let me know.
Also.. I saw a while ago a guide on how to go to developer edition. Why isn't that front and center anymore? Isn't Dev edition completely unlocked... Why wouldn't I want to convert to dev edition before dealing with any rom changes? If someone can give some clarification I'd appreciate it.
Great news, I went for the plunge and succeeded. Confirmed -> stock and latest version software as of Jan 20 2017 (CPL1) can be downgraded to 5.1.1, rooted, TWRPed, and blah blah. I used the same guide you mentioned at top (hsbadr's CM13 guide), except i stopped at step 52 and continued to install emotion OS instead. Highly recommend it.
I'm on EmotionOS now. Wow, it was really worth it. So smooth compared to touchwiz 6.0.1. Haven't found a bug yet, but even if i do, i won't care.
I'm not sure what you mean "when i got to the point of installing newer roms". If you got to that point, why were you trying to flash 5.1.1 again?
How did you root it? I flashed mine back to 5.1.1, but I'm not having any luck rooting.
Michael7332 said:
How did you root it? I flashed mine back to 5.1.1, but I'm not having any luck rooting.
Click to expand...
Click to collapse
Follow the guide. You are going to go through a complicated process using the king root apk. I think the guide makes you use king root 3 times total to accomplish various parts of the process. King root loads up and spins for a few minutes, eventually succeeds, then you gotta punch in some things to command line using adb. I believe this is rooting your phone a few times.
Eventually you end up with twrp bootloader and jasmine Rom and everything just sticks.
So far.. The only annoying thing with emotion is that I lost volte and video calling. Maybe they'll bring it in one day.
Hello!
So currently I'm looking for some advice on where to go from here. I bought my SM-n910v DE directly from Samsung because I wanted the unlocked boot loader right from the get-go. Once I got it, I decided to root it. I don't exactly remember the exact method to root, I believe it may have been with an app.
Since then, I have not taken any OTAs and so I am still on 4.4! I don't know what disabled the OTA, or if I needed to activate it somehow since I didn't buy the phone from Verizon, and perhaps there was a step I missed when I activated it with them. Either way, I have enjoyed my Note 4 a ton. I like being on 4.4 since I know it'll function as expected and I had read some people talking about later releases being not so great on the Note 4 particularly so I decided to not worry about the OTAs and stay on KitKat.
So I was trying to do some research on perhaps customize it a bit more, and so when I tried a few steps, and I booted into recovery (vol up + home + pow), the blue text above booting into recovery did appear, but then when the green droid first appears, the phone seems to reset itself back into the green droid again, again. It is as if recovery mode (starting with the pic of the green droid with its belly open) restarts again, and again and again. Never getting passed the green droid.
I'm wondering if anyone has any suggestions as to what to do about the OTAs. What is the safest path to a good stable release? do I need to un-root prior to taking an update? Do I have to do updates in succession? Can I even take an OTA with root? will that break things?
also about the loop I'm experiencing. What could it be? If I revert back by attempting to flash a stock firmware, or something, will I need to re-root? Would I need to try? Since I can't even get into recovery, can I even revert?
Any direction would be greatly appreciated. Thanks so much for this forum and the awesome people that help in here!
J
I would think that yes, you will have to unroot and then I would take it to a Verizon store and ask them to flash it. I know Sprint will. I had a bad ota. They fixed it free as well. I can tell you that 6.0.1 is solid. This one is rooted and running 7.1.1 not bad either. Whatever you decide to do, good luck!
Sent from my SM-N910P using Tapatalk
Modtronix said:
I would think that yes, you will have to unroot and then I would take it to a Verizon store and ask them to flash it. I know Sprint will. I had a bad ota. They fixed it free as well. I can tell you that 6.0.1 is solid. This one is rooted and running 7.1.1 not bad either. Whatever you decide to do, good luck!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. I might have to end up going and have them just flash it. I was wondering if I could avoid going over there. If perhaps there was a way to reset the phone through Odin or something. Glad to know 6.0.1 is solid as well! cheers!:good: