IT CAN BE DONE
Here's how I did it. (And don't blame me if you brick the phone, etc., etc....)
PLEASE DO NOT ATTEMPT IF YOU DO NOT UNDERSTAND THESE NOTES! Read them thoroughly!
1. Install stock NC2 (Instructions are all over)
2. Root with towelroot.
3. Install latest SU from the play store and update binary (you know the drill, right?)
4. See Chainfire's site here. http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 Get FlashFire
5. Place the AT&T stock lollipop .tar file on your SD card. It is available in the note 3 forum.
6. Run FlashFire. Once it has done its thing, click on the + sign.
7. Click on flash firmware package and navigate to the stock .tar file.
8. FlashFire will analyze the file and you will see a screen with partitions checked. These are the partitions that FlashFire can write (AND ROOT)
9. Click the download sign at the top on the red bar.
10. Click on the check mark to Create New Archive (FlashFire will create a .tar.md5 file take note of where it is saved and COPY TO YOUR PC BEFORE you run FlashFire! You will need it!
11. Next you will see the screen with ACTIONS on a red bar. Scroll to the bottom and touch FLASH
12. FlashFire will now write the partitions that are checked. When it reboots the phone, IMMEDIATELY hold the volume down, home, and power button to enter download.
13. Go to your PC where you copied the archive (that .tar.md5 fike). Right click on the file and choose rename. Remove the .md5 from the file name or odin will likely give you an error.
14. Open odin and connect your phone. Place the .tar archive FlashFire created in the AP section and flash. It will write the partitions that FlashFire could not.
15. Reboot and enjoy rooted lollipop on your phone.
Hate that I still have to wipe data to get it to boot at all, but a minor gripe I suppose. Just hate having to reinstall my apps and set them back up. Thanks for sharing this, been waiting for something like this for a while!
Yeah but if you're already on rooted nc2, why not just flash the stock rooted lollipop rom?
Doesn't that process require using SafeStrap, where this process does not?
netracerx said:
Doesn't that process require using SafeStrap, where this process does not?
Click to expand...
Click to collapse
You can use flashfire...
Plus why go through all this hassle to reach the same result?
That's absolutely true. but think it is a matter of preference. I had some issues with Safestrap, but were it still supported for lollipop, I would probably still be there. I also had a soft brick when I attempted to do a backup, which supposedly still works by booting from the power screen. SO for those who would prefer a cleaner option, this might suit them better. Flashfire also has the potential to install other custom roms. I am still looking at that option.
swapavi said:
You can use flashfire...
Plus why go through all this hassle to reach the same result?
Click to expand...
Click to collapse
this is the first post i've seen for the N900A that advised using Flashfire, all other posts required using Safestrap (which i personally did not like the idea of using just because it wasn't actually updating the OS on the phone, but essentially tricking the phone into loading a different set of files much like multi-booting). if it were possible to use Flashfire with the rooted lollipop roms, i'm surprised none of the thread OPs updated their posts to reflect that.
FlashFire has only been out since April. It is Chainfire's successor for Mobile Odin. It takes a while for all of the phones to be tested. There are a couple of other users that have tested it. Just search the FlashFire forum for Note 3 and you can read the comments. At least one other has used it on the AT&T variant.
reboot into download mode
I just finished your method successfully. Thank you. I would like to add that there was an option to reboot into download mode after flashing with FlashFire. I didn't have to worry
about immediately holding vol. down . I think the version of FlashFire I used is a little newer. Anyway thanks again!
I will keep trying
Hi all,
I was able to go through all the steps but keep getting stuck on step 14. Odin fails at the very very end and never finishes. I have done the whole process 3 times over.
Questions:
1. When picking the .tar in step 7, I am selecting the largest file of lollipop. I believe it is an AP file about 2.2 Gigabytes. This is the right one to select in step 7??
2. On step 10 when it ask you to Create New Archive, do i check ALL the boxes?? Nothing is checked by default when i press the download sign in step 9.
Other than these two things, everything else seems to work nicely. I did also notice that when Flash Fire runs and writes the system, wipe is set to OFF. I figured it was like that on purpose but just saying.
Thanks in advance,
John :good:
Sorry for the delay. I have moved on to the S6, so been busy with it.
For step 7, choose whichever ROM you wish to use. The one you have should be fine.
With regards to the second question, Flashfire should check the files in step 8 that are needed for the archive. Are you using a stock rom for step 7? If not, it might be able to flash without a separate tar file.
Ok,
Yes it was stock and thanks for the tip i will give this a shot as soon as i can and see how it goes.
So this will work to Root the Note III on Lollipop?
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
fitzly said:
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
Click to expand...
Click to collapse
Great Guide and find.
Flashfire has the power to bypass the security that would provent Odin from installing , for example a custom kernel, so be carefull with Flashfire, it installed a custom kernel on my phone and flagged Knox to a 1
Followed the steps in the 1st post...worked flawless! May I add its good to clear cache & delvic cache as well
Sent from my SAMSUNG-SM-N900A using Tapatalk
Excellent. I don't like Safestrap, so this was perfect... I didn't have to wipe my phone, and everything went perfectly the first time. One note, I did have to put my phone in Download Mode (as stated in the OP) after the reboot from Flashfire. Thanks so much to all who worked on this!
Update: The OC2 update happened pretty much immediately after I booted. The OTA update actually managed to complete, and I still have root.
I am currently on 4.3 MI9 version..
i rooted it with chainfire method root de la vega.
Now can i flash NC2 with odin and continue the thing ?
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Chocu1a said:
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Click to expand...
Click to collapse
look here, if you still have issues let me know
http://forum.xda-developers.com/showthread.php?t=2703006
Related
Here is my Note 4 Guide. I did one for the note 3 so figured i will throw one up for note 4 so it might look familiar to it! Sorry this one is a little late but here it is!
I TAKE NO CREDIT I AM NO DEVELOPER! THIS IS MERELY A GUIDE!!
UNDERSTAND ROOT/RECOVERY WILL VOID YOUR WARRANTY
Part 1: Flashing TWRP onto Developer Note 3
Step 1- Download and install Odin onto Windows PC http://uploaded.net/file/o2xcp01n
Step 2- Download Verzion TWRP Tar File (openrecovery-twrp-2.8.1.1-trltevzw.img.tar) http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.1.1-trltevzw.img.tar
Step 3- Flash your Verizon TWRP Tar File your just downloaded in Odin under the AP Slot ONLY!
BE CAREFUL IF YOU PLACE IN WRONG SLOT DEVICE WILL BE A BRICK!
Side note phone will now say Set Warranty Bit: Recovery when booting into recovery. Don't worry this is normal. This is showing you what tripped warranty. More about this below later in guide.
Step 4- Flash Superuser if TWRP doesn't ask you to root http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
Step 5- Make a complete backup of EVERYTHING in TWRP. Boot, Recovery, System, Data, Cache ALL OF THEM I have backed up to internal sdcard & external sdcard & even throw a backup on your pc just in case something catastrophic happens since we have no Odin stock files still!
Step 6- (optional) Flash a rom/kernel.
Rom Section: Only one stock rooted, deodexed, Knox-Free rom so far
Thanks @EMSpilot!!
http://forum.xda-developers.com/not...rom-stock-root-odex-deodex-knox-free-t2949569
Kernel Section: While there is no verizon specific kernels there are ones that will work. I have flashed ktoonsez's kernel over in the T-Mobile side of things and it does work. Haven't been on long but it will flash. I am testing now how much better it is then stock. Always have your boot.img ready to go and/or your stock backup in TWRP ready to restore the boot if required. Some other carrier kernels will not play nice with it but from what i have expereienced with Note 4 so far and the Note 3 T-Mobile kernels will work without any hassle. So continue to check back here for updates!
Thanks @ktoonsez!
http://forum.xda-developers.com/not...lopment/kernel-kt-note4-nih-ktweaker-t2936809
Step 7- Enjoy!
Part 2: Restoring Boot.img if phone will not boot after rom or kernel install
If you get a kernel that won't run properly or boot loop or a rom that will not boot on the developer edition without proper boot.img here is how you fix.
Step 1- Boot into TWRP. From phone being off use three finger method of vol up, power and home button to boot into TWRP.
Step 2- Restore boot.img from the very important backup in step 5 from part one! This is why you have to have a backup of everything! Restore the boot.img only and reboot!
Step 3- Back to enjoy!!
I do not take any credit for roms/kernel/recovery just sharing links and what I have done. Hope this guide helps!! Please continue to check back here for updates on roms/kernels or other helpful Developer Edition info!
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
keithce said:
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
Click to expand...
Click to collapse
yes it does and oh i havent experienced that. i actually flashed stock kernel again to get a good baseline for battery life and such for a week or so before i start going off the deep end with kernels! haha what settings did you change?
bobbarker2 said:
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
Click to expand...
Click to collapse
there wasnt when i looked but i will have to check them out! any special settings you are using!?
yesterday i successfully rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
glennnall said:
yesterday i successfully
rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
Click to expand...
Click to collapse
Follow these instructions and you will have a custom recovery installed on your SM-T530. Yes I know the title of the post is root your tablet, but this is accomplished by installing a custom recovery. Nobody here is going to take much pity on you for not understanding the terminology, we all took it upon ourselves to learn it at some point or another, it just kind of comes with the territory. XDA University can be very helpful if you feel lost or overwhelmed
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
glennnall said:
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
Click to expand...
Click to collapse
Yes this will install safely over your current configuration. PDA button is the correct option, on newer versions of Odin it is renamed AP, sorry. You should be using at least Odin 3.07
Since you're already rooted, you shouldn't have to worry about the auto reboot, but do install that newer version of superSU at some point, it's designed for lollipop, works better than old versions.
can I run this on top of my rooted Tab, or do i need to "unroot" it?
yesterday, CF Auto Root installed SuperSU already, so i don't know which of these following instructions to follow... can i just run all of these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
sorry, reposted in my impatience. thanks for the help.
ok, great - worked as advertised.
SuperSU updated normal, reboot, now i'm sitting on "Samsung" ... hmmm...
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!
I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......
How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?
Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.
just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method
Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.
^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!
Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.