Related
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.
This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.
beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.
The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?
SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?
I dont think that method will work.
Read here: http://www.needrom.com/download/row-s422/
please help me too..!!!
shinudgr8 said:
So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?
Click to expand...
Click to collapse
i had tried everything no use.. anyone please help to root the update version... lenovo k3 note...:crying::crying::crying::crying::crying::crying:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
it work well...
shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
no ya it works well.. but cant find a way root it....
ChainFire Beta SuperUser for Marshmallow K3 Note
Hi,
You may try the steps "androiding.how" on how to root the Lenovo K3 Note after the Marshmallow OTA update.
NOTE : THE ABOVE WOULD ONLY WORK THROUGH CWM/TWRP Recovery. Use the older Lollipop TWRP/CWM recovery. It should work.
Where is the link??
Fizix7 said:
Where is the link??
Click to expand...
Click to collapse
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!
massguy786 said:
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!
Click to expand...
Click to collapse
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?
I also got back to stock recovery from TWRP. but my update to marshmallow failed, can you help? I had rooted with Lenovo k3 note manager by prince3v. it also installed twrp. Using the same tool I went back to stock. Thanks.
shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
That supersu file is the one causing problem. I started from scratch, and got marshmallow working. But as soon as I flash data.zip file, it gets stuck at empty black screen. It works without supersu fine, sadly no root.
shinudgr8 said:
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?
Click to expand...
Click to collapse
LOL... It will work.. You are not the Guinea pig...
[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP
This is really simple but I'm guessing people are still wondering.
Download TWRP
Download SuperSU 2.76 Systemless (for Stock Kernels) or Download SuperSU 2.76 SystemMode (Permissive Kernel Required)
*Optional* Download a Permissive Kernel like BeastMode (only needed for System Mode SuperSu)
Download Odin
Put the SuperSU on your SD Card / Internal Storage
*Optional* Put Custom Kernel on SD Card (Optional, Only required if using SuperSu SystemMode)
Reboot into Download Mode
Flash TWRP in Odin
Boot into TWRP
Flash SuperSU
Enjoy!
For details on how to flash with Odin, flash with TWRP please see other threads or use Google.
Additional Downloads:
-N910T PE3 Stock Recovery
Additional Info:
NetFlix:
Some users have reported that NetFlix would not connect after rooting. There is no need to do this if you do not have any problems with NetFlix.
-Delete /system/vendor/lib/liboemcrypto.so and reboot.
------------------------------------------------------
Thanks of course to Chainfire & Teamwin
Also Thanks to freeza.
Cool. Thanks. it's same for all other mm roms too.
Is this Systemless root?
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your prior rooted device needs to be rerooted. Download SuperSu to phone. Download TWRP to computer. Odin TWRP. Once TWRP is flashed, boot to TWRP and install Supersu [at least that's what I did.]
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Click to expand...
Click to collapse
Odin flashing MM will overwrite your recovery.
Got it. Thanks fo clarifying that.
Sent from my SM-N910T3 using XDA-Developers mobile app
Question, have rooted and jail broke many but not this 910T yet. I am on non-root 5.1.1, should I take the OTA 6.0.1 and then follow the above instructions or download 6.0.1 from samsung and install via Odin and then start following these instructions? Would perfer to take over the air so I dont have to reset up everything.
Thanks in advance and I cant fn wait to start using Adfree again!
I downloaded via Kies. Didn't have to setup a thing after.
Sent from my SM-N910T using XDA-Developers mobile app
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
Agreed.
Anybody know if editing the platform.xml still works for SD card writing? And with the update I am getting the stupid -504 error in google play store trying to install Titanium backup......I might have to reflash ugh.
Edit*****
I fixed my issue
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
They will.
Man I hope not. We did a lot of *****in! Looks like HTC is gonna do the next nexus and should be on par with the N7 but I really don't want to do that. There is no way any phone can compare with the same phone rooted and custom. We will see.
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Has anyone flashed the new 6.0 MM BL and CP vs Flashfire?
The G.O.A.T. said:
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Click to expand...
Click to collapse
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
DeeXii said:
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
Click to expand...
Click to collapse
Yeah idk... It just worked this time. IF I was to say what I did different I booted into recovery first it started with applying update or something then crashed because no update was there, then showed stock MM recovery I then. Shutdown and went into download mode and did the OP.
It work!!!
Doing a new backup now